Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of cctrieloff@redhat.com
 designates 66.187.233.31 as permitted sender)
Message-ID: <474A1C2C.5090702@redhat.com>
Date: Sun, 25 Nov 2007 20:06:52 -0500
From: Carl Trieloff <cctrieloff@redhat.com>
Reply-To: cctrieloff@redhat.com
Organization: Red Hat
User-Agent: Thunderbird 1.5.0.7 (X11/20060913)
MIME-Version: 1.0
To: Maven Developers List <dev@maven.apache.org>
CC: legal-discuss@apache.org, Richard van Nieuwenhoven <ritchie@gmx.at>
Subject: Re: copieing sources in to a maven-plugin
References: <47397060.4030506@gmx.at>
	 <0A1B7D0F-9499-4E94-8DA1-A09467208CB0@apache.org>
 <262c6c680711251546y7d054d08r44cf1529d050483d@mail.gmail.com>
In-Reply-To: <262c6c680711251546y7d054d08r44cf1529d050483d@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------080402000906050603010401"

--------------080402000906050603010401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


yes and no.

You can NOT copy files from EPL into an ASL project, or modify them in 
an ASL project. However you can take a binary (jar) dependency on an EPL 
binary. So you would have to copy the jar that the source is in. 
However, the source or part of the jar is also not permitted by the 
combination of ASL / EPL. i.e. only binary dependencies on EPL will work 
under ASL. Cliff has a good page posted on topic posted.

Carl.

Arnaud HERITIER wrote:
> Hi Guys,
>
>   Thus what can I do ?
>   Richard proposed a patch (http://jira.codehaus.org/browse/MECLIPSE-344)
> which is very useful for our eclipse plugin, but it bundles 2 java classes
> coming from eclipse (IBM - EPL 1.0). Those sources are in src/main/eclipse
> with the license file.
>
>   Can I add them, or is it prohibited ?
>
> Arnaud
>
> On Nov 14, 2007 4:37 AM, Brett Porter <brett@apache.org> wrote:
>
>   
>> On 13/11/2007, at 4:37 AM, Richard van Nieuwenhoven wrote:
>>
>>     
>>> I see different solutions, but witch one to take ....
>>> - copy the sources and leaf them as untouched as possible (may be even
>>> in a own source folder to separate them and exclude them from code
>>> reformating)
>>>       
>> yes, they will need to be separate in this case - note that the EPL
>> requires you contribute enhancements and fixes back to the author.
>>
>>     
>>> - extract the classes or sources at build time and include them in the
>>> package as classes
>>>       
>> this is likely a better alternative to the above, but remember you
>> need to include the relevant license/notice if you distribute your code.
>>
>>     
>>> - completely rewrite the part i need (to remove the copyright)
>>>       
>> you can't just "remove copyright" and rewrite in place - if you
>> rewrite it must be free of influence from the original.
>>
>>     
>>> - include the dependency anyway
>>>       
>> that might be the best place to start, and use exclusions to remove
>> the tree of deps you don't need.
>>
>> - Brett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>>     
>
>
>   


--------------080402000906050603010401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
yes and no.<br>
<br>
You can NOT copy files from EPL into an ASL project, or modify them in
an ASL project. However you can take a binary (jar) dependency on an
EPL binary. So you would have to copy the jar that the source is in.
However, the source or part of the jar is also not permitted by the
combination of ASL / EPL. i.e. only binary dependencies on EPL will
work under ASL. Cliff has a good page posted on topic posted.<br>
<br>
Carl.<br>
<br>
Arnaud HERITIER wrote:
<blockquote
 cite="mid262c6c680711251546y7d054d08r44cf1529d050483d@mail.gmail.com"
 type="cite">
  <pre wrap="">Hi Guys,

  Thus what can I do ?
  Richard proposed a patch (<a class="moz-txt-link-freetext" href="http://jira.codehaus.org/browse/MECLIPSE-344">http://jira.codehaus.org/browse/MECLIPSE-344</a>)
which is very useful for our eclipse plugin, but it bundles 2 java classes
coming from eclipse (IBM - EPL 1.0). Those sources are in src/main/eclipse
with the license file.

  Can I add them, or is it prohibited ?

Arnaud

On Nov 14, 2007 4:37 AM, Brett Porter <a class="moz-txt-link-rfc2396E" href="mailto:brett@apache.org">&lt;brett@apache.org&gt;</a> wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">On 13/11/2007, at 4:37 AM, Richard van Nieuwenhoven wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">I see different solutions, but witch one to take ....
- copy the sources and leaf them as untouched as possible (may be even
in a own source folder to separate them and exclude them from code
reformating)
      </pre>
    </blockquote>
    <pre wrap="">yes, they will need to be separate in this case - note that the EPL
requires you contribute enhancements and fixes back to the author.

    </pre>
    <blockquote type="cite">
      <pre wrap="">- extract the classes or sources at build time and include them in the
package as classes
      </pre>
    </blockquote>
    <pre wrap="">this is likely a better alternative to the above, but remember you
need to include the relevant license/notice if you distribute your code.

    </pre>
    <blockquote type="cite">
      <pre wrap="">- completely rewrite the part i need (to remove the copyright)
      </pre>
    </blockquote>
    <pre wrap="">you can't just "remove copyright" and rewrite in place - if you
rewrite it must be free of influence from the original.

    </pre>
    <blockquote type="cite">
      <pre wrap="">- include the dependency anyway
      </pre>
    </blockquote>
    <pre wrap="">that might be the best place to start, and use exclusions to remove
the tree of deps you don't need.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:dev-unsubscribe@maven.apache.org">dev-unsubscribe@maven.apache.org</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:dev-help@maven.apache.org">dev-help@maven.apache.org</a>


    </pre>
  </blockquote>
  <pre wrap=""><!---->

  </pre>
</blockquote>
<br>
</body>
</html>

--------------080402000906050603010401--