Hey Carsten,
Thanks for those pointers, that is good to consider, especially for the
nature and the container. The resolveall is a bit much but would rather
just resolve that single ivy.xml file. I'm sure there is a way to pass
that to an existing handler so it only resolves one.
But in general
Hi Greg,
most of what you do with the IvyDE API can be done without the IvyDE API.
1. You can easily add the nature by using IProject.setDescription() and
providing the Ivy nature ID as a string.
2. You can add the Ivy classpath container to a project's classpath with
JavaCore.newContainerEn
Hey Nicolas,
Answers inline:
On Tue, Jul 2, 2013 at 8:34 PM, Nicolas Lalevée
wrote:
> Hi Greg,
>
> Le 2 juil. 2013 à 12:16, Greg Amerson a
> écrit :
>
> > Hello IvyDE developers,
> >
> > My name is Greg Amerson and I am the project lead for Liferay IDE, which
> is
> > a set of Eclipse plugins
Hi Greg,
Le 2 juil. 2013 à 12:16, Greg Amerson a écrit :
> Hello IvyDE developers,
>
> My name is Greg Amerson and I am the project lead for Liferay IDE, which is
> a set of Eclipse plugins for Liferay development. In an upcoming version
> of Liferay Portal, we have integrated the use of Ivy d
Hello IvyDE developers,
My name is Greg Amerson and I am the project lead for Liferay IDE, which is
a set of Eclipse plugins for Liferay development. In an upcoming version
of Liferay Portal, we have integrated the use of Ivy dependency management
for plugin projects, e.g. liferay plugins (fancy
