Hi,
*** NOTE ***
This release depends on the pending 1.3 release of
maven-common-artifact-filters. You will need BOTH of the staging
repositories listed below in order to build the maven-assembly-plugin.
We solved 92 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126&ver
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15582
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSH
yes, using maven-archetype packaging is recommended since it adds some
lifecycle bindings to simple jar:
- add-archetype-metadata
- integration-tests
- update-local-catalog
see [1]
for your second point, I don't know: perhaps the nexus plugin that generates
archetype-catalog.xml only considers
[Originally posted to d...@mojo without response. This might be the more
appropriate list, so reposting here also with some updates.]
Recently I worked on an IDE feature [1] which enumerates archetypes available in your local repository that you might want to instantiate projects from, so you c