Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.incubator.apache.org
From: rdowner <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
References: <git-pr-823-incubator-brooklyn@git.apache.org>
In-Reply-To: <git-pr-823-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: license automation
Content-Type: text/plain
Message-Id: <20150817091517.50161E00D5@git1-us-west.apache.org>
Date: Mon, 17 Aug 2015 09:15:17 +0000 (UTC)

Github user rdowner commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/823#issuecomment-131740318
  
    Aside from the change to the root `LICENSE` and the unrelated `pom.xml` changes, I'm happy with this PR. Handling license compliance in a project with as many dependencies as Brooklyn is a pain and adding this automation simplifies part of that process.
    
    I have a good wishlist of what a license-helping tool would do! As I said earlier, established tooling is thin on the ground and I can easily see this and your Maven plugin developing into a comprehensive tool that could be re-used by many projects. The questions is do you want to consider that just now, or stick to the simplest thing that could possible work for Brooklyn :smile:


---
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.
---