Re: Looking for class property-substitution plugin

2013-10-01 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 plu

Re: Maven Version 3.0.4 compatibility with Java Version

2013-10-01 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"

Maven Version 3.0.4 compatibility with Java Version

2013-10-01 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

Re: maven shade: how to actually use custom shader (plus a few ideas)

2013-10-01 Thread Stephen Connolly
Glad to have been of help! On 1 October 2013 21:14, Bear Giles wrote: > Knowing that something can be done and should be easy is half the battle! I > have no idea why the people in charge of deployments had problems figuring > out how to do this - it only took me a few hours to get everything n

Re: Maven versions in compilation

2013-10-01 Thread Gordon Cody
The first project I was switching to mvn3 I was also skeptical about the ear produced being the same. You must ensure both mvn2 and mvn3 use the same version of java (check using mvn -version) Separately explode the ear created by each version of mvn (lets call them A and B) and and all war files

Re: maven shade: how to actually use custom shader (plus a few ideas)

2013-10-01 Thread Bear Giles
Knowing that something can be done and should be easy is half the battle! I have no idea why the people in charge of deployments had problems figuring out how to do this - it only took me a few hours to get everything nailed down. Bear On Tue, Oct 1, 2013 at 7:04 AM, Bear Giles wrote: > >> The

Maven versions in compilation

2013-10-01 Thread John Dix
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

Re: maven install plugin version 2.5 installAtEnd question

2013-10-01 Thread Tonio Caputo
Hi, Continuing with this issue, I'll describe one more unexpected behaviour I'm facing in my project. Just to describe the project, its a kind of plugin-project that has an implementation that should be hidden from the developer that uses the plugin, so my project contains these poms - main pom

Re: maven shade: how to actually use custom shader (plus a few ideas)

2013-10-01 Thread Bear Giles
>> The specific motivation for the jar-of-jars is that we need to collect >> dependencies for third-party vulnerability assessment. We've been doing it >> by hand but it's very error prone. With a trivial change to DefaultShader >> we can immediately create a jar containing all of the dependencies.

Re: maven shade: how to actually use custom shader (plus a few ideas)

2013-10-01 Thread Stephen Connolly
On 1 October 2013 02:49, Bear Giles wrote: > First the question: how do I actually use a custom shader? I've created my > own Shader implementation based on DefaultShader, set a new hint, and > modified the working pom.xml entry with > myShaderHint. > > It blows up - it can't find a class impleme