I would just like to add my thoughts about having a build and deployment process that is IDE agnostic, and that it is in fact more possible than you might think...
In our environment we actually _dev_ on jboss/eclipse but our deployment environment is WAS. And it has worked very well for us. The developers do not change their behaviour because of this, they only in fact see jboss/eclipse. There have been a few instances where because vendors don't always follow spec and/or decide on a certain path not specified in the spec, there have been differences in behaviour between WAS and Jboss, but on the whole it has allowed us to be much more efficient and these differences have been handled. In terms of which IDE one should use, I don't think there is significant competitive advantage in using either one of Eclipse/Netbeans or IntelliJ for every day development (possibly might find that one of those IDE's is better for example, with swing/gui development). Whatever IDE you do pick however, get to know it very*well* ;-) Michael Wiles Java Developer 021 947-4695 083 652-8131 Disclaimer Sanlam Life Insurance Limited - Reg No 1998/021121/06 - Licensed Financial Services Provider Disclaimer and Directors Alternatively, send a blank email to Disclaimer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CTJUG Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/CTJUG-Forum For the ctjug home page see http://www.ctjug.org.za -~----------~----~----~----~------~----~------~--~---
