Hi Ernest, I agree with your assessment that this is messy stuff... At the risk of complicating it even further, it might be useful to review the "Flexible Project Structure" being developed as part of the Eclipse Web Tools project (see design documents at http://www.eclipse.org/webtools/development/proposals/index.html). I have not followed this work in detail, but watch the messages on the wtp-dev mail list.
There has been some discussion about folding this design back into the Eclipse platform in a later release. Its motivation here is to deal with different strategies for organizing projects, dependencies, and libraries in J2EE development. E.g. one project containing both tomcat web folder with JSP pages + the Java code for servlets, or allowing developers to break this into two projects. The goal is to allow config flexibility for either. The initial proposal came out of IBM's experience with WebSphere development, then recently BEA suggested some adjustments. I have not followed the detailed designs, but the folks involved seem to feel it is maturing nicely. Hope this helps! Dave Carlson > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Tuesday, June 07, 2005 2:18 PM > To: jess-users@sandia.gov > Subject: Re: JESS: Using relative paths with require* > > > I think Greenblatt, Howard wrote: > > > > > > Am I doing something fundamentally wrong here? > > > > Nope, you're just in the right place at the wrong time... :) > > Eclipse's notion of a workspace with build paths and source > directories and exporting runtime packages, etc, blah, blah, blah, is > messy stuff. This is the only part of Eclipse I'm truly unhappy > with. People who are used to heavyweight IDEs are likely to not > understand what I'm talking about; people who've used something like > IntelliJ IDEA probably understand. > > The problem here, anyway, is that the JessDE hasn't 100% nailed down > how it's going to use these concepts. I wanted to do this without > restricting how you could lay out projects, but it's really looking > like Eclipse forces you to embrace its way of thinking. > > One solution that lets you use just "(require my-templates)" and > everything works at both edit-time and runtime is to make "rules" an > Eclipse "Source Folder." This lets you store the clp files in the > "rules" folder in your project, but the rules folder will disappear in > the deployed app, and the two files will be able to find each other. > > The JessDE should eventually be smart enough to help you get > everything set up appropriately and explain any problems. > > > > --------------------------------------------------------- > Ernest Friedman-Hill > Advanced Software Research Phone: (925) 294-2154 > Sandia National Labs FAX: (925) 294-2234 > PO Box 969, MS 9012 [EMAIL PROTECTED] > Livermore, CA 94550 http://herzberg.ca.sandia.gov > > -------------------------------------------------------------------- > To unsubscribe, send the words 'unsubscribe jess-users > [EMAIL PROTECTED]' > in the BODY of a message to [EMAIL PROTECTED], NOT to the list > (use your own address!) List problems? Notify > [EMAIL PROTECTED] > -------------------------------------------------------------------- > > -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
