It would be something like:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.0</version>
<executions>
<execution>
<id>list-deps</id>
<phase>generate-resources</phase>
<goals>
<goal>list</goal>
</goals>
<configuration>
<outputFile>foo.txt</outputFile>
</configuration>
</execution>
</executions>
<plugins>
</build>
Hth,
Nick S.
-----Original Message-----
From: Lachlan Deck [mailto:[EMAIL PROTECTED]
Sent: Thu 4/24/2008 04:40
To: Maven Users List
Subject: Re: [newby] how to include/package private libs/*.jar
Hi Joshua,
On 23/04/2008, at 11:23 PM, Joshua ChaitinPollak wrote:
> On Apr 23, 2008, at 1:05 AM, Lachlan Deck wrote:
>>>> - append to the text file a list of the jars bundled (prefixing
>>>> each with a custom path).
>>>
>>> That's a tricky one. I'd have to say start with the dependency or
>>> assembly plugin and see if they can do what you need. I know one
>>> of the plugins can put the jars on your classpath in the Manifest,
>>> but we don't use the manifest, so I have no experience with it.
>>
>> Right. This is the bit I'm stuck with...
>
> Well, I'm not sure if this is helpful or not, but you can do this:
>
> mvn -DoutputFile=foo.txt dependency:list
>
> which will put your dependencies in a file called foo.txt. You could
> then use the exec or groovy plugins to process the output file into
> the format you want.
Interesting. Forgive my ignorance (still a maven newbie) but how might
I incorporate that into the build lifecycle?
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
