Anders Hammar wrote: > Only so that you don't forget, the general Maven rule is "one project, > one artifact". You could use classifiers to create more than one > artifact for a project, but I don't really see the benefit. Have > several projects is not bad (I think), it makes your code base > structured. Changes to one customer's code will then only affect that > customer's project and making it possible to make a new release for > just that customer. If you mix all customers' code in one project you > will get a new version for all customers (while only one of them has > really changed). Not very clean I think. > The assemblies goes in separate projects.
He can also add the assemblies to the same project, it does not make it worse than it already is - as you've explained :) - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
