I had in mind to do some backport for Maven 3.0.x, since upgrading is not 
always possible because fo Aether transition to Eclipse.
I prepared a "issues to be reviewed for 3.0.6" version in Jira for this [1] 
(my main driver being MNG-5477  
"malformed POM" warning issued when no version in reporting section)
But it seems nobody was interested and the work was left as is.


I didn't imagine upgrading from 3.2.x to 3.3.x could be difficult: is there 
some 
specific issue?

Regards,

Hervé

[1] https://issues.apache.org/jira/browse/MNG/fixforversion/12330181

Le mardi 13 octobre 2015 22:12:53 Karl Heinz Marbaise a écrit :
> Hi,
> 
> I have created a maven-3.2.6 branch for the back port...and added those
> issues to the Roadmap for 3.2.6 in JIRA as well...
> 
> The question is:
> 
> Is there something which should be part of this bug fix release as
> well...backport some other issues which are ready ?
> 
> 
> Kind regards
> Karl Heinz Marbaise
> 
> On 10/12/15 11:10 PM, Karl Heinz Marbaise wrote:
> > Hi,
> > 
> > i have tried to backport the following issues:
> > 
> > https://issues.apache.org/jira/browse/MNG-5793
> > https://issues.apache.org/jira/browse/MNG-5742
> > 
> > from 3.3.X to a (currently local) 3.2.6-branch which was very easy ..and
> > it works as i expect...
> > 
> > Is there something else i need to pay attention to making a new core
> > release 3.2.6 ?
> > 
> > Kind regards
> > Karl Heinz Marbaise
> > 
> > ---------------------------------------------------------------------
> > 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]

Reply via email to