- This topic has 5 replies, 2 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
Hi,
Stupid question time.
Is the feature of having sub-projects within a project a myeclipse or an eclipse concept?
And if it is both, what is the value add of the myeclipse approach?It would be an Eclipse concept, but I am not aware of Eclipse support subprojects and MyEclipse definately doesn’t support this. Did you mean *dependent* projects maybe?
@support-rkalla wrote:
It would be an Eclipse concept, but I am not aware of Eclipse support subprojects and MyEclipse definately doesn’t support this. Did you mean *dependent* projects maybe?
Yes dependent projects may work.
I have one massive project, which is split up into 3 separate teams.
I want one project to represent everything, which can contact the 3 separate projects.
The idea is that teams can work independently but may like to see what’s going, e.g. debug code, in the other projects.Or another example, suppose I want to debug hibernate source code while I write some persistence code. I was thinking of having hibernate as a sub project to my main project. As I do not want it to be part of builds, I just would like to have to be able to include it in the debugging.
Can dependent projects achieve this?
Are these projects all web projects that need to get deployed into a single EAR, or are they all totally independent web projects that don’t interact but *do* share similar libraries?
@support-rkalla wrote:
Are these projects all web projects that need to get deployed into a single EAR, or are they all totally independent web projects that don’t interact but *do* share similar libraries?
They will eventually get deployed in a single EAR, but can also work independently.
For example one project could be the business logic which depends on a persistence logic project e.g. hibernate which of course can work independently for a number of other projects.
The projects may similar jars on the classpath, e.g. junit but may also have different jars on the classpath.
