Bug 887496
| Summary: | xbean: xbean-spring module is disabled | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Himpel <john> | ||||||||||
| Component: | xbean | Assignee: | Mikolaj Izdebski <mizdebsk> | ||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | rawhide | CC: | kdaniel, mizdebsk, puntogil, sochotni | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | 3.12-4 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | |||||||||||||
| : | 887502 (view as bug list) | Environment: | |||||||||||
| Last Closed: | 2012-12-17 13:24:49 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 664049 [details]
yum stderr
Created attachment 664060 [details]
yum list maven\*
Created attachment 664061 [details]
yum list xbean\*
xbean-spring package was disabled, but it's not obsoleted by anything. This breaks upgrade path. xbean-spring was temporarly disabled because of dependency cycle between eclipse and xbean packages. Krzysztof, can we re-enable xbean-spring package now? If I remember correctly xbean fails to build if support for spring framework was enabled because of the xbean-blueprint module (requested in bug #849955). Gil, do you have any solution for that, or should I disable xbean-blueprint and xbean-classloader modules for now? (In reply to comment #4) > If I remember correctly xbean fails to build if support for spring framework > was enabled because of the xbean-blueprint module (requested in bug > #849955). Gil, do you have any solution for that, or should I disable > xbean-blueprint and xbean-classloader modules for now? if I remember correctly the problem only exists only with xbean-blueprint module caused by unavailable deps: org.apache.aries.blueprint org.apache.aries.blueprint.api 1.0.0 org.apache.aries.blueprint org.apache.aries.blueprint.cm 1.0.0 already packaged http://gil.fedorapeople.org/aries-blueprint-api.spec http://gil.fedorapeople.org/aries-blueprint-cm.spec (in rawhide is available "only" aries-blueprint 0.3.1 but 0.3.x and 1.x have incompatible apis) regards > or should I disable
> xbean-blueprint and xbean-classloader modules for now?
yes sure thanks
ops, sorry for the noise classloader module shouldn't be a problem depend on maven-xbean-plugin and spring-beans I believe that this bug is fixed in xbean-3.12-4, which is available in Fedora Rawhide. I am closing the bug now, thank you for reporting it. A summary of changes is included below. * Mon Dec 17 2012 Mikolaj Izdebski <mizdebsk> - 3.12-4 - Enable xbean-spring, resolves rhbz#887496 - Disable xbean-blueprint due to FTBFS xbean-3.12-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/xbean-3.12-4.fc18 |
Created attachment 664048 [details] yum standard output Description of problem:When I use yum to install latest rawhide packages of 12/13/2012, I get the attached output Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.yum upgrade 2. 3. Actual results: See attached Expected results:Packages updated Additional info: