On March 21, 2019 2:42:44 AM UTC, Bill Barker wrote:
>To whom it may engage...
>
>This is an automated request, but not an unsolicited one. For
>more information please visit http://gump.apache.org/nagged.html,
>and/or contact the folk at gene...@gump.apache.org.
>
>Project tomcat-trunk
On 17/01/2019 02:09, Bill Barker wrote:
> [javac] symbol: class ExtensibilityElement
> [javac] location: class ServiceRefFactory
> [javac]
> /srv/gump/public/workspace/tomcat-trunk/java/org/apache/naming/factory/webservices/ServiceRefFactory.java:328:
> error: cannot find
On Tue, Oct 9, 2018 at 4:45 AM Bill Barker wrote:
> The following work was performed:
>
> http://vmgump-vm3.apache.org/tomcat-trunk/tomcat-trunk/gump_work/build_tomcat-trunk_tomcat-trunk.html
> Work Name: build_tomcat-trunk_tomcat-trunk (Type: Build)
> Work ended in a state of : Failed
>
On 31/05/18 14:13, Mark Thomas wrote:
> On 31/05/18 10:07, Bill Barker wrote:
>
>
>
>> /srv/gump/public/workspace/tomcat-trunk/build.xml:3037: Problem: failed to
>> create task or type bndwrap
>
> I have made an attempt to fix this. I based my fix on how the Eclipse
> JDT jar is referenced. I
On 31/05/18 10:07, Bill Barker wrote:
> /srv/gump/public/workspace/tomcat-trunk/build.xml:3037: Problem: failed to
> create task or type bndwrap
I have made an attempt to fix this. I based my fix on how the Eclipse
JDT jar is referenced. I think I did it correctly but we'll need to wait
until
This is caused by the update to JDT 4.7.x in trunk.
There is a backwards incompatible change in the constant used to refer
to Java 9 between 4.6.x and 4.7.x.
My plan to fix this is as follows:
- update Gump to use latest ECJ JAR
- this will fix 9.0.x
- this will break the Gump build for all
