Re: Accessing .properties file

common, just entering it into google gives you the right page at the top.. no, you don't need to configure anything, if you just add your properties file into the src/main/resources (sub)directory, it will be included into the resulting jar file. Milos On Mon, Apr 2, 2012 at 7:31 AM,

Re: Different behavior when building a project as a module or stand-alone

Thanks for your answer, Wayne. I'll refrain from using Nabble's formatting options from now on. Here are the informations from my first message, in plain text this time. === === === My project has a basic multi-module structure, like this : project |_project-core |_project-web

eclipse plugin for maven using jdk 1.3

Hello guys, I installed a maven plugin in eclipse when i ran my pavne project and tried to build it there it used jdk 1.3 to build and compile. here is the verbose out put sections related to this: / [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ CorpWeb --- [DEBUG] Created

Re: Ear Plugin skinnyWars EJB problem

I tried this approach, /plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.2/version configuration

Re: eclipse plugin for maven using jdk 1.3

Hi, I checked if the JRE in the Run AS configuration was 1.3 but it was not. Why is the maven plugin using 1.3 is beyond my understanding. http://maven.apache.org/general.html#Compiling-J2SE-5 HTH Thorsten

RE: Avoiding duplicate POM code: profiles, inheritance, properties

Hello Wayne, Seems my first post was really not clear. Trying to make it simpler: Basically, my main concern is to be able to package separately parts of the POM: - plugin configuration and/or dependencies (previously the type POM) - distribution management information (previously the deployment

Re: Avoiding duplicate POM code: profiles, inheritance, properties

It sounds like you are describing the usage of a parent POM. A parent is a project specific POM that ideally carries your plug-in versions, deployment information and code versions for all of the POMs in the maven projects that makes up your application. Some of this is properties and some is

Re: Different behavior when building a project as a module or stand-alone

between the two builds. It happens during the execution of dependency:purge-local-repository. As you can see in the build pastebins I have a lot of projects that are built with Maven, and not a single one uses purge-local-repo. Why are you using it? below, there's only one library affected

Re: Avoiding duplicate POM code: profiles, inheritance, properties

Hi Gillet, Basically, my main concern is to be able to package separately parts of the POM: - plugin configuration and/or dependencies (previously the type POM) - distribution management information (previously the deployment POM) To me, it sounds like you are asking for multiple

Using artifacts as resources in other projects.

Hello Maven users, I am really newbie in Maven, so I am not pretty sure if my way of thinking is right. If it's not, do not hesitate to criticize it. I am developing medium-size project, which contains both Java SE and Android sub-projects. After many troubles with Ant, I've decided to give

Re: Avoiding duplicate POM code: profiles, inheritance, properties

On Mon, Apr 2, 2012 at 7:55 AM, Gillet Thomas (2) thomas.gille...@consultant.volvo.com wrote: Seems my first post was really not clear. Trying to make it simpler: Basically, my main concern is to be able to package separately parts of the POM: - plugin configuration and/or dependencies

Re: Different behavior when building a project as a module or stand-alone

Indeed, our use case for purge-local-repository is a bit dodgy and definitely sub-optimal. Our project depends on various corporate libraries which are not Mavenized. In order to use these libraries, we frequently use deploy:deploy-file to drop them on our repository, with a fixed version (given

Re: Using artifacts as resources in other projects.

However, I would like to deliver only one file - Main.jar. Two other files - Android.apk and Swing.jar should be put as entire files inside of Main.jar (they should stay there as full files, without unpacking or anything). This way, when user decided to generate e.g. Swing application,

Re: Different behavior when building a project as a module or stand-alone

Are you using a Maven repo such as Nexus? Can you not give your corporate libraries GAV designations that are controlled so the version numbers are monotonically increasing? Ron On 02/04/2012 11:53 AM, Philippe Lagardère wrote: Indeed, our use case for purge-local-repository is a bit dodgy

configuration plugin

Hi. I am looking for a configuration plugin or (if it does not exist) some brainstorming related to the maven-way of configuration. First let me say that the configuration task is relevant for our php-maven projects where we do not have clear conventions you may know from java/jar or java/war

Re: Different behavior when building a project as a module or stand-alone

Our project depends on various corporate libraries which are not Mavenized. In order to use these libraries, we frequently use deploy:deploy-file to drop them on our repository, with a fixed version (given that new versions are duly tested and obsolete older versions). I want to be sure that

Re: Using artifacts as resources in other projects.

You should probably use the maven assembly plugin Jeff Le 2 avr. 2012 17:47, Mariusz Plucinski plucinski.mari...@gmail.com a écrit : Hello Maven users, I am really newbie in Maven, so I am not pretty sure if my way of thinking is right. If it's not, do not hesitate to criticize it. I am

Re: configuration plugin

Profiles appear to be magic but it is black magic. They should only be used by senior sorcerers who possess advanced skills and have all of the required potions of healing and invulnerability. They are inherently evil and can make your life a living hell. There are a few Maven experts who can

configuration plugin

Hi. I am looking for a configuration plugin or (if it does not exist) some brainstorming related to the maven-way of configuration. First let me say that the configuration task is relevant for our php-maven projects where we do not have clear conventions sou may know from java/jar or java/war

installing non-maven jars before compile

Hi, I'm trying to install some non-maven files before I compile my project. Here's a snippet of my pom.xml: [code] plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-install-plugin/artifactId version2.3.1/version