On Feb 28, 2007, at 10:35 AM, Luciano Resende wrote:
My suggestion was to use a maven profile to have all pieces
necessary to run
a sample built, and I think this is the purpose of maven.
Note that I didn't suggest having maven performing the following
command
(that would actually run the sample) :
java -jar ../../../runtime/standalone/smoketest/target/assembly/bin/
launcher.jar target/calc.jar add 2 5
OK, guess it's different interpretations of "run" :-)
I'd suggested earlier in this thread of adding a pom in core-samples
that would build/itest all the common modules. That should be all the
prep a user needs before working with an individual sample. We
wouldn't need a profile for that as it would be the default goal.
This would make the typical user experience:
* download a released distribution
* install
* download the sample source
* build the common modules
* play with a sample
More experimental users could get the distribution in other ways -
either downloading an (unstable) SNAPSHOT version, or building it
themselves (really unstable). The rest of the process though would
remain the same.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
