You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Sahoo <sa...@oracle.com> on 2013/08/12 08:45:51 UTC
Updating obr with latest release of prefs service
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
Re: Updating obr with latest release of prefs service
Posted by Felix Meschberger <fm...@adobe.com>.
Hi Sahoo
Thanks for exploring.
The site can be updated as described here: http://felix.apache.org/documentation.html#site-how-to
Regards
Felix
Am 16.08.2013 um 06:00 schrieb Sahoo:
> Hi,
>
> I was able to update OBR using the following command:
>
>> $export dist=# your checkout of (https://dist.apache.org/repos/dist/release/felix)
>> $ export artifactId=# artifactId of the bundle getting released
>> $ export version=# version of the bundle getting released
>> $exportsite=# your checkout of (https://svn.apache.org/repos/asf/felix/site/trunk/content)
>> $exportobr=${site}/obr
>> $mvn org.apache.felix:maven-bundle-plugin:deploy-file \
>> -DremoteOBR=releases.xml \
>> -Durl=file:${obr} \
>> -DbundleUrl=http://repo1.maven.org/maven2/org/apache/felix/${artifactId}/${version}/${artifactId}-${version}.jar \
>> -DpomFile=${dist}/${artifactId}-${version}.pom \
>> -Dfile=${dist}/${artifactId}-${version}.jar
>> $svn commit -m"..." ${obr}/repository.xml
>>
>
> I also noticed that using maven 3, the new repository.xml didn't have
> any of the unnecessary whitespace related changes or single quote to
> double quote related changes. I think we should update the release steps
> documented at [1] with above instructions. We should also remove the
> following note as it does not seem to be applicable anymore:
>> *Note*: with Maven 3, you must add an extension to your |<build>|
>> providing the SCP/SSH protocol:
>
> How does one update [1]?
>
> Thanks,
> Sahoo
>
> [1]
> http://felix.apache.org/documentation/development/release-management-nexus.html
>
> On Tuesday 13 August 2013 08:23 PM, Sahoo wrote:
>> Hi Stuart,
>>
>> Could you please check if this is the optimal and correct way to
>> invoke the command? I can then update the documentation.
>>
>> ~/software/apache-maven-2.2.1/bin/mvn \
>> org.apache.felix:maven-bundle-plugin:deploy-file \
>> -DremoteOBR=releases.xml \
>> -Durl=file:${obr} \
>> -DbundleUrl=http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.prefs/1.0.6/org.apache.felix.prefs-1.0.6.jar
>> \
>> -DpomFile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.pom \
>> -Dfile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.jar
>>
>> After I run this command, I see a lot of diffs related to reordering
>> of XML attributes and quote character substitution (" by ') . I am
>> assuming I can safely ignore them and check in the updated the
>> repository.xml.
>>
>> Thanks,
>> Sahoo
>> On Tuesday 13 August 2013 01:03 PM, Stuart McCulloch wrote:
>>> Use the bundle:deploy-file goal to upload details of an existing
>>> artifact.
>>>
>>> On 13 Aug 2013, at 05:28, Sahoo <sa...@oracle.com> wrote:
>>>
>>>> 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
>>>>>>
>>
>
Re: Updating obr with latest release of prefs service
Posted by Sahoo <sa...@oracle.com>.
Hi,
I was able to update OBR using the following command:
> $export dist=# your checkout of (https://dist.apache.org/repos/dist/release/felix)
> $ export artifactId=# artifactId of the bundle getting released
> $ export version=# version of the bundle getting released
> $exportsite=# your checkout of (https://svn.apache.org/repos/asf/felix/site/trunk/content)
> $exportobr=${site}/obr
> $mvn org.apache.felix:maven-bundle-plugin:deploy-file \
> -DremoteOBR=releases.xml \
> -Durl=file:${obr} \
> -DbundleUrl=http://repo1.maven.org/maven2/org/apache/felix/${artifactId}/${version}/${artifactId}-${version}.jar \
> -DpomFile=${dist}/${artifactId}-${version}.pom \
> -Dfile=${dist}/${artifactId}-${version}.jar
> $svn commit -m"..." ${obr}/repository.xml
>
I also noticed that using maven 3, the new repository.xml didn't have
any of the unnecessary whitespace related changes or single quote to
double quote related changes. I think we should update the release steps
documented at [1] with above instructions. We should also remove the
following note as it does not seem to be applicable anymore:
> *Note*: with Maven 3, you must add an extension to your |<build>|
> providing the SCP/SSH protocol:
How does one update [1]?
Thanks,
Sahoo
[1]
http://felix.apache.org/documentation/development/release-management-nexus.html
On Tuesday 13 August 2013 08:23 PM, Sahoo wrote:
> Hi Stuart,
>
> Could you please check if this is the optimal and correct way to
> invoke the command? I can then update the documentation.
>
> ~/software/apache-maven-2.2.1/bin/mvn \
> org.apache.felix:maven-bundle-plugin:deploy-file \
> -DremoteOBR=releases.xml \
> -Durl=file:${obr} \
> -DbundleUrl=http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.prefs/1.0.6/org.apache.felix.prefs-1.0.6.jar
> \
> -DpomFile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.pom \
> -Dfile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.jar
>
> After I run this command, I see a lot of diffs related to reordering
> of XML attributes and quote character substitution (" by ') . I am
> assuming I can safely ignore them and check in the updated the
> repository.xml.
>
> Thanks,
> Sahoo
> On Tuesday 13 August 2013 01:03 PM, Stuart McCulloch wrote:
>> Use the bundle:deploy-file goal to upload details of an existing
>> artifact.
>>
>> On 13 Aug 2013, at 05:28, Sahoo <sa...@oracle.com> wrote:
>>
>>> 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
>>>>>
>
Re: Updating obr with latest release of prefs service
Posted by Sahoo <sa...@oracle.com>.
Hi Stuart,
Could you please check if this is the optimal and correct way to invoke
the command? I can then update the documentation.
~/software/apache-maven-2.2.1/bin/mvn \
org.apache.felix:maven-bundle-plugin:deploy-file \
-DremoteOBR=releases.xml \
-Durl=file:${obr} \
-DbundleUrl=http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.prefs/1.0.6/org.apache.felix.prefs-1.0.6.jar
\
-DpomFile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.pom \
-Dfile=$HOME/WS/felix/dist/org.apache.felix.prefs-1.0.6.jar
After I run this command, I see a lot of diffs related to reordering of
XML attributes and quote character substitution (" by ') . I am assuming
I can safely ignore them and check in the updated the repository.xml.
Thanks,
Sahoo
On Tuesday 13 August 2013 01:03 PM, Stuart McCulloch wrote:
> Use the bundle:deploy-file goal to upload details of an existing artifact.
>
> On 13 Aug 2013, at 05:28, Sahoo <sa...@oracle.com> wrote:
>
>> 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
Re: Updating obr with latest release of prefs service
Posted by Stuart McCulloch <mc...@gmail.com>.
Use the bundle:deploy-file goal to upload details of an existing artifact.
On 13 Aug 2013, at 05:28, Sahoo <sa...@oracle.com> wrote:
> 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
>
Re: Updating obr with latest release of prefs service
Posted by Sahoo <sa...@oracle.com>.
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
Re: Updating obr with latest release of prefs service
Posted by Felix Meschberger <fm...@adobe.com>.
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