yup it's only a cli generator/executor and this upgrade is not really
mandatory.
but it just doesn't make much sense for me to be java7 as the goal is to
execute a cli which is only available >=9 :)
On Wed, 19 Feb 2020 at 17:53, Romain Manni-Bucau
wrote:
> If upgrading helps I dont see how it c
If upgrading helps I dont see how it could hurt but I see it as a process
executor so shouldnt be important, no?
Le mer. 19 févr. 2020 à 08:39, Olivier Lamy a écrit :
> Hi
> I was looking at jlink plugin and trying it.
> I'm using java11 and got issues because of this..
> Easy fix is upgrading p
Hi
I was looking at jlink plugin and trying it.
I'm using java11 and got issues because of this..
Easy fix is upgrading plexus-java version
But I noticed java for jlink plugin is java7.
As jlink has been released with java9 I wonder if this java7 minimum really
makes sense?
cheers
--
Olivier Lam
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12345961&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1552/
https://repository.apache.org/content/repositories/maven-1552/org/apache/maven/doxia/dox
All done. All note with pointers to both project readme files, closed all
issues and closed all PRs. Hopefully further input and help will show up here
now.
Manfred
Robert Scholte wrote on 2020-02-18 10:56 (GMT -08:00):
> sure, go ahead
> On 18-2-2020 19:47:29, Manfred Moser wrote:
> Okay ..
Hi,
The vote has passed with the following result:
+1 : Sylwester Lachiewicz, Michael Osipov, Olivier Lamy, Tibor Digana, Hervé
Boutemy
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsubscri
sure, go ahead
On 18-2-2020 19:47:29, Manfred Moser wrote:
Okay .. so then I think I should update the Takari repos with a note about that
and send any contributors to the Maven dev list NOW. I think this has the
potential to drive some more help in this effort.
If you agree I can do that tonig
I've created MWRAPPER in Jira[1] so please register those wishes there.
Be aware that the wrapper already exists and that a buildtoold like Maven is
already about downloading and executing.
The community is asking for the wrapper because they like that feature in tools
like Gradle.
I understand
Okay .. so then I think I should update the Takari repos with a note about that
and send any contributors to the Maven dev list NOW. I think this has the
potential to drive some more help in this effort.
If you agree I can do that tonight ..
manfred
Robert Scholte wrote on 2020-02-18 10:40
This will be part of 3.7.0 together with other huge changes.
Having the wrapper makes it possible to start updating the defaults for our
Maven plugins.
I don't expect a release soon and I don't see a reason to hurry that.
We've done 3.6.2 and a 3.6.3 regression release to give us time to work on
Robert>Once the Maven Wrapper has it's final location, one can provide new
PRs on our codebase
Do you think Wrapper script should verify the integrity of the downloaded
file?
AFAIK the current implementation just downloads a file and executes it.
Executing random files from the internet does not s
Agreed... if you think now is a good time, I am happy to update the Takari
repos with a redirect to the maven dev list and the sandbox repo for now.
I plan to close all issues and all PR and declare the project inactive and
moved to Apache Maven upstream. Just not sure what the best timing for
Would this simply affect the output of what's shown to the user by
maven dependency:tree or would it also affect the order of resolution
for compile, exec:java, and everything else?
On Mon, Feb 17, 2020 at 3:28 PM Loïc Le Doyen wrote:
>
> Hello @dev team !
>
> Being a frequent user of the *maven-
13 matches
Mail list logo
