+1
--
Olivier
On Mar 23, 2014 8:52 AM, "Karl Heinz Marbaise" wrote:
> Hi,
>
> based on the decision we have made on the 18. february 2014 to define End
> Of Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
>
> I would suggest to retire the Maven Reactor Plugin.
> The last release has b
+1
Regards,
Hervé
Le samedi 22 mars 2014 22:52:22 Karl Heinz Marbaise a écrit :
> Hi,
>
> based on the decision we have made on the 18. february 2014 to define
> End Of Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
>
> I would suggest to retire the Maven Reactor Plugin.
> The last
+1
I've had it with the maven-foo-plugin.
:-)
On Mar 22, 2014, at 2:52 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> based on the decision we have made on the 18. february 2014 to define End Of
> Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
>
> I would suggest to retire the Maven
Hi,
based on the decision we have made on the 18. february 2014 to define
End Of Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
I would suggest to retire the Maven Reactor Plugin.
The last release has been made on 23rd of september 2008 version 1.0.
Apart from that the complete fu
Hi,
There is a section on the plugins page for retired plugins.
If you want to retire a plugin here's a page with some instructions on
how to do it:
https://maven.apache.org/developers/retirement-plan-plugins.html
On Sat, Mar 22, 2014 at 4:51 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> I have rem
Op Sat, 22 Mar 2014 17:12:49 +0100 schreef Hervé BOUTEMY
:
well done
notice we should do something on profile activation, because ${basedir}
is
supported here but not ${project.basedir}
see MNG-5590
IMHO, we should add support for ${project.basedir} in file-based profile
activation, and p
Hi Hervé,
>>
Outch...missed that...will that bite the site generation in any way ? I
hope not otherwise it's simple to undone the change...
if I read your site modifications correctly, you didn't change any case where
${basedir} was used in file-based profile activation: so don't worry, you did
Le samedi 22 mars 2014 17:30:27 Karl Heinz Marbaise a écrit :
> Hi Hervé,
>
> > notice we should do something on profile activation, because ${basedir} is
> > supported here but not ${project.basedir}
> > see MNG-5590
>
> Outch...missed that...will that bite the site generation in any way ? I
> h
Hi Hervé,
>
notice we should do something on profile activation, because ${basedir} is
supported here but not ${project.basedir}
see MNG-5590
Outch...missed that...will that bite the site generation in any way ? I
hope not otherwise it's simple to undone the change...
IMHO, we should add
Hi Hervé,
> +1
great idea
for the moment, there was nothing to put in "Maven 2.x specific documentation",
but now you've found m-reactor-p, this is the right place
So i will create
http://maven.apache.org/archives/maven-2.x/
area and move such things to it...
Thanks.
Kind regards.
Karl-Heinz
well done
notice we should do something on profile activation, because ${basedir} is
supported here but not ${project.basedir}
see MNG-5590
IMHO, we should add support for ${project.basedir} in file-based profile
activation, and properly document this precise case in deprecation
documentation
Hi,
Maven-2.x has reached EOL, which I would translate as "we've stopped
developing on the 2.x branch of Maven Core".
But IMHO that doesn't mean that we immediately must drop M2 support for
all Maven-plugins. I think that's a different discussion.
Robert
Op Thu, 20 Mar 2014 09:59:36 +0100
+1
great idea
for the moment, there was nothing to put in "Maven 2.x specific documentation",
but now you've found m-reactor-p, this is the right place
Regards,
Hervé
Le samedi 22 mars 2014 16:51:35 Karl Heinz Marbaise a écrit :
> Hi,
>
> I have removed the maven-reactor-plugin from the list o
Hi,
I have removed the maven-reactor-plugin from the list of the plugins,
cause it's only Maven 2 related
So the question is: Should we create a graveyard for such informations
with links on them ?
I have seen we have such kind of
http://maven.apache.org/maven-2.x-eol.html (documented
Hi Hervé,
Sebb's instructions were quite explicit: I suppose he knows what he requested
notice we have the problem not only on our site examples, but on the ASF
parent POM itself!
I just opened https://issues.apache.org/jira/browse/MPOM-48 and made the fix
but ASF parent POM was just released
another idea: improve the plugin archetype
http://maven.apache.org/archetype/maven-archetype-bundles/maven-archetype-plugin/
I don't know which approach is better, just an idea
Regards,
Hervé
Le samedi 22 mars 2014 12:30:42 Karl Heinz Marbaise a écrit :
> Hi,
>
> during my reread of the web si
Sebb's instructions were quite explicit: I suppose he knows what he requested
notice we have the problem not only on our site examples, but on the ASF
parent POM itself!
I just opened https://issues.apache.org/jira/browse/MPOM-48 and made the fix
but ASF parent POM was just released a few days a
Hi Simone,
I've added the projectVersionPolicyId to the releaseDescriptor. We might
need to add dependencyVersionPolicyId, parentVersionPolicyId and
pluginVersionPolicyId in the future as well.
So the manager is ready to switch from implementation, which should be
enough for unittesting.
W
Hi,
during my reread of the web sites i found out that there a given
examples about maven plugin developement...(Apart from being a little
bit out-of-date)...
I would suggest to create a full working example in the subversion
sandbox in the following location (with a link on the web-site):
Hi,
i have fixed the issue http://jira.codehaus.org/browse/MNGSITE-191
and changed the information accordingly see in changeset
http://svn.apache.org/r1580196 cause the license is really called
http://apache.org/licenses/ "Apache License, Version 2.0" and not
"The Apache Software License, Versi
20 matches
Mail list logo
