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 only
On Friday 2 September 2016, Tibor Digana
wrote:
> @Stephen
> I know that you don't want to have too big change and maven1->maven2 but
> one way or another XML is strictly defined by XSD.
> We must accept that fact to accept a format with more freedom and therefore
> I would prefer code/interface
@Stephen
I know that you don't want to have too big change and maven1->maven2 but
one way or another XML is strictly defined by XSD.
We must accept that fact to accept a format with more freedom and therefore
I would prefer code/interface instead of XML like Groovy script :
*dependencies: ["com.exa
On Friday 2 September 2016, Robert Scholte wrote:
> On Wed, 31 Aug 2016 22:51:20 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> On Wednesday 31 August 2016, Robert Scholte wrote:
>>
>> On Wed, 31 Aug 2016 19:35:02 +0200, Stephen Connolly <
>>> stephen.alan.conno...@gmail
On Wed, 31 Aug 2016 22:51:20 +0200, Stephen Connolly
wrote:
On Wednesday 31 August 2016, Robert Scholte wrote:
On Wed, 31 Aug 2016 19:35:02 +0200, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
On Wednesday 31 August 2016, Christian Schulte wrote:
Am 08/31/16 um 18:39 schri
On Friday 2 September 2016, Tibor Digana
wrote:
> @Stephen
> IIUC the 3rd part artifact is a platform (architecture) specific dependency
> for another project. Thus the 3rd party artifact can be a tree of
> dependencies for my project.
> In my imagination some mapping between _architecture_ 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 horrible in almost every area because
@Stephen
IIUC the 3rd part artifact is a platform (architecture) specific dependency
for another project. Thus the 3rd party artifact can be a tree of
dependencies for my project.
In my imagination some mapping between _architecture_ and _dependency_tree_.
>>we need to move Maven forward
RESTful M
Richart,
>>couple features of Java8 which I've avoided adding because of needing
backward compatibility.
If I have to decide where my time goes, then I would rather keep Java 6 in
source code and make s/w more stable improving architecture and features;
rather than Java 7 or 8 or 9 or 10 since I k
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 than
10 matches
Mail list logo
