Hi Team,
I am trying to pass jvmArguments in plugin but they are not working.
We are using embedded cassandra in our application and it tries to access
JDK's internal classes and after JDK 11 Java has put strict checks on
internal class access using reflection . There is one work-around for it
Missed plugin name, I am using appassembler-maven-plugin
I have tried and but both are not
working
Thanks & Regards,
Ankit
On Wed, Jun 3, 2020 at 6:39 PM Ankit Tomar
wrote:
> Hi ,
>
> Please suggest how to pass these arguments to the plugin.
>
> On Tue, Jun 2, 2020 at 11:13 PM Ankit Tomar
jonvolfson commented on a change in pull request #31:
URL: https://github.com/apache/maven-site-plugin/pull/31#discussion_r434863055
##
File path: src/it/projects/MSITE-856/verify.bsh
##
@@ -0,0 +1,48 @@
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ *
Based on https://www.apache.org/dev/licensing-howto.html
[https://www.apache.org/dev/licensing-howto.html] it looks like I should add
these to the distributions as well, but to me it doesn't make sense to unpack
these files into the targeted directory.
Robert
On 3-6-2020 21:00:47, Christofer
Well doesn't have to be compatible as long as it does what it's supposed to.
Was just asking as I wrote the Downloader to enable Apache projects to use the
maven wrapper (No checked in binaries)
Unfortunately we always were required to maintain the NOTICE reference that the
scripts and the java
elharo commented on a change in pull request #31:
URL: https://github.com/apache/maven-site-plugin/pull/31#discussion_r434760284
##
File path: src/it/projects/MSITE-856/src/site/site.xml
##
@@ -0,0 +1,30 @@
+
+
+
+
+http://maven.apache.org/DECORATION/1.6.0;
+
Looks good to me.
I expect some trouble when moving plugins from Maven 3.0 to 3.1.0, so I've
started a wiki page[1] with the first known issue and solution.
Robert
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857
ps. As long as Maven isn't bundled with its own
Starting with Maven 3.7.0 there will be 3 wrapper distributions,
org.apache.maven:apache-maven-wrapper
and with the following classifiers:
script: mvnw, mvnw.cmd, mvnwDebug, mvnwDebug.cmd,
.mvn/wrapper/maven-wrapper.properties
bin: like script, but also .mvn/wrapper/maven-wrapper.jar
source:
jonvolfson commented on a change in pull request #31:
URL: https://github.com/apache/maven-site-plugin/pull/31#discussion_r434688818
##
File path: src/main/java/org/apache/maven/plugins/site/render/SiteMap.java
##
@@ -172,9 +172,13 @@ private static void extractItems( List
Hi ,
Please suggest how to pass these arguments to the plugin.
On Tue, Jun 2, 2020 at 11:13 PM Ankit Tomar
wrote:
> Hi Team,
>
> I am trying to pass jvmArguments in plugin but they are not working.
> We are using embedded cassandra in our application and it tries to access
> JDK's internal
On Wed, 3 Jun 2020 at 4:56 pm, Michael Osipov wrote:
> Am 2020-06-03 um 03:00 schrieb Olivier Lamy:
> > Hi
> > Please comment or (not) complain on this change.
> > html version https://maven.apache.org/developers/compatibility-plan.html
>
> LGTM
>
> > PS: FYI Eclipse will be jdk11 in September
>
Thanks for reading this
On Wed, 3 Jun 2020 at 6:28 pm, Anders Hammar wrote:
> A few comments:
>
> 1. I think we should separate the prerequisites for Maven core and those
> for our plugins.
> 2. Do users really care about "Maven Plugin API"? I think that an end user
> would like to know what
definitely +1
On Wed, 3 Jun 2020 at 18:08, Romain Manni-Bucau
wrote:
> Hi everyone,
>
> Shouldn't we set trimStackTrace=false by default?
> Current state makes the log quite useless since there is never the data you
> need to understand why it failed so it just mess up the output without
>
A few comments:
1. I think we should separate the prerequisites for Maven core and those
for our plugins.
2. Do users really care about "Maven Plugin API"? I think that an end user
would like to know what version of Maven (core) that a plugin will work
with.
/Anders
On Wed, Jun 3, 2020 at 3:01
Il giorno mer 3 giu 2020 alle ore 10:08 Romain Manni-Bucau <
rmannibu...@gmail.com> ha scritto:
> Hi everyone,
>
> Shouldn't we set trimStackTrace=false by default?
>
+1
It is very awkward current default (trimStackTrace=true)
Enrico
> Current state makes the log quite useless since there is
Hi everyone,
Shouldn't we set trimStackTrace=false by default?
Current state makes the log quite useless since there is never the data you
need to understand why it failed so it just mess up the output without
added value IMO.
Wdyt?
Romain Manni-Bucau
@rmannibucau
The Apache Maven team is pleased to announce the release of the Maven
Resolver Ant Tasks version 1.2.1.
https://maven.apache.org/resolver-ant-tasks/
Release Notes - Maven Resolver Ant Tasks - Version 1.2.1
** Bug
* [MRESOLVER-100] - Resolver Ant Task taskdef failing
** Improvement
*
Congrats on this ...
As the rest is usually just dropping the mwnw scripts, the config file and my
downloader.java ...
is there an apache package we can now just drop in to replace the old and get
rid of the Notice stuff?
Chris
Am 02.06.20, 22:36 schrieb "Robert Scholte" :
Hi,
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Sylwester Lachiewicz, Hervé Boutemy, Olivier Lamy
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
Am 2020-06-03 um 03:00 schrieb Olivier Lamy:
Hi
Please comment or (not) complain on this change.
html version https://maven.apache.org/developers/compatibility-plan.html
LGTM
PS: FYI Eclipse will be jdk11 in September
https://www.eclipse.org/lists/cross-project-issues-dev/msg17532.html
I
20 matches
Mail list logo