That's essentially what the profile would do. But it should be added in the corporate parent so that not all projects need to specify it. Also, and possibly more importantly, i don't want it to be bound to the build lifecycle for the developers as it adds some significant build time. It should only be executed on the CI (deploying snapshots to the repo). So it has to be in a profile not active by default.
/Anders On Fri, Feb 10, 2012 at 14:15, Thorsten Heit <[email protected]> wrote: > Hi, > >> Anyone run into the desire to deploy javadoc and sources artifacts for >> snapshots, in a similar fashion as done by the release-profile? If so, >> how are you handling that? > > Add the following configuration to build>>plugins in your pom.xml: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.8.1</version> > <executions> > <execution> > <id>attach-javadocs</id> > <goals> > <goal>jar</goal> > </goals> > </execution> > </executions> > </plugin> > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-source-plugin</artifactId> > <version>2.1.2</version> > <executions> > <execution> > <id>attach-sources</id> > <phase>verify</phase> > <goals> > <goal>jar-no-fork</goal> > </goals> > </execution> > </executions> > </plugin> > > > This is what I'm doing in a pluginManagement section in my parent pom. > > > See: > http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How_to_deploy_Javadoc_jar_file > http://maven.apache.org/plugins/maven-source-plugin/usage.html > > > HTH > > Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
