On Fri, 1 Feb 2013 17:34:59 +0100
Olivier Lamy wrote:
+1
Keep fighting ;)
thanks,
tony.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
Regards,
Hervé
Le mercredi 30 janvier 2013 00:40:43 Olivier Lamy a écrit :
> Hi,
> I'd like to release Plugins parent 24 and Shared parent 19.
> Staging repository:
> https://repository.apache.org/content/repositories/maven-172/
>
> Diffs:
>
> * Plugins parent 24:
> http://svn.apache.org/vi
Sure I know. But if plugins upgrade to this new parent and were depending
on extra groovy-utils, they will first face breaking integration tests.
Next they have to know they need to use either m-invoker-p 1.6 or 1.8. And
with the parent 25 they have to remove it again since it should inherit
Nothing prevent you to use this version with overriding that in a pom
if you really need it.
We are talking here only about a pom ! which doesn't have any impact
neither real value for end users.
Perso if I prefer to concentrate my energy and use my time for end
users rather than for a pom.
--
Oli
+0
I have to agree with Anders: m-invoker-p 1.7 is missing groovy´s
XmlSlurper and 1.8 is really powerful compared to its previous versions
Robert
Op Thu, 31 Jan 2013 16:54:36 +0100 schreef Anders Hammar
:
0
It would have been good to get v1.8 of m-invoker-p in maven-plugins while
we'r
+1
2013/1/30 Olivier Lamy :
> Hi,
> I'd like to release Plugins parent 24 and Shared parent 19.
> Staging repository:
> https://repository.apache.org/content/repositories/maven-172/
>
> Diffs:
>
> * Plugins parent 24:
> http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-24/pom.xml?r1=HE
+1 on Arnaud's comments.
The main problem with this "feature" is that it is not documented thus I
can't explain the real reason why Maven download several times released
artifacts and this causes members of the Maven bashing group to grow
Jeff
On Fri, Feb 1, 2013 at 9:47 AM, Arnaud Héritier wro
My position was to propose the low cost possible solution to have a quick
fix and not to wait for months.
If it could be fixed/configurable in aether it may be the solution to
follow but I'm not sure about the status of this 3rd party project (eclipse
migration ...) on which we don't have the hand.
Andreas Gudian wrote:
> Am Freitag, 1. Februar 2013 schrieb Jason van Zyl :
>
>>
>> On Jan 31, 2013, at 7:13 PM, Arnaud Héritier
>> > wrote:
>>
>> > Hi Olivier,
>> >
>> > Thx a lot for the fix. It will help a lot the community.
>> > But from my point of view it's perhaps not yet enough.
>> >
