#339 Path is "none:null" in psf file

closed-fixed
6
2012-10-04
2012-10-01
Rebecka
No

When I export a team project set the path in the psf file becomes "none:null", e.g.:

<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
<provider id="net.sourceforge.eclipseccase.ClearCaseProvider">
<project reference="1.0:BbModule3Elements:none:null"/>
</provider>
</psf>

This happens in versions 2.2_22 and 2.2_16, but not in 2.2_15.

Discussion

  • Mikael Petterson

    ok I have a look at it.

    //mike

     
  • Mikael Petterson

    • assigned_to: nobody --> eraonel
    • priority: 5 --> 6
    • status: open --> open-accepted
     
  • Mikael Petterson

    By the way you don't happen to have a trace available?

    br,

    //mike

     
  • Mikael Petterson

    Also can you attach the working psf file and view name.

    //mike

     
  • Mikael Petterson

    Looking at the code it is more pure luck that it in 2.2.15 :-)

    Anyway related to your request, 3573773 Get rid of manual prompt for vob location it is better to fix this once and for all.

    The current format for exported psf file is:

    <?xml version="1.0" encoding="UTF-8"?>
    <psf version="2.0">
    <provider id="net.sourceforge.eclipseccase.ClearCaseProvider">
    <project reference="1.0:<project_name>:<vob name>:<relative vob path>"/>
    </provider>
    </psf>

    Then when you do import as mentioned in 3573773 you specify the root ( /vobs or M: ).

    Then currently the code is concatenating:

    <root>+<vob_name>+<relative_path>

    Working with unix path we have no problem. We could make the vobname same as /vobs/<name>
    but for windows we have a slight problem since view can be mounted on different drives.

    //mike

     
  • Rebecka

    Rebecka - 2012-10-04

    Does that mean you've found the problem then, or do you still want a trace, working psf file and view name? Or is there any other way I can help?

     
  • Mikael Petterson

    I have found the problem.

    //mike

     
  • Mikael Petterson

    I have made a quick fix for this.

    The getVobName(IResource) uses:
    public String getViewRoot(IResource resource) throws TeamException {
    return ClearCasePlugin.getEngine().getViewLocation();
    }

    But this will not return empty String but mounted ucm vob ( last in the list):

    /cc/<server>/vobname,

    I have currently implemented the more correct ClearCasePlugin.getEngine().getViewRoot(String filepath).

    br,

    //mike

     
  • Mikael Petterson

    • status: open-accepted --> pending-fixed
     
  • Mikael Petterson

    Fixed and in release 2.2.24

    //mike

     
  • Rebecka

    Rebecka - 2012-10-04

    I've tested 2.2.24 and it works! Thanks for fixing it, and for fixing it so fast, we really appreciate it! :)

    If I understand you correctly about the feature request, the problem is that the vob location is different in windows than in unix? If this information (whether it's a windows or unix system) can't be stored in the psf file, maybe it could be a preference setting? E.g. if I set the preference option "Vob location" to "/vobs", I won't have to choose it every time I import a project, and those who work in windows can set it to "M:".

     
  • Rebecka

    Rebecka - 2012-10-04
    • status: pending-fixed --> open-accepted
     
  • Mikael Petterson

    Appreciations go here: https://sourceforge.net/projects/eclipse-ccase/reviews/

    Thanks :-)

    Yes I was thinking we could have a vob root variable ${VOB_ROOT} that could be set in the preferences ( for windows it could be M:\\ and unix /vobs). I will have a look at it asap.

    br,

    //mike

     
  • Mikael Petterson

    • status: open-accepted --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks