You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Pierre De Rop <pi...@gmail.com> on 2014/07/20 22:46:15 UTC
Proceeding with the Dependency Manager 3.2.0 release process
Hi everybody,
I should probably know all this since a long time ... but I'm trying to
proceeed with the promotion of the DM 3.2.0 release; So, following the
instructions from [1], I have uploaded the DM 3.2.0 artifacts to the Felix
dist; then I released the maven repository.
Now, I'm at the point where I would like to release the DM bundles to the
OBR. But I'm not sure I understand what I have to do. So, according to the
documentation, I should do something like this:
$ export site=# your checkout of
(https://svn.apache.org/repos/asf/felix/site/trunk/content)$ export
obr=${site}/obr$ mvn clean install \
org.apache.felix:maven-bundle-plugin:deploy \
-DprefixUrl=http://repo1.maven.org/maven2 \
-DremoteOBR=releases.xml \
-DaltDeploymentRepository=apache.website::default::file:///${obr}$
svn commit -m"..." ${obr}/repository.xml
The directory of my DM checkout is
"/home/nxuser/work/osgi/felix-trunk/dependencymanager";
so, since I would like to first release the DM core to the OBR, I have
tried to do this:
---
export site=/home/nxuser/work/osgi/felix-trunk/dependencymanager/core
export obr=${site}/obr
mvn clean install org.apache.felix:maven-bundle-plugin:deploy
-DprefixUrl=http://repo1.maven.org/maven2 -DremoteOBR=releases.xml
-DaltDeploymentRepository=apache.website::default::file:///${obr}
---
with the following output:
[INFO] Using alternate deployment repository
apache.website::default::file:////home/nxuser/work/osgi/felix-trunk/dependencymanager/core/obr
[INFO] LOCK
file:////home/nxuser/work/osgi/felix-trunk/dependencymanager/core/obr/releases.xml
[INFO] Downloading releases.xml
[INFO] Computed bundle uri:
http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.dependencymanager/3.2.1-SNAPSHOT/org.apache.felix.dependencymanager-3.2.1-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] Deploying
http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.dependencymanager/3.2.1-SNAPSHOT/org.apache.felix.dependencymanager-3.2.1-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] Uploading releases.xml
[INFO] UNLOCK
file:////home/nxuser/work/osgi/felix-trunk/dependencymanager/core/obr/releases.xml
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
now, I'm having the following file in dependencymanager/core/obr/ directory:
->
releases.xml
releases.xml.lock
so, my first question is: am I correct so far ? I'm not sure because in the
dependencymanager/core/obr/releases.xml, the version used for the
dependencymanager core artifact is 3.2.1-SNAPSHOT while I would like to
deploy in the OBR the just releasing DM core, which version is 3.2.0
(3.2.1-SNAPSHOT is the next development version which has been generated by
the "mvn release prepare/perform" commands).
then; I have not yet committed the obr/releases.xml file; but should I
really do it now ? and then how the OBR will be updated with the new DM
core 3.2.0 version ?
thanks in advance and kind regards;
/Pierre
[1]
http://felix.apache.org/documentation/development/release-management-nexus.html#create-an-announcement