Stephen Connolly wrote:
does it alter cr+lf pairs?
It looks for the artifactId element. It then copies the text from before
or after that element and puts that before or after itself depending on
whether the element is being added before or after the artifactId. In
all my tests it ends up lo
does it alter cr+lf pairs?
does it change formatting of attributes within tags (eg custom
enforcer rules)?
Sent from my iPod
On 29 Aug 2008, at 15:21, Ralph Goers <[EMAIL PROTECTED]>
wrote:
Yes. The original pom.xml is used and only the artifactId, groupId,
version or parent version a
Yes. The original pom.xml is used and only the artifactId, groupId,
version or parent version are modified or added as needed.
Benjamin Bentmann wrote:
Ralph Goers wrote:
This change will have a minor impact on existing projects. If you
don't specify the artifact's groupId or versionId (i.e.
Ralph Goers wrote:
This change will have a minor impact on existing projects. If you don't
specify the artifact's groupId or versionId (i.e. it is inherited from
the parent) then a new pom.xml should get created in the target
directory that has those fields filled in. That file will be the one
5:30 PM
To: Maven Developers List
Subject: Re: MNG-624 automatic parent versioning
On 13/06/2008, at 2:05 AM, Brian E. Fox wrote:
> Perhaps, but 10 releases into a branch isn't a great place for
> innovation
> either.
I agree, but with that being the case we need a featu
On 13/06/2008, at 2:05 AM, Brian E. Fox wrote:
Perhaps, but 10 releases into a branch isn't a great place for
innovation
either.
I agree, but with that being the case we need a feature development
location that we are confident enough to release.
Given that, I think we need to move imme
Perhaps, but 10 releases into a branch isn't a great place for innovation
either.
On 6/12/08 10:40 AM, "Ralph Goers" <[EMAIL PROTECTED]> wrote:
> I wouldn't be quiet so harsh. Of course stability is great and should
> always be strived for. But so is innovation.
>
> For me the key is all about
I wouldn't be quiet so harsh. Of course stability is great and should
always be strived for. But so is innovation.
For me the key is all about compatibility. If a feature can be added in
such a way that by default nothing changes, then we should lean towards
putting it in. If it cannot be done
ne 11, 2008 9:47 PM
To: Maven Developers List
Subject: MNG-624 automatic parent versioning
MNG-624 (automatic parent versioning) is far and away the most popular
MNG
issue with 85 votes (the next highest has 57).
In June of last year, Jason evaluated the attached patch and found
problems wi
would it be possible to remove the default relative path... if people want it
they can add it... ../pom.xml just seems very arbitrary
maybe if you want group based parents it makes sense , i have found real power
in using functional parents that define all the plugins for a particular type
of
On 11-Jun-08, at 6:47 PM, Dan Fabulich wrote:
MNG-624 (automatic parent versioning) is far and away the most
popular MNG issue with 85 votes (the next highest has 57).
In June of last year, Jason evaluated the attached patch and found
problems with it, but the problems weren't spec
On 12/06/2008, at 12:45 PM, Dan Fabulich wrote:
Brett Porter wrote:
I haven't reviewed the patch, but the comments by Eric about what
he did sound quite reasonable to me.
Me, too.
- ensure that when deployed to the repository, it is *always* set.
A POM in the repository with a versionle
Brett Porter wrote:
I haven't reviewed the patch, but the comments by Eric about what he did
sound quite reasonable to me.
Me, too.
- ensure that when deployed to the repository, it is *always* set. A POM in
the repository with a versionless-parent would be considered invalid (this is
the m
this case - utilising a property of the
source control structure while not relying on it sounds like a good
idea to me.
Cheers,
Brett
On 12/06/2008, at 11:47 AM, Dan Fabulich wrote:
MNG-624 (automatic parent versioning) is far and away the most
popular MNG issue with 85 votes (the next high
MNG-624 (automatic parent versioning) is far and away the most popular MNG
issue with 85 votes (the next highest has 57).
In June of last year, Jason evaluated the attached patch and found
problems with it, but the problems weren't specified in the bug
description.
Can we r
the parent could be different.
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus.org/browse/MNG-624
> Project: Maven 2
> Type: Improvement
> Components: Inheritence and Interpol
hint for the universal source directory.
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus.org/browse/MNG-624
> Project: Maven 2
> Type: Improvement
> Components: maven-project
leave off all three: , , , since it simply
uses the specified one.
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus.org/browse/MNG-624
> Project: Maven 2
> Type: Improvement
> C
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Fix Version: (was: 2.0-beta-2)
2.1
> automatic parent versioning
> ---
>
> Key: MNG-624
>
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Component: maven-project
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus.org
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
> automatic parent versioning
> ---
>
> Key: MNG-624
>
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Assign To: Brett Porter
Remaining Estimate: 4 hours
Original Estimate: 14400
> automatic parent versioning
> ---
>
>
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Priority: Blocker (was: Critical)
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus
[ http://jira.codehaus.org/browse/MNG-624?page=all ]
Brett Porter updated MNG-624:
-
Priority: Critical (was: Major)
> automatic parent versioning
> ---
>
> Key: MNG-624
> URL: http://jira.codehaus
automatic parent versioning
---
Key: MNG-624
URL: http://jira.codehaus.org/browse/MNG-624
Project: Maven 2
Type: Improvement
Reporter: Brett Porter
Fix For: 2.0-beta-1
(this may be bumped to 2.1 or even made WON't FIX as
25 matches
Mail list logo
