[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2376) eclipseclasspath task broken for windows

[Pete Muir (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2376?page=comments#action_12392100 ] 
            
Pete Muir commented on JBSEAM-2376:
-----------------------------------

It was a very cheap way to build a classpath with source jars automatically attached :) 

Now we need to just push more source jars into maven...

> eclipseclasspath task broken for windows 
> -----------------------------------------
>
>                 Key: JBSEAM-2376
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2376
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 2.0.0.GA
>            Reporter: Matt Drees
>         Assigned To: Pete Muir
>            Priority: Minor
>             Fix For: 2.0.1.GA
>
>
> The eclipseclasspath task in Seam's build.xml file creates an invalid .classpath file on windows.  For example, a generated classpath line looks like this:
> 	<classpathentry kind="lib" path="C:Documents and Settingsmatthew.drees.m2repositoryjavaxjmsjms1.1jms-1.1.jar"/>
> I did some debugging, and the removal of forward slashes occurs here: (EclipseClasspathTask.java line 77)
>                line = line.replaceFirst("@" + filterProperty + "@", eclipsepaths);
> It turns out String.replaceFirst treats forward slashes in the second argument as escape characters.
> (see http://forum.java.sun.com/thread.jspa?threadID=626091&messageID=3574350 and http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Matcher.html#appendReplacement(java.lang.StringBuffer,%20java.lang.String) )
> An easy solution is to use String.replace instead of String.replaceFirst.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira