Hello, I am trying to specify non jar dependencies in my project.xml. I
was under the impression that any type of artifact could be listed as a
dependency similar to the following xml example:
<dependency>
<id>jboss-server</id>
<type>distributions</type>
<version>3.0.2</version>
<artifact>jboss-3.0.2.zip</artifact>
</dependency>
I have a remote repository setup with the following structure:
jboss-server/distributions/jboss-3.0.2.zip
Unfortunately, maven tries to download my dependency as:
jboss-server/jars/jboss-3.0.2.zip
Looking at the code impl for ProjectVerifier.verifyDependencies() I can
see why. It assumes all dependencies are a DefaultJarArtifact! Wouldn't a
more generic approach be to build the url by <id>/<type>/<artifact>?
I am a newbie user so maybe I just misunderstand the purpose of the
dependency element in a maven project.xml. I was hoping I could have maven
automatically download the jboss dist to the local repository so I can
write a goal to unpack the jboss dist, deploy, and test my project's ejbs.
Regards,
--mike
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
