You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2008/06/20 16:43:46 UTC

[jira] Created: (LEGAL-30) Options for including bridge code to prohibited works

Options for including bridge code to prohibited works
-----------------------------------------------------

                 Key: LEGAL-30
                 URL: https://issues.apache.org/jira/browse/LEGAL-30
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Sebb


The 3rd party policy says:

"YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."

In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.

Is the build process allowed to unconditionally depend on a prohibited work?

If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?

Or must the bridge code be buildable without the presence of the prohibited work?
[e.g. in Java this can be done with reflection]


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615567#action_12615567 ] 

Jukka Zitting commented on LEGAL-30:
------------------------------------

Sebb:
> In the case of Maven projects, how can the POM refer to the prohibited work?
> Must it be "provided" - i.e. the user is responsible for obtaining it, or can it be downloaded automatically?

I think setting the dependency to "optional" [1] would be more accurate. That means that the project is usable without the optional dependency, and that downstream projects must explicitly include the optional dependency if they want to use related functionality.

[1] http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615417#action_12615417 ] 

Henri Yandell commented on LEGAL-30:
------------------------------------

We don't know :) That's why it's in the draft, not the resolved questions.

I think these are exactly the questions that are not going to be answerable until we have lots of experience of use cases.

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Sebb (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607541#action_12607541 ] 

Sebb commented on LEGAL-30:
---------------------------

In the case of Maven projects, how can the POM refer to the prohibited work?

Must it be "provided" - i.e. the user is responsible for obtaining it, or can it be downloaded automatically?

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Closed: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell closed LEGAL-30.
------------------------------

    Resolution: Later

Closing this. It's a part of the draft we've not tried to bring over, and in the last couple of years have had very little in the way of driving use cases to want to bring over. 

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732388#action_12732388 ] 

Henri Yandell commented on LEGAL-30:
------------------------------------

Agreed, that's a possibility. It's possible that provided implies platform - so anything can go there, while optional needs to be a use case the Legal PMC have agreed with.

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


[jira] Commented: (LEGAL-30) Options for including bridge code to prohibited works

Posted by "Sebb (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615578#action_12615578 ] 

Sebb commented on LEGAL-30:
---------------------------

OK, but there may be some cases where the code is not optional. I cannot think of any at present, apart from Java itself.

Maybe one way to look at this is to say that Maven POMs can only use either 'provided' or 'optional' dependenecies to refer to prohibited works.

> Options for including bridge code to prohibited works
> -----------------------------------------------------
>
>                 Key: LEGAL-30
>                 URL: https://issues.apache.org/jira/browse/LEGAL-30
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sebb
>
> The 3rd party policy says:
> "YOU MAY include code within the Apache product necessary to achieve compatibility with a prohibited work through the use of API calls, "bridge code", or protocols, provided that the compatibility code was contributed under a CLA."
> In the case of Java code, the easiest way to build bridge code is to include a copy of the prohibited work in the classpath when compiling the code.
> This means that the prohibited work is a requirement for building the Apache product, and would need to be provided somehow by the builder.
> Is the build process allowed to unconditionally depend on a prohibited work?
> If the build process can be modified to conditionally build the bridge code when the prohibited work is present, is that OK?
> Or must the bridge code be buildable without the presence of the prohibited work?
> [e.g. in Java this can be done with reflection]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org