No matter how i mess with this, it still complains about having no POM
file.
Hrm
Roger
On Nov 5, 2009, at 11:41 AM, Sony Antony wrote:
If I understood correctly, you dont need any fake pom.
mvn -DdescriptorId=jar-with-dependencies assembly:single
This will package all teh dependencies - recirsively - and create a
single
jar file
--sony
On Thu, Nov 5, 2009 at 8:02 AM, Roger Studner <[email protected]>
wrote:
So the only trick then, is I have to make a "fake" pom.xml file
that lists
all the dependencies my project *would need*, include these plugins
and see
if they can at least make me a ZIP of all the stuff.
Thanks, i'll check this out.
I'm doing a GWT front end on a Spring MVC j2ee webapp. And from
all i've
read, there are just a bunch of pain points with GWT & Maven
(competing
plugins, work arounds for directory/path differences). Just
worries me to
"convert wholly" to maven when really what I need, is "which of 75
jars to I
really need to put in lib" and that is it :) (technically).
Roger
On Nov 4, 2009, at 11:55 PM, Ed Hillmann wrote:
On Thu, Nov 5, 2009 at 10:24 AM, Roger Studner <[email protected]>
wrote:
I've dodged(?) using Maven since its inception, but quite clearly
that
isn't
possible anymore.
I was thinking of using the Jboss RESTEasy project, and then
reailty
struck.
There are 471,932 jars (okay, that isn't true). They don't list
which
are
for what. But of course, there are a variety of core and option
maven
dependencies for a pom.
Now, to use RESTEasy, I'd rather not convert 10+ projects to be
100%
required to use maven :).
Is there an easy way, using maven, to have mvn simply resolve
each of
those
and put the necessary jars into folders? So I then can determine
which I
truely need and copy them over as appropriate.
Have a look at the maven-dependency-plugin
http://maven.apache.org/plugins/maven-dependency-plugin/
For a project, it can show what artifacts are being used. It has a
handy utility that displayed the dependencies in a tree. You can
also
copy out the dependencies from the repository to the filesystem
(which
is what I think you're looking to do).
For example, here's a POM file that takes an artifact from the local
repository and writes it out to a directory
<profile>
<id>icefaces.push-server</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</
artifactId>
<configuration>
<artifactItems>
<artifactItem>
<groupId>org.icefaces</groupId>
<artifactId>push-server</
artifactId>
<version>${icefaces.version}</
version>
<type>war</type>
<destFileName>push-server.war</destFileName>
<overWrite>true</overWrite>
</artifactItem>
</artifactItems>
</configuration>
</plugin>
</plugins>
</build>
</profile>
Also, look at the assembly plugin
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html
This has a handy feature of packaging up any artifacts you depend
on,
along with any of the artifacts they depend on. Using this, you can
copy out all the required libraries, even if you only declare one
artifact as a dependency.
Hope this helps,
Ed
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
