Comments on: Eclipse 3.6 Helios: WTP + Ivy and Deployment Assembly… Working reliably at last?

By: Ramazan Varlikli

Ramazan Varlikli — Wed, 23 Mar 2011 14:37:44 +0000

don’t know who to blame; IvyIde or WTP ? If I go to Properties->Deployment Assembly> Add, I can’t even see Referenced Projects Libraries

By: Jase

Jase — Fri, 28 Jan 2011 06:13:14 +0000

I found with Ivy that it couldn’t pull multiple dependencies from( in my case Hudson running in) winstone.
I believe the problem still exists. the solution for me was to switch Hudson to running under another container. Perhaps your issue is related, ivy failing to talk with some endpoint or other in a reliable way?

By: Lorenzo

Lorenzo — Wed, 12 Jan 2011 12:54:07 +0000

I’m sorry to say but this is where commercially developed software almost always performs better: ease of use and functionality! Although it is great what people offer to the community for free, the level of quality and integration leaves MUCH to be desired. Eclipse is sooo buggy and unstable and all these kinds of “little” problems make it that developers spend 20% of their time coding while solving IDE problems for the remainder… Now you tell me again about productivity and open source!

By: Julia

Julia — Wed, 14 Jul 2010 12:59:35 +0000

I have the same problems in Galileo and Helios. When I add, remove or modify adependency in the ivy file, this dependency is not published/unpublished in Tomcat6 and sometimes any library gets published…

In Eclipse Galileo, I had a “trick” to get my dependencies published propertly. Maybe it’s not the best way to do it but at least it works. When I add a new dependency in my ivy file I know that it’s not going to be published, so I go to my project Preferences > Java EE Module Dependencies and tick(or untick) any java project that I have in my workspace, apply changes and publish on tomcat and it works!
Somehow this action refreshes something and WTP realises that must update the dependencies.

I didn’t find a way to do a similar trick in Helios.

When I first used ivyDE I remember that all worked to me, I think that in one WTP update stopped to work but I don’t know when. Maybe it’s time to put a bug in WTP (if it is not already)

I hope you understand me, my english is not really good

By: Heinz

Heinz — Wed, 14 Jul 2010 09:15:28 +0000

When starting the server after adding new dependencies which it doesn’t find, try removing the app from the server, cleaning the server, re-adding the app. If that still doesn’t help, throw in a project close/open as well.

By: Heinz

Heinz — Tue, 13 Jul 2010 11:30:56 +0000

Blog doesn’t like XML:

handle=”module:/classpath/con/org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/? ivyXmlPath=ivy.xml&confs=build,runtime”>
consumes

By: Heinz

Heinz — Tue, 13 Jul 2010 11:29:40 +0000

Thanks for your blog entry, it helped me to find out where to add IvyDE-contributed class path entries to a WTP project in the first place.

I was unable to get it to work using ‘Referenced Projects CP Entries’ (it nevery copied any JARs), but got it to work using ‘Classpath Container’. As long as I didn’t change anything on the IvyDE container settings screen, it would let me add a new IvyDE container. The confs can then be edited manuall in .settings/org.eclipse.wst.common.component. Or just add these lines manuall to the settings file:

consumes

By: rob stryker

rob stryker — Tue, 06 Jul 2010 04:50:15 +0000

>> it appears you need to delete the container and re-add it, if you change your ivy.xml file. Rather annoying!

This may be a JDT bug, or a bug in the way WTP is dealing with JDT. I’d really need an easier use-case to investigate properly though

By: Max andersen

Max andersen — Fri, 02 Jul 2010 06:05:59 +0000

Opening a bug against wtp could help too.

We help form
The new assembly page so if that is behaving weird we can help track
Down the issue. Just needs some description on how to reproduce.