Make scripts default to the current pax construct version when finding
archetypes
---------------------------------------------------------------------------------
Key: PAXCONSTRUCT-10
URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-10
Project: Pax Construct
Issue Type: Improvement
Components: scripts
Affects Versions: 0.1.4
Reporter: Stuart McCulloch
Assigned To: Stuart McCulloch
Priority: Minor
Fix For: 0.1.5
The maven archetype creator defaults to the RELEASE metaversion when it looks
for the archetype artifact, this resolves to the most recent release of the
archetype. Unfortunately, when running maven offline this can cause build
errors as it tries to contact the repository to check the latest released
version.
At the moment, this can be worked around by using the PAX_CONSTRUCT_OPTIONS
environment variable:
export PAX_CONSTRUCT_OPTIONS=-DarchetypeVersion=0.1.4
which can be used to force the archetype version to a known level, skipping the
metaversion check.
Perhaps this should be done by default - the only problem is that people would
need to download a new set of scripts each time a release was made.
Alternatively, we could only override the archetypeVersion setting if the
PAX_CONSTRUCT_VERSION environment variable is set to a specific release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
