Re: [VOTE] Release Apache Wagon version 3.3.4
Thank you Vladimir. This problem affects Maven core binary package, as you already reported. For the source release we do not have a real problem as we did not copy/paste Jsoup code. For binary release (that actually is not part of the official VOTE), the jar we are deploying to Maven central, I think we can only bundle the LICENSE file of Jsoup inside the jar such LICENSE file includes the NOTICE we are talking about. This is really some task we should document in maven shade plugin website, or at least mention that whoever embeds another library to handle this kind of problem I wonder if we could enhance the pom in the future to report machiene readable statements like 'the artifact will include a binary copy of this other third party pom' (I apologize, I don't want to pollute the vote thread, but this is somehow related) Enrico Il mer 6 nov 2019, 00:38 Tibor Digana ha scritto: > The MIT license can be included in the project > https://www.apache.org/legal/resolved.html > Are we talking about the file /META-INF/DEPENDENCIES in JAR? > > On Tue, Nov 5, 2019 at 8:10 PM Vladimir Sitnikov < > sitnikov.vladi...@gmail.com> wrote: > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1535/ > > > > -1 since > > > > > https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar > > violates licensing terms for the third-party code. > > One of the violations is org.jsoup:jsoup. > > > > I know releases may not be vetoed ( > > https://www.apache.org/foundation/voting.html#ReleaseVotes ) > > However, there's > > > > > http://www.apache.org/legal/release-policy.html#licensing > > >Every ASF release MUST comply with ASF licensing policy. This > requirement > > is of utmost importance > > > > Vladimir > > >
Re: [VOTE] Release Apache Wagon version 3.3.4
The MIT license can be included in the project https://www.apache.org/legal/resolved.html Are we talking about the file /META-INF/DEPENDENCIES in JAR? On Tue, Nov 5, 2019 at 8:10 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1535/ > > -1 since > > https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar > violates licensing terms for the third-party code. > One of the violations is org.jsoup:jsoup. > > I know releases may not be vetoed ( > https://www.apache.org/foundation/voting.html#ReleaseVotes ) > However, there's > > > http://www.apache.org/legal/release-policy.html#licensing > >Every ASF release MUST comply with ASF licensing policy. This requirement > is of utmost importance > > Vladimir >
Re: [VOTE] Release Apache Wagon version 3.3.4
> Are you referring to his statement of the MIT license? I am Vladimir
Re: [VOTE] Release Apache Wagon version 3.3.4
Am 2019-11-05 um 20:10 schrieb Vladimir Sitnikov: Staging repo: https://repository.apache.org/content/repositories/maven-1535/ -1 since https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar violates licensing terms for the third-party code. One of the violations is org.jsoup:jsoup. Are you referring to his statement of the MIT license? The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Wagon version 3.3.4
Am 2019-11-05 um 20:10 schrieb Vladimir Sitnikov: Staging repo: https://repository.apache.org/content/repositories/maven-1535/ -1 since https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar violates licensing terms for the third-party code. One of the violations is org.jsoup:jsoup. Are you referring to his statement of the MIT license? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Wagon version 3.3.4
Why? jsoup is MIT licensed which is compatible with Apache V2. Manfred Vladimir Sitnikov wrote on 2019-11-05 11:10 (GMT -08:00): >> Staging repo: >> https://repository.apache.org/content/repositories/maven-1535/ > > -1 since > https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar > violates licensing terms for the third-party code. > One of the violations is org.jsoup:jsoup. > > I know releases may not be vetoed ( > https://www.apache.org/foundation/voting.html#ReleaseVotes ) > However, there's > >> http://www.apache.org/legal/release-policy.html#licensing >>Every ASF release MUST comply with ASF licensing policy. This requirement > is of utmost importance > > Vladimir > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Wagon version 3.3.4
> Staging repo: > https://repository.apache.org/content/repositories/maven-1535/ -1 since https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon-http/3.3.4/wagon-http-3.3.4-shaded.jar violates licensing terms for the third-party code. One of the violations is org.jsoup:jsoup. I know releases may not be vetoed ( https://www.apache.org/foundation/voting.html#ReleaseVotes ) However, there's > http://www.apache.org/legal/release-policy.html#licensing >Every ASF release MUST comply with ASF licensing policy. This requirement is of utmost importance Vladimir
Re: [VOTE] Release Apache Wagon version 3.3.4
Am 2019-11-03 um 21:04 schrieb Hervé BOUTEMY: Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12345956=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1535/ https://repository.apache.org/content/repositories/maven-1535/org/apache/maven/wagon/wagon/3.3.4/wagon-3.3.4-source-release.zip Source release checksum(s): wagon-3.3.4-source-release.zip sha512: 1484d17bede842ed45ae3642ccb12f585489a95604fd100a4fddea05e39b0d0471a3d878c8252cc2a29fcdc4f3d2ec0dd25629842ea4443d7557e488b0f3c25f Staging site: https://maven.apache.org/wagon-archives/wagon-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 My upcoming improvements will need more time... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-apache-parent 22 ETA?
Hi Maven devs,
I just wanted to circle back to this. Is the ASF parent POM still
being maintained by the Maven community? And regarding my other
questions, I never got a response. Thanks for any response you can
give.
On Mon, Aug 5, 2019 at 4:14 PM Christopher wrote:
>
> Hi,
>
> In spite of the specific title, I actually have several questions
> (note, I'm not currently subscribed to list, so feel free to CC me
> directly on any responses):
>
> 1. What's the timeline for the maven-apache-parent 22? It seems a bit
> overdue, especially given all the plugins that have been updated since
> 21 was released.
>
> I'm hoping https://github.com/apache/maven-apache-parent/pull/1 gets
> merged in. Can somebody merge that before 22 is released? Two people
> reviewed and approved it 10 months ago.
>
> 2. I had another idea for adding something like the following to
> satisfy the use case for cross-compilation using newer JDKs without
> specifying `-bootstrapclasspath`. Would this be worth a pull request
> (or a committer could just add it if they think it's a good idea).
>
>
> 8
>
>
> jdk-release-flag
>
> [9,)
>
>
> ${compilerCompliance}
>
>
>
> 3. And finally... I noticed that JDK 11's javadoc is not getting the
> backports of the JDK 12 upstream patches... even though 11 is supposed
> to be an LTS version. This causes javadocs generated with
> maven-javadoc-plugin to be broken for projects which aren't using
> modules. Specifically, the following bug appears to not be patched in
> 11 that affect all users of maven-javadoc-plugin. Some plugin goals
> output (such as javadoc:aggregate) can be patched after building, but
> others (javadoc:jar) can't easily be patched, because the broken
> javadoc jar would have to be disassembled to patch and reconstructed.
> Is there a workaround for these planned by the maven-javadoc-plugin
> developers, or is the hope that upstream will fix it eventually?
>
> https://bugs.openjdk.java.net/browse/JDK-8215291 (severe loss of
> functionality when building non-modular code... which is most java
> code today... using JDK 11)
>
> https://bugs.openjdk.java.net/browse/JDK-8227487 (a minor regression
> also not patched in 11)
> https://bugs.openjdk.java.net/browse/JDK-8214856 (another bug, not
> sure how serious, also not patched in 11)
>
>
> Thanks,
>
> Christopher
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
