You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2013/11/11 23:39:59 UTC
Do releases _really_ need to be built with Java 1.5?
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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Stephen Connolly <st...@gmail.com>.
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 Java 1.6...
Speaking of 3.2... Jason, any sign on when we will cut that baby and move
ourselves to 1.6!
On 11 November 2013 22:39, Benson Margulies <bi...@gmail.com> wrote:
>
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Dawid Weiss <da...@gmail.com>.
> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Chris Graham <ch...@gmail.com>.
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 contracts...
There are plans to move to CC&B 2.4 on top of WAS 8.5 (8.5.5), but that
will be sometime in the next 24 odd months.
So the main issue is funding to support the migration development issue.
Not a decision NOT to migrate as it where. :-)
-Chris
On Tue, Nov 12, 2013 at 10:26 PM, Lennart Jörelid <lennart.jorelid@gmail.com
> wrote:
> 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 there technological reasons why your organisation
> (and, therefore, likely others in the 0.0001% league) cannot move to a
> newer version of the application server supporting a newer JDK standard?
>
> There is always the delicate balance between upgrading minimum (JDK/lib)
> requirements to enable nice/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 <ch...@gmail.com>
>
> > 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 <rm...@gmail.com>
> > wrote:
> >
> > > 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" <nh...@gmail.com> 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 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 <bi...@gmail.com>
> > wrote:
> > >>
> > >>>
> > >>>
> > >>
> >
> 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-unsubscribe@maven.apache.org
> > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>
> > >>>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
>
> --
> +==============================+
> | Bästa hälsningar,
> | [sw. "Best regards"]
> |
> | Lennart Jörelid
> | EAI Architect & Integrator
> |
> | jGuru Europe AB
> | Mölnlycke - Kista
> |
> | Email: lj@jguru.se
> | URL: www.jguru.se
> | Phone
> | (skype): jgurueurope
> | (intl): +46 708 507 603
> | (domestic): 0708 - 507 603
> +==============================+
>
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Lennart Jörelid <le...@gmail.com>.
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 there technological reasons why your organisation
(and, therefore, likely others in the 0.0001% league) cannot move to a
newer version of the application server supporting a newer JDK standard?
There is always the delicate balance between upgrading minimum (JDK/lib)
requirements to enable nice/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 <ch...@gmail.com>
> 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 <rm...@gmail.com>
> wrote:
>
> > 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" <nh...@gmail.com> 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 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 <bi...@gmail.com>
> wrote:
> >>
> >>>
> >>>
> >>
> 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-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL: www.jguru.se
| Phone
| (skype): jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Stephen Connolly <st...@gmail.com>.
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 <ch...@gmail.com> 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/2013, at 4:41 PM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > 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" <nh...@gmail.com> 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 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 <bi...@gmail.com>
> wrote:
> >>
> >>>
> >>>
> >>
> 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-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Chris Graham <ch...@gmail.com>.
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 <rm...@gmail.com> wrote:
> 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" <nh...@gmail.com> 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 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 <bi...@gmail.com> wrote:
>>
>>>
>>>
>> 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-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Do releases _really_ need to be built with Java 1.5?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <nh...@gmail.com> 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 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 <bi...@gmail.com> wrote:
>
> >
> >
> 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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: Do releases _really_ need to be built with Java 1.5?
Posted by John Patrick <nh...@gmail.com>.
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 <bi...@gmail.com> wrote:
>
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>