AOP approach for NPanday 2.0

Developer
Apr 28, 2010 at 12:17 PM

* assuming we switch to Maven 3.0 for NPanday 2.0

Instead of rewriting Maven or rely on maven-plugins to be derived from we could just inject custom behaviour and configuration changes for maven using runtime AOP-configuration with Guice.

This could be used to attach config-files and pdb's before install and deploy, and also to resolve these when a dotnet-library is resolved by maven.

http://code.google.com/p/google-guice/wiki/AOP

Coordinator
Apr 28, 2010 at 2:21 PM

I don't think we should plan anything around a certain Maven adoption curve. M 3.0 is still a little while away, adoption is further away, and it's uncertain if Guice will even be present, let alone how NPanday might interact with it in that way.

I'm more interested in simplifying the NPanday code (by removing things that really aren't necessary) in a way that works with Maven 2.2 before moving to advanced features like auto-resolution of attached bits.