Lin Sun wrote:
I thought of converting this to a maven plugin today, but Joe, do you
think this will still be an issue after we release the sample and
publish the buildutil to a public maven repo?

I don't think this will be an issue for the 2.1.2 samples once we have them published. It will continue to be an issue for any samples that are currently under development (SNAPSHOTs). For snapshots I think it is reasonable to expect the user to build from the top level first.

I'm not sure if creating a maven plugin will improve things much. This plugin would still have to be built and released via some mechanism. If it ends up being similar to the car-maven-plugin on the server a bootstrap or something similar would be required prior to building an individual sample. From a user perspective, I don't see that being much different than what we have now.

Joe



Lin

On Fri, Jul 18, 2008 at 1:35 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
Specifics on why this is an issue:
- We had to add in the building of a tomcat utility (Txt2Html included in
buildutil).  This is used to generate html from java source and jsp files.
 The html is then included with the jsp & servlet samples and can be
displayed when running the samples (we might want to consider this for some
of our other samples as well).  The utility is run via ant and so we are
using the maven-antrun-plugin.   When the configuration for the execution of
the utility was included in the specific sample it worked great for just
that one sample but produced errors when attempting to build from a higher
level.  This is apparently because of the way the the maven plugin is
resolved and loaded.  To get the build working from the top level we had to
move the dependency of the antrun-plugin on buildutil up under
pluginmanagement.  However, this has the effect of now requiring buildutil
to be available for all samples even if it is not used (since most samples
use the antrun-plugin for other purposes).  There is a maven issue that
describes our problem (and indicates that it is fixed in maven 2.1.* but not
2.0.*) - MNG-1323 (http://jira.codehaus.org/browse/MNG-1323).


Reply via email to