Bug 497130
| Summary: | Include OSGi metadata | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Overholt <overholt> |
| Component: | wsdl4j | Assignee: | Deepak Bhole <dbhole> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dbhole |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-04-22 20:53:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 251747 | ||
|
Description
Andrew Overholt
2009-04-22 13:37:20 UTC
Sorry, I am not too familiar with OSGi and how eclipse uses it. The axis rpm has multiple jars: $ rpm -ql axis | grep jar$ /usr/share/java/axis/axis-1.2.1.jar /usr/share/java/axis/axis-ant-1.2.1.jar /usr/share/java/axis/axis-ant.jar /usr/share/java/axis/axis.jar /usr/share/java/axis/jaxrpc-1.2.1.jar /usr/share/java/axis/jaxrpc.jar /usr/share/java/axis/saaj-1.2.1.jar /usr/share/java/axis/saaj.jar Which ones should the manifest be added to? In my first comment I said "in this page" when I meant "in this package". Sorry. What we need is one of the wsdl4j JARs (if there is more than one) to contain the META-INF/MANIFEST.MF OSGi data. It can be in any of the JARs as long as we know which one it is so that we can symlink it into our build directory and install directory. Equinox (the OSGi runtime) will take care of finding the metadata and determining the bundle version, etc. from there. The linked manifest appears to be for wsdl4j. Are you sure the manifest for axis needs to be changed for this? There is a separate wsdl4j package that provides ws4l4j.jar and it appears to be the right place for the manifest changes. This bug is filed against wsdl4j. Doh! Sorry about that, for some reason I've been thinking it was against axis :( Wsdl4j already had a manifest, but the version was lower than what axis needed. I have bumped the version in the manifest to match the actual version. Please give it a try now and let me know if there are any problems: http://koji.fedoraproject.org/koji/taskinfo?taskID=1315665 This works great from within Eclipse. The real test will be to build against it and verify that functionality works but for now I think we're good. Thanks! |