Hi Malte,
> Btw, tried to have a look at the namespace declaration at
> http://maven.apache.org/POM/4.0.0- this URL is specified in basically
> any of any POM I have seen thus far. Turns out
> that page does not exist. What's up with that?
Funny thing about XML namespaces... they don't actually
Hi,
I thought the version is defined in
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/default-bindings.xml;h=09ecba441e61d4a997b01af0171815c558548537;hb=maven-3.0.4
(replace hb with the version of your choice :-)).
Hmm, I guess you
On Wed, Nov 27, 2013 at 6:49 AM, Mirko Friedenhagen wrote:
> the only pity with using properties is that they are not namespaced most of
> the time (the maven.compiler.* ones being an exception here), "output" is
> claimed at least by three mojos IIRC. And skipTests is almost a general one
> but
The best part of convention over configuration: when convention doesn't work
you get to go on these fun easter egg hunts for where the configuration belongs.
- Original Message - Subject: Re: Changing JDK version without
specifying maven-compiler-plugin version
From: &qu
ahh yes they got moved there...
On 27 November 2013 20:52, Mirko Friedenhagen wrote:
> Hello,
>
> I thought the version is defined in
>
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/default-bindings.xml;h=09ecba441e61d4a997b01af01718
Hello,
I thought the version is defined in
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/default-bindings.xml;h=09ecba441e61d4a997b01af0171815c558548537;hb=maven-3.0.4
(replace hb with the version of your choice :-)).
Regards Mirko
--
ht
On 27 November 2013 10:18, Malte Skoruppa wrote:
> Hi all,
>
> thank you for your helpful answers. I grasped a lot about how Maven
> internally works and learned some tricks (e.g., dependency:analyze). This
> is a great mailing list indeed.
>
> @Laird: that is quite interesting. From all the other
Hi all,
thank you for your helpful answers. I grasped a lot about how Maven
internally works and learned some tricks (e.g., dependency:analyze).
This is a great mailing list indeed.
@Laird: that is quite interesting. From all the other posts I really
gained the impression that my original qu
Hello Laird,
the only pity with using properties is that they are not namespaced most of
the time (the maven.compiler.* ones being an exception here), "output" is
claimed at least by three mojos IIRC. And skipTests is almost a general one
but you may not easily specify that you do not want to run
On Tuesday, November 26, 2013, Malte Skoruppa wrote:
>
> is there some way for me to achieve the following three things at the same
> time:
> (1) have Maven compile my source files with -source 1.4 (or anything
> higher than 1.3)
> (2) *not* specify the maven-compiler-plugin version to use; instead
appreciate a change ;)
FWIW,
Randal Kamradt
- Original Message ----- Subject: Changing JDK
version without specifying maven-compiler-plugin version
From: "Malte Skoruppa"
Date: 11/26/13 7:59 am
To: users@maven.apache.org
Hi,
I'm new to Maven and I'm currently goin
On Tue, Nov 26, 2013 at 05:05:40PM +0100, Malte Skoruppa wrote:
[snip]
> I am not so intent on having the 'latest-and-greatest' plugin as you
> might think. It's more that I would like to stick to the default
> configuration unless I have good reason not to do so. It's really just
> that I find
favor precision over simplicity
when the two come into conflict (unless your boss dictates that you keep it
simple because 'we need to deliver tomorrow')
--------- Original Message - Subject: Re: Changing JDK version without
specifying maven-compiler-plugin version
From: "M
Hi,
I read that as you wanting to only use features of Java 1.3 (madness I say)
which will break once you have Java 8 as its javac will only support down
to -source 1.6 IIRC (but it may be 1.5)
I think it is current and two back that is the new policy that is being
introduced from Java 8 onward
On 26 November 2013 15:59, Malte Skoruppa wrote:
> Hi,
>
> thanks for your quick answer.
>
>
>
>
>> Generally, I don't want to do that. On the one hand, I would like for
>>> Maven to simply use the latest version of the maven-compiler-plugin that
>>> is
>>> available (the default behaviour).
>>>
at version.
Remember, Infants are the only people that appreciate a change ;)
FWIW,
Randal Kamradt
- Original Message ----- Subject: Changing JDK version without specifying maven-compiler-plugin version
From: "Malte Skoruppa"
Date: 11/26/13 7:59 am
To: us
Hi,
thanks for your quick answer.
Generally, I don't want to do that. On the one hand, I would like for
Maven to simply use the latest version of the maven-compiler-plugin that is
available (the default behaviour).
Not the default behaviour any more at least since 2.0.9 IIRC... the
"cor
he
version, and then all child poms will work with that version.
Remember, Infants are the only people that appreciate a change ;)
FWIW,
Randal Kamradt
- Original Message --------- Subject: Changing JDK version without
specifying maven-compiler-plugin version
From: "Malte
On 26 November 2013 14:59, Malte Skoruppa wrote:
> Hi,
>
> I'm new to Maven and I'm currently going through the "Getting Started"
> guide.
>
> While reading, the following question came to me.
> As far as I understand, Maven defaults to compiling all Java source files
> with compatibility for JDK
Hi,
I'm new to Maven and I'm currently going through the "Getting Started"
guide.
While reading, the following question came to me.
As far as I understand, Maven defaults to compiling all Java source
files with compatibility for JDK 1.3 (i.e., -source 1.3).
The guide explains how to change th
20 matches
Mail list logo
