Hi,
         
        I’ve currently
            set the ModelExplorer dependency to Guava 10 or 11
            (Excluding 12). So far, so good, but it might be better for
            the long term to remove all usages of
            deprecated/experimental Guava APIs, and relax the dependency
            constraints, especially since many plug-ins actually declare
            Guava-based APIs.
         
        I’ve also
            removed all dependencies to the old
            com.google.collect/com.google.inject and replaced them with
            Guava.
         
        Regards,
            Camille
        
         
        
         
        Hi Camille
          
          I just checked a new M3 installation.
          
          MWE contributes Guava 10, then Xpand/Xtend and Xtext are
          happy.
          
          So maybe enforcing 10 for a while may be ok.
          
              Regards
          
                  Ed
          
          On 14/11/2013 10:46, LETAVERNIER Camille wrote: 
        Hi Ed,
        
            
            
          
        Well, I don’t
            really have any better solution. Guava APIs move really
            fast, which makes it difficult to actually fix the issues
            (And the sources don’t seem to be included in Orbit). I
            don’t really feel like exploring new Guava APIs every 6
            months to find the replacement for each deprecated method.
         
        Soft
            dependencies are not a solution either, because it will just
            not work on Guava >= 11.0.x (The method doesn’t exist
            anymore).
         
        As we don’t
            reexport the Guava dependency, and probably don’t expose it
            too much to the outside, I have the feeling that
            explicit/restricted dependencies is the best (only?) way to
            go.
         
         
        Camille
        
         
        
         
        Hi Camille
          
          Explicit bounds creates significant hazards that users who
          install Papyrus and something else will have an exciting time.
          
          I hope the use of explicit bounds in Papyrus will be
          prohibited from at least M6 inwards.
          
          NB Guava 12 is Java 6  and Luna is unuseable on Java 5 so
          installing Guava 11 may not be practical with DI and other
          clever facilities.
          
              Regards
          
                  Ed Willink
          
          
          On 14/11/2013 10:01, LETAVERNIER Camille wrote: 
        Use an explicit dependency to
            Guava [10.0.0, 11.0.0) (i.e. excluding Guava >= 11.0.0)
          
         
         
        
            
            
            
        _______________________________________________
        mdt-papyrus.dev mailing list
        mdt-papyrus.dev@xxxxxxxxxxx
        https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
        
            
            
            
        No virus found in this
            message.
            Checked by AVG - www.avg.com
            Version: 2014.0.4158 / Virus Database: 3629/6822 - Release
            Date: 11/09/13