Re: [exec] Update from Java 5 to 6
I am ok with Java 8 as the requirement. Gary On Sun, Jul 12, 2020, 06:16 T. Schapitz wrote: > Hi there, > > maybe a bit late in the game, because the original post regarding this > topic was 9 months ago, but i think there is a good case for skipping > directly to JDK 8: > > If we opt for utilizing not only the java.lang.ProcessBuilder introduced > in JDK 1.5, but also the additional methods for stream inheritance and > stream redirection(*) introduced in 6 & 7, this will likely be done by > introducing additional methods into the API interfaces, whether it is > the CommandLauncher or the Executor. But this could potentially break > backward compatibility for users of common-exec, that implemented those > interfaces. (Granted, it's rather unlikely somebody did this - most > would rather be extending DefaultExecutor). But problems like this could > easily avoided by adding default implementations introduced with JDK 8. > > Btw: who would be reviewing a pull request, if I had one? Is currently > somebody reviewing working on the issues? > > (I'm just trying to get a feel for the project, and want to avoid > duplication) > > Thomas > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
for 1.5 to 1.6: Seems only 1.6 users can benefit from that...does it worth? for 1.5 to 1.8: GREAATE! +1 for it. T. Schapitz 于2020年7月12日周日 下午6:16写道： > Hi there, > > maybe a bit late in the game, because the original post regarding this > topic was 9 months ago, but i think there is a good case for skipping > directly to JDK 8: > > If we opt for utilizing not only the java.lang.ProcessBuilder introduced > in JDK 1.5, but also the additional methods for stream inheritance and > stream redirection(*) introduced in 6 & 7, this will likely be done by > introducing additional methods into the API interfaces, whether it is > the CommandLauncher or the Executor. But this could potentially break > backward compatibility for users of common-exec, that implemented those > interfaces. (Granted, it's rather unlikely somebody did this - most > would rather be extending DefaultExecutor). But problems like this could > easily avoided by adding default implementations introduced with JDK 8. > > Btw: who would be reviewing a pull request, if I had one? Is currently > somebody reviewing working on the issues? > > (I'm just trying to get a feel for the project, and want to avoid > duplication) > > Thomas > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org
[exec] Update from Java 5 to 6
Hi there, maybe a bit late in the game, because the original post regarding this topic was 9 months ago, but i think there is a good case for skipping directly to JDK 8: If we opt for utilizing not only the java.lang.ProcessBuilder introduced in JDK 1.5, but also the additional methods for stream inheritance and stream redirection(*) introduced in 6 & 7, this will likely be done by introducing additional methods into the API interfaces, whether it is the CommandLauncher or the Executor. But this could potentially break backward compatibility for users of common-exec, that implemented those interfaces. (Granted, it's rather unlikely somebody did this - most would rather be extending DefaultExecutor). But problems like this could easily avoided by adding default implementations introduced with JDK 8. Btw: who would be reviewing a pull request, if I had one? Is currently somebody reviewing working on the issues? (I'm just trying to get a feel for the project, and want to avoid duplication) Thomas pEpkey.asc Description: application/pgp-keys - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
On Mon, Oct 14, 2019 at 11:31 AM sebb wrote: > On Mon, 14 Oct 2019 at 07:51, Luis Panadero Guardeño > wrote: > > > > > > El 10/10/19 a las 12:50, sebb escribió: > > > Please explain what you mean. > > > > > > Are you saying that code compiled with Java 5 will not run on Java 12+ > ? > > > Is not, why not? > > > > Have you try to use JAI on OpenJDK 8 or Java 11/12/13 ? > > > > You will find that reading/writing images fails, because it's using some > > Sun internal APIs that only works on Sun/Oracle Java 6, 7 and 8. I need > > to change some old code using JAI, to read/write image using directly > > ImageIO to avoid this problem. > > I don't see how that is relevant to Commons Exec. > > If code uses unofficial APIs then there's bound to be a problem at some > point. > +1, "Sun internal" -> All bets are off. Gary > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [exec] Update from Java 5 to 6
On Mon, 14 Oct 2019 at 07:51, Luis Panadero Guardeño wrote: > > > El 10/10/19 a las 12:50, sebb escribió: > > Please explain what you mean. > > > > Are you saying that code compiled with Java 5 will not run on Java 12+ ? > > Is not, why not? > > Have you try to use JAI on OpenJDK 8 or Java 11/12/13 ? > > You will find that reading/writing images fails, because it's using some > Sun internal APIs that only works on Sun/Oracle Java 6, 7 and 8. I need > to change some old code using JAI, to read/write image using directly > ImageIO to avoid this problem. I don't see how that is relevant to Commons Exec. If code uses unofficial APIs then there's bound to be a problem at some point. > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
El 10/10/19 a las 12:50, sebb escribió: > Please explain what you mean. > > Are you saying that code compiled with Java 5 will not run on Java 12+ ? > Is not, why not? Have you try to use JAI on OpenJDK 8 or Java 11/12/13 ? You will find that reading/writing images fails, because it's using some Sun internal APIs that only works on Sun/Oracle Java 6, 7 and 8. I need to change some old code using JAI, to read/write image using directly ImageIO to avoid this problem.
Re: [exec] Update from Java 5 to 6
On Thu, 10 Oct 2019 at 08:53, John Patrick wrote: > > what about people wanting to use it on java 12 or java 13. Please explain what you mean. Are you saying that code compiled with Java 5 will not run on Java 12+ ? Is not, why not? > if java 1.5 and not wanting to upgrade is the argument, why would they be > upgrading the software... It's very different upgrading a single component as opposed to upgrading the JVM which runs multiple components. Much easier to test and revert. > if a company is choosing to use and run an out of support jvm’s then it is a > risk they are choosing to accept, either implicity or explicitly. > > maven and modules are two different things, in a few releases time the > classpath disappears and so any framework/jar that has not upgraded won’t > execute on the modern and current jvm. > > Sent from my iPhone > > > On 10 Oct 2019, at 08:40, Luis Panadero Guardeño > > wrote: > > > > The problem sometimes not are the developers and their desire of > > upgrading. The problem are the clients that don't desire to upgrade the JVM > > that have installed in their servers. > > I had a case where a client was running a Sun Java 5 JVM with a bug on > > String class that sometimes calculated bad string lengths and was making to > > our product to fail. The solution was to updated to a more modern JVM, but > > they don't like to do it. > > > > > > > > De: Xeno Amess > > Enviado: jueves, 10 de octubre de 2019 8:16 > > Para: Commons Developers List > > Asunto: Re: [exec] Update from Java 5 to 6 > > > > +1 for java 8 > > I just assume developers who still using java 6 do not care about > > upgrading their commons too... > > But what is the meaning of jigsawI mean, everybody use maven and > > maven is good, right? > > > > sebb 于2019年10月10日周四 上午6:55写道： > >> > >>> On Wed, 9 Oct 2019 at 22:38, John Patrick wrote: > >>> > >>> Regarding the question, it was by Simon Ritter (Azul Systems > >>> previously Oracle previously Sun). "Put your hand up if your running > >>> applications in production using Java X", started with Java 8, then > >>> asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if > >>> he said Java 5 but I don't think he did. > >> > >> OK, thanks. > >> > >>> It's great java is backwards compatible, but Java 5 was EOL 2009, Java > >>> 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage > >>> 2020 and AdoptOpenJDK 2023). > >>> > >>> People jokes and complained about Java was dead or slow and releases > >>> took 2-5 years... JPMS has now been released for 2 years and how many > >>> frameworks/applications have actually release a version where you can > >>> take advantage of modules and create real lightweight images. > >> > >> Most of Commons components are quite small, so is this really a concern? > >> > >>> I've been using Java since 1.1, I was annoyed major releases took > >>> ages, but I'm more annoyed about the whole java ecosystem not stepping > >>> up as they have got use to the previously slow release cycles. I > >>> realise OpenSource project is done in peoples spare time and they are > >>> choosing to participate, but I've tried with multiple projects to > >>> raise pull requests to help taking the next steps. > >>> > >>> My personal view is all commons projects should aim from Jan 2020 to > >>> bump to creating multi release jars of Java 8 and Java 11, so people > >>> using Java 8 are still supported and people using Java 11+ can uses > >>> modules. > >> > >> And anyone using Java 7 or earlier is excluded. > >> > >> Unless I am mistaken, if we don't create these multi-release jars, > >> people will still be able to use existing releases. > >> > >>> > >>> On Wed, 9 Oct 2019 at 18:21, Alex Herbert > >>> wrote: > >>>> > >>>> On 09/10/2019 14:12, Gary Gregory wrote: > >>>>> Hi All, > >>>>> > >>>>> I'd like to update Commons Exec from Java 5 to 6 to get it to build on > >>>>> Java > >>>>> 11. > >>>>> > >>>>> Gary > >>>> > >>>> Gary changed git master to update to 1.6 but travis was not able to > >>>> build for older JDKs. > &g
Re: [exec] Update from Java 5 to 6
what about people wanting to use it on java 12 or java 13. if java 1.5 and not wanting to upgrade is the argument, why would they be upgrading the software... if a company is choosing to use and run an out of support jvm’s then it is a risk they are choosing to accept, either implicity or explicitly. maven and modules are two different things, in a few releases time the classpath disappears and so any framework/jar that has not upgraded won’t execute on the modern and current jvm. Sent from my iPhone > On 10 Oct 2019, at 08:40, Luis Panadero Guardeño > wrote: > > The problem sometimes not are the developers and their desire of upgrading. > The problem are the clients that don't desire to upgrade the JVM that have > installed in their servers. > I had a case where a client was running a Sun Java 5 JVM with a bug on String > class that sometimes calculated bad string lengths and was making to our > product to fail. The solution was to updated to a more modern JVM, but they > don't like to do it. > > > > De: Xeno Amess > Enviado: jueves, 10 de octubre de 2019 8:16 > Para: Commons Developers List > Asunto: Re: [exec] Update from Java 5 to 6 > > +1 for java 8 > I just assume developers who still using java 6 do not care about > upgrading their commons too... > But what is the meaning of jigsawI mean, everybody use maven and > maven is good, right? > > sebb 于2019年10月10日周四 上午6:55写道： >> >>> On Wed, 9 Oct 2019 at 22:38, John Patrick wrote: >>> >>> Regarding the question, it was by Simon Ritter (Azul Systems >>> previously Oracle previously Sun). "Put your hand up if your running >>> applications in production using Java X", started with Java 8, then >>> asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if >>> he said Java 5 but I don't think he did. >> >> OK, thanks. >> >>> It's great java is backwards compatible, but Java 5 was EOL 2009, Java >>> 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage >>> 2020 and AdoptOpenJDK 2023). >>> >>> People jokes and complained about Java was dead or slow and releases >>> took 2-5 years... JPMS has now been released for 2 years and how many >>> frameworks/applications have actually release a version where you can >>> take advantage of modules and create real lightweight images. >> >> Most of Commons components are quite small, so is this really a concern? >> >>> I've been using Java since 1.1, I was annoyed major releases took >>> ages, but I'm more annoyed about the whole java ecosystem not stepping >>> up as they have got use to the previously slow release cycles. I >>> realise OpenSource project is done in peoples spare time and they are >>> choosing to participate, but I've tried with multiple projects to >>> raise pull requests to help taking the next steps. >>> >>> My personal view is all commons projects should aim from Jan 2020 to >>> bump to creating multi release jars of Java 8 and Java 11, so people >>> using Java 8 are still supported and people using Java 11+ can uses >>> modules. >> >> And anyone using Java 7 or earlier is excluded. >> >> Unless I am mistaken, if we don't create these multi-release jars, >> people will still be able to use existing releases. >> >>> >>> On Wed, 9 Oct 2019 at 18:21, Alex Herbert wrote: >>>> >>>> On 09/10/2019 14:12, Gary Gregory wrote: >>>>> Hi All, >>>>> >>>>> I'd like to update Commons Exec from Java 5 to 6 to get it to build on >>>>> Java >>>>> 11. >>>>> >>>>> Gary >>>> >>>> Gary changed git master to update to 1.6 but travis was not able to >>>> build for older JDKs. >>>> >>>> I have tried following the recommended instructions for their trusty >>>> distribution to use JDK 6 [1]. This did not work [2]. It would appear >>>> that travis cannot support openjdk6 any more. >>>> >>>> Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. >>>> >>>> I recommend dropping openjdk6 from the build matrix. >>>> >>>> Other items from the .travis.yml are the broken configuration for the >>>> coveralls report. This can be fixed separately as the pom needs some >>>> updating. >>>> >>>> Alex >>>> >>>> [1] >>>> https://docs.t
RE: [exec] Update from Java 5 to 6
The problem sometimes not are the developers and their desire of upgrading. The problem are the clients that don't desire to upgrade the JVM that have installed in their servers. I had a case where a client was running a Sun Java 5 JVM with a bug on String class that sometimes calculated bad string lengths and was making to our product to fail. The solution was to updated to a more modern JVM, but they don't like to do it. De: Xeno Amess Enviado: jueves, 10 de octubre de 2019 8:16 Para: Commons Developers List Asunto: Re: [exec] Update from Java 5 to 6 +1 for java 8 I just assume developers who still using java 6 do not care about upgrading their commons too... But what is the meaning of jigsawI mean, everybody use maven and maven is good, right? sebb 于2019年10月10日周四 上午6:55写道： > > On Wed, 9 Oct 2019 at 22:38, John Patrick wrote: > > > > Regarding the question, it was by Simon Ritter (Azul Systems > > previously Oracle previously Sun). "Put your hand up if your running > > applications in production using Java X", started with Java 8, then > > asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if > > he said Java 5 but I don't think he did. > > OK, thanks. > > > It's great java is backwards compatible, but Java 5 was EOL 2009, Java > > 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage > > 2020 and AdoptOpenJDK 2023). > > > > People jokes and complained about Java was dead or slow and releases > > took 2-5 years... JPMS has now been released for 2 years and how many > > frameworks/applications have actually release a version where you can > > take advantage of modules and create real lightweight images. > > Most of Commons components are quite small, so is this really a concern? > > > I've been using Java since 1.1, I was annoyed major releases took > > ages, but I'm more annoyed about the whole java ecosystem not stepping > > up as they have got use to the previously slow release cycles. I > > realise OpenSource project is done in peoples spare time and they are > > choosing to participate, but I've tried with multiple projects to > > raise pull requests to help taking the next steps. > > > > My personal view is all commons projects should aim from Jan 2020 to > > bump to creating multi release jars of Java 8 and Java 11, so people > > using Java 8 are still supported and people using Java 11+ can uses > > modules. > > And anyone using Java 7 or earlier is excluded. > > Unless I am mistaken, if we don't create these multi-release jars, > people will still be able to use existing releases. > > > > > On Wed, 9 Oct 2019 at 18:21, Alex Herbert wrote: > > > > > > On 09/10/2019 14:12, Gary Gregory wrote: > > > > Hi All, > > > > > > > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on > > > > Java > > > > 11. > > > > > > > > Gary > > > > > > Gary changed git master to update to 1.6 but travis was not able to > > > build for older JDKs. > > > > > > I have tried following the recommended instructions for their trusty > > > distribution to use JDK 6 [1]. This did not work [2]. It would appear > > > that travis cannot support openjdk6 any more. > > > > > > Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. > > > > > > I recommend dropping openjdk6 from the build matrix. > > > > > > Other items from the .travis.yml are the broken configuration for the > > > coveralls report. This can be fixed separately as the pom needs some > > > updating. > > > > > > Alex > > > > > > [1] > > > https://docs.travis-ci.com/user/reference/trusty/#jvm-clojure-groovy-java-scala-images > > > > > > [2] https://travis-ci.org/apache/commons-exec/builds/595713743 > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
+1 for java 8 I just assume developers who still using java 6 do not care about upgrading their commons too... But what is the meaning of jigsawI mean, everybody use maven and maven is good, right? sebb 于2019年10月10日周四 上午6:55写道： > > On Wed, 9 Oct 2019 at 22:38, John Patrick wrote: > > > > Regarding the question, it was by Simon Ritter (Azul Systems > > previously Oracle previously Sun). "Put your hand up if your running > > applications in production using Java X", started with Java 8, then > > asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if > > he said Java 5 but I don't think he did. > > OK, thanks. > > > It's great java is backwards compatible, but Java 5 was EOL 2009, Java > > 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage > > 2020 and AdoptOpenJDK 2023). > > > > People jokes and complained about Java was dead or slow and releases > > took 2-5 years... JPMS has now been released for 2 years and how many > > frameworks/applications have actually release a version where you can > > take advantage of modules and create real lightweight images. > > Most of Commons components are quite small, so is this really a concern? > > > I've been using Java since 1.1, I was annoyed major releases took > > ages, but I'm more annoyed about the whole java ecosystem not stepping > > up as they have got use to the previously slow release cycles. I > > realise OpenSource project is done in peoples spare time and they are > > choosing to participate, but I've tried with multiple projects to > > raise pull requests to help taking the next steps. > > > > My personal view is all commons projects should aim from Jan 2020 to > > bump to creating multi release jars of Java 8 and Java 11, so people > > using Java 8 are still supported and people using Java 11+ can uses > > modules. > > And anyone using Java 7 or earlier is excluded. > > Unless I am mistaken, if we don't create these multi-release jars, > people will still be able to use existing releases. > > > > > On Wed, 9 Oct 2019 at 18:21, Alex Herbert wrote: > > > > > > On 09/10/2019 14:12, Gary Gregory wrote: > > > > Hi All, > > > > > > > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on > > > > Java > > > > 11. > > > > > > > > Gary > > > > > > Gary changed git master to update to 1.6 but travis was not able to > > > build for older JDKs. > > > > > > I have tried following the recommended instructions for their trusty > > > distribution to use JDK 6 [1]. This did not work [2]. It would appear > > > that travis cannot support openjdk6 any more. > > > > > > Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. > > > > > > I recommend dropping openjdk6 from the build matrix. > > > > > > Other items from the .travis.yml are the broken configuration for the > > > coveralls report. This can be fixed separately as the pom needs some > > > updating. > > > > > > Alex > > > > > > [1] > > > https://docs.travis-ci.com/user/reference/trusty/#jvm-clojure-groovy-java-scala-images > > > > > > [2] https://travis-ci.org/apache/commons-exec/builds/595713743 > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
On Wed, 9 Oct 2019 at 22:38, John Patrick wrote: > > Regarding the question, it was by Simon Ritter (Azul Systems > previously Oracle previously Sun). "Put your hand up if your running > applications in production using Java X", started with Java 8, then > asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if > he said Java 5 but I don't think he did. OK, thanks. > It's great java is backwards compatible, but Java 5 was EOL 2009, Java > 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage > 2020 and AdoptOpenJDK 2023). > > People jokes and complained about Java was dead or slow and releases > took 2-5 years... JPMS has now been released for 2 years and how many > frameworks/applications have actually release a version where you can > take advantage of modules and create real lightweight images. Most of Commons components are quite small, so is this really a concern? > I've been using Java since 1.1, I was annoyed major releases took > ages, but I'm more annoyed about the whole java ecosystem not stepping > up as they have got use to the previously slow release cycles. I > realise OpenSource project is done in peoples spare time and they are > choosing to participate, but I've tried with multiple projects to > raise pull requests to help taking the next steps. > > My personal view is all commons projects should aim from Jan 2020 to > bump to creating multi release jars of Java 8 and Java 11, so people > using Java 8 are still supported and people using Java 11+ can uses > modules. And anyone using Java 7 or earlier is excluded. Unless I am mistaken, if we don't create these multi-release jars, people will still be able to use existing releases. > > On Wed, 9 Oct 2019 at 18:21, Alex Herbert wrote: > > > > On 09/10/2019 14:12, Gary Gregory wrote: > > > Hi All, > > > > > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on > > > Java > > > 11. > > > > > > Gary > > > > Gary changed git master to update to 1.6 but travis was not able to > > build for older JDKs. > > > > I have tried following the recommended instructions for their trusty > > distribution to use JDK 6 [1]. This did not work [2]. It would appear > > that travis cannot support openjdk6 any more. > > > > Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. > > > > I recommend dropping openjdk6 from the build matrix. > > > > Other items from the .travis.yml are the broken configuration for the > > coveralls report. This can be fixed separately as the pom needs some > > updating. > > > > Alex > > > > [1] > > https://docs.travis-ci.com/user/reference/trusty/#jvm-clojure-groovy-java-scala-images > > > > [2] https://travis-ci.org/apache/commons-exec/builds/595713743 > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
Regarding the question, it was by Simon Ritter (Azul Systems previously Oracle previously Sun). "Put your hand up if your running applications in production using Java X", started with Java 8, then asked about 11, then 12 and 13, then asked 7 and then 6. Not sure if he said Java 5 but I don't think he did. It's great java is backwards compatible, but Java 5 was EOL 2009, Java 6 was EOL 2013, Java 7 was EOL 2015, java 8 EOL 2019 personal usage 2020 and AdoptOpenJDK 2023). People jokes and complained about Java was dead or slow and releases took 2-5 years... JPMS has now been released for 2 years and how many frameworks/applications have actually release a version where you can take advantage of modules and create real lightweight images. I've been using Java since 1.1, I was annoyed major releases took ages, but I'm more annoyed about the whole java ecosystem not stepping up as they have got use to the previously slow release cycles. I realise OpenSource project is done in peoples spare time and they are choosing to participate, but I've tried with multiple projects to raise pull requests to help taking the next steps. My personal view is all commons projects should aim from Jan 2020 to bump to creating multi release jars of Java 8 and Java 11, so people using Java 8 are still supported and people using Java 11+ can uses modules. On Wed, 9 Oct 2019 at 18:21, Alex Herbert wrote: > > On 09/10/2019 14:12, Gary Gregory wrote: > > Hi All, > > > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java > > 11. > > > > Gary > > Gary changed git master to update to 1.6 but travis was not able to > build for older JDKs. > > I have tried following the recommended instructions for their trusty > distribution to use JDK 6 [1]. This did not work [2]. It would appear > that travis cannot support openjdk6 any more. > > Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. > > I recommend dropping openjdk6 from the build matrix. > > Other items from the .travis.yml are the broken configuration for the > coveralls report. This can be fixed separately as the pom needs some > updating. > > Alex > > [1] > https://docs.travis-ci.com/user/reference/trusty/#jvm-clojure-groovy-java-scala-images > > [2] https://travis-ci.org/apache/commons-exec/builds/595713743 > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
On 09/10/2019 14:12, Gary Gregory wrote: Hi All, I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java 11. Gary Gary changed git master to update to 1.6 but travis was not able to build for older JDKs. I have tried following the recommended instructions for their trusty distribution to use JDK 6 [1]. This did not work [2]. It would appear that travis cannot support openjdk6 any more. Using 'dist: trusty' allows a clean build on JDK 7, 8, 11. I recommend dropping openjdk6 from the build matrix. Other items from the .travis.yml are the broken configuration for the coveralls report. This can be fixed separately as the pom needs some updating. Alex [1] https://docs.travis-ci.com/user/reference/trusty/#jvm-clojure-groovy-java-scala-images [2] https://travis-ci.org/apache/commons-exec/builds/595713743 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
+1 Am 09.10.2019 um 17:25 schrieb John Patrick: What about Java 5 to 8. I'm current sat at Jax London and was the sole person who put their hand up for Java 6, and next Conference I hope to have migrated everything to at least Java 8. From the rest I saw 1 hand being raised for Java 7, about 2/3rd's said Java 8 and 1/3rd said Java 11, with a handful saying Java 12 or 13. On Wed, 9 Oct 2019 at 14:12, Gary Gregory wrote: Hi All, I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java 11. Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
On Wed, 9 Oct 2019 at 16:25, John Patrick wrote: > > What about Java 5 to 8. > I'm current sat at Jax London and was the sole person who put their > hand up for Java 6, and next Conference I hope to have migrated > everything to at least Java 8. From the rest I saw 1 hand being raised > for Java 7, about 2/3rd's said Java 8 and 1/3rd said Java 11, with a > handful saying Java 12 or 13. What was the exact question? Java is upward compatible, so the binary for Exec compiled on Java 5 will work on Java 6,7, etc. Indeed the source will probably compile without any need for changes on the same platforms. However, there does come a time when it becomes difficult to get hold of the earlier compilers. At which point it may be necessary to update the minimum compiler version in the Maven POM. In many cases, that should be sufficient; no need to update the source as well. Let's do the minimum work needed here, and exclude as Java versions as possible. > On Wed, 9 Oct 2019 at 14:12, Gary Gregory wrote: > > > > Hi All, > > > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java > > 11. > > > > Gary > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [exec] Update from Java 5 to 6
What about Java 5 to 8. I'm current sat at Jax London and was the sole person who put their hand up for Java 6, and next Conference I hope to have migrated everything to at least Java 8. From the rest I saw 1 hand being raised for Java 7, about 2/3rd's said Java 8 and 1/3rd said Java 11, with a handful saying Java 12 or 13. On Wed, 9 Oct 2019 at 14:12, Gary Gregory wrote: > > Hi All, > > I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java > 11. > > Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[exec] Update from Java 5 to 6
Hi All, I'd like to update Commons Exec from Java 5 to 6 to get it to build on Java 11. Gary
