[orbit-dev] ebr-maven-plugin: How to handle odd licenses that will only

["Erwin DL" <erwindl0@xxxxxxxxx>]

Dear all,

I have a similar issue as discussed last week, but this time for a license
that may only be needed once.

CQs 12473 & 12474 have been approved for binary distribution, and the
original license is SISSL 1.2.
Similar to below, this license has been approved for CQs.
But as it is no longer actively used for new projects, I guess there will be
very few future requests with it.

The related binaries have already been uploaded to the Orbit approved
artifacts repository (thanks Roland).
But now I need to add them in Orbit, preferably via a bundle recipe. 

And the ebr-maven-plugin does not accept SISSL, which I assume must still be
used as LICENSE (even if it's a binary-only redistribution)?

Any advice on how to get this working? 
Do I also request to add it in KnownLicenses in EBR?
Or is there a way to handle this as an exception?

Thanks!

Erwin


-----Original Message-----
From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx]
On Behalf Of Gunnar Wagenknecht
Sent: Tuesday, August 8, 2017 3:40 PM
To: Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
Cc: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Subject: Re: [orbit-dev] ebr-maven-plugin: How to handle odd licenses?
(Invalid license 'Custom license based on Apache 1.1')

> On 8. Aug 2017, at 10:04, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
wrote:
> Can you tell me a bit more how <localLicenseFiles> is supposed to be 
> used? I had a brief look at the EclipseIpInfoMojo code [1], but 
> couldn't figure it out. :-(

Sight. I was hoping that the example in the class JavaDoc would be enough.
:)

Anyway, I took the opportunity and documented an example as integration test
for future use:
https://github.com/eclipse/ebr/pull/20

> 
>> [WARNING] Found existing about.html file at ... Please set the force
property to true in order to update/override it (eg. '-Dforce=true' via
command line).
> 
> Likewise for the ip_log.xml. This seems to suggest that these files 
> are supposed to be generated *during* the build rather than checked 
> into Git. Is this correct? But settings -Dforce=true doesn't do 
> anything (like downloading a license file).

They are initially generated during create. Setting force triggers
"overriding" of those files during build with updated information. Sometimes
this is not wanted. I can't remember the default for Orbit, though.

However, I noticed that a force will override the reference attribute of the
license with the "good" one based on the hard-coded KnownLicenses values.
Thus, I added a note to the new custom license.

-Gunnar


--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/orbit-dev