I am happy to contribute in the forum and I have some blog items at
blog.artifact-software.com/tech that might help but you would be much
better served by Wayne or Stephen as they are true experts.
At http://maven.apache.org/team-list.html you get a list of the team
members who work on Maven and they are both in the list.
In our use of Spring, we used JNDI to separate deployment from
development and used the Jetspeed portal framework which separated the
look and feel customization from our code which gave us a different
problem in generating our WAR files.
We broke our application into about 70 projects with code that made JARs
or WARs and 10-12 JAR projects with just dependencies (Apache utilities,
Spring-MySQL-Hibernate-Tomcat, JasperReports, CXF, etc...) that we
loaded into Tomcat's shared library to get them out of the WARs. Our WAR
files only had our code in them with the Spring and JSF configuration files.
We were building for an SaaS so we had more permanent servers for
production and test so the JNDI solution worked well.
Thanks for the offer. I am pleased that we are able to help.
Ron
On 01/03/2012 7:40 PM, offbyone wrote:
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]<
[email protected]> wrote:
On 01/03/2012 2:43 PM, offbyone wrote:
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 is a bad practice and it is
better
to make your maven structure deep.
So are profiles going to be deprecated? I would think I am not alone
in
getting turned down the wrong path because most of the
documentation/howtos
I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a
documentation issue.
It is fairly common in Apache documentation for the programmers to make
a big deal about all the wonderful things that the package can do.
They are not particularly concerned about "Best Practices".
The most common usage is often left out of the documentation since it is
"dull" or not very impressive.
This sometimes means that obscure usage of features or seldom used
features are heavily documented while the main use case is not described.
New Maven users often fall into the trap that you were headed into.
A really simple "Best Practice" that most people use, is hard to find in
the documentation while an obscure "Worst Practice" is described because
it shows how clever the software developers are and how powerful the
product is.
There should be a "Best Practice" section on the Maven site describing
the best way to implement the common software development patterns.
There are not really a lot of cases to consider but every new Maven user
has to sort out their own case.
Ron
--
View this message in context:
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=5529204&i=0>
For additional commands, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=5529204&i=1>
--
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]<http://user/SendEmail.jtp?type=node&node=5529204&i=2>
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=5529204&i=3>
For additional commands, e-mail: [hidden
email]<http://user/SendEmail.jtp?type=node&node=5529204&i=4>
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5529204.html
To unsubscribe from using build profiles for WAR plugin, click
here<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5525954&code=cnlhbkBpcmlkaXVtc3VpdGUuY29tfDU1MjU5NTR8NzI4MTgyOTE0>
.
NAML<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5529755.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
