Hi Ben,
Nice!
https://github.com/apache/maven-jlink-plugin/blob/master/src/it/projects/MJLINK-52_classifiers_jarproject/pom.xml
This is what I as looking for, even if an explicit
jlink has t be defined.
Thanks!
Cheers,
Andres
---
Java Champion; Groovy En
Le mardi 15 décembre 2020, 22:53:47 CET Andres Almiray a écrit :
> Hello,
>
> Not that I want to hijack this thread but considering that the move is from
> a fix release to a minor release I wonder about the use of
> jlink.
>
> For a multi-module project having this packaging option is not much o
Merci! Yes, I cannot change releases, so highly appreciated!
I might ping you again about the release, as I created a
ECDSA OpenPGP key, which nexus does not yet recognize.
Thanks!
Ben
On 16.12.20 08:06, Hervé BOUTEMY wrote:
given the number of new features, yes, switching to 3.1.0 makes sense
Not that I want to hijack this thread
No worries! It is always good to have an extra pair of eyes look at
the work of a new committer. ;-)
However for single project builds the jlink would
prevent other packaging options, wouldn't it?
I created ITs, but this set-up is not an the list:
https://
given the number of new features, yes, switching to 3.1.0 makes sense
I just renamed the next release to 3.1.0 in Jira (I fear you don't have
permissions)
No need to create 3.0.x Git branch for now, unless you really have a specific
reason to do so: we generally don't try to maintain multiple ve
+1 for 3.1.0 release
wt., 15 gru 2020 o 22:38 Benjamin Marwell napisał(a):
>
> Hello everyone,
>
> looking at the issues already solved and soon-be-solved, the next release
> feels much more like a 3.1.0 release than a 3.0.1 (bugfix) release [1].
>
> If you agree, I would like to update the git r
Hello,
Not that I want to hijack this thread but considering that the move is from
a fix release to a minor release I wonder about the use of
jlink.
For a multi-module project having this packaging option is not much of a
problem, as if the project produces more than one artifact (such as a
shade
Hello everyone,
looking at the issues already solved and soon-be-solved, the next release
feels much more like a 3.1.0 release than a 3.0.1 (bugfix) release [1].
If you agree, I would like to update the git repository to 3.1.0 and create
a 3.0.x branch from the last release, if needed.
I would a
