It should work as I believe that command-line configuration overrides POM configuration. Haven't tested this specific scenario though. But it's a bit messy to specify a profile AND then a java system property to compensate. It will be very close to not understandable for a newbie in a CI interface where properties and profiles are configured on separate rows (not a pure Maven issue though).
Looking at the release-profile specified in the Super-POM, it states: <!-- NOTE: The release profile will be removed from future versions of the super POM --> Any one know the thinking behind this comment? /Anders On Fri, Feb 10, 2012 at 14:55, Thiessen, Todd (Todd) <tthies...@avaya.com> wrote: > Good thought. Unfortunately, the deploy plugin sets the updateReleaseInfo > property directly in the super pom. > >> -----Original Message----- >> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> Sent: Friday, February 10, 2012 8:44 AM >> To: Maven Users List >> Subject: Re: Antwort: Deploy javadoc/sources for snapshots >> >> can we not cheat and specify -DupdateReleaseInfo=false >> >> Or is the flag set in the parent directly in the configuration and not >> by setting the property >> >> On 10 February 2012 13:32, Thiessen, Todd (Todd) <tthies...@avaya.com> >> wrote: >> > You certainly can do the work yourself. But most of what you have >> defined is already defined in the super pom via the release profile. >> And of course the benefit of using the release profile is that is >> isn't active by default. You can configure you CI to activate the >> profile, no extra work needed. Very neat and tidy. >> > >> > But the question still remains is if this can have any negative side >> effects since the release profile also configures the deploy plugin >> with updateReleaseInfo=true. >> > >> >> -----Original Message----- >> >> From: Thorsten Heit [mailto:thorsten.h...@vkb.de] >> >> Sent: Friday, February 10, 2012 8:15 AM >> >> To: Maven Users List >> >> Subject: Antwort: Deploy javadoc/sources for snapshots >> >> >> >> 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: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
