On Sat, 6 Jun 2020 at 23:08, Elliotte Rusty Harold
wrote:
> maven-dependency-plugin depends on maven-artifact-transfer, and that's
> causing us some trouble, though perhaps that dependency can be removed
> if we can upgrade the dependency plugin to a 3.1 minimum.
>
I guess we can as we
olamy commented on pull request #13:
URL:
https://github.com/apache/maven-artifact-transfer/pull/13#issuecomment-640130752
**NO NEED OF PR FOR THIS**
This is an automated message from the Apache Git Service.
To respond to
Seriously!!
Please commit this directly.
I feel like receiving a lot of spam. Having a PR for this is definitely
useless.
At the end everybody will just configure their email client to filter every
PR to a spam or junk folder.
The risk is to miss/ignore important PR.
-- Forwarded
Hi.
I created a pr 8 days ago.
Is there anyone who interested in giving some suggestions?
jira [MJAVADOC-653], github
https://github.com/apache/maven-javadoc-plugin/pull/48
elharo merged pull request #14:
URL: https://github.com/apache/maven-artifact-transfer/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
maven-dependency-plugin depends on maven-artifact-transfer, and that's
causing us some trouble, though perhaps that dependency can be removed
if we can upgrade the dependency plugin to a 3.1 minimum.
On Sat, Jun 6, 2020 at 8:36 AM Robert Scholte wrote:
>
> I think you already asked this question
I think you already asked this question before, but the answer is no.
The whole idea behind maven artifact transfer was to have a library that made
it possible to support all Maven 3 releases.
Especially when Maven 3.1.0 cam out, several plugins were broken because of the
API change compared to
elharo opened a new pull request #14:
URL: https://github.com/apache/maven-artifact-transfer/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
elharo merged pull request #13:
URL: https://github.com/apache/maven-artifact-transfer/pull/13
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Thanks. Latest master build passed:
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/103/
so I withdraw my -1. I am now at +0 (no opinion) on this release.
On Sat, Jun 6, 2020 at 6:46 AM Hervé BOUTEMY wrote:
>
> this one is a memory issue with H30 node (node name
elharo opened a new pull request #13:
URL: https://github.com/apache/maven-artifact-transfer/pull/13
Deliberately did not file a JIRA issue for this per latest communication
from project lead
This is an automated message
Maven Artifact Transfer has extra dependencies and code related to
org.sonatype.aether to support Maven 3.0.
Is this something we want to support and release or should we rip this
out before going to 1.0? (I don't think this is a blocker for the 0.13
beta release).
--
Elliotte Rusty Harold
this one is a memory issue with H30 node (node name is displayed at the
beginning)
I just pinged infra to fix the node
Regards,
Hervé
Le vendredi 5 juin 2020, 13:27:57 CEST Elliotte Rusty Harold a écrit :
> -1 from me.
>
> Jenkins Build is red:
>
Hi,
We solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12345578=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1587/
14 matches
Mail list logo
