[rgiudici]

So the one thing that I’ve not been able to find is how to keep all project configuration either shared with the team or in source control… The current project we work on uses the “spring capabilities” “hibernate capabilities” multiple webapps configurations, AOP, and some of the other wonders that MyEclipse provides.

My problem is that the current setup for new developers is a guide that goes step to step on where to click to “Add Spring Capabilities” “Add hibernate”, whereas I envision a situtation where the developer can just do

cvs checkout <xxxx>
and then just open the project and click run because all configuration is already on the project.

If that’s impossible, I am looking at least for a “export project configuration” and then the process would be:

check out
import project configuration
click run ….

So is this possible ?
what’s the best practice regarding having a consistent environment and project among developers ?

Appologies if this is already discussed, but searching the forums and FAQ, I did not find it.

BTW this is with MyEclipse Workbench 6.0

[Loyal Water]

rgiudici,
Have you taken a look at our Examples on Demand ? Are you looking at something like that ?

[rgiudici]

That looks about right, so I “checked out” using the menu, and then right click, run as server and I can see itrunning,as well as I can see that the menu to add struts capabilities is not there (in the example I got) so I assume the project is already struts enabled.

So two questions:
1.- how do I do to go about it ? is there a guide ? Can it be done from Source Control
2.- Does the same mechanim works for updates ? i.e. adding new libraries, removing them, adding new capabilities etc ?

Thanks

[Riyad Kalla]

rgiudici,
Actually when you share a project using the team operations in the IDE, by default I *think* it will exclude the project “dot” files (.project, .classpath, etc.) if you go to the navigator view and forcibly check those in, if anyone else on yoru team checks them out, whammo, they will be ready to rock and roll right away (just like EOD)

[rgiudici]

Perfect, that seems to be working for a new project so thanks a ton.

Now I got a new problem. The current project CVS structure is actually a few “java projects” + 3 “web projects”

So I get a structure like:

root
+–> web1
+–> web2
+–> web3
+–> java1
+–> java2
+–> java3
+–> java4

All web projects are dependent on the java1-4 projects, and when deploying and runnning I want to get all 3 webapps deployed.

Is it possible to configure it to work that way ?

[Riyad Kalla]

Because you have such a large dependency chain, what you actually have there is an enterprise project with 3 web modules and 4 supporting library modules.

Does the server you are using support EARs? (e.g. Tomcat does not support EARS)

If it doesn’t, then you need to manually deploy each web project. The deployment operation is a 1:1 map to a project, but some projects (like EARs) can be reliant on other projects, and that’s how you get “lots of stuff” deployed when you just deploy 1 project.

[Author]

Posts