1 Reply Latest reply on Jan 23, 2015 4:57 PM by George Gastaldi

    Unable to fully remove addon (forge 2.13.0)

    Michael Schwartz Newbie

      While developing addon's it is important to constantly redeploying the addon without changing the version number for each deploy. Currently this is not possible without closing/opening eclipse between each redeploy. After a while I found the following:

       

      When executing "addon-remove" in Eclipse Luna the specified addon gets removed in the installed.xml file in the user's .forge directory.

      The corresponding class-files in .forge directory however are still there and cannot be deleted under windows which is an indicator of an open file pointer.

       

      When stopping forge console the directory still cannot be deleted. One have to close eclipse in order to delete the directory.

       

      I assume that this is the cause of not being able to update the addon without exiting eclipse.

       

      Steps to reproduce:

      1. Create a UICommand, return getMetadata() with .name("Test1");
      2. addon-build-and-install
      3. test with <ctrl>-4, you should see the new command with name "Test1"
      4. change getMetadata() to .name("Test2");
      5. addon-build-and-install
      6. test with <ctrl>-4

       

      addon is gone :-)

      installed.xml still contains the addon

      class-file is updated

       

      1. stop and restart forge
      2. test with <ctrl>-4

       

      still missing

       

      1. stop and restart eclipse
      2. test with <ctrl>-4

       

      still missing

       

      1. stop eclipse
      2. remove subdirectory and modify installed.xml to remove the addon
      3. start eclipse
      4. addon-build-and-install
      5. test with <ctrl>-4

       

      addon is updated.

       

      Annoying, isn't it?

        • 1. Re: [forge-users] Unable to fully remove addon (forge 2.13.0)
          George Gastaldi Master

          Please open a JIRA with this info and we'll check it out when possible

           

           

           

          Em 23/01/2015, às 13:03, forge-users@lists.jboss.org escreveu:

           

          While developing addon's it is important to constantly redeploying the addon without changing the version number for each deploy. Currently this is not possible without closing/opening eclipse between each redeploy. After a while I found the following:

           

          When executing "addon-remove" in Eclipse Luna the specified addon gets removed in the installed.xml file in the user's .forge directory.

          The corresponding class-files in .forge directory however are still there and cannot be deleted under windows which is an indicator of an open file pointer.

           

          When stopping forge console the directory still cannot be deleted. One have to close eclipse in order to delete the directory.

           

          I assume that this is the cause of not being able to update the addon without exiting eclipse.

           

          Steps to reproduce:

          1. Create a UICommand, return getMetadata() with .name("Test1");

          2. addon-build-and-install

          3. test with <ctrl>-4, you should see the new command with name "Test1"

          4. change getMetadata() to .name("Test2");

          5. addon-build-and-install

          6. test with <ctrl>-4

           

          addon is gone

          installed.xml still contains the addon

          class-file is updated

           

          1. stop and restart forge

          2. test with <ctrl>-4

           

          still missing

           

          1. stop and restart eclipse

          2. test with <ctrl>-4

           

          still missing

           

          1. stop eclipse

          2. remove subdirectory and modify installed.xml to remove the addon

          3. start eclipse

          4. addon-build-and-install

          5. test with <ctrl>-4

           

          addon is updated.

           

          Annoying, isn't it?

           

          Posted by forums

          Original post: https://developer.jboss.org/message/916822#916822

          _______________________________________________

          forge-users mailing list

          forge-users@lists.jboss.org

          https://lists.jboss.org/mailman/listinfo/forge-users

           

          _______________________________________________

          forge-users mailing list

          forge-users@lists.jboss.org

          https://lists.jboss.org/mailman/listinfo/forge-users