GitHub user rdowner opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/855
Skip Maven deploy for the OSGi test bundles
Like #851, but uses a different property (that one didn't work).
These cannot be installed into a repository and uploaded to Nexus as they
do not use the same version number as Brooklyn. They have been breaking our
Jenkins CI builds as Nexus refuses to accept non-SNAPSHOT-versioned artifacts
into the snapshot repository. We would also likely encounter versioning
conflicts for release, too.
This change sets `maven.deploy.skip` on the affected modules so they are
not installed into the local repository, therefore Jenkins will not attempt to
deploy them into the remote repository.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rdowner/incubator-brooklyn
dont-deploy-osgi-test-artifacts
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/855.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #855
----
commit a6db7bca2301b9d2663e095bebab3791dfeefac3
Author: Richard Downer <[email protected]>
Date: 2015-08-20T10:03:04Z
Skip Maven deploy for the OSGi test bundles
Like 320bed4, but uses a different property (that one didn't work).
These cannot be installed into a repository and uploaded to Nexus as
they do not use the same version number as Brooklyn. They have been
breaking our Jenkins CI builds as Nexus refuses to accept
non-SNAPSHOT-versioned artifacts into the snapshot repository. We would
also likely encounter versioning conflicts for release, too.
This change sets `maven.deploy.skip` on the affected modules so they are
not installed into the local repository, therefore Jenkins will not
attempt to deploy them into the remote repository.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
