Bug 972746
| Summary: | Archetypes use different BOM versions than what is in repository | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | rfalhar |
| Component: | Examples, Maven | Assignee: | Pete Muir <pmuir> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Matous Jobanek <mjobanek> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.3.0 | CC: | bsutter, kpiwko, mnovotny, oskutka, pmuir, rruss |
| Target Milestone: | GA | ||
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-16 15:58:24 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: | |||
|
Description
rfalhar
2013-06-10 14:06:06 UTC
Complete report for newest archetype versions: jboss-html5-mobile-archetype:7.1.3.CR6 requires: jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-wfk-1 jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-wfk-1 jboss-errai-kitchensink-archetype:2.2.1.Final requires: jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-wfk-1 jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-wfk-1 jboss-javaee6-webapp-archetype:7.1.3.CR6; same with -ear version requires: jboss-javaee-6.0-with-tools:1.0.2.Final-redhat-1 jboss-javaee-6.0-with-hibernate:1.0.2.Final-redhat-1 spring-mvc-webapp:1.0.0.CR8 requires: spring-3.2-bom:2.2.0-redhat-1 jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-wfk-1 All should use WFK 2.3.0 related versions: jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-wfk-2, jboss-javaee-6.0-with-tools:1.0.2.Final-redhat-2 spring-3.2-bom:2.3.0-redhat-1 @Radek, please create JDF issue for these archetypes to get that fixed as they are asynchronously handled. Rafael Benevides <benevides> updated the status of jira JDF-377 to Coding In Progress Rafael Benevides <benevides> made a comment on jira JDF-377 jboss-errai-kitchensink-archetype and spring-mvc-webapp are not managed by JDF. A issue should be opened to Errai team for jboss-errai-kitchensink-archetype Rafael Benevides <benevides> made a comment on jira JDF-377 Working with JDF-364 in this repository. Rafael Benevides <benevides> updated the status of jira JDF-377 to Resolved Rafael Benevides <benevides> made a comment on jira JDF-377 7.1.3.CR7 released Migrated to JIRA Jonathan Fuerth <jfuerth> made a comment on jira ERRAI-575 We can't update artifacts that were already deployed to Maven Central. We double-checked that we were using the correct version before publishing the archetype that's presently there. I tested it myself. The runtime variable for WFK version is a very good idea, but I wasn't aware that the version number was going to change before WFK went GA. Jonathan Fuerth <jfuerth> updated the status of jira ERRAI-575 to Resolved Rafael Benevides <benevides> updated the status of jira WFK2-31 to Closed Rafael Benevides <benevides> made a comment on jira WFK2-31 Fix was available on 7.1.3.CR7. I'm releasing 7.1.3.CR9 today Rafael Benevides <benevides> made a comment on jira WFK2-31 7.1.3.CR9 released Pete Muir <pmuir.uk> updated the status of jira WFK2-31 to Reopened Pete Muir <pmuir.uk> updated the status of jira WFK2-31 to Resolved Marek Schmidt <maschmid> updated the status of jira WFK2-31 to Closed Marek Schmidt <maschmid> made a comment on jira WFK2-31 out of date Christian Sadilek <csadilek> updated the status of jira ERRAI-575 to Closed |