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

> I had to remove the project from <workspace> and re-create it.
That's what I meant.
I would not remove the directory that the workspace expects to be there - you're confusing it.

When you re-create sync project pointing remote target at the old one, all the stuff shoudl come in.
If you had stuff in local dir that was filtered from being synced between the systems you could probably paste that in manually, but it would be tedious.

>On windows, I'd hope the new kepler-m7 build would reformat the drive and start a fresh install of linux mint.  :)
OK, now recovered from snorting coffee. good thing I'm wearing black jeans today.


...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 "Arnold, Galen Wesley" ---05/07/2013 10:09:04 AM---Beth, Removing the project directory from workspac"Arnold, Galen Wesley" ---05/07/2013 10:09:04 AM---Beth, Removing the project directory from workspace/ isn't sufficient.  The project still shows up a


    From:

"Arnold, Galen Wesley" <gwarnold@xxxxxxxxxxxx>

    To:

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

    Date:

05/07/2013 10:09 AM

    Subject:

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

    Sent by:

ptp-dev-bounces@xxxxxxxxxxx




Beth,

Removing the project directory from workspace/ isn't sufficient.  The project still shows up and is now missing important piece(s).  I had to remove the project from eclipse-kepler-m7 and re-create it.

That's the story on linux.

On windows, I'd hope the new kepler-m7 build would reformat the drive and start a fresh install of linux mint.  :)

-Galen

Galen Arnold
NCSA - systems engineer

From: ptp-dev-bounces@xxxxxxxxxxx [ptp-dev-bounces@xxxxxxxxxxx] on behalf of Greg Watson [g.watson@xxxxxxxxxxxx]
Sent: Tuesday, May 07, 2013 7:48 AM
To: Parallel Tools Platform general developers
Subject: Re: [ptp-dev] Juno to Kepler project migration

Yes, resync with remote project.

On May 6, 2013, at 5:02 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:
    >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

    <graycol.gif>    John Eblen ---05/06/2013 04:50:13 PM---Yes, that should work because only the local information needs to be reconstructed. The remote files

<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:50 PM
<ecblank.gif>
    Subject:
<ecblank.gif>
Re: [ptp-dev] Juno to Kepler project migration
<ecblank.gif>
    Sent by:
<ecblank.gif>
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
      _______________________________________________
      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
    _______________________________________________
    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[attachment "Screenshot from 2013-05-07 08:58:33.png" deleted by Beth Tibbitts/Watson/IBM] _______________________________________________
    ptp-dev mailing list
    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev


GIF image

GIF image

Back to the top