I see no one objects.
I will cut a release for jdeps as soon as possible.
for the 'scripting' plugin maybe I will need more help than usual as it is
the first release of ever.
Thanks
Enrico
Il giorno mar 28 mag 2019 alle ore 14:11 Enrico Olivelli <
eolive...@gmail.com> ha scritto:
> Hi,
> I
Hi Tony,
I answered your question at Jira.
The release Vote will start asap.
Cheers
Tibor
On Mon, Jun 10, 2019 at 8:27 PM Homer, Tony wrote:
> Tibor completed the work of removing dom4j library and reverted the change
> that moves maven-archetype to Java 8 [1].
> This change mitigates the
Tibor completed the work of removing dom4j library and reverted the change that
moves maven-archetype to Java 8 [1].
This change mitigates the vulnerability to CVE-2018-1000632 while retaining
Java 7 compatibility.
In the JIRA I asked about when this can be released and Tibor suggested that I
Trying again in plain text. Sorry for the resends. Its Monday morning and I'm
moving a bit slowly today...
https://github.com/hunterpayne/maven-unbound
Hunter
On Monday, June 10, 2019, 4:15:32 AM PDT, Enrico Olivelli
wrote:
Hi, Hunter,
I have received your email a bit corrupted.
Weird. The url you want is https://github.com/hunterpayne/maven-unboundSent
from my T-Mobile 4G LTE Device
Original message From: Enrico Olivelli
Date: 6/10/19 4:15 AM (GMT-08:00) To: Maven Developers List
Subject: Re: hocon and json formats for the Project
Object Model
Weird. The url you want is https://github.com/hunterpayne/maven-unboundSent
from my T-Mobile 4G LTE Device
Original message From: Enrico Olivelli
Date: 6/10/19 4:15 AM (GMT-08:00) To: Maven Developers List
Subject: Re: hocon and json formats for the Project
Object Model
Hey StephenC,
I was looking for Anders' answer in Eclipse issue. Important is that the
issue was isolated to https://github.com/tesla/m2eclipse-mavenarchiver and
to Maven.
Issues are everywhere, in every tool, that's the life. Maybe some did not
reach such ratings to fix them nor contributor who
On Mon, 10 Jun 2019 at 13:36, Mickael Istria wrote:
> Hi,
>
> On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > however
> > because of architectural history, Eclipse (last time I checked... some
> > years ago) had issues keeping the main and test
Hi,
On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> however
> because of architectural history, Eclipse (last time I checked... some
> years ago) had issues keeping the main and test classpaths separate
This was fixed last year, during development
Hi, Hunter,
I have received your email a bit corrupted.
Did you put some ASCII art ?
Did you add attachments ?
I find your idea interesting. thank you
Enrico
Il giorno lun 10 giu 2019 alle ore 11:33 Hunter C Payne
ha scritto:
> Hello all, I've used Maven for probably 15 years now. I think
Tibor,
If one is ranking correctness of integration with Maven of the various IDEs
then IntelliJ is not the "gold standard".
There are two *major* bugs in how IntelliJ handles Maven projects:
1. It does not allow different Java versions for test versus main trees:
Hello all, I've used Maven for probably 15 years now. I think its great and
want to thank you all for all your hard work.
I've written a quick Scala library that converts pom.xml files to/from
pom.json and pom.conf (Hocon) files. This allows for a much less verbose way
to specify pom
Please read the bug report [1], which was reference in the first reply to
this thread. It clearly explains that the problem is in the mavenarchiver
m2e connector/plugin. The simplest solution is to just update that plugin.
URL to update site is in the bug report.
[1]
13 matches
Mail list logo
