Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discontinue building jformatstring from source #4843

Conversation

davido
Copy link
Contributor

@davido davido commented Mar 14, 2018

This change stops building jformatstring from the source and consumes
the artifacts from Central. As the consequence, the sources are removed
from the Bazel tree and we discontinue packaging the sources in Bazel
source artifact.

GPL v2 with Classpath exception sources have to be still included in
third_party:gpl-srcs rule. The source jar is included in this rule, that
is used in embeded_tools archive.

@jbduncan
Copy link
Contributor

jbduncan commented Mar 16, 2018

@davido I may have misunderstood you, but AFAICT, jFormatString isn't really LGPL but GPL v2 with Classpath exception instead (same as OpenJDK's license, IIRC). Perhaps you could correct me if I'm wrong? :)

This change stops building jformatstring from the source and consumes
the artifacts from Central. As the consequence, the sources are removed
from the Bazel tree and we discontinue packaging the sources in Bazel
source artifact.

GPL v2 with Classpath exception sources have to be still included in
third_party:gpl-srcs rule. The source jar is included in this rule, that
is used in embeded_tools archive.
@davido davido force-pushed the stop-building-jformatstring-from-source branch from 5c88962 to 8d7197b Compare March 16, 2018 20:29
@davido
Copy link
Contributor Author

davido commented Mar 16, 2018

@jbduncan Yes, you are right. I was confused with this rule name: //third_party:gpl-srcs. I fixed the commit message.

@lfpino
Copy link
Contributor

lfpino commented Mar 27, 2018

Hi @iirina, Bazel sheriff here, what's the status of this pull request? It hasn't been updated for more than a week so it'd be good to understand if it's still ongoing or safe to close. Thanks.

@davido davido closed this Mar 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants