+1
I could make my archetypes, deploy, and use mvn archetype:generate no
problem. The old way works fine too now as I've had a bunch of scripts
forever I've used and they all spit out project that build.
On 18-Feb-08, at 4:18 PM, Brian E. Fox wrote:
Rerolled to correct the tag and 2 header issues identified by Brett.
The most important early issues have been fixed and we need to get
this
out there. The site is updated and here's the list of issues fixed:
Staging repo: http://people.apache.org/~brianf/staging-repository
Release Notes - Maven Archetype - Version 2.0-alpha-2
** Bug
* [ARCHETYPE-128] - Unable to create a Cocoon app with Maven
archetype: [WARNING] No archetype repository found.
* [ARCHETYPE-133] - POMs generated as part of create-from-project
are not correct and prevent using this feature completely
** Improvement
* [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer
respected
* [ARCHETYPE-117] - return previous defaults
Because of the urgent nature of this release, this vote will be open
for
24hrs unless someone objects.
+1
--Brian
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
