Hi Guillaume,
you're right, the archetype build is not totally correct as
archetype-catalog analyzes the local repository, so it should be
executed after all archetype sub-project.
If all are OK, I propose three alternatives:
1/ I rollback the release. If we consider that the catalog is not
required (as repository managers such as Nexus automatically create
catalog), I remove the archetype-catalog and submit a new release.
2/ I rollback the release, move the archetype-catalog build after the
archetype modules and submit a new release
3/ I close the release vote, the archetype-catalog will be uploaded and
fix by hand.
What do you think ?
Regards
JB
On 08/27/2010 11:13 AM, Guillaume Nodet wrote:
The catalog contains snapshots instead of the released version:
https://repository.apache.org/content/repositories/orgapacheservicemix-134/org/apache/servicemix/tooling/catalog/2010.01/catalog-2010.01.xml
So I'd suggest to either fix it or remote it from the release if we
don't need it.
On Mon, Aug 23, 2010 at 11:40, Jean-Baptiste Onofré<[email protected]> wrote:
Hi,
The ServiceMix Archetypes 2010.01 release includes:
- usage of ServiceMix 2010.01 Components (with transitive dependencies like
Camel, CXF, ActiveMQ)
- one archetype per component, the archetype now provides all endpoints
sample in one xbean.xml
- no license stamping in generated resources
- new archetypes (like exec, mail, vfs, etc)
Staging repository:
https://repository.apache.org/content/repositories/orgapacheservicemix-134/
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks
Regards
JB
