Noel J. Bergman ha scritto: > Stefano Bagnara wrote: > >> I'm +1 to remove mordred at all in trunk (after tagging because before >> this change trunk is backward compatible to 2.3.1, instead after this >> change we are no more 100% compatible). > > How do you figure? Trunk is not compatible with 2.3.x due to the changes in > the deployment descriptor. And that's the only change here. Someone would > need to replace a single token in the configuration file. There is no code > level issue.
Current "compatibility" between 2.3.1 and trunk is defined as: storage compatibility + config.xml compatibility. This mean that we tried to have james trunk working "as is" with a 2.3.1 config.xml We never declared compatibility at code level for trunk vs v2.3. > I'm not sure that we have any need for a tag. If someone needs mordred, it > exists in other tags and branches essentially unchanged from its current > state. The only difference is the removal of the JDBC 3 comments. The tag is not about mordred but about config.xml + storage compatibility between trunk and v2.3. Btw I don't care too much about this. I remember what is the release that break that compatibility. I just think it is a good practice to tag source tree before breaking compatibility. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
