brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-21) Verify licenses of dependencies
Date Mon, 07 Jul 2014 15:18:33 GMT


ASF GitHub Bot commented on BROOKLYN-21:

GitHub user richardcloudsoft opened a pull request:

    POM dependency version fixes

    An attempt to sanitise the versions of our dependencies, while in the process of working
on BROOKLYN-21. This pull request addresses:
    * References to JUnit in our tests. These should all be to TestNG
    * Some components depend on the same artifact with different versions - change these so
the same version number is used in all places that depend on it. Where there is a conflict,
the earlier version is upgraded to match the later version.
    * All dependency versions should be addressed by defining a constant property for the
version number in the root POM, and using the `dependencyManagement` section to make this
the default. Child POMs should not mention a version number.
    * A couple of other minor issues

You can merge this pull request into a Git repository by running:

    $ git pull pom-dependency-fixes

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #50
commit 31d30d53aa2a5402cc8ae3ea6a421ac54635785a
Author: Richard Downer <>
Date:   2014-07-07T13:03:14Z

    Fix IntelliJ compilation oddity
    The code as it was does not build in IntelliJ, although the IDE editor
    does not detect there is a problem; only at compile time. The change
    fixes the compilation issue without changing the behaviour.

commit e800bea6d8046d4733f17a170324ff09efc36503
Author: Richard Downer <>
Date:   2014-07-04T15:19:44Z

    Change junit references to TestNG
    All probably the result of accepting an IDE's suggested `import` without
    looking closely!

commit 9b1cbb6e8892d5dc578c2cad508d173d14cb761a
Author: Richard Downer <>
Date:   2014-07-07T13:12:06Z

    brooklyn-software-osgi, change OSGi dependency ref
    Was previously org.osgi:core:4.3.0; changed to
    org.osgi:org.osgi.core:4.3.0 to match usage/launcher/pom.xml reference
    to OSGi

commit a513d8e127c24107afeb7a962daafb9b4f9fd955
Author: Richard Downer <>
Date:   2014-07-07T14:04:36Z

    Fix interior version conflicts - qpid

commit d6944861c8b1168d6759da0b1716f1d943c7a23a
Author: Richard Downer <>
Date:   2014-07-07T14:10:57Z

    Fix interior version conflicts - slf4j

commit 342a00dd2e59cfbd5f3747bac623221ce27db156
Author: Richard Downer <>
Date:   2014-07-07T14:13:11Z

    Fix interior version conflicts - MongoDB

commit b0a5d2ca67401b87f6ca393e5da4c223a2f5fdd3
Author: Richard Downer <>
Date:   2014-07-07T14:14:49Z

    Fix interior version conflicts - maven-war-plugin

commit 2cf8065c7ee89044f03529fdb6575654c5db8a8e
Author: Richard Downer <>
Date:   2014-07-07T14:40:42Z

    Missing dependencies on TestNG

commit 3c49dbf5f7e6a65edea43f794b8ca9ff6ff854a4
Author: Richard Downer <>
Date:   2014-07-04T16:54:45Z

    Specify version numbers in root pom.xml only
    This removes any hard-coded version numbers from pom.xml except for the
    root; the root contains a set of properties that define version numbers.
    In some cases this will change the minor version used; where this
    happens, the version used will always move forward, not backward; and
    the major version does not change.


> Verify licenses of dependencies
> -------------------------------
>                 Key: BROOKLYN-21
>                 URL:
>             Project: Brooklyn
>          Issue Type: Sub-task
>            Reporter: Richard Downer
>            Assignee: Richard Downer
>             Fix For: 0.7.0-M2
> Our dependencies must be compatible with ASF licensing policy; see:
> A slightly looser standard may apply in some cases, see:
>   *
>   *
>   *
> This may be useful for test-scoped dependencies (e.g. the LGPL MySQL JDBC driver), as
long as we ensure that the user has to undertake an "informed action" to start using the non-policy-compliant

This message was sent by Atlassian JIRA

View raw message