For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 13 years ago by
.
-
Posts
-
Hi
We’ve recently upgraded to 10.6. As part of this, many config files have changed and we’re trying to understand the changes and to apply them properly. We have a number of projects which have dependencies. In effect something like:
– Core
— Dependent1 (needs Core)
— Dependent2 (needs Core & Dependent1)
—- Web (needs Core, Dependent1, Dependent2)In the Web project, the classpath references the projects like so:
<classpathentry combineaccessrules="false" kind="src" path="/Core"/>We are using Maven and the POM files reference their ‘parent’ projects too (referring to their SNAPSHOT repository versions).
This all seems to be working with hot deployment (into a Tomcat server config), but we’ve now got a ‘new’ config file “org.eclipse.wst.common.component”.
This has within in ‘dependent-module’s which seem to replicate the above classpath and Maven directives. These also refer to SNAPSHOT jars which get deployed to the remote WEB-INF lib directory.
So, my questions are:
1) Is org.eclipse.wst.common.component & dependent-modules necessary? This is a config file that we don’t really want to update with each version.
2) If so. Is there any way of using a generic “bundling” so that this does not need updating?
3) Is this the right way to handle dependent projects?Regards
Matt
Hi optimad!
I assume you are using Maven as your dependency manager. First of all, you should update project’s configuration according to your pom.xml, if you haven’t done it already: right click on the project -> Maven4Eclipse -> Update Project.
Going back to your questions:
1. Is org.eclipse.wst.common.component & dependent-modules necessary? This is a config file that we don’t really want to update with each version.
It is necessary for Maven projects. Make sure all your Maven projects use Deployment Assembly. Select project, right click -> Properties -> MyEclipse -> Deployment Assembly. “Use Deployment Assembly” should be checked.
2. If so. Is there any way of using a generic “bundling” so that this does not need updating?
In Deployment Assembly, there should be mappings for source folders and Maven Dependencies container only. Assuming Maven Dependencies container is providing all dependencies, you can remove any other jars, thus you would get “generic” solution.
(If you have any doubts, please send me a screenshot of Deployment Assembly page for your project)
