991 2014-03-04 20:23:18 +0100 Some files are not being deployed by the maven scripts 2014-03-06 12:21:00 +0100 1 1 3 JogAmp General builds unspecified All all RESOLVED FIXED --- enhancement --- 1 org.jogamp org.jogamp --- 7f28cc15004e143f77f7b90f8e543c16f84dcff0 --- oldest_to_newest 3820 0 org.jogamp 2014-03-04 20:23:18 +0100 Specifically, make-deploy-one.sh is being too conservative about which jar files it's picking up. It should probably be more brutal and just grab everything matching "${PROJECT}-${VERSION}-*.jar". 3821 1 org.jogamp 2014-03-04 20:23:43 +0100 Will start work on this immediately. 3822 2 org.jogamp 2014-03-04 22:04:15 +0100 Should be fixed in jogamp-scripting 7f28cc15004e143f77f7b90f8e543c16f84dcff0. 3823 3 org.jogamp 2014-03-04 22:06:49 +0100 I've ended up actually being more strict with it in some respects. The initial make-copy-jars.sh pass uses a list of atomics given in make-projects.txt and writes out a manifest file of every jar file included. The make-deploy-one.sh script then reads this manifest and uploads everything on it (as opposed to redoing some of the work of make-copy-jars.sh as it did before). 3834 4 org.jogamp 2014-03-06 12:21:00 +0100 Just waiting for the next aggregated build to check that everything is actually present.