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 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? -- ------------------------------------------------------------------- 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 -------------------------------------------------------------------
