Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
I am working on implementing your recommended layout. I am experiencing some problems. 1)I keep getting this error in reference to the generic-war project: 'packaging' with value 'war' is invalid. Aggregator projects require 'pom' as packaging. I tried to changing it to pom but that doesn

Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
Ron- You interested in a couple hours of contract work. I would happily pay you to help me through this? -ryan On Thu, Mar 1, 2012 at 12:56 PM, Ron Wheeler [via Maven] < ml-node+s40175n552920...@n5.nabble.com> wrote: > On 01/03/2012 2:43 PM, offbyone wrote: > > > Ok so I sh

Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
Really struggling here and could use some help with these overlays. I seem to be missing basic concepts or maybe I am just slow, sorry if these questions are pedestrian. So I am trying to produce an overlay to add the extra configuration for each of my server deployments. I have my main projec

Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
Ok so I should create a base pom with a war configuration and then a separate pom for each site that depends on this with overlays to add the extra configuration file. I will try. If I am interpreting your comments correctly, profiles allow for a user to flaten a maven build deployment, but this i

Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
Ok, I hear you, profiles are evil. BUT I still don't understand the alternative so let me give a specific and tangible example and maybe you can explain a specific alternative. I am currently deploying my product in a tomcat/linux environment as a war file. My webapp is driven by a set of spring

Re: using build profiles for WAR plugin

2012-03-01 Thread offbyone
I appreciate the feedback, but I am struggling to follow, clearly I don't understand "the maven way". I am new to maven, based on the documentation and the specification it seems like profiles are used to create different versions of a deployment package. Why would profiles be there if not for th

Re: using build profiles for WAR plugin

2012-02-29 Thread offbyone
Thanks for the reply. Unfortunately all the documentation I have seen point to profiles for this tool. If profiles are not used to differentiate runtime configuration changes, then what are? Can you point me to some documentation? -- View this message in context: http://maven.40175.n5.nabb

Re: using build profiles for WAR plugin

2012-02-29 Thread offbyone
I am trying to understand how profiles work. I don't want to use classifiers for this as this has nothing to do with my environment which is identical but rather my deployment needs. Could someone please explain what I am missing about profiles? -- View this message in context: http://maven.4

Re: using build profiles for WAR plugin

2012-02-29 Thread offbyone
I have no interest in using JNDI. Could someone please address my question regarding profiles? -- View this message in context: http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5526140.html Sent from the Maven - Users mailing list archive at Nabble.com. ---

Re: multiple project builds

2011-05-03 Thread offbyone
I am curious about the use of "etc" in your example. What is that all about? Do you perchance know the location of any examples like this that I could look at? -- View this message in context: http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368529.html Sent from the Maven -

Re: multiple project builds

2011-05-03 Thread offbyone
Thanks for the reply. I am looking at something like this: base-utilities app-common app-client app-server With these modules the dependencies look something like this: base-utilities -> app-common -> app-client, app-server Based on this representation could I still have a flat directory structu

multiple project builds

2011-05-03 Thread offbyone
I am developing an extremely large project that has a separate build procedure for the client and the server. Currently, the project is one large project. I am currently using Ant, but would like to embrace maven. I understand that the "maven way" is to have a separate project per build, but I a