brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdowner <...@git.apache.org>
Subject [GitHub] incubator-brooklyn pull request: Skip Maven install for the OSGi t...
Date Wed, 19 Aug 2015 14:52:27 GMT
GitHub user rdowner opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/851

    Skip Maven install for the OSGi test bundles

    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.install.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-install-osgi-test-artifacts

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/851.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 #851
    
----
commit 320bed451249fdb0f123f3df5a4da0470761458b
Author: Richard Downer <richard@apache.org>
Date:   2015-08-19T14:49:13Z

    Skip Maven install for the OSGi test bundles
    
    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.install.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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message