Empty extension won't load
Hi, I have an extension with no written code from me but it still won't load (I get the error 2016-08-09 10:45:56,362 [ Launch callback handler] ERROR eam.repository.provision.internal.ProvisionService - CRJZS0383E The "adv3" bundle could not be resolved
(translated)
Here's my plugin.xml
http://pastebin.com/6jt0c7QdFor clarification, my project is called adv3, my class is called AbstractService (and only has the Interface IOperationParticipant implemented and the extended Methods included from com.ibm.team.repository.service.AbstractService)
My class is in a package, also named adv3.
Here's my MANIFEST.mf
http://pastebin.com/aSK6ZsbJ
Here's my feature.xml:
http://pastebin.com/9GpEDMTXand here my site.xml: http://pastebin.com/3tRkETX1I can't find a clue why it won't resolve. Weird thing is I have the same project but with and Advisor instead of a Participant and it works.... Thanks |
Accepted answer
|
I accidentally had a client plugin in my dependencies.
Please mark as solved.
Thank you
Ralph Schoon selected this answer as the correct answer
|
One other answer
Ralph Schoon (63.5k●3●36●46)
| answered Aug 09 '16, 6:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Aug 09 '16, 6:13 a.m.
http://pastebin.com/6jt0c7Qd
defines a class and package implementationclass="adv3.AbstractService", that apparently is not there. It can't find the package adv3. Comments oh and I translated the error wrong, It should say:
The "adv3" bundle could not be resolved
sorry
Then you will have to find it yourself, as the provided data and explanation does not support enough information about the deployment process. Be assured that I have found errors like that to have a good reason that usually revealed itself at some time.
If this is a real deployment (not Jetty) it is most important how the build.xml looks like and what is in the deployed features and the plugins.
What do you mean with build.xml? Where is it? Sorry, build.properties alongside the plugin XML.
source.. = src/
output.. = bin/
bin.includes = META-INF/,\
.,\
plugin.xml
That's in both build.properties, in the one that's working and in the one that's not
Got it, thanks for your help!
showing 5 of 8
show 3 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.