Am 2023-06-06 um 14:14 schrieb Eric Lilja:
> > Hello everyone, the timestamp (e.g., #Tue Jun 06 01:59:04 CEST 2023) in
> the
> > _remote.repositories file, is that just for human consumption or is it
> > processed? If only as a courtesy for humans, can its generation be
>
Hello everyone, the timestamp (e.g., #Tue Jun 06 01:59:04 CEST 2023) in the
_remote.repositories file, is that just for human consumption or is it
processed? If only as a courtesy for humans, can its generation be disabled
somehow?
Best regards,
Eric Lilja
Are the providers leaking byte-buddy today? I just had to add explicit byte
buddy to my pom-file, for Mockito to work.
- Eric L
On Thu, Mar 9, 2023 at 2:13 PM Slawomir Jaranowski
wrote:
> To avoid leaking external libraries to classpath used under tests.
>
> But we should only use in providers
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
Now that's a good list of changes, thank you for doing that and I'm really
looking forward to this release!
- Eric L
On Fri, Oct 22, 2021 at 10:12 AM Michael Osipov wrote:
> Am 2021-10-22 um 07:52 schrieb Tamás Cservenák:
> > Howdy,
> >
> > I just wanted a heads up, that 3.6.2 of
Thank you for testing a bit more, Dan, I can't see anything particular on
my end either, but I don't have access to any really huge builds at
the moment, since I'm on vacation
All in all, I do however feel comfortable to vote now: +1 (non-binding)
- Eric Lilja
On Tue, Aug 10, 2021 at 10:29 AM
It's an impressive list of fixes and we are many that would like to see a
3.8.2 release appear. Question for me is if the particular change
that appears to cause a general performance degradation on the scale of ten
percent is worth it (if it indeed can be isolated to particular JIRA and
not due
For what it's worth, I noticed the same thing a while back when setting up
an offline system for a particular project at work. I was stunned at 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,
week!
- Eric L
On Thu, Oct 1, 2020 at 1:49 PM Eric Lilja wrote:
> I opened https://issues.apache.org/jira/browse/SUREFIRE-1850
>
> Thanks!
>
> - Eric L
>
> On Wed, Sep 30, 2020 at 11:30 PM Eric Lilja wrote:
>
>> Of course, I will do it when I get to the office to
I opened https://issues.apache.org/jira/browse/SUREFIRE-1850
Thanks!
- Eric L
On Wed, Sep 30, 2020 at 11:30 PM Eric Lilja wrote:
> Of course, I will do it when I get to the office tomorrow, thanks!
>
> - Eric L
>
> On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold
>
Of course, I will do it when I get to the office tomorrow, thanks!
- Eric L
On Wed, Sep 30, 2020 at 5:51 PM Elliotte Rusty Harold
wrote:
> Looks like we don't need that. Can you file a bug in Jira?
>
> On Wed, Sep 30, 2020 at 11:12 AM Eric Lilja wrote:
> >
> > Hello, I
Hello, I have to set up Maven on a system which is completely offline,
restricted to work on a few, select projects.
During testing, everything initially looked good, I could perform "mvn
clean install" in all projects without issue, and could perform other
Maven-task as well, Intellij was happy,
Again problems with "fix version" not being set properly..seems some of the
newer contributors do not have the same WoW with regards to it as the more
senior ones, but they should.
- Eric L
On Fri, Aug 7, 2020 at 9:39 AM Robert Scholte wrote:
> Should MDEP-708 be moved or cloned? It must be
On Fri, Jul 24, 2020 at 12:06 AM Sylwester Lachiewicz
wrote:
> +1
>
> in fact, in this release, based on commits, we have also fixed:
> MSHARED-879 Reproducible builds
> MSHARED-810 Support for Java 12
> MSHARED-792 Maven Dependency Analyzer ignores Java 8 type annotations on
> local variables
>
+1 non-binding
Nice to see a release of this plugin!
- Eric Lilja
On Thu, Apr 30, 2020 at 8:09 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> +1 from me
>
>
> Kind regards
> Karl Heinz Marbaise
> On 27.04.20 20:19, Robert Scholte wrote:
> > Hi,
> >
packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le jeu. 16 avr. 2020 à 11:18, Eric Lilja a écrit :
>
> > But the proposal was not to deprecate 3.5, but anything below (since 3.5
> > was when the resolver was introduced)?
> >
> > - Eri
But the proposal was not to deprecate 3.5, but anything below (since 3.5
was when the resolver was introduced)?
- Eric L
On Thu, Apr 16, 2020 at 11:08 AM Romain Manni-Bucau
wrote:
> Hi Tibor, technically you are likely right but deprecating is not only
> technical, i'd say it is only 10% of
I was personally hoping to see the java 8 edition of ant used, as indicated
it would be in previous email threads on this list, but +1 from me
(non-binding)
A release is greatly appreciated!
- Eric L
On Sun, Apr 12, 2020 at 10:25 PM Sylwester Lachiewicz
wrote:
> +1
> Tested with
Ah, I see, perfect, thanks for the clarification!
- Eric L
On Fri, Apr 3, 2020 at 11:43 PM Robert Scholte wrote:
> yes it does, but not bound to a jira issue
> On 3-4-2020 22:10:54, Eric Lilja wrote:
> Still no parent pom update that was mentioned to, unfortunately, be missing
>
Still no parent pom update that was mentioned to, unfortunately, be missing
in the vote for 1.7.0?
- Eric L
On Fri, Apr 3, 2020 at 9:36 PM Robert Scholte wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12347880=Text
>
> There
Hi!
Any update on this? At least, in Jira, I cannot see any activity regarding
issues.
- Eric L
On Mon, Mar 2, 2020 at 12:30 AM Eric Lilja wrote:
>
>
> On Sun, Mar 1, 2020 at 4:29 PM Enrico Olivelli
> wrote:
>
>>
>>
>> Sorry I forgot, too much time pas
at benefit do you expect from
> these? are you stuck by a bug?
>
> Le dimanche 8 mars 2020, 13:14:31 CET Eric Lilja a écrit :
> > It's not too late, all it takes is will, and it was feedbacked by another
> > person in the previous thread regarding the upcoming release of this
>
will be done for 0.13.0... and
> afterwards making a release of it ...and then integrate that into
> maven-dependency-plugin and make another release of maven dependency
> plugin.
>
>
> Kind regards
> Karl Heinz Marbaise
>
> On 07.03.20 19:33, Eric Lilja wrote:
> > It would be
hoose to finish the release or cancel it
>
> Regards,
>
> Hervé
>
> Le samedi 7 mars 2020, 19:33:47 CET Eric Lilja a écrit :
> > It would be very nice to release maven-artifact-transfer first (both
> 0.12.1
> > and 0.13.0 look ready in Jira, with one and two issue
It would be very nice to release maven-artifact-transfer first (both 0.12.1
and 0.13.0 look ready in Jira, with one and two issues closed respectively,
so I would go for 0.13.0 to get all ready fixes out), and integrate into
this release. Please consider doing that!
- Eric L
On Sat, Mar 7, 2020
Seems to me that fixes are never back-ported, meaning only the latest
version of Maven is really supported. That being said, care also seems to
be taken to not make changes in plugins which break older versions of
Maven. I think you ask an important question, because trying to keep
plugins working
On Sun, Mar 1, 2020 at 4:29 PM Enrico Olivelli wrote:
>
>
> Sorry I forgot, too much time passed :)
>
>
No worries, Enrico! Thanks again for this initiative, we appreciate it to a
grea degree!
By the way, I checked the summary of maven-ant-plugin on Jira [1] and
happened to notice that it was
No no, not at all, if you see my first reply in this thread, I am
personally in favor of moving to latest Ant for this plugin, even if it
requires Java 8!
- Eric L
On Sun, Mar 1, 2020 at 4:19 PM Enrico Olivelli wrote:
> Il Dom 1 Mar 2020, 16:04 Eric Lilja ha scritto:
>
> > Oh
Oh, so ant has already been bumped to 1.9.14 (released March 2019), which
is the highest version of Ant not requiring java 8?
- Eric L
On Sun, Mar 1, 2020 at 3:35 PM Elliotte Rusty Harold
wrote:
> Deps look good except for org.apache.ant which is as high as it can go
> without requiring Java
Thanks for doing this, Enrico! It would be absolutely lovely to see the
plugin uplifted to Maven 3 requirement, as the other plugins have, along
with other parent/dependency updates, as you mentioned. Also hoping to see
ant itself bumped to 1.10.7!
Thanks again!
- Eric L
On Sun, Mar 1, 2020
russ
> Bernd
> --
> http://bernd.eckenfels.net
> ____
> Von: Eric Lilja
> Gesendet: Tuesday, February 4, 2020 3:21:51 PM
> An: Maven Developers List
> Betreff: Prevent maven-release-plugin from reformatting attributes on
> project element
&
rmatting, so I suppose
> you're
> in a case I did not expect
>
> Regards,
>
> Hervé
>
> Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pre
>
> I see.
> I am not aware of any such feature.
> If you have some tool that pretty prints XML according to your
> comporate rules you could invoke it in completionGoals [1]
>
That could be a workaround for now. Thanks!
- Eric L
>
> Enrico
>
> [1]
>
t; As far as it creates a valid XML with the same meaning this should not be a
> problem
>
> Enrico
>
> Il Mar 4 Feb 2020, 15:22 Eric Lilja ha scritto:
>
> > Hi, we noticed that maven-release-plugin changes formatting of the
> project
> > element, it writes the elemen
Hi, we noticed that maven-release-plugin changes formatting of the project
element, it writes the element as a single line, removing existing line
breaks on attributes. Is it possible to make it preserve original
formatting?
We're using maven-release-plugin version 3.0.0-M1
- Eric L
Which version of Checkstyle will be used for the release? 8.28?
- Eric L
On Wed, Jan 15, 2020 at 9:43 AM Enrico Olivelli wrote:
> This is red
>
> https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/
>
> We need it blue :-)
>
> Enrico
>
> Il giorno mer 15 gen 2020
I guess the reasoning goes something like this: "I am a plugin developer,
and I want to release a number of changes, a sub-set of which are "breaking
changes". Since all my changes are not ready at the same time and I want to
avoid releasing several major versions close to each other (assuming
On 2019-10-19 23:55, Sylwester Lachiewicz wrote:
I always read the release notes very carefully and I don't mind seeing
individual JIRA's per upgrade, even if does increase the length of the
release notes. I guess others only want to see features and possibly bug
fixes. Personally I like
On 2019-08-22 04:39, wrote:
Works fine for me, are you logged in?
https://issues.apache.org/jira/projects/MNG/summary
- Eric L
when will the maven jira be ok?
it has been down for several days.
-
To unsubscribe,
Ah, thanks Vladimir, that's even better. I was not 100% sure it would be
possible to retain complete control over resulting line endings for those
files, regardless of user git settings of stuff like autocrlf = true and
whatnot, but it seems there is, that's great news. Thanks!
- Eric L
On Thu,
proposition
- Eric L
On Wed, Jul 17, 2019 at 1:32 PM Enrico Olivelli wrote:
> Il mer 17 lug 2019, 13:28 Eric Lilja ha scritto:
>
> > I believe, if we instead upgrade to Checkstyle 8.21 or later, we don't
> need
> > to do any of those alternative approaches.
> >
> &
I believe, if we instead upgrade to Checkstyle 8.21 or later, we don't need
to do any of those alternative approaches.
https://github.com/checkstyle/checkstyle/issues/4073
- Eric L
On Wed, Jul 17, 2019 at 1:20 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Robert>A clone from
Hi! When could we see a release of maven-assembly-plugin 3.1.2? In Jira,
eight issues are associated with version 3.1.2, and they are all resolved.
We're keen to see 3.1.2 released, as it contains important dependency
upgrades, like MASSEMBLY-910 [1]
Best regards,
Eric L
[1]
+1 (non-binding)
- Eric Lilja
On Thu, Jul 4, 2019 at 10:04 PM Michael Osipov wrote:
> Am 2019-07-03 um 23:54 schrieb Graham Leggett:
> > On 01 Jul 2019, at 23:10, Michael Osipov wrote:
> >
> >> We solved 11 issues:
> >>
> https://issues.apache.org/ji
+1, people on old versions of Java can remain on the old version of the
plugin. No one who is in a project where an old version of Java is still in
use (< 8) expect to have everything else in their eco-system (3PPs, maven
plugins etc) at bleeding edge versions. I guess many such projects are many
forward to the next release of this plugin, thanks for your work on this
and other things in the Maven ecosystem!
- Eric L
On Mon, May 27, 2019 at 10:35 PM Enrico Olivelli
wrote:
> Il lun 27 mag 2019, 22:27 Eric Lilja ha scritto:
>
> > I mean that we don't need to convert any line b
checkstyle/checkstyle/issues/4073)
- Eric L
On Mon, May 27, 2019 at 10:17 PM Eric Lilja wrote:
> Hi Enrico! Just out of curiosity, what do you mean by " We are also fixing
> EOL in the checkstyle plugin code base"? No change in the plugin is
> required with regards to EOLs to
ot
related to EOL characters). Cheers!
- Eric L
On Mon, May 27, 2019 at 8:37 PM Enrico Olivelli wrote:
> Eric
> Thank you
>
> We are also fixing EOL in the checkstyle plugin code base
>
> Enrico
>
>
>
> Il lun 27 mag 2019, 11:34 Eric Lilja ha scritto:
>
> &
r not.
> >
> > Feel free to cast a -1 if you think that the staged artifacts are not
> > "stable" or there is any showstopper problem for the release.
> >
> > Let's move this discussion to a separate thread, something like
> "Validation
> > fai
+1 (non-binding), thanks for doing the release!
- Eric Lilja
On 2019-05-23 19:55, Karl Heinz Marbaise wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12343424
There are still a couple of issues left in JIRA:
https
Hi, in Jira there are five issues assigned to version 3.2.3, and they
are all closed. When can we see a new release? It would be nice to get
plexus-archiver fix out for this plugin as well! Not sure about status
for maven-assembly-plugin and maven-javadoc-plugin, if the latest
versions of
+1 (non-binding) - nice to see this under vote!
- Eric Lilja
On Wed, May 15, 2019 at 9:58 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924=12336941
>
> There are still a couple o
, May 14, 2019 at 4:18 PM Eric Lilja wrote:
> Hi, I edited the wrong files before when I changed line breaks (edited
> copies under target folder, silly me!). I changed the line separators to
> Windows-style for the two files under MCHECKSTYLE-54 (Mcheckstyle54.java
> and
showstopper problem for the release.
>>
>> Let's move this discussion to a separate thread, something like
>> "Validation
>> failures in Windows over current checkstyle plugin master branch")
>>
>> Enrico
>>
>>
>>
>>
>&
enerated-sources\plugin
- Eric L
On Tue, May 14, 2019 at 11:04 AM Eric Lilja wrote:
> I tried bumping checkstyle to 8.20, plus a few of the plexus dependencies,
> but that just brought an additional failure... (to
> MCHECKSTYLE-70-multi-sourcefolder\pom.xml) :-)
>
> I suppose the
L
On Tue, May 14, 2019 at 10:38 AM Eric Lilja wrote:
> I also see a failure for MCHECKSTYLE-54 on Windows. (Sorry, I didn't try
> the source zip, just cloned master)
>
> I tested on one of our corporate laptops:
> Windows 10
> Cygwin 64-bit (I use it to clone the repo and
I also see a failure for MCHECKSTYLE-54 on Windows. (Sorry, I didn't try
the source zip, just cloned master)
I tested on one of our corporate laptops:
Windows 10
Cygwin 64-bit (I use it to clone the repo and use Maven)
Maven 3.6.0
Java 8 update 202
The build log says:
[INFO] There are 2 errors
Great news! Which version of Checkstyle will be default, 8.20? Hoping for
8.20!
- Eric L
On Fri, May 10, 2019 at 2:42 PM Tibor Digana wrote:
> Thx for your effort.
> Good job with everything you have done in Maven.
>
> On Fri, May 10, 2019 at 2:23 PM Enrico Olivelli
> wrote:
>
> > Hi all,
> >
+1 (non-binding)
On Fri, May 10, 2019 at 8:54 AM Karl Heinz Marbaise
wrote:
> Hi,
> +1 from me.
>
> Kind regards
> Karl Heinz Marbaise
> On 08.05.19 22:22, Karl Heinz Marbaise wrote:
> > Hi,
> >
> > We solved 2 issues:
> >
>
ter/ReleaseNotes.md#plexus-archiver-400
>
> /Anders
>
> On Tue, May 7, 2019 at 8:07 PM Eric Lilja wrote:
>
> > Hi, in my organization we're seeing big increases in build time using
> newer
> > versions of maven-jar-plugin and maven-sources-plugin, because those
> >
Hi, in my organization we're seeing big increases in build time using
newer versions of maven-jar-plugin and maven-sources-plugin, because
those plugins are affected by a bug in plexus-io it seems.
The issue in plexus-io has been fixed since some time: [1] and I
believe a release has been
Hi, in my organization we're seeing big increases in build time using newer
versions of maven-jar-plugin and maven-sources-plugin, because those
plugins are affected by a bug in plexus-io.
The issue in plexus-io has been fixed since some time: [1] and I believe a
release has been made of
to
follow the latest versions! I think that's good!
- Eric L
On Sat, May 4, 2019 at 8:57 PM Enrico Olivelli wrote:
> Il sab 4 mag 2019, 19:46 Eric Lilja ha scritto:
>
> > That's great news, Sylwester! Since it will be version 3.0 (as you say),
> > I'm assuming the plugin will be
That's great news, Sylwester! Since it will be version 3.0 (as you say),
I'm assuming the plugin will be changed to require Maven 3.x and Java 7
(and update to latest Maven parents), as that is a target for official
Maven plugins versioned 3 and higher? And why can't we use ant version
1.10.x,
In my organization, we would be very happy to see newer, more modernized
releases of maven-ant-plugin. So a big thumbs up for that!
- Eric L
On Sat, Apr 13, 2019 at 11:50 AM Robert Scholte
wrote:
> Hi Sebastian,
>
> be careful with your naming, because my first response would have been
> 'no'.
+1 (non-binding), tested with Java 8 on Windows 10 and Linux, both
personal projects and at work
- Eric L
On 2019-04-04 21:55, Karl Heinz Marbaise wrote:
Hi,
We have solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12338966
There are issues left
+1 (non-binding) Tested with personal projects and larger projects at work
- Eric Lilja
On Fri, Dec 21, 2018 at 2:49 PM Tibor Digana wrote:
> Thx Enrico, Christian for testing.
> This is not an ideal time for the release since it's Christmas season.
> I hope we will get some PM
for the reason described above, and I wanted to share that excitement.
Great work!
- Eric L
On 2018-12-08 19:40, Tibor Digana wrote:
@Eric Lilja
You use Pax. I guess you are refering to the problem with standard input
and standard output stream. The plugin says that the stream is corrupted.
Am I right
+1 (non-binding)
M2 is looking good on my projects, and I can't wait for the upcoming M3
after M2, which I believe will solve the long-standing problems running
Pax Exam tests (in the organization I work in we use 2.18.1 of surefire
for Pax-Exam tests particularly, as no version of Surefire
>
>
> > +private boolean isVersion( String version )
> > +{
> > +return StringUtils.isNotEmpty( version ) &&
> > !StringUtils.isWhitespace( version );
> > +}
>
Maybe use StringUtils.isNotBlank() instead?
- Eric L
Aha, indeed, I missed that part. Sorry for the noise!
- EL
On 2018-11-03 22:26, Tibor Digana wrote:
It was a component [1] but now it is a plugin [2].
[1]: https://github.com/apache/maven-jarsigner
[2]: https://github.com/apache/maven-jarsigner-plugin
On Sat, Nov 3, 2018 at 6:32 PM Eric
order. I noticed the process took a lot longer than usual
after adding the staging repo, but I solved that by adding the default
plugin repo as well.
By the way, there were five issues closed, not four, which is not a bad
thing, just a tiny error in the vote email text :)
- Eric Lilja
If one just reads the list, it's hard to understand why this is voted on
again after this announcement [1] (but I can see it didn't make it to
Maven central). Seems some off-list communication have taken place here...
[1]
with personal projects at home and
also with bigger projects at work, both on personal workstation and on
Jenkins
- Eric Lilja
Reasons:
1. Not enough VOTE's from PMC's
2. I would like to see more feedback from community.
Kind regards
Karl Heinz Marbaise
On 24/10/18 21:50, Karl Heinz Marbaise
+1 (non-binding), tested with my personal projects and bigger projects
at work (and at work both on personal workstations and certain Jenkins
installations).
Very much looking forward to the release!
- Eric Lilja
On 2018-10-24 21:50, Karl Heinz Marbaise wrote:
Hi,
We have solved 26 issues
>
>
>
> > 2. Both projects (install, deploy) have several warnings
>
> Can you be more accurate? Where ?
>
I just went to link describing the fixes issues in your email,
https://issues.apache.org/jira/projects/MINSTALL/versions/12334343, and I
can see JIRA saying there are 20 warnings. Warnings
solve versions should have been "solved issues"
On Mon, Sep 24, 2018 at 9:29 AM Eric Lilja wrote:
>
>
> On Sun, Sep 23, 2018 at 7:44 PM Karl Heinz Marbaise
> wrote:
>
>> Hi,
>>
>> We solved 32 issues:
>> https://issues.apache.org/jira/project
On Sun, Sep 23, 2018 at 7:44 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 32 issues:
> https://issues.apache.org/jira/projects/MINSTALL/versions/12334343
>
Hi and thank you for doing the releases of both maven-deploy-plugin and
maven-install-plugin, it's exciting! However, when I follow
On 2018-06-17 21:18, Stephen Connolly wrote:
y'all good now... 3.5.4 cut... vote will follow once the other bits sync
Yay! I cannot wait to see the vote email! Awesome work by everyone
involved, exciting!
- Eric L
-
To
How's the release of plexus-interpolation going? We're looking forward to a
new release of maven-war-plugin!
- EL
On Sun, May 13, 2018 at 10:16 AM Karl Heinz Marbaise
wrote:
> Hi Gabriel,
>
> I have added an issue for the upgrade of plexus-interpolation (MWAR-417)
> which is related to
On 2018-03-06 14:27, Tibor Digana wrote:
Hi Herve,
Can you send me a zip of the test which failed
*surefire-its/target/Surefire1177TestngParallelSuitesIT_shouldRunTwoSuitesInParallel*
?
It is a parallelism in TestNG. I will discuss it with the guys in TestNG
team on GitHub.
Thx.
Tibor
Is https://issues.apache.org/jira/browse/MNG-6025 being included in
3.5.1? I sure hope so!
- Eric L
On 2017-05-01 22:15, Hervé BOUTEMY wrote:
great!
I'll mark it for 3.5.1
Regards,
Hervé
Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit :
@Hervé, I want to second MNG-6223
Robert
Indeed, I would not expect to having my provided manifest modified at all.
On 2015-06-07 18:57, Igor Fedorenko wrote:
If I provide custom jar manifest, I expect the manifest to be used
as-is, without anything added, removed or reordered. Just my 2 kopecks.
83 matches
Mail list logo
