Bug 991 - Some files are not being deployed by the maven scripts
Summary: Some files are not being deployed by the maven scripts
Status: RESOLVED FIXED
Alias: None
Product: General
Classification: JogAmp
Component: builds (show other bugs)
Version: unspecified
Hardware: All all
: --- enhancement
Assignee: Mark Raynsford
URL:
Depends on:
Blocks:
 
Reported: 2014-03-04 20:23 CET by Mark Raynsford
Modified: 2014-03-06 12:21 CET (History)
0 users

See Also:
Type: ---
SCM Refs:
7f28cc15004e143f77f7b90f8e543c16f84dcff0
Workaround: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Raynsford 2014-03-04 20:23:18 CET 
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".
Comment 1 Mark Raynsford 2014-03-04 20:23:43 CET 
Will start work on this immediately.
Comment 2 Mark Raynsford 2014-03-04 22:04:15 CET 
Should be fixed in jogamp-scripting 7f28cc15004e143f77f7b90f8e543c16f84dcff0.
Comment 3 Mark Raynsford 2014-03-04 22:06:49 CET 
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).
Comment 4 Mark Raynsford 2014-03-06 12:21:00 CET 
Just waiting for the next aggregated build to check that everything is actually present.