Hi,
I'd like to prepare an alpha release of the Maven JDeprScan Plugin
It is a wrapper around the jdeprscan tool[1], available since Java 9.
You use the jdeprscan tool as a static analysis tool that scans a jar
file (or some other aggregation of class files) for uses of deprecated API
elem
Github user vadeg commented on the issue:
https://github.com/apache/maven-plugin-testing/pull/4
Hello!
Are there any updates?
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional com
Hi,
I'd like to prepare an alpha release of the Maven JDeprScan Plugin
It is a wrapper around the jdeprscan tool[1], available since Java 9.
You use the jdeprscan tool as a static analysis tool that scans a jar
file (or some other aggregation of class files) for uses of deprecated API
elem
INFRA issue created
https://issues.apache.org/jira/browse/INFRA-15396
Regards,
Hervé
Le samedi 21 octobre 2017, 12:22:47 CEST Hervé BOUTEMY a écrit :
> Currently, comments are sent to dev@maven.a.o
>
> For our classical official Jira issue tracker, notifications are sent to
> issues@maven.a.o
>
Fixed in Jira
On Sat, 28 Oct 2017 10:51:30 +0200, Andreas Dangel
wrote:
Thanks! Then it will be 3.9.0 :)
Am 28.10.2017 um 10:35 schrieb Robert Scholte:
I would say no. Just keep it on 3(but do switch to 3 segments, i.e
3.9.0). Maven-site-plugin and maven-compiler-plugin suffered with the
Thanks! Then it will be 3.9.0 :)
Am 28.10.2017 um 10:35 schrieb Robert Scholte:
> I would say no. Just keep it on 3(but do switch to 3 segments, i.e
> 3.9.0). Maven-site-plugin and maven-compiler-plugin suffered with the
> same issue, they were already on 3.x before they were Maven3-only.
>
> IIR
I would say no. Just keep it on 3(but do switch to 3 segments, i.e 3.9.0).
Maven-site-plugin and maven-compiler-plugin suffered with the same issue,
they were already on 3.x before they were Maven3-only.
IIRC there's a small list with plugins which couldn't follow this new
convention.
Rob
Hi,
I'm working on MPMD-240 [1] and the current trunk version of the plugin
is 3.9-SNAPSHOT.
Shall I move its version to 4.0.0-SNAPSHOT? Other plugins where at 2.x
before the maven 3 upgrade and moved to 3.0.0-SNAPSHOT afterwards.
Is the matching major version of the plugin and maven version jus
Hello Benedikt,
I will have a look this weekend.
On Sat, Oct 28, 2017 at 9:11 AM, Benedikt Ritter wrote:
> Hello Tibor,
>
> did you have some time to do the rebase and help me get the build to work
> in the junit5 branch?
>
> Regards,
> Benedikt
>
> > Am 18.10.2017 um 09:13 schrieb Benedikt Rit
Nice! Another plugin which doesn't depend on maven-compat anymore
On Sat, 28 Oct 2017 10:22:19 +0200, wrote:
Author: adangel
Date: Sat Oct 28 08:22:19 2017
New Revision: 1813594
URL: http://svn.apache.org/viewvc?rev=1813594&view=rev
Log:
[MPMD-240] Migrate plugin to Maven 3.0
maven-compat no
Hello Tibor,
did you have some time to do the rebase and help me get the build to work in
the junit5 branch?
Regards,
Benedikt
> Am 18.10.2017 um 09:13 schrieb Benedikt Ritter :
>
> Hello Tibor,
>
> Sorry for the daily I somehow missed this mail.
>
>> Am 15.10.2017 um 13:07 schrieb Tibor Dig
11 matches
Mail list logo