Turadg Aleahmad wrote:
I also added a maven.xml with some Maven build code and a LICENSE.txt
which the repository requires. Then I made this with "maven
create-upload-bundle".
http://tels.berkeley.edu/~turadg/sisc/sisc-1.9.1-alpha-bundle.jar
Turadg,
the jar appears to contains the contents of sisc.jar, sisc-opt.jar, and
the sisc.shp file. Is there any particular reason why this jar couldn't
have the same structure as a sisc release tar, i.e. contain
ChangeLog
COPYING
doc/
GOALS
install-srfi22.sh
README
scheme-src/
sisc
sisc.bat
sisc.jar
sisc-lib.jar
sisc-opt.jar
sisc.shp
TODO
?
I gather maven is adding the jars of declared dependencies to the class
path. So perhaps the difficulty with the above is that the jar contains
other jars/files rather than the classes themselves. How can we get
around that? Is there a way to create a bundle containing multiple jars?
Or perhaps each jar should be a different artifact? But then what should
happen to the non-jar artifacts like shell scripts?
Another thing I noticed is that your maven.xml duplicates an ant task
from build.xml. Is there any way that the maven.xml could just refer to
the ant task in build.xml? The instructions at
http://maven.apache.org/ant-guide/qna/antfarming.html
appear to suggest there is.
Matthias.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
|
