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

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

Re: How to stop embedded Tomcat server?

/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

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

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

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

RAR : How to get the jar included, how to limit transitive deps inclusion

Hi, I try to use the RAR plugin for M2 and have 2 problems. Background I have a project with src/java and the code for a JCA adapter under that. This is viewable here http://datanucleus.svn.sourceforge.net/viewvc/datanucleus/platform/jdo.connector/trunk/ If I execute mvn clean install I get a

maven-jaxb-plugin 1.1

Hello, My maven project used to download all dependencies like a charm, but recently I hear complaints from people who start from scratch that the project fails to download the jaxb compiler: The pom for my plugin is downloaded but the jar itself seems to be missing. I get the following

running jaxb twice with different configs

Hello, to build my app I compile two differen xsd files to generate O/X mapping. I have duplicated the jaxb-maven-plugin in my pom. When I run the build from eclipse both xsds are compiled, when i run from the command lineonly one xsd is compiled. Is my solution at fault or is the maven

Handling different resource files for eclipse development and production

Hi, We need to apply different .properties files depending on the environment, for instance we have different database connections in the development and production environment and we want to configure them with .properties files. We tried to use the resource plugin, and achieved what we want

Disallowing access to projects based on user roles?

Hi, is it possible to hide or disallow access to certain projects within continuum based on user roles? This is a requirement for inhouse projects where I am working - not everybody may work with all projects. Still it would make sense to use one continuum instance to build the projects.

Setting an arbitrary property for a plugin within its configuration

Hi, I always need to run the eclipse plugin with a certain profile (some common resources must be ignored, the eclipse plugin does not yet properly add common resources outside project folders). We defined a build profile that does not define this resource and activate it using a role