[Frits Jalvingh]

Using 3.8.2 with Eclipse 3.0.1 with the Resin 3 appserver.

I have a project which uses (a lot of) dependent projects (libraries and stuff). I noticed that MyEclipse failed to (re)deploy many of the dependent projects.

I have played with the settings in preferences->MyEclipse -> J2EE project -> Web Project Deployment; I want to use smart deployment but I tried “always JAR” too.

What I saw was that for some dependent project a {project name}_bin.jar was generated in WEB-INF/lib, but for some other projects it was not. I could not get MyEclipse to properly generate the missing jars (or the missing classes in WEB-INF/classes when using smart deploy), not even using redeploy, or a rebuild all, or a delete deployment and recreate etc.

But I noticed something else: in the “manage deployments” dialog the resin 3 deployment for my project often had a warning sign with the notice that the “bin” directory for a dependent project was missing (failed to remove deployment). This message occurs when a project consists of jar files only, and has no source path defined, and so no bin directory is created (or it is empty).

By creating the bin directory for jar-only projects AND by placing a dummy file in it the warning sign disappears.

As a side effect the deployment then works also: it now generates the rest of the dependent projects.

So the problems seem to be:
– When a dependent project has no bin directory, even when it has no source directory specified, MyEclipse reports an error which is wrong.
– Worse is that when the list of dependent project is traversed for (re)deployment the first error encountered causes the process to silently fail, without any message, leaving an incomplete deployment (and a baffled user 😉

IMO MyEclipse should ONLY complain if a dependent project has a source folder but no classes in the bin folder; and if an error is encountered during redeployment it should at least give a message…

[Scott Anderson]

Thanks for posting this. We’re greatly expanding our support for dependent projects in the upcoming 3.8.3 release. To make sure we covered these I ran a few tests on the internal build and this is what I found.

– When a dependent project has no bin directory, even when it has no source directory specified, MyEclipse reports an error which is wrong.

This no longer happens. Projects containing only libs can now be set up so that their exported libraries are packaged properly in both exploded and packaged deployments.

– Worse is that when the list of dependent project is traversed for (re)deployment the first error encountered causes the process to silently fail, without any message, leaving an incomplete deployment (and a baffled user 😉

IMO MyEclipse should ONLY complain if a dependent project has a source folder but no classes in the bin folder; and if an error is encountered during redeployment it should at least give a message…

Agreed. Error handling has been enhanced and more cases are now handled without error. From what I can see, I think 3.8.3 (in early December) will resolve the issues you’re seeing. Thanks for your patience.

[Frits Jalvingh]

Great 😉

[Frits Jalvingh]

Hello,
I just started to use MyEclipse again and installed 3.8.4. But sadly it has exactly the same problem as described in the above post. So I’m still not able to deploy projects unless I create ‘bin’ directories in them manually which is a pain in the – ehh – you know.

[Author]

Posts