You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2010/01/20 22:45:54 UTC
[jira] Commented: (ARIES-126) Aries does not deploy sources to mvn
repository
[ https://issues.apache.org/jira/browse/ARIES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803004#action_12803004 ]
David Jencks commented on ARIES-126:
------------------------------------
Don't do this.
I haven't looked at the actual poms in aries, so this might already be set up, but a better idea is to use (possibly several levels deep) the apache 7 pom as parent and build with
mvn clean deploy -Papache-release
This builds all the artifacts for a release including the source jars, javadoc jars, source archive, and binary jars (normal jars) and deploys them as snapshots. If this works you are 90% on the way to being able to use the release plugin for releases.
> Aries does not deploy sources to mvn repository
> -----------------------------------------------
>
> Key: ARIES-126
> URL: https://issues.apache.org/jira/browse/ARIES-126
> Project: Aries
> Issue Type: Bug
> Reporter: Thomas Diesler
>
> Perhaps you could add this to the default parent pom.xml
> <plugin>
> <artifactId>maven-source-plugin</artifactId>
> <executions>
> <execution>
> <id>attach-sources</id>
> <goals>
> <goal>jar</goal>
> </goals>
> </execution>
> </executions>
> <inherited>true</inherited>
> </plugin>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.