[QAS]

hi,

i have 3 projects; 1 java project and 2 web projects which i will call a, b and c respectively.

the web projects b and c both need to include classes from a. i have achieved this by adding project a to the project references section of the java build path.

the issue i face now, is that project c needs to include classes from project a AND project b (as well as it’s own). i add both a and b as project references.

my understanding of the myeclipse-web web project dependent project deployment policy, specifically the use smart deployment option, is that when i deploy my project c, it’s classes should be populated with the merged classes from a, b and c.

what i get is classes from a and c only, and no b.

the package hierarchy for the projects is as follows;

a) com.my.company.a
b) com.my.company.parent.b
c) com.my.company.parent.c

i am using MYIDE 5.0 M2 but this problem is also in 4.

consequently, i am having to define a JAR export in project b to get it into the lib of project c but it’s really nasty doing so, especially when smart deploy appears to partially work.

am i missing something extra to get a, b and c classes into one deployed classes folder?

many thanks

[Riyad Kalla]

The problem is that the deployment rules only apply to Java projects, not Web projects. There is no support for dependent web projects. We do have a pending request to add it, and I have added your comments to it.

[QAS]

Would it be premature to ask when this feature may be added?

Otherwise I think we’ll need to rip out all our web project SRC into pure java projects which is a little messy to get around this issue. Would it also be simplistic of me to assume that dependent web project classes support is pretty much the same as pure java and so relatively simple to achieve?

[Riyad Kalla]

I added your comments to the request, and the problem is that it’s not just web-project-class support, we have had users requesting dependent web proejct deployments before where MyEclipse merges the projects together including web content. The handful of times (2) we have quickly added “simple features” so one or two users could be happy, we ended up regretting it and had to rip it out, because it ended up becomming bugs for other users that didn’t want it.

So no, no feature is as simple as you would hope, but the feature you are requesting is being discussed and hopefully addressed in a future release. I’m sorry about that, but we need to stay methodical about our chances so the product doesn’t suffer.

[Author]

Posts