>> Regarding "writing your own build tool" -- I think this is probably a >> bad idea, but of course, you are welcome to disagree. If you have >> decided to abandon Maven, perhaps take a look at "buildr" and other >> tools (you already mentioned ivy) that have taken ideas from Maven and >> incorporated the Central repository as a source of dependency >> artifacts etc.
Of course, you can stick with Maven where it works and then invoke ant for those areas that maven doesn't yet support (or do well). E.g. the signing of artifacts in a specified order should be a simple thing for ant to do. For jars that are not in the repository you could store them in the projects lib/ directory and define a system scope with corresponding systemPath. This practice is discouraged and you would be better off to submit the artifact for inclusion on the central repository and/or convince the project maintainers to do this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
