Am 09/03/16 um 11:48 schrieb Robert Scholte:
> Simple? We have several options. Most user friendly might be to have the
> "magic" in the maven-compiler-plugin, which implies you need to be able to
> set the javac executable for both, set the source/target/release for both.
> And how about
On Sat, 03 Sep 2016 03:57:30 +0200, Christian Schulte
wrote:
Am 09/02/16 um 19:06 schrieb Robert Scholte:
I'll rephrase the question: What to do which projects who want to have
their code compatible with a version lower than Java 9 AND want to
provide
a module-info file
Am 09/02/16 um 19:06 schrieb Robert Scholte:
> I'll rephrase the question: What to do which projects who want to have
> their code compatible with a version lower than Java 9 AND want to provide
> a module-info file as well?
The main sources are compiled with, for example, -target 1.6 and
On Fri, 02 Sep 2016 15:49:36 +0200, Tibor Digana
wrote:
Robert, I disagree with you. There is no reason to increase effort only
because of one class.
Now let's be concrete. I see many managers in commercial firms behave
like
non-dev managers, and it is
267 984 3651
>
>
>
>
> -- Original Message --
> From: "Andreas Gudian" <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5879624=0>>
> To: "Maven Developers List" <[hidden email]
> <http:///user/SendEmail.jtp?type=node=
Robert, I disagree with you. There is no reason to increase effort only
because of one class.
Now let's be concrete. I see many managers in commercial firms behave like
non-dev managers, and it is horrible in almost every area because now in
Europe the political decisions become more important
-- Original Message --
From: "Andreas Gudian" <andreas.gud...@gmail.com>
To: "Maven Developers List" <dev@maven.apache.org>
Sent: 8/31/2016 4:52:16 PM
Subject: Re: Building jar targeting multiple Java versions, including 9
2016-08-31 22:02 GMT+02:00 Tibor Digana <t
On Wed, 31 Aug 2016 22:02:04 +0200, Tibor Digana
wrote:
So, we can try to have different source folders for different runtimes.
No. If you are developers you would not say this.
No developer would develop and merge the same code multiple times!!!
Look, now let
2016-08-31 22:02 GMT+02:00 Tibor Digana :
> >>So, we can try to have different source folders for different runtimes.
> No. If you are developers you would not say this.
> No developer would develop and merge the same code multiple times!!!
> Look, now let the
>>So, we can try to have different source folders for different runtimes.
No. If you are developers you would not say this.
No developer would develop and merge the same code multiple times!!!
Look, now let the maven-compiler-plugin to download jars of the same
artifact which was released for
lt;dev@maven.apache.org>; "Richard Sand"
<rs...@idfconnect.com>
Sent: 8/31/2016 11:50:26 AM
Subject: Re: Building jar targeting multiple Java versions, including 9
Richard, I share your sentiment. I've given this subject some thought
and
I've come to the conclusion that a f
t;ZML-Apache-Maven-Developers" <dev@maven.apache.org>
> Sent: 8/31/2016 11:10:33 AM
> Subject: Re: Building jar targeting multiple Java versions, including 9
>
> To be clear, I was purely addressing the concern of a Multi-Release JAR.
>>
>> Cheers,
>> Pau
ert Scholte" <rfscho...@apache.org>
To: "ZML-Apache-Maven-Developers" <dev@maven.apache.org>; "Paul
Benedict"
<pbened...@apache.org>
Sent: 8/31/2016 10:39:52 AM
Subject: Re: Building jar targeting multiple Java versions, including
9
Hi Paul,
t; <rfscho...@apache.org>
> To: "ZML-Apache-Maven-Developers" <dev@maven.apache.org>; "Paul Benedict"
> <pbened...@apache.org>
> Sent: 8/31/2016 10:39:52 AM
> Subject: Re: Building jar targeting multiple Java versions, including 9
>
> Hi
al Message --
From: "Robert Scholte" <rfscho...@apache.org>
To: "ZML-Apache-Maven-Developers" <dev@maven.apache.org>; "Paul
Benedict" <pbened...@apache.org>
Sent: 8/31/2016 10:39:52 AM
Subject: Re: Building jar targeting multiple Java versions, in
Hi Paul,
no problem to move it to this thread. It is indeed about "The Maven Way",
although we may need to start from the beginning, explaining the issue
we're facing.
Let's use ASM as an example, their 6.0_ALPHA has been built like this,
although without Maven.
ASM is an all purpose
Robert, I'm responding to dev@maven so we can discuss Maven philosophies...
I believe the pattern should be based on a multi-module project. Each
module should target the expected JDK version. Then introduce a new "mrjar"
type for the parent that knows how to bind them all together into a
17 matches
Mail list logo