I believe this sentence explains how the relate: "All attached artifacts must differ from each other with unique classifiers." Brian's the author, so go for his response in this thread.
However, to be frank, I can't follow your use case completely. I think the confusing thing is that you seem to be using the term "plugin" in the context of "maven plugin" AND "geronimo plugin". Please remember that this is a Maven list, I don't know anything about how geronimo works. Only use the plugin term for maven plugins, everything else (geronimo plugins for instance) are artifacts. So trying to translate your following sentence: "We have to put the artifacts in the repository, as the goal is to create a plugin repository that contains many plugins and copy them to a remote repository so that other users can install these plugins from the remote repository." I think it should be: "We have to put the artifacts in the repository, as the goal is to create a geronimo plugin repository that contains many artifacts and copy them to a remote repository so that other users can install these geronimo plugins from the remote repository." If that's the case and you're the only one who will be creating the three artifacts I'd say that the maven way would be to have different artifactIds. They should share the same groupId, but have different artifactIds. This making things a little bit complicated for you is not a problem (well :-)), it will not impact the end users. However, if you're creating some generic maven plugin for doing this kind of thing that end geronimo users will be using, it MIGHT be a better solution going with classifiers. Even though it's not a "pure" maven solution. My two cents, /Anders Lin Sun-2 wrote: > > Yes, when reading the link you supplied, I could not differentiate the > difference between classifier and attached artifacts. Seems they are > both used for javadocs, sources, etc. We are proposing to use > classfiers to solve the probs we mentioned in the above posts but we > 'd like to get your feedback and maybe even a better solution. > > Thanks, > > Lin > > On Mon, Aug 18, 2008 at 10:19 AM, Anders Hammar <[EMAIL PROTECTED]> wrote: >> >> Is it attached artifacts we're talking about? >> http://blogs.sonatype.com/brian/2008/05/19/1211249747887.html >> >> /Anders >> >> >> Lin Sun-2 wrote: >>> >>> Hi, >>> >>> My understanding is yes the maven car plugin is just producing the >>> artifacts. We have to put the artifacts in the repository, as the >>> goal is to create a plugin repository that contains many plugins and >>> copy them to a remote repository so that other users can install these >>> plugins from the remote repository. >>> >>> Lin >>> >>> On Mon, Aug 18, 2008 at 7:51 AM, Anders Hammar <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> Hi, >>>> >>>> Is there a specific need to put the artifacts in the repository? If >>>> not, >>>> the >>>> plugin could produce the three car files and deploy (copy) them to the >>>> Geronimo server. The car files could be named pretty much what ever you >>>> like >>>> as groupId, artifactId and classifiers only matters in a repository. >>>> Nothing >>>> is put in local or remote repository. >>>> >>>> Or, is the car plugin just producing the artifacts and some other >>>> plugin >>>> is >>>> used to deploy them to Geronimo? >>>> >>>> /Anders >>> >> >> -- >> View this message in context: >> http://www.nabble.com/can-we-use-classifier-here--tp18950457p19032733.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/can-we-use-classifier-here--tp18950457p19063934.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
