You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Lukas Theussl (JIRA)" <co...@jakarta.apache.org> on 2006/05/14 08:18:08 UTC

[jira] Created: (JELLY-230) Problem with default namespace in imported scripts

Problem with default namespace in imported scripts
--------------------------------------------------

         Key: JELLY-230
         URL: http://issues.apache.org/jira/browse/JELLY-230
     Project: Jelly
        Type: Bug

  Components: core / taglib.core  
    Versions: 1.1    
 Environment: jelly-1.1-SNAPSHOT
    Reporter: Lukas Theussl
 Assigned to: 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
http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).

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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402290 ] 

Paul Libbrecht commented on JELLY-230:
--------------------------------------

I fear that the problem is considered to be "backwards compatibility" even though a normal perspective would be call to it a bug-fix.

Lukas, does the solution replaceNamespace sound doable for you ?
Alternatively, what about having a flag at XMLOutput (which is probably instantiated by Maven anyways) to do this?
(it seems pretty equivalent, actually)

As far as I know this has nothing to do with import... or I'd need an extra explanation

paul

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      Project: 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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12416139 ] 

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"> 
	<glup/>
</project>

</x:replaceNamespace></j:jelly>

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

paul

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Lukas Theussl (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12417207 ] 

Lukas Theussl commented on JELLY-230:
-------------------------------------

Ok, I have to correct myself twice :(

First, the dummy namespace does have a special treatment in maven, it gets excluded in the startPrefixMapping() method of PluginScriptParser.java.
Second, I did get the replaceNamespace tag to work: I had to wrap it around the j:import:

<j:file name="build.xml" prettyPrint="true">
  <x:replaceNamespace fromURI="dummy" toURI="">
    <j:import file="templates/build.jelly" inherit="true"/>
  </x:replaceNamespace>
</j:file>

That means that this looks like its doable for us, even though not very convenient. We'd have to republish a number of plugins that we just released recently, with only minor modifications and dependency upgrades, and they will all be incompatible with Maven 1.0. Prerequisite for all that is that you get me a new release of jelly-core and taglib-xml out ASAP. :)

Playing around with it today, I found another issue: the xml:parse tag doesn't seem to work properly if the parsed xml has a namespace declaration in it's top element. I didn't investigate any further for now, just wanted to know if this is a known issue or if I'm missing something again.

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Diogo Bacelar Quintela (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402283 ] 

Diogo Bacelar Quintela commented on JELLY-230:
----------------------------------------------

You could use the replaceNamespace tag..

<x:replaceNamespace fromURI="dummy" toURI="">
   <project name="${pom.artifactId}" default="jar" basedir=".">
      <target name="clean" description="Clean up">
        <delete dir="$${defaulttargetdir}"/>
        <delete dir="$${distdir}"/>
      </target>
  </project> 
</x:replaceNamespace> 


It should work dispite i haven't tested.

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      Project: 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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Lukas Theussl (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402354 ] 

Lukas Theussl commented on JELLY-230:
-------------------------------------

The replaceNamespace thingy doesn't work for me. I may be doing something wrong or be missing something, but here is the beginning of the generated build.xml:

<x:replaceNamespace xmlns:x="jelly:xml" toURI="" fromURI="dummy">
  <project xmlns="dummy" default="jar" basedir="." name="test-maven-ant-plugin">

ie the <x:replaceNamespace> gets translated verbatim, even though I have a <x:comment> just before that which gets correctly translated into a comment. I tried with jelly-tags-xml-1.1 and 1.2-SNAPSHOT from svn.

Anyway, Paul is right that my main concern is backwards compatibility: we would have to adjust a number of plugins and they would all be incompatible with older maven releases (the latest stable maven 1.0.2 in particular). Also I don't think that this is specific to Maven (at least I am not aware of "dummy" having any special treatment in maven). The problem is: how to generate a file without namespace declaration from a template where I need to declare a default namespace in order to distinguish it from the default namespace of the application that parses the template?

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      Project: 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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (JELLY-230) Problem with default namespace in imported scripts

Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/JELLY-230?page=comments#action_12402265 ] 

Paul Libbrecht commented on JELLY-230:
--------------------------------------

Gee!! I certainly hope that Jelly acts like this as this is normal XML!

What I realize is that this dummy namespace has had a special treatment for maven or within maven and that special treatment means... be renamed to the no-namespace, correct ?

I cannot see this without an "environment observation" of seeing maven around in order to decide that such a renaming should happen... or do you ?

paul

> Problem with default namespace in imported scripts
> --------------------------------------------------
>
>          Key: JELLY-230
>          URL: http://issues.apache.org/jira/browse/JELLY-230
>      Project: 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
> http://jira.codehaus.org/browse/MAVEN-1691 (gee, I wish I'd checked the svn archives earlier!).
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org