Re: Starting to move Gump to using Java 11
On 11/08/2021 10:46, Mark Thomas wrote: On 11/08/2021 09:06, Adam Jack wrote: I am traveling home from abroad right now but I can look into things when I get settled back. That said, I am sure others are far less rusty than me on this. That said, from my rusty/simplistic perspective: Would the best case be that the whole stack be built with one compiler/language version, the newest supported, so we uncover any build issues and then mail them to teams? Would that be helpful to getting those build issues resolved, or are such notifications going unanswered? Meaning do we change the Java version and then wait, rather than work around things? Sorry if that is missing something obvious (I haven’t touched Java in well over a decade.) Thanks. Additional eyes on this would be good. I agree that in an ideal world, everything would build with the latest version of Java. Switching from Java 8 to Java 11 was a step in that direction. The complicating factor is that the chain of dependencies leads back to (branches of) projects that are no longer maintained and don't build with Java >8. In some cases, updating the dependencies to newer branches is an option. I managed to remove Commons Lang 2.x from the dependency chain that way. However, there are some dependency chains where that does not appear to be an option. Maybe the right answer is that we should just provide JARs for such projects rather than trying to build them. Also, there are potentially some dependencies where we aren't building from source and perhaps should be such as the Eclipse JDT JAR. Given that Tomcat is the only project really using Gump right now, I think I am going to start there and work backwards checking dependencies as I suspect some of those may be rather out of date. It might be that the problem will turn out to be a lot simpler than it appears, once the dependencies are tidied up. Packaging log4j 1.2.x and removing a number of the old XML dependencies has improved things quite a bit. I think there has been sufficient progress to continue running with Java 11 and fix the remaining issues as they arise. As part of the clean-up / simplification I am currently planning on pruning various optional dependencies unless the Tomcat builds require them. Please speak up if there are any objections to doing this. Mark - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Problem running Apache Gump [vmgump]
There is a problem with run 'vmgump' (11082021_165910), location :
http://gump-vm2.apache.org/
The log ought be at:
http://gump-vm2.apache.org/gump_log.txt
The last (up to) 50 lines of the log are :
Parsed file /srv/gump/public/gump/metadata/project/xml-xalan.xml
Parsed file /srv/gump/public/gump/metadata/project/xml-commons.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-migration.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-1.2-1.1.1.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-main.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-10.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-9.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-8.5.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs-parent.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-connectors-native.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-servletapi-5.xml
Parsed file /srv/gump/public/gump/metadata/project/apr-1.xml
Parsed file /srv/gump/public/gump/metadata/project/apr.xml
Parsed file /srv/gump/public/gump/metadata/project/logging-log4j-12.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-httpd.xml
Parsed file /srv/gump/public/gump/metadata/project/pcre.xml
Parsed file /srv/gump/public/gump/metadata/project/gump.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-validator.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-net.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-logging.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-lang-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-io.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-httpclient.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-exec.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-digester-2.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-daemon.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-compress.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-collections-3.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-codec-1.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-cli.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-beanutils.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-bsf.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-attic.xml
Parsed file /srv/gump/public/gump/metadata/project/antlibs-antunit.xml
Parsed file /srv/gump/public/gump/metadata/project/ant.xml
Traceback (most recent call last):
File "bin/integrate.py", line 114, in
irun()
File "bin/integrate.py", line 88, in irun
run=gump.core.run.gumprun.GumpRun(workspace,ps,options)
File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 82, in
__init__
self.gumpSet=gump.core.run.gumpset.GumpSet(self.workspace,expr)
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 119, in
__init__
self.validate()
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 124, in
validate
raise RuntimeError('No projects match [' + self.projectexpression + ']')
RuntimeError: No projects match [tomcat-8.5.x]
Process Exit Code : 1
--
Gump Version: 2.0.2-alpha-0003
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Problem running Apache Gump [vmgump]
There is a problem with run 'vmgump' (11082021_145503), location :
http://gump-vm2.apache.org/
The log ought be at:
http://gump-vm2.apache.org/gump_log.txt
The last (up to) 50 lines of the log are :
Parsed file /srv/gump/public/gump/metadata/project/xml-xalan.xml
Parsed file /srv/gump/public/gump/metadata/project/xml-commons.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-migration.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-1.2-1.1.1.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-main.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-10.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-9.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-8.5.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs-parent.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-connectors-native.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-servletapi-5.xml
Parsed file /srv/gump/public/gump/metadata/project/apr-1.xml
Parsed file /srv/gump/public/gump/metadata/project/apr.xml
Parsed file /srv/gump/public/gump/metadata/project/logging-log4j-12.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-httpd.xml
Parsed file /srv/gump/public/gump/metadata/project/pcre.xml
Parsed file /srv/gump/public/gump/metadata/project/gump.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-validator.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-net.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-logging.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-lang-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-io.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-httpclient.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-exec.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-digester-2.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-daemon.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-compress.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-collections-3.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-codec-1.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-cli.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-beanutils.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-bsf.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-attic.xml
Parsed file /srv/gump/public/gump/metadata/project/antlibs-antunit.xml
Parsed file /srv/gump/public/gump/metadata/project/ant.xml
Traceback (most recent call last):
File "bin/integrate.py", line 114, in
irun()
File "bin/integrate.py", line 88, in irun
run=gump.core.run.gumprun.GumpRun(workspace,ps,options)
File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 82, in
__init__
self.gumpSet=gump.core.run.gumpset.GumpSet(self.workspace,expr)
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 119, in
__init__
self.validate()
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 124, in
validate
raise RuntimeError('No projects match [' + self.projectexpression + ']')
RuntimeError: No projects match [xml-xalan]
Process Exit Code : 1
--
Gump Version: 2.0.2-alpha-0003
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Problem running Apache Gump [vmgump]
There is a problem with run 'vmgump' (11082021_145059), location :
http://gump-vm2.apache.org/
The log ought be at:
http://gump-vm2.apache.org/gump_log.txt
The last (up to) 50 lines of the log are :
Parsed file /srv/gump/public/gump/metadata/project/xml-xalan.xml
Parsed file /srv/gump/public/gump/metadata/project/xml-commons.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-migration.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-native-1.2-1.1.1.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-main.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-10.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-9.0.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-8.5.x.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs-parent.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-taglibs.xml
Parsed file /srv/gump/public/gump/metadata/project/tomcat-connectors-native.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-servletapi-5.xml
Parsed file /srv/gump/public/gump/metadata/project/apr-1.xml
Parsed file /srv/gump/public/gump/metadata/project/apr.xml
Parsed file /srv/gump/public/gump/metadata/project/logging-log4j-12.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-httpd.xml
Parsed file /srv/gump/public/gump/metadata/project/pcre.xml
Parsed file /srv/gump/public/gump/metadata/project/gump.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-validator.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-net.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-logging.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-lang-trunk.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-io.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-httpclient.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-exec.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-digester-2.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-daemon.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-compress.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-collections-3.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-codec-1.x.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-cli.xml
Parsed file /srv/gump/public/gump/metadata/project/commons-beanutils.xml
Parsed file /srv/gump/public/gump/metadata/project/jakarta-bsf.xml
Parsed file /srv/gump/public/gump/metadata/project/apache-attic.xml
Parsed file /srv/gump/public/gump/metadata/project/antlibs-antunit.xml
Parsed file /srv/gump/public/gump/metadata/project/ant.xml
Traceback (most recent call last):
File "bin/integrate.py", line 114, in
irun()
File "bin/integrate.py", line 88, in irun
run=gump.core.run.gumprun.GumpRun(workspace,ps,options)
File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 82, in
__init__
self.gumpSet=gump.core.run.gumpset.GumpSet(self.workspace,expr)
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 119, in
__init__
self.validate()
File "/srv/gump/public/gump/python/gump/core/run/gumpset.py", line 124, in
validate
raise RuntimeError('No projects match [' + self.projectexpression + ']')
RuntimeError: No projects match [xerces]
Process Exit Code : 1
--
Gump Version: 2.0.2-alpha-0003
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Re: Starting to move Gump to using Java 11
On 11/08/2021 09:06, Adam Jack wrote: I am traveling home from abroad right now but I can look into things when I get settled back. That said, I am sure others are far less rusty than me on this. That said, from my rusty/simplistic perspective: Would the best case be that the whole stack be built with one compiler/language version, the newest supported, so we uncover any build issues and then mail them to teams? Would that be helpful to getting those build issues resolved, or are such notifications going unanswered? Meaning do we change the Java version and then wait, rather than work around things? Sorry if that is missing something obvious (I haven’t touched Java in well over a decade.) Thanks. Additional eyes on this would be good. I agree that in an ideal world, everything would build with the latest version of Java. Switching from Java 8 to Java 11 was a step in that direction. The complicating factor is that the chain of dependencies leads back to (branches of) projects that are no longer maintained and don't build with Java >8. In some cases, updating the dependencies to newer branches is an option. I managed to remove Commons Lang 2.x from the dependency chain that way. However, there are some dependency chains where that does not appear to be an option. Maybe the right answer is that we should just provide JARs for such projects rather than trying to build them. Also, there are potentially some dependencies where we aren't building from source and perhaps should be such as the Eclipse JDT JAR. Given that Tomcat is the only project really using Gump right now, I think I am going to start there and work backwards checking dependencies as I suspect some of those may be rather out of date. It might be that the problem will turn out to be a lot simpler than it appears, once the dependencies are tidied up. Mark Regards, Adam On Tue, Aug 10, 2021 at 11:15 PM Mark Thomas wrote: On 10/08/2021 21:38, Mark Thomas wrote: On 10/08/2021 21:17, Adam Jack wrote: Thanks for the update. Good luck. Thanks. I think I am going to need it. This is going to be *far* from simple. There is lots of code currently being built by Gump that needs changes to build with Java 9+. You will have seen I started to try and hack around the issues with Commons Lang 2.4 (it was using source=1.4) but forcing source to 1.6 (the minimum Java 11 supports) just creates a different problem - the source using "enum" as an identifier but it is a reserved word from Java 5 onwards. I don't see a simple or quick solution for this. Is there a way in Gump to get just some projects to build with a different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11 is the minimum requirement. We can then take a harder look at the dependency chains and see what we can do to update versions / trim things down. On the topic of dependency chains, log4j 1.2.x is currently blocking progress. I need to set the source and target to 1.6 (local testing on vmgump suggests this will then work) but I don't know how to do that. I see "POM overrides" in a few places But I can't figure out how to use them. Is there a way to copy the log4j POM, store it somewhere in Gump and then tweak it (essentially change "1.4" to "1.6")? Mark Mark Adam On Tue, Aug 10, 2021, 15:57 Mark Thomas wrote: All, Since Tomcat's main development branch now requires Java 11, I have started the process of moving Gump over to Java 11. So far, I have added Java 11 to the packages installed by Puppet. I want to confirm that Java 11 has been installed, then I'll switch JAVA_HOME to point to Java 11 rather than Java 8. In theory that should 'just work'. When it doesn't (optimistic soul that I am), we'll have to see what fails and figure out the best way to deal with each issue. Once everything is running smoothly on Java 11, then I'll remove Java 8. Mark - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org -- Sent from Mobile - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Starting to move Gump to using Java 11
I am traveling home from abroad right now but I can look into things when I get settled back. That said, I am sure others are far less rusty than me on this. That said, from my rusty/simplistic perspective: Would the best case be that the whole stack be built with one compiler/language version, the newest supported, so we uncover any build issues and then mail them to teams? Would that be helpful to getting those build issues resolved, or are such notifications going unanswered? Meaning do we change the Java version and then wait, rather than work around things? Sorry if that is missing something obvious (I haven’t touched Java in well over a decade.) Regards, Adam On Tue, Aug 10, 2021 at 11:15 PM Mark Thomas wrote: > On 10/08/2021 21:38, Mark Thomas wrote: > > On 10/08/2021 21:17, Adam Jack wrote: > >> Thanks for the update. Good luck. > > > > Thanks. I think I am going to need it. This is going to be *far* from > > simple. > > > > There is lots of code currently being built by Gump that needs changes > > to build with Java 9+. > > > > You will have seen I started to try and hack around the issues with > > Commons Lang 2.4 (it was using source=1.4) but forcing source to 1.6 > > (the minimum Java 11 supports) just creates a different problem - the > > source using "enum" as an identifier but it is a reserved word from Java > > 5 onwards. > > > > I don't see a simple or quick solution for this. > > > > Is there a way in Gump to get just some projects to build with a > > different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11 > > is the minimum requirement. We can then take a harder look at the > > dependency chains and see what we can do to update versions / trim > > things down. > > On the topic of dependency chains, log4j 1.2.x is currently blocking > progress. > > I need to set the source and target to 1.6 (local testing on vmgump > suggests this will then work) but I don't know how to do that. > > I see "POM overrides" in a few places But I can't figure out how to use > them. Is there a way to copy the log4j POM, store it somewhere in Gump > and then tweak it (essentially change "1.4" to "1.6")? > > Mark > > > > > > Mark > > > > > > > >> > >> Adam > >> > >> On Tue, Aug 10, 2021, 15:57 Mark Thomas wrote: > >> > >>> All, > >>> > >>> Since Tomcat's main development branch now requires Java 11, I have > >>> started the process of moving Gump over to Java 11. > >>> > >>> So far, I have added Java 11 to the packages installed by Puppet. > >>> > >>> I want to confirm that Java 11 has been installed, then I'll switch > >>> JAVA_HOME to point to Java 11 rather than Java 8. In theory that should > >>> 'just work'. When it doesn't (optimistic soul that I am), we'll have to > >>> see what fails and figure out the best way to deal with each issue. > >>> > >>> Once everything is running smoothly on Java 11, then I'll remove Java > 8. > >>> > >>> Mark > >>> > >>> - > >>> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > >>> For additional commands, e-mail: general-h...@gump.apache.org > >>> > >>> > >> > > > > - > > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > > For additional commands, e-mail: general-h...@gump.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > For additional commands, e-mail: general-h...@gump.apache.org > > -- Sent from Mobile
