2013/3/18 Paul Benedict <[email protected]>: > Oh, I see what you mean. Sure, why support something you already have a > replacement for? Just take it out of the build and move them to an "extras" > distribution for others to get -- they should no longer come as part of the > standard distribution.
Good point, extras is the place for them - just to remember to add a Jenkins build for them ;-) > BTW... Right now, the plugins are part of S2 release. I think if the > plugins could be independently developed and released like Maven plugins, > you would have no problem doing this. I was once against this approach > because it would be difficult to find which core and plugins were releted, > but I would like to reconsider this. Therefore, push S3 plugins into > "org.apache.struts.plugins" groupId and let them develop their own > lifecycle. Yeah... I'm wondering if this is the best option as we miss active maintainers to keep each plugin up to date with the core ;-) Also keeping dependencies in sync between plugins and the core. With the current solution all the plugins at least compile against the core. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
