Community
Participate
Working Groups
Some COSMOS plugins have dependencies on axis2 jar files. These jar files are added during the build, but removed from the packaging. So at runtime, the manifest files will have missing dependencies. It may cause runtime problems. (It mainly affects the COSMOS SDK.) We need to make sure COSMOS plugins are loaded properly with no dependency errors. One suggestion for handling the axis2 jars is to create an empty axis2 plugin. COSMOS plugins depend on this plugin. We will need to ask users to copy jar files into this plugin. There may be other solutions...
I will prefer empty axis-2 plugin as it will be easy for user and build to copy the jar at one location in place of different locations. Please let RE team know once cosmos plugins modified to use this new empty axis2 plugin.
Adding a couple of ppl to the cc: list who might have input or requirements.
Where does this issue stand? Do we still favor the empty Axis2 plugin approach? If so, who is planning to initiate this effort?
I checked in new plugin "org.apache.axis2" into data-collection module. Please modify other required plugins to use this new plugin.
All the example MDRs will need to be updated for this change. Saurabh, will you be making those changes? Basically, all projects that depend on axis2 (i.e. those for which we are now copying the axis2 jar file into the lib dir) need to change. If you won't be making those changes, please create a separate bugzilla so the work can be planned and assigned.
I will start making the remaining changes related to this defect.
(In reply to comment #6) > I will start making the remaining changes related to this defect. except for the change in bug 244154, which I will probably need to make due to the learning curve
Modified other data-collection project to use this new Axis2 plugin. Request developers to check the changes and let us know if anything else required to be done for this.
Closing this one as we do provide empty Axis2 plugin into cosmos to have dependency on it.
