There is Jira issue reported
https://issues.apache.org/jira/browse/SUREFIRE-1664
Every volunteer is welcome!
On Sun, Jun 2, 2019 at 11:23 PM James Gough wrote:
> Hi,
>
> I've just started looking into
> https://issues.apache.org/jira/browse/MTOOLCHAINS-21, which is a bug
> report
> about Toolcha
Hi,
I've just started looking into
https://issues.apache.org/jira/browse/MTOOLCHAINS-21, which is a bug report
about Toolchains having a dead link to wiki pages previously hosted on:
http://docs.codehaus.org/display/MAVENUSER/Toolchains+Plugin
I had a look at a few other pages to get an idea what
The Apache Maven team is pleased to announce the release of the Apache
Maven Doxia, version 1.9
https://maven.apache.org/doxia/
Release Notes - Maven Doxia - Version 1.9
** Bug
* [DOXIA-497] - APTSink: links and paragraphs inside tables
* [DOXIA-538] - Tag used for monospaced is not
Hi,
The vote has passed with the following result:
+1: Michael Osipov, François Papon, Tibor Digana, Karl Heinz Marbaise,
Sylwester Lachiewicz
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file and add this release the board report.
We are working hard to get this done.
I will commit as soon as CI is green (blue...)
Enrico
Il sab 1 giu 2019, 10:02 Enrico Olivelli ha scritto:
> If there is any complaint I will commit the change.
> We are already moving to java8 other plugins that are not part of the core
> lifecycle (Maven
Tibor,
Il dom 2 giu 2019, 15:32 Tibor Digana ha scritto:
> Enrico, I sent you a message regarding this question on GitHub, pls see it
> here
> https://github.com/apache/maven-archetype/pull/28#issuecomment-498030811
Thank you so much
Enrico
>
> On Sun, Jun 2, 2019 at 12:44 PM Enrico Oliv
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 30.05.19 17:26, Michael Osipov wrote:
Hi,
We solved 22 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230&version=12342342
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues
Am 2019-05-30 um 17:26 schrieb Michael Osipov:
Hi,
We solved 22 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317230&version=12342342
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIA%20AND%20resolut
Enrico, I sent you a message regarding this question on GitHub, pls see it
here
https://github.com/apache/maven-archetype/pull/28#issuecomment-498030811
On Sun, Jun 2, 2019 at 12:44 PM Enrico Olivelli wrote:
> Hi,
> I am not able to understand why integration tests of Maven Archetype plugin
> ar
I’m going to add a test where the “newer” pom has an incompatible schema
with only modelVersion retained to ensure the parser errors get dismissed
and we bomb early with the modelVersion complaint
On Sat 1 Jun 2019 at 22:05, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Ok I've swi
Hi,
I am not able to understand why integration tests of Maven Archetype plugin
are randomly failing here:
https://builds.apache.org/job/maven-box/job/maven-archetype/job/ARCHETYPE-567/
I ca't reproduce the failures.
Is there any way to see the logs of the integration tests ? like having a
ZIP of
For better dynamic ranges we need GROOVY-8704 (IntRange should be
Serializable) first:
[1] https://issues.apache.org/jira/browse/GROOVY-8704
On Sun, 02 Jun 2019 12:16:32 +0200, Enrico Olivelli
wrote:
It seems to me that they are already skipped
https://gitbox.apache.org/repos/asf?p=mave
I've added this line to the asfMavenTlpPlgnBuild.groovy:
// minimum, LTS, current and next ea
minimum: right now Java 7 for most of our projects
LTS: Java 8 + 11
current: Java 12
next ea: Java 13
Not sure which projects still use other versions, probably does with
dedicated range. They simply
It seems to me that they are already skipped
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob_plain;f=vars/asfMavenTlpPlgnBuild.groovy;hb=HEAD
But in some cases, like in the checkstyle plugin, we have a custom liat
jdks on the Jenkins file.
I am going to do the same for the mave
Agree, let's skip 9 and 10.We can always add them later should lots of users
surface, but I believe that's unlikely.
On Sun, Jun 2, 2019, 19:28 Stephen Connolly
wrote:
EOL not rolling (autocorrect)
On Sun 2 Jun 2019 at 10:27, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> +1 to
+1 for deleting 9 1nd 10.
yes, there's a statement by Robert "all non-EOL versions and the first EA".
Now that includes 7 and 8 .
On Sun, Jun 2, 2019 at 10:42 AM Enrico Olivelli wrote:
> Hi,
> To me it is not clear if we should keep tests against java 9 and java 10.
>
> I think it is mostly a wa
Am 2019-06-02 um 10:42 schrieb Enrico Olivelli:
Hi,
To me it is not clear if we should keep tests against java 9 and java 10.
I think it is mostly a waste of resources and time.
Do we have a clear and documented statement about which versions are
supported and tested ?
Drop them, there are no
EOL not rolling (autocorrect)
On Sun 2 Jun 2019 at 10:27, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> +1 to Drop. They are rolling
>
> On Sun 2 Jun 2019 at 09:42, Enrico Olivelli wrote:
>
>> Hi,
>> To me it is not clear if we should keep tests against java 9 and java 10.
>>
>> I
+1 to Drop. They are rolling
On Sun 2 Jun 2019 at 09:42, Enrico Olivelli wrote:
> Hi,
> To me it is not clear if we should keep tests against java 9 and java 10.
>
> I think it is mostly a waste of resources and time.
>
> Do we have a clear and documented statement about which versions are
> sup
Hi,
To me it is not clear if we should keep tests against java 9 and java 10.
I think it is mostly a waste of resources and time.
Do we have a clear and documented statement about which versions are
supported and tested ?
Thoughts?
Enrico
20 matches
Mail list logo
