Hi Marco,
I have 2 thoughts reading your post:
1. Should be enforced by an extension (sonatype plugin if target is
central?)
2. It likely misses a few phases compared to maven release plugin which
validates the release can be done (including tests) and runs the tests on
the tag as well
Now if 20
Hello Maven Dev & Community
Sine a long time I thought, it would be cool to have a well defined process to
prepare a release of an artifact and deploy it on mvn central. Now I got a bit
time to formulate a short proposal of my idea. I published a description of my
thought on my bolg:
https://enre
Le jeu. 3 oct. 2019 à 21:23, Tibor Digana a écrit :
> >> any previous jdk is not maintained
>
> Romain I was not talking about yes/no J8.
> I was talking about J8 sources.
> Not about dead J7 and Oracle support of J7.
>
> Not sure if the Maven devs would be able to use J8. Important is "how".
> T
>> any previous jdk is not maintained
Romain I was not talking about yes/no J8.
I was talking about J8 sources.
Not about dead J7 and Oracle support of J7.
Not sure if the Maven devs would be able to use J8. Important is "how".
Therefore the Wiki should help them "how".
>> We can still get fixe
Le jeu. 3 oct. 2019 à 20:22, Tibor Digana a écrit :
> The topic related to TLS is only related to runtime, means JDK, which is
> under the control of the particular user or CI.
> I guess the user can easily find the answer:
>
> https://stackoverflow.com/questions/50824789/why-am-i-getting-receive
The topic related to TLS is only related to runtime, means JDK, which is
under the control of the particular user or CI.
I guess the user can easily find the answer:
https://stackoverflow.com/questions/50824789/why-am-i-getting-received-fatal-alert-protocol-version-or-peer-not-authentic
The thing
On Thu, 3 Oct 2019 at 16:49, Karl Heinz Marbaise wrote:
> Hi,
>
> On 03.10.19 17:03, Tibor Digana wrote:
> > This is not very serious discussion since we saw users on our mailing
> > list who said that he is using Java 1.6 compiler and JDK7 in Maven.
>
> Would that change anything? Using JDK 8 fo
Hi,
On 03.10.19 17:03, Tibor Digana wrote:
This is not very serious discussion since we saw users on our mailing
list who said that he is using Java 1.6 compiler and JDK7 in Maven.
Would that change anything? Using JDK 8 for Maven and using JDK 6 for
compiling/test...
Serious discussion wou
Le 03/10/2019 à 16:54, Karl Heinz Marbaise a écrit :
> Hm.. first Java 7 is out for eight years now (2011) (End of live) and
> has no public updates for security/bug fixes etc. since 2015
RedHat still maintains OpenJDK 7 until June 2020 [1].
Emmanuel Bourg
[1]
https://access.redhat.com/article
Java 8 as a min is fine by me FWIW.
Gary
On Thu, Oct 3, 2019 at 11:07 AM Tibor Digana wrote:
> Sorry my important typo " I would have a problem with Java 1.8 ".
> Correction " I would NOT have a problem with Java 1.8 "
>
> On Thu, Oct 3, 2019 at 5:03 PM Tibor Digana
> wrote:
>
> > This is not
Sorry my important typo " I would have a problem with Java 1.8 ".
Correction " I would NOT have a problem with Java 1.8 "
On Thu, Oct 3, 2019 at 5:03 PM Tibor Digana wrote:
> This is not very serious discussion since we saw users on our mailing list
> who said that he is using Java 1.6 compiler
Hi,
first thanks...
I have several question regarding your blog post ...
Apart from beeing not accurate in some part I miss one very important thing:
What is the real problem when doing a release via release plugin etc.
which works well (I haven't said that it could be improved)...
I want to
This is not very serious discussion since we saw users on our mailing list
who said that he is using Java 1.6 compiler and JDK7 in Maven.
Serious discussion would uncover pros/cons and impact analysis.
I would have a problem with Java 1.8 in target and source code but I have
problem that we exclud
Hi,
On 03.10.19 14:36, Elliotte Rusty Harold wrote:
Theoretically that would work. In practice though, every project I've
seen convert to Java 8 rapidly starts adding lambdas that make the
code more obfuscated for no good reason and soon introduces hard
dependencies on Java 8, intentionally or o
On 03.10.19 14:15, Elliotte Rusty Harold wrote:
Strong -1 on Java 8 as the minimum version. Google Cloud Platform has
lots of products and customers that still require Java 7. If Maven
requires Java 8, we'd have to stick to the latest of whichever release
does support Java 7 for at least a year a
Who codes for 18 months before discovering that qa/prod are not compatible,
anymore? Especially if Google ship a use-this-Pom starter.
On Thu, Oct 3, 2019 at 1:44 PM Elliotte Rusty Harold
wrote:
> Theoretically that would work. In practice though, every project I've
> seen convert to Java 8 rapi
Theoretically that would work. In practice though, every project I've
seen convert to Java 8 rapidly starts adding lambdas that make the
code more obfuscated for no good reason and soon introduces hard
dependencies on Java 8, intentionally or otherwise. At a bare minimum,
a CI environment that runs
Would jdk 8 for maven itself and a target of 7 for the compiler (etc) for
maven-using projects be ok?
On Thu, Oct 3, 2019 at 1:15 PM Elliotte Rusty Harold
wrote:
> Strong -1 on Java 8 as the minimum version. Google Cloud Platform has
> lots of products and customers that still require Java 7. If
Strong -1 on Java 8 as the minimum version. Google Cloud Platform has
lots of products and customers that still require Java 7. If Maven
requires Java 8, we'd have to stick to the latest of whichever release
does support Java 7 for at least a year and I'm guessing longer.
On Sat, Sep 28, 2019 at 8
19 matches
Mail list logo
