The wizard should create a runnable JAR file despite the warnings. Have you
tried running that? Some files may be provided by multiple bundles but as
long as they are the same it should not matter.
A jar file is in fact produced. Alas, I get a stack dump when I try running it as per the wiki's instructions. I opened a bugzilla issue for it here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243830Interestingly, when I manually put what I think to be all of the jars that the mylyn/bugzilla headless stuff depends on on my classpath I get a very similar looking stack dump when I try to run the simple example from the wiki.
Am I doing something wrong? I'd wonder if perhaps there's not something provided by the org.eclipse core and runtime stuff that I need to instantiate or mock in some way to keep the mylyn stuff from blowing up on the NPEs...?
Using the export wizard is the easiest way I know of to get a runnable JAR
file with a standalone distribution. I read a while ago that there is some
effort under way to provide a Maven repository that would support automatic
resolution of dependencies for headless builds with Maven but I don't know
far a long that project is.
That would be terrifically useful to me, as my project's build is maven-based. Do you know any of the people involved in that work that I could contact? I found some kind of old mylyn JARs in some maven repositories, but they seemed to be missing some of their dependencies as well as pretty old.
Please note, that the Team project set only contains the dependencies for
Bugzilla. To build a standalone distribution for the JIRA connector you will
need the org.apache.axis plug-in including all dependencies:
http://wiki.eclipse.org/Mylyn/Libraries.
I was expecting JIRA to be another ball of SOAP-dependent wax after the bugzilla example, to be tackled next... :-)
Best regards,
Jerry
