Not every problem is solved by waving the lemon of 'SOA' over it and expecting it to turn into lemonade. Some of us code things that have actual computations in them, and those computations have shared, reused classes, and those classes do not belong behind a web service -- either for performance or sheer common sense.
And the effect of this, in toto, is that it highlights some of the edges of what the maven-release-plugin is useful for. When working on the far side of those edges, it makes (to me) more sense to find another procedure than to warp the software architecture. There's a line between "the maven way" and "procrustes' bed," and that line does not necessarily pass through a point at infinity. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
