You could package them all up and deploy them using assembly, and then use 
assembly or dependency to unpack them during the build. 

-----Original Message-----
From: Edwin Punzalan [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 20, 2006 3:57 AM
To: Maven Users List
Subject: Re: [m2] multiple project's component dependency declaration possible 
or too complex?


I think he means to use it at build time for mvn use.


dan tran wrote:

>how about create one big zip file?? then use antrun to unpack.
>
>I do that quite often
>
>-Dan
>
>
>
>On 1/19/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote:
>  
>
>>You mean you want a single pom to have several jars associated with it?
>>This doesn't comply with the one-artifact-one-jar philosophy of maven 
>>and so is not possible.
>>
>>Also, accdg to the maven gurus, such configuration you gave is 
>>possible as long as the each jar you set as a dep is placed in the 
>>repository
>>(read: placed properly in the repository accdg to 
>>groupId/artifacId/version).
>>
>>
>>
>>Loïc Lefèvre wrote:
>>
>>    
>>
>>>Hello,
>>>After some time struggling with my local repository I wonder if it's 
>>>me doing mistakes or if the declaration of multiple project's 
>>>components is too complex.
>>>
>>>Let's take my current example:
>>>
>>>In my local repository, I want to add LWJGL which is compound of 
>>>multiple jar, dll, so, dylib and jnilib files; a total of 30 files!
>>>
>>>What I whish to do is to declare my repository like that:
>>>
>>>[local repo directory]\lwjgl\lwjgl\0.99\all the files + metadata.xml
>>>+.pom + .md5 + .sha1
>>>
>>>In the pom (packaging pom) I could declare ALL the files required to 
>>>use LWJGL 0.99 using dependencies.
>>>
>>>And in my project pom.xml file I could just add:
>>>
>>>   <dependency>
>>>     <groupId>lwjgl</groupId>
>>>     <artifactId>lwjgl</artifactId>
>>>     <type>pom</type>
>>>     <version>0.99</version>
>>>   </dependency>
>>>
>>>so all the 30 files would directly be downloaded...
>>>
>>>Moreover, (see a recent mail) LWJGL's dll/so files don't include the 
>>>version number in their name so that Java code doesn't have to be 
>>>modified with new versions...
>>>
>>>Well is it a dream or is it possible?
>>>
>>>TIA,
>>>Loic
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>    
>>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to