5 Replies Latest reply on Sep 20, 2010 1:31 PM by dgolovin

    update from jbt 3.2 m1 to m2

    nimo22

      I want to update from jbt 3.2 m1 to milestone 2 (with eclipse helios). I installed M1 via Update Site within eclipse.

       

      Is it enough to go to "help->check for updates" to update from m1 to m2?

       

      Or should I remove m1 completely and make a new install of m2 ?

        • 1. Re: update from jbt 3.2 m1 to m2
          maxandersen

          We don't guarantee Milestones upgrades are smooth, but it *should* work.

          • 2. Re: update from jbt 3.2 m1 to m2
            nimo22

            Okay thanks. I have done it and it works.

             

            By the way, my plugin-directory also contains the jars of the old version (m1). Is there a way to configure eclipse to switch to different versions?

             

            For example, in Mavens pom.xml, I can declare which version of a dependency I want to use. Is there a way to do that in eclipse? Would be really cool, if the plugin-directory is handled as a repo for eclipse the same as mavens repo.

            • 3. Re: update from jbt 3.2 m1 to m2
              maxandersen

              it kinda is since its P2 that resolves against that repository.

               

              I believe in recent eclipses P2 will prune the repo once in a while to not leave "garbage" around.

               

              You can go back and forth between installations by the Installation history in eclipse.

              • 4. Re: update from jbt 3.2 m1 to m2
                dgolovin

                Max Andersen wrote:

                 

                You can go back and forth between installations by the Installation history in eclipse.

                It works only if eclipse have access to plug-in with version saved in history and can install it from update site. It is not working for JBT because we have only most recent version available through update site. It means update M1->M2 works, but to be able to restore M1 you need update site for it to be available in eclipse.

                • 5. Re: update from jbt 3.2 m1 to m2
                  dgolovin

                  I guess we can use Composite Repository to keep all versions available in development update site. It should be declared in compositeContent.xml and contain two links to M1 and M2 release. Below is example from Eclipse documentation

                  <?xml version='1.0' encoding='UTF-8'?>
                  <?compositeMetadataRepository version='1.0.0'?>
                  <repository name='"Eclipse Project Test Site"'
                      type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
                      version='1.0.0'>
                    <properties size='1'>
                      <property name='p2.timestamp' value='1243822502499'/>
                    </properties>
                    <children size='2'>
                      <child location='http://example.eclipse.org/childOne'/>
                      <child location='http://example.eclipse.org/childTwo'/>
                    </children>
                  </repository>