The thing is though is that for those of us who do use eclipse, ivyDE is available, and therefore we naturally want to use it. I checked my inbox for emails on this ivy-user list, I have 517 conversations, with about 90 conversations about ivyDE (about 17%), so clearly there are a lot of people who are or want to use it.
On Jan 17, 2008 5:49 PM, Niklas Matthies <[EMAIL PROTECTED]> wrote: > On Thu 2008-01-17 at 08:24h, Xavier Hanin wrote on ivy-user: > > On Jan 17, 2008 2:39 AM, John Gill <[EMAIL PROTECTED]> wrote: > > > > > I've said this before, but I'll say it again. ivyDE is what makes ivy > a > > > killer tool IMHO. > > > > I don't share your opinion, but I understand. IMO Ivy shines by its > > flexibility and predictability. Ivy+IvyDE is a very good combination, > but > > you have pretty similar eclipse plugin for maven and this doesn't make > me > > love maven. > > Also, not everyone is using Eclipse. There's NetBeans, IntelliJ and > JDeveloper too, for example. One good thing about Ivy is that it's not > IDE-bound. At our company, anyone can use their favorite IDE on the > same shared project with no problems. I'd rather have the development > effort concentrate on Ivy itself than on a plugin for a particular IDE. > > Just my two cents, > > -- Niklas Matthies > -- Regards, John Gill
