Thanks for the pointer, we figured out something along these lines meanwhile after re-reading the poms. We got a bit confused at one point because we thought the "skip deploy" would be in the apache-release profile, which it turned out not to be, it's in a different profile in the UIMA build master POM. Anyway, it ended up somehow being in the TM pom within the apache-release profile and after removing it from there, things started to improve ;)
-- Richard Am 23.01.2013 um 19:34 schrieb Marshall Schor <[email protected]>: > 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 -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab (UKP-TUD) FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 [email protected] www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
