Hi Sachin, It may be worth posting this to the Maven Users list, there are several folks that can help out there.
The problem here is that "plugin" is a reserved type for Maven plugins. Also note that / should not be valid in a groupId - they are meant to be identifiers, not path elements - and when converted to a different layout the / or .jar in artifactId would cause confusion. I'd suggest using a type = jar (which is the default). There is little advantage to having a separate type. I'd also suggest using groupId = org.eclipse.core, artifactId = org.eclipse.core.resources, version = 3.1.0. This will give you a filename almost what you want, except that _ will be replaced with -. This is just how Maven deals with its repository - you are able to rename the file when you reuse it in Eclipse after it has been downloaded. Hope this helps. Cheers, Brett On 8/29/05, Sachin Patel <[EMAIL PROTECTED]> wrote: > I'm playing around trying to declare a dependency on an eclipse plugin > purely using the <dependency> element. Theres are 2 problems in doing so... > > If I have the following.... > > <dependency> > <groupID>eclipse</groupID> > <artifactID>org.eclipse.core.resources</artifactID> > <version>3.1.0</version> > <type>plugin</type> > </dependency> > > This according to the documentation would resolve to > [REPO_ROOT]/eclipse/plugins/org.eclipse.core.resources-3.1.0.plugin > > rather then [REPO_ROOT]/eclipse/plugins/org.eclipse.core.resources_3.1.0.jar > > Notice the two differences, (1) where <type> will be used as the > extension rather then .jar, and (2) the version number for eclipse > plugins are appended with an underscore rather then a dash. > > Is the <type> element required? Can I just change groupID to > <groupID>eclipse/plugins</groupID> and then also remove the version > number and have the full artifact file name specified > <artifactID>org.eclipse.core.resources_3.1.0.jar</artifactID> ? > > Thanks. >
