RE: new dependency
Luis personally i never download snapshots as snapshots reflect the collection of files at a particular date/time so for example if you would be willing to take 1.8.0 version (no datetime snapshot) in maven configuration file which is named apache-settings.xml or gump-settings.xml locate the configuration file*-settings.xml insert the repository that hosts fontbox-1.8.0.jar for example i can locate fontbox-1.8.0.jar in mvnrepository at http://mvnrepository.com/artifact/org.apache.pdfbox/fontbox/1.8.0 repositories ... repository idfontbox/id nameRepository for fontbox builds/name url http://mvnrepository.com/artifact//url layoutdefault/layout snapshotPolicyalways/snapshotPolicy /repository in the pom.xml add the fontbox dependency pom.xml dependencies dependency groupIdorg.apache.pdfbox/groupId artifactIdfontbox/artifactId version1.8.0/version /dependency ... /dependencies Saludos Cordiales desde EEUU Martin __ Porfavor..no altere ni interrumpir esta communicacion...Gracias Date: Tue, 20 Aug 2013 00:11:44 +0100 From: lmpmberna...@gmail.com To: general@gump.apache.org Subject: new dependency Hello, I am a developer for the xmlgraphics-fop project. Our build gump has been failing for the last couple of days. While trying to figure out how to fix the problem, which is due to a new dependency on a new jar file, I came across the info below in your http://gump.apache.org/nagged.html page: The most common occurrence of problems here is introducing a new dependency without the Gump project definition being updated. A note togene...@gump.apache.org http://gump.apache.org/mail.htmlletting us know what is going on is appreciated when this occurs. So it looks like I cannot fix it myself but rather I have to ask you to do so. A new jar, fontbox-1.8.0-SNAPSHOT.jar, was added to the project, so I assume you need to update the project definition. Let me know if there is anything else I can do. Thanks, Luis lberna...@apache.org
RE: new dependency
Hi Martin, Martin Gainty wrote: Luis personally i never download snapshots as snapshots reflect the collection of files at a particular date/time Well, but that's the whole purpose of Gump. Even more, Gump will take a SNAPSHOT anyway - unless you overwrite this in the Gump descriptor, see Stefan's answer. [snip] - Jörg - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: new dependency
On 2013-08-20, Jörg Schaible wrote: personally i never download snapshots as snapshots reflect the collection of files at a particular date/time Well, but that's the whole purpose of Gump. Right. As Luis told me off-list, FOP's case is a bit different as FOP uses a patched version of fontbox as long as their patch hasn't been accepted upstream. That's why he changed the dependency to their own local version of fontbox. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
2013/8/20 Mark Thomas ma...@apache.org: On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? 1) First, model-level log http://vmgump.apache.org/gump/public/tomcat-7.0.x/index.html says *** Failed to update from source control.Stale contents *** and the following: [[[ svn: URL 'http://svn.apache.org/repos/asf/tomcat/trunk/modules/jdbc-pool' of exis... ting directory 'tomcat-7.0.x/modules/jdbc-pool' does not match expected URL 'htt... p://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/modules/jdbc-pool' ]]] I think removing the whole directory and performing a clean svn checkout should fix this. (The modules/jdbc-pool directory was an external that pulled sources from Tomcat trunk, but nowadays it is just an ordinary subdirectory. This change happened more than a year ago. I think most of the sources in the working copy are up-to-date, but that particular directory is stale. It explains why it went unnoticed for quite some time). 2) Second, I suspect that svn update happens when a Gump run starts. That may be several hours before the actual build. I do not see any indication of what revision number was used for the build. Is it possible to remove --quiet flag from svn update command? With that flag removed it would print a) list of updated files, b) svn revision number to which the working copy was updated. http://vmgump.apache.org/gump/public/tomcat-7.0.x/gump_work/update_tomcat-7.0.x.html Best regards, Konstantin Kolinko - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? 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:
snip/
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 tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
On 2013-08-21, Konstantin Kolinko wrote: 2013/8/20 Mark Thomas ma...@apache.org: On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? 1) First, model-level log http://vmgump.apache.org/gump/public/tomcat-7.0.x/index.html says *** Failed to update from source control.Stale contents *** [...] I think removing the whole directory and performing a clean svn checkout should fix this. Oh, I missed that in the logs, directory removed, the next Gump run (at 6AM UTC) will perform a fresh checkout. 2) Second, I suspect that svn update happens when a Gump run starts. It happens just before the first project defined in the module is built. That may be several hours before the actual build. Right now the whole Gump run takes about two-and-a-half hours, I don't think this will be a big issue. I do not see any indication of what revision number was used for the build. Is it possible to remove --quiet flag from svn update command? With that flag removed it would print a) list of updated files, b) svn revision number to which the working copy was updated. http://vmgump.apache.org/gump/public/tomcat-7.0.x/gump_work/update_tomcat-7.0.x.html I just see the documentation for this is missing. The svn element (and all other SCM and builder related elements) support two attributes verbose and debug which enable more detailed output when set to true. For svn both have the same effect and just remove the --quiet. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
