[zabo]

Hi,

I am not sure wether this is a bug, but just in case.
If you have a web module project A, depending on antoher project B (not web module), when you deploy A the code from B is not copied to the deployment dir.

Env: eclipse 2.1.1, myeclipse2.5

thanks,

[support-michael]

Auto-deployment of dependent projects is on our feature hot list. Look for it to be supported in the very soon.

Michael
MyEclipse Support

[Rob Ward]

@support wrote:

Auto-deployment of dependent projects is on our feature hot list. Look for it to be supported in the very soon.

Michael
MyEclipse Support

Thanks for the info Michael.

I was looking for a post on this issue as we ran into this as well. At first we weren’t sure whether or not we were doing something wrong!

Currently we (painstakingly :cry:) copy over the dependent classes when “necessary”.

Any estimate on the upcoming 2.5.2 date and if this is addressed in it?

—
rob

[support-michael]

Our professional services group has been beating on us for this feature as well. Dependent projects is still several weeks out. The 2.5.2 maintenance release will be out sooner than that (probably early next week).

Michael
MyEclipse Support

[Author]

Posts