Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed
On 18/08/2013 00:42, b...@apache.org wrote:
> build-only:
> [javac] Compiling 97 source files to
> /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
> [javac]
> /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/src/share/org/apache/jasper/compiler/JDTCompiler.java:86:
> error: CompilationUnit is not abstract and does not override abstract method
> ignoreOptionalProblems() in ICompilationUnit
> [javac] class CompilationUnit implements ICompilationUnit {
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 1 error
This isn't going to work until the right version the Eclipse JDT
compiler (ecj-3.7.2.jar) is available in the Eclipse package.
Is there a way I can make this happen via updating the metadata? I
didn't see anything obvious.
Mark
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed
On 2013-08-20, Mark Thomas wrote:
> On 18/08/2013 00:42, b...@apache.org wrote:
>
>> build-only:
>> [javac] Compiling 97 source files to
>> /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
>> [javac]
>> /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/src/share/org/apache/jasper/compiler/JDTCompiler.java:86:
>> error: CompilationUnit is not abstract and does not override abstract
>> method ignoreOptionalProblems() in ICompilationUnit
>> [javac] class CompilationUnit implements ICompilationUnit {
>> [javac] ^
>> [javac] Note: Some input files use or override a deprecated API.
>> [javac] Note: Recompile with -Xlint:deprecation for details.
>> [javac] 1 error
> This isn't going to work until the right version the Eclipse JDT
> compiler (ecj-3.7.2.jar) is available in the Eclipse package.
> Is there a way I can make this happen via updating the metadata? I
> didn't see anything obvious.
No, the "installed packages", i.e. stuff Gump doesn't build but provides
as jars, can only be added by Gump PMC members.
So far I held back as I expected you to tell me that you wanted to drop
the Tomcat 5 builds :-)
I can and will take care of the older ecj version unless Bill beats me
to it or you stop me.
Stefan
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed
Stefan Bodewig wrote:
>On 2013-08-20, Mark Thomas wrote:
>
>> On 18/08/2013 00:42, b...@apache.org wrote:
>
>>
>
>>> build-only:
>>> [javac] Compiling 97 source files to
>/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
>>> [javac]
>/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/src/share/org/apache/jasper/compiler/JDTCompiler.java:86:
>error: CompilationUnit is not abstract and does not override abstract
>method ignoreOptionalProblems() in ICompilationUnit
>>> [javac] class CompilationUnit implements
>ICompilationUnit {
>>> [javac] ^
>>> [javac] Note: Some input files use or override a deprecated API.
>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>> [javac] 1 error
>
>> This isn't going to work until the right version the Eclipse JDT
>> compiler (ecj-3.7.2.jar) is available in the Eclipse package.
>
>> Is there a way I can make this happen via updating the metadata? I
>> didn't see anything obvious.
>
>No, the "installed packages", i.e. stuff Gump doesn't build but
>provides
>as jars, can only be added by Gump PMC members.
>
>So far I held back as I expected you to tell me that you wanted to drop
>the Tomcat 5 builds :-)
Dropping the Tomcat 5 builds is fine. I assumed it was still there because
something else you wanted to keep depended on it.
Mark
-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed
On 2013-08-21, Mark Thomas wrote: > Dropping the Tomcat 5 builds is fine. I assumed it was still there > because something else you wanted to keep depended on it. No, the Tomcat 4/5 builds are really only there because I didn't want to pull the trigger too soon. I am subscribed to dev@tomcat and have seen your answer there. Tomcat 4 is used by Ant for the old jspc task but the dependency is optional and Ant doesn't want Gump builds anymore anyway. Some projects depend on some old Servlet API builds so we can't remove everything right away. I'll sort this out and remove the Tomcat 4/5 related builds over the next few iterations - and I'll remove nagging for those projects immediately. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
