Re: Should I use classifiers to differentiate between devel and production builds?
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 *configuring* the relevant properties of your application at runtime/startup time, as much as possible. A common mechanism to configure things at runtime is using JNDI parameters. I'mconsidering changing our build process. Setting up the DB using JNDI is easy enough, but how do you suggest we deal with different logging configurations, which differ not only on some values, but structure (ie log4j Loggers and Appenders with different classes, file paths and severity thresholds) ? Regards, Daniel Serodio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Should I use classifiers to differentiate between devel and production builds?
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, is is this an appropriate solution? Thanks in advance, Daniel Serodio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to stop embedded Tomcat server?
Que memória, heim? Sim, era eu mesmo! :) I didn't know about this plugin, thanks for the pointer. []'s Daniel Serodio Aldrin Leal wrote: Você era o Daniel Serodio da Altconn? btw, tenta isso: https://github.com/t7mp/t7mp -- -- Aldrin Leal,ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On 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 the tests finish, but the tomcat:stop goal needs the Tomcat Manager application, which is not included in the embedded Tomcat. How can I stop this embedded Tomcat server from within Maven? Thanks in advance, Daniel Serodio --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to stop embedded Tomcat server?
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 the embedded Tomcat. How can I stop this embedded Tomcat server from within Maven? Thanks in advance, Daniel Serodio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Why isn't Maven using the (site) plugin version I told it?
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 using Maven 2.2.1 BTW. Why isn't Maven using the plugin versions I told it to use? Thanks in advance, Daniel Serodio project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.example/groupId artifactIdbusca-web/artifactId version1.0.0-SNAPSHOT/version packagingwar/packaging nameBusca/name descriptionBusca - Frontent Web/description properties project.build.sourceEncodingISO8859-1/project.build.sourceEncoding project.reporting.outputEncodingUTF-8/project.reporting.outputEncoding /properties build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.6/source target1.6/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId /plugin /plugins /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.3/version /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.8/version configuration outputEncodingUTF-8/outputEncoding /configuration /plugin /plugins /reporting dependencies dependency groupIdorg.slf4j/groupId artifactIdslf4j-api/artifactId version1.6.1/version /dependency dependency groupIdorg.slf4j/groupId artifactIdslf4j-log4j12/artifactId version1.6.1/version /dependency dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId version2.6/version /dependency dependency groupIdmysql/groupId artifactIdmysql-connector-java/artifactId version5.1.6/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.8.1/version scopetest/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.5/version scopeprovided/scope /dependency /dependencies /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why isn't Maven using the (site) plugin version I told it?
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 intoreporting/ . Put that into pluginManagementplugins//pluginManagement On Tue, Jun 7, 2011 at 5:29 PM, Daniel Serodio (lists) daniel.lis...@xxx.com.br wrote: 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 using Maven 2.2.1 BTW. Why isn't Maven using the plugin versions I told it to use? Thanks in advance, Daniel Serodio project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.example/groupId artifactIdbusca-web/artifactId version1.0.0-SNAPSHOT/version packagingwar/packaging nameBusca/name descriptionBusca - Frontent Web/description properties project.build.sourceEncodingISO8859-1/project.build.sourceEncoding project.reporting.outputEncodingUTF-8/project.reporting.outputEncoding /properties build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.6/source target1.6/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId /plugin /plugins /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.3/version /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.8/version configuration outputEncodingUTF-8/outputEncoding /configuration /plugin /plugins /reporting dependencies dependency groupIdorg.slf4j/groupId artifactIdslf4j-api/artifactId version1.6.1/version /dependency dependency groupIdorg.slf4j/groupId artifactIdslf4j-log4j12/artifactId version1.6.1/version /dependency dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId version2.6/version /dependency dependency groupIdmysql/groupId artifactIdmysql-connector-java/artifactId version5.1.6/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.8.1/version scopetest/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.5/version scopeprovided/scope /dependency /dependencies /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
