You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "L. Compère (JIRA)" <ji...@codehaus.org> on 2011/09/16 00:27:17 UTC
[jira] Created: (MDEP-325) build-classpath adds a newline character
when dependency artifact name starts with letter n
build-classpath adds a newline character when dependency artifact name starts with letter n
-------------------------------------------------------------------------------------------
Key: MDEP-325
URL: https://jira.codehaus.org/browse/MDEP-325
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: build-classpath
Affects Versions: 2.3, 2.2, 2.1
Reporter: L. Compère
Assignee: Brian Fox
I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MDEP-325) build-classpath adds a
newline character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282825#comment-282825 ]
Thomas Gran edited comment on MDEP-325 at 11/4/11 1:39 PM:
-----------------------------------------------------------
I have added a patch witch:
o Fixes so the pathSeparator is left untouched by the replacment of the fileSeparator.
o The unit tests are updated.
o The fix does not escape '\' with another '\' when the outputFilterFile is set.
To escape the '\' when outputFilterFile is set, is not so easy. You should not replace '\' in the prefix, pathSeparator or fileSeparator (when set), because this would make it impossible to use '\n' and so on. Then only doing it in the file name seems a bit odd. Futher this would break the backward compabillity. In most cases setting the fileSeparator to a double '\' or '/' would be a good workaround.
was (Author: thomasgran):
I have added a patch witch:
o Fixes so the pathSeparator is left untouched by the replacment of the fileSeparator.
o The unit tests are updated.
o The fixdoes not escape '\'with another '\' when outputToFilterFile. See comments on this bug.
To escape the '\' when outputFilterFile is set, is not so easy. You should not replace '\' in the prefix, pathSeparator or fileSeparator (when set), because this would make it impossible to use '\n' and so on. Then only doing it in the file name seems a bit odd. Futher this would break the backward compabillity. In most cases setting the fileSeparator to a double '\' or '/' would be a good workaround.
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
> Attachments: MDEP-325.patch
>
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MDEP-325) build-classpath adds a
newline character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282558#comment-282558 ]
Thomas Gran edited comment on MDEP-325 at 11/4/11 1:37 PM:
-----------------------------------------------------------
Ignore
was (Author: thomasgran):
I ment,
{noformat}
When generating a properties file the File.separator should by default be '\\' on windows and '/' on Unix.
{noformat}
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
> Attachments: MDEP-325.patch
>
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-325) build-classpath adds a newline
character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282558#comment-282558 ]
Thomas Gran commented on MDEP-325:
----------------------------------
I ment,
{noformat}
When generating a properties file the File.separator should by default be '\\' on windows and '/' on Unix.
{noformat}
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MDEP-325) build-classpath adds a
newline character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282825#comment-282825 ]
Thomas Gran edited comment on MDEP-325 at 11/4/11 1:34 PM:
-----------------------------------------------------------
I have added a patch witch:
o Fixes so the pathSeparator is left untouched by the replacment of the fileSeparator.
o The unit tests are updated.
o The fixdoes not escape '\'with another '\' when outputToFilterFile. See comments on this bug.
To escape the '\' when outputFilterFile is set, is not so easy. You should not replace '\' in the prefix, pathSeparator or fileSeparator (when set), because this would make it impossible to use '\n' and so on. Then only doing it in the file name seems a bit odd. Futher this would break the backward compabillity. In most cases setting the fileSeparator to a double '\' or '/' would be a good workaround.
was (Author: thomasgran):
o This patch fixes so the pathSeparator is left untouched by the replacment of the fileSeparator.
o The unit tests are updated.
o The fixdoes not escape '\'with another '\' when outputToFilterFile. See comments on this bug.
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
> Attachments: MDEP-325.patch
>
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MDEP-325) build-classpath adds a
newline character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282556#comment-282556 ]
Thomas Gran edited comment on MDEP-325 at 11/4/11 1:37 PM:
-----------------------------------------------------------
I am trying to inject (using filtering) the classpath into a fitnesse content.txt file (more on this later). I get simular errors. When a properties file is read by Java the '\n' is translated the same way as in Java Strings, so is '\r', '\t', '\f' ... as well as '\012' and '\u0020'. This is nice and make it simple to inject new lines as well as other specal characters. But setting the <fileSeparator> and <pathSeparator> does not work correct:
Example:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n</pathSeparator>
Should produce:
___
C:/myrepo/org/a/a-1.0.jar
C:/myrepo/org/b/b-1.0.jar
^^^
but instead I get:
___
C:/myrepo/org/a/a-1.0.jar/nC:/myrepo/org/b/b-1.0.jar
^^^
All '\' (not only File.separator) is replaced.
Note! When generating a fitness classpath I also need to insert whitespace (both new lines and space). Since whitespace is trimed of xml elements (even CDATA) it is important for me to keep the translation of the '\' character when loading the properties file.
HOWTO ON FITNESS:
Here is how a fitness classpath could be generated:
content.txt:
!contents -g
!path ${classpath}
!path ../../target/classes
maven-dependency-plugin config:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n!path\u0020</pathSeparator>
<outputFilterFile>true</outputFilterFile>
<outputFile>myFilter.properties</outputFile>
And then set up resource filtering ...
was (Author: thomasgran):
I am trying to inject (using filtering) the classpath into a fitnesse content.txt file (more on this later). I get simular errors. When a properties file is read by Java the '\n' is translated the same way as in Java Strings, so is '\r', '\t', '\f' ... as well as '\012' and '\u0020'. This is nice and make it simple to inject new lines as well as other specal characters. But setting the <fileSeparator> and <pathSeparator> does not work correct:
Example:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n</pathSeparator>
Should produce:
___
C:/myrepo/org/a/a-1.0.jar
C:/myrepo/org/b/b-1.0.jar
^^^
but instead I get:
___
C:/myrepo/org/a/a-1.0.jar/nC:/myrepo/org/b/b-1.0.jar
^^^
All '\' (not only File.separator) is replaced.
When generating a properties file the File.separator should by default be '\\' on windows and '/' on Unix.
Note! When generating a fitness classpath I also need to insert whitespace (both new lines and space). Since whitespace is trimed of xml elements (even CDATA) it is important for me to keep the translation of the '\' character when loading the properties file.
HOWTO ON FITNESS:
Here is how a fitness classpath could be generated:
content.txt:
|!contents -g|
!path ${classpath}
!path ../../target/classes
maven-dependency-plugin config:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n!path\u0020</pathSeparator>
<outputFilterFile>true</outputFilterFile>
<outputFile>myFilter.properties</outputFile>
And then set up resource filtering ...
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
> Attachments: MDEP-325.patch
>
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-325) build-classpath adds a newline
character when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282556#comment-282556 ]
Thomas Gran commented on MDEP-325:
----------------------------------
I am trying to inject (using filtering) the classpath into a fitnesse content.txt file (more on this later). I get simular errors. When a properties file is read by Java the '\n' is translated the same way as in Java Strings, so is '\r', '\t', '\f' ... as well as '\012' and '\u0020'. This is nice and make it simple to inject new lines as well as other specal characters. But setting the <fileSeparator> and <pathSeparator> does not work correct:
Example:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n</pathSeparator>
Should produce:
___
C:/myrepo/org/a/a-1.0.jar
C:/myrepo/org/b/b-1.0.jar
^^^
but instead I get:
___
C:/myrepo/org/a/a-1.0.jar/nC:/myrepo/org/b/b-1.0.jar
^^^
All '\' (not only File.separator) is replaced.
When generating a properties file the File.separator should by default be '\\' on windows and '/' on Unix.
Note! When generating a fitness classpath I also need to insert whitespace (both new lines and space). Since whitespace is trimed of xml elements (even CDATA) it is important for me to keep the translation of the '\' character when loading the properties file.
HOWTO ON FITNESS:
Here is how a fitness classpath could be generated:
content.txt:
|!contents -g|
!path ${classpath}
!path ../../target/classes
maven-dependency-plugin config:
<fileSeparator>/</fileSeparator>
<pathSeparator>\n!path\u0020</pathSeparator>
<outputFilterFile>true</outputFilterFile>
<outputFile>myFilter.properties</outputFile>
And then set up resource filtering ...
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEP-325) build-classpath adds a newline character
when dependency artifact name starts with letter n
Posted by "Thomas Gran (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Gran updated MDEP-325:
-----------------------------
Attachment: MDEP-325.patch
o This patch fixes so the pathSeparator is left untouched by the replacment of the fileSeparator.
o The unit tests are updated.
o The fixdoes not escape '\'with another '\' when outputToFilterFile. See comments on this bug.
> build-classpath adds a newline character when dependency artifact name starts with letter n
> -------------------------------------------------------------------------------------------
>
> Key: MDEP-325
> URL: https://jira.codehaus.org/browse/MDEP-325
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: L. Compère
> Assignee: Brian Fox
> Attachments: MDEP-325.patch
>
>
> I'm using a combination of the maven-dependency-plugin and the maven-assembly-plugin to insert a classpath in a filtered resource.
> It so happens that one of the dependencies to be added to the classpath is "neethi-2.0.4.jar".
> The build-classpath goal of the dependency plugin writes the following in a file (all on one line):
> classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> When the assembly plugin uses the content of the file generated by the build-classpath goal of the dependency plugin, it translates the \n found in "%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;" into a NEWLINE character... causing my classpath to be broken as such (on two lines):
> %MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
> eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
> notice how neethi-2.0.4.jar has become eethi-2.0.4.jar....
> Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira