-
Notifications
You must be signed in to change notification settings - Fork 10
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
No javadoc and sources avaliable for 2.7.1 #4
Comments
Is this still required? |
As you can see there are no Javadoc and source artifacts for plexus-io 2.7.1 (http://central.maven.org/maven2/org/codehaus/plexus/plexus-io/2.7.1/), while for the previous versions there are (http://central.maven.org/maven2/org/codehaus/plexus/plexus-io/2.7/). It's not something important, especially given the fact that 3.0.0 is going to be released soon. |
I do not even understand how this passed oss.sonatype.org checks. |
2.7.1 is generally broken if you take a closer look. No file is GPG signed. I will do the following now: I will branch off before Java 7, and release 2.7.2. It that OK for you? |
Yes. Thanks.
…On May 10, 2017 21:45, "Michael Osipov" ***@***.***> wrote:
2.7.1 is generally broken if you take a closer look. No file is GPG
signed. I will do the following now. I will branch off before Java 7, and
release 2.7.2. It that OK for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMLobb1rpxk-55K5bj1TC3cB7yROY7LJks5r4gXOgaJpZM4JDdYO>
.
|
It pretty much looks like Plexus IO is unreleasable on Windows:
|
Artifacts on their way. |
2.7.2 is on central and supersedes 2.7.1. Issue solved. |
Hi,
It looks like the Javadoc and source artifacts are not available from the Maven repo for plexus-io 2.7.1.
The text was updated successfully, but these errors were encountered: