You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Nararasimhaiah Sreehari (JIRA)" <de...@myfaces.apache.org> on 2008/05/15 00:57:55 UTC

[jira] Updated: (TRINIDAD-1077) jdev plugin library configuration

     [ https://issues.apache.org/jira/browse/TRINIDAD-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nararasimhaiah Sreehari updated TRINIDAD-1077:
----------------------------------------------

    Status: Patch Available  (was: Open)

> jdev plugin library configuration
> ---------------------------------
>
>                 Key: TRINIDAD-1077
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1077
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Plugins
>    Affects Versions:  1.2.6-plugins
>         Environment: both windows and linux
>            Reporter: Nararasimhaiah Sreehari
>
> When the project path and the library path are absolute paths are not the same but  have a common folder name in the path, the libarary definition constructs incorrectly.
> eg: 
> project path d:\work\nsreehar\myapp\....
> and path to library is 
> c:\documents and settings\nsreehar\.m2\repository\org\.....
> Since the project is on d drive, the full path should be picked up. Instead, the plugin interprets this as having a single common path folder.
> The problem exists in both windows as well as linux.
> The problem appears to go away when the following patch
> 1665c1674
> <         if (sourcePaths[i].equals(targetPaths[i]))
> ---
> >         if (sourcePaths[i].equals(targetPaths[i])) 
> 1666a1676,1677
> >         else           
> >            break;    
> Please note that the fix described in TRINIDAD-331  has already been applied.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.