Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Ian Evans
Reporter: Ian Evans
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Archetypes should generate stand-alone pom.xml files

Created: 21/Jun/13 08:34 PM   Updated: 21/Jun/13 09:11 PM   Resolved: 21/Jun/13 09:11 PM
Component/s: examples
Affects Version/s: 7.0.1
Fix Version/s: 7.0.2

Time Tracking:
Not Specified

Participants: Ian Evans

 Description  « Hide

Currently the archetypes in First Cup and the Java EE 7 Tutorial have the parent set. This can cause errors if the parent pom hasn't been installed yet.

Since these archetypes are presumably going to be used by developers for their own applications, it's better to make the generated project's pom.xml standalone, with the necessary dependencies and configuration all in the pom.xml file, not inherited from our project's pom.xml file hierarchy.

Ian Evans added a comment - 21/Jun/13 09:11 PM

Fixed in the source. Will appear in the 7.0.2 release.