I'm not familiar enough with Maven's recent developments to write on this. Perhaps you could contribute? I'm also not sure how many projects there are that are currently using Maven, however, since this seems to be expanding I suspect it would be worthwhile.
Actually using Ant (or Maven) from an IDE is easy enough. The tricky bit is getting the IDE to see the same classpath that the build script uses, for code completion and the like. I noticed the Maven to Eclipse integration for example tries to work by allowing you to generate a file containing the classpath - seems like a decent approach; if all IDEs supported something like this - and Ant scripts were written to support it - life would be easy.
You might want to explain how to work with Jakarta CVS from within an IDE. I reckon it might be better to have a page per IDE, gathering together instructions, and put this on an equal footing with a page of command line instructions.Humm, its already on this page http://jakarta.apache.org/site/cvsonwin32.html for the clients but I think I'll link that more directly.
This is excellent. I'll format it into a page this evening. Thanks!
Right, I just don't know how so I left that there... I'm the worst person to write this because I've only started using an IDE again since Eclipse because I found them all unusable (or unusably slow) until now. (Eclipse just has a seriously overcomplicated UI, but it gets out of your way if you need)
How to produce a unified diff from NetBeans without dropping back to the command line is something I've never seen written down; probably because it demonstrates how much easier the command line is ;). BTW I reckon the command line for producing a patch should be on the CVS page, instead of on the page for IDE users!
Cheers, Baz PS yes, yes I know, I should have submitted all this as patches.
No worries. -Andy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
