| commit | c6738282f722a39e97f2fae9f4c8288e39fae6e2 | [log] [tgz] |
|---|---|---|
| author | Stefan Seelmann <seelmann@apache.org> | Sat Jun 06 21:18:08 2015 +0000 |
| committer | Stefan Seelmann <seelmann@apache.org> | Sat Jun 06 21:18:08 2015 +0000 |
| tree | 7534d34a5e975d17087ee8845c5938591c06dbd4 | |
| parent | 891be33edfde2ce441570c55ccc9bf32078a00be [diff] |
Set version number for release 2.0.0.v20150606-M9 git-svn-id: https://svn.apache.org/repos/asf/directory/studio/branches/2.0.0.v20150606-M9@1683957 13f79535-47bb-0310-9956-ffa450edef68
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
You can use either of those two methods to build the project :
Build the ‘Eclipse Target Platform’ and generate MANIFEST.MF files first
mvn -f pom-first.xml clean install
Build the main eclipse artifacts using Tycho
mvn clean install
On Linux / Mac OS X :
$ ./build.sh
or on Windows :
> build.bat
Tycho doesn't handle snapshot dependencies well. The first time a snapshot dependency is used within the build it is cached in ~/.m2/repository/p2. Afterwards any change in the dependency (e.g. ApacheDS or LDAP API) is the considered unless it is deleted from the cache.
Recommended IDE is ‘Eclipse (Luna) for RCP Developers’: http://www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/lunasr1
Import ‘Eclipse Target Platorm’ project first
Initialize target platform
eclipse-trgt-platform.target file with the ‘Target Editor’Import the main plugins
During import some Maven plugin connectors need to be installed, accept the installation and restart.
The build produces binaries for all platforms. Archived versions can be found in product/target/products/, unpacked versions can be found below product/target/products/org.apache.directory.studio.product
tentative, not fully tested yet...
We release the following artifacts:
Test the release build: rat check, javadoc and source jar generation, GPG signing, userguide generation
mvn -f pom-first.xml clean install mvn -Papache-release -Duserguides clean install
Run UI tests (if possible on all platforms)
mvn clean install -Denable-ui-tests
As Tycho doesn't support the maven-release-plugin the release process is as follows:
We use a release number scheme that suites for both, Maven and Eclipse.
<MAJOR>.<MINOR>.<PATCH>.v<YYYYMMDD>[-M<X>|RC<X>]
Example for milestone version: 2.0.0.v20150529-M9 Example for GA version: 2.0.1.v20150529
Define a variable for later use:
export VERSION=2.0.0.v20150529-M9
svn copy https://svn.apache.org/repos/asf/directory/studio/trunk https://svn.apache.org/repos/asf/directory/studio/branches/$VERSION -m "Prepare release $VERSION"
find . -name pom-first.xml | xargs sed -i 's/2.0.0-SNAPSHOT/'$VERSION'/' find . -name pom-first.xml | xargs sed -i 's/2.0.0.qualifier/'$VERSION'/' mvn -f pom-first.xml clean install mvn org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=$VERSION
svn commit -m "Set version numbers for release $VERSION"
svn copy https://svn.apache.org/repos/asf/directory/studio/branches/$VERSION https://svn.apache.org/repos/asf/directory/studio/tags/$VERSION -m "Tag release $VERSION"
mvn -f pom-first.xml clean install mvn -Papache-release -Duserguides clean install/deploy
There is a script that collects and signs all update sites and distribution packages.
For non-interactive signing with GPG agent define env variable:
export RELEASE_KEY=28686142
Run the dist script:
cd dist ./dist.sh
Afterwards all distribution packages are located in target. Upload target/$VERSION to people.apache.org and start the vote. After successful vote the content of target can be committed as-is to https://dist.apache.org/repos/dist/release/directory/studio.
tbc.
How to search features, plugins, versions in P2 repo?