I guess you mean you don't have any tag in your pom.xml.
Under build/plugins declare a plugin block like this to override the
inherited version
maven-checkstyle-plugin
6.3
Btw, you should be aware that always "pinning" the plugin versions is a
strongly recommended practice. Indeed, one of
Do you use dependencyManagement ?
And Jason is right: providing a test project is quicker to help you. Might
be even quicker for you than explaining it by mail.
Push it for example on your github account and post the link here.
Cheers
Le 13 févr. 2015 21:21, "Jason van Zyl" a écrit :
> Provide
Hi better ask for a release in the dev list. If the code is actually
already fixed and just needs be released there's generally committers
willing to do it.
Cheers
Le 14 févr. 2015 02:23, "Mikko Kuokkanen" a
écrit :
> Hi.
>
> We are prototyping following combination for our web site generation:
I agree that dependency insanity could cause problems , as well as
resources.
However, the maven dependencies can be partly resolved because we can also
just analyze the pom to look at those dependencies.
I imagine as long as resources are loaded from /src/test/resources then we
can make ANY chan
Hi Curtis,
Yes, I believe, we are concerned about the same challenges, however with
slightly different approach.
I'm trying to come with a recipe or recipes for:
- determining impact of introduction of a backward incompatible change;
- determining delivered (released) versions of software,
