> -----Original Message-----
> From: James CE Johnson [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 3:28 PM
> To: [EMAIL PROTECTED]
> Subject: I clearly don't understand artifact:install
>
>
> In my maven.xml I do this:
>
> <artifact:install
> artifact="${maven.build.dir}/${maven.final.name}-client.jar"
> type="jar"
> project="${pom}"/>
>
> And maven does this:
>
> Copying: from
> '/home/jcej/projects/Extranet/PortfolioAnalytics/security/target/E
> xtranet-PortfolioAnalytics-Security-2.0-client.jar'
> to:
> '/home/jcej/tools/lib/Extranet/jars/Extranet-PortfolioAnalytics-Se
curity-2.0.jar'
>
> Why, oh why, did it drop the trailing '-client' bit from the filename?
>
Because such artifact cannot be downloaded from repository without using jar
override feature.
Repository path for any artifact is a function of: artifactId, groupId,
type, version
Every dependency of type "jar" should be named:
${groupId}/jars/${artifactId}-${version}.jar and is kept in directory named
"jars"
In your case the type is not really "jar" but something like "ejb-client"
and Maven should be able
to support such types.
The problem is that at the moment it does not and
Repository Layout Service which you can exists in maven-new and which I want
to use for configurable computation of paths is not yet ported to Maven.
So I will suggest you to use type "ejb-client" and wait in patient until it
is supported by maven.
java, javadoc, uberjar plugins have goals like "java:src-install",
"javadoc:install" are also producing stupidly named artifact like:
javadocs/foo-1.1.javadoc
srcs/foo-1.1.src
which I also want to change.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
