The Maven team is pleased to announce the release of the Apache Maven
Checkstyle Plugin, version 2.12
Generates a report on violations of code style and optionally fails the build
if violations are detected.
http://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the versio
The Maven team is pleased to announce the release of the Apache Maven PMD
Plugin, version 3.1
A Maven plugin for the PMD toolkit, that produces a report on both code rule
violations and detected copy and paste
fragments,
as well as being able to fail the build based on these metrics.
ht
I would have thought that the trunk would always have a SNAPSHOT version
and branches would be a series of SNAPSHOTS ending in a RELEASE which
has been merged back into the trunk as part of the next version's
current SNAPSHOT.
In order for someone to get into trouble, they would have to check-
Could you try the recently release 1.6 version?
If it also fails, please file an issue ticket [1] and provide a small
project that can be used to reproduce the issue.
/Anders
[1] https://jira.codehaus.org/browse/MJAXB
On Thu, Mar 13, 2014 at 11:29 PM, blipsman wrote:
> I found solution:
> To
The pom on trunk or any branch should *always* specify a SNAPSHOT version.
/Anders
On Fri, Mar 14, 2014 at 1:46 PM, richard_senior wrote:
> Hello,
>
> We are using maven, jenkins and nexus for continuous integration.
>
> Our trunk branch contains no snapshots, and jenkins is polling the scm and
Hi,
We are suffering from SCM-740 [1]. Is there any chance to apply the
attached patch?
Thanks
[1]: http://jira.codehaus.org/browse/SCM-740
