Dear Maven Developers,
today I'd like to propose a new core feature of Maven: Maven Workflows.
Since several time there had been workflow-style plugins, i. e. plugins that
simply execute mojos of other plugins in a particular sequence. Well-known
examples are the Maven Release Plugin
In the very long term I would be +1 for JAXB, as clearly much more Java
programmers on earth are used to JAXB than with Modello due to it being a
former part of the JRE. It now is open source at the Eclipse Foundation, so we
all can contribute to it, which could make it a success story.
But I
Looking at the impressively reduced bootstrap times of modern JDKs with
features like Automatic AppCDS, I wonder if in the year 2021 this still makes
sense? In rather near future there will be native precompilation available in
most JDKs, effectively reducing bootstrap time to few ms. So is it
:31 Markus KARG, wrote:
> We should not do any tricks or unexpected behavior but just stick with
> SemVer.
> If there is a need for a security fix, it has to be 3.6.4 and BTW there
> should be an option to still use unsecure http as many people run http in
> their LANs.
> If
>> - Why not 3.7.0?
>> Apache Maven 3.7.0 has been advertised in the past that it would be the
>> first release where you could optionally activate the build/consumer
>> feature: the version containing this feature has been renamed to 4.0.0.
>> Reusing 3.7.0 might lead to confusion, hence we
We should not do any tricks or unexpected behavior but just stick with SemVer.
If there is a need for a security fix, it has to be 3.6.4 and BTW there should
be an option to still use unsecure http as many people run http in their LANs.
If it contains backwards-compatible features, it has to be
Yes, there is an API to embed Maven.
-Markus
-Ursprüngliche Nachricht-
Von: Som Lima [mailto:somplastic...@gmail.com]
Gesendet: Sonntag, 28. März 2021 06:26
An: dev@maven.apache.org
Betreff: Running maven from inside JVM.
Hi,
Is it possible to run maven from inside JVM ?
i.e.
Java
LGTM. Please tell me when done! ;-D
-Markus
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Donnerstag, 25. Februar 2021 16:16
An: Maven Developers List
Betreff: Re: Future of maven scripting plugin, java?
Le jeu. 25 févr. 2021 à 15:28, Markus
Romain,
just to understand your target: In the end what you want is that the Java
scripting plugin will execute Java source code, just like jshell does? That
sounds interesting to me.
-Markus
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet:
linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le sam. 20 févr. 2021 à 09:14, Markus KARG a
écrit :
> I second that. It is counterintuitive. It would be beneficial if -pl !X
> would also exclude ist submodules.
&g
I second that. It is counterintuitive. It would be beneficial if -pl !X would
also exclude ist submodules.
-Markus
-Ursprüngliche Nachricht-
Von: Falko Modler [mailto:f.mod...@gmx.net]
Gesendet: Samstag, 20. Februar 2021 01:39
An: dev@maven.apache.org
Betreff: Maven 4: -pl !... is not
munity, not having access
to dedicated routes to central other than OSSRH, is suffering that's all.
Matthieu
On Fri, Jan 22, 2021 at 6:46 PM Markus KARG wrote:
> If you follow the official twitter channel then you will learn that the
> problem is simply the internal load of the free OSSRH se
If you follow the official twitter channel then you will learn that the problem
is simply the internal load of the free OSSRH service, which is just one of
several ways onto Maven Central. At the Eclipse Foundation for example, we have
our own Sonatype-powered instance with separate workload
I have 2 +1 for https://github.com/apache/maven/pull/421, so can somebody
please merge this PR (I am not a committer)?
Thanks!
-Markus
Well, whether or not switching off a build platform should more be a question
of: Why have we switched it on actually?
-Markus
-Ursprüngliche Nachricht-
Von: Gary Gregory [mailto:garydgreg...@gmail.com]
Gesendet: Mittwoch, 30. Dezember 2020 15:14
An: Maven Developers List
Betreff: Re:
>> Regarding javax: No, this was not the free decision of the Jakarta EE WG,
>> this was the SOLE CHOICE we had due to Oracle, as they forbid ALL changes
>> to the javax namespace, so the were FORCED to rename the workspace. Believe
>> me, nobody in the Jakarta EE WG thought that this is a good
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Montag, 28. Dezember 2020 17:14
An: Maven Developers List
Betreff: Re: Maven 4 / @Inject
Le lun. 28 déc. 2020 à 16:44, Markus KARG a écrit :
> I don't like the idea of simply keeping javax "an
tion-development/java-ee-8-high-performance>
Le lun. 28 déc. 2020 à 15:51, Markus KARG a écrit :
> With "dead" I mean: Nobody is allowed to add anything new in that namespace
> -- neither classes nor interfaces nor even new parameters.
>
> I would like that Maven 4
apache.org]
Gesendet: Montag, 28. Dezember 2020 14:59
An: dev@maven.apache.org
Betreff: Re: Maven 4 / @Inject
Am 2020-12-28 um 14:56 schrieb Markus KARG:
> We are used to "import javax.inject.*" in Maven, but that namespace if
dead
> since Jakarta EE 9. Since November the new nam
We are used to "import javax.inject.*" in Maven, but that namespace if dead
since Jakarta EE 9. Since November the new namespace is released "import
jakarta.inject.*". I wonder if Maven 4 really still wants to stick with the
dead namespace instead, or whether it makes sense that we adopt the new
ake Apache projects more agile and
more friendly for external contributors.
For example I did a few feature / fix for maven-invoker-plugin and I wait
about year for release next version, I don't have knowledge when it can
happen ...
pon., 28 gru 2020 o 14:04 Markus KARG napisał(a):
>
Please turn it into an official Maven plugin, as there are many people out
there reluctant when it comes to third party due to sustained support etc.! :-)
-Markus
-Ursprüngliche Nachricht-
Von: Slawomir Jaranowski [mailto:s.jaranow...@gmail.com]
Gesendet: Montag, 28. Dezember 2020
Sandra,
welcome in the Maven dev community! :-)
I think a good starting point would be to simply write up your personal
lessions lerned, so others can then add PRs ontop with their additions.
Regards
-Markus
P.S.: Like to join us at JavaLand 2021's community workshop on becoming a Maven
Just pick anything you do have fun with working on. :-)
-Markus
-Ursprüngliche Nachricht-
Von: Andrey Fadeev [mailto:aaa...@yandex.ru]
Gesendet: Dienstag, 22. Dezember 2020 12:53
An: dev@maven.apache.org
Betreff: First issue
Hello everyone!
I'd like to contribute in order to learn
ell
will report back to you when I can compile and test
gruss
martin
_
From: Markus Karg
Sent: Thursday, December 3, 2020 12:23 PM
To: dev@maven.apache.org
Subject: Help Wanted
I would be super happy if somebody of the Maven Heros could help me with my
PR as I am totally stuc
, 12. Dezember 2020 12:46
An: dev@maven.apache.org
Betreff: Re: [DISCUSS] Allow attributes shorthand in pom.xml
Am 2020-12-12 um 11:04 schrieb Markus KARG:
> Wouldn't it be a more modern and even more effective approach to add JSON
> support for POMs? We could keep POM.xml for legacy reasons b
d by Maven.
This is a clear separation, and it will give the Maven team the opportunity to
focus on the real issues.
So please join your forces and spend your energy on improving polyglot!
thanks,
Robert
On 12-12-2020 11:04:33, Markus KARG wrote:
Wouldn't it be a more modern and even more effective appro
Wouldn't it be a more modern and even more effective approach to add JSON
support for POMs? We could keep POM.xml for legacy reasons but add support for
POM.json files.
-Markus
-Ursprüngliche Nachricht-
Von: Will Iverson [mailto:wiver...@gmail.com]
Gesendet: Freitag, 11. Dezember 2020
I would be super happy if somebody of the Maven Heros could help me with my PR
as I am totally stuck!
https://github.com/apache/maven-dependency-plugin/pull/109
Anybody having an idea how I can solve this?
Thanks!
-Markus
In fact, as along term user of Maven and Linux, I actually even dislike that
binary JARs are rebuilt from scratch, as this is not what WORA was invented
for. It adds no benefits, it just adds new bugs happening on one distro but no
on another. If you ask me, immediately stop doing that and
Dear Maven Developers,
I’d like to kindly request your feedback on my PRs:
https://github.com/apache/maven-dependency-plugin/pull/109
https://github.com/apache/maven-dependency-plugin/pull/87
Thanks a lot!
-Markus
, and yes, that could mean that PRs will stay
unanswered.
IF we would also join hacktober, we must change those priorities for a month
and focus on that, maybe even using the time to respond the open PRs.
thanks,
Robert
On 4-10-2020 13:36:52, Markus KARG wrote:
Robert,
in fact I think it would
Robert,
in fact I think it would be an even better signal to new contributors is at
least 5 committers would agree to pick up PRs for a whole year.
-Markus
-Ursprüngliche Nachricht-
Von: Robert Scholte [mailto:rfscho...@apache.org]
Gesendet: Sonntag, 4. Oktober 2020 10:55
An: Maarten
b <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le mer. 19 août 2020 à 14:35, Markus KARG a écrit :
> I do not support your judgement. That bug you mention wa
I do not support your judgement. That bug you mention was fixed nine years ago,
so even the most exotic platforms should have adopted the fix meanwhile. This
IS reliable and not more nor less buggy than any other part of the JRE. What we
should do is give intensive tensting of Stefan's PR, but
to stick with older junit then you can implement your
AssumptionViolatedException to extend BuildFailureException
any feedback from junit author on this behaviour?
gruss
~martin~
From: Markus KARG
Sent: Monday, August 17, 2020 1:53 PM
To: 'Maven Developers List
*
>> * @deprecated Please use {@link
>> org.junit.AssumptionViolatedException}
>> instead.
>> */
>> @Deprecated
>> public AssumptionViolatedException(String assumption, Throwable e) {
>> this(assumption, false, null, null);
>>
sumptionViolatedException does not
FAIL test-case is intended behaviour?
martin
From: Markus KARG
Sent: Sunday, August 16, 2020 1:39 PM
To: 'Maven Developers List'
Subject: AW: Assumption fail treated as unexcepted exception?!
The debug output is quite huge, so I won't put it her
So the bug is that Maven Dependency Plugin's test suite uses the JUnit 4
library for test-compile, but actually executes the tests using JUnit 3, right?
-Markus
-Ursprüngliche Nachricht-
Von: Tibor Digana [mailto:tibordig...@apache.org]
Gesendet: Montag, 17. August 2020 14:09
An:
with JUnit 4.12 and whatever plugin version.
Turn this code to your specifics one by one and you will see what you have
added necessarily has changed the behavior.
T
On Sun, Aug 16, 2020 at 1:40 PM Markus KARG wrote:
> Guys,
>
>
>
> I'm stuck with working on a new feature due to
ed it's hard to tell if it's correct or not.
John
On Sun, 16 Aug 2020 at 13:31, Martin Gainty wrote:
>
> MG>below
>
>
> From: Markus KARG
> Sent: Sunday, August 16, 2020 7:40 AM
> To: dev@maven.apache.org
> Subject: Assumption fail treate
with it.
-Markus
-Ursprüngliche Nachricht-
Von: Martin Gainty [mailto:mgai...@hotmail.com]
Gesendet: Sonntag, 16. August 2020 14:24
An: Maven Developers List
Betreff: Re: Assumption fail treated as unexcepted exception?!
MG>below
From: Markus
Happens with surefire 2.22.0 (but also with 3.0.0-M5, just tried it).
Just added the assumption, did not otherwise touch any config properties, but
maybe maven dependency plugin's existing build does that (haven't read the
complete source). Any clue which property to search for which could
option tell
Maven it shall SKIP instead of ERROR on failing assumptions?!
Thanks in advance!
-Markus Karg
invest in other issues.
Robert
On 13-4-2020 19:43:44, Markus KARG wrote:
What users finally expect is to have multirelease JAR building being a Maven
native functionality. This means, it should be as-easy-as putting code in these
folders:
src/main/java/9/
src/main/java/
src/main/java/11
What users finally expect is to have multirelease JAR building being a Maven
native functionality. This means, it should be as-easy-as putting code in these
folders:
src/main/java/9/
src/main/java/
src/main/java/11/
then perform
mvn clean package
to get a multi-release jar -- without *any*
Great to hear!
Here is my personal wish list. ;-)
IMHO generally a good idea is to provide public releases of all maven plugins
and mojohouse plugins which had not been release within 12 months, so we all
can get rid of depending on -SNAPSHOTs and private forks. :-)
When asking for
Thanks! :-)
-Markus Karg
-Ursprüngliche Nachricht-
Von: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Gesendet: Mittwoch, 11. März 2020 19:08
An: Maven Developers List
Cc: Maven Project Management Committee List
Betreff: [RESULT] [VOTE] Release Apache Maven Dependency Plugin version
]
Gesendet: Freitag, 14. Februar 2020 21:25
An: Maven Developers List
Betreff: Re: AW: [ANN] Apache Maven Shade Plugin 3.2.2 Released
thanks for the positive feedback :)
Le vendredi 14 février 2020, 17:02:36 CET Markus KARG a écrit :
> Yippi! :-)
>
> -Ursprüngliche Nachricht-
>
Yippi! :-)
-Ursprüngliche Nachricht-
Von: Hervé Boutemy [mailto:hbout...@apache.org]
Gesendet: Donnerstag, 13. Februar 2020 22:03
An: annou...@maven.apache.org; us...@maven.apache.org; dev@maven.apache.org
Betreff: [ANN] Apache Maven Shade Plugin 3.2.2 Released
The Apache Maven team is
+1 :-)
-Ursprüngliche Nachricht-
Von: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Gesendet: Samstag, 8. Februar 2020 21:53
An: Maven Developers List
Betreff: Re: Releasing Maven Shade Plugin
perfect plan: everything seems ready for the immediate release, the rest
will
come in a few
+1 ! :-)
Nothing to add from my side.
-Markus
-Ursprüngliche Nachricht-
Von: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Gesendet: Samstag, 8. Februar 2020 00:47
An: Maven Developers List
Betreff: Releasing Maven Shade Plugin
I'd like to release this plugin: anything to add before
I desperately wait for publication of Maven Dependency Plugin v3.1.2. v3.1.1
was release in 2018 already, which is more than one year ago. There are
several features I desperately need to use in production, so I kindly like
to ask what the plan for releasing 3.1.2 is. Thanks.
-Markus
Dear Committers,
I'd kindly like to ask for consideration of my PR:
http://github.com/apache/maven-shared/pull/12
Regards
-Markus
: mar...@headcrashing.eu
Subject: Re: Please consider my PRs :-)
Hello, Markus,
are you aware, that plexus-utils is being replaced by the maven-shared-utils?
Jochen
On Sun, Jun 12, 2016 at 6:03 PM, Markus KARG <mar...@headcrashing.eu> wrote:
> Hello Maven Committers,
>
>
>
> I
Hello Maven Committers,
I would like to kindly ask to consider my PRs for merging:
* Plexus Utils: https://github.com/codehaus-plexus/plexus-utils/pull/12
* Plexus Utils: https://github.com/codehaus-plexus/plexus-utils/pull/13
* Maven Plugins:
error message=Unable to create Marker: C:\Users\Markus
Karg\workspace\maven-dependency-plugin\target\markers\testGroupId-release-jar-1.0.unresolved
type=org.apache.maven.plugin.MojoExecutionExceptionorg.apache.maven.plugin.MojoExecutionException:
Unable to create Marker: C:\Users\Markus
Karg
As a Maven user I think that everybody who is working on a project should
behave the same. Hence, I would say, PMC members should rather certainly
demonstrate how to live the community rules.
-Ursprüngliche Nachricht-
Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Just found it... It's a bit small and hidden due to the black colour.
-Original Message-
From: Markus KARG [mailto:mar...@headcrashing.eu]
Sent: Sonntag, 15. Juli 2012 09:17
To: 'Maven Users List'; dev@maven.apache.org
Subject: RE: Issue-wise Crowdfunding platform for Maven
Would
Would be good if each funding item would contain a link to the particular
item in the project's tracker, so it is easier to learn about the issue's
details.
-Original Message-
From: tony Tony [mailto:t...@freedomsponsors.com]
Sent: Freitag, 13. Juli 2012 22:38
To:
60 matches
Mail list logo
