Community
Participate
Working Groups
Build Identifier: M20110909-1335 I have a web project which is dependent on a number of projects within the workspace. I do not have modification privileges to those projects in SVN. Cannot write Ant files for them. Do not wish to write Ant files for them. Therefore, cannot product jars for them. Cannot change them into Maven modules. I do not wish to create shadow projects for those projects - there are too many of them. Do not wish to maintain a parallel set of projects outside the policy of my organisation. I am too small a fry to dictate/change build policies in the organisation. In order to produce a war for my web project, I need the war to include classes from the projects upon which it is dependent, and package them either as jars in war's WEB-INF/lib or as compiled classes in WEB-INF/classes. Deployment Assembly does NOT allow me to specify projects it depends upon to be packaged as WEB-INF/classes in the deploy path. Deployment Assembly does allow me to specify projects it depends upon to be packaged as jars into WEB-INF/lib in the deploy path, as long as a jar is already available for each of those projects. Reproducible: Always
Moving to Java EE Tools, since this is a WAR-specific request. In order to clarify what is being requested (and this sounds like an enhancement, moreso than a defect): the projects that the WAR depends on- are they simply Java projects? (Not Utility projects) If the desire is to include simple Java projects in a WAR without modification to the Java projects, there is already an enhancement open for that. If it is something otherwise (some other project type), can you please give more details?
My apologies. This issue submission looks like I am jumping the gun. The actual misbehaviour is that Deployment Assembly keeps blanking itself out, whenever I changed the project or maven dependency, giving me the impression that Deployment Assembly is rejecting my entries. I am changing this issue to - Deployment Assembly blanks out entries whenever dependencies are altered. It should only blank out dependencies that had been removed.
It sounds like you are using the m2e-wtp plugin to help sync maven dependencies with Eclipse / WTP infrastructure. Making a change to a maven dependency (pom) will always drive changes to the WTP dependencies, and could override any custom entries yo have added.. This is how the m2e-wtp project configurator works. If you have problems expressing or maintaining dependencies via Maven or m2e - you should contact the appropriate newsgroups from that project - Thanks! I'll keep this open for a bit - please let me know if I'm miss-interpreting your issue.
Could you direct me, if you don't mind, to a file (hopefully an xml or text file rather than database entry) in workspace meta data that stores Deployment Assembly records. So that I could save them before I update dependencies. This behaviour is very frustrating as I have to key in the entries all over again after every dependency update.
Never mind. The file is org.eclipse.wst.common.component in project .settings. I simply revert from SVN after every dependency update.
Hi - Can you confirm that you are using m2e-wtp plugins? Editing the .component file directly is not recommended, and you will continue to see these problems as the pom.xml file from Maven ultimately drives changes to the deployment assembly if using m2e (m2eclipse).
OK - it sounds like you resolved your immediate issue... closing for now. If this is an issue with WTP / M2E interaction.. we are looking forward to starting work in this area soon
