maven-wagon pull request: Upgrade the dependency on Easymock to 3.2

2013-11-12 Thread ebourg
Github user ebourg closed the pull request at: https://github.com/apache/maven-wagon/pull/7 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.11

2013-11-12 Thread Olivier Lamy
+1 On 12 November 2013 11:36, Benson Margulies wrote: > Hi, > > We solved 7 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=19110&styleName=Text&projectId=11127&Create=Create&atl_token=ACIO-CAVI-QX7G-9IAS%7C963c6bebb9ceae25b98c7c7add910785a302a0b4%7Clin > > (or see below) > >

Re: Do releases _really_ need to be built with Java 1.5?

2013-11-12 Thread Chris Graham
The client in question is using Oracle's CC&B (Customer Care and Billing) their package for power companies. So moving is not a trivial decision, as Oracle have to say if they are prepared to support the specific combination we have. AIX level, WAS version, JDK version etc. The joys of commercial

maven-wagon pull request: Upgrade the dependency on Easymock to 3.2

2013-11-12 Thread ebourg
GitHub user ebourg opened a pull request: https://github.com/apache/maven-wagon/pull/7 Upgrade the dependency on Easymock to 3.2 Hi, Wagon depends on a rather old version of EasyMock. The class `MockControl` used in several tests has been deprecated in EasyMock 2.0 (2005) a

[ANN] Maven Jarsigner 1.1 Released

2013-11-12 Thread Tony Chemit
The Maven team is pleased to announce the release of the Maven JArsigner, version 1.1 This component provides some utilities to sign/verify jars/files in your Mojos. http://maven.apache.org/shared/maven-jarsigner/ To use the Maven Jarsigner, add the following dependency to your project:

[RESULT] [VOTE] Release maven-jarsigner 1.1

2013-11-12 Thread Tony Chemit
On Sat, 9 Nov 2013 09:10:47 +0100 Tony Chemit wrote: Hi, The vote has passed with the following result: +1 (binding): Robert Scholte, Hervé BOUTEMY, Olivier Lamy (always the same :D) +1 (non binding): Me I will promote the artifacts to the central repo. tony. > Hi, > > We solved 5 issues: >

Re: Do releases _really_ need to be built with Java 1.5?

2013-11-12 Thread Lennart Jörelid
Hm.. While WAS 6.1 is still certainly still an IBM-supported version, I can certainly feel your JDK version pain there, Chris. Just out of curiosity - would you claim that the motives for staying on such an old application server version would be motivated more by economy than technology? Or are

Re: Do releases _really_ need to be built with Java 1.5?

2013-11-12 Thread Stephen Connolly
Well it's not like Maven [,3.2) is critically broken... so you'll just have to live with that toolchain... anyways, toolchains support should resolve issues down to 1.5 at least (or older if you can live with older versions of surefire plugin) On 12 November 2013 11:02, Chris Graham wrote: > Um

Re: Do releases _really_ need to be built with Java 1.5?

2013-11-12 Thread Chris Graham
Um, yes, me! :-) Seriously we are still stuck on Java 1.5/WAS 6.1/COBOL for at least another year. Until we move to java 6 (or 7) depending on what oracle will support. -Chris, representing 0.0001% :-) Sent from my iPhone On 12/11/2013, at 4:41 PM, Romain Manni-Bucau wrote: > Isnt the quest

Re: Do releases _really_ need to be built with Java 1.5?

2013-11-12 Thread Stephen Connolly
Well, as long as plugins declare support for Maven [2.0,2.2) strictly speaking we should be building those on Java 1.4 If the plugin declares support for Maven [2.2,3.2) then we need to ensure Java 1.5 support. If a plugin declares that it requires Maven 3.2 then we are only needing to ensure Jav