Howdy,
We fixed several issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRAR%20AND%20fixVersion%20%3D%203.0.0
Staged repository:
https://repository.apache.org/content/repositories/maven-1782
Source release SHA512:
661a4ff1f12970f86e481c219dd08f072d85f13b3f7e27adef57cf5de940030
Howdy,
We fixed one bug:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-common-artifact-filters-3.3.1
Staged repository:
https://repository.apache.org/content/repositories/maven-1783
Source release SHA512:
f88c5d5537a80bc8bde69aafdf38fc34608eb
+1
On Sat, Jul 16, 2022 at 6:00 PM Tamás Cservenák wrote:
> Howdy,
>
> We fixed one bug:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINDEXER%20AND%20fixVersion%20%3D%206.2.2
>
> Staged repository:
> https://repository.apache.org/content/repositorie
Howdy,
The vote has passed with the following result:
+1 : Sylwester, Michael, Guillaume, Slawomir, Karl-Heinz and me
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Karl-Heinz, Romain, Guillaume
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Karl-Heinz, Romain, Guillaume and me
-1 : Václav (nb)
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Indexer 6.2.2.
Site: https://maven.apache.org/maven-indexer/
Release Notes - Maven Indexer - Version 6.2.2
** Bug
* [MINDEXER-164] - IndexOutOfBoundsException during indexing of
repositories files
Have fun
- The Apac
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Install Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.2.5+
Site: https://maven.apache.org/plugins/maven-install-plugin/
===
NOTE: Release 3.0.0 has a regression related to install-file Mojo that
slipped r
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Deploy Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.2.5+
Site: https://maven.apache.org/plugins/maven-deploy-plugin/
Release Notes - Maven Deploy Plugin - Version 3.0.0
** Bug
* [MDEPLOY-193] - depl
Howdy,
We fixed one regression in install-file Mojo
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20AND%20fixVersion%20%3D%203.0.1
Staged repository:
https://repository.apache.org/content/repositories/maven-1784
Source release SHA512:
bb2b4216ba0da11f6de4a9c02921a92839a3e0e
Howdy,
Running or building?
As for building, I am all for it.
For running (so the bytecode level of built Maven artifacts) may be "too
soon" IMHO, I am unsure about this.
Hence, I'd go with enforcer to require JDK17, but use compiler release=11
for now.
Note: key component, like sisu inject doe
@Anders I'd stop using the "run on for what you build for" aspect. We will
have to split it IMHO. It caused a lot of luggage for us in the past (we
still release Java 7 plugins in 2022).
Instead, I think we need to simplify toolchains for users, and make it
clear for them that for their benefit (b
t 7:03 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> On 19.07.22 18:48, Tamás Cservenák wrote:
> > @Anders I'd stop using the "run on for what you build for" aspect. We
> will
> > have to split it IMHO. It caused a lot of luggage for us in the past (we
> > still
; see many fals positive fails on such node ...
>
> Next step can be stop building PR by jenkins - it is only triggered for
> dependabot and for branch from repo - not triggered for build PR for forked
> repo.
>
> sob., 2 lip 2022 o 21:42 Tamás Cservenák napisał(a):
>
> >
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz, Guillaume
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The vote has passed with the following result:
+1 : Michael, Sylwester, Karl-Heinz, Guillaume
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
Thanks
T
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Rar Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.3.9+
Site: https://maven.apache.org/plugins/maven-rar-plugin/
Release Notes - Maven RAR Plugin - Version 3.0.0
** Bug
* [MRAR-41] - Update plexus-inte
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Remote Resources Plugin 3.0.0.
Plugin is Java7 level and compatible with Maven 3.2.5+
Site: https://maven.apache.org/plugins/maven-remote-resources-plugin/
Release Notes - Maven Remote Resources Plugin - Version 3.0.0
** I
Howdy,
The Apache Maven team is pleased to announce the release of
Maven Shared Maven Common Artifact Filters 3.3.1 component.
Site: https://maven.apache.org/shared/maven-common-artifact-filters/
Release Notes - Maven Shared Components - Version
maven-common-artifact-filters-3.3.1
** Bug
* [
Bah, that was me:
https://github.com/apache/maven-remote-resources-plugin/commit/66b6074ef1715f1198fbee13bf8673a495f20319#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L73
T
On Wed, Jul 20, 2022 at 1:48 PM Piotr Żygieło
wrote:
> > Howdy,
> >
> > The Apache Maven team is p
Created https://github.com/apache/maven-remote-resources-plugin/pull/8
On Wed, Jul 20, 2022 at 1:56 PM Tamás Cservenák wrote:
> Bah, that was me:
>
> https://github.com/apache/maven-remote-resources-plugin/commit/66b6074ef1715f1198fbee13bf8673a495f2
Howdy,
The master branch is ready for 3.4.2
https://github.com/apache/maven-assembly-plugin
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20fixVersion%20%3D%203.4.2
Anyone?
Thanks
Tamas
+1
On Wed, Jul 20, 2022 at 7:18 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12351652
>
> Changes since the last release:
>
> https://github.com/apache/maven-parent/compare/maven-parent-36...mave
+1
On Wed, Jul 20, 2022, 22:10 Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352050
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MS
+1
On Wed, Jul 20, 2022, 23:50 Michael Osipov wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220&version=12352095
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MA
+1
On Tue, Jul 19, 2022, 16:26 Tamás Cservenák wrote:
> Howdy,
>
> We fixed one regression in install-file Mojo
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20AND%20fixVersion%20%3D%203.0.1
>
> Staged repository:
> https://repository.apache.
+1
On Mon, Jul 25, 2022, 19:23 Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12351875
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MR
Don't mix in plexus (is dead). You need Guice spi TypeConverter.
T
On Fri, Jul 29, 2022, 16:22 Romain Manni-Bucau
wrote:
> Hi Konrad,
>
> Guess what you are looking for is
>
> https://github.com/eclipse/sisu.plexus/blob/27a29dc633e6b03753a3c8d29a033648630c8831/org.eclipse.sisu.plexus/src/org/ec
+1
On Thu, Jul 28, 2022, 21:02 Michael Osipov wrote:
> Hi,
>
> We solved 24 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12351598
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/SCM/issues
>
> Staging
+1
On Fri, Jul 29, 2022, 22:31 Michael Osipov wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352152
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSH
+1
On Sun, Aug 7, 2022, 00:00 Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352179
>
> There are no issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20re
+1
On Wed, Aug 10, 2022, 21:28 Michael Osipov wrote:
> Hi,
>
> we solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12352097
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging
+1
On Wed, Aug 10, 2022, 22:12 Michael Osipov wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12352053
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MJAVADOC/issues
>
> Sta
+1
On Sat, Aug 20, 2022 at 9:01 AM Michael Osipov wrote:
> Hi,
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12345559
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+M
+1
On Sat, Aug 20, 2022 at 5:37 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12342991
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%2
+1
On Sat, Aug 20, 2022 at 9:15 AM Michael Osipov wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621&version=12351813
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
Howdy,
In maven 3 the only way to do this is using Resolver API directly (your 3.
bullet). Now, as there was a mess between 3.0 and 3.1 (resolver package
change), MAT (maven-artifact-transfer) was introduced to fix the gap (using
reflection), but I hope Maven 3.0 can be really considered as
"dead/
Howdy,
VersionResolver component?
HTH
T
On Fri, Aug 19, 2022 at 9:20 PM Slawomir Jaranowski
wrote:
> Hi
>
> Interface ArtifactMetadataSource [1] is deprecated - what is
> replacement for it?
> especially for method retrieveAvailableVersions
>
>
> [1]
>
> https://maven.apache.org/ref/3.8.6/apid
resolver/apidocs/org/eclipse/aether/impl/VersionResolver.html
> > but it is not what I need ...
> >
> > I need to discover all available versions of artifacts.
> >
> >
> >
> > niedz., 21 sie 2022 o 00:49 Tamás Cservenák
> > napisał(a):
> >
&g
+1
On Sun, Aug 21, 2022, 16:55 Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12351759
>
> There are no issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AN
Howdy,
If one would choose the version layout "that happens" to be like you
describe, that would be really unfortunate.
The "timestamped snapshot version" was introduced in (very late) Maven2
AFAIR, Maven 3.0 allowed turning it off (while defaulted to using it), and
-- again AFAIR, someone correc
+1
On Thu, Sep 1, 2022, 12:07 Andreas Dangel wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352255&styleName=Text&projectId=12317621
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=proj
+1
Looks good to me, inspected Linux zip content, used it on some projects,
worked OK
Tested on Linux Fedora 36 w/ Java 17 Temurin and several Maven projects...
One minor bug detected: https://github.com/apache/maven-mvnd/issues/685
T
On Thu, Sep 8, 2022 at 3:13 PM Guillaume Nodet wrote:
> I
+1
On Mon, Sep 12, 2022, 18:04 Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12351126
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
+1
On Sun, Sep 11, 2022, 12:38 Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12351491
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
+1
On Mon, Sep 12, 2022, 21:26 Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352116
>
> There are still one issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHAR
+1
On Thu, Sep 22, 2022, 22:38 Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12352314
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3
Howdy,
you did not specify what is what you exactly look for but in general:
definitely avoid maven-compat (maven2 support).
Your best bet is to:
- NOT support older Maven then 3.1, then you save yourself from
aether/resolver package change (so no need for things like
https://github.com/apach
gt;
> and
>
>
> org.apache.maven.repository.RepositorySystem.resolve(ArtifactResolutionRequest)
>
> calls ...
>
>
> Am 26.09.22 um 12:47 schrieb Tamás Cservenák:
> > Howdy,
> >
> > you did not specify what is what you exactly look for but in gene
Howdy,
Some (historical) clarification here:
The sisu-build-api has existed since 2009, but was _abandoned_ since by its
initial author as being "incomplete".
Also, that repo has been _archived_ since the 2010-ish year, also many
years ago (I think it was longer archived than not).
Not long ago,
Howdy Mathias,
well, first to clear up: maven-resolver does NOT support operations like
"resolve me this artifact HERE". The "local repository" is coupled with it,
and resolution of artifacts always happens from remote to local repository,
and then the result handles you the java.io.File of the re
Howdy,
It should not break, but if it does, we did something wrong.
The new API will coexist with old stuff, so in essence Maven 3 plugins
should not break with Maven 4, as long Maven 4 provides this "backward 3.x
compat window"
(but no Maven2 compat anymore, we cannot provide two major versions
://github.com/apache/maven-resolver/pull/183
Thanks
T
On Tue, Oct 4, 2022 at 1:51 PM Gary Gregory wrote:
> Does Maven and it's own plugins use JApiCmp or any tool to detect binary
> compatibility breaks?
>
> Gary
>
> On Tue, Oct 4, 2022, 06:53 Tamás Cservenák wrote:
>
&g
+1
Tested on several in-house (maven, maven-resolver) and some of external
little bigger projects, seems fine
No more flickering on download ;)
T
On Tue, Oct 4, 2022 at 9:50 AM Guillaume Nodet wrote:
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/0.
Howdy,
just one remark: as I said, Maven so far never had a "surface" meant to be
an API, on the other hand Maven tries its best to "signal" internal areas.
In this very example
org.apache.maven.lifecycle.internal.MojoDescriptorCreator the package name
is "internal" (sometimes impl, etc). The inte
Howdy,
+1 for release alpha
-1 (not vote but opinion) for snapshots in builds -- but I could live with
it
T
On Wed, Oct 12, 2022 at 9:57 AM Maarten Mulders
wrote:
> Hi all,
>
>
> TL;DR: +1 for releasing an "4.0.0-alpha-1".
>
>
> I think that an "alpha-1" could also be of value for end users. T
+1 for this. Tested on resolver, that has many old/untouched and hence,
badly formatted sources.
T
On Wed, Oct 12, 2022, 18:23 Guillaume Nodet wrote:
> I'd like to propose merging the following PRs:
> * https://github.com/apache/maven-shared-resources/pull/1
> * https://github.com/apache/mave
+1 for this formatting change.
T
On Wed, Oct 12, 2022, 18:23 Guillaume Nodet wrote:
> Related to the discussion about automatically formatting and sorting
> imports, I think it would be nice, given the big reformat commits if those
> PRs are to be merged, to eventually discuss some changes to
Formatting happens during build, so once merged all we need is to merge
master into PR branches...
T
On Thu, Oct 13, 2022 at 8:40 AM Sylwester Lachiewicz
wrote:
> What about already open PR with some features or bug fixes.
> Don't we should review and merge it before reformatting code - otherwi
and that
CI build did reformat them...
But even without this step mitigation is simple: someone just rebuilds HEAD
and commits...
Thanks
T
On Thu, Oct 13, 2022 at 8:41 AM Tamás Cservenák wrote:
> Formatting happens during build, so once merged all we need is to merge
> master into PR
To answer my own question:
https://maven.apache.org/scm/maven-scm-plugin/check-local-modification-mojo.html
T
On Thu, Oct 13, 2022 at 9:47 AM Tamás Cservenák wrote:
> Howdy,
>
> to not get lost in implementation details, it is really unimportant
> (spotless, this or that...)
On Thu, Oct 13, 2022 at 6:26 PM David Jencks
wrote:
> A possible data point… For a while I worked on isomorphic-git (javascript)
> which had a pre-commit hook to format the code. It was rather surprising at
> first, but I ended up really liking it, more than projects that attempted
> to check the
On Thu, Oct 13, 2022 at 6:36 PM Slawomir Jaranowski
wrote:
> +1 for simply checking during build, formatting should be done by
> developer, nevermind if using plugin or by IDE
> It can work like checkstyle.
>
>
This is where we are today. And "done by developer" is either IDE, either
some tool, a
Howdy,
On Thu, Oct 13, 2022 at 1:55 PM Jeff Jensen <
jeffjen...@upstairstechnology.com> wrote:
> I think reformatting files during every build is less desirable and adds
> risk. I prefer the build to *enforce* the desired results, failing as
> needed, and configuring the IDEs to auto-format the
et wrote:
> > Le jeu. 13 oct. 2022 à 12:50, Olivier Lamy a écrit :
> >
> >> On Thu, 13 Oct 2022 at 17:47, Tamás Cservenák
> wrote:
> >>>
> >>> Howdy,
> >>>
> >>> to not get lost in implementation details, it is really unimpor
Howdy,
On Thu, Oct 13, 2022 at 12:50 PM Olivier Lamy wrote:
> Then in case of failure, the committer can just run
> foo-bar-formatted-plugin:format.
>
>
Why on earth yet another _manual_ step in all this process?
"in case of failure committer run" part would not exist in this story,
that's t
+1 works ok for me on several projects
T
On Sat, Oct 15, 2022 at 2:19 AM Guillaume Nodet wrote:
> I've staged a release candidate at
> https://repository.apache.org/content/repositories/maven-1811
>
> The binaries are available at:
>
>
> https://repository.apache.org/service/local/repositorie
+1
On Tue, Oct 18, 2022, 19:38 Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422&version=12349537
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3
Slawek,
Are you sure those issues still stand for 3.0.x of plugins?
T
On Wed, Oct 19, 2022, 22:07 Slawomir Jaranowski
wrote:
> Hi,
>
> I'm looking for how to resolve issues connected with the feature
> installAtEnd / deployAtEnd of install and deploy plugins.
>
> We have a similar feature in
eploy plugin to
> none phase in one of modules.
>
>
>
> śr., 19 paź 2022 o 22:59 Tamás Cservenák napisał(a):
>
> > Slawek,
> >
> > Are you sure those issues still stand for 3.0.x of plugins?
> >
> > T
> >
> >
> > On Wed, Oct 19, 202
Howdy,
an example solution, please verify it:
https://github.com/apache/maven-install-plugin/pull/38
T
On Thu, Oct 20, 2022 at 9:21 AM Slawomir Jaranowski
wrote:
> czw., 20 paź 2022 o 09:04 Tamás Cservenák
> napisał(a):
>
> > Howdy,
> >
> > I cannot reproduce a
Howdy
On Thu, Oct 20, 2022 at 9:21 AM Slawomir Jaranowski
wrote:
> You are right - issues should be closed - I will review it.
>
>
Be careful, many reproducers are INCOMPLETE.
For example, MINSTALL-102 attached test.zip is WRONG:
it mixes m-install-p versions from pom packaging and maven-archety
Howdy,
created PR that should restore compatibility, moreover, it remains mvn 3
and 4 compatible
(and some little cosmetic change to plexus xml)
https://github.com/repaint-io/maven-tiles/pull/133
Thanks
T
On Thu, Oct 20, 2022 at 1:37 AM Mark Derricutt wrote:
> Trying out the new 4.0.0-alpha-2
+1
Btw, maven-indexer is 11.
Tia
T
On Sat, Oct 22, 2022, 21:44 Guillaume Nodet wrote:
> Given maven and the resolver have upgraded their minimum JDK requirement to
> 1.8, I think it makes sense to raise it globally in the parent pom.
>
> Any objections ?
>
> Cheers,
> Guillaume Nodet
>
Howdy,
The 1.9.0 release is near being complete:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.0
If anyone has anything to add, please let me know.
Thanks
T
Howdy,
I already thought about this, and probably shared some thoughts (that may
have slipped, or did not share on ML?).
In short: personally, I consider these "resolver configurations" LOW LEVEL
settings that ARE exposed to those users who are adventurous, but in
general, Maven should provide sa
we can allow in profiles/profile/properties maven.resolver.*?
>
> maven.resolver.transport - native can benefit with - "included checksums"
> [1]
>
> I think that options like aether.enhancedLocalRepository.split* can be
> attractive for users
>
> [1] https://maven.apache.o
+1
On Tue, Oct 25, 2022 at 9:58 PM Michael Osipov wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12352129
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/SCM/issues
>
> Stag
+1
On Sat, Oct 29, 2022, 19:37 Michael Osipov wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12351828
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MRELEASE/issues
>
> Sta
Howdy,
Will we keep asking the same questions over and over again? Until we get
the "wanted" answer?
Maven core and ecosystem uses SLF4J API. Full stop.
Just use SLF4J API, and you will get a pre-configured back-end as well.
Done.
Now,. this story keeps popping up: "plugin developers using fram
Le ven. 4 nov. 2022 à 13:17, Tamás Cservenák a
> écrit :
>
> > Howdy,
> >
> > Will we keep asking the same questions over and over again? Until we get
> > the "wanted" answer?
> >
> > Maven core and ecosystem uses SLF4J API. Full stop.
> &
+1
On Thu, Oct 27, 2022, 13:11 Guillaume Nodet wrote:
> Hi,
>
> I've staged a release of Maven Build Cache Extension 1.0.0.
> This is the first release of this component.
>
> Solved issues:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820&version=12351243
>
> JIRA
+1
On Sun, Oct 30, 2022 at 11:02 AM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 42 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project
Yup, am still on vacation so briefly...
Jira issues should more or less be up to date, with fixFor set to 6.0.
Martin was great help with fixing indexer issues and de-plexusizing it as
well.
thanks (phone),
~t~
On Aug 19, 2014 10:15 AM, "Martin Todorov" wrote:
> Hi Barrie,
>
> Nice to hear bac
Hi there,
Index already contains the SHA1 sums of _indexed_ artifacts (if available).
It all depends only on how up-to-date index is (is just released artifacts
might not be on index yet...)
HTH,
~t~
On Wed, Aug 27, 2014 at 4:49 PM, Bernd Eckenfels
wrote:
> Hello Jason,
>
> a somewhat related
Examples fixed with 2c916cbdaf9ec79e5f66ecbb85b6bd80ad302152.
Please update.
thanks (phone),
~t~
On Aug 28, 2014 7:55 PM, "Martin Todorov" wrote:
> Oh, you're right! This seems to have been broken by a recent merge.
>
> I believe 7d5ed7af1eff148ab509ae8c89d61f936e37bf2a should be a safe
> revis
I do plan to parachute in as last year...
As am unsure about kidnapping this year, but having beers (or alike) is
something I still can guarantee :)
On Sat, Sep 19, 2015 at 12:17 PM Tibor Digana
wrote:
> I have booked the room in conference's hotel, so anybody will find me
> there easily.
> I ar
+1
On Sun, Sep 20, 2015 at 9:41 PM Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> +1
>
> 2015-09-17 22:12 GMT+02:00 Tibor Digana :
> > Hi,
> >
> > We solved 4 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12332813
> >
> > There are st
+1 retire it
On Sun, Oct 4, 2015, 17:01 Arnaud Héritier wrote:
> +1 to retire it from Apache and to give it to MojoHaus where contributions
> are easier if some users want to give him some love.
>
> On Sun, Oct 4, 2015 at 11:18 AM, Robert Scholte
> wrote:
>
> > Hi,
> >
> > during the latest upg
Yup, checksum validation != content validation, the latter may become
tricky...
On Tue, Oct 6, 2015 at 3:43 PM Anders Hammar wrote:
> That ticket is not about the root cause I think.
>
> /Anders (mobile)
> Den 6 okt 2015 15:36 skrev "Michael Osipov" <1983-01...@gmx.net>:
>
> >
> >
> > > Gesendet
Howdy,
it seems I have no powers to manage MI mirror at
https://github.com/apache/maven-indexer
Could someone help here, or this is infra issue?
Thanks,
~t~
--
Thanks,
~t~
+1
On Wed, May 24, 2017, 23:42 Manfred Moser wrote:
> Lgtm +1
>
> Igor Fedorenko wrote on 2017-05-24 14:38:
>
> > I'd like to ask for somebody to second my change described in
> > [MNG-6233]. The change cleans up mixture of jsr330 and plexus
> > annotations used in maven-resolver-provider, leavi
+1
On Mon, Jul 3, 2017 at 9:04 PM Hervé BOUTEMY wrote:
> +1
>
> Regards,
>
> Hervé
>
> Le vendredi 30 juin 2017, 22:12:35 CEST Michael Osipov a écrit :
> > Hi,
> >
> > We solved 15 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&ve
> > rsion=12339212 <(1)%
[VOTE] Release Maven Indexer 6.0.0
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12330802
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MINDEXER/issues/MINDEXER-81?filter=allopenissues
Stagin
My 5c:
>From "Failed to create parent directories"...
Local repo directory ownership/permissions?
HTH,
T
On Tue, Nov 28, 2017 at 7:21 PM Tibor Digana wrote:
> The settings.xml:
>
>
> http://maven.apache.org/SETTINGS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
@Brian @Olivier
Release 6.0.0 is perfectly compatible backwards, so no need to publish with
6.0.0 to consume it with 6.0.0. The changed creators (like OSGi) were
anyway unused on central AFAIK, central publishes with "min" set of
publishers.
@Andreas
thanks!
Vote passed with +1's from: Olivier, H
The Apache Maven team is pleased to announce the release of the Apache
Maven Indexer, version 6.0.0
Apache Maven Indexer (former Sonatype Nexus Indexer) is the defacto
standard for producing indexes of Maven repositories. The Indexes are
produced and consumed by all major tools in the ecosystem.
Hi,
The vote has passed with the following result:
+1 : Olivier, Herve, Robert, Manfred, Eric and Andreas
PMC quorum: Olivier, Herve, Robert
I will promote the artifacts to the central repo.
Thanks,
T
--
Thanks,
~t~
Hi there,
you are, but without this
https://issues.apache.org/jira/browse/MINDEXER-81
you will get hardly any progress (without getting very "dirty" wrt code and
incompatible).
HTH,
Tamas
On Thu, Feb 15, 2018 at 11:29 PM Sylvain Lacaze wrote:
> Hi all,
>
> I was hoping to get a little bit of g
301 - 400 of 1468 matches
Mail list logo
