Bug 979310 - Update archetype jboss-spring-mvc-archetype to reference correct versions from EAP 6.1.0 and WFK 2.3.0 maven repositories
Summary: Update archetype jboss-spring-mvc-archetype to reference correct versions fro...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Spring
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 2.3.0
Assignee: Tejas Mehta
QA Contact: Tomas Repel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-28 08:07 UTC by Tomas Repel
Modified: 2013-10-22 12:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-16 11:32:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JDF-393 0 Major Resolved Update archetype jboss-spring-mvc-archetype to reference correct versions from EAP 6.1.0 maven repository 2015-09-01 03:09:08 UTC

Description Tomas Repel 2013-06-28 08:07:03 UTC
Description of problem:

Use the archetype org.jboss.spring.archetypes:jboss-spring-mvc-archetype:1.0.0.Final to generate a project, set enterprise property to true.
The versions in generated pom.xml should be aligned for use with WFK 2.3.0 and EAP 6.1.0 maven repositories.
change version of com.redhat.jboss.wfk.boms:spring-3.2-bom to 2.3.0-redhat-1,
change version of org.jboss.bom:jboss-javaee-6.0-with-hibernate to 1.0.4.Final-redhat-wfk-2
add dependency (either to <dependency> or <dependencyManagement> section):

<dependency>
  <groupId>dom4j</groupId>
  <artifactId>dom4j</artifactId>
  <version>1.6.1-redhat-5</version>
</dependency>

The pom.xml also defines property `version.spring` (with value 3.2.2.RELEASE) that is never used (the Spring Framework version is specified by Spring-3.2 BOM).

Version-Release number of selected component (if applicable):

org.jboss.spring.archetypes:jboss-spring-mvc-archetype:1.0.0.Final
WFK 2.3.0.CR1
EAP 6.1.0

How reproducible:

Always.

Steps to Reproduce:
1. generate project using jboss-spring-mvc-archetype, version 1.0.0.Final
2. build project using WFK 2.3.0.CR1 and EAP 6.1.0 maven repositories

Actual results:

[ERROR]     Non-resolvable import POM: Failure to find com.redhat.jboss.wfk.boms:spring-3.2-bom:pom:2.2.0-redhat-1 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central-repository has elapsed or updates are forced @ line 45, column 25 -> [Help 2]
[ERROR]     Non-resolvable import POM: Failure to find org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:1.0.4.Final-redhat-wfk-1 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central-repository has elapsed or updates are forced @ line 53, column 25 -> [Help 2]

Expected results:

It builds without errors.

Comment 1 Tejas Mehta 2013-06-28 13:30:15 UTC
Fixed here: https://github.com/jboss-eap/wfk-archetypes.

Should I wait till WFK 2.3 GA, to release it?

Comment 2 Marek Novotny 2013-07-01 06:36:12 UTC
You don't have to wait for WFK 2.3.0 release. Stage the release and let QE know to verify that. That's enough.

Comment 5 Tomas Repel 2013-07-02 14:07:41 UTC
Verified, the staged archetype works with WFK 2.3.0 and EAP 6.1.0 maven repositories.

Comment 8 JBoss JIRA Server 2013-10-22 12:47:13 UTC
Tomas Repel <trepel> updated the status of jira JDF-393 to Resolved


Note You need to log in before you can comment on or make changes to this bug.