Could something clever be done - perhaps if the project.xml file contained a default maven target that tested to see if commons-build> is where project.xml expects and goes and fetches it if not? If the
fetch fails (perhaps the user is not online), then print a useful user message?
It's an interesting idea, but for all of the magic involved in this scenario I think it would be easier just to write a plugin.
If the user is not online, the Maven or Ant builds aren't going to work anyway, unless all of the dependencies are already downloaded.
It seems that the issue here can be interpreted as a simple dependency problem. All commons projects now depend on commons-build, and we all have ideas about how to manage this.
I know that Mark has said before that he didn't want to make it a plugin, but due to the current complications, it may be worth another thought.
Why invent a solution to use with Maven, or abandon Maven for source distros, instead of using one of the things that Maven does best, dependency handling? It could eliminate some work.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
