Re: Starting to move Gump to using Java 11

2021-08-12 Thread Mark Thomas
It looks like I have broken the Ant build somehow. I can't see what I 
have done wrong. No rush, but some help on this from someone more 
familiar with the Ant build than I would be helpful.


Mark


On 12/08/2021 10:57, Mark Thomas wrote:



On 12/08/2021 10:46, Stefan Bodewig wrote:

Many thank for doing this, Mark

On 2021-08-10, Mark Thomas wrote:


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.


I think it should be possible to allow JAVA_HOME to be overridden on a
project by project basis but I doubt anybody is less rusty WRT Gump's
Python code base than Adam :-)

If the short term solution is to make some Tomcat builds use a different
version of Java then we'd only need to modify the Ant builder. This one
uses self.run.getEnvironment().getJavaCommand() which is what JAVA_HOME
points at. We could add a "java_home" property or something similar to
the model for  (BaseAnt) and calculate the Java command inside of
the Ant builder if this attribute is set. Making a configurable
JAVA_HOME work for Gradle and Maven as well would require a bit more of
work.

I can try to carve out some time for this next week, but I'm afraid you
want a solution more quickly.


Thanks for the offer. Things have moved on a bit and I think we are OK 
running with Java 11 everywhere. There are still a few things to clean 
up but it looks doable at this point.


I'm going to chip away at the remaining issues as I get the time. As 
always, help welcome. I'm expecting this is going to take a few more 
weeks to sort out. I think there are also some genuine failures in the 
Tomcat test runs so Java 11 may not be responsible for all the current 
issues.


Cheers,

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



Problem running Apache Gump [vmgump]

2021-08-12 Thread gump
There is a problem with run 'vmgump' (12082021_140947), 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 [ant-dist]
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]

2021-08-12 Thread gump
There is a problem with run 'vmgump' (12082021_120001), 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 :
Failed to publish 
'/srv/gump/public/workspace/tomcat-tc9/output/build/lib/tomcat-i18n-ru.jar' to 
proxy
Traceback (most recent call last):
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 88, in processProject
self.publish(groupId, output.getId(), fileName)
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 100, in publish
urllib.request.urlopen(self.proxyURL + 'addartifact',
  File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 522, in open
req = meth(req)
  File "/usr/lib/python3.8/urllib/request.py", line 1285, in do_request_
raise TypeError(msg)
TypeError: POST data should be bytes, an iterable of bytes, or a file object. 
It cannot be of type str.
Failed to publish 
'/srv/gump/public/workspace/tomcat-tc9/output/build/lib/tomcat-i18n-zh-CN.jar' 
to proxy
Traceback (most recent call last):
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 88, in processProject
self.publish(groupId, output.getId(), fileName)
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 100, in publish
urllib.request.urlopen(self.proxyURL + 'addartifact',
  File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 522, in open
req = meth(req)
  File "/usr/lib/python3.8/urllib/request.py", line 1285, in do_request_
raise TypeError(msg)
TypeError: POST data should be bytes, an iterable of bytes, or a file object. 
It cannot be of type str.
Build Project: #[(130, 139)] : tomcat-tc9-test-nio :  [state:Unset]
Run Ant on Project: #[(130, 139)] : tomcat-tc9-test-nio
Failed to build project #[(130, 139)] : [tomcat-tc9-test-nio], state:Failed
Perform Update on #[(62, 62)] : tomcat-taglibs
Perform Git Checkout/Update on #[(62, 62)] : tomcat-taglibs
Build Project: #[(131, 139)] : taglibs-standard-spec :  [state:Unset]
Run Maven on Project: #[(131, 139)] : taglibs-standard-spec
Failed to publish 
'/srv/gump/public/workspace/tomcat-taglibs/spec/target/taglibs-standard-spec-2.0.0-SNAPSHOT.jar'
 to proxy
Traceback (most recent call last):
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 88, in processProject
self.publish(groupId, output.getId(), fileName)
  File "/srv/gump/public/gump/python/gump/actor/mvnrepoproxy/proxycontrol.py", 
line 100, in publish
urllib.request.urlopen(self.proxyURL + 'addartifact',
  File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 522, in open
req = meth(req)
  File "/usr/lib/python3.8/urllib/request.py", line 1285, in do_request_
raise TypeError(msg)
TypeError: POST data should be bytes, an iterable of bytes, or a file object. 
It cannot be of type str.
Build Project: #[(132, 139)] : tomcat-10.0.x-test-nio2 :  [state:Unset]
Run Ant on Project: #[(132, 139)] : tomcat-10.0.x-test-nio2
Killed
Process Exit Code : 137
--
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

2021-08-12 Thread Mark Thomas




On 12/08/2021 10:46, Stefan Bodewig wrote:

Many thank for doing this, Mark

On 2021-08-10, Mark Thomas wrote:


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.


I think it should be possible to allow JAVA_HOME to be overridden on a
project by project basis but I doubt anybody is less rusty WRT Gump's
Python code base than Adam :-)

If the short term solution is to make some Tomcat builds use a different
version of Java then we'd only need to modify the Ant builder. This one
uses self.run.getEnvironment().getJavaCommand() which is what JAVA_HOME
points at. We could add a "java_home" property or something similar to
the model for  (BaseAnt) and calculate the Java command inside of
the Ant builder if this attribute is set. Making a configurable
JAVA_HOME work for Gradle and Maven as well would require a bit more of
work.

I can try to carve out some time for this next week, but I'm afraid you
want a solution more quickly.


Thanks for the offer. Things have moved on a bit and I think we are OK 
running with Java 11 everywhere. There are still a few things to clean 
up but it looks doable at this point.


I'm going to chip away at the remaining issues as I get the time. As 
always, help welcome. I'm expecting this is going to take a few more 
weeks to sort out. I think there are also some genuine failures in the 
Tomcat test runs so Java 11 may not be responsible for all the current 
issues.


Cheers,

Mark

-
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

2021-08-12 Thread Stefan Bodewig
Many thank for doing this, Mark

On 2021-08-10, Mark Thomas wrote:

> 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.

I think it should be possible to allow JAVA_HOME to be overridden on a
project by project basis but I doubt anybody is less rusty WRT Gump's
Python code base than Adam :-)

If the short term solution is to make some Tomcat builds use a different
version of Java then we'd only need to modify the Ant builder. This one
uses self.run.getEnvironment().getJavaCommand() which is what JAVA_HOME
points at. We could add a "java_home" property or something similar to
the model for  (BaseAnt) and calculate the Java command inside of
the Ant builder if this attribute is set. Making a configurable
JAVA_HOME work for Gradle and Maven as well would require a bit more of
work.

I can try to carve out some time for this next week, but I'm afraid you
want a solution more quickly.

Stefan

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org