maven-2

I am making my first foray into scala for a production app. The app is currently packaged as a war file. My plan is to create a jar file of the scala compiled artifacts and add that into the lib folder for the war file. My enhancement is a mysql-backed app exposed via Jersey & will be integrated with a 3rd party site via HttpClient invocations. I know how to do this via plain java. But when doing it in scala, there are several decision points that I am pussyfooting on. scala 2.7.7 or 2.8 RC ? JDBC via querulous Is this API ready for production ? sbt vs maven. I am comfortable with maven. Is

I was going through a book that explain how to override 'default' lifecycle of Maven. It says: To define a new lifecycle for a packaging type, you'll need to configure a LifecycleMapping component in Plexus. In your plugin project, create a META-INF/plexus/components.xml under src/main/resources. In components.xml add the content as shown below, and you're done. With below configuration, I'm able to customize the default lifecycle for 'jar' packaging type. Now If I exeute $ mvn package It straigh away executes 'package' phase skipping all other phases of default lifecycle and executes 'echo'

I've been using Cobertura plugin for report generation and instrumentation (with surefire). Here is the issue I am facing: I am unable to make the plugin ignore report generation for specific classes in my project. PF below the related excerpt from pom.xml, I have added the ignore tag, but that just ignores instrumentation for the ignored classes. I want the report for specific projects to not be generated at all. Firstly, due to my limited knowledge of both Maven and Conberture, I want to know is it possible, and if yes, then what are the changes I need to get done in pom.xml. pom.xml <report

I have a maven3 multimodule project, and for a strange reason i need to customize POM filename for one of my child module (ie: module-pom.xml) Is it possible to configure this in the parent pom ? The strange reason is a bit long to explain sorry, but you will have the plain context. Context I'm working on a closed source project that also use LGPLed projects. this project is called main I want main to declare modules of every projects, closed and opened. The full build should be made with a unique mvn clean package command. Inside the main reactor project, i have lgpl-reactor multimodule

I have installed m2eclipse plugin from http://m2eclipse.codehaus.org/ . Now I want to use that as a standalone build tool but I am unable to find the installation directory. Can anyone help me in this? I have both the plugin (with its embedded maven instance) and a full maven download. Both should end up using the same repository in something like C:\Documents and Settings\user\.m2 . There are a few cases where you need a full maven download anyways. For example, trying to build a groovy maven plugin crashes with the embedded maven, but works fine for the full download. You can also specify

Given that it's very hard to find anything about dependency version ranges in the official documentation (the best I could come up with is http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution ), I wonder if they're still considered a 1st class citizen of Maven POMs. I think most people would agree that they're a bad practice anyway, but I wonder why it's so hard to find anything official about it. Brett Porter They are not deprecated in the formal sense that they will be removed in a future version. However, their limitations (and the subsequent lack of wide

I am using Maven, with the one-jar pluggin, but when I run the one jar executable, I'm greeted with a wall of warnings, this is unacceptable for use I've looked at every available resource on one-jar and see no instruction on how to keep the jar for spewing out tons of warnings when run, has anyone solved this? JarClassLoader: Warning: META-INF/LICENSE.txt in lib/commons-io-1.4.jar is hidden by lib/commons-collections-3.2.1.jar (with different bytecode) JarClassLoader: Warning: META-INF/NOTICE.txt in lib/commons-io-1.4.jar is hidden by lib/commons-collections-3.2.1.jar (with different bytecode

Is there a way to tell maven (when doing mvn package , mvn site or ...) not to resolve the dependencies from the local repository? Background of this question: Sometimes I get into problems, when previously cached dependencies (e.g. SomeProject-0.7-ALPHA) are no longer available in the remote repository. In my local build everything still works fine as the dependency has been cached before. As soon as I share my pom with others, they may get into trouble, as they dont have a cached version of that dependency and the dependency can no longer be resolved from the remote repository. Any help will

I have following tests structure: public class WorkerServiceTest { public class RaiseErrorTest extends AbstractDbUnitTest{ @Test public void testSomething(){ } ... } ... } It's done because I don't want to create a separate class file for every test case extending AbstractDbUnitTest . The problem is that mvn test doesn't run test from my inner class. Is there is a way how to configure Maven to run such tests? Of course I can create methods in the parent class calling the inner class methods but I want a clearer way. Yes, this is possible using the new (well, it's not new anymore) Enclosed