Hi. This may seem a little obvious to most...... but...... I've had a lot of trouble finding what makes a good "module". I'm new to Ivy and implementing it accross a quite large group of java projects, (and 3rd party softwares, config files, media files etc...). This is an excellent opportunity to do it correctly from scratch.
I've not been able to really understand what constitutes a "module" that ivy describes in a ivy.xml file. Which of these should have their own (unique) ivy file. :rules: java class java package java project source file scripts jar file 3rd party jar file 3rd party s/w (ie. media player) configuration file (property files included or data files) system folders (ie \src or \doc) thanks in advance. Best Regards, Patrick p.s. this post should really be in ivy-user..... my apologies for this. I will post it there now. -- View this message in context: http://www.nabble.com/Module-definition...-an-*easy*-question--tf4323260.html#a12311353 Sent from the ivy-dev mailing list archive at Nabble.com.
