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 dav...@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 > dk...@apache.org > http://www.dankulp.com/blog >