Sorry, I'm a little confused by what you mean here. All I was
referring to was that jars with the same group, artifact ids and
version will end up in the same spot.
- Brett
On 10/28/05, Xavier Toth <[EMAIL PROTECTED]> wrote:
> No I don't simple want to copy the files. I'm trying to use install along
> with the artifact:dependencies task to reference the repository where I'm
> installing. When all the 'install's get the same groupd id and artifact id I
> end up with only one jar containing the contents of the last jar I
> installed. It doesn't seem like this is the intended behavior. What is the
> 'defined layout' you refer to?
>
> On 10/21/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> > The role of the repository is special to maven and the tasks, so it
> > uses the defined layout. If you simply need to copy the file to a
> > particular location, use a filesetId and <copy />
> >
> > Cheers,
> > Brett
> >
> > On 10/21/05, Xavier Toth <[EMAIL PROTECTED]> wrote:
> > > No matter the jar file name it installs a jar named apparently for the
> > > package name. It seem like the artifactId ought to be the original jar
> > file
> > > name and the groupId ought to be the package name.
> > >
> > > <artifact:install file="${build.jar.dir}/${jar.name <http://jar.name> <
> > http://jar.name>}">
> > > <pom refid="maven.project"/>
> > > </artifact:install>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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]
