It's the maven-bundle-plugin:deploy goal that takes care of updating
obr, so I would like to believe package phase would be sufficient. But,
it's still not clear how I am supposed to update obr using the artifacts
that are already created during release process? If I checkout from the
svn tag and run the following maven command:
mvn clean package\
org.apache.felix:maven-bundle-plugin:deploy\
-DprefixUrl=http://repo1.maven.org/maven2\
-DremoteOBR=releases.xml\
-DaltDeploymentRepository=apache.website::default::file:///${obr}
, it's going to generate new artifacts and use them to update the obr.
Is that not an issue?
Thanks,
Sahoo
On Monday 12 August 2013 01:00 PM, Felix Meschberger wrote:
Hi Sahoo
Good point.
I am not sure, whether the "package" build phase would be sufficient and you don't actually need
the "install" build phase. The actual repository.xml maintenance takes place in the
"org.apache.felix:maven-bundle-plugin:deploy" goal which just adds references to the maven
repository.
Regards
Felix
Am 12.08.2013 um 08:45 schrieb Sahoo:
Hi,
The process as documented in [1] to update obr is not clear to me. How
do I actually update repository.xml with released artifacts? Do I
checkout from the svn tag and run the maven command? It does not sound
correct, since it will lead to regeneration of artifacts. Ideally I
would like repository.xml to be updated with artifacts that are uploaded
to remote repository.
Thanks,
Sahoo
[1]
http://felix.apache.org/documentation/development/release-management-nexus.html
