Howdy,
The vote has passed with the following result:
+1: Michael, Slawomir, Tamas
+0: Elliotte
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file and add this release to the board report.
Howdy,
just FTR:
Aether project was originally created in org.sonatype.aether package
namespace, and was used in Maven 3.0. Later, it moved to Eclipse, and
renamed packages to org.eclipse.aether, and was used in Maven 3.1+.
But, the org.sonatype -> org.eclipse package rename caused havoc in plugi
Looking at 1.9.16 it seems the maven-resolver-api artifact is
org.eclipse.aether. That's an...interesting...design and a little
surprising. I'm not sure what to think about that yet, but at least
it's not a new issue. So I'll upgrade to +0 for now.
On Mon, Nov 6, 2023 at 9:00 AM Elliotte Rusty Ha
On Mon, Nov 6, 2023 at 7:18 AM Konrad Windszus wrote:
>
> The resolver API is only containing classes below org.eclipse.aether for
> historical reasons:
> https://github.com/apache/maven-resolver/tree/master/maven-resolver-api/src
>
Is this still necessary? It seems likely to cause dependency c
The resolver API is only containing classes below org.eclipse.aether for
historical reasons:
https://github.com/apache/maven-resolver/tree/master/maven-resolver-api/src
Konrad
> On 6. Nov 2023, at 13:13, Elliotte Rusty Harold wrote:
>
> -1
>
> I see at least one issue that should be resolved
-1
I see at least one issue that should be resolved before alpha 1.
The API docs at
https://maven.apache.org/resolver-archives/resolver-LATEST/apidocs/index.html
contains docs for aether and for resolver examples but not for the
resolver API itself. Possibly a misconfig in the javadoc generation
+1
czw., 2 lis 2023 o 12:23 Tamás Cservenák napisał(a):
> Howdy,
>
> Note: This is a preview release of Resolver 2.0.0, that would allow any
> downstream consumers to try it out and adapt. Most of the major issues were
> fixed, almost all of the functionality is there (compare JIRA "2.0.0" and
>
+1
On Thu, Nov 2, 2023, 12:23 Tamás Cservenák wrote:
> Howdy,
>
> Note: This is a preview release of Resolver 2.0.0, that would allow any
> downstream consumers to try it out and adapt. Most of the major issues were
> fixed, almost all of the functionality is there (compare JIRA "2.0.0" and
> "2
Am 2023-11-03 um 12:02 schrieb Tamás Cservenák:
Howdy,
@Michael Osipov
Banner removed already: https://issues.apache.org/jira/browse/MRESOLVER-423
Can you point me at issues and/or PRs?
* MRESOLVER-9
* MRESOLVER-8
* MRESOLVER-12
* MRESOLVER-43
* https://github.com/apache/maven-resolver/pull/
Howdy,
@Michael Osipov
Banner removed already: https://issues.apache.org/jira/browse/MRESOLVER-423
Can you point me at issues and/or PRs?
Thanks
T
On Thu, Nov 2, 2023 at 5:29 PM Michael Osipov wrote:
> Am 2023-11-02 um 12:23 schrieb Tamás Cservenák:
> > Howdy,
> >
> > Note: This is a preview
Am 2023-11-02 um 12:23 schrieb Tamás Cservenák:
Howdy,
Note: This is a preview release of Resolver 2.0.0, that would allow any
downstream consumers to try it out and adapt. Most of the major issues were
fixed, almost all of the functionality is there (compare JIRA "2.0.0" and
"2.0.0-alpha-1" ver
Howdy,
Note: This is a preview release of Resolver 2.0.0, that would allow any
downstream consumers to try it out and adapt. Most of the major issues were
fixed, almost all of the functionality is there (compare JIRA "2.0.0" and
"2.0.0-alpha-1" versions).
IF the vote is successful, the staging si
12 matches
Mail list logo
