Re: Excluding -beta-N from a range

2017-01-13 Thread Dan Tran 
+1 to fix it at maven-core

-D

On Fri, Jan 13, 2017 at 7:37 AM, Benson Margulies 
wrote:

> On Thu, Jan 12, 2017 at 11:42 PM, Florian Schätz 
> wrote:
> > Am Donnerstag, den 12.01.2017, 14:22 -0800 schrieb Benson Margulies:
> >
> >> I agree with them that this is counter-intuitive. The whole point of
> >> -beta-1 is to introduce new, incompatible, stuff. The whole point of
> >> that range is to exclude it.
> >
> > Doesn't 2.0.0-beta1 imply that it's a beta for the 2.0.0 release, so
> > that the final 2.0.0 release will include everything that's in this
> > beta, thus the range quite correctly contains it...?
>
>
> The range [1,2) excludes 2.0.0. So, by your logic, which is my logic,
> it should also exclude the beta.
> >
> > If the stuff from the 2.0.0-beta1 will not be part of the final 2.0.0
> > release, wouldn't it be better called 2.0.1-beta1?
> >
> > Just curious because we had some discussions about versioning strategies
> > here, too, a while ago.
> >
> > Regards,
> >
> > Flo
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Mark Prins 
Op 13 jan. 2017 18:15 schreef "John Patrick" :

If you only have Java 8 installed, would that work? Or does target
still default to something older?


The default value for the compiler plugin is 1.5 even when using java 8
runtime.
You may want to look into toolchains as well.

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Chris Barlock 
Maybe...Depends on what you mean by "a module of that parent."  If you 
mean


  ...
  ...


then I think not.  I think it means that every POM that wants to use the 
same common stuff would include something like:


my.groupId
build.master
1.0.0.0-SNAPSHOT
../build.master


Chris




From:   Dean Schulze 
To: Maven Users List 
Date:   01/13/2017 01:14 PM
Subject:Re: Is there a way to make mvn default to Java 8?



That means making every new project a module of that parent.  Ugh.

On Fri, Jan 13, 2017 at 9:54 AM, Bernd Eckenfels 
wrote:

> Sorry when this answer is an over-simplification, but you can just
> configure it in a common parent. This is a quite typical case why you 
want
> shared company/team/product/buildenv parents.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Fri, Jan 13, 2017 at 5:51 PM +0100, "Dean Schulze" <
> dean.w.schu...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> I would like to avoid having to add
>
>
> 1.8
> 1.8
>
>
> to every pom.xml.  Is there a global setting I can set in mvn to make 
Java
> 8 the default so I don't have to add this to every pom.xml?
>
>
>
>
>
>

Re: Plexus component question

2017-01-13 Thread Laird Nelson 
Thanks; confirming that there's a page with a 5 minute tutorial and no
further docs.  OK, off to the source code.

On Fri, Jan 13, 2017 at 11:06 AM Robert Scholte 
wrote:

> Nowadays you need to go to https://www.eclipse.org/sisu/docs/ , that's
> where the bridge/implementation of Plexus is maintained.
>
> Robert
>
> On Fri, 13 Jan 2017 19:37:23 +0100, Laird Nelson 
> wrote:
>
> > On Fri, Jan 13, 2017 at 9:33 AM Robert Scholte 
> > wrote:
> >
> >> I haven't verified this, but it could be that Plexus-Components switches
> >> to the non-default if such an implementation is available.
> >>
> >
> > OK, so if I hear you right, merely putting a components.xml in
> > META-INF/plexus in my archetype should do it.  Or that's the idea,
> > anyway.
> > Is there definitive documentation somewhere on how to affect the Plexus
> > component model?
> >
> > Best,
> > Laird
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Plexus component question

2017-01-13 Thread Robert Scholte 
Nowadays you need to go to https://www.eclipse.org/sisu/docs/ , that's  
where the bridge/implementation of Plexus is maintained.


Robert

On Fri, 13 Jan 2017 19:37:23 +0100, Laird Nelson   
wrote:


On Fri, Jan 13, 2017 at 9:33 AM Robert Scholte   
wrote:



I haven't verified this, but it could be that Plexus-Components switches
to the non-default if such an implementation is available.



OK, so if I hear you right, merely putting a components.xml in
META-INF/plexus in my archetype should do it.  Or that's the idea,  
anyway.

Is there definitive documentation somewhere on how to affect the Plexus
component model?

Best,
Laird


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Plexus component question

2017-01-13 Thread Laird Nelson 
On Fri, Jan 13, 2017 at 9:33 AM Robert Scholte  wrote:

