Hi Naci,
Thanks for the feedback,
In regards to dependencies outside the workspace. We can do this now for utility jars. The "J2EE Module dependencies" page offers this option under "EAR Modules" and "Web libraries".
The buttons "Add External jar" and "Add Variable" will settup classpath entries for these jars, and the variable can be used for team sharing scenarios.
If a single shared folder is the requirment, resource linking could be used here, as it doesn't require the folder to be managed by the workspace, just a path to the filesystem.
I'm not sure I completely follow your second scenario. Are you describing multiple dependencies? such as an Web project depending on another war, that depends on a util jar? The util jar should be on the
original Web projects classpath. If not, its a bug. Maybe you can elaborate on this scenario?
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: [EMAIL PROTECTED]
Phone: 919-254-1848 (T/L: 444)
| Naci Dai <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 09/19/2005 01:11 PM
|
|
Chuck,
Thank you for the detailed description. I appreciate the effort to be as inclusive as possible to as many different project scenarios. The concept of a "web source" source folder is a good one, and it is conceptually similar to jdt so this it is also good for usability.
There is one point that was not very clear to me. Can you also comment on how flexible projects propose to manage "web libraries" (i.e jars in web-inf/lib ). I would like to hear your comments on two issues. First, there is a good level of interest in being able to refer to out-of-workspace repositories for libraries. For example, struts, and spring libraries can be stored in a different folder and can be shared by many web applications. More specifically, I am looking for a maven-like library/classpath resolution. I think maven has it right when it comes to managing library dependencies.
Second, I would like to be able to manage web-inf/lib as a library entry to be used in project build-paths. For example, if I have a web module, the libraries that the web module contributes to the project build-path (i.e web-inf/lib and web-inf/classes) should be an entity that is usable by the developer in other project and editable by the developer (relates to my first question). The scenario where this is useful is when a module is split into a set of projects.
everyone,
I have added some additional details, and two additional scenarios to demonstrate the differences between our current support , and the proposals in our WTP 1.5 timeframe.
http://www.eclipse.org/webtools/jst/components/j2ee/proposals/WTPFlexibleProjectProposals.html
It must be understood that our current support will remain through WTP 1.0, and existing metadata/structure will be migated to any new format/proposal in future releases.
Please respond with your feedback by September 27, we will be making some decisions on this topic soon.
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email: [EMAIL PROTECTED]
Phone: 919-254-1848 (T/L: 444)
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
--
Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com/
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
