Re: Enquiry about POM parent tag version

Hi All, Thanks for your advice. POM3 is depending on POM2. The following is POM3: pom2GroupId pom2ArtifactId pom2Version Now, P

Re: Enquiry about POM parent tag version

hi Bernd, Thanks for your advice. The following is parent of POM3: POM3 parent someId true

Re: Enquiry about POM parent tag version

Please read my answer here: http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072 I think you are trying to do something that does not work On Thursday, 15 January 2015, Bernd wrote: > In order to help you we need the full chain, in pom3 y

Re: Enquiry about POM parent tag version

In order to help you we need the full chain, in pom3 you do not show the parent. In pom2 the current version must be defined, otherwise it cannot get to the parent. Did you check you actually get the pom versions you expect (just watch the downloads or look at help:effective-pom) Grettings Bernd

Re: source-plugin vs, the initialize phase?

Hi, On 1/15/15 5:45 PM, org.apache.maven.u...@io7m.com wrote: 'Lo. On 2015-01-15T17:41:33 +0100 Karl Heinz Marbaise wrote: Hi, you problem is simply you have bound the `jar` goal of the maven-source-plugin which forks the life cycle. On 2015-01-15T16:40:36 + Stuart McCulloch wrote:

Re: source-plugin vs, the initialize phase?

'Lo. On 2015-01-15T17:41:33 +0100 Karl Heinz Marbaise wrote: > Hi, > > you problem is simply you have bound the `jar` goal of the > maven-source-plugin which forks the life cycle. > On 2015-01-15T16:40:36 + Stuart McCulloch wrote: > Use the jar-no-fork and test-jar-no-fork goals of the m

Re: source-plugin vs, the initialize phase?

Hi, you problem is simply you have bound the `jar` goal of the maven-source-plugin which forks the life cycle. To prevent that you should use the `jar-no-fork` goal instead [1]... Kind regards Karl Heinz Marbaise [1] http://maven.apache.org/plugins/maven-source-plugin/jar-no-fork-mojo.htm

Re: source-plugin vs, the initialize phase?

Use the jar-no-fork and test-jar-no-fork goals of the maven-source-plugin - these won’t fork the build (which is what is causing initialize to run multiple times) On Thursday, 15 January 2015 at 16:24, org.apache.maven.u...@io7m.com wrote: > Hi. > > I have a custom plugin that inserts some ex

source-plugin vs, the initialize phase?

Hi. I have a custom plugin that inserts some extra files into the jars produced by the jar plugin. Because of the way the plugin works, it will fail if it tries to make the modifications to a jar file that has already had the modifications made. For reasons that aren't really relevant here, modify

Re: Enquiry about POM parent tag version

What does your parent tag say in POM3? Isn't that how current version is going to get resolved? Maven will use what you tell it to find places where variables get resolved to values. On 15/01/2015 2:02 AM, yeelong wrote: Hi All, Could you please help to advise the following? I hav

Re: Maven Incremental Build: JDT Compiler Implementation

Good questions. Most of our projects use our lifecycle[1] and they serve as good examples. The compiler is generally very fast so from a raw performance perspective if you have a very large build you simply can't have an incremental compile with Javac. It's all or nothing because it just can't

Re: Maven Incremental Build: JDT Compiler Implementation

Is there an example project to kick the tires for incremental builds? How about early timings for performance? Seems like the feature requires its own package type, won't that cause lots of downstream headache for other tools? On Jan 13, 2015 2:18 PM, "Jason van Zyl" wrote: > Hi, > > Incremental

Re: Help with this question

Hi, test-jar goal does'nt seems to have a classifier configuration property so it's probably why it does'nt work. You probably will have to use finalName. On Wed, Jan 14, 2015 at 9:38 PM, Carlos Bribiescas wrote: > I'm setting up our system to do dual building for different versions of > java