Maven Version 3.0.4 compatibility with Java Version

2013-10-02 Thread Raghavendra Nandagopal

Hi,
  The maven version I am using is Maven 3.0.4.  When I try to compile a 
Java project, the error that states is enums are not supported in 
-source 1.3

(use -source 5 or higher to enable enums).

  My java version is JDK 7.0 and the JAVA_HOME variable is set 
correctly and part of the build path.


  I understand that the java version has to be configured in the 
pom.xml for the project to make use of JDK 7.0.
The clarification I needed is if Maven version 3.0.4 then isn't by 
default uses JDK 5.0 and above?
I don't need to change the value for each and every pom.xml for the 
projects that I work.

Please let me know if you have any workaround.

Thanks,
Raghavendra Nandagopal


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



Re: Maven Version 3.0.4 compatibility with Java Version

2013-10-02 Thread Anders Hammar
This is controlled by the maven-compiler-plugin. The version of that plugin
that Maven 3.0.4 uses by default uses Java 5 by default. So you must either
have an older version of the plugin defined or a configuration of that
plugin stating Java 1.3.
If you check the effective-pom it should be easy to tell.

/Anders


On Wed, Oct 2, 2013 at 5:45 AM, Raghavendra Nandagopal 
speaktorag...@gmail.com wrote:

 Hi,
   The maven version I am using is Maven 3.0.4.  When I try to compile a
 Java project, the error that states is enums are not supported in -source
 1.3
 (use -source 5 or higher to enable enums).

   My java version is JDK 7.0 and the JAVA_HOME variable is set correctly
 and part of the build path.

   I understand that the java version has to be configured in the pom.xml
 for the project to make use of JDK 7.0.
 The clarification I needed is if Maven version 3.0.4 then isn't by default
 uses JDK 5.0 and above?
 I don't need to change the value for each and every pom.xml for the
 projects that I work.
 Please let me know if you have any workaround.

 Thanks,
 Raghavendra Nandagopal


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




Re: Looking for class property-substitution plugin

2013-10-02 Thread Baptiste Mathus
Hi,
The templating-m-p as stated in the documentation was exactly designed to
filter source files. Its name might not make it that obvious but it's
because the idea is to some day support other templating engines.

In your case, you have to design your source files with variables inside
and the plugin will first filter source file then add it for compilation.

The plugin uses standard maven properties. So if that properties must come
from an external file that is another issue (properties:read-properties
approximate goal name is a way to go).

Cheers
Le 30 sept. 2013 17:30, Russell Gold r...@gold-family.us a écrit :

 Thanks; I am aware that I could just keep the processing in ant; there are
 a couple of problems with your solution, that I see:

 1) If I keep the file in the source directory, changing it wreaks havoc
 with source control - CM cannot tell if I meant to change it or not, and in
 a system such as Perforce, the file would be read-only in any event if I am
 not changing it.
 2) The ant solution makes it very hard to ensure that the file gets added
 to the list of files that maven will compile

 That's why I want a plugin that does this the maven way.

 Thanks,
 Russ

 On Sep 30, 2013, at 10:50 AM, Lyons, Roy roy.ly...@cmegroup.com wrote:

  :) I have an obligatory recommendation.  If nothing else, theres the
  antrun plugin which will allow you to do that substitution as well.  It
  allows you to run ant functions within the pom.
 
  You may be able to just keep the files in your src/main/language folder,
  and do a replace function, pointing to that src/main/language folder.
 
 
  Thanks,
 
  Roy Lyons
 
 
 
 
  On 9/30/13 9:44 AM, Russell Gold r...@gold-family.us wrote:
 
  Before I write this myselfŠ
 
  I am converting an ant build to maven. One of the steps processes a
  template file, using properties from a properties file to replace tokens
  and produce a java source file, which is then compiled. Is there an
  existing plugin which does this? The resource plugin can do the
  substitution, but will not mark the resultant file for compilation. It's
  not all that difficult to write, but one fewer plugin to maintain is a
  good thing.
 
  Thanks,
  Russ
  -
  Come read my webnovel, Take a Lemon http://www.takealemon.com,
  and listen to the Misfile radio play
  http://www.fuzzyfacetheater.com/misfile/!
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 

 -
 Come read my webnovel, Take a Lemon http://www.takealemon.com,
 and listen to the Misfile radio play 
 http://www.fuzzyfacetheater.com/misfile/!








Re: Maven Version 3.0.4 compatibility with Java Version

2013-10-02 Thread Russell Gold
You would think so, but a co-worker of mine ran into the same issue without 
putting anything in his POM. He had installed it using apt-get on ubuntu, but 
when he replaced that with 3.0.4 from the maven website, it worked fine. I 
never delved into the issue, but I wonder if apt-get is somehow finding a 
different 3.0.4?

- Russ

On Oct 2, 2013, at 2:19 AM, Anders Hammar and...@hammar.net wrote:

 This is controlled by the maven-compiler-plugin. The version of that plugin
 that Maven 3.0.4 uses by default uses Java 5 by default. So you must either
 have an older version of the plugin defined or a configuration of that
 plugin stating Java 1.3.
 If you check the effective-pom it should be easy to tell.
 
 /Anders
 
 
 On Wed, Oct 2, 2013 at 5:45 AM, Raghavendra Nandagopal 
 speaktorag...@gmail.com wrote:
 
 Hi,
  The maven version I am using is Maven 3.0.4.  When I try to compile a
 Java project, the error that states is enums are not supported in -source
 1.3
 (use -source 5 or higher to enable enums).
 
  My java version is JDK 7.0 and the JAVA_HOME variable is set correctly
 and part of the build path.
 
  I understand that the java version has to be configured in the pom.xml
 for the project to make use of JDK 7.0.
 The clarification I needed is if Maven version 3.0.4 then isn't by default
 uses JDK 5.0 and above?
 I don't need to change the value for each and every pom.xml for the
 projects that I work.
 Please let me know if you have any workaround.
 
 Thanks,
 Raghavendra Nandagopal
 
 
 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 

-
Author, Getting Started with Apache Maven

Come read my webnovel, Take a Lemon http://www.takealemon.com, 
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!








Re: Maven Version 3.0.4 compatibility with Java Version

2013-10-02 Thread Anders Hammar
I was talking about official Maven core. Any tweaked version could be
differently.
However, the effective-pom would show what is used. I.e. an older version
of the plugin or a configuration.

/Anders


On Wed, Oct 2, 2013 at 12:25 PM, Russell Gold r...@gold-family.us wrote:

 You would think so, but a co-worker of mine ran into the same issue
 without putting anything in his POM. He had installed it using apt-get on
 ubuntu, but when he replaced that with 3.0.4 from the maven website, it
 worked fine. I never delved into the issue, but I wonder if apt-get is
 somehow finding a different 3.0.4?

 - Russ

 On Oct 2, 2013, at 2:19 AM, Anders Hammar and...@hammar.net wrote:

  This is controlled by the maven-compiler-plugin. The version of that
 plugin
  that Maven 3.0.4 uses by default uses Java 5 by default. So you must
 either
  have an older version of the plugin defined or a configuration of that
  plugin stating Java 1.3.
  If you check the effective-pom it should be easy to tell.
 
  /Anders
 
 
  On Wed, Oct 2, 2013 at 5:45 AM, Raghavendra Nandagopal 
  speaktorag...@gmail.com wrote:
 
  Hi,
   The maven version I am using is Maven 3.0.4.  When I try to compile a
  Java project, the error that states is enums are not supported in
 -source
  1.3
  (use -source 5 or higher to enable enums).
 
   My java version is JDK 7.0 and the JAVA_HOME variable is set correctly
  and part of the build path.
 
   I understand that the java version has to be configured in the pom.xml
  for the project to make use of JDK 7.0.
  The clarification I needed is if Maven version 3.0.4 then isn't by
 default
  uses JDK 5.0 and above?
  I don't need to change the value for each and every pom.xml for the
  projects that I work.
  Please let me know if you have any workaround.
 
  Thanks,
  Raghavendra Nandagopal
 
 
 
 --**--**-
  To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org
 users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 

 -
 Author, Getting Started with Apache Maven

 Come read my webnovel, Take a Lemon http://www.takealemon.com,
 and listen to the Misfile radio play 
 http://www.fuzzyfacetheater.com/misfile/!









Re: dependency:tree gets wrong version?

2013-10-02 Thread James Green
Appreciate that and this provides a good way forward. While debugging the
problem we actually ended up removing a pile of dependencies included which
were no longer required shaving about 7mb from the binary so it ended up
being fruitful anyway..!


On 20 September 2013 18:04, Jörg Schaible joerg.schai...@gmx.de wrote:

 Hi James,

 James Green wrote:

  org.apache.maven.plugins:maven-dependency-plugin:2.8
 
  The only way we resolved our problem was by loading the project into
  Eclipse and viewing the graph of dependencies, then dropping each that
 had
  a transitive dependency on the older woodstox. Eventually jaxws-rt was
  dropped and the woodstox 2.4.0 was included. So we added an exclude here
  and we've been fine since.
 
  It would have been nice if the dependency plugin showed that really. We
  did upgrade the dependency from an older release but didn't see any
 change
  as a result.

 Hmm. I control my versions normally with a shared dependencyManagement
 section. No room for surprises!

 - Jörg


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




New Maven video course!

2013-10-02 Thread Russell Gold
I'd like to mention the release of my video course, Getting Started with Apache 
Maven, now available from PackT publications. It's a bit over two hours long 
and takes the viewer from installation of the tool through development of 
multi-module projects and websites. Check it out!
-
Author, Getting Started with Apache Maven

Come read my webnovel, Take a Lemon http://www.takealemon.com, 
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!








Re: Maven versions in compilation

2013-10-02 Thread Baptiste Mathus
Well, as Maven delegates some important parts like compilation to plugins
or even external tools like javac, any risk of being different is quite low.

And put differently, as what you ask is actually controlled by the
maven-ear-plugin, maven-jar-plugin, etc. and not by maven core (granted you
locked plugin versions as one should do, sure), the risk is very low that
there's anything different (without upgrading one of those plugin which may
new behaviour and/or bug.

We migrated from m2 to m3 some time ago a quite big numbers of projects
(I'd say more 30+ if talking about multimodule build, and even tens or
hundreds if you speak of projects/modules), and we didn't encounter
importantly noticeable differences.

Cheers
Le 1 oct. 2013 21:31, John Dix john@amdocs.com a écrit :

 I have a question in order to make our dev managers warm and fuzzy.

 My understanding is that a pom that compiles under 2.1.0 and 3.0.5
 produces the same jars. I know this to be true so long as either version of
 Maven is pulling down the correct versions of SDK's used to build the java
 files but I need some kind of official stamp on that to ease nervousness.

 Thanks!

 John Caolan Dix
 Programming Sr. SME, Digital Commerce
 Amdocs Digital Services Division
 o: 206-288-0334 m: 425.351.7340

 AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS

 Did you know...?
 Amdocs Mobile Payments enables operators to manage any number of app
 stores, merchants and aggregators and generate revenues from digital
 content and mobile commerce

 Follow Amdocs on Facebookhttp://www.facebook.com/amdocsinc/, Twitter
 http://twitter.com/AmdocsInc, LinkedIn
 http://www.linkedin.com/company/amdocs, YouTube
 http://www.youtube.com/amdocsinc and Google+
 https://plus.google.com/105657940751678445194 - and read the latest on
 the Amdocs blog networkhttp://blogs.amdocs.com/.



 This message and the information contained herein is proprietary and
 confidential and subject to the Amdocs policy statement,
 you may review at http://www.amdocs.com/email_disclaimer.asp



RE: Maven versions in compilation

2013-10-02 Thread John Dix
Thank you Baptiste and Gordon! I'll work something up for a comparison in jars 
and go from there.

-Original Message-
From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste Mathus
Sent: Wednesday, October 02, 2013 4:01 AM
To: Maven Users List
Subject: Re: Maven versions in compilation

Well, as Maven delegates some important parts like compilation to plugins or 
even external tools like javac, any risk of being different is quite low.

And put differently, as what you ask is actually controlled by the 
maven-ear-plugin, maven-jar-plugin, etc. and not by maven core (granted you 
locked plugin versions as one should do, sure), the risk is very low that 
there's anything different (without upgrading one of those plugin which may new 
behaviour and/or bug.

We migrated from m2 to m3 some time ago a quite big numbers of projects (I'd 
say more 30+ if talking about multimodule build, and even tens or hundreds if 
you speak of projects/modules), and we didn't encounter importantly noticeable 
differences.

Cheers
Le 1 oct. 2013 21:31, John Dix john@amdocs.com a écrit :

 I have a question in order to make our dev managers warm and fuzzy.

 My understanding is that a pom that compiles under 2.1.0 and 3.0.5 
 produces the same jars. I know this to be true so long as either 
 version of Maven is pulling down the correct versions of SDK's used to 
 build the java files but I need some kind of official stamp on that to ease 
 nervousness.

 Thanks!

 John Caolan Dix
 Programming Sr. SME, Digital Commerce
 Amdocs Digital Services Division
 o: 206-288-0334 m: 425.351.7340

 AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS

 Did you know...?
 Amdocs Mobile Payments enables operators to manage any number of app 
 stores, merchants and aggregators and generate revenues from digital 
 content and mobile commerce

 Follow Amdocs on Facebookhttp://www.facebook.com/amdocsinc/, 
 Twitter http://twitter.com/AmdocsInc, LinkedIn 
 http://www.linkedin.com/company/amdocs, YouTube 
 http://www.youtube.com/amdocsinc and Google+ 
 https://plus.google.com/105657940751678445194 - and read the latest 
 on the Amdocs blog networkhttp://blogs.amdocs.com/.



 This message and the information contained herein is proprietary and 
 confidential and subject to the Amdocs policy statement, you may 
 review at http://www.amdocs.com/email_disclaimer.asp


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp


RE: New Maven video course!

2013-10-02 Thread John Dix
Link?

-Original Message-
From: Russell Gold [mailto:r...@gold-family.us]
Sent: Wednesday, October 02, 2013 3:36 AM
To: Maven Users List
Subject: New Maven video course!

I'd like to mention the release of my video course, Getting Started with Apache 
Maven, now available from PackT publications. It's a bit over two hours long 
and takes the viewer from installation of the tool through development of 
multi-module projects and websites. Check it out!
-
Author, Getting Started with Apache Maven

Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to 
the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!







This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp

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



Re: New Maven video course!

2013-10-02 Thread Stevo Slavić
http://www.packtpub.com/getting-started-with-apache-maven/video


On Wed, Oct 2, 2013 at 10:53 PM, John Dix john@amdocs.com wrote:

 Link?

 -Original Message-
 From: Russell Gold [mailto:r...@gold-family.us]
 Sent: Wednesday, October 02, 2013 3:36 AM
 To: Maven Users List
 Subject: New Maven video course!

 I'd like to mention the release of my video course, Getting Started with
 Apache Maven, now available from PackT publications. It's a bit over two
 hours long and takes the viewer from installation of the tool through
 development of multi-module projects and websites. Check it out!
 -
 Author, Getting Started with Apache Maven

 Come read my webnovel, Take a Lemon http://www.takealemon.com, and
 listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/
 !







 This message and the information contained herein is proprietary and
 confidential and subject to the Amdocs policy statement,
 you may review at http://www.amdocs.com/email_disclaimer.asp

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




Re: New Maven video course!

2013-10-02 Thread Jose Manuel Garcia Maciel/Mexico/IBM
is it this one?

http://www.packtpub.com/getting-started-with-apache-maven/video

Manuel Garcia,
regards

m2e workspace resolution doesn't include test-classes

2013-10-02 Thread Peter Kahn
Hi all,

Does anyone have a workaround for m2e no longer adding target/test-classes
to launcher when workspace resolution is used?  This used to work but
doesn't anymore which forces us to add folders and projects to launchers
manually.

After closing  dependent projects in workspace I see the test jars on my
classpath.  It is only when they are opened that resolution fails.  I saw a
discussion back in may on this  topic (
http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg01343.html) and was hoping
someone had a workaround.

Thanks

Peter

Apologies is m2e is too off topic for this list.
-- 
Peter Kahn
citizenk...@gmail.com
http://www.google.com/profiles/citizenkahn
Awareness - Intention - Action


RE: New Maven video course!

2013-10-02 Thread Martin Gainty
Buenas Manuel-

Yo soy incapaz de conseguir las fichas (las ventanas pequenas) para trabajar
¿funciona para ti?

Martín 
__ 
Porfavor...no altere ni interrumpir esta communicacion..Gracias


 Subject: Re: New Maven video course!
 To: users@maven.apache.org
 From: jos...@mx1.ibm.com
 Date: Wed, 2 Oct 2013 16:55:15 -0500
 
 is it this one?
 
 http://www.packtpub.com/getting-started-with-apache-maven/video
 
 Manuel Garcia,
 regards
  

Re: New Maven video course!

2013-10-02 Thread Russell Gold
Yes, that's the one.

On Oct 2, 2013, at 5:55 PM, Jose Manuel Garcia Maciel/Mexico/IBM 
jos...@mx1.ibm.com wrote:

 is it this one?
 
 http://www.packtpub.com/getting-started-with-apache-maven/video
 
 Manuel Garcia,
 regards

-
Author, Getting Started with Apache Maven 
http://www.packtpub.com/getting-started-with-apache-maven/video

Come read my webnovel, Take a Lemon http://www.takealemon.com, 
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!