felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre De Rop <pierre.de...@gmail.com>
Subject Proceeding with the Dependency Manager 3.2.0 release process
Date Sun, 20 Jul 2014 20:46:15 GMT
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 \
svn commit -m"..." ${obr}/repository.xml

The directory of my DM checkout is

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

with the following output:
[INFO] Using alternate deployment repository
[INFO] Downloading releases.xml
[INFO] Computed bundle uri:
[INFO] Writing OBR metadata
[INFO] Deploying
[INFO] Writing OBR metadata
[INFO] Uploading releases.xml

now, I'm having the following file in dependencymanager/core/obr/ directory:

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;


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message