om my iPhone
>>
>>> On 22 Feb 2014, at 20:03, Jason van Zyl wrote:
>>>
>>> Didn't we decide that everything can be 1.6? I remember because it was one
>>> of Stephen's overly long emails :-)
>>>
>>> jvz
>&g
n Zyl wrote:
> >>
> >> Didn't we decide that everything can be 1.6? I remember because it was
> one of Stephen's overly long emails :-)
> >>
> >> jvz
> >>
> >
>> On Feb 22, 2014, at 11:02 AM, Benson Margulies
>>> wrote:
>>>
>>> How much longer with this Java 1.5 business? It' a giant pain.
>>>
>>> -
m... but we are now OT
>
>
> 2014-02-22 21:26 GMT+01:00 Stephen Connolly <
> stephen.alan.conno...@gmail.com
> >:
>
> > If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with
> > Java 1.5
> >
> > Hence my version policy that you lot are all ignoring
+1 to dump Java 5.
Gary
Original message
From: Baptiste Mathus
Date:02/22/2014 17:00 (GMT-05:00)
To: Maven Developers List
Subject: Re: Java 1.5
+1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become
old. We're already using Java 1.7 at our
ugin could from now on be released with 1.6+
requirement, you would just have to make sure to bump the MAJOR (or only
minor?) version number to acknowledge the change" ?
2014-02-22 21:26 GMT+01:00 Stephen Connolly :
> If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with
>
If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5
Hence my version policy that you lot are all ignoring commenting on... No
comments means I'll just put it up for a vote ;-)
Sent from my iPhone
> On 22 Feb 2014, at 20:10, "Arnaud Héritier" wr
Stephen's overly long emails :-)
>
> jvz
>
>> On Feb 22, 2014, at 11:02 AM, Benson Margulies wrote:
>>
>> How much longer with this Java 1.5 business? It' a giant pain.
>>
>> -
e decide that everything can be 1.6? I remember because it was one of
> Stephen's overly long emails :-)
> jvz
>> On Feb 22, 2014, at 11:02 AM, Benson Margulies wrote:
>>
>> How much longer wit
Didn't we decide that everything can be 1.6? I remember because it was one of
Stephen's overly long emails :-)
jvz
> On Feb 22, 2014, at 11:02 AM, Benson Margulies wrote:
>
> How much longer with this Java 1.5 busines
to use it in all Maven releases, which
> adds a layer of VM complexity to my process.
> On Sat, Feb 22, 2014 at 2:31 PM, Dennis Lundberg wrote:
>> Which business are you referring to?
>>
>> On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies
>> wrote:
>>> How m
t; How much longer with this Java 1.5 business? It' a giant pain.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@m
Which business are you referring to?
On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies wrote:
> How much longer with this Java 1.5 business? It' a giant pain.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...
How much longer with this Java 1.5 business? It' a giant pain.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
2013/11/12 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.00
/productive features versus staying on an elder
version for compatibility reasons. Personally, I wouldn't claim Maven to be
overly progressive in its minimum JDK requirements...
2013/11/12 Chris Graham
> Um, yes, me! :-)
>
> Seriously we are still stuck on Java 1.5/WAS 6.1/COBO
ham wrote:
> 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
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
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
> I don't know where I'm going to get that environment.
Everything is still accessible in Oracle Java Archive:
http://www.oracle.com/technetwork/java/archive-139210.html
Dawid
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apac
Isnt the question: is there still someone needing j5? Almost all apache
projects and others moved to j6 at least
Le 11 nov. 2013 23:53, "John Patrick" a écrit :
> i guess it's the only way to definitely ensure backwards compatibility
>
> open potential solution would be to use vagrant, I use it t
i guess it's the only way to definitely ensure backwards compatibility
open potential solution would be to use vagrant, I use it to ensure
developers as using the same base build setup and the files can be source
controlled
On 11 November 2013 22:39, Benson Margulies wrote:
>
> http://maven.a
http://maven.apache.org/developers/release/maven-project-release-procedure.html
says so. I don't know where I'm going to get that environment.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-
Pushing to master-git and pushing releases. All the license headers and
GAV's are still codehaus.
Kristian
to., 09.06.2011 kl. 15.15 -0400, skrev John Casey:
> Yeah, I thought that's what we were talking about...so, if you clone the
> git repo, the "commit bit" you're talking about is for pul
Yeah, I thought that's what we were talking about...so, if you clone the
git repo, the "commit bit" you're talking about is for pulling those
changes back to the sonatype clone, right?
Not to be a pain, but who's saying sonatype's the ultimate authority on
plexus?
On 6/9/11 2:57 PM, Arnaud H
On Thu, Jun 9, 2011 at 6:32 PM, John Casey wrote:
>
>
> On 6/9/11 6:09 AM, Kristian Rosenvold wrote:
>
>> It was like
>> that at codehaus, and it still works that way.
>>
>
> Sorry to display my ignorance, but I haven't done much with the plexus-*
> code in awhile...
>
> Other than the container,
chains based invoking of older java
> versions is not affected, with moving our runtime requirement up to
> java 1.5
+1
>
> -Stephen
>
> On 9 June 2011 10:30, Kristian Rosenvold
> wrote:
>> I'd like to gradually start migrating some of these to java 1.5. Doing
>
On 6/9/11 6:09 AM, Kristian Rosenvold wrote:
It was like
that at codehaus, and it still works that way.
Sorry to display my ignorance, but I haven't done much with the plexus-*
code in awhile...
Other than the container, where is the plexus-compiler stuff now, if not
codehaus? Are we talk
Totally agree, onward and upward!
On 6/9/11 5:30 AM, Kristian Rosenvold wrote:
I'd like to gradually start migrating some of these to java 1.5. Doing
so will effectively prevent any java 1.4 clients from upgrading.
It's my opinion that this move will effectively be the end of ja
moving our runtime requirement up to
> java 1.5
>
> -Stephen
>
> On 9 June 2011 10:30, Kristian Rosenvold wrote:
> > I'd like to gradually start migrating some of these to java 1.5. Doing
> > so will effectively prevent any java 1.4 clients from upgrading.
> >
> Actually I'd go further one step: plexus has been developed to 90% by ASF
> committers. So I'd rather go and move plexus over to maven completely while
> upgrading to java 1.5 and rewrite/drop parts with uncertain provenience.
I don't really see the point of all this
+1 for dropping java 1.4 support.
> Since these projects are technically not ASF ...
Actually I'd go further one step: plexus has been developed to 90% by ASF
committers. So I'd rather go and move plexus over to maven completely while
upgrading to java 1.5 and rewrite/dr
, with moving our runtime requirement up to
java 1.5
-Stephen
On 9 June 2011 10:30, Kristian Rosenvold wrote:
> I'd like to gradually start migrating some of these to java 1.5. Doing
> so will effectively prevent any java 1.4 clients from upgrading.
>
> It's my opini
no objections.
Onward !
2011/6/9 Kristian Rosenvold :
> I'd like to gradually start migrating some of these to java 1.5. Doing
> so will effectively prevent any java 1.4 clients from upgrading.
>
> It's my opinion that this move will effectively be the end of java all
> 1
I'd like to gradually start migrating some of these to java 1.5. Doing
so will effectively prevent any java 1.4 clients from upgrading.
It's my opinion that this move will effectively be the end of java all
1.4 support. (The surefire fork is the only "declared" java 1.3/1.4 (
I think I recall now that it was holding off for the ever-expectant "1.0" to
manage compatibility expectations - but I don't think 2.0.11 can still
correctly upgrade wagons anyway.
IMO, just do it. :)
On 24/05/2011, at 3:16 AM, Stephen Connolly wrote:
> if the fix targets 2.2.x+ then that's al
if the fix targets 2.2.x+ then that's all 1.5+
if the fix targets 2.0.x+ then that has to remain 1.4+
Our officially supported version is 3.0.3 and 2.2.1, with 2.0.x being
an also ran.
If you take care to create the branch prior to the switch then AFAIK
it's all Nike (Just Do It(tm))
On 23 May 2
#x27;importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Mon, 23 May 2011 17:59:18 +0100
> From: strub...@yahoo.de
> Subject: upgrading
Hi folks!
Is there any reason why we still stick with jdk-1.4 in lots of our sub projects?
Even java5 is already dead, dead, dead.. [1]
I would like to upgrade wagon to java5 at least to be able to run with
junit-4.8.2 which is required for our wagon TCK (which is relying on
annotations and in
+1
Emmanuel
On Tue, Dec 28, 2010 at 9:15 PM, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding this . (jira entry
> http://jira.codehaus.org/browse/SCM-591)
>
> Thanks,
>
I don't see any objections in this thread.
So I will do the necessary code change (probably next year).
--
Olivier
2010/12/28 Olivier Lamy :
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding this .
+1 since we moved that way for 2.2 and 3, I think we can safely move all of our
cosebases to 1.6 as needed
--Brian (mobile)
On Dec 28, 2010, at 3:15 PM, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any tro
+1
On 2010-12-28 21:15, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding this . (jira entry
> http://jira.codehaus.org/browse/SCM-591)
>
> Thanks
+1
On Tue, Dec 28, 2010 at 10:19 PM, Stephane Nicoll wrote:
> +1
>
> S.
>
> On Tue, Dec 28, 2010 at 9:15 PM, Olivier Lamy wrote:
>
> > Hi,
> > As we will start a new year, I'd like to move scm to java 1.5.
> > Let me know if you have any trou
+1
S.
On Tue, Dec 28, 2010 at 9:15 PM, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding this . (jira entry
> http://jira.codehaus.org/browse/SCM-591)
>
> Thanks,
> --
> Oliv
+1
On Dec 28, 2010, at 3:15 PM, Olivier Lamy wrote:
> Hi,
> As we will start a new year, I'd like to move scm to java 1.5.
> Let me know if you have any trouble regarding this . (jira entry
> http://jira.codehaus.org/browse/SCM-591)
>
> Thanks,
> --
> Olivier La
+1
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 28 Dec 2010 20:16, "Olivier Lamy" wrote:
> Hi,
> As we will start a new year, I'd like to move scm
+1
2010/12/28 Arnaud Héritier
> +1
>
> Arnaud
>
> On Tue, Dec 28, 2010 at 9:29 PM, Kristian Rosenvold
> wrote:
> > +1
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional command
+1
Arnaud
On Tue, Dec 28, 2010 at 9:29 PM, Kristian Rosenvold
wrote:
> +1
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
-
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Olivier Lamy wrote:
As we will start a new year, I'd like to move scm to java 1.5.
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
As we will start a new year, I'd like to move scm to java 1.5.
Let me know if you have any trouble regarding this . (jira entry
http://jira.codehaus.org/browse/SCM-591)
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/
t; can we add a
>
>
>org.apache.maven.plugins
>maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
> to the pom of maven-eclipse-plugin (2.6-SNAPSHOT: trunk).
>
> Currently im fixing the bug http://jira.codehaus.org/
use java 1.5 features (generics etc.). Is this possible or not
(for backward compatibility)?
regards
höhmi
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
oader used by SAX simply
doesn't know about any classes loaded by the maven classloader.
*expletive deleted*
Is it possible to create a plugin which uses Xalan 2.8.1 despite the fact
that maven has its own Xalan in lib/endorsed and with Java 1.5?
Regards,
--
Aaron Digulla
[EMAIL PROTEC
Hello,
I'm trying to port StatCVS to maven2 and had some success ... well, if I
invoke
StatCVS as a subprocess.
But I want to invoke StatCVS directly, too. Now, I'm stuck while invoking
StatCVS
from Java. When I try, I get this error:
saxFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
java
Java 1.5 specific code
--
Key: DOXIA-41
URL: http://jira.codehaus.org/browse/DOXIA-41
Project: doxia
Type: Bug
Reporter: mike perham
[ERROR] BUILD FAILURE
[INFO
[ http://jira.codehaus.org/browse/MNG-685?page=all ]
Brett Porter closed MNG-685:
Resolution: Fixed
Fix Version: (was: 2.0-beta-2)
2.0-beta-1
> FAQ about compiling with Java 1.5 are incompl
[ http://jira.codehaus.org/browse/MNG-685?page=comments#action_46541 ]
Ken Weiner commented on MNG-685:
Great. Thanks. This issue can be closed now.
> FAQ about compiling with Java 1.5 are incompl
.
> FAQ about compiling with Java 1.5 are incomplete.
> -
>
> Key: MNG-685
> URL: http://jira.codehaus.org/browse/MNG-685
> Project: Maven 2
> Type: Bug
> Components: documentation
>
[ http://jira.codehaus.org/browse/MNG-685?page=all ]
Brett Porter updated MNG-685:
-
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
> FAQ about compiling with Java 1.5 are incompl
[ http://jira.codehaus.org/browse/MNG-685?page=all ]
Trygve Laugstol updated MNG-685:
Complexity: Novice
> FAQ about compiling with Java 1.5 are incomplete.
> -
>
> Key: MNG-685
&g
[ http://jira.codehaus.org/browse/MNG-685?page=all ]
Brett Porter updated MNG-685:
-
Fix Version: 2.0-beta-1
> FAQ about compiling with Java 1.5 are incomplete.
> -
>
> Key: MNG-685
&g
FAQ about compiling with Java 1.5 are incomplete.
-
Key: MNG-685
URL: http://jira.codehaus.org/browse/MNG-685
Project: Maven 2
Type: Bug
Components: documentation
Versions: 2.0-alpha-3
Reporter: Ken Weiner
64 matches
Mail list logo
