+1
- Ben
On Mon, 16 Jun 2025, 23:05 Slawomir Jaranowski,
wrote:
> Hi,
>
> We solved 47 issues:
>
> https://github.com/apache/maven-ear-plugin/issues?q=is%3Aclosed%20milestone%3A%223.4.0%22
>
> Changes since the last release:
>
> https://github.com/apache/maven-ear-plugin/compare/maven-ear-plu
> > There is no rule about how long that phase is and how many RCs there should
> > be.
> > > >
> > > > * The new constraints on users only apply if they upgrade to Maven 4
> > .. which is completely optional.
> > > >
> > > > * Even peopl
-1 for release, +1 for rc4.
Reason: What Sylwester said, plus Nikita from JetBrains asking nicely.
They (JB) would love to see API stability so they can ship an IntelliJ
IDEA release in time with Maven 4.
This of course applies to all other IDEs.
Nikita is on #maven in slack, maybe also subscribed
+1 (binding)
Thanks!
Question to the -1 voters: Please do share a reason for downvotes. I
am eager to know why you think we should not update to Java 21.
Am Mi., 30. Apr. 2025 um 15:12 Uhr schrieb Matthias Bünger
:
>
> Hi everyone,
> over the last years we had several discussions about lifting
I think we should also take a look at JReleaser.
It has been around quite a while, Andres is an excellent contact and maintainer.
Any reason why we should choose one of the two?
JReleaser moves the releasing process out of maven, which is a bit
sad. But it can be used as a plugin, too.
So maybe t
Hi Bear Giles!
Infra said, you were able to log in successfully according to their logs.
Is this resolved then?
- Ben
On Sun, 6 Apr 2025, 00:27 Benjamin Marwell, wrote:
> I'll let Apache infra know!
>
> Ben
>
>
>
> On Sun, 30 Mar 2025, 18:07 Bear Giles, wrote
I'll let Apache infra know!
Ben
On Sun, 30 Mar 2025, 18:07 Bear Giles, wrote:
> I'm ready to submit some issues + patches and having weird problems with
> the self-submit process. I have an existing JIRA account, and I've
> definitely contributed to an Apache project in the past (read-only ac
Nice work! However, if may clash, it's used differently in executions.
Better use g:, a: and v:, and other fields instead of one long id. Makes
updates easier, too, as well as scrolling through the document.
What do you think?
Otherwise, like tamas said: go for it. I also like the idea of creating
+1
On Sat, 22 Feb 2025, 09:45 Matthias Bünger,
wrote:
> Good morning everybody,
> ten days ago I started a discussion about the Maven PDF plugin, asking
> who is using it, if people have switched over to other tools and what
> everybody is thinking about archiving the plugin. You can read the
Hi all!
We have some good and some bad (but not too bad) news on this topic.
The good news are: We migrated all issues. No more pending state.
Additionally, all duplicates got deleted.
The downside: The PRs had matching titles and were in the same list
and API endpoint. GitHub support is looking
No, sorry, no idea. I will ask Sandra about it.
Am Do., 6. Feb. 2025 um 08:25 Uhr schrieb Herve Boutemy :
>
>
>
> On 2025/02/05 08:16:44 Guillaume Nodet wrote:
> > Searching for infos in old issues often involves switching between github
> > (for commits / PRs) and JIRAs.
> > If history can be rew
t and don't reimport,
just create one more new issue manually or so.
On Wed, 5 Feb 2025, 10:10 Slawomir Jaranowski,
wrote:
> On Wed, 5 Feb 2025 at 09:55, Benjamin Marwell wrote:
> >
> > It should have been. You're right.
> > I'll talk to infra about this.
> &g
It should have been. You're right.
I'll talk to infra about this.
We also disabled jira comments to the ML for migration.
On Wed, 5 Feb 2025, 09:29 Slawomir Jaranowski,
wrote:
> One more issue ... we have many notifications on ML, like:
> https://lists.apache.org/list?iss...@maven.apache.org:l
We are on contact with GitHub support. Please refrain from manually closing
them for now.
Before that, some were not displayed, were in status pending, which
effectively made them missing.
I'll keep you posted.
On Tue, 4 Feb 2025, 23:44 Elliotte Rusty Harold, wrote:
> If you look at https://
Nice design of the output!
Have you tested the extension in an CI environment? That might be useful,
especially combined with mvnd or mvn -T...
- Ben
On Thu, 23 Jan 2025, 16:25 Adrian Tarau, wrote:
> Hello everybody,
>
> I'm building a Maven extension to change the behavior of Maven while
> bui
-chaining, only one
return per method, etc., which I wouldnt want to enable either.
Am So., 5. Jan. 2025 um 20:45 Uhr schrieb Elliotte Rusty Harold
:
>
> On Sun, Jan 5, 2025 at 7:28 PM Benjamin Marwell wrote:
> >
> > Not sure about Elliotes NPEs. The ones I checked were vali
code (pom.xml etc.) is ensured.
Am Mo., 30. Dez. 2024 um 10:06 Uhr schrieb Matthias Bünger
:
>
>
> Am 30.12.2024 um 08:55 schrieb Guillaume Nodet:
> > Le dim. 29 déc. 2024 à 16:12, Benjamin Marwell a
> > écrit :
> >> We could instead configure checkstyl
+1, works well in other projects as well, and if needed, we can always
extend on that.
Questions should go to SO (or, maybe, to discussions).
Am Sa., 4. Jan. 2025 um 22:37 Uhr schrieb Slawomir Jaranowski
:
>
> On Sat, 4 Jan 2025 at 22:28, Matthias Bünger
> wrote:
> >
> > Hi,
> > I personally don
Not sure about Elliotes NPEs. The ones I checked were valid, e.g.:
https://sonarcloud.io/project/issues?open=AZQn8ht1KAwsFelognsS&id=support-and-care_maven
And even when calling another method inbetween, the explanation is excellent:
https://sonarcloud.io/project/issues?issueStatuses=OPEN%2CCONFIR
. 2024 um 13:52 Uhr schrieb Elliotte Rusty Harold
:
>
> Can I pick all of the above? That is, avoid spotless, text blocks, and
> anonymous lambda parameters. They all have issues that independently
> make me prefer code without them.
>
> On Thu, Nov 28, 2024 at 7:31 PM Benja
me know if you need more information on OpenJ9.
Am Sa., 21. Dez. 2024 um 14:01 Uhr schrieb Sylwester Lachiewicz
:
>
> Value would be more visible if we could react and fix or report builds
> issues for j9.
> Sylwester
>
> sob., 21 gru 2024, 13:41 użytkownik Benjamin Marwell
&
Hi Piotr, any news on this? You said you reached out to your palantir contacts?
The least they could do is to give access to some more devs...
Am Fr., 29. Nov. 2024 um 10:33 Uhr schrieb Piotr P. Karwasz
:
>
> Hi Benjamin,
>
> On 28.11.2024 20:31, Benjamin Marwell wrote:
> >
In addition to what Martijn said, I think it was me adding the Eclipse
OpenJ9-based JVM (the release is called IBM Semeru) to the build
matrix.
IIRC we had an issue we needed to solve and this is why I added it as
a regression test. A normal unit test would not do here.
Since Semeru is the only JV
+1
Am Mi., 18. Dez. 2024 um 08:30 Uhr schrieb Slawomir Jaranowski
:
>
> Hi,
>
> I open vete for question:
>
> Do we want to Switch to GitHub issues from JIRA?
>
> Discussion was in thread:
> https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
>
> About technical questions how we wi
+1
Palantir is by far the best formatter out there. Any means to keep it would
be desirable, in ANY way.
Donation or forking would be feasible when the maintainer is not able to
keep up or needs more help. Not trying to rip it away from them, more like
the thought of offering help.
Is there anyo
Hello everyone!
Sadly, palantir-java-format, used in Maven builds via spotless, still has
no support for text blocks and will misformat them. Also, it
still cannot parse anonymous lambda parameters (_).
Text blocks are available since 14, this bugs me already. The anonymous
underscore parameter
I think skipping 9 Java versions between Maven 3 and 4 is a big deal and
has never happened before 😁
Java 17 will be required for Maven 4.
Also Maven 4: extensions where you can use pom.conf or pom.yml etc.
On Mon, 23 Sept 2024, 10:53 Robert Scholte, wrote:
> Hi all,
>
>
>
> Within 2 weeks I w
Hi Exiahuang!
Sorry for getting back to you late.
Just sign up here: https://selfserve.apache.org/jira-account.html
Please write a short description of your intention so we know it is not spam.
Thanks for participating!
Am So., 12. Mai 2024 um 17:52 Uhr schrieb コ ウ :
>
> Dear Developer of maven
+1
Thanks, Tamas! 👍🏻
On Thu, 13 Jun 2024, 10:49 Tamás Cservenák, wrote:
> Howdy,
>
> We solved 16 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354748
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/iss
+1
Am Mi., 22. Mai 2024 um 12:10 Uhr schrieb Tamás Cservenák :
>
> Howdy,
>
> We solved 21 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12353964
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%
Hi all,
the vote has passed with the following result:
PMC +1: Anders Hammar, Arnaud Héritier, Benjamin Marwell, Guillaume
Nodet, Hervé Boutemy, Karl Heinz Marbaise, Konrad Windszus, ,Maarten
Mulders, Olivier Lamy, Romain Manni-Bucau, Sylwester Lachiewicz, Tamás
Cservenák
PMC majority quorum
Elliotte,
as per guidelines, it is not required. And I did not put it that way in my
email.
However, a reason would have helped in finding alternatives.
Anyway, here's my +1.
On Fri, 1 Mar 2024, 19:14 Elliotte Rusty Harold, wrote:
> On Wed, Feb 28, 2024 at 2:31 AM Benjamin Marwell
At this point, we have discussed many aspects.
Please feel to vote:
User List:
https://lists.apache.org/thread/ty321ns72qc6l26bjy58d9430ofg2w5t
Dev List:
https://lists.apache.org/thread/vngchrr3owd92v9y09lyfjjhwkl5hvtn
-
To unsu
Hi Maven Devs/Users/Committers and PMC members!
After several discussions on the mailing lists, I would like to
start a vote in favour of setting the minimal Java bytecode target
of Maven-Core 4 to 17 and hence require Java 17 for Maven 4.
This is a procedural majority vote [1*]:
You can also vot
Rusty Harold,
wrote:
> On Mon, Feb 26, 2024 at 7:24 PM Benjamin Marwell
> wrote:
> >
> > > 1. The Java version required by the project being built. That is, the
> > byte code and API level of the project.
> > > 2. The Java version used to compile the proj
> 1. The Java version required by the project being built. That is, the
byte code and API level of the project.
> 2. The Java version used to compile the project.
> 3. The Java version used to run Maven.
> 4. The Java version used to compile and build Maven itself.
> For #1, it is mandatory to sup
Brian, any Chance you could make a stacked 100% graph for every *week*
of the past two years?
We could then see where we are heading…
(or the raw numbers per week, so we could work with that).
That's probably a lot to ask, but I think it will show us how "fast"
the progression was (and will be).
FWIW, bazel changed its runtime requirement to Java 21.
But they are shipping their own Java Runtime, so their users won't notice. [1]
I think they are the first build tool to do that.
I say this as a FYI fact only, not implying anything.
Make of it what you want.
- Ben
Am Di., 20. Feb. 2024 um
+1 for the release as it is
+100 with the way Tamás put it.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
on if the caller of the method tries to pass NULL
> > into it. If I'm too lazy to check my parameters than I deserve it to get
> > NPE e.g. (funny enough an external coder with 20+ years of experience at
> > my work just experience that exactly now, as he just relies that
> we need to think about companies
that pay for old JDK support
There was a suggestion on slack that companies could provide "dev and
release manager" for Maven 3 and manage the JDK 8 Maven 3 until they lose
interest. This already works well for other projects.
Even if no one stands up for volunt
mono-repos to update their technical debt.
It is just not justifiable for all the other users.
I agree with Gary that an EOL schedule might be our best shot here.
Am Mo., 5. Feb. 2024 um 19:56 Uhr schrieb Elliotte Rusty Harold
:
>
> On Mon, Feb 5, 2024 at 12:01 PM Benjamin Marwell wrote:
Those who need Java 8 to *run* Maven will probably not upgrade to
Maven 4 anyway, as their builds will have other problems preventing
them from upgrading.
A few third-party plugins already moved to Java 11+, thinking of spotless.
That said:
+1 Stick with 8 for Maven 3.9.x and maybe a 3.10.x (not
The Apache Maven team is pleased to announce the release of the Apache
Maven JLink Plugin, version 3.2.0
The JLink Plugin is intended to create modular Java Run-Time Images via jlink.
https://maven.apache.org/plugins/maven-jlink-plugin/
You should specify the version in your project's plugin con
Hi,
The vote has passed with the following result:
+1 : Sylwester, Romain, Slawomir, Tamás, Olivier, Hervé
PMC quorum: reached
I will promote the source release zip file to the Apache distribution
area, the staging site to the live location and the artifacts to the
central repo.
Thanks!
- Ben
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432&version=12349496
There are still two issues left in JIRA:
https://issues.apache.org/jira/projects/MJLINK/issues
Staging repo:
https://repository.apache.org/content/repositories/maven-2064
https://re
To add some more information, I have seen some extreme reduction in
build times after switching from Java 11 to 17 or even 21 (just for
build, not the runtime).
We can still verify it runs on 11/17 by using the integration tests,
but having the (possibly parallel) unit- and integration tests
compil
Adopt-OpenJ9 is now Semeru, and their v21 will be released next week if I
am not mistaken.
I'd love to keep that in, because it is the only JVM which does not run on
hotspot.
On Wed, 10 Jan 2024, 15:40 Slawomir Jaranowski,
wrote:
> śr., 10 sty 2024 o 13:58 Romain Manni-Bucau
> napisał(a):
>
+1
Thanks for the quick fix!
On Thu, 21 Dec 2023, 08:54 Slawomir Jaranowski,
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12354061
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/
> We (as Maven developers) will have to use Java 11 to build plugins but
> not be able to use Java 11 features in the code.
> That sounds frustrating to me :)
> Or I don't understand the change you are trying to propose?
Not at all. This is how I did it at work.
This already removes a lot of frust
Big +1
I sometimes need to switch back from JDK 21 to 17 or earlier to build
some of the plugins.
If we start building with 11+, we can detect build errors easier for newer JDKs.
The spotless profile might not be the only profile we can remove.
One catch, though. Should we not test on JDK8? Maybe
Hi Tison,
do you have access to the issue tracker?
https://issues.apache.org/jira/projects/SUREFIRE/issues
Am Mo., 16. Okt. 2023 um 07:51 Uhr schrieb tison :
>
> Bubble up. Or where I can file an issue to track if it's likely an
> improvement.
>
> Best,
> tison.
>
>
> tison 于2023年9月23日周六 09:48写道
+1
Am So., 5. Nov. 2023 um 20:32 Uhr schrieb Michael Osipov :
>
> Am 2023-11-03 um 21:42 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 7 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12353815
> >
> > There are still a couple of issues left in JIR
+1
On Mon, 23 Oct 2023, 08:11 Slawomir Jaranowski,
wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317224&version=12353735
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20
+1, but consider removing the dependency upgrade for commons from the
release notes. It's been removed anyway.
Improvement
[MDEP-832] - Remove commons-collections-4
vs
Dependency upgrade
[MDEP-869] - commons-collections to 4.4
On Fri, 20 Oct 2023, 23:28 Michael Osipov, wrote:
> Hi,
>
> we
+1
- Ben
Michael Osipov schrieb am Fr., 20. Okt. 2023, 21:45:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12352247
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=proj
+1. -- thanks!
- Ben
Guillaume Nodet schrieb am Fr., 20. Okt. 2023, 23:38:
> I'm starting a new vote to release this new alpha.
>
> This alpha release provides new cornerstone features for the future Maven
> evolution.
> In particular, the POM model which was set in stone to a 4.0.0 version
> s
com/rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <
> > > >
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > > >
> >
venák, wrote:
> What about type=java-agent? Basically a new ArtifactHandler?
>
> See https://maven.apache.org/repositories/artifacts.html
>
> T
>
> On Tue, Oct 17, 2023, 23:54 Benjamin Marwell wrote:
>
> > Hey all,
> >
> > In a mockito issue, JDK maintainers su
Hey all,
In a mockito issue, JDK maintainers suggested to differentiate between
agents and normal dependencies. Starting with JDK 21 already, this makes a
lot of sense: dynamic loading of agents will be a no-go.
One suggestion was:
...
...
+1
On Tue, 17 Oct 2023, 00:50 Slawomir Jaranowski,
wrote:
> Hi,
>
> - Last release was in 2015
> - use Maven 2.2.1
> - we have a Maven Plugin Tools - which should be one project for build and
> check Maven plugins
> - no active development ...
>
>
> https://issues.apache.org/jira/issues/?jql
Basil,
I am a Maven committer. If you want to have replies from specific persons,
don't use the developer mailing list. There is no such role as a core
committer. There's only the PMC, which are not necessarily the most active
committers.
To be honest, I don't think "core" committers will give yo
Hello Basil,
I wrote the mail while the ITs were running.
Please note the naming issue is not "minor". It will break the build very
soon.
There's a reason for this:
SEE:
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html
QUOTE:
You will typically name your plugin -maven-p
Hi Basil,
the first issue I see when using Maven 3.9.2:
[INFO] --- plugin:3.9.0:descriptor (default-descriptor) @ maven-hpi-plugin ---
[WARNING]
Artifact Ids of the format maven-___-plugin are reserved for
plugins in the Group Id org.apache.maven.plugins
Please change your artifactId to the form
+1
Am So., 11. Juni 2023 um 22:14 Uhr schrieb Michael Osipov :
>
> Hi,
>
> we solved 17 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12350597
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MWAR/issues
>
Big +1 for an alternative format, but not sure HOCON is the best of all
those out there.
It surely is one of the better ones, though.
Big plus is easiness to humans, no deps, external docs.
However, TOML gained some popularity. I'd say Maven should ship no more
than one alternative to XML. And w
Hunter,
please keep to facts and do not get on a personal level:
> It isn't OK to just ignore their input
But then you say:
> Your personal taste shouldn't [...]
I think you just ignored some other dev's input yourself, as some already
voted for JDK11+.
> If you leave Java8, you leave behind eve
Ok, here's a benefit of Java 11/17 or two:
* Reduce build matrix, save energy
* Attract devs
* CDS for non-OpenJ9-users
* Better clarity of code (yes, I mean that)
* No additional work (we don't need to migrate, just use the features when
modifying a line for a bug/feature anyway)
* We leave no on
I am pretty sure if that happens (terms&conditions changes, GH not an
option), we have plenty of time to migrate.
The same has happened multiple times in the past: SourceForge, BerliOS,
Google Code...
Now it is ASF JIRA and maybe some day we will be migrating away from GitHub
Issues to something el
Big +1, as more and more projects are already migrating (including Apache
Shiro).
I'd vote for maven-jlink-plugin: Not many issues currently.
> not having to create an issue if a PR exists first
I'd at least make milestones mandatory in that case.
It is far less work than maintaining an issue.
The advantage is simple.
With "maven4" in the module name, you don't need a compatibility matrix on
every plugins homepage or readme.
Just look at npm modules and webpack... Tables over tables...
On Sun, 26 Mar 2023, 19:29 Michael Osipov, wrote:
> Am 2023-03-26 um 19:02 schrieb Romain Manni-
+1 to your proposal
org.apache.maven:maven4-xyz-plugin:
I don't think it would cause too much trouble as Maven APIs will love for a
few years. It will only occasionally break when a new major Maven release
is published. I can live with that.
Also, maven 3 plugins will be compatible for a while.
Big +1!
On Wed, 15 Mar 2023, 15:17 Jorge Solórzano, wrote:
> Hi Maven Devs,
>
> I want to bring up the discussion about the default encoding used in
> Maven, specifically Maven 4.0+ (since it's still in alpha it could be
> done for that release or possibly wait another decade), we are in
> 2023,
No one ever told me about this convention and I knew about it the
moment I saw the version numbers.
However, Elliote is right, that's not semver.
The alternative would be to put a lookup / compatibility table in
each plugin's readme. But that would be so annoying as a user, because
Maven is just S
+1 for dropping. Make it a new minor Version. We may want to add a
migration strategy. But then, if there's not even a hit on GitHub... Just
go with it. We do have a well working mailing list.
On Fri, 10 Mar 2023, 10:56 Olivier Lamy, wrote:
> not sure how useful this feature is...
> I would say
Sadly, --ntp also disables upload progress and ANY information associated
with this.
Maybe it would be beneficial to have an option for that.
On Sun, 19 Feb 2023, 18:26 Michael Osipov, wrote:
> Am 2023-02-19 um 18:17 schrieb Romain Manni-Bucau:
> > Not sure we can find an agreement on this to
+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 maven the related
Hello everyone!
Richard asked me a few days ago to take a look at the TomEE maven
build, as it takes up to a few hours to complete. One issue is the
jenkins setup, granted. But I have two findings.
1. shading
Because a few deps, e.g. Apache MQ RA Client, still do not provide
artifacts with the j
gt; | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le dim. 20 nov. 2022
Hi!
Due to the recent GH activities (eg [1]), it came to my attention that
there is no file ".well-known/security.txt" on maven.apache.org.
We really should adopt it!
For some more information, please refer to [2].
WDYT?
- Ben
[1]: https://github.com/apache/maven-project-utils/pull/5
[2]: http
Please do NOT consider jbake.
We (shiro team) ported the page to jbake, and it is really a mess.
Many things are not supported which can easily be done in other static
site generators.
There is absolutely no progress. No java.time support. JSON/YAML
support is broken and needs a lot of workarounds.
Hi Raivo!
This is a better question for the users list. The developer list is
for maven development.
But long story short:
javax.xml.bind got removed from Java 9+. So even if you are compiling
TO java 8 (e.g. using switches like maven.compiler.release or
maven.compiler.target), it will still not
> Maven Plugin code should use Plugin Api for logging purpose
> In shared libraries used by Maven and maintained by us - we will use
SLF4J directly
I asked to be allowed to put this on the logging site, but we never had
consensus of this. I agree 💯 here, but ut really needs to get documented.
I sa
+1, BUT in addition to Hervé's answer:
Create a file '.git-blame-ignore-revs', which seems to be a common convention:
https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame
This way, we can see CODE changes via diff/blame without those nasty
formatting changes.
---
For the fo
Unpopular opinion:
Deactivate automatic push. If release:perform went well, push main and the tags.
Besides, push --delete works for tags, too (if PMC agrees).
I doubt there are already forks from the tag active anywhere.
But yes, bumping the version is what we used to do in this case.
- Ben
Am
add-exports
> jdk.compiler/com.sun.tools.javac.code=com.foo.mymodule and my module reads
> jdk.compiler. All of that is incompatible with --release.
>
> Best,
> Laird
>
> On Thu, Sep 1, 2022 at 11:47 PM Benjamin Marwell
> wrote:
>
> > Can you give us a hint why you ar
Can you give us a hint why you are using source and target instead of
the release parameter?
Am Fr., 2. Sept. 2022 um 01:10 Uhr schrieb Laird Nelson :
>
> The problem was difficult to uncover due to the swallowed exception at
> https://github.com/apache/maven-surefire/blob/surefire-3.0.0-M7/maven-
Haven't seen a discussion in Slack or on the mailing list, so I guess no.
But I like the idea. Be aware that there are still Junit3 tests iirc.
Updating would be a breaking change, but that's okay for the upcoming Maven
4 release.
On Fri, 12 Aug 2022, 01:37 Vladimir V. Bychkov, wrote:
> H
nd also the
> >
>
> +1
>
>
> > -DtrimStackTrace=false.
> >
>
> surefire has been changed in 3.0.0-M6 with this default value ;)
>
>
> >
> > Le jeu. 21 juil. 2022 à 20:24, Benjamin Marwell a
> > écrit :
> >
> > > Hi every
No, 2 JDKs are not required by default. Only if you use --release={<17} and
don't trust running tests on 17 are the same as running tests on 8.
Yes, there are changes (certificates, XML libs, rhino, etc).
So, for most projects that's probably not needed. For those who think it is
needed, I don't h
here in many years
>
> Le jeu. 21 juil. 2022 à 18:53, Benjamin Marwell a
> écrit :
>
> > I was going to answer: go for 17.
> >
> > But running the tests on the same language level is really a good
> argument.
> > So much changed: HttpClient, TLS and ci
Hi everyone,
as discussed in Slack, here are a few ideas for Maven 4.0 Plugin
default's changes.
Rationale: Convention over configuration, but things have diverged
from when Maven 3 was started.
* Set the default Java Source file encoding to UTF-8.
This seems to receive a broad agreement. Not onl
I was going to answer: go for 17.
But running the tests on the same language level is really a good argument.
So much changed: HttpClient, TLS and cipher suites, DNS resolution
(starting with Java 18 it will be pluggable!) etc.
Yes, in theory it should not fail. But this is (sadly) a strong argum
Here you go.
https://issues.apache.org/jira/browse/MSHARED-1032
On Mon, 11 Jul 2022, 20:21 Benjamin Marwell, wrote:
>
> Please note there are more exceptions, e.g. in reporting. That's always
> been a problem. Not sure, but I must have opened an issue for this
> somewhere.
Please note there are more exceptions, e.g. in reporting. That's always
been a problem. Not sure, but I must have opened an issue for this
somewhere.
Just for the sake of completeness.
On Mon, 11 Jul 2022, 14:12 Guillaume Nodet, wrote:
> Yes, that's why I only kept a single exception in the ne
You can use this solution.
https://github.com/heiseonline/shariff
The PHP part is not needed, only if you want to display share count.
It's widely known in Germany due to the c't magazine, but not much
maintained anymore. Same applies to the forks.
However, works like a charm.
WDYT?
On Sat, 11
Thanks everyone involved, and thank you to Brian Demers for starting this
project in the first place!
On Sat, 14 May 2022, 16:07 Hervé Boutemy, wrote:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven
> Wrapper, version 3.1.1.
>
> The Maven Wrapper is an easy wa
Hi Daniele,
sorry that no one has answered you in more than a month.
We can all help with specific questions, but I guess there are too few
volunteers to make it an ASF project.
However, there is also the mojohaus organization which has seen some
activity lately.
Would that work for you?
Am Mo.
Hi Tim,
tbh I did not even notice, because I use Java 11 to compile Java 8 projects.
You can either use the properties maven.compiler.source/target or
maven.compiler.release (recommended for Java 9+).
This would require Java 11+ for your build, but the compiled bytecode
will still be Java 8 bytec
undation
> V.P., Data Privacy
>
>
> On Sun, Mar 6, 2022, at 18:37, Benjamin Marwell wrote:
>
>
> Exactly for this question I CC'd Martijn 😅. You accidentally clicked on
> "reply" instead of "reply all", I guess...
>
> You can also find us in
1 - 100 of 201 matches
Mail list logo
