Re: svn commit: r599553 - /maven/doxia/doxia/branches/doxia-1.0-alpha-x/doxia-modules/doxia-module-fml/src/main/mdo/fml.mdo

Le vendredi 30 novembre 2007, Vincent Siveton a écrit : > Hi Hervé, > > The goal of this branch was originaly to release the site plugin and > MPIR, without an important issue found in the doxia-1.0-alpha-9. > Now that site plugin is out, I dont think that we need to maintain it: > I hope we will r

Maven install

Hi I have the following structure src | ---main | resources | --- A.properties store

Re: [m1] PMD plugin dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Arnaud HERITIER wrote: > I hope that 1.1.1 is compatible with 1.1-beta-9. Depending of the part of > jaxen which is used by pmd it's possible that it works fine with the old > version. First, let me give you some general info: I'm an admin fo

Use of AntRun causes clean to fail for multiproject?

So I've whittled my way down to a very simple multiproject that exhibits the same failure I'm seeing on a larger-scale project. Attached is the example. http://www.nabble.com/file/p14085638/test.zip test.zip Here's the summary. The project consists of project 'test' with modules 'test-a' and

RE: [m1] PMD plugin dependencies

I'm open to it. I can complete the plugin upg and test with the existing dep versions as well. If it fails, then we are dead-ended without doing those upgrades; if it does not fail, then we have options ;-) > -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: F

RE: [m1] PMD plugin dependencies

I'm open to it. I can complete the plugin upg and test with the existing dep versions as well. If it fails, then we are dead-ended without doing those upgrades; if it does not fail, then we have options ;-) > -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: F

Re: [VOTE] Release maven-dependency-tree 1.1

+1 Vincent 2007/11/29, Carlos Sanchez <[EMAIL PROTECTED]>: > It has many improvements related to resolution event handling, using > the latest fixes in Maven 2.0.8 > > Release is staged in > http://people.apache.org/~carlos/staging-repo/ > > -- > I could give you my word as a Spaniard. > No good.

Re: [VOTE] maven-remote-resources-plugin 1.0-beta-1

+1 Vincent 2007/11/29, Daniel Kulp <[EMAIL PROTECTED]>: > > I'd like to release version 1.0-beta-1 of the > maven-remote-resources-plugin. This resolves one critical bug reported > by Jason Dillon as well as fixes two other issues: > > > Release Notes - Maven 2.x Remote Resources Plugin - Versi

Re: [Vote] Release Maven Clean Plugin 2.2 (take 2)

+1 Fabrice On Nov 30, 2007 12:43 AM, Vincent Siveton <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to release (again) maven-clean-plugin 2.2. All artifacts > respect the Apache release rules (Thanks Dan). > > This release fixes some bugs and makes some improvements. The last > release was made ov

Re: issue with filtering in Maven2

Just spotted that you're using a war. You could do the same for the webapps too. I have yet to come up with a good structure for the webapp problem... do I go: /src/filtered/resources /src/filtered/webapp /src/main/resources /src/main/webapp /src/test/resources /src/where do the filtered tes

Re: issue with filtering in Maven2

I normally have two subfolders of resources: /src/main/resources/verbatim /src/main/resources/filtered /src/test/resources/verbatim /src/test/resources/filtered with the following in the build section of the pom false ${basedir}/src/main/reso

issue with filtering in Maven2

Dear all, My dev environment is - Struts2, Spring Maven version: 2.0.5 Problem: ${user.id} in the struts.xml is getting replaced by the value of project.artifactID by maven2 filter plugin Description: part of my struts.xml :