Well, this is interesting. I ran into the issue of needing multiple build artifacts from a single project, and even though I theorized that this was not possible, no one either agreed or disagreed with me at that time. Now this posting agrees with my theory, and moreover, states that it is a basic philosophy of Maven.
Again, the problem is that in building an Eclipse plugin, I must have two artifacts: 1. The JAR containing the class files, so that other projects can depend upon the classes in this plugin. 2. A "meta-JAR" that contains the original JAR plus the plugin.xml file the Eclipse requires. This is needed to build an update site, and it must also be an artifact because the feature and update site builds must depend upon it. So, assuming that there is no way to have multiple JARs produced by a single project, then it will not be possible to create Eclipse features and update sites without resorting to hackery and not using the repository. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -----Original Message----- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Friday, January 20, 2006 2: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]
