Re: Maven dependency

Turadg Aleahmad wrote:

> Maven is "limited" (by design) to creating one artifact per project. 

I hear you. Let's not try to make Maven do things it wasn't designed for.

> But what's the real problem with how Maven is bundling it now?

That depends on what the purpose of the bundle is. See below ...

>> But then what should happen to the non-jar artifacts like shell scripts?
> 
> 
> 
> I don't think shell scripts are relevant for the Maven repository.  The 
> repository isn't a software distribution system; it's a canonical place 
> for getting JAR dependencies.  There's no Java code that depends on 
> sisc.sh.

If all you care about is Java compilation, why did you ask about 
sisc.shp? No Java code depends on it, so why is it in your bundle?

If otoh, you want to create projects that depend on sisc more generally, 
then there will typically not just have dependencies on the java classes 
but also the heap image, and the scheme libraries in sisc-lib.jar, and, 
conceivably but unlikely, the shell scripts.

Now, there is no harm in combining sisc.jar, sisc-lib.jar and 
sisc-opt.jar into a single jar for the bundle. However, sticking the 
heap image in that jar seems problematic. What use is a sisc.shp that is 
hidden away inside a jar? You can tell sisc to load the heap image from 
a file in a jar, but that's one of the least efficient ways of accessing 
the heap image since it precludes any lazy loading.


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