+1
On Thu, Jul 4, 2013 at 11:18 AM, Baptiste MATHUS wrote:
> +1 (non-binding)
>
>
> 2013/7/1 sebb
>
> > On 1 July 2013 03:56, Barrie Treloar wrote:
> > > On 1 July 2013 06:52, sebb wrote:
> > >> Another problem: the NOTICE file contains the following spurious text:
> > >>
> > >>
> >
> =
+1 nb
On Jul 23, 2013 4:00 PM, "Stephen Connolly"
wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to
Hi,
it seems in 3.1.x, since Aether was swapped from Sonatype one to Eclipse
one, the filtering was not updated, and Eclipse Aether is getting into
plugin Class Realms...
See
https://github.com/apache/maven/blob/892b464683645bcdc1d28febf0bf3cc1c3181350/maven-core/src/main/java/org/apache/maven/De
Hi,
We solved 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&version=19092
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC
Staging repo:
h
Vote closed. Results:
+3 binding (Olivier, Robert and Hervé).
Will continue with release.
Thanks,
~t~
On Sun, Sep 15, 2013 at 8:31 AM, Hervé BOUTEMY wrote:
> +1
>
> tested with Maven core and ITs
>
> Regards,
>
> Hervé
>
> Le jeudi 12 septembre 2013 13:29:32 Tamás
The Apache Maven team is pleased to announce the release of the Apache
Maven Wagon, version 2.5
Maven Wagon is a transport abstraction that is used in Maven's artifact and
repository handling code.
Site
http://maven.apache.org/wagon/
To make use of it, you may override the Wagon version with ext
Hi Arnaud,
I could not reproduce this, but instead DAV Wagon threw CNFEx... (but it
did kick in).
Actually, this is in line with maven 3.0.4, as it behaves the same.
In both cases commons logging LogFactory class was missing, but I have no
clue from where it should come, as from wagon-webdav POM
+1 tried on Nexus builds (with modded nx plugin in build, that updates
Aether to Eclipse one).
On Thu, Sep 26, 2013 at 8:21 AM, Wayne Fay wrote:
> +1 binding
> Finally gave it a shot last night after your reminder email, works
> well on various projects I tested it with.
>
> Wayne
>
> On Wed, S
+10 for markdown and getting rid of old formats. Markdown is really easy,
and as Jason says, tooling for editing it is really superb.
Thanks,
~t~ (mobile)
On Oct 5, 2013 5:19 PM, "Jason van Zyl" wrote:
> We current have multiple formats for our site documentation and two of
> them no one else in
Hi there,
I am toying with some thoughts to make a bigger leap with MI. I plan to
start 6.0 of it, with following changes:
Changes would be along these lines:
- Collapse indexer-artifact into indexer-core (this modularization had a
historical reason, coming from Sonatype Nexus)
- Remove Maven1 su
+1
downloaded the staged release zip, checksum matches, is buildable to me.
On Tue, Dec 3, 2013 at 3:35 PM, Igor Fedorenko wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11761&version=19029
>
> There are still a couple of issues left in JIR
Don't want to stir too much here, but the
http://oi41.tinypic.com/33bctw2.jpg
is typographically incorrect (odd kerning and odd/different typeface).
Long time ago I made vector based Maven logo (for Proximity site) that I
thought I donated to Maven project...
That one could serve as a great start
down the interwebs from apache using Tamás's
> > text
> > > > >
> > > > > http://people.apache.org/~stephenc/maven-logo-contest/maven.png
> > > > >
> > > > > And a screenshot with it
> > > > >
> > > > >
> http:/
Here is an example, same as proposed by Igor
https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/AbstractStagingMojo.java#L72
Still, you need to be careful if you want maven 2.x, maven 3.0.x and maven
3.1.x compatibility,
I did the last 2.5 one, that had two major problems: 2G file limit and
httpclient 4.x pool pollution problem
As I see, there are 3 issues solved
http://jira.codehaus.org/issues/?jql=project%20%3D%20WAGON%20AND%20fixVersion%20%3D%20%222.6%22%20AND%20status%20%3D%20Closed%20ORDER%20BY%20priority
As i mentioned in referenced thread, i would really like to see maven at
java7.
We talk about release to happen in near future, that would be used in a bit
further future by users, but even _today_ there is no other java than 7
that is not eol-d. For those locked in, there are still 3.0, 3.1 relea
I missed jvz's question: yes for removal of deprecations eagerly. If
anything, we should start doing that eagerly (4 years?), and declare this
step as transitioning one toward 4.0?
thanks,
~t~ (mobile)
On Jan 5, 2014 11:29 AM, "Tamás Cservenák" wrote:
> As i mentioned in re
Jason,
a bit off topic, but you mention that "if last reactorProject" type logic
breaks badly in parallel mode.
Any pointers how to fix/replace it?
Thanks,
~t~
On Thu, Feb 6, 2014 at 4:05 PM, Jason van Zyl wrote:
> Hi,
>
> I made a first pass at coalescing the logic for a specific way to b
+1
On Tue, Feb 11, 2014 at 3:22 AM, Jason van Zyl wrote:
> +1
>
> ---
>
> Analyzer...
>
> stagingUrl: https://repository.apache.org/content/repositories/maven-1005
> groupId: org.apache.maven
> artifactId: apache-maven
> version: 3.2.0
>
> Source ZIP url exists.
>
> https://repository.apache.or
Maybe related to https://jira.codehaus.org/browse/MNG-5513 ?
As cdi-api is now also in core?
Thanks,
~t~
On Thu, Feb 13, 2014 at 8:28 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> Stuart,
>
> We're seeing java.lang.LinkageError: loader constraint violation: loader
> (instanc
+1
On Thu, Feb 13, 2014 at 4:30 PM, Anders Hammar wrote:
> +1
>
> /Anders
>
>
> On Thu, Feb 13, 2014 at 4:14 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > We have not made a release of Maven 2.x since 2.2.1 which was August
> 2009.
> >
> > During that period no release
Install at end of m-install-p has problems related to aggregator POMs for
example, here is an example plugin that will NOT install anything than the
aggregator POM (attached).
If you have such set up, it will fail. Simply put, the m-install-p install
mojo blindly expects it will get invoked for _e
Yeah, I just wanted to show one example.
The point is that install mojo is not invoked for all projects in the
build, as expected, and will never kick in to install the accumulated
projects:
https://github.com/apache/maven-plugins/blob/8678f791e717c14f6b91b80fade0a376ac87625a/src/main/java/org/ap
Re MNG issue links... they are in codehaus Jira. Just prepend the "
http://jira.codehaus.org/browse"; to them.
Like
http://jira.codehaus.org/browse/MNG-5102
On Tue, Apr 1, 2014 at 11:51 AM, Alexander Kriegisch <
alexan...@kriegisch.name> wrote:
> Thanks Anders,
>
> so part of my question is ans
Howdy,
module "maven-project" was removed as part of Maven3 changes/refactoring
(but as you noted, was still present in some early alphas).
Just compare the two diagrams, and you will see that "project" module is
gone:
http://maven.apache.org/ref/2.2.1/
http://maven.apache.org/ref/3.2.1/
It's mo
go for it
On Tue, Apr 15, 2014 at 8:40 AM, Olivier Lamy wrote:
> Hi,
>
> Someone with a strong opposition to move maven-indexer code to git?
> If no one complains within 72H, I will ask migration to infra.
>
> Cheers,
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/ola
+1
On Tue, Apr 29, 2014 at 9:17 AM, Arnaud Héritier wrote:
> Hi all,
>
> Is there someone against the idea to create a dedicated ML to receive
> commit notifications for website updates ?
> I'm tired to receive this SPAM that are filling my inbox each time we
> release a project and it's not
Seems fine to me (true, I have no karma to edit, but logged in and pageload
is quite fast).
Thanks,
~t~
On Fri, May 23, 2014 at 2:30 PM, Jason van Zyl wrote:
> For the last few days the instance seems to be in distress. Anyone else
> having issues?
>
> Thanks,
>
> Jason
>
> --
+1
thanks,
~t~ (mobile)
On Jun 11, 2014 7:54 AM, "Kristian Rosenvold"
wrote:
> I've been considering attending apachecon in Budapest, and I would be
> really interested in creating a meet up to discuss "future maven" (for
> one or more days). It would be interesting to see if we'd be capable
> o
I could not make it for hangout, and got a message by google that hangout
was canceled?
Where is a link of the recording, if any?
Thanks,
~t~
On Thu, Jun 19, 2014 at 3:40 PM, Jason van Zyl wrote:
> We had the hangout yesterday. I pushed the initial bit of information
> about evolving the POM
Ah, both localhost and recording problem solved. The proper link is
http://takari.io/2014/06/19/hangout-pom-format.html
On Thu, Jun 19, 2014 at 3:45 PM, Tamás Cservenák
wrote:
> I could not make it for hangout, and got a message by google that hangout
> was canceled?
>
> Where
I did not make it for the first one, but watched the recording.
One topic I'd like to propose is about thing mentioned at very last minutes
of the recording: repository tags in POM, "smarter protocol" between Maven
and MRM, etc
Should we have some wiki with topic proposals maybe?
Thanks,
~t
In Plexus, you can make the plexus component "prototype" (as opposite of
current singleton) by adding
instantiationStrategy="per-lookup"
in that case, Plexus container will create new instance of the component
for every injection/lookup.
On Fri, Jun 20, 2014 at 1:20 PM, Karl Heinz Marbaise
w
Hi there,
finally got to sort out some changes, among other is Lucene bump. Due to
that change, MI6 (heh) on master is now Java7...
I'd like to ask someone with enough power to update the Jenkins job.
Currently it consistently fails as it uses Java6.
https://builds.apache.org/job/maven-indexer/
Thanks Robert!
Thanks,
~t~
On Sat, Jun 28, 2014 at 5:49 PM, Robert Scholte
wrote:
> Done,
>
> Robert
>
> Op Sat, 28 Jun 2014 17:32:45 +0200 schreef Tamás Cservenák <
> ta...@cservenak.net>:
>
>
> Hi there,
>>
>> finally got to sort out some change
Yes. But repo IDs are meaningless imo, urls are a bit better (as Igor
mentioned, could be used as uris, sorta).
Nx even today stores all the urls a cached artifact was downloaded in its
own attributes (you can check it with ?describe request). The only problem
currently is that if you access repo
+1 (binding) works OK on system/openjdk that initially made me report
SUREFIRE-1588 in the first place.
On Fri, Nov 2, 2018 at 5:00 PM Tibor Digana wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
>
> There are st
+1
On Sun, Nov 4, 2018, 11:48 Tibor Digana Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+stat
+1
On Sat, Nov 10, 2018, 23:50 Olivier Lamy My +1
>
> @Tibor https://markmail.org/message/u465ivo46osuskhi
>
> On Sun, 11 Nov 2018 at 02:48, Tibor Digana wrote:
>
> > +1
> > I do not see the previous history in this vote.
> >
> > On Sat, Nov 10, 2018 at 2:34 PM Robert Scholte
> > wrote:
> >
> >
+1
T
+1
On Wed, May 15, 2019, 22:33 Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our am
Just wondering: what stops you developing on more modern java, and
targeting older java? Or in other words, why is using target java a must on
development? Just curious.
Ps: sry for jumping the thread
On Mon, Jun 3, 2019, 16:48 Elliotte Rusty Harold wrote:
> I know there are plenty of places at
te:
> Java 8 uses a different major version number in the .class file than
> Java 7. Generally a Java 8 .class file can't be loaded into a Java 7
> VM. In this case, I think dom4j would have to compile for Java 7 for
> the dom4j.jar to load into Java 7.
>
> On Tue, Jun 4
Just fyi, am aware of 3+2 oss solutions out there (the +2 are the trimmed
ones)
On Sat, Jul 6, 2019, 00:26 dzikoysk (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/MNG-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879546#comment-168
+1
On Wed, Aug 7, 2019, 21:13 Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects,
> including our ambi
+1
On Thu, Aug 15, 2019 at 1:53 PM Tibor Digana wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12345950
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+MRE
+1
On Mon, Aug 19, 2019, 22:50 Tibor Digana wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12345957
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCH
+1
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects,
> including our
+1
On Wed, Aug 28, 2019 at 9:18 PM Enrico Olivelli wrote:
> Hi,
>
> We have solved 52 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12345234
>
> There are issues left in JIRA for Maven core:
>
> https://issues.apache.org/jira/issues/?jql=project%20
FYI,
And just to confirm, HU mirror lost 3.6.1 as well.
T
-- Forwarded message -
From: 'Jörg Hohwiller' via mojohaus-dev
Date: Tue, Sep 3, 2019 at 7:13 PM
Subject: maven download broken on all mirrors
To: mojohaus-dev
Hi there,
may be wrong here but I unsubsribed from maven-d
+1
On Mon, Sep 9, 2019, 04:01 Olivier Lamy wrote:
> Hi
> I'd like to release Apache Maven Invoker Plugin version 3.2.1.
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344863&styleName=Text&projectId=12317525&Create=Create
>
> Staged repository:
> https
Hi there,
just a shot in a dark: Have you tried any of the existing stuff, like
Takari Lifecycle before modding Maven itself? (
http://takari.io/book/40-lifecycle.html)
Thanks,
T
On Fri, Sep 13, 2019 at 10:46 PM Maximilian Novikov <
maximilian.novi...@db.com> wrote:
> Hi All,
>
>
>
> *We want t
The fixed phases were one of the main strengths of Maven, and with this
automatism it could really be enhanced.
My dislike: the `before:goal` invocation is being "projected" to non
existent plugin invocation. This sounds like a hack. Could we clear that
part up?
T
On Fri, Oct 25, 2019 at 10:23 P
lugin".
On Fri, Oct 25, 2019 at 11:13 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Fri 25 Oct 2019 at 21:41, Tamás Cservenák wrote:
>
> > The fixed phases were one of the main strengths of Maven, and with this
> > automatism it could really be
+1
On Tue, Oct 29, 2019, 21:11 Karl Heinz Marbaise wrote:
> Hi to all,
>
> based on the discusion this is the formal VOTE to lift the minimum of
> Maven Core with version 3.7.0 to JDK 8 minimum.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Kind regards
> Karl Heinz Mar
+1
On Thu, Nov 21, 2019 at 9:06 PM Robert Scholte wrote:
> Hi,
>
> This will be a regression release based on some critical issues discovered
> in Maven 3.6.2
>
> We solved 10 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12346152&styleName=Text
>
There are traces of it in resolver provider:
https://github.com/apache/maven/blob/716cc1fe02661897232a7cc3e4c1bb3b3df3b832/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultArtifactDescriptorReader.java#L316
And AFAIK, it _does_ obeys it...
T
On Sat, Feb 15, 2020
+1
On Wed, Feb 19, 2020, 08:13 Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12345961&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1552/
>
> https://repositor
Hi Bakary,
this is the wrong list for question like these: this list is about core
Maven development, and it's core plugins, which minify maven plugin
certainly is not.
Look around and ask here for help:
https://samaxes.github.io/minify-maven-plugin/
HTH,
T
On Wed, Apr 29, 2020 at 6:54 PM Bakar
+1 to rip out plexus logging
On Sun, May 31, 2020, 17:58 Elliotte Rusty Harold
wrote:
> Moved from slack per suggestion:
>
> The documentation on logging for Maven seems of two minds:
>
> "Maven uses [Plexus logging API][6] with basic Maven implementation
> writing to stdout.
> We have reached t
https://issues.apache.org/jira/browse/MNG-4059
maybe?
On Tue, Jul 7, 2020 at 8:58 PM Elliotte Rusty Harold
wrote:
> Thank you. That's exactly what I needed to know. The behavior did
> indeed change from 3.0 to 3.1 so I should not be surprised that my PR
> that updates the dependency plugin to 3.
Hi Bjorn and Emmanuel,
Without starting any flame wars, am really curious: why are you
repackaging Maven?
I'd understand for OS/distro native packages, but
why do you rebuild JVM bytecode as well?
Again, am not to start any flame war, am just curious!
Am Linux user since 98 (first worked on S.u
is
"dance" once, but from now on, all this work can be scraped, right?
Thanks
Tamas
On Fri, Nov 20, 2020 at 9:49 AM Emmanuel Bourg wrote:
> On 19/11/2020 09:51, Tamás Cservenák wrote:
>
> > Without starting any flame wars, am really curious: why are you
> > repacka
no need to redo all this for EVERY maven version, right?
T
On Fri, Nov 20, 2020 at 10:06 AM Tamás Cservenák
wrote:
> Thanks for the answers!
>
> AFAIK, we in Apache as well "vote for source", while we provide binaries
> as well.
>
> Given the video mentions that Maven
the same, if not deeper
dependency hierarchy as with deb/rpm or whatever other package system has
as well.
(Another joke) By the way, what do you do with npm packages? ;)
Thanks
Tamas
T
On Fri, Nov 20, 2020 at 10:13 AM Tamás Cservenák
wrote:
> Maybe it was not clear from my last statement: so
+1
On Fri, Nov 27, 2020 at 2:15 PM Michael Osipov wrote:
> Am 2020-11-25 um 21:47 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 3 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12348348
> >
> >
> > There are still a couple of issues left in JI
Agree with Robert here: this issue is really about "hard to author/write
POMs as they are chatty".
Then use polyglot, and let's Maven itself (or Maven + polyglot) sort out
things, but modding POM modello is something not we'd like to do... (as
many others noted, existing tooling etc).
My 5 cents.
+1
On Fri, Dec 25, 2020, 22:20 Michael Osipov wrote:
> I need one more binding vote...
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Howdy,
well, it's not so simple, is buried under layer and layers of
abstraction... you did start on good place, but it is actually something
like
m-deploy-p -> m-artifact-transfer -> maven-resolver ->
maven-resolver-connector (usually wagon) -> HTTP wagon
So if you are literally after code "whe
Simplest is to clone (in gh) these reposes to your user
https://github.com/apache/maven
https://github.com/apache/maven-resolver
https://github.com/apache/maven-wagon
Then clone them from there to your machine (git clone). I usually add
"upstream" remote (git remote add upstream ...) that points
Just add few cents to Stuart superb answer:
the singleton scope depends on the "realm" (no idea how to call it better)
where it is singleton, as the "lifespan" of realm may not be same/aligned.
Core and Core Extension lifespan vs Mojo/Plugin lifespan is clearly not the
same...
Also, take a peek at
When I read "jsr330" (in maven context), I always "replace it" with SISU in
my head, as Maven is SISU powered.
So there is nothing undefined for me, as SISU defines all the "blind spots"
IMO.
Maven, while it may look so, will NOT work with any other JSR330
implementation, just SISU.
Maven 3 was ma
+1 fot option 3: we drag so much of legacy, that m4 really should accept
maven 3.1+ plugins only (covers 14 years?).
T
On Sat, Feb 6, 2021, 14:32 Robert Scholte wrote:
> (I'm not sure if this has already been discussed on the dev-list, but I
> can't find any related thread)
>
> Plugins that dep
Howdy,
my 5 cents:
Something is stale, very stale in there, as plexus-container-default was
abandoned about 10 (maybe 12?) years ago, and sisu "shim"
(sisu-inject-plexus) was created as the direct replacement (as functional
and as API).
If your project has Plexus "the old container" (plexus-cont
Sorry, but I have to clarify this "Plexus et al is one of the reasons..."
misleading statement:
It is not Plexus per se THE reason, but the "neglected and stale"
dependencies, or better "dependencies like these"...
T
On Tue, Feb 9, 2021 at 5:38 PM Tamás Cservenák w
Howdy,
Some time ago I stumbled upon Robert S. remark in "[DISCUSS] MNG-7020
Remove Maven 2 WagonExcluder backward compat code" thread: "Why download,
if they are being removed from the classpath afterwards due to classworld
config". Similarly, there is a thread "maven-site-plugin and
sisu-inject-
plexus-container-default count is SAME as
with Maven build, so it is most probably some "common" plugin(s) pulling it
in...
Again, around 1.1k unnecessary downloads prevented, which surprises me...
So, to me the "gain" looks constant so maybe not really worth the
effort?
T
3.6.3?
>
> AFAIK there's no ticket for it yet, these were just the ideas I could
> think of regarding the WagonExcluder issue.
> Looks like it is time to create it.
>
> thanks,
> Robert
>
> On 10-2-2021 09:50:24, Tamás Cservenák wrote:
> Howdy,
>
> Some time
Created https://issues.apache.org/jira/browse/MNG-7097
On Thu, Feb 11, 2021 at 8:41 AM Tamás Cservenák wrote:
> Hi Robert,
>
> I agree with you: is a really small change.
> Re non-exported packages: will take a look into those a bit more, my POC
> was just at "artifact
ice,
> which
> will take longer time...
> need to test also...
>
> Regards,
>
> Hervé
>
> Le jeudi 11 février 2021, 08:41:21 CET Tamás Cservenák a écrit :
> > Hi Robert,
> >
> > I agree with you: is a really small change.
> > Re non-exported packa
<https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://ww
Howdy,
take a peek at resolver "demo" snippets here:
https://github.com/apache/maven-resolver/blob/master/maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples/ResolveTransitiveDependencies.java
Word of warning: do not "mix" ServiceLocator and DI (Guic
+1 go for it
On Thu, Feb 18, 2021 at 2:48 PM Enrico Olivelli wrote:
> Hello,
> there are issues on GitHub Actions that could be mitigated/fixed with a new
> release of Wagon Wheel.
>
> There is only this fix, about upgrading Http Client dependencies
> https://issues.apache.org/jira/projects/WAGO
+1
On Thu, Feb 18, 2021 at 11:32 PM Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12349719
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
+1
On Sat, Feb 20, 2021, 10:33 Sylwester Lachiewicz
wrote:
> Kindly reminder, need one more pmc votes
>
> niedz., 14 lut 2021, 01:40 użytkownik Sylwester Lachiewicz <
> slachiew...@apache.org> napisał:
>
> > Hi,
> >
> > We solved 17 issues:
> >
> >
> https://issues.apache.org/jira/secure/Relea
Howdy,
just a quick question, I thought someone may enlighten me...
Noticed, that Maven _resolves_ and _creates extension realms_ for things I
did not opt to at all. Typical example is nexus-staging-maven-plugin, that
maven 3.6.3 resolves at one moment in my build, despite not using it.
So, what
t some
> of the artifacts being downloaded when invoking certain plugins. Thanks for
> looking into this and trying to improve the situation.
>
> - Eric L
>
> On Thu, Mar 11, 2021 at 4:19 PM Tamás Cservenák
> wrote:
>
> > Howdy,
> >
> > just a quick question,
+1
On Mon, Mar 15, 2021, 23:53 Michael Osipov wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=1235
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/projects/MRESOLVER/issues?filt
l without trying to extend it to a general purpose
> framework. YAGNI.
>
> On Tue, Feb 9, 2021 at 4:39 PM Tamás Cservenák
> wrote:
> >
> > Howdy,
> >
> > my 5 cents:
> >
> > Something is stale, very stale in there, as plexus-container-default was
> > aban
Tamás Cservenák wrote:
> Plexus-container-default is NOT (and SHOULD NOT) be used anywhere, but the
> drop in sisu-plexus drop replacement should be used instead.
>
> If we use p-c-d anywhere (even in UTs), that's bad, as maven uses s-p
> instead.
>
> p-c-d is not use
+1
On Sun, Apr 25, 2021, 21:46 Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12349521
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging
Howdy,
plexus-sec-dispatcher is a really widely used dependency, is used in maven
itself, but also in many shared components and plugins (nb: there are even
some org.sonatype.plexus:plexus-sec-dispatcher among shared deps!).
Given this module is really maven specific, I see no reason to keep it
"
>
>
> would makes sense with changing groupId/artifactId and packages
>
> but cons: release this if needed will take ages because of ASF procedures
>
>
So, understood re ID/package
But forgot about the ASF process... but it would be weird if I want to
"de-plexus" plexus-sec-dispatcher in codehaus-
+1
On Wed, May 5, 2021 at 6:31 PM Hervé BOUTEMY wrote:
> +1
>
> build successfully reproduced: reference is JDK 8 on Windows
>
> Le mardi 4 mai 2021, 15:32:08 CEST Michael Osipov a écrit :
> > Hi,
> >
> > we solved 4 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=
+1
Tamás
On Sat, May 8, 2021, 11:36 Michael Osipov wrote:
> Hi,
>
> we solved 23 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12349416
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%
+1
On Sun, May 9, 2021, 20:15 Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12349726&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1647/
>
> https://repository
+1
On Thu, May 13, 2021, 20:18 Michael Osipov wrote:
> Am 2021-05-13 um 20:17 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 2 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12350159
> >
> >
> > There are still a couple of issues left in JIRA:
Howdy,
Something is wrong here...
You want to _extend_ sisu-plexus-shim, codebase that is here to buy out
(functionally) old Plexus Containers? The one meant to be a drop-in
replacement for legacy Plexus containers? Given we have STILL mixed use of
sisu-plexus-shim and "original" plexus-container,
+1
On Mon, Jun 7, 2021, 14:29 Michael Osipov wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348705&styleName=Html&projectId=12317227
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MDEP/issu
+1
On Mon, Jun 14, 2021 at 10:45 AM Michael Osipov wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12350167
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
1 - 100 of 1665 matches
Mail list logo