> I haven't verified this, but it could be that Plexus-Components switches
> to the non-default if such an implementation is available.
>

OK, so if I hear you right, merely putting a components.xml in
META-INF/plexus in my archetype should do it.  Or that's the idea, anyway.
Is there definitive documentation somewhere on how to affect the Plexus
component model?

Best,
Laird

Re: Plexus component question

2017-01-13 Thread Robert Scholte 

Hi,

I haven't verified this, but it could be that Plexus-Components switches  
to the non-default if such an implementation is available.

Otherwise the DefaultArchetypeGenerationConfigurator should be improved:

@Requirement
private Map archetypeGenerationQueryers;

and give the ArchetypeGenerationRequest the option to pass the hint of the  
ArchetypeGenerationQueryer.


thanks,
Robert

On Thu, 12 Jan 2017 23:49:12 +0100, Laird Nelson   
wrote:



Hello from (at the moment) cold Bainbridge Island, WA

!

I am writing an archetype.  I'd like to use a different
org.apache.maven.archetype.ui.generation.ArtifactGenerationQueryer
.
Is there some way, using META-INF/plexus/components.xml to cause (in my
case) the maven-artifact-plugin to use my implementation instead of the
default one?

Thanks,
Best,
Laird
--
http://about.me/lairdnelson


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Bernd Eckenfels 
It is no problem if you have installed multiple JVMs, maven only knows about 
the current java version used to start it or if you explicitly specify 
executables or toolchains. (Some POMs like Apache Commons defines profiles 
using environment variables like JAVA_1_8_HOME)
Anyway, on your system you can test it, if you do not specify source or target 
versions it will default to the start-jvm (which is not good for having stable 
and repeatable builds)
Gruss
Bernd
-- 
http://bernd.eckenfels.net




On Fri, Jan 13, 2017 at 6:15 PM +0100, "John Patrick"  
wrote:










If you only have Java 8 installed, would that work? Or does target
still default to something older? I've got Java 7, 8 and 9 on my
machine so can't easily test myself.


On 13 January 2017 at 17:04, Chris Barlock  wrote:
> Most projects I've been on have a notion of a "parent" or "common" script
> (whether Ant, Maven or just about anything else).  With Maven, you could
> define a  POM that contains all the common stuff.  Of course, you
> would have to add the parent element to all child POMs, but if you ever
> want to change something in the parent (such as this Java version), you
> would only have to do it once.
>
> Chris
>
>
>
>
> From:   Dean Schulze 
> To: users@maven.apache.org
> Date:   01/13/2017 11:51 AM
> Subject:Is there a way to make mvn default to Java 8?
>
>
>
> I would like to avoid having to add
>
> 
> 1.8
> 1.8
> 
>
> to every pom.xml.  Is there a global setting I can set in mvn to make Java
> 8 the default so I don't have to add this to every pom.xml?
>
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread John Patrick 
If you only have Java 8 installed, would that work? Or does target
still default to something older? I've got Java 7, 8 and 9 on my
machine so can't easily test myself.


On 13 January 2017 at 17:04, Chris Barlock  wrote:
> Most projects I've been on have a notion of a "parent" or "common" script
> (whether Ant, Maven or just about anything else).  With Maven, you could
> define a  POM that contains all the common stuff.  Of course, you
> would have to add the parent element to all child POMs, but if you ever
> want to change something in the parent (such as this Java version), you
> would only have to do it once.
>
> Chris
>
>
>
>
> From:   Dean Schulze 
> To: users@maven.apache.org
> Date:   01/13/2017 11:51 AM
> Subject:Is there a way to make mvn default to Java 8?
>
>
>
> I would like to avoid having to add
>
> 
> 1.8
> 1.8
> 
>
> to every pom.xml.  Is there a global setting I can set in mvn to make Java
> 8 the default so I don't have to add this to every pom.xml?
>
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Bernd Eckenfels 
No, you only need to point to an installed parent project, it does not have to 
be an aggregator.

Gruss
Bernd
-- 
http://bernd.eckenfels.net




On Fri, Jan 13, 2017 at 6:00 PM +0100, "Dean Schulze" 
 wrote:










That means making every new project a module of that parent.  Ugh.

On Fri, Jan 13, 2017 at 9:54 AM, Bernd Eckenfels 
wrote:

> Sorry when this answer is an over-simplification, but you can just
> configure it in a common parent. This is a quite typical case why you want
> shared company/team/product/buildenv parents.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Fri, Jan 13, 2017 at 5:51 PM +0100, "Dean Schulze" <
> dean.w.schu...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> I would like to avoid having to add
>
>
> 1.8
> 1.8
>
>
> to every pom.xml.  Is there a global setting I can set in mvn to make Java
> 8 the default so I don't have to add this to every pom.xml?
>
>
>
>
>
>

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Laird Nelson 
On Fri, Jan 13, 2017 at 8:51 AM Dean Schulze 
wrote:

> I would like to avoid having to add
>
> 
> 1.8
> 1.8
> 
>
> to every pom.xml.  Is there a global setting I can set in mvn to make Java
> 8 the default so I don't have to add this to every pom.xml?
>

Like others on the list, I recommend you use a common parent pom, since
these settings are part of the reproducibility of your build.  If for some
reason you're not going to do that, then I suppose you can add
-Dmaven.compiler.source=1.8 -Dmaven.compiler.target=1.8 to MAVEN_OPTS in
your ~/.mavenrc file (which does not appear to be listed here:
http://maven.apache.org/configure.html, but definitely is consulted as part
of overall Maven configuration at startup).

(Of course if I or others consume your pom.xml we have no idea what version
of Java we're supposed to use.)

Best,
Laird

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Chris Barlock 
Most projects I've been on have a notion of a "parent" or "common" script 
(whether Ant, Maven or just about anything else).  With Maven, you could 
define a  POM that contains all the common stuff.  Of course, you 
would have to add the parent element to all child POMs, but if you ever 
want to change something in the parent (such as this Java version), you 
would only have to do it once.

Chris




From:   Dean Schulze 
To: users@maven.apache.org
Date:   01/13/2017 11:51 AM
Subject:Is there a way to make mvn default to Java 8?



I would like to avoid having to add


1.8
1.8


to every pom.xml.  Is there a global setting I can set in mvn to make Java
8 the default so I don't have to add this to every pom.xml?

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Dean Schulze 
That means making every new project a module of that parent.  Ugh.

On Fri, Jan 13, 2017 at 9:54 AM, Bernd Eckenfels 
wrote:

> Sorry when this answer is an over-simplification, but you can just
> configure it in a common parent. This is a quite typical case why you want
> shared company/team/product/buildenv parents.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Fri, Jan 13, 2017 at 5:51 PM +0100, "Dean Schulze" <
> dean.w.schu...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> I would like to avoid having to add
>
>
> 1.8
> 1.8
>
>
> to every pom.xml.  Is there a global setting I can set in mvn to make Java
> 8 the default so I don't have to add this to every pom.xml?
>
>
>
>
>
>

Re: Is there a way to make mvn default to Java 8?

2017-01-13 Thread Bernd Eckenfels 
Sorry when this answer is an over-simplification, but you can just configure it 
in a common parent. This is a quite typical case why you want shared 
company/team/product/buildenv parents.

Gruss
Bernd
-- 
http://bernd.eckenfels.net




On Fri, Jan 13, 2017 at 5:51 PM +0100, "Dean Schulze" 
 wrote:










I would like to avoid having to add


1.8
1.8


to every pom.xml.  Is there a global setting I can set in mvn to make Java
8 the default so I don't have to add this to every pom.xml?

Is there a way to make mvn default to Java 8?

2017-01-13 Thread Dean Schulze 
I would like to avoid having to add


1.8
1.8


to every pom.xml.  Is there a global setting I can set in mvn to make Java
8 the default so I don't have to add this to every pom.xml?

Re: Excluding -beta-N from a range

2017-01-13 Thread Benson Margulies 
On Thu, Jan 12, 2017 at 11:42 PM, Florian Schätz  wrote:
> Am Donnerstag, den 12.01.2017, 14:22 -0800 schrieb Benson Margulies:
>
>> I agree with them that this is counter-intuitive. The whole point of
>> -beta-1 is to introduce new, incompatible, stuff. The whole point of
>> that range is to exclude it.
>
> Doesn't 2.0.0-beta1 imply that it's a beta for the 2.0.0 release, so
> that the final 2.0.0 release will include everything that's in this
> beta, thus the range quite correctly contains it...?


The range [1,2) excludes 2.0.0. So, by your logic, which is my logic,
it should also exclude the beta.
>
> If the stuff from the 2.0.0-beta1 will not be part of the final 2.0.0
> release, wouldn't it be better called 2.0.1-beta1?
>
> Just curious because we had some discussions about versioning strategies
> here, too, a while ago.
>
> Regards,
>
> Flo

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org