The super-pom turns out to document:
<plugin>
<inherited>true</inherited>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
Which is the source of his charming situation. I need to rebind it to
a nonexistent phase, I guess.
On Thu, Jul 30, 2009 at 10:09 PM, Wayne Fay<[email protected]> wrote:
>> The maven-source-plugin is running in my lifecycle even though I never
>> mention it in a pom. Is there a way to chase it out?
>
> Is it mentioned in a parent or grandparent pom? Are you using a
> profile that brings it in -- perhaps one that is activeByDefault? Did
> you check mvn help:effective-pom?
>
> What command are you running that results in m-s-p being executed? It
> is bound to some profiles that automatically come down with Maven, so
> you might be running into one of those, perhaps.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
