maven-2

问题 We use Wicket as our front end framework and until now our application is pure Java. However, I would like to start using a bit of Scala on some of our new classes. The old code would stay in Java. After installing the maven-scala-plugin, scala-library, scalatest dependencies and downloading them I had to face the problem that I do not know how to mix Scala with Java in Wicket. Until now I have only seen tutorials about either pure Java or pure Scala projects in Wicket. In the extended class

问题 We're using Maven at work at quite regularly we get the error message "The artifact has no valid ranges". After a long time of Googling and experimenting I realised what this error message means: The artifact does have valid ranges, just too many of them. For example, my master POM has a dependency on superframework v.1.0 only, but there is also a transitive dependency on superframework v.0.5-0.9. Until now, whenever I had such a problem I've looked at the (very cryptic) error message and

问题 I'm trying to setup a new gwt project in Eclipse (3.4 Ganymede) using maven with the codehause gwt-mave-plugin (v. 1.1). I have installed the Google Eclipse Plugin including the Google App Engine Java SDK 1.2.2, the Google Plugin for Eclipse 3.4 and the Google Web Toolkit SDK 1.7.0. I'm using the gwt-maven-plugin archetype to generate a sample project as specified here. I have successfully generated the project files and imported them as a maven project into eclipse. I have then generated a

问题 What I want to do is this: I have a pom.xml that depends on some property that the user will have to type as he calls mvn by an -D property. The problem is, if the user don't give me this option, the mvn should fail with an custom error message, as "This program won't compile because you must define this property..." Does anyone know what's the simplest way to make this happen? I don't want to create a plugin that throws an Exception just to do this. 回答1: The Maven Enforcer Plugin already has

问题 When I run the following command for the root project, it checks for updates of ALL dependencies: mvn versions:use-latest-versions I want to limit versions update for only those dependencies which are reachable from the root : root/pom.xml ├── A/pom.xml │ └── D/pom.xml │ └── E/pom.xml ├── B/pom.xml └── C/pom.xml ├── F/pom.xml └── G/pom.xml The group and artifact ids of these dependencies are in the current reactor build (multi-module build). For example, I don not want to update external

问题 I have some code generated from xsd files by xmlbeans-maven-plugin. Unfortunately generated code uses raw collection types, like: java.util.List targetList = new java.util.ArrayList(); get_store().find_all_element_users(CURRENCY$0, targetList); Currency[] result = new Currency[targetList.size()]; targetList.toArray(result); which causes lots of warnings. Is there a way to force the plugin to generate generic types or generate @SupressWarnings annotations? I use maven v 2.0.9, xmlbeans-maven

问题 I deployed a sonatype nexus server inside my LAN , mapping some remote repositories to my public repositories : alt text http://img576.imageshack.us/img576/5517/7875d01884ad4234a5b02e2.png First question is , why these repositories not sync with the "real" repositories ? For example , I mapped maven central (http://repo1.maven.org/maven2) to "central" , but when I browse http://smallufo:8081/nexus/content/repositories/central/org/springframework/ , the packages are not complete , in http:/

问题 I'm trying to override the default resources directory (src/main/resources) when using the maven-remote-resources-plugin . However the specified value in the sample below doesn't seem to be taken into account. Would appreciate if someone could give me some pointers. <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"> <modelVersion>4.0.0<

问题 From what I can find there is no specific maven plugin for WAS 7, so I am wondering if the was6-maven-plugin will work with the newer version of the server. 回答1: I asked IBM the same very questions: officialy yes, in reality the Jar Hell will give you some problems.. If I were you I would dimension a couple of days for issue resolution. 回答2: was6-maven-plugin works for me on WAS7 without problems but you have to hack when you want to deploy multiple EARs from one Maven module. You don't have

问题 I am using the latest version 1.341 of the Hudson CI to build my maven-2 project (built using 2.2.0). But I get some warnings which I don't see if executed via a command prompt. Can someone let me know, how to debug this issue? ---------------------------------------------------------- Executing Maven: -B -f d:\work\software\data\hudson\jobs\bio\workspace\trunk\pom.xml install [WARNING] ************ WARNING ************ This Maven runtime contains a LifecycleExecutor component with an