+1
Additionally, I feel that we should treat properties defined from the
CLI as equivalent to properties defined in settings.xml
I see as perfectly valid to enforce no property substitution from the
CLI or from settings.xml in
/project/parent/(groupId|artifactId|version)
/project/(groupId|artifa
+1
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sun, Sep 20, 2009 at 8:17 PM, Olivier Lamy wrote:
> +1
>
> 2009/9/20 Benjamin Bentmann :
> > Hi,
> >
> > This is a prerequisite for the upcoming release of
+1
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sun, Sep 20, 2009 at 8:17 PM, Olivier Lamy wrote:
> +1
>
> 2009/9/20 Benjamin Bentmann :
> > Hi,
> >
> > We solved 21 issues:
> >
> http://jira.codehaus.or
Making resolution of things from a repository dependent on an
environment is definitely dangerous. The only way I would consider it
valid is if there's some default provided in the pom itself, but
that's going to be difficult to enforce reliably I think.
On Mon, Sep 21, 2009 at 6:09 AM, Jason van
Hi,
I'm trying to figure out how to work the DefaultArtifactResolver class. I
just need to get Maven to resolve an artifact from the remote repository and
download it to the local repository and give me the path. I'm assuming that
after you pass an Artifact to the DefaultArtifactResolver's
resolve
I apologize for rewriting this without seeing Benjamin Bentmann's response
to my earlier letter. I fail at using mailing lists. Thanks very much for
the response.
On Fri, Sep 18, 2009 at 3:30 PM, Tristan JC Rouse <
tris...@tristanjcrouse.com> wrote:
> Hi,
>
> I'm trying to figure out how to work
On 2009-09-21, at 5:56 AM, Benjamin Bentmann wrote:
Hi,
The current fix for this issue makes me feel a little uneasy. As is,
the code in the 2.2.x branch applies profiles from the settings in
full extent to POMs of dependencies. In particular, properties
defined by profiles from the use
Hi,
The current fix for this issue makes me feel a little uneasy. As is, the
code in the 2.2.x branch applies profiles from the settings in full
extent to POMs of dependencies. In particular, properties defined by
profiles from the user's settings override properties in dependency POMs.
For