- This topic has 3 replies, 2 voices, and was last updated 19 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
brentruddMemberIn the forums, I have seen some discussion about inter-project dependency. Specifically, I am looking for the ability to create a web project name project_A. project_A is a generic foundation to build other web applications. project_B is built off of project_A (or has a dependency on project_A) and project_B contains jsp includes and file includes from project_A. What future release will (if any) will support the deployment of project_B with dependent projects and does cross/dependent validation, debugging, and general JSP development features?
Thanks in advance.
Riyad KallaMemberbrent,
We support making Java Projecte dependent as libraries, but there is no support for making 2 web projects reliant on eachother and supporting deployment of them. How would we be able to determine which web.xml file to use? The one from projectA or B? Which struts-config.xml (if any) or other descriptor file do we use if there is a conflict? What do we do about /lib or /classes conflicts? What about JSP pages with the same names?These are all problems/reasons that we don’t have planned support for this type of development/deployment. If you can provide a convincing use case that other users think will be helpful, I”m sure we can do something to acommodate your development model though.
brentruddMemberRiyad,
I would approach it as follows:
Project dependencies can not be circular. Meaning, project_A can not reference files .jsp, .properites, .config, etc of project_B if project_B is referencing files in project_A. Next, apply the concept of filters. For example, if project_B references project_A and both projects have the same directory structure and file name then project_B’s files takes presidents over project_A’s files. This concept would apply to team share, error checking and deployment.
What are our thoughts and other concerns?
Riyad KallaMemberSounds reasonable to me. How we would proceed from here is either to get enough interest from users to implement this functionality or have a company willing to purchase enough licenses to justify this enhancement.
From our perspective, we want to implement all good ideas and have the ultimate flexibility… but we are a business. We need to prioritize, and when faced with 100 things on our todo list we need some metric for bumping things to the top of the list and that is metric is either user interest or company interest.
Also we are always happy to work with authors that implement functionality as external plugins and wish to work with or donate the code to MyEclipse.
-
AuthorPosts