1. d9c913a switch Guice from manually repackaging Guava to depending on Guava. it's still jarjar'd right now, which is causing a ~400k increase in guice-snapshot.jar. next step is to switch to ProGuard to remove the unnecessary code and cut it back down (even further?!). this will let people build from Guice source and depend directly on Guava code without having to worry about hiding internal/util. by sberlin · 13 years ago
  2. dfee9fd issue 531 -- don't let c.g.i.internal.util reference outside its package. by sberlin · 14 years ago
  3. 74d714c Issue 552: (step 1) move core code to its own subdirectory by mcculls · 14 years ago[Renamed from src/com/google/inject/internal/util/Classes.java]
  4. 9a227be Move internal utility code to separate package. by limpbizkit@gmail.com · 14 years ago[Renamed (93%) from src/com/google/inject/internal/Classes.java]
  5. 5ae41eb Post release refactor. I moved almost everything that was package-private in com.google.inject to the internal package. The motivation is to simplify things - the previous setup was extremely awkward because c.g.i could call into internal, but not the reverse. Similarly for the SPI package. by limpbizkit · 15 years ago
  6. eb06177 Stuart's fixes for the BytecodeGenTest. by limpbizkit · 16 years ago
  7. d0c4b8b Extended Binding to better support tools. Fixed bug where we were ignoring exceptions during member injection. Added TOOL stage. by crazyboblee · 17 years ago