On Tue, 31 Dec 2013 13:10:17 +0100, Benedikt Ritter wrote:
Hey Gilles
2013/12/31 Gilles <gil...@harfang.homelinux.org>
On Sun, 29 Dec 2013 13:33:23 -0800, Phil Steitz wrote:
On 12/29/13, 6:39 AM, Gilles wrote:
Hello.
Is there some framework in place in order to generate executable
files
from the Java sources located there?
I guess that a configuration snippet could be added in the
"pom.xml"[1]
so that one of the build phases can also compile (and perhaps also
run)
the example applications.
Regards,
Gilles
[1] I tried to use the "pom.xml" located in "src/userguide" but it
"failed
to resolve artefact"
org.apache.commons:commons-math3:jar:3.3-SNAPSHOT.
You need to install the [math] snapshot locally for maven to be
able
to resolve it. Run "mvn install" to get a current snapshot
installed locally.
OK. That's easy enough for me at the moment.
[I just wanted to check that what I put under "src/userguide/java"
does compile and run.]
However, I wonder why it is deemed better to have another "pom.xml"
rather than have the main one generate the "examples" JAR.
Have a look here [1]. Bottom line is, that creating multiple
artifacts from
one class path violates one of the core concepts of maven:
modularity.
I'm fine with simplifying the main "pom.xml" (i.e. use another for
creating
the "tools" JAR and yet another to create the "examples" JAR) but this
must
somehow be integrated in the "workflow" (i.e. by adding a few lines to
the
recipe in "doc/release") so that when preparing a release, everything
will
be generated and copied to the appropriate place.
Regards,
Gilles
HTH
Benedikt
[1]
http://blog.sonatype.com/2010/01/how-to-create-two-jars-from-one-project-and-why-you-shouldnt/#.UsKy2XkiOgk
Thanks,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
