You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by da...@apache.org on 2009/12/18 10:35:36 UTC
DOSGi deploy failing on Hudson
Hi all,
The DOSGi deploy build on Hudson is failing with the following:
[INFO] Error deploying artifact: Authorization failed: Access denied
to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar
See [1]. Anyone an idea what might be causing this or how to resolve it?
Thanks!
David
[1] http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org.apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console
Re: DOSGi deploy failing on Hudson
Posted by Eoghan Glynn <eo...@gmail.com>.
Hmmm ... smells like a Nexus issue.
If I follow that link, I'm redirected to:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar
with the message:
Item not found on path
"/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar"
in repository "orgapachecxf-001"!This looks a reference to a temporary
staging area created by Nexus, for use for example while a release vote is
in motion (so for the recent dOSGi 1.1 release that I cut, the staging area
was assigned orgapachecxf-021).
Normally when the vote is declared, the staging area would be closed as the
artifacts are promoted. I'd expect the backing storage is discarded by
Nexus.
I don't know why its pointing back to the first CXF staging area ever
created in this case (i.e. the "-001" suffix) but that would have long since
ceased to exist.
Maybe report the issue to the infrastructure folks, or whomever has admin
access to Nexus.
Cheers,
Eoghan
2009/12/18 <da...@apache.org>
> Hi all,
>
> The DOSGi deploy build on Hudson is failing with the following:
>
> [INFO] Error deploying artifact: Authorization failed: Access denied
> to:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar
>
> See [1]. Anyone an idea what might be causing this or how to resolve it?
>
> Thanks!
>
> David
>
> [1]
> http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org.apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console
>
Re: DOSGi deploy failing on Hudson
Posted by da...@apache.org.
Ok - I'll take a look.
I can't just change it to 1.0.0-SNAPSHOT because these classes are
defined by the OSGi Alliance and their version is actually 1.0.0. But
maybe we can avoid building this module separately, this module is
only an internal artefact for DOSGi...
Cheers,
David
2009/12/18 Daniel Kulp <dk...@apache.org>:
>
>
> The problem is due to:
> parent/pom.xml:
> <remote.service.admin.interfaces.version>1.0.0</remote.service.admin.interfaces.version>
>
>
> Thus, the build of
> dsw/cxf-osgi-remote-service-admin-interfaces/pom.xml
>
> is considered a release and is trying to deploy as a release. That version
> number needs to change to a SNAPSHOT.
>
> Dan
>
>
> On Fri December 18 2009 4:35:36 am davidb@apache.org wrote:
>> Hi all,
>>
>> The DOSGi deploy build on Hudson is failing with the following:
>>
>> [INFO] Error deploying artifact: Authorization failed: Access denied
>> to:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apac
>> he/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remo
>> te-service-admin-interfaces-1.0.0.jar
>>
>> See [1]. Anyone an idea what might be causing this or how to resolve it?
>>
>> Thanks!
>>
>> David
>>
>> [1]
>> http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org
>> .apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
Re: DOSGi deploy failing on Hudson
Posted by Daniel Kulp <dk...@apache.org>.
The problem is due to:
parent/pom.xml:
<remote.service.admin.interfaces.version>1.0.0</remote.service.admin.interfaces.version>
Thus, the build of
dsw/cxf-osgi-remote-service-admin-interfaces/pom.xml
is considered a release and is trying to deploy as a release. That version
number needs to change to a SNAPSHOT.
Dan
On Fri December 18 2009 4:35:36 am davidb@apache.org wrote:
> Hi all,
>
> The DOSGi deploy build on Hudson is failing with the following:
>
> [INFO] Error deploying artifact: Authorization failed: Access denied
> to:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apac
> he/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remo
> te-service-admin-interfaces-1.0.0.jar
>
> See [1]. Anyone an idea what might be causing this or how to resolve it?
>
> Thanks!
>
> David
>
> [1]
> http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org
> .apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog