> Steinar Bang <[EMAIL PROTECTED]>:
> So... if I move it to eg. generate-sources, I may get rid of the
> problem? I'll try, and post back the results.
Moving the dependency:copy config from generate-sources to
generate-resources, and doing the antrun:run patch in process-resources
did the tr
First an update: removing this from both the SuperPOM and the
Project parent POM, caused my forked lifecycle message to go away.
I tried doing like this page does
http://maven.apache.org/plugins/maven-source-plugin/usage.html
ie. changing the original
org.apache.maven.plugins
m
Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Steinar Bang
Sent: Wednesday, January 09, 2008 12:55 PM
To: users@maven.apache.org
Subject: Re: Why do maven lifecycles fork?
>>>>> "Brian E. Fox" <[EMAIL PROTECTED]>:
> Any plugin that declares @execu
> "Brian E. Fox" <[EMAIL PROTECTED]>:
> Any plugin that declares @execute [phase] will cause the build to
> fork. The dependency plugin does not, but one of your other plugins
> must. I know that javadoc did, assembly does (depending on which
> goal), enforcer:enforce-once does. Take a look a
Any plugin that declares @execute [phase] will cause the build to fork.
The dependency plugin does not, but one of your other plugins must. I
know that javadoc did, assembly does (depending on which goal),
enforcer:enforce-once does. Take a look at the various plugins you have
bound and see which o
