[
http://jira.codehaus.org/browse/MSOURCES-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104173
]
Christian Sauer commented on MSOURCES-11:
-----------------------------------------
Hey,
may it be possible that this issue is still present in 2.0.6?
I' ve got a parent POM with following plugin config:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.3</version>
<executions>
<execution>
<goals>
<goal>jar</goal>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
Building a component with a pom inheriting from the parent one, the build will
still not create the source artifact!
I have to add the definition to each component for the sources jar being
created ...
Any idea?
Cheers
> When source plugin is used, it should make sure it is invoked during install
> ----------------------------------------------------------------------------
>
> Key: MSOURCES-11
> URL: http://jira.codehaus.org/browse/MSOURCES-11
> Project: Maven 2.x Source Plugin
> Issue Type: Improvement
> Reporter: Aaron Digulla
> Assignee: Jason van Zyl
> Fix For: 2.0.3
>
>
> I have a really hard time to make the source plugin work. When I just run
> "mvn install", the source plugin is ignored.
> I tried to use executions
> (http://garbuz.com/sm/content.php/articles/maven2_deploying_sources/) but
> that also doesn't work reliably.
> The only stable way I found so far is:
> mvn source:jar install
> but that's tedious. Isn't it possible to configure the plugin by default in
> such a way that, when it is used in the POM, it will be invoked automatically
> during "mvn install", "mvn deploy", etc?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
