Ansgar Konermann wrote:
Am 25.07.2011 22:13, schrieb Daniel Serodio (lists):
Do you think using a classifier to differentiate artifacts built for
development and production is "hacky", is is this an appropriate
solution?
Use the same *artifacts* for all stages and allow for *config
We have two sets of (database and logging) settings, for development and
productions builds. We're using "dev" and "prod" profiles to choose the
appropriate settings for each environment.
Do you think using a classifier to differentiate artifacts built for
development and production is "hacky"
n Tue, Jun 21, 2011 at 4:23 PM, Daniel Serodio (lists)<
daniel.lis...@xxx.com.br> wrote:
I'm using the maven-tomcat-plugin to run an embedded, forked Tomcat server
which is then used by the maven-failsafe-plugin to run tests on.
I'd like to stop this embedded Tomcat after
I'm using the maven-tomcat-plugin to run an embedded, forked Tomcat
server which is then used by the maven-failsafe-plugin to run tests on.
I'd like to stop this embedded Tomcat after the tests finish, but the
tomcat:stop goal needs the "Tomcat Manager" application, which is not
included in th
That was it. Thanks a lot.
Is there somewhere in the documentation I could've found this information?
Benson Margulies wrote:
The site plugin does not go into . Put that into
On Tue, Jun 7, 2011 at 5:29 PM, Daniel Serodio (lists)
wrote:
When I run "mvn site", I get a "
When I run "mvn site", I get a "AbstractMethodError [...]
SiteRendererSink.unknown" error. As reported in SUREFIRE-714,
maven-surefire-plugin 2.8 needs maven-site-plugin 2.1 or greater; I told
Maven to use these versions of the plugins, but it's still using
maven-site-plugin 2.0-beta-7
I'm us
