1.0-alpha-6 release of archetype plugin is hosed
I had to edit my local copy of the plugin pom to look like this;
org.apache.maven.archetype
maven-archetype-model
1.0-alpha-6
org.apache.maven.archetype
maven-archetype-core
1.0-alpha-6
org.apache.maven.archetype
maven-archetype-creator
1.0-alpha-6
it did look like this;
org.apache.maven.archetype
maven-archetype-model
1.0-alpha-5
org.apache.maven.archetype
maven-archetype-core
1.0-alpha-5
org.apache.maven.archetype
maven-archetype-creator
1.0-alpha-5
Which causes the archetype plugin to fail because the 1.0-alpha-5
stuff does not exist.
TTFN,
-bd
The maven team is pleased to announce the maven archetype plugin
1.0-alpha-6 release.
This release substitutes the failed 1.0-alpha-5 release too.
Issues fixed
ARCHETYPE-78 Dependencies listed as version ${project.version} in
maven-archetype prevent the use of archetypes
ARCHETYPE-60Archetype Documentation Incorrect
ARCHETYPE-38The archetype is using user.dir which prohibits
clean embedding
Change log
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&pid=11095&fixfor=13683
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&pid=11095&fixfor=12413
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Bill Dudney
MyFaces - http://myfaces.apache.org
Cayenne - http://incubator.apache.org/projects/cayenne.html
Re: proposed mailing lists names
+1 (non-binding) Bill Dudney MyFaces - myfaces.apache.org On Mar 6, 2006, at 12:01 AM, Brett Porter wrote: Since we've voted to do this, I'm just going to give people 48 hours to object to these particular names. [see MPA-50] Our dev list traffic has gone nuts. Let's create: [EMAIL PROTECTED] * this will be for CI, error reports from the repository manager, and so on * depending on policy, this may not be archived (we won't archive it unless it's required - I don't think it's necessary, but there is no harm in it if it is) * this will be for all maven projects (ie, no continuum- notifications, etc). [EMAIL PROTECTED] * this will be for JIRA issues. For now, just one will be created. If it is later determined to split one set off, we can create more. commits@maven.apache.org * for commits - we already have it (each subproject has its own) dev@maven.apache.org * for human discussion - we already have it Note that all subscribers to dev@maven.apache.org will be automatically subscribed to these lists at creation, but going forward you will need to subscribe to each individually. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1779) properties not being replaced before being passed to plugins (specificaly the surefire plugin)
[ http://jira.codehaus.org/browse/MNG-1779?page=all ]
Bill Dudney updated MNG-1779:
-
Attachment: transcript.txt
> properties not being replaced before being passed to plugins (specificaly the
> surefire plugin)
> --
>
> Key: MNG-1779
> URL: http://jira.codehaus.org/browse/MNG-1779
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle, Plugin API, maven-surefire-plugin
> Versions: 2.0.1
> Reporter: Bill Dudney
> Attachments: foo-root.tar.gz, transcript.txt
>
>
> in the attached foo-root proj run mvn package from foo-root and you will see
> that ${project.build.directory} is not substituted but
> ${project.x.build.directory} is.
> I spent a bit of time chatting with jdcasey on irc on Dec-07-2005 about this
> issue if that helps.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1779) properties not being replaced before being passed to plugins (specificaly the surefire plugin)
properties not being replaced before being passed to plugins (specificaly the
surefire plugin)
--
Key: MNG-1779
URL: http://jira.codehaus.org/browse/MNG-1779
Project: Maven 2
Type: Bug
Components: Plugins and Lifecycle, Plugin API, maven-surefire-plugin
Versions: 2.0.1
Reporter: Bill Dudney
Attachments: foo-root.tar.gz
in the attached foo-root proj run mvn package from foo-root and you will see
that ${project.build.directory} is not substituted but
${project.x.build.directory} is.
I spent a bit of time chatting with jdcasey on irc on Dec-07-2005 about this
issue if that helps.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
