The vote has passed with the following result:
+1 (binding): Kristian, Hervé, Olivier
0: Anders, Robert
I will continue release process.
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
+1
2013/1/30 Olivier Lamy ol...@apache.org:
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:
+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
and...@hammar.net:
0
It would have been good to get v1.8 of m-invoker-p in
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.
--
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
+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:
On Fri, 1 Feb 2013 17:34:59 +0100
Olivier Lamy ol...@apache.org 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
0
It would have been good to get v1.8 of m-invoker-p in maven-plugins while
we're at it.
/Anders
On Wed, Jan 30, 2013 at 12:40 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Plugins parent 24 and Shared parent 19.
Staging repository:
I see two of these comments:
!-- TODO remove when upgrading parent to 23 --
And we're using maven-parent v23.
/Anders
On Wed, Jan 30, 2013 at 6:38 AM, Kristian Rosenvold
kristian.rosenv...@zenior.no wrote:
+1
Den 30. jan. 2013 kl. 00:41 skrev Olivier Lamy ol...@apache.org:
Hi,
I'd
That's just properties already defined in parent.
Just redundancy sure maybe that could improve performance with
reducing the number of transfered bytes when downloaded the pom :-)
Perso I won't consider this as blocker as we are talking about a pom
release so any sub project can override values.
No problems, I didn't add a negative vote as I didn't look into what they
were doing but merely just mentioning what I saw.
/Anders
On Wed, Jan 30, 2013 at 10:20 AM, Olivier Lamy ol...@apache.org wrote:
That's just properties already defined in parent.
Just redundancy sure maybe that could
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=HEADr2=1371605diff_format=h
* Shared parent
+1
Den 30. jan. 2013 kl. 00:41 skrev Olivier Lamy ol...@apache.org:
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:
13 matches
Mail list logo
