So I actually had to go through all 165 things the NOTICE plugin could not
figure out and exclude them or add them to the license list. I was able to
successfully do that for 163 of them :-)
Two remaining:
<artifact>
<groupId>com.atlassian.confluence</groupId>
<artifactId>confluence</artifactId>
<version>3.5</version>
</artifact>
<artifact>
<groupId>com.atlassian.jira</groupId>
<artifactId>jira-core</artifactId>
<version>4.4</version>
</artifact>
These are provided scope but I'm required to relate them back to a license.
Does anyone know what I should flag it as? Just a link to the
JIRA/Confluence license page?
For reference, here are the other licenses:
https://source.jasig.org/licenses/license-mappings.xml
On Tue, Dec 31, 2013 at 10:05 AM, Scott Battaglia <scott.battag...@gmail.com
> wrote:
> Just a note that I know people have been waiting on the release. We've
> been playing some upgrade games with a combination of the Maven Notice
> Plugin and the Jasig Parent POM file, discovering some incompatibilities.
> I believe Misagh and I have worked them all out so I will upgrade the
> parent POM to the latest Notice plugin tomorrow morning (probably won't get
> to it today) and then push the CAS Client release tomorrow night.
>
> In theory, assuming everything goes according to plan, which as we can
> see, hasn't happened so far :-)
>
>
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
