> > In particular because I have seen better decomposition allowing me to > > e.g. extend the Project class and parse the project.xml myself. > > > Certainly there are side effects of the decomposition made in maven-new > which might result in such temptation to "personalize" your instance > of maven. > But if something is technicaly possible it does not necessarily mean > that it should be applied/used.
Well, we need a few features that cannot be integrated into the old maven without actually changing the whole lot, while it can be plugged in as a component easily in maven new's structure. We have got two specific requirements. One is that we cannot use the central repository, but are bound to a local FTP repository, which follows other naming conventions than the ones proposed by Maven. The other thing is dat we need to support and publish multiple target artifacts per project, and we need to be able to specify this somehow using the Project class, meaning we need to parse the project.xml file ourselves, although it is just a little extension. If you can show me how to do this with plugins in the old Maven, I would be glad to do so, but I'm afraid Maven old is just not flexible enough for our needs... Regards, Gino. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
