Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] Juno to Kepler project migration

>Users should just remove the project from their local workspace, then resync. There is even no need to remove the .ptp-sync as John has already taken care of that.
Do you mean: remove the project from their local workspace, and recreate the sync project, pointing at the same remote dir?
(How do you resync a project you removed?)


...Beth

Beth Tibbitts
Eclipse Parallel Tools Platform  http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


Inactive hide details for John Eblen ---05/06/2013 04:50:13 PM---Yes, that should work because only the local information needsJohn Eblen ---05/06/2013 04:50:13 PM---Yes, that should work because only the local information needs to be reconstructed. The remote files


    From:

John Eblen <jeblen@xxxxxxx>

    To:

Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>

    Date:

05/06/2013 04:50 PM

    Subject:

Re: [ptp-dev] Juno to Kepler project migration

    Sent by:

ptp-dev-bounces@xxxxxxxxxxx




Yes, that should work because only the local information needs to
be reconstructed. The remote files should be fine.


John


On Mon, May 6, 2013 at 4:37 PM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
    The .eclipsesettings directory is irrelevant.

    Users should just remove the project from their local workspace, then resync. There is even no need to remove the .ptp-sync as John has already taken care of that.

    Greg

    On May 6, 2013, at 4:19 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:

      John,
      How would a user migrate their code from ptp-juno to ptp-kepler?
      Assuming a sync project has code in the client workspace dir, and on the remote target project dir as well...


      I would venture to guess: new client workspace, but on remote target: delete home/.eclipsesettings, delete project/.ptp-sync dir and all .* files -
      then re-create sync project in new workspace, pointing at src code.
      The beauty of synchronized projects!



      ...Beth

      Beth Tibbitts
      Eclipse Parallel Tools Platform  
      http://eclipse.org/ptp
      IBM STG - High Performance Computing Tools
      Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


      <graycol.gif>
      John Eblen ---05/06/2013 04:09:23 PM---Hi Yes, due to the numerous changes we've made to synchronized projects,
<ecblank.gif>
    From:
<ecblank.gif>
John Eblen <
jeblen@xxxxxxx>
<ecblank.gif>
    To:
<ecblank.gif>
Parallel Tools Platform general developers <
ptp-dev@xxxxxxxxxxx>
<ecblank.gif>
    Date:
<ecblank.gif>
05/06/2013 04:09 PM
<ecblank.gif>
    Subject:
<ecblank.gif>
Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench
<ecblank.gif>
    Sent by:
<ecblank.gif>
ptp-dev-bounces@xxxxxxxxxxx




    Hi

    Yes, due to the numerous changes we've made to synchronized projects, projects created
    with Juno won't work in Kepler. (This is because project data are now stored in different
    places and in different formats.)


    John


    On Mon, May 6, 2013 at 3:43 PM, Arnold, Galen Wesley <
    gwarnold@xxxxxxxxxxxx> wrote:
      Beth,

      It looks broken to me, you owe me a workspace.

      :)

      ...cannot sync after making a change to a src file...nothing happens at all and the file is only changed locally.

      I haven't been able to find a workaround/fix
        -removing .ptp-sync: no help,
        -proj. properties -> synchronize -> add (it was all blank)

      ???

      It's broken but good.  This is quite the *upgrade*. 


      -Galen


      Galen Arnold
      NCSA - systems engineer



      From:
       ptp-dev-bounces@xxxxxxxxxxx [ptp-dev-bounces@xxxxxxxxxxx] on behalf of Beth Tibbitts [tibbitts@xxxxxxxxxx]
      Sent:
       Monday, May 06, 2013 2:34 PM
      To:
       Parallel Tools Platform general developers
      Subject:
       Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench

      Breaking existing workspaces from previous versions of ptp-kepler might be "to be unavoidably expected" if we have changed the underlying project infrastructure.
             ..just sayin'   :)
      However breaking previous workspaces from a juno version is different. We need a migration plan for existing PTP users, yes.  (I haven't tried it.)
      John E can answer this better than I can.

      But yes, please try it!  Good point.

      ...Beth

      Beth Tibbitts
      Eclipse Parallel Tools Platform  
      http://eclipse.org/ptp
      IBM STG - High Performance Computing Tools
      Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


      <graycol.gif>
      "Arnold, Galen Wesley" ---05/06/2013 03:22:12 PM---no can do.  I'll test with existing workspace and if you break it, you bought it!!! Really, breaking


    <ecblank.gif>
      From:
    <ecblank.gif>
    "Arnold, Galen Wesley" <
    gwarnold@xxxxxxxxxxxx>
    <ecblank.gif>
      To:
    <ecblank.gif>
    Parallel Tools Platform general developers <
    ptp-dev@xxxxxxxxxxx>
    <ecblank.gif>
      Date:
    <ecblank.gif>
    05/06/2013 03:22 PM
    <ecblank.gif>
      Subject:
    <ecblank.gif>
    Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench
    <ecblank.gif>
      Sent by:
    <ecblank.gif>
    ptp-dev-bounces@xxxxxxxxxxx




      no can do.  I'll test with existing workspace and if you break it, you bought it!!!

      Really, breaking existing workspaces is a bug and not a feature.  I'll let you know ...


      Galen Arnold
      NCSA - systems engineer



      From:
       ptp-dev-bounces@xxxxxxxxxxx [ptp-dev-bounces@xxxxxxxxxxx] on behalf of Beth Tibbitts [tibbitts@xxxxxxxxxx]
      Sent:
       Monday, May 06, 2013 10:37 AM
      To:
       Parallel Tools Platform general developers
      Subject:
       Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench

      P.S. Please test with a new workspace (at least to start with) - sync project infrastructure has changed.

      ...Beth

      Beth Tibbitts
      Eclipse Parallel Tools Platform  
      http://eclipse.org/ptp
      IBM STG - High Performance Computing Tools
      Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


      <graycol.gif>
      Doug James ---05/06/2013 10:59:32 AM---Thanks Beth. I assumed that this pre-release stuff was too raw to be supported by Install New Softwa 
      <ecblank.gif>
        From:
      <ecblank.gif>
      Doug James <
      djames@xxxxxxxxxxxxxxx>
      <ecblank.gif>
        To:
      <ecblank.gif>
      Parallel Tools Platform general developers <
      ptp-dev@xxxxxxxxxxx>
      <ecblank.gif>
        Date:
      <ecblank.gif>
      05/06/2013 10:59 AM
      <ecblank.gif>
        Subject:
      <ecblank.gif>
      Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench
      <ecblank.gif>
        Sent by:
      <ecblank.gif>
      ptp-dev-bounces@xxxxxxxxxxx




      Thanks Beth. I assumed that this pre-release stuff was too raw to be supported by Install New Software. Figured I was going to have to manually configure things. Rookie mistake. Good to know.

      Doug James
      High Performance Computing
      Texas Advanced Computing Center
      The University of Texas at Austin


      From:
       ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx] On Behalf Of Beth Tibbitts
      Sent:
       Monday, May 06, 2013 9:55 AM
      To:
       Parallel Tools Platform general developers
      Subject:
       Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench
       

      Sorry Doug -- use the text of those links b.c.d. as update sites: with Help>Install New Software..., don't click on them.
      My stupid email client made links out of some it shouldn't have (and did it incorrectly)

      These are more correct:  (Note that b.c.d. are update sites, not meant to go to in your browser for most of them (for ptp we do have an index.html there though)
      a. get parallel package e.g. from M6
      http://eclipse.org/downloads/index-developer.php
      b. update CDT from  
      http://download.eclipse.org/tools/cdt/builds/kepler/nightly/
      c. update PTP from
      http://download.eclipse.org/tools/ptp/builds/kepler/nightly/
      d. update jGit from    
      http://download.eclipse.org/egit/updates-nightly  

      ...Beth

      Beth Tibbitts
      Eclipse Parallel Tools Platform  
      http://eclipse.org/ptp
      IBM STG - High Performance Computing Tools
      Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511


      <graycol.gif>
      Doug James ---05/06/2013 10:37:24 AM---Beth - I'm having trouble with some of the links. Am I missing something? 
    <52848493.gif>
      From:
    <52075997.gif>
    Doug James <
    djames@xxxxxxxxxxxxxxx>
    <52848493.gif>
      To:
    <52075997.gif>
    Parallel Tools Platform general developers <
    ptp-dev@xxxxxxxxxxx>
    <52848493.gif>
      Date:
    <52075997.gif>
    05/06/2013 10:37 AM
    <52848493.gif>
      Subject:
    <52075997.gif>
    Re: [ptp-dev] Kepler M7 early testing: How to assemble an updated workbench
    <52848493.gif>
      Sent by:
    <52075997.gif>
    ptp-dev-bounces@xxxxxxxxxxx
    _______________________________________________
    ptp-dev mailing list

    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev


    _______________________________________________
    ptp-dev mailing list

    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


GIF image

GIF image


Back to the top