Re: Filtering resources

Hi! On 13 January 2016 at 19:01, Robert Scholte wrote: > Hi, > > What would you expect when start and end delimiters are the same in > combination with nested expression. Don't think that'll ever work. > I assume that in your case @PoolSize.@ and @@ are evaluated. > AFAIK

Maven Checkstyle Plugin 2.17 and Generics

Hi! I have got the following checkstyle definition [1]. If I update the checkstyle plugin from 2.16.to 2.17 or use checkstyle 6.11.1 as dependency, I get several errors concerning ? in generics. E.g. * public Class getMergeStrategy() { * public interface ModelValidator extends

Re: Filtering resources

and how do I differentiate @foo@bar@@ whether that would be equivalent to either: ${foo}bar${} or ${foo${bar}} if using ${ } style delimiters for the start and end? At least with ${ } style delimiters one can count braces... how about @foo@bar@manchu@ is that supposed to be

RE: [EXTERNAL] How best to override maven-javadoc-plugin to do nothing?

Try setting property maven.javadoc.skip to true in your pom.xml https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#skip https://maven.apache.org/plugins/maven-javadoc-plugin/jar-mojo.html#skip > -Original Message- > From: David M. Karr

Why is checkstyle failing on one project, but not others?

This may be a checkstyle-specific problem, but I'll start with the maven checkstyle plugin. I'm integrating a large codebase into another larger project that has checkstyle standards. After I added the parent pom spec to the top-level pom and ran the build, I noticed it successfully built

Re: Why is checkstyle failing on one project, but not others?

Hello, Most likely the source directory is (incorrectly) overwritten at the compile plugin (or it is compiled by the parent pom or some other strange mechanisms like an ant plugin). The -X output (together with the effective pom) should tell you that as well. Removing the , moving the files

How best to override maven-javadoc-plugin to do nothing?

Simple question: How do I best override the maven-javadoc-plugin to make it do nothing? I'm integrating a non-API project into a much larger build where everything else is an API, so maven-javadoc-plugin is specified in the parent. It would be best to just have it not run javadoc on this

Re: surefire 'forked vm failed'

2.19.1 is just as broken in these cases. On Tue, Jan 12, 2016 at 3:57 PM, Andreas Gudian wrote: > You might wanna try 2.19.1, where Tibor fixed a couple of issues regarding > the fork-communication that crept in to 2.19. > > 2016-01-12 15:13 GMT+01:00 Benson Margulies

RE: Should I disable maven-compiler-plugin when using aspectj-maven-compiler?

> Date: Thu, 14 Jan 2016 09:21:41 +0200 > Subject: Re: Should I disable maven-compiler-plugin when using > aspectj-maven-compiler? > From: dagansand...@gmail.com > To: users@maven.apache.org

Re: Why is checkstyle failing on one project, but not others?

Hello, You can run the build with -X it will give you the actual config parameters used for the plugin (especially includes/excludes/sourceDirectory) as well as a list of the (not) scanned resources. Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: "David M. Karr"

Re: Why is checkstyle failing on one project, but not others?

Ok, that gave me a big clue, and a new question. I've realized that ALL of these projects are using "src" as their source root, instead of "src/main/java", but this one that is failing is the only one that specifies the "sourceDirectory" value. Those projects that aren't specifying the value

Re: Filtering resources

Hi! On 14 January 2016 at 15:09, Stephen Connolly wrote: > and how do I differentiate @foo@bar@@ whether that would be equivalent to > either: > > ${foo}bar${} > > or > > ${foo${bar}} > This is obviously a complicated example if you allow empty tokens when