commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Libbrecht (JIRA)" <>
Subject [jira] Commented: (JELLY-230) Problem with default namespace in imported scripts
Date Wed, 14 Jun 2006 08:51:31 GMT
    [ ] 

Paul Libbrecht commented on JELLY-230:

Lukas... replacenamespace is working fine for me.

The following:

<?xml version="1.0" encoding="UTF-8"?>
<j:jelly xmlns:j="jelly:core"
  xmlns:x="jelly:xml"><x:replaceNamespace xmlns:x="jelly:xml" toURI="" fromURI="dummy">

<project xmlns="dummy" default="jar" basedir="." name="test-maven-ant-plugin"> 


creates me:

<project default="jar" name="test-maven-ant-plugin" basedir="."><glup></glup></project>

as I expect.

If you get this re-output verbatim, your xml taglib version is wrong... the replaceNamespace
tag is missing.

Tell us if it helps... I am a bit reluctant to insert back the implicit replaceNamespace as
it is a normal purist approach to consider it a bug (and there's no way to get rid of it).
Would it be too many changes on the maven side ??


> Problem with default namespace in imported scripts
> --------------------------------------------------
>          Key: JELLY-230
>          URL:
>      Project: Commons Jelly
>         Type: Bug

>   Components: core / taglib.core
>     Versions: 1.1
>  Environment: jelly-1.1-SNAPSHOT
>     Reporter: Lukas Theussl
>     Assignee: james strachan
>     Priority: Critical

> I am trying to build Maven with jelly-1.1-SNAPSHOT from svn trunk because it contains
a fix for a regression that has blocked us for a long time, see
> (gee, I wish I'd checked the svn archives
> However, even though jelly-1.1-SNAPSHOT solves the above issue, it also leads to a whole
bunch of test failures in several of our plugins.
> After some investigation I found that they all turn out to be due to the same cause,
an apparent backwards incompatibility introduced in the fix for JELLY-213.
> I am not sure actually if this is a bug or the intended behavior, but it certainly breaks
backwards compatibility.
> To illustrate the problem: in the ant plugin we use the following snippet to generate
an ant build.xml file from a template:
> <j:file name="build.xml" prettyPrint="true">
>   <j:import file="templates/build.jelly" inherit="true"/>
> </j:file>
> where the template file build.jelly looks like this (simplified):
> <j:jelly
>   xmlns:ant="jelly:ant"
>   xmlns:j="jelly:core" 
>   xmlns="dummy">
>   <project name="${pom.artifactId}" default="jar" basedir=".">
>       <target name="clean" description="Clean up">
>         <delete dir="$${defaulttargetdir}"/>
>         <delete dir="$${distdir}"/>
>       </target>
>   </project>
> </j:jelly>
> Note the xmlns="dummy" namespace declaration which is necessary to distinguish the default
namespace of the template script from Maven's default namespace. Now with jelly-1.0, this
works as expected, but with the current jelly-1.1-SNAPSHOT, I get:
> <project xmlns="dummy" name="test-maven-ant-plugin" default="jar" basedir=".">
>   <target description="Clean up" name="clean">
>     <delete dir="${defaulttargetdir}">
>     </delete>
>     <delete dir="${distdir}">
>     </delete>
>   </target>
> <project>
> ie the dummy namespace declaration makes it into the top-level element of the generated
file. This makes ant very unhappy when invoked on this build file...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message