Just been doing this myself and you can use regular plugin
dependencies rather than resorting to extensions. For example,
putting this in your company-wide parent pom will run checkstyle:check
at the verify phase:
build
plugins
plugin
doesnt let us control changes to it;
thanks again
-t.
On 12/2/06, Robert Reiner [EMAIL PROTECTED] wrote:
Trevor Torrez wrote:
What is the best way to have all subprojects use the same checkstyles
file?
Hi Trevor,
I do not know what the best way is, but this is how it works for me:
I
On 12/4/06, Trevor Torrez [EMAIL PROTECTED] wrote:
Thanks; I had thought about that, I was hoping there was something simpler
and just as transparent. It kinda grates me to create a maven project and
repository jar file for one file; using a simple URL is tempting, but
anywhere we can stick
On 04/12/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Yep... this is one of those times when Maven is (not so) gently
encouraging you to do the right thing, (version everything associated
with your build) even if it seems a bit over the top to have to
release a jar containing a single file. :)
Yup; i agree; versioning everything associated with the build is a good
idea, and currently we do do this; I was hoping to get rid of the
duplications from project to project in an elegent manner; c'est la vie.
The maven-remote-resources plugin, although it would work, doesn't seem
right either.
Trevor Torrez wrote:
What is the best way to have all subprojects use the same checkstyles
file?
Hi Trevor,
I do not know what the best way is, but this is how it works for me:
I have a parent POM to all POMs of my subprojects. In this I declare my
checkstyle configuration
On 11/30/06, Trevor Torrez [EMAIL PROTECTED] wrote:
What is the best way to have all subprojects use the same checkstyles file?
Robert's suggestion of using a separate module as a build extension is
preferable.
Another option is to point checkstyle at a URL for its config file.
This has
What is the best way to have all subprojects use the same checkstyles file?
