You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ralph Pöllath <li...@poellath.org> on 2006/09/01 09:37:19 UTC
Re: [POLL] Why switch to Maven?
On 31.08.2006, at 23:27, ArneD wrote:
>> After all, if can't trust your team to stick to approved
>> versions of artifacts how can you trust them to write your precious
>> business code?
>
> I think it's not a question of mistrusting people, but a question
> of how can
> you help people to avoid mistakes. Even if they use a Maven-based
> build for
> the first time and don't have a M.Sc. in Computer Science or x
> years of
> experience.
>
> If the team *wants* to used unapproved versions of artifacts, of
> course,
> they will be able to do it. But you should help them to not do it by
> mistake.
FWIW, wouldn't it be simple to write a plugin that compares all
dependencies to a list of approved artifacts?
Cheers,
-Ralph.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: directory v. outputDirectory
Posted by dan tran <da...@gmail.com>.
you are always welcome to provide patch ;-)
1. svn repo
2 and 3 point to the same snapshot repository
-D
On 9/6/06, Jimisola Laursen <li...@jimisola.com> wrote:
>
>
> Hi!
>
> Asked in the #maven recently about the maven-dependency-plugin.
> There are a lot of reported issues, but there don't seem to be any
> development activity according to Jira's "Recently resolved". Does anyone
> here now?
> I have a particular interest in "Make (sure) dependency:resolve outputs
> absolute filename (or at least make it configurable)"
> (http://jira.codehaus.org/browse/MDEP-29) to allow us to use the plugin to
> create our installer.
> It might be that it already works that way, but I haven't been able to
> find
> 2.0-SNAPSHOT before.
>
> Also, may I ask about the difference in the two (2!) repos that have been
> mentioned and the people one:
>
> 1.
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-dependency-plugin/
> 2. http://people.apache.org/maven-snapshot-repository/
> 3. http://svn.apache.org/maven-snapshot-repository
>
> Regards,
> Jimisola
>
>
>
> dan tran wrote:
> >
> > a snapshot of this plugin is at
> >
> > http://people.apache.org/maven-snapshot-repository/
> >
> > you can build the plugin yourself as well.
> >
> > -D
> >
> >
> > On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
> >>
> >> Failed to resolve this artifact
> >>
> >> <groupId>org.apache.maven.plugins</groupId>
> >> <artifactId>maven-dependency-plugin</artifactId>
> >> <version>2.0-SNAPSHOT</version>
> >>
> >> Brad
> >>
> >> > -----Original Message-----
> >> > From: dan tran [mailto:dantran@gmail.com]
> >> > Sent: Tuesday, September 05, 2006 5:23 PM
> >> > To: Maven Users List
> >> > Subject: Re: directory v. outputDirectory
> >> >
> >> >
> >> > please note that depenency-maven-plugin has been accepted
> >> > into apache. It
> >> > is now at
> >> >
> >> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-depe
> >> > ndency-plugin/
> >> >
> >> > The more ppl using this new plugin, the more chance we can
> >> > get it released
> >> > ;-)
> >> >
> >> > -D
> >> >
> >> > On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
> >> > >
> >> > > org.codehaus.plugins:dependency-maven-plugin works.
> >> > >
> >> > > Thanks.
> >> > >
> >> > > Brad
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: dantran@gmail.com [mailto:dantran@gmail.com]
> >> > > > Sent: Tuesday, September 05, 2006 1:30 PM
> >> > > > To: Maven Users List
> >> > > > Subject: Re: directory v. outputDirectory
> >> > > >
> >> > > >
> >> > > > Brad, you can use a combination of assembly and dependency
> >> > > > plugin to copy
> >> > > > final built artfacts into a single
> >> > > > directory the way you want it it and have assembly to zip(
> >> > > > tgz, etc) them
> >> > > > up.
> >> > > >
> >> > > > Use a separate maven project for that purpose.
> >> > > >
> >> > > > -Dan
> >> > > >
> >> > > >
> >> > > > On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
> >> > > > >
> >> > > > > Can you define multiple source directories?
> >> > > > >
> >> > > > > I am guessing that transitive dependencies aren't
> >> > getting linked in?
> >> > > > >
> >> > > > > D-
> >> > > > >
> >> > > > > -----Original Message-----
> >> > > > > From: Brad Harper
> >> > > > > Sent: Tuesday, September 05, 2006 12:25 PM
> >> > > > > To: users
> >> > > > > Subject: RE: directory v. outputDirectory
> >> > > > >
> >> > > > > The libraries will be built as a mixture of .lib and
> >> > .dll files (on
> >> > > > > Windows)
> >> > > > > and .a and .so archives (on *nix platforms).
> >> > > > >
> >> > > > > Brad
> >> > > > >
> >> > > > > > -----Original Message-----
> >> > > > > > From: Douglas Ferguson
> >> > > > > > Sent: Tuesday, September 05, 2006 11:36 AM
> >> > > > > > To: users
> >> > > > > > Subject: RE: directory v. outputDirectory
> >> > > > > >
> >> > > > > >
> >> > > > > > What format must the archive be in?
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > -----Original Message-----
> >> > > > > > From: Brad Harper
> >> > > > > > Sent: Tuesday, September 05, 2006 10:02 AM
> >> > > > > > To: users
> >> > > > > > Subject: RE: directory v. outputDirectory
> >> > > > > >
> >> > > > > > Dan:
> >> > > > > >
> >> > > > > > My intent is to have copies of a set of archive libraries
> >> > > > collected
> >> > > > > > into a single directory. The libraries are sibling
> >> > > > modules of a parent
> >> > > > > > project.
> >> > > > > >
> >> > > > > > Each library could be copied into the target area as it
> >> > > > is built, or
> >> > > > > > the libraries could be copied (from their respective
> >> > > > projects) by the
> >> > > > > > parent project in a roll-up operation.
> >> > > > > >
> >> > > > > > I considered running the assembly plugin in the
> >> > parent project,
> >> > > > > > but the archive libraries cannot be in a
> >> > .zip/.tar/.tgz format.
> >> > > > > >
> >> > > > > > Brad
> >> > > > > >
> >> > > > > > > -----Original Message-----
> >> > > > > > > From: dan tran [mailto:dantran@gmail.com]
> >> > > > > > > Sent: Saturday, September 02, 2006 12:32 AM
> >> > > > > > > To: Maven Users List
> >> > > > > > > Subject: Re: directory v. outputDirectory
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > native-maven-plugin''s outputDirectory purposely set to
> >> > > > > > > readonly so that all
> >> > > > > > > outputs ( .o, .dll, etc) stay inside
> >> > > > > > > target directory. and mvn clean can clear them as well.
> >> > > > > > >
> >> > > > > > > Why do you want the output files outside of project?
> >> > > > > > perhaps there is
> >> > > > > > > another way to accomplish
> >> > > > > > > what you need after the build.
> >> > > > > > >
> >> > > > > > > -D
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > What's the difference between
> >> > > > > > > >
> >> > > > > > > > <build>
> >> > > > > > > > <directory>
> >> > > > > > > > <outputDirectory>
> >> > > > > > > > ...
> >> > > > > > > >
> >> > > > > > > > I'm using maven-native-plugin, which has identical
> >> > > > configuration
> >> > > > > > > > elements, but I'm prevented from using them, i.e.
> >> > > > > > > >
> >> > > > > > > > <build>
> >> > > > > > > > <plugins>
> >> > > > > > > > <plugin>
> >> > > > > > > > <configure>
> >> > > > > > > > <directory>
> >> > > > > > > > <outputDirectory>
> >> > > > > > > >
> >> > > > > > > > by errors complaining about over-written
> >> > read-only parameters.
> >> > > > > > > >
> >> > > > > > > > It would be OK if libraries (modules) were to build
> >> > > > in their own
> >> > > > > > > > target/ sub-directories, but I'd like to move a
> >> > copy of the
> >> > > > > > > resulting
> >> > > > > > > > libraries into a central location higher in the
> >> > > > project hierarchy.
> >> > > > > > > >
> >> > > > > > > > Brad
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > ---------------------------------------------------------------------
> >> > > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@maven.apache.org
> >> > > > > > > > For additional commands, e-mail:
> >> > users-help@maven.apache.org
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > >
> >> > ---------------------------------------------------------------------
> >> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > >
> >> > ---------------------------------------------------------------------
> >> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > ---------------------------------------------------------------------
> >> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > > > > For additional commands, e-mail: users-help@maven.apache.org
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > ---------------------------------------------------------------------
> >> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > > > > For additional commands, e-mail: users-help@maven.apache.org
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > > For additional commands, e-mail: users-help@maven.apache.org
> >> > >
> >> > >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/-POLL--Why-switch-to-Maven--tf2185174.html#a6180108
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: directory v. outputDirectory
Posted by Jimisola Laursen <li...@jimisola.com>.
Hi!
Asked in the #maven recently about the maven-dependency-plugin.
There are a lot of reported issues, but there don't seem to be any
development activity according to Jira's "Recently resolved". Does anyone
here now?
I have a particular interest in "Make (sure) dependency:resolve outputs
absolute filename (or at least make it configurable)"
(http://jira.codehaus.org/browse/MDEP-29) to allow us to use the plugin to
create our installer.
It might be that it already works that way, but I haven't been able to find
2.0-SNAPSHOT before.
Also, may I ask about the difference in the two (2!) repos that have been
mentioned and the people one:
1.
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-dependency-plugin/
2. http://people.apache.org/maven-snapshot-repository/
3. http://svn.apache.org/maven-snapshot-repository
Regards,
Jimisola
dan tran wrote:
>
> a snapshot of this plugin is at
>
> http://people.apache.org/maven-snapshot-repository/
>
> you can build the plugin yourself as well.
>
> -D
>
>
> On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
>>
>> Failed to resolve this artifact
>>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-dependency-plugin</artifactId>
>> <version>2.0-SNAPSHOT</version>
>>
>> Brad
>>
>> > -----Original Message-----
>> > From: dan tran [mailto:dantran@gmail.com]
>> > Sent: Tuesday, September 05, 2006 5:23 PM
>> > To: Maven Users List
>> > Subject: Re: directory v. outputDirectory
>> >
>> >
>> > please note that depenency-maven-plugin has been accepted
>> > into apache. It
>> > is now at
>> >
>> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-depe
>> > ndency-plugin/
>> >
>> > The more ppl using this new plugin, the more chance we can
>> > get it released
>> > ;-)
>> >
>> > -D
>> >
>> > On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
>> > >
>> > > org.codehaus.plugins:dependency-maven-plugin works.
>> > >
>> > > Thanks.
>> > >
>> > > Brad
>> > >
>> > > > -----Original Message-----
>> > > > From: dantran@gmail.com [mailto:dantran@gmail.com]
>> > > > Sent: Tuesday, September 05, 2006 1:30 PM
>> > > > To: Maven Users List
>> > > > Subject: Re: directory v. outputDirectory
>> > > >
>> > > >
>> > > > Brad, you can use a combination of assembly and dependency
>> > > > plugin to copy
>> > > > final built artfacts into a single
>> > > > directory the way you want it it and have assembly to zip(
>> > > > tgz, etc) them
>> > > > up.
>> > > >
>> > > > Use a separate maven project for that purpose.
>> > > >
>> > > > -Dan
>> > > >
>> > > >
>> > > > On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
>> > > > >
>> > > > > Can you define multiple source directories?
>> > > > >
>> > > > > I am guessing that transitive dependencies aren't
>> > getting linked in?
>> > > > >
>> > > > > D-
>> > > > >
>> > > > > -----Original Message-----
>> > > > > From: Brad Harper
>> > > > > Sent: Tuesday, September 05, 2006 12:25 PM
>> > > > > To: users
>> > > > > Subject: RE: directory v. outputDirectory
>> > > > >
>> > > > > The libraries will be built as a mixture of .lib and
>> > .dll files (on
>> > > > > Windows)
>> > > > > and .a and .so archives (on *nix platforms).
>> > > > >
>> > > > > Brad
>> > > > >
>> > > > > > -----Original Message-----
>> > > > > > From: Douglas Ferguson
>> > > > > > Sent: Tuesday, September 05, 2006 11:36 AM
>> > > > > > To: users
>> > > > > > Subject: RE: directory v. outputDirectory
>> > > > > >
>> > > > > >
>> > > > > > What format must the archive be in?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > -----Original Message-----
>> > > > > > From: Brad Harper
>> > > > > > Sent: Tuesday, September 05, 2006 10:02 AM
>> > > > > > To: users
>> > > > > > Subject: RE: directory v. outputDirectory
>> > > > > >
>> > > > > > Dan:
>> > > > > >
>> > > > > > My intent is to have copies of a set of archive libraries
>> > > > collected
>> > > > > > into a single directory. The libraries are sibling
>> > > > modules of a parent
>> > > > > > project.
>> > > > > >
>> > > > > > Each library could be copied into the target area as it
>> > > > is built, or
>> > > > > > the libraries could be copied (from their respective
>> > > > projects) by the
>> > > > > > parent project in a roll-up operation.
>> > > > > >
>> > > > > > I considered running the assembly plugin in the
>> > parent project,
>> > > > > > but the archive libraries cannot be in a
>> > .zip/.tar/.tgz format.
>> > > > > >
>> > > > > > Brad
>> > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: dan tran [mailto:dantran@gmail.com]
>> > > > > > > Sent: Saturday, September 02, 2006 12:32 AM
>> > > > > > > To: Maven Users List
>> > > > > > > Subject: Re: directory v. outputDirectory
>> > > > > > >
>> > > > > > >
>> > > > > > > native-maven-plugin''s outputDirectory purposely set to
>> > > > > > > readonly so that all
>> > > > > > > outputs ( .o, .dll, etc) stay inside
>> > > > > > > target directory. and mvn clean can clear them as well.
>> > > > > > >
>> > > > > > > Why do you want the output files outside of project?
>> > > > > > perhaps there is
>> > > > > > > another way to accomplish
>> > > > > > > what you need after the build.
>> > > > > > >
>> > > > > > > -D
>> > > > > > >
>> > > > > > >
>> > > > > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > What's the difference between
>> > > > > > > >
>> > > > > > > > <build>
>> > > > > > > > <directory>
>> > > > > > > > <outputDirectory>
>> > > > > > > > ...
>> > > > > > > >
>> > > > > > > > I'm using maven-native-plugin, which has identical
>> > > > configuration
>> > > > > > > > elements, but I'm prevented from using them, i.e.
>> > > > > > > >
>> > > > > > > > <build>
>> > > > > > > > <plugins>
>> > > > > > > > <plugin>
>> > > > > > > > <configure>
>> > > > > > > > <directory>
>> > > > > > > > <outputDirectory>
>> > > > > > > >
>> > > > > > > > by errors complaining about over-written
>> > read-only parameters.
>> > > > > > > >
>> > > > > > > > It would be OK if libraries (modules) were to build
>> > > > in their own
>> > > > > > > > target/ sub-directories, but I'd like to move a
>> > copy of the
>> > > > > > > resulting
>> > > > > > > > libraries into a central location higher in the
>> > > > project hierarchy.
>> > > > > > > >
>> > > > > > > > Brad
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > >
>> > ---------------------------------------------------------------------
>> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > > > > > > For additional commands, e-mail:
>> > users-help@maven.apache.org
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > >
>> > ---------------------------------------------------------------------
>> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > > > > For additional commands, e-mail: users-help@maven.apache.org
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > >
>> > ---------------------------------------------------------------------
>> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > > > > For additional commands, e-mail: users-help@maven.apache.org
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > > > For additional commands, e-mail: users-help@maven.apache.org
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > > > For additional commands, e-mail: users-help@maven.apache.org
>> > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: users-help@maven.apache.org
>> > >
>> > >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-POLL--Why-switch-to-Maven--tf2185174.html#a6180108
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: directory v. outputDirectory
Posted by dan tran <da...@gmail.com>.
a snapshot of this plugin is at
http://people.apache.org/maven-snapshot-repository/
you can build the plugin yourself as well.
-D
On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
>
> Failed to resolve this artifact
>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <version>2.0-SNAPSHOT</version>
>
> Brad
>
> > -----Original Message-----
> > From: dan tran [mailto:dantran@gmail.com]
> > Sent: Tuesday, September 05, 2006 5:23 PM
> > To: Maven Users List
> > Subject: Re: directory v. outputDirectory
> >
> >
> > please note that depenency-maven-plugin has been accepted
> > into apache. It
> > is now at
> >
> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-depe
> > ndency-plugin/
> >
> > The more ppl using this new plugin, the more chance we can
> > get it released
> > ;-)
> >
> > -D
> >
> > On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
> > >
> > > org.codehaus.plugins:dependency-maven-plugin works.
> > >
> > > Thanks.
> > >
> > > Brad
> > >
> > > > -----Original Message-----
> > > > From: dantran@gmail.com [mailto:dantran@gmail.com]
> > > > Sent: Tuesday, September 05, 2006 1:30 PM
> > > > To: Maven Users List
> > > > Subject: Re: directory v. outputDirectory
> > > >
> > > >
> > > > Brad, you can use a combination of assembly and dependency
> > > > plugin to copy
> > > > final built artfacts into a single
> > > > directory the way you want it it and have assembly to zip(
> > > > tgz, etc) them
> > > > up.
> > > >
> > > > Use a separate maven project for that purpose.
> > > >
> > > > -Dan
> > > >
> > > >
> > > > On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
> > > > >
> > > > > Can you define multiple source directories?
> > > > >
> > > > > I am guessing that transitive dependencies aren't
> > getting linked in?
> > > > >
> > > > > D-
> > > > >
> > > > > -----Original Message-----
> > > > > From: Brad Harper
> > > > > Sent: Tuesday, September 05, 2006 12:25 PM
> > > > > To: users
> > > > > Subject: RE: directory v. outputDirectory
> > > > >
> > > > > The libraries will be built as a mixture of .lib and
> > .dll files (on
> > > > > Windows)
> > > > > and .a and .so archives (on *nix platforms).
> > > > >
> > > > > Brad
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Douglas Ferguson
> > > > > > Sent: Tuesday, September 05, 2006 11:36 AM
> > > > > > To: users
> > > > > > Subject: RE: directory v. outputDirectory
> > > > > >
> > > > > >
> > > > > > What format must the archive be in?
> > > > > >
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brad Harper
> > > > > > Sent: Tuesday, September 05, 2006 10:02 AM
> > > > > > To: users
> > > > > > Subject: RE: directory v. outputDirectory
> > > > > >
> > > > > > Dan:
> > > > > >
> > > > > > My intent is to have copies of a set of archive libraries
> > > > collected
> > > > > > into a single directory. The libraries are sibling
> > > > modules of a parent
> > > > > > project.
> > > > > >
> > > > > > Each library could be copied into the target area as it
> > > > is built, or
> > > > > > the libraries could be copied (from their respective
> > > > projects) by the
> > > > > > parent project in a roll-up operation.
> > > > > >
> > > > > > I considered running the assembly plugin in the
> > parent project,
> > > > > > but the archive libraries cannot be in a
> > .zip/.tar/.tgz format.
> > > > > >
> > > > > > Brad
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: dan tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Saturday, September 02, 2006 12:32 AM
> > > > > > > To: Maven Users List
> > > > > > > Subject: Re: directory v. outputDirectory
> > > > > > >
> > > > > > >
> > > > > > > native-maven-plugin''s outputDirectory purposely set to
> > > > > > > readonly so that all
> > > > > > > outputs ( .o, .dll, etc) stay inside
> > > > > > > target directory. and mvn clean can clear them as well.
> > > > > > >
> > > > > > > Why do you want the output files outside of project?
> > > > > > perhaps there is
> > > > > > > another way to accomplish
> > > > > > > what you need after the build.
> > > > > > >
> > > > > > > -D
> > > > > > >
> > > > > > >
> > > > > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > What's the difference between
> > > > > > > >
> > > > > > > > <build>
> > > > > > > > <directory>
> > > > > > > > <outputDirectory>
> > > > > > > > ...
> > > > > > > >
> > > > > > > > I'm using maven-native-plugin, which has identical
> > > > configuration
> > > > > > > > elements, but I'm prevented from using them, i.e.
> > > > > > > >
> > > > > > > > <build>
> > > > > > > > <plugins>
> > > > > > > > <plugin>
> > > > > > > > <configure>
> > > > > > > > <directory>
> > > > > > > > <outputDirectory>
> > > > > > > >
> > > > > > > > by errors complaining about over-written
> > read-only parameters.
> > > > > > > >
> > > > > > > > It would be OK if libraries (modules) were to build
> > > > in their own
> > > > > > > > target/ sub-directories, but I'd like to move a
> > copy of the
> > > > > > > resulting
> > > > > > > > libraries into a central location higher in the
> > > > project hierarchy.
> > > > > > > >
> > > > > > > > Brad
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > > For additional commands, e-mail:
> > users-help@maven.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: directory v. outputDirectory
Posted by Brad Harper <br...@epsiia.com>.
Failed to resolve this artifact
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
Brad
> -----Original Message-----
> From: dan tran [mailto:dantran@gmail.com]
> Sent: Tuesday, September 05, 2006 5:23 PM
> To: Maven Users List
> Subject: Re: directory v. outputDirectory
>
>
> please note that depenency-maven-plugin has been accepted
> into apache. It
> is now at
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-depe
> ndency-plugin/
>
> The more ppl using this new plugin, the more chance we can
> get it released
> ;-)
>
> -D
>
> On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
> >
> > org.codehaus.plugins:dependency-maven-plugin works.
> >
> > Thanks.
> >
> > Brad
> >
> > > -----Original Message-----
> > > From: dantran@gmail.com [mailto:dantran@gmail.com]
> > > Sent: Tuesday, September 05, 2006 1:30 PM
> > > To: Maven Users List
> > > Subject: Re: directory v. outputDirectory
> > >
> > >
> > > Brad, you can use a combination of assembly and dependency
> > > plugin to copy
> > > final built artfacts into a single
> > > directory the way you want it it and have assembly to zip(
> > > tgz, etc) them
> > > up.
> > >
> > > Use a separate maven project for that purpose.
> > >
> > > -Dan
> > >
> > >
> > > On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
> > > >
> > > > Can you define multiple source directories?
> > > >
> > > > I am guessing that transitive dependencies aren't
> getting linked in?
> > > >
> > > > D-
> > > >
> > > > -----Original Message-----
> > > > From: Brad Harper
> > > > Sent: Tuesday, September 05, 2006 12:25 PM
> > > > To: users
> > > > Subject: RE: directory v. outputDirectory
> > > >
> > > > The libraries will be built as a mixture of .lib and
> .dll files (on
> > > > Windows)
> > > > and .a and .so archives (on *nix platforms).
> > > >
> > > > Brad
> > > >
> > > > > -----Original Message-----
> > > > > From: Douglas Ferguson
> > > > > Sent: Tuesday, September 05, 2006 11:36 AM
> > > > > To: users
> > > > > Subject: RE: directory v. outputDirectory
> > > > >
> > > > >
> > > > > What format must the archive be in?
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Brad Harper
> > > > > Sent: Tuesday, September 05, 2006 10:02 AM
> > > > > To: users
> > > > > Subject: RE: directory v. outputDirectory
> > > > >
> > > > > Dan:
> > > > >
> > > > > My intent is to have copies of a set of archive libraries
> > > collected
> > > > > into a single directory. The libraries are sibling
> > > modules of a parent
> > > > > project.
> > > > >
> > > > > Each library could be copied into the target area as it
> > > is built, or
> > > > > the libraries could be copied (from their respective
> > > projects) by the
> > > > > parent project in a roll-up operation.
> > > > >
> > > > > I considered running the assembly plugin in the
> parent project,
> > > > > but the archive libraries cannot be in a
> .zip/.tar/.tgz format.
> > > > >
> > > > > Brad
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: dan tran [mailto:dantran@gmail.com]
> > > > > > Sent: Saturday, September 02, 2006 12:32 AM
> > > > > > To: Maven Users List
> > > > > > Subject: Re: directory v. outputDirectory
> > > > > >
> > > > > >
> > > > > > native-maven-plugin''s outputDirectory purposely set to
> > > > > > readonly so that all
> > > > > > outputs ( .o, .dll, etc) stay inside
> > > > > > target directory. and mvn clean can clear them as well.
> > > > > >
> > > > > > Why do you want the output files outside of project?
> > > > > perhaps there is
> > > > > > another way to accomplish
> > > > > > what you need after the build.
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > > > > > >
> > > > > > >
> > > > > > > What's the difference between
> > > > > > >
> > > > > > > <build>
> > > > > > > <directory>
> > > > > > > <outputDirectory>
> > > > > > > ...
> > > > > > >
> > > > > > > I'm using maven-native-plugin, which has identical
> > > configuration
> > > > > > > elements, but I'm prevented from using them, i.e.
> > > > > > >
> > > > > > > <build>
> > > > > > > <plugins>
> > > > > > > <plugin>
> > > > > > > <configure>
> > > > > > > <directory>
> > > > > > > <outputDirectory>
> > > > > > >
> > > > > > > by errors complaining about over-written
> read-only parameters.
> > > > > > >
> > > > > > > It would be OK if libraries (modules) were to build
> > > in their own
> > > > > > > target/ sub-directories, but I'd like to move a
> copy of the
> > > > > > resulting
> > > > > > > libraries into a central location higher in the
> > > project hierarchy.
> > > > > > >
> > > > > > > Brad
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: directory v. outputDirectory
Posted by dan tran <da...@gmail.com>.
please note that depenency-maven-plugin has been accepted into apache. It
is now at
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-dependency-plugin/
The more ppl using this new plugin, the more chance we can get it released
;-)
-D
On 9/5/06, Brad Harper <br...@epsiia.com> wrote:
>
> org.codehaus.plugins:dependency-maven-plugin works.
>
> Thanks.
>
> Brad
>
> > -----Original Message-----
> > From: dantran@gmail.com [mailto:dantran@gmail.com]
> > Sent: Tuesday, September 05, 2006 1:30 PM
> > To: Maven Users List
> > Subject: Re: directory v. outputDirectory
> >
> >
> > Brad, you can use a combination of assembly and dependency
> > plugin to copy
> > final built artfacts into a single
> > directory the way you want it it and have assembly to zip(
> > tgz, etc) them
> > up.
> >
> > Use a separate maven project for that purpose.
> >
> > -Dan
> >
> >
> > On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
> > >
> > > Can you define multiple source directories?
> > >
> > > I am guessing that transitive dependencies aren't getting linked in?
> > >
> > > D-
> > >
> > > -----Original Message-----
> > > From: Brad Harper
> > > Sent: Tuesday, September 05, 2006 12:25 PM
> > > To: users
> > > Subject: RE: directory v. outputDirectory
> > >
> > > The libraries will be built as a mixture of .lib and .dll files (on
> > > Windows)
> > > and .a and .so archives (on *nix platforms).
> > >
> > > Brad
> > >
> > > > -----Original Message-----
> > > > From: Douglas Ferguson
> > > > Sent: Tuesday, September 05, 2006 11:36 AM
> > > > To: users
> > > > Subject: RE: directory v. outputDirectory
> > > >
> > > >
> > > > What format must the archive be in?
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Brad Harper
> > > > Sent: Tuesday, September 05, 2006 10:02 AM
> > > > To: users
> > > > Subject: RE: directory v. outputDirectory
> > > >
> > > > Dan:
> > > >
> > > > My intent is to have copies of a set of archive libraries
> > collected
> > > > into a single directory. The libraries are sibling
> > modules of a parent
> > > > project.
> > > >
> > > > Each library could be copied into the target area as it
> > is built, or
> > > > the libraries could be copied (from their respective
> > projects) by the
> > > > parent project in a roll-up operation.
> > > >
> > > > I considered running the assembly plugin in the parent project,
> > > > but the archive libraries cannot be in a .zip/.tar/.tgz format.
> > > >
> > > > Brad
> > > >
> > > > > -----Original Message-----
> > > > > From: dan tran [mailto:dantran@gmail.com]
> > > > > Sent: Saturday, September 02, 2006 12:32 AM
> > > > > To: Maven Users List
> > > > > Subject: Re: directory v. outputDirectory
> > > > >
> > > > >
> > > > > native-maven-plugin''s outputDirectory purposely set to
> > > > > readonly so that all
> > > > > outputs ( .o, .dll, etc) stay inside
> > > > > target directory. and mvn clean can clear them as well.
> > > > >
> > > > > Why do you want the output files outside of project?
> > > > perhaps there is
> > > > > another way to accomplish
> > > > > what you need after the build.
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > > > > >
> > > > > >
> > > > > > What's the difference between
> > > > > >
> > > > > > <build>
> > > > > > <directory>
> > > > > > <outputDirectory>
> > > > > > ...
> > > > > >
> > > > > > I'm using maven-native-plugin, which has identical
> > configuration
> > > > > > elements, but I'm prevented from using them, i.e.
> > > > > >
> > > > > > <build>
> > > > > > <plugins>
> > > > > > <plugin>
> > > > > > <configure>
> > > > > > <directory>
> > > > > > <outputDirectory>
> > > > > >
> > > > > > by errors complaining about over-written read-only parameters.
> > > > > >
> > > > > > It would be OK if libraries (modules) were to build
> > in their own
> > > > > > target/ sub-directories, but I'd like to move a copy of the
> > > > > resulting
> > > > > > libraries into a central location higher in the
> > project hierarchy.
> > > > > >
> > > > > > Brad
> > > > > >
> > > > > >
> > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: directory v. outputDirectory
Posted by Brad Harper <br...@epsiia.com>.
org.codehaus.plugins:dependency-maven-plugin works.
Thanks.
Brad
> -----Original Message-----
> From: dantran@gmail.com [mailto:dantran@gmail.com]
> Sent: Tuesday, September 05, 2006 1:30 PM
> To: Maven Users List
> Subject: Re: directory v. outputDirectory
>
>
> Brad, you can use a combination of assembly and dependency
> plugin to copy
> final built artfacts into a single
> directory the way you want it it and have assembly to zip(
> tgz, etc) them
> up.
>
> Use a separate maven project for that purpose.
>
> -Dan
>
>
> On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
> >
> > Can you define multiple source directories?
> >
> > I am guessing that transitive dependencies aren't getting linked in?
> >
> > D-
> >
> > -----Original Message-----
> > From: Brad Harper
> > Sent: Tuesday, September 05, 2006 12:25 PM
> > To: users
> > Subject: RE: directory v. outputDirectory
> >
> > The libraries will be built as a mixture of .lib and .dll files (on
> > Windows)
> > and .a and .so archives (on *nix platforms).
> >
> > Brad
> >
> > > -----Original Message-----
> > > From: Douglas Ferguson
> > > Sent: Tuesday, September 05, 2006 11:36 AM
> > > To: users
> > > Subject: RE: directory v. outputDirectory
> > >
> > >
> > > What format must the archive be in?
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Brad Harper
> > > Sent: Tuesday, September 05, 2006 10:02 AM
> > > To: users
> > > Subject: RE: directory v. outputDirectory
> > >
> > > Dan:
> > >
> > > My intent is to have copies of a set of archive libraries
> collected
> > > into a single directory. The libraries are sibling
> modules of a parent
> > > project.
> > >
> > > Each library could be copied into the target area as it
> is built, or
> > > the libraries could be copied (from their respective
> projects) by the
> > > parent project in a roll-up operation.
> > >
> > > I considered running the assembly plugin in the parent project,
> > > but the archive libraries cannot be in a .zip/.tar/.tgz format.
> > >
> > > Brad
> > >
> > > > -----Original Message-----
> > > > From: dan tran [mailto:dantran@gmail.com]
> > > > Sent: Saturday, September 02, 2006 12:32 AM
> > > > To: Maven Users List
> > > > Subject: Re: directory v. outputDirectory
> > > >
> > > >
> > > > native-maven-plugin''s outputDirectory purposely set to
> > > > readonly so that all
> > > > outputs ( .o, .dll, etc) stay inside
> > > > target directory. and mvn clean can clear them as well.
> > > >
> > > > Why do you want the output files outside of project?
> > > perhaps there is
> > > > another way to accomplish
> > > > what you need after the build.
> > > >
> > > > -D
> > > >
> > > >
> > > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > > > >
> > > > >
> > > > > What's the difference between
> > > > >
> > > > > <build>
> > > > > <directory>
> > > > > <outputDirectory>
> > > > > ...
> > > > >
> > > > > I'm using maven-native-plugin, which has identical
> configuration
> > > > > elements, but I'm prevented from using them, i.e.
> > > > >
> > > > > <build>
> > > > > <plugins>
> > > > > <plugin>
> > > > > <configure>
> > > > > <directory>
> > > > > <outputDirectory>
> > > > >
> > > > > by errors complaining about over-written read-only parameters.
> > > > >
> > > > > It would be OK if libraries (modules) were to build
> in their own
> > > > > target/ sub-directories, but I'd like to move a copy of the
> > > > resulting
> > > > > libraries into a central location higher in the
> project hierarchy.
> > > > >
> > > > > Brad
> > > > >
> > > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: directory v. outputDirectory
Posted by dan tran <da...@gmail.com>.
Brad, you can use a combination of assembly and dependency plugin to copy
final built artfacts into a single
directory the way you want it it and have assembly to zip( tgz, etc) them
up.
Use a separate maven project for that purpose.
-Dan
On 9/5/06, Douglas Ferguson <do...@epsiia.com> wrote:
>
> Can you define multiple source directories?
>
> I am guessing that transitive dependencies aren't getting linked in?
>
> D-
>
> -----Original Message-----
> From: Brad Harper
> Sent: Tuesday, September 05, 2006 12:25 PM
> To: users
> Subject: RE: directory v. outputDirectory
>
> The libraries will be built as a mixture of .lib and .dll files (on
> Windows)
> and .a and .so archives (on *nix platforms).
>
> Brad
>
> > -----Original Message-----
> > From: Douglas Ferguson
> > Sent: Tuesday, September 05, 2006 11:36 AM
> > To: users
> > Subject: RE: directory v. outputDirectory
> >
> >
> > What format must the archive be in?
> >
> >
> >
> > -----Original Message-----
> > From: Brad Harper
> > Sent: Tuesday, September 05, 2006 10:02 AM
> > To: users
> > Subject: RE: directory v. outputDirectory
> >
> > Dan:
> >
> > My intent is to have copies of a set of archive libraries collected
> > into a single directory. The libraries are sibling modules of a parent
> > project.
> >
> > Each library could be copied into the target area as it is built, or
> > the libraries could be copied (from their respective projects) by the
> > parent project in a roll-up operation.
> >
> > I considered running the assembly plugin in the parent project,
> > but the archive libraries cannot be in a .zip/.tar/.tgz format.
> >
> > Brad
> >
> > > -----Original Message-----
> > > From: dan tran [mailto:dantran@gmail.com]
> > > Sent: Saturday, September 02, 2006 12:32 AM
> > > To: Maven Users List
> > > Subject: Re: directory v. outputDirectory
> > >
> > >
> > > native-maven-plugin''s outputDirectory purposely set to
> > > readonly so that all
> > > outputs ( .o, .dll, etc) stay inside
> > > target directory. and mvn clean can clear them as well.
> > >
> > > Why do you want the output files outside of project?
> > perhaps there is
> > > another way to accomplish
> > > what you need after the build.
> > >
> > > -D
> > >
> > >
> > > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > > >
> > > >
> > > > What's the difference between
> > > >
> > > > <build>
> > > > <directory>
> > > > <outputDirectory>
> > > > ...
> > > >
> > > > I'm using maven-native-plugin, which has identical configuration
> > > > elements, but I'm prevented from using them, i.e.
> > > >
> > > > <build>
> > > > <plugins>
> > > > <plugin>
> > > > <configure>
> > > > <directory>
> > > > <outputDirectory>
> > > >
> > > > by errors complaining about over-written read-only parameters.
> > > >
> > > > It would be OK if libraries (modules) were to build in their own
> > > > target/ sub-directories, but I'd like to move a copy of the
> > > resulting
> > > > libraries into a central location higher in the project hierarchy.
> > > >
> > > > Brad
> > > >
> > > >
> > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: directory v. outputDirectory
Posted by Douglas Ferguson <do...@epsiia.com>.
Can you define multiple source directories?
I am guessing that transitive dependencies aren't getting linked in?
D-
-----Original Message-----
From: Brad Harper
Sent: Tuesday, September 05, 2006 12:25 PM
To: users
Subject: RE: directory v. outputDirectory
The libraries will be built as a mixture of .lib and .dll files (on Windows)
and .a and .so archives (on *nix platforms).
Brad
> -----Original Message-----
> From: Douglas Ferguson
> Sent: Tuesday, September 05, 2006 11:36 AM
> To: users
> Subject: RE: directory v. outputDirectory
>
>
> What format must the archive be in?
>
>
>
> -----Original Message-----
> From: Brad Harper
> Sent: Tuesday, September 05, 2006 10:02 AM
> To: users
> Subject: RE: directory v. outputDirectory
>
> Dan:
>
> My intent is to have copies of a set of archive libraries collected
> into a single directory. The libraries are sibling modules of a parent
> project.
>
> Each library could be copied into the target area as it is built, or
> the libraries could be copied (from their respective projects) by the
> parent project in a roll-up operation.
>
> I considered running the assembly plugin in the parent project,
> but the archive libraries cannot be in a .zip/.tar/.tgz format.
>
> Brad
>
> > -----Original Message-----
> > From: dan tran [mailto:dantran@gmail.com]
> > Sent: Saturday, September 02, 2006 12:32 AM
> > To: Maven Users List
> > Subject: Re: directory v. outputDirectory
> >
> >
> > native-maven-plugin''s outputDirectory purposely set to
> > readonly so that all
> > outputs ( .o, .dll, etc) stay inside
> > target directory. and mvn clean can clear them as well.
> >
> > Why do you want the output files outside of project?
> perhaps there is
> > another way to accomplish
> > what you need after the build.
> >
> > -D
> >
> >
> > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > >
> > >
> > > What's the difference between
> > >
> > > <build>
> > > <directory>
> > > <outputDirectory>
> > > ...
> > >
> > > I'm using maven-native-plugin, which has identical configuration
> > > elements, but I'm prevented from using them, i.e.
> > >
> > > <build>
> > > <plugins>
> > > <plugin>
> > > <configure>
> > > <directory>
> > > <outputDirectory>
> > >
> > > by errors complaining about over-written read-only parameters.
> > >
> > > It would be OK if libraries (modules) were to build in their own
> > > target/ sub-directories, but I'd like to move a copy of the
> > resulting
> > > libraries into a central location higher in the project hierarchy.
> > >
> > > Brad
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: directory v. outputDirectory
Posted by Brad Harper <br...@epsiia.com>.
The libraries will be built as a mixture of .lib and .dll files (on Windows)
and .a and .so archives (on *nix platforms).
Brad
> -----Original Message-----
> From: Douglas Ferguson
> Sent: Tuesday, September 05, 2006 11:36 AM
> To: users
> Subject: RE: directory v. outputDirectory
>
>
> What format must the archive be in?
>
>
>
> -----Original Message-----
> From: Brad Harper
> Sent: Tuesday, September 05, 2006 10:02 AM
> To: users
> Subject: RE: directory v. outputDirectory
>
> Dan:
>
> My intent is to have copies of a set of archive libraries collected
> into a single directory. The libraries are sibling modules of a parent
> project.
>
> Each library could be copied into the target area as it is built, or
> the libraries could be copied (from their respective projects) by the
> parent project in a roll-up operation.
>
> I considered running the assembly plugin in the parent project,
> but the archive libraries cannot be in a .zip/.tar/.tgz format.
>
> Brad
>
> > -----Original Message-----
> > From: dan tran [mailto:dantran@gmail.com]
> > Sent: Saturday, September 02, 2006 12:32 AM
> > To: Maven Users List
> > Subject: Re: directory v. outputDirectory
> >
> >
> > native-maven-plugin''s outputDirectory purposely set to
> > readonly so that all
> > outputs ( .o, .dll, etc) stay inside
> > target directory. and mvn clean can clear them as well.
> >
> > Why do you want the output files outside of project?
> perhaps there is
> > another way to accomplish
> > what you need after the build.
> >
> > -D
> >
> >
> > On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> > >
> > >
> > > What's the difference between
> > >
> > > <build>
> > > <directory>
> > > <outputDirectory>
> > > ...
> > >
> > > I'm using maven-native-plugin, which has identical configuration
> > > elements, but I'm prevented from using them, i.e.
> > >
> > > <build>
> > > <plugins>
> > > <plugin>
> > > <configure>
> > > <directory>
> > > <outputDirectory>
> > >
> > > by errors complaining about over-written read-only parameters.
> > >
> > > It would be OK if libraries (modules) were to build in their own
> > > target/ sub-directories, but I'd like to move a copy of the
> > resulting
> > > libraries into a central location higher in the project hierarchy.
> > >
> > > Brad
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: directory v. outputDirectory
Posted by Douglas Ferguson <do...@epsiia.com>.
What format must the archive be in?
-----Original Message-----
From: Brad Harper
Sent: Tuesday, September 05, 2006 10:02 AM
To: users
Subject: RE: directory v. outputDirectory
Dan:
My intent is to have copies of a set of archive libraries collected
into a single directory. The libraries are sibling modules of a parent
project.
Each library could be copied into the target area as it is built, or
the libraries could be copied (from their respective projects) by the
parent project in a roll-up operation.
I considered running the assembly plugin in the parent project,
but the archive libraries cannot be in a .zip/.tar/.tgz format.
Brad
> -----Original Message-----
> From: dan tran [mailto:dantran@gmail.com]
> Sent: Saturday, September 02, 2006 12:32 AM
> To: Maven Users List
> Subject: Re: directory v. outputDirectory
>
>
> native-maven-plugin''s outputDirectory purposely set to
> readonly so that all
> outputs ( .o, .dll, etc) stay inside
> target directory. and mvn clean can clear them as well.
>
> Why do you want the output files outside of project? perhaps there is
> another way to accomplish
> what you need after the build.
>
> -D
>
>
> On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> >
> >
> > What's the difference between
> >
> > <build>
> > <directory>
> > <outputDirectory>
> > ...
> >
> > I'm using maven-native-plugin, which has identical configuration
> > elements, but I'm prevented from using them, i.e.
> >
> > <build>
> > <plugins>
> > <plugin>
> > <configure>
> > <directory>
> > <outputDirectory>
> >
> > by errors complaining about over-written read-only parameters.
> >
> > It would be OK if libraries (modules) were to build in their own
> > target/ sub-directories, but I'd like to move a copy of the
> resulting
> > libraries into a central location higher in the project hierarchy.
> >
> > Brad
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: directory v. outputDirectory
Posted by Brad Harper <br...@epsiia.com>.
Dan:
My intent is to have copies of a set of archive libraries collected
into a single directory. The libraries are sibling modules of a parent
project.
Each library could be copied into the target area as it is built, or
the libraries could be copied (from their respective projects) by the
parent project in a roll-up operation.
I considered running the assembly plugin in the parent project,
but the archive libraries cannot be in a .zip/.tar/.tgz format.
Brad
> -----Original Message-----
> From: dan tran [mailto:dantran@gmail.com]
> Sent: Saturday, September 02, 2006 12:32 AM
> To: Maven Users List
> Subject: Re: directory v. outputDirectory
>
>
> native-maven-plugin''s outputDirectory purposely set to
> readonly so that all
> outputs ( .o, .dll, etc) stay inside
> target directory. and mvn clean can clear them as well.
>
> Why do you want the output files outside of project? perhaps there is
> another way to accomplish
> what you need after the build.
>
> -D
>
>
> On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
> >
> >
> > What's the difference between
> >
> > <build>
> > <directory>
> > <outputDirectory>
> > ...
> >
> > I'm using maven-native-plugin, which has identical configuration
> > elements, but I'm prevented from using them, i.e.
> >
> > <build>
> > <plugins>
> > <plugin>
> > <configure>
> > <directory>
> > <outputDirectory>
> >
> > by errors complaining about over-written read-only parameters.
> >
> > It would be OK if libraries (modules) were to build in their own
> > target/ sub-directories, but I'd like to move a copy of the
> resulting
> > libraries into a central location higher in the project hierarchy.
> >
> > Brad
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: directory v. outputDirectory
Posted by dan tran <da...@gmail.com>.
native-maven-plugin''s outputDirectory purposely set to readonly so that all
outputs ( .o, .dll, etc) stay inside
target directory. and mvn clean can clear them as well.
Why do you want the output files outside of project? perhaps there is
another way to accomplish
what you need after the build.
-D
On 9/1/06, Brad Harper <br...@epsiia.com> wrote:
>
>
> What's the difference between
>
> <build>
> <directory>
> <outputDirectory>
> ...
>
> I'm using maven-native-plugin, which has identical configuration
> elements, but I'm prevented from using them, i.e.
>
> <build>
> <plugins>
> <plugin>
> <configure>
> <directory>
> <outputDirectory>
>
> by errors complaining about over-written read-only parameters.
>
> It would be OK if libraries (modules) were to build in their own
> target/ sub-directories, but I'd like to move a copy of the resulting
> libraries into a central location higher in the project hierarchy.
>
> Brad
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: directory v. outputDirectory
Posted by Douglas Ferguson <do...@epsiia.com>.
directory = target
outputDirectory = target/classes
----- Original Message -----
From: brad.harper@epsiia.com
Sent: Sat, 9/2/2006 2:15am
To: users
Subject: directory v. outputDirectory
What's the difference between
<build>
<directory>
<outputDirectory>
...
I'm using maven-native-plugin, which has identical configuration
elements, but I'm prevented from using them, i.e.
<build>
<plugins>
<plugin>
<configure>
<directory>
<outputDirectory>
by errors complaining about over-written read-only parameters.
It would be OK if libraries (modules) were to build in their own
target/ sub-directories, but I'd like to move a copy of the resulting
libraries into a central location higher in the project hierarchy.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
directory v. outputDirectory
Posted by Brad Harper <br...@epsiia.com>.
What's the difference between
<build>
<directory>
<outputDirectory>
...
I'm using maven-native-plugin, which has identical configuration
elements, but I'm prevented from using them, i.e.
<build>
<plugins>
<plugin>
<configure>
<directory>
<outputDirectory>
by errors complaining about over-written read-only parameters.
It would be OK if libraries (modules) were to build in their own
target/ sub-directories, but I'd like to move a copy of the resulting
libraries into a central location higher in the project hierarchy.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org