Adam Lally (JIRA) wrote:
[ https://issues.apache.org/jira/browse/UIMA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501723 ]
Adam Lally commented on UIMA-402:
---------------------------------
Marshall wrote (on uima-dev):
Basic thought: if the user of the CDE sets it up so the soap axis jars
are available (is there a way to do that?), then things would work nicely.
The jars would have to be listed in the uima runtime plugin manifest. So
unless we wanted to ship the plugin with extra entries in its manifest, this
would require the user editing the manifest file which is pretty ugly. Or is
there another way?
I think there is another way, but before going there -
Is it reasonable to just include the Axis JARs in the UIMA Runtime
Plugin (as well as put them in the manifest)? If the JARs are Apache v2
licensed, there should not be any legal issue. Are there any technical
issues (e.g. the JAR implements some classes which collide with other
classes, or there are many "versions" and the user would need to pick
the right version)?
The other way: Package the Axis JARs into a "fragment" plugin. Perhaps
we may need several of these, depending on Axis version requirements.
Then add right one to the Eclipse plugin directory. Fragments are a way
to add stuff to an existing plugin.
Exactly how to do this might depend on versioning requirements for Axis.
-Marshall
