2007/4/21, Paul Benedict <[EMAIL PROTECTED]>:
I am proposing a new module for Struts 1.x called "modules" which would contain integration classes into popular open source libraries. For starters, it would contain a new command to let Spring wire up the CRP using a command.
Sorry for jumping in too late, but I think that this is not the right path to follow. I hoped that, for each integration "module" a new project is created. Since each integration project is independent from the core of Struts 1, can have its version management and its snapshot dependencies. What I mean is that releasing the Struts 1 core must not depend on the stability of its plugins/integrations. And since the Maven release plugin does not accept a snapshot dependency of any kind, this would mean that we cannot release Struts 1 until all of its integration modules reach a certain amount of stability. I am writing this because in Struts 2 there was some sort of "snapshot hell" with lots of snapshots dependencies (including Tiles 2.0-SNAPSHOT!) that were released as GA. Almost surely the Struts 2 core is GA, but at least Tiles 2 integration is not. If all integrations were projects on themselves, this would not happen. This is due probably to the fact that Struts 2 did not use the Maven release plugin, and I think that we need to use it since it forces us to follow the correct way of doing releases. Just my 2 eurocents Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
