Hi all,
as already mentioned, I will create a mail thread for each epic that we defined
for the “Support & Care for Apache Maven” initiative
(https://open-elements.com/support-care-maven/).
All information about this specific epic can be found at
https://github.com/OpenElements/maven-support-c
s you can
> >> ask the Eclipse EMO (e...@eclipse.org added as CC).
> >>
> >> If you need any help I can offer to give some help from my experience in
> >> other Eclipse Projects, at a first glance looking at the release page[1]
> >> a release review
e.org/projects/technology.sisu
[2] https://projects.eclipse.org/projects/technology.sisu/governance
Am 07.05.24 um 23:23 schrieb Olivier Lamy:
Hi,
Sure but as a long-term developer, I cannot release this plexus part
anymore.
It used to be very easy to release this major part of the system (but
for some reason
schedule one just to be sure.
> >
> > HTH
> > Christoph
> >
> > [1] https://projects.eclipse.org/projects/technology.sisu
> > [2] https://projects.eclipse.org/projects/technology.sisu/governance
> >
> > Am 07.05.24 um 23:23 schrieb Olivier Lamy:
>
s specific
> topic, it just wont hurt to schedule one just to be sure.
>
> HTH
> Christoph
>
> [1] https://projects.eclipse.org/projects/technology.sisu
> [2] https://projects.eclipse.org/projects/technology.sisu/governance
>
> Am 07.05.24 um 23:23 schrieb Olivier Lamy
[1] https://projects.eclipse.org/projects/technology.sisu
[2] https://projects.eclipse.org/projects/technology.sisu/governance
Am 07.05.24 um 23:23 schrieb Olivier Lamy:
Hi,
Sure but as a long-term developer, I cannot release this plexus part anymore.
It used to be very easy to release this major part of
Hi,
Sure but as a long-term developer, I cannot release this plexus part anymore.
It used to be very easy to release this major part of the system (but
for some reason this has been moved somewhere else. not something to
discuss again, of course)
I have been asking sisu dev mailing list for a
Sorry for the noise on this. After further looking, in our super pom, we were
overriding plexus utils on multiple plugins, one of which was the site plugin.
Since those did not have the override on plexus xml set to 3 and the fact we
override back to plexus utils 4 using same property value
Get Outlook for Android<https://aka.ms/AAb9ysg>
>
> From: Slawomir Jaranowski
> Sent: Saturday, September 16, 2023 9:50:51 AM
> To: Maven Developers List
> Subject: Re: plexus-utils 4.x and Xpp3DomBuilder
>
> śr., 13 wrz 2023 o 08:47 Hervé
9:50:51 AM
To: Maven Developers List
Subject: Re: plexus-utils 4.x and Xpp3DomBuilder
śr., 13 wrz 2023 o 08:47 Hervé Boutemy napisał(a):
> can you try plexus-xml 3.0.0 and confirm this works as you expected
> initially,
> please?
>
>
plexus-utils 4.x and plexsu-xml 3.0.0 can be
śr., 13 wrz 2023 o 08:47 Hervé Boutemy napisał(a):
> can you try plexus-xml 3.0.0 and confirm this works as you expected
> initially,
> please?
>
>
plexus-utils 4.x and plexsu-xml 3.0.0 can be used on both Maven 3.x and 4.x
So now it will be ok.
https://github.com/apache/mave
can you try plexus-xml 3.0.0 and confirm this works as you expected initially,
please?
Regards,
Hervé
Le mardi 25 juillet 2023, 20:56:04 CEST Slawomir Jaranowski a écrit :
> Hi
>
> I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
> maven-enforcer .
plexus-xml 3.0.0 released, compatible with Maven 3
Maven Archetype upgraded as a proof of work:
https://issues.apache.org/jira/browse/ARCHETYPE-648
= upgrading plexus-utils 3 to plexus-utils 4 + plexus-xml 3 (when XML APIs
required) is a breeze
what has to be avoided is upgrading plexus-xml 3
working on it, I created a branch for plexus-xml 3.x:
https://github.com/codehaus-plexus/plexus-xml/tree/3.x
we should probably release such plexus-xml 3 that is the "normal" usual XML
code that we used for years, extracted from plexus-utils 3
plexus-xml 4 is currently only for Maven
And looks like this apply not only to plugins but also to shared libs for
maven (ASF also plexus and mojohous)
Sylwester
niedz., 10 wrz 2023, 09:00 użytkownik Hervé Boutemy
napisał:
> Le samedi 9 septembre 2023, 19:33:51 CEST Václav Haisman a écrit :
> > On 25. 07. 23 20:56,
Le samedi 9 septembre 2023, 19:33:51 CEST Václav Haisman a écrit :
> On 25. 07. 23 20:56, Slawomir Jaranowski wrote:
> > Hi
> >
> > I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
> > maven-enforcer
> >
> > In maven-enfo
On 25. 07. 23 20:56, Slawomir Jaranowski wrote:
Hi
I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
maven-enforcer
In maven-enforcer (and in many other plugins ...) is used, code like:
Xpp3Dom enforcerRules = Xpp3DomBuilder.build(descriptorS
now that plexus-xml has more details, I see the key point causing the most
issues: it uses not only maven-xml-api but also maven-xml-impl
maven-xml-impl is the Maven 4-specific reimplementation of XML parsing that is
causing the incompatibility
probably that this Maven XML Implementation
ok, I updated plexus-utils and plexus-xml sites
and added a few key aspects about how these relate to old Plexus Utils 3
https://codehaus-plexus.github.io/plexus-utils/
https://codehaus-plexus.github.io/plexus-xml/
I hope this will help
Le samedi 9 septembre 2023, 11:14:52 CEST Hervé Boutemy a
eta and m-api-xml are small very stable APIs, very non-Maven core
specific
I understand that we want to put them at Apache instead of Plexus, and I
agree.
But I think we should make their release cycle independent from Maven core:
they do not deserve the current 7 alphas, then new releases
yes
notice p-u site is broken https://codehaus-plexus.github.io/plexus-utils/
and we should probably also find a way to publish also latest p-u 3 javadoc in
parallel
I'll see what I can do also to help on this
Le vendredi 8 septembre 2023, 10:53:11 CEST Slawomir Jaranowski a écrit :
>
Howdy,
Basil's issue is made me realize:
o.c.p:p-u 4.x that depends on
-> o.c.p:p-xml 4 that depends on
-> o.a.m:m-api-xml that depends on
-> o.a.m:m-api-meta
This means that p-u pulls in new Maven4 API bits.
Hence, Maven 3 plugin, that is built against maven-plugin-api 3.x, if
switched to p-u 4,
I raised this issue in
https://github.com/jenkinsci/maven-hpi-plugin/pull/490#issuecomment-1557970717
but did not receive a response.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-
l introduce "plugin X will work ONLY with
> Maven 3.9.5+", no?
>
> T
>
> On Mon, Sep 4, 2023 at 10:51 PM Guillaume Nodet wrote:
>
>> I think the decision to not export plexus-utils was taken some time ago.
>>
>> Unfortunately, the xml bits still have to
1 PM Guillaume Nodet wrote:
> I think the decision to not export plexus-utils was taken some time ago.
>
> Unfortunately, the xml bits still have to be provided by the maven core
> class loader.
> I think in this case, Maven 3.9.x should also expose the builder class
>
>
> org
Maven Core, "knowing
itself constituents" already auto-injects itself as depMgt for plugins)
And sorry for the thread hijack...
===
As for current thread:
Given our goal is to totally decouple plexus-utils, maybe we want instead
this:
org.cod
Thanks, I will create an IT for it.
Good idea to describe the migration from plexus 3.x to 4.x.
pt., 8 wrz 2023 o 10:26 Guillaume Nodet napisał(a):
> I've raised MNG-7873.
> Slawomir, do you think you could create an IT for that ?
> I'll try to provide a fix asap, but a
I've raised MNG-7873.
Slawomir, do you think you could create an IT for that ?
I'll try to provide a fix asap, but a clean IT would make sure the problem
is actually fixed.
I think we should also update the plexus-utils release notes with some more
information about the migration t
right conclusion
Le mercredi 26 juillet 2023, 06:55:10 CEST Christoph Läubrich a écrit :
> I tried the same with Tycho and the conclusion was that a maven plugin
> can currently not upgrade to plexus-xml4 if you still want to support
> maven 3.x
>
> Am 25.07.23 um 20:56 s
I think the decision to not export plexus-utils was taken some time ago.
Unfortunately, the xml bits still have to be provided by the maven core
class loader.
I think in this case, Maven 3.9.x should also expose the builder class
org.codehaus.plexus.util.xml.Xpp3DomBuilder
I think this should
I tried the same with Tycho and the conclusion was that a maven plugin
can currently not upgrade to plexus-xml4 if you still want to support
maven 3.x
Am 25.07.23 um 20:56 schrieb Slawomir Jaranowski:
Hi
I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
maven-enf
Hi
I'm trying to update plexus-utils 3.5.x to plexus-utils/plexus-xml 4.x in
maven-enforcer
In maven-enforcer (and in many other plugins ...) is used, code like:
Xpp3Dom enforcerRules = Xpp3DomBuilder.build(descriptorStream,
"UTF-8");
Xpp3Dom and Xpp3DomBu
slachiewicz commented on PR #2:
URL: https://github.com/apache/maven-2/pull/2#issuecomment-1500966170
@hboutemy please close and archive
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the speci
dependabot[bot] opened a new pull request, #13:
URL: https://github.com/apache/maven-shared-jar/pull/13
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.4.2 to 3.5.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/releases
Just curious, why is such an old version of maven-dependency-plugin used in
that build?
- Eric L
On Sat, Feb 25, 2023 at 2:46 PM Elliotte Rusty Harold
wrote:
> On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet
> wrote:
> >
> > Which goal are you running ?
> > I think you need to run the package
On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet wrote:
>
> Which goal are you running ?
> I think you need to run the package phase as hinted by the error.
>
mvn test
also
mvn compile; mvn test
mvn clean test
mvn package; mvn test
All end with the same failure. This seems to be a regression
about this:
>
> [INFO] Unpacking
>
> /Users/elharo/.m2/repository/org/codehaus/plexus/plexus-utils/3.5.0/plexus-utils-3.5.0.jar
> to /Users/elharo/maven/plexus-utils/target/classes with includes
> "**/*.class,**/*.xml" and excludes
>
> "org/codehaus/plexus/u
FYI, maven core tests fail for me (Java 1.8. Maven 3.8.7) when
building at head like so. I'm not sure what to do about this:
[INFO] Unpacking
/Users/elharo/.m2/repository/org/codehaus/plexus/plexus-utils/3.5.0/plexus-utils-3.5.0.jar
to /Users/elharo/maven/plexus-utils/target/classes with inc
Maybe really a backport is the way to go. Please check in and out and
I will happily merge if this fixes the problem for components like yours.
I was able to backport and test it sucessfully, see
https://github.com/apache/maven/pull/999
Btw, I'll explore a reflection hack to mitigate the impact
Am 2023-02-10 um 18:55 schrieb Falko Modler:
Hi Michael,
Have you tried to back port the class loading strategy from gnodet@
back to 3.8.x?
Not yet. First, I'm looking for solutions without touching Maven itself
but there might be none in this case.
I was actually thinking myself whether that
fter trying a few other things without luck, I tried adding an
explicit dependency to plexus-utils which does fix this general issue!
But that brings back another issue I already had before 3.9.0 in a
specific use case / code path _and only for the third flavor_ (core
extension):
java.
Hi Michael,
Have you tried to back port the class loading strategy from gnodet@
back to 3.8.x?
Not yet. First, I'm looking for solutions without touching Maven itself
but there might be none in this case.
I was actually thinking myself whether that feature could be backported,
so good you ment
Correction:
It's also way too early to drop support for Maven <=3.9.
"for Maven < 3.9".
Also sorry for the formatting mess, I copied the error directly from the
console.
Cheers,
Falko
-
To unsubscribe, e-mail: dev-unsubscr
ck, I tried adding an
explicit dependency to plexus-utils which does fix this general issue!
But that brings back another issue I already had before 3.9.0 in a
specific use case / code path _and only for the third flavor_ (core
extension):
java.lang.ClassCastException: class org.codehaus.plexus.util.xml.X
I've created a draft PR to switch the underlying plexus xml classes (the
Xpp3Dom and Xpp3DomBuilder) to wrap the maven provided implementation.
I need to investigate why 2 tests are failing though...
https://github.com/codehaus-plexus/plexus-utils/pull/236
Le mer. 1 févr. 2023 à 08:57,
> The only "problem" is that it
> creates a cycle between maven-core and plexus-utils, but
to reduce the problem, that's why I proposed at plexus-utils level to split the
xml part in another plexus-xml artifact, so at least the overlap is reduced and
there is clarifi
On Tue, Jan 31, 2023 at 9:43 AM Guillaume Nodet wrote:
>
> So I think my earlier proposal is fine, i.e. remove the plexus classes from
> the maven code tree, update them where they belong (i.e. in the plexus
> code tree) by adding a dependency to the maven-xml-impl.
> This keeps o
If you want to keep the fully package qualified class names the same,
> then don't change the artifact IDs or class locations and live with
> the current situation.
>
That was actually my proposal. I.e. keep things where they are, just
add a dependency from plexus-utils to m
e api), the
> old classes which were part of the maven 3 api were slightly modified
> to wrap the new ones. So we have the Xpp3Node from plexus-utils which
> now wrap the XmlNodeImpl (implementing the new XmlNode interface
> which is immutable). So far so good.
>
> However, to achieve t
.
Now, in order to get some compatibility with all the 3.x world in maven 4
and achieve the goals (one of them was to have an immutable api), the
old classes which were part of the maven 3 api were slightly modified
to wrap the new ones. So we have the Xpp3Node from plexus-utils which
no
org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > > html
> > I really think having the full API in a single tree / release cycle is a
> > good thing, so I'm not really keen on such a move.
> > I don't care so much about the plexus classes which are not suppos
.
> > > html
> > I really think having the full API in a single tree / release cycle is a
> > good thing, so I'm not really keen on such a move.
> > I don't care so much about the plexus classes which are not supposed to
> be
> > part of the new API, so tho
/index.html
= https://github.com/apache/maven/tree/master/api
The hard part, is the rewrite for Maven core immutable API of classes that are
from the XML classes of plexus utils: by definition, on these, the situation is
more complex
It's composed of:
- maven-xml-impl: new artifactId that reimple
it only depends on
> > previous one
> >
> > https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.
> > html
> I really think having the full API in a single tree / release cycle is a
> good thing, so I'm not really keen on such a move.
> I
having the full API in a single tree / release cycle is a
good thing, so I'm not really keen on such a move.
I don't care so much about the plexus classes which are not supposed to be
part of the new API, so those can be moved wherever it's easier, but unless
there's a very
On Mon, Jan 30, 2023 at 1:53 AM Hervé Boutemy wrote:
>
> I think that first steps are:
>
> 1. release maven-api-meta as a shared component, given it has no dependency
> https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-meta/dependencies.html
> Eventually renaming it maven-api-annotations, g
n-api-xml as a shared component, given it only depends on
previous one
https://maven.apache.org/ref/4.0.0-alpha-4/api/maven-api-xml/dependencies.html
then we'll refine the plan on Maven XML reimplementation of Plexus Utils XML
classes and injection into Maven 4 distribution
Creati
That sounds like a good plan.
A few observations:
* the usage of the plexus xml classes should be deprecated along with the
v3 model once the v4 api is stabilized and matured imho
* this will introduce a release cycle between maven-core / plexus-utils,
which is not really clean even though it
+1 and maybe drop the builder from plexus package for v4 (not too late to
fix it)
Le ven. 30 déc. 2022 à 23:56, Hervé Boutemy a
écrit :
> ok, if everyone wants to go that route of clarifying dependency from Maven
> on
> plexus-utils, let's go and do it fully.
>
> First,
ok, if everyone wants to go that route of clarifying dependency from Maven on
plexus-utils, let's go and do it fully.
First, I'm lost if you call "plexus-xml" an artifact that is maintained at
Maven. So we'll need to rephrase with one strict convention: plexus-*
ar
To reduce dependency from maven to plexus, we could keep the xml api and
implementation which are used by maven 4 inside maven, and update
plexus-utils (or the new plexus-xml) to be compatible with the new
immutable DOM api from maven.
So this would mean:
* move the two re-implemented plexus
+1 to what Romain said. Let's reduce dependencies to other orgs where
possible and feasible. It is, in this case.
On Fri, 30 Dec 2022, 10:27 Romain Manni-Bucau,
wrote:
> Hi Hervé,
>
> As mentionned in the thread I think it makes sense to freeze plexus and
> slowly import to
Hi Hervé,
As mentionned in the thread I think it makes sense to freeze plexus and
slowly import to maven the related code so I'd be to import the parts we
need (guess some abstraction can be dropped at the same time).
So +1 to split, -0 to do it at plexus, +1 to do it in maven.
Romain
while working on the XML side of Maven 4 immutable API, we had the idea of
extracting the XML code from plexus-utils to a new separate plexus-xml
artifact
that could be done for version 4
see https://github.com/codehaus-plexus/plexus-utils/issues/228
any objection?
Regards,
Hervé
uot;
Datum 10-11-2022 08:49:03
Onderwerp Access the maven commandline options from a plexus component?
Is it possible to access the commandline options I pass to maven in a plexus
component?
I'm especially interested in the -V option because I want this to trigger
printing the versio
Is it possible to access the commandline options I pass to maven in a
plexus component?
I'm especially interested in the -V option because I want this to
trigger printing the version of my core-extension as well
---
dependabot[bot] closed pull request #6: Bump plexus-component-api from
1.0-alpha-16 to 1.0-alpha-33
URL: https://github.com/apache/maven-shared-incremental/pull/6
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
dependabot[bot] closed pull request #7: Bump plexus-component-annotations from
1.6 to 2.1.1
URL: https://github.com/apache/maven-shared-incremental/pull/7
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
dependabot[bot] commented on PR #6:
URL:
https://github.com/apache/maven-shared-incremental/pull/6#issuecomment-1192283438
Looks like org.codehaus.plexus:plexus-component-api is no longer a
dependency, so this is no longer needed.
--
This is an automated message from the Apache Git Servi
dependabot[bot] closed pull request #8: Bump plexus-component-metadata from
1.7.1 to 2.1.1
URL: https://github.com/apache/maven-shared-incremental/pull/8
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
dependabot[bot] commented on PR #7:
URL:
https://github.com/apache/maven-shared-incremental/pull/7#issuecomment-1192283431
Looks like org.codehaus.plexus:plexus-component-annotations is no longer a
dependency, so this is no longer needed.
--
This is an automated message from the Apache G
dependabot[bot] commented on PR #8:
URL:
https://github.com/apache/maven-shared-incremental/pull/8#issuecomment-1192283429
Looks like org.codehaus.plexus:plexus-component-metadata is no longer a
dependency, so this is no longer needed.
--
This is an automated message from the Apache Git
olamy commented on PR #8:
URL:
https://github.com/apache/maven-shared-incremental/pull/8#issuecomment-1192283289
@dependabot recreate
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
dependabot[bot] opened a new pull request, #8:
URL: https://github.com/apache/maven-shared-incremental/pull/8
Bumps
[plexus-component-metadata](https://github.com/codehaus-plexus/plexus-containers)
from 1.7.1 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus-plexus
dependabot[bot] opened a new pull request, #7:
URL: https://github.com/apache/maven-shared-incremental/pull/7
Bumps
[plexus-component-annotations](https://github.com/codehaus-plexus/plexus-containers)
from 1.6 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus
dependabot[bot] opened a new pull request, #6:
URL: https://github.com/apache/maven-shared-incremental/pull/6
Bumps plexus-component-api from 1.0-alpha-16 to 1.0-alpha-33.
[ from 1.5.15
to 3.0.16.
Commits
https://github.com/sonatype/plexus-utils/commit/cf317f9b4070c3c619e9ee75a3e38bea3ff621c1
dependabot[bot] opened a new pull request, #3:
URL: https://github.com/apache/maven-ant-tasks/pull/3
Bumps [plexus-utils](https://github.com/sonatype/plexus-utils) from 1.5.15
to 3.0.16.
Commits
https://github.com/sonatype/plexus-utils/commit
asfgit closed pull request #17:
URL: https://github.com/apache/maven-archiver/pull/17
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr
slachiewicz merged pull request #57:
URL: https://github.com/apache/maven-artifact-transfer/pull/57
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail
dependabot[bot] opened a new pull request #57:
URL: https://github.com/apache/maven-artifact-transfer/pull/57
Bumps
[plexus-component-annotations](https://github.com/codehaus-plexus/plexus-containers)
from 2.1.0 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus
slachiewicz closed pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubs
dependabot[bot] commented on pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78#issuecomment-1001555337
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor v
dependabot[bot] opened a new pull request #78:
URL: https://github.com/apache/maven-doxia/pull/78
Bumps
[plexus-container-default](https://github.com/codehaus-plexus/plexus-containers)
from 2.1.0 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus
dependabot[bot] opened a new pull request #56:
URL: https://github.com/apache/maven-artifact-transfer/pull/56
Bumps
[plexus-component-metadata](https://github.com/codehaus-plexus/plexus-containers)
from 2.1.0 to 2.1.1.
Release notes
Sourced from https://github.com/codehaus
dependabot[bot] opened a new pull request #64:
URL: https://github.com/apache/maven-site-plugin/pull/64
Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
from 4.2.5 to 4.2.6.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-archiver
elharo closed pull request #70:
URL: https://github.com/apache/maven-doxia/pull/70
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
elharo closed pull request #61:
URL: https://github.com/apache/maven-site-plugin/pull/61
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsub
dependabot[bot] commented on pull request #61:
URL: https://github.com/apache/maven-site-plugin/pull/61#issuecomment-922459713
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or mi
dependabot[bot] commented on pull request #44:
URL:
https://github.com/apache/maven-artifact-transfer/pull/44#issuecomment-922457356
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
majo
elharo closed pull request #44:
URL: https://github.com/apache/maven-artifact-transfer/pull/44
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
dependabot[bot] opened a new pull request #70:
URL: https://github.com/apache/maven-doxia/pull/70
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/releases
dependabot[bot] opened a new pull request #61:
URL: https://github.com/apache/maven-site-plugin/pull/61
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/releases
dependabot[bot] opened a new pull request #44:
URL: https://github.com/apache/maven-artifact-transfer/pull/44
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.1.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils
elharo closed pull request #69:
URL: https://github.com/apache/maven-doxia/pull/69
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
elharo closed pull request #59:
URL: https://github.com/apache/maven-site-plugin/pull/59
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsub
dependabot[bot] commented on pull request #59:
URL: https://github.com/apache/maven-site-plugin/pull/59#issuecomment-889860653
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or mi
elharo closed pull request #41:
URL: https://github.com/apache/maven-artifact-transfer/pull/41
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
dependabot[bot] commented on pull request #41:
URL:
https://github.com/apache/maven-artifact-transfer/pull/41#issuecomment-889860340
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
majo
dependabot[bot] opened a new pull request #41:
URL: https://github.com/apache/maven-artifact-transfer/pull/41
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.0.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils
1 - 100 of 1270 matches
Mail list logo
