another workaround attempt to fix the release

git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1674601 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Mark Struberg 2015-04-19 10:39:39 +00:00
parent 232581e523
commit 0221ff996d
2 changed files with 9 additions and 10 deletions

View File

@ -232,16 +232,6 @@
</build>
</profile>
<!--
Profile to openbooks to be built during a release (because it creates a build loop).
Activating this profile will simply disable the default profile
-->
<profile>
<id>apache-release</id>
</profile>
</profiles>
</project>

View File

@ -770,6 +770,15 @@
<version>2.4.2</version>
<configuration>
<useReleaseProfile>false</useReleaseProfile>
<!--
The openbooks example contains a build.xml which tries to add ~/.m2/repository/../openjpa-all-nnn.jar
to the classpath. But since the maven-release-plugin by default only prepares with 'clean verify'
the jar doesn't end in the local m2 repo. It will only be in the opanjpa-all/target folder.
For now I forced an 'install', but we should ultimately just fix the openbooks example.
-->
<preparationGoals>clean install</preparationGoals>
<goals>deploy</goals>
<arguments>-Papache-release,docbook-profile,test-derby,bval</arguments>
<autoVersionSubmodules>true</autoVersionSubmodules>