On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.comwrote:
Hi,
Java 6 EOL was in feb and Maven and its plugins are always compatible
Oracle Java 6 was EOL'd.
IBM Java 6 was, and is not due to be for a few more years. They even
*extended* 1.5's life for a year. Sept this
+1 to ensure that we have a good solution (toolchains) to continue to keep
a compatibility with old Java builds.
Like always, upgrading the prerequisite of the core is less annoying than
the one in plugins.
Users can always keep an old core (and many of them will do it as far as
new core versions
Michael's point about omiting the trailing .0 is valid, and introducing it
now does not follow the established convention.
Is it going to be cleaned up?
-Chris
On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.comwrote:
lol
On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY
As long as surefire can fork down to 1.5 and as long as tool chains can
compile with 1.5, the only issue I can see is if the development
environments where these older JVMs are running do not have newer JDKs
available also.
This is the same issue we face in the Jenkins project, were we are
Good point. I updated the survey to tell it is the Oracle JDK EOL
Survey :
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform
Replies :
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics
On Tue, Jul 16, 2013 at 8:06 AM,
I'm not in favor to recreate a maven-3.1 tag to avoid confusions and we
need to keep the maven-3.1.0 which was used in the release
But I agree to improve our release/RCs/Staging process as far as it remains
as automated as possible.
It is already complexe to release stuffs on Apache side and I
For all of those who asked to access to replies (I didn't see they were
protected) I'll find a solution to share these results when the survey will
be really started/published.
On Tue, Jul 16, 2013 at 8:19 AM, Arnaud Héritier aherit...@gmail.comwrote:
Good point. I updated the survey to tell
Hi Arnaud.
You need to at least add an OTHER (ie non oracle) entry as well. You you
can track Oracle java 6 and Non-Oracle java 6.
-Chris
On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier aherit...@gmail.comwrote:
Good point. I updated the survey to tell it is the Oracle JDK EOL
Survey :
My 2c:
- J7 on Mac is unstable (trust me...) and non-performant, and thus I
require my users to use Apple's J6 on the Mac.
- On Linux there are lots of Swing bugs in all versions, but a lot less
in J7 than J6, so I recommend J7 for Linux guys.
- I don't use J5 for anything at all
This is not (or should not be) an entirely technical question - support for
various versions of JDK may be the simpler criterion to discuss, but I feel
the more relevant question is
Do we first and foremost see small-scale projects [small organisations] or
enterprise-scale projects
On Tue, Jul 16, 2013 at 8:14 AM, Chris Graham chrisgw...@gmail.com wrote:
Michael's point about omiting the trailing .0 is valid, and introducing it
now does not follow the established convention.
Is it going to be cleaned up?
I sincerely hope not! That would involve potential for confusion
I've put a question on Stack Overflow:
http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto
see if we can get something that is a bit more focus on facts.
e.g. we are all OSS developers: thus premium/extended/sustaining support
On 16 July 2013 09:44, Fred Cooke fred.co...@gmail.com wrote:
On Tue, Jul 16, 2013 at 8:14 AM, Chris Graham chrisgw...@gmail.com wrote:
Michael's point about omiting the trailing .0 is valid, and introducing it
now does not follow the established convention.
Is it going to be cleaned up?
I
Oracle Java 5 and 6 are EOLed but Oracle continues to support customers using
commercial products that require them that themselves are not EOLed. Given
that current versions of Maven support Java 5 and 6, the real question is how
important is it for older applications that cannot support Java
On Tue, Jul 16, 2013 at 6:26 PM, Lennart Jörelid
lennart.jore...@gmail.comwrote:
This is not (or should not be) an entirely technical question - support for
various versions of JDK may be the simpler criterion to discuss, but I feel
the more relevant question is
Do we first and foremost see
Speaking as a Maven Developer...
My primary development machine is OS-X.
On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25
I have a personal linode running 1.6.0_22, and my famous Acer Aspire One
that has some Java 1.5 and 1.6 versions on it... but I have not turned it
Recent MacOS also thus only Java 1.6 and 1.7.
Maybe I could setup a VM with a Java 1.5 but to be honest I already have
not enough time to contribute thus working on Maven inside a VM will never
occur.
On Tue, Jul 16, 2013 at 1:35 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
perso osx. So only = 1.6
2013/7/16 Stephen Connolly stephen.alan.conno...@gmail.com:
Speaking as a Maven Developer...
My primary development machine is OS-X.
On that machine I have 1.6.0_24-b07-334, 1.7.0_17, 1.7.0_21, and 1.7.0_25
I have a personal linode running 1.6.0_22, and my famous
I rum mainly on OSX for client and some Linuxes for server - so client side is
= JDK 1.6
// vänlig hälsning,
// [sw: best regards],
//
// Lennart Jörelid
16 jul 2013 kl. 13:53 skrev Olivier Lamy ol...@apache.org:
perso osx. So only = 1.6
2013/7/16 Stephen Connolly
Me:
Linux, Windows, AIX (and if I have too, OS/2!) 1.4, 5, 6 and if I need it,
I can get 7.
On Tue, Jul 16, 2013 at 10:13 PM, Lennart Jörelid lennart.jore...@gmail.com
wrote:
I rum mainly on OSX for client and some Linuxes for server - so client
side is = JDK 1.6
// vänlig hälsning,
//
Folks
In the states..government sector (specifically State Agencies) lag at least 5
years behind available current releases
the specific example I provide is the app I was working on was based on JVM 1.5
the Portal was based on JVM 1.4
the end result was:
Annotations: NOPE
Generics: NOPE
Hi.
Would anybody care to release the enforcer 1.3.1 plugin so we can go around
http://jira.codehaus.org/browse/MENFORCER-156?
All issues for 1.3.1 are fixed:
http://jira.codehaus.org/browse/MENFORCER/fixforversion/19426#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
Nice idea to have this survey to have some feedback from users.
Do you think it may be possible to make this kind of survey to get feedback for
maven web site (not plugin) or other area of maven ?
Eric
Joke: perso win user so using jdk8 or jdk7 according to the os version
Real: jdk 7 on server
Hi,
The release vote is already in progress.
Cheers,
On Tue, Jul 16, 2013 at 10:17 AM, David Karlsen davidkarl...@gmail.comwrote:
Hi.
Would anybody care to release the enforcer 1.3.1 plugin so we can go around
http://jira.codehaus.org/browse/MENFORCER-156?
All issues for 1.3.1 are
*BUT* such agencies also find it too expensive to upgrade Maven to 3.2 so
we don't actually have to worry about them ;-)
If you are a refusenick on JVM you are likely also a refusenik on Maven ;-)
On 16 July 2013 13:45, Martin Gainty mgai...@hotmail.com wrote:
Folks
In the
The last project I was on was migrating WAS/WPS/Portal V6 (JDK 1.4) -
WAS/BPM/Portal V8 (JDK 1.6).
Why?
Because the support costs for EOL software finally made it cost effective
to upgrade! :-)
And even then, it was meant to be a lift and shift as in just keep the
functionality the same as much
I tucked away the last public debs of 1.5 and can release 1.5
indefinitely. In the release of the last security patch, it seems like
Oracle have released approx 10 nonpublic jdk 5 versions. Shame we can't
have it.
Kristian
Den 16. juli 2013 14:14 skrev Lennart Jörelid lennart.jore...@gmail.com
FYI, in the next version of logback, i.e. 2.0, we will be using JDK 1.6.
However, the logback 1.1.x series will continue to be based on JDK 1.5.
On 16.07.2013 07:06, Stephen Connolly wrote:
So what I am hearing is that until we bump core to require JDK6 (or 7) then
logback is the only runner
Can you tell me if now you can see the result :
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics
On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold
kristian.rosenv...@zenior.no wrote:
I tucked away the last public debs of 1.5 and can release 1.5
Yep.
Sent from my iPhone
On 16 Jul 2013, at 20:24, Arnaud Héritier aherit...@gmail.com wrote:
Can you tell me if now you can see the result :
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics
On Tue, Jul 16, 2013 at 3:37 PM, Kristian Rosenvold
Just to clarify my comments:
I can't and won't build anything with anything higher than J6 for the
foreseeable future, maybe upto 2 years or so, who knows.
J7 is purely a runtime option for users for me, same for J8. J5 is dead for
both builds and runtime in my eyes. I'd prefer to maximise my
Isn't the convention way to omit the last zero? This has been done for
Maven and all plugins/components before.
No, we have 2.1.0 and 2.2.0 for the Maven core distro. Plugins would/could
be a different story though.
/Anders
Mike
For now what is resulting from this thread is :
* We do a survey to better know where our user are and were they are going
* We check what is the status of our tools (toolchains co) to be sure how
we can easily use versions of java older than the one required by maven
* We discuss on the ML to
+1
Regards,
Hervé
Le vendredi 12 juillet 2013 23:12:02 Robert Scholte a écrit :
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=H
tmlversion=19426
There are still a couple of issues left in JIRA:
What I do not really understand:
- Say I am a company which are forced to run JDK1.5 because they have
to recertificate everything due to Sarbains-Oxley or German GOBS.
- Would I not force my developers to use the same tools to build they
used for previous versions, then?
- Maven 3 behaves
Look you chickens; until quite recently I kept a 1.3 JVM running on windows to
do the occasional
test of surefire on jdk 1.3. (I kept a vmware image since installing 1.3 on
linux required surrendering your first born to Sauron) All your complaining
about not being able to run 1.5 sounds like
16. juli 2013 kl. 07:35 skrev Stephen Connolly
stephen.alan.conno...@gmail.com:
- have we good test coverage with toolchains?
No.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
Hi,
Do we consider the 3.1.0 as the latest stable ?
On the download page there is a typo (?)
http://maven.apache.org/download.cgi
Maven 3.1.0 :This is the future of Maven (alpha status).
On the homepage we always have the Get Maven 3.0.5 on the right
http://maven.apache.org/index.html
Typo on my part. There are 48 things to change when updating a release.
I updated and triggered the publish an hour ago. I'm not sure when/how it
updates.
On Jul 16, 2013, at 5:34 PM, Arnaud Héritier aherit...@gmail.com wrote:
Hi,
Do we consider the 3.1.0 as the latest stable ?
On
On Tue, Jul 16, 2013 at 11:37 PM, Jason van Zyl ja...@tesla.io wrote:
Typo on my part. There are 48 things to change when updating a release.
Ok. I wasn't sure if it was intentional
I agree, that's a pain to do a release :(
I updated and triggered the publish an hour ago. I'm not sure
On Fri, 12 Jul 2013 23:12:02 +0200
Robert Scholte rfscho...@apache.org wrote:
+1,
works fine to me,
thanks,
tony.
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=Htmlversion=19426
There are still a couple of issues left in JIRA:
On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote:
Typo on my part. There are 48 things to change when updating a release.
I updated and triggered the publish an hour ago. I'm not sure when/how it
updates.
Should be immediate (within a few seconds), assuming svnpubsub is
running
On 16 July 2013 21:52, Kristian Rosenvold kristian.rosenv...@zenior.nowrote:
Look you chickens; until quite recently I kept a 1.3 JVM running on
windows to do the occasional
test of surefire on jdk 1.3. (I kept a vmware image since installing 1.3
on linux required surrendering your first
Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
personal view) Maven job type will be unable to run 1.5
The crappy one which doesn't work with Maven 3.1.0 too (I tested it this
afternoon)
Can still keep trucking with a FreeStyle + Maven Build Step though (and I
On 16 July 2013 23:01, Arnaud Héritier aherit...@gmail.com wrote:
Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
personal view) Maven job type will be unable to run 1.5
The crappy one which doesn't work with Maven 3.1.0 too (I tested it this
afternoon)
On 17 July 2013 07:31, Arnaud Héritier aherit...@gmail.com wrote:
Can still keep trucking with a FreeStyle + Maven Build Step though (and I
prefer that way anyway)
asJenkinsUser
Me too if we backport features from the crappy maven integration into the
freestyle job (automatic dependencies,
On 16 July 2013 23:25, Barrie Treloar baerr...@gmail.com wrote:
On 17 July 2013 07:31, Arnaud Héritier aherit...@gmail.com wrote:
Can still keep trucking with a FreeStyle + Maven Build Step though (and
I
prefer that way anyway)
asJenkinsUser
Me too if we backport features from the
On Jul 16, 2013, at 5:42 PM, sebb seb...@gmail.com wrote:
On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote:
Typo on my part. There are 48 things to change when updating a release.
I updated and triggered the publish an hour ago. I'm not sure when/how it
updates.
Should be
We generally follow the practice of building on the target platform using
the tools of the target platform. EG on AIX using the same version of the
JDK that WAS runs on (typically using Jenkins).
That does not meant that I do not want to make use of the newer versions of
maven, it's plugins and
2013/7/17 Stephen Connolly stephen.alan.conno...@gmail.com:
On 16 July 2013 23:01, Arnaud Héritier aherit...@gmail.com wrote:
Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
personal view) Maven job type will be unable to run 1.5
The crappy one which doesn't
+1
2013/7/13 Robert Scholte rfscho...@apache.org:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530styleName=Htmlversion=19426
There are still a couple of issues left in JIRA:
On 16 July 2013 23:45, Jason van Zyl ja...@tesla.io wrote:
On Jul 16, 2013, at 5:42 PM, sebb seb...@gmail.com wrote:
On 16 July 2013 22:37, Jason van Zyl ja...@tesla.io wrote:
Typo on my part. There are 48 things to change when updating a release.
I updated and triggered the publish an hour
52 matches
Mail list logo
