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 Danie
The problem is due to:
parent/pom.xml:
1.0.0
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...@apa
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 foun
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
