with ${maven.home}, you can have your use case
for other options:
- POM is a nonsense to me
- WORKINGDIRECTORY too: notice that it can be done with ${user.dir}, if you
really want to
the more I'm thinking at this, the more I'm convinced we should not accept
relative path at all: with java system properties, you already have a lot of
choice (user.home, user.dir, maven.home). And if you really want something
more flexible, just define a convention in your organization to set an
environment variable that is required
but adding a feature to Maven for that is an anti-pattern IMHO
Just for the record, if you provide a patch, please have a look at code
conventions [1], and IDE configurations to have them directly done by your IDE
Regards
Hervé
[1] http://maven.apache.org/developers/conventions/code.html
Le dimanche 18 septembre 2011, Jason Pyeron a écrit :
> > -----Original Message-----
> > From: Manfred Moser
> > Sent: Sunday, September 18, 2011 0:24
> > To: Maven Developers List
> > Subject: Re: Request for review and comment
> > http://jira.codehaus.org/browse/MNG-5167
> >
> > On 11-09-17 08:55 PM, Jason Pyeron wrote:
> > >> -----Original Message-----
> > >> From: Manfred Moser
> > >> Sent: Saturday, September 17, 2011 23:38
> > >> To: dev@maven.apache.org
> > >> Subject: Re: Request for review and comment
> > >> http://jira.codehaus.org/browse/MNG-5167
>
> <snip/>
>
> > >> Cludging something into Maven itself feels wrong to me.
> > >
> > > What part of the patch is cludgy, I would like to fix it.
> >
> > The patch by itself might not be but in my feeling it goes
> > against the general design of Maven and might have problems
> > associated to it in various use cases beyond your specific example
> >
> > Taking on the patch means providing documentation for it and
> > support into the future and around use cases others come up
> > with together with plugins and so on. At a minimum I would
> > suggest to have that all done as well as some IT tests around it.
>
> Thank you. I have been struggling on the tests aspect, do you have any
> recommendations? I will create better documentation too.
>
> > I can see this feature being used by a lot of people coming
> > from manual dependency management and never actually getting
> > the benefits of Maven due to being stuck with this approach
> > since that is how they started.
>
> Agreed, I will try to show how to leverage maven in the maven way too
> (prevent anti-patterns)
>
> -Jason
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
