Has anyone verified that ARCHETYPE-38 really fixed the problem?
the current code snippet in MavenArchetypeMojo.java looks like this:
/**
* @parameter default-value="${user.dir}"
*/
private String basedir = System.getProperty( "user.dir" );
that still doesn't allow embedded use as one cannot pass
-Dbasedir="new directory" to the executed maven instance. I guess
expression="${basedir}" is missing..
vote: 0, as long as the old way works I'm fine.
Milos
On 8/24/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> +1
>
> On 24/08/2007, at 8:46 AM, Carlos Sanchez wrote:
>
> > Issues fixed
> >
> > ARCHETYPE-78 Dependencies listed as version ${project.version} in
> > maven-archetype prevent the use of archetypes
> > ARCHETYPE-60 Archetype Documentation Incorrect
> > ARCHETYPE-38 The archetype is using user.dir which prohibits clean
> > embedding
> >
> > Change log
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?
> > reset=true&pid=11095&fixfor=12413
> >
> > The release is staged at
> > http://people.apache.org/~carlos/staging-repo/
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
