On 1/22/2013 9:12 AM, Richard Eckart de Castilho wrote: > Yup, sounds like the culprit. The "apache-release" profile is used to > simulate a release, isn't it? So that setting would be there to avoid the > staging, which makes sense. During a "mvn release:perform", the profile > "apache-release" shouldn't be active
Whoops, this is backwards I think. The apache-wide POM [1] configures the maven-release-plugin to use the profile "apache-release" when doing the deploy goal, see [2] for some documentation on how this setting is done. We enable apache-release manually, to simulate a release, without doing the mvn release... plugin. -Marshall [1] http://repo1.maven.org/maven2/org/apache/apache/10/apache-10.pom [2] http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html > and the setting shouldn't be used outside that profile unless you really want > to avoid deploying dist zips or such. > > -- Richard > > Am 22.01.2013 um 15:01 schrieb Peter Klügl <[email protected]>: > >> it says: >> >> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ >> uimaj-textmarker-parent --- >> [INFO] [INFO] Skipping artifact deployment >> >> looks like my parent pom is not correctly configured. I found in the profile >> "apache-release": >> >> <plugin> >> <artifactId>maven-deploy-plugin</artifactId> >> <configuration> >> <skip>true</skip> >> </configuration> >> </plugin> >> >> I copied this, when I created the my textmarker parent pom. The original >> setting is in build/trunk/parent-pom. >> There is a comment about "https://issues.apache.org/jira/browse/UIMA-2008";. >> Would that not also be a problem for uimaj releases? I think I can remove >> this in my pom, right? >
