You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Russell Simpkins <Ru...@bluefly.com> on 2008/09/15 16:13:10 UTC

small request

Maven team,

I discovered a small issue with the pom file that causes issues for xslt
templates. I find it useful to generate my own reports with xslt going
against the project pom file. By default, the project pom looks like
this:

<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">

When it really should look like this:

<project xmlns:maven="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">

----------------------------------------------------------

xmlns="http://maven.apache.org/POM/4.0.0"

v.s.

xmlns:maven="http://maven.apache.org/POM/4.0.0" 

----------------------------------------------------------

It's a slight change that has no harmful effect on maven. I thought I
fixed this for good by modifying my pom, but the release plugin
overwrote my fixes. I noticed that a fix was added some time back
http://jira.codehaus.org/browse/MDEP-39 could we modify that ever so
slightly to label the xmlns?

Thanks,

Russ

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: small request

Posted by Manos Batsis <ma...@geekologue.com>.
Russell Simpkins wrote:

> It's a slight change that has no harmful effect on maven. 


Actually, I believe what you propose sets the default POM namespace to 
null and declares a new namespace bound to the "maven" prefix but used 
nowhere in the document. This would certainly break other applications 
or XSLTs.

Declaring the POM namespace as the default (i.e. un-prefixed) NS in your 
XSLT will make XPAth like "/project/name". Alternatively, you can bind 
the maven namespace in your XSLT to "maven" and use 
"/maven:project/maven:name".

In any case, there is no reason to mess with the POM.

hth,

Manos


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org