Re: No compile errors with plexus-compiler-eclipse

Hello Olivier, Am 03.12.2012 um 10:52 schrieb Olivier Lamy : > Thanks for the test project. > It's now fixed. > You can test the fix with compiler plugin 3.1-SNAPSHOT and with > plexus-compiler-eclipse 2.1-SNAPSHOT Thanks a lot. I was able to get maven-compiler-plugin:3.1-SNAPSHOT from Apache s

RE: problem while conversion in build

I am using Xdoclet 1.2.3 and org.apache.maven.plugin is 1.6. There is no encoding tag in validator-global.xml If I add Then it simply added to validation.xml with all other tag and This line is added 2 time in Validation.xml   and it fails while xml validation. but conversion done p

[ANN] Maven Enforcer Plugin 1.2 Released

The Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.2 The enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules. http://maven.ap

maven-eclipse-plugin generates wrong eclipse project

Hi! I have a source directory structure like below (1). I have maven project that compiles uses in the pom.xml and all builds OK. When I run mvn eclipse:eclipse in same directory I do not get a usable Eclipse project. The classes dir after compilation looks like (2). I suggest that in general

Maven archetype Plugin, renaming a resource file?

Hi, I'am trying to rename a resource file when gnerating the archetype frome project : for exemple : "foo" project with a resource file "src/main/resources/foo.properties" , generating the archetype should generate "src/main/resources/__rootArtifactId__.properties" and then the final projetc "My

Re: problem while conversion in build

I've never used XDoclet but it sounds like xmlencoding attribute of tag only sets the output encoding, and there is no simple way to set the input incoding. It is also noteworthy that the default output encoding is UTF-8. Can you try to convert your validator-global.xml from

RE: problem while conversion in build

When we include xdoclet in the project there is no need to write validation.xml (for struts validation). All rules are defined in validator-global.xml and when user build using maven validation.xml is generated runtime and validator-global.xml is merged in validation.xml All properties ar

Re: problem while conversion in build

Hi,I don't understand your problem and doubt many people do. What is validation.xml and how does it relate to validation-global.xml? Why is form-validation tag relevant? I am afraid your question is as cryptic as Napoleon's kremlin letter (http://www.bbc.co.uk/news/world-europe-20572136). If you su

Re: No compile errors with plexus-compiler-eclipse

2012/12/2 Peter Palmreuther : > Hello Martin, > > Am 02.12.2012 um 15:37 schrieb Martin Gainty : >> I downloaded maven-eclipse-compiler version 1.9.2 from maven repo1 and was >> able to use the pom.xml to compile and package >> here is the pom.xml i implemented: >> [...] >> http://repo1.maven.org/

Re: hi, is these any properties like ${project.module} in maven's system properties?

There apparently are special ${module.*} properties you can use in a moduleSet (e.g. ${module.artifactId}); see http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_binaries (outputFileNameMapping's default value) And you might be able to use ${artifactId} also, see http://mave

Re: hi, is these any properties like ${project.module} in maven's system properties?

project.artifactId ? Jeff On Sun, Dec 2, 2012 at 4:21 PM, a wrote: > > I assembly a multi-module project, in the assembly, I write like the > follow, > is there any property word like ${project.module} to replace "module1"? > or can i user .properties file to set project.module1=module1? >