Re: Eclipse and forrest.
Sorry, my focus has changed considerably since making a couple of promises here. I still have this on my todo list, but it's not right at the top right now (although it is rising again). With respect to Ivy + Eclipse specifically you need IvyDE, see the Ivy site. Ross On 24/06/07, Gav [EMAIL PROTECTED] wrote: -Original Message- From: Brian M Dube [mailto:[EMAIL PROTECTED] Sent: Sunday, 24 June 2007 4:38 AM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 April 2007 8:42 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. I'm going to have to come back to you on this. I'll set up my eclipse from scratch and take notes. You can then work through those notes and turn them into a clearer doc. Ross Thanks Ross, jeez, didn't mean to put you to all this effort :( I have also been taking notes on what I have been doing, and looking where other docs are within forrest. I'm sure your notes will be more accurate. Hopefully once the docs up, someone will be able to test drive it for us. Did this document happen? The question is not meant to be pushy, it's just that I'm still trying to catch up after moving house and I would have easily missed it. I didn't get any useful results by creating a project based on trunk, regardless of the workspace location. I'm trying to achieve a useful setup for Forrest plugin development that makes use of Ivy. With all of trunk as one project, it seemed that my whiteboard plugin's Ivy details are lost. Yesterday I had it set up so that the plugin in question was a standalone project, and Ivy worked this way. I've made some changes today and I can't recreate the working configuration from yesterday. Does anyone else use Eclipse specifically for Forrest plugins? Brian Hi Brian, I have some notes I wrote down gleaned from what Ross has explained on list. However I never got it working successfully, the main problem being I guess is that I am a noob where Eclipse is concerned and don't really know how to use it. I spent a fair amount of time trying to get it to work without success and was not getting much work done, so have delayed trying to get it to work for a while so I can move forward a bit. I will try again at some point but wont be for a while. Gav... -- -- Ross Gardler OSS Watch - awareness and understanding of open source software development and use in education http://www.oss-watch.ac.uk
Re: Eclipse and forrest.
Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 April 2007 8:42 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. I'm going to have to come back to you on this. I'll set up my eclipse from scratch and take notes. You can then work through those notes and turn them into a clearer doc. Ross Thanks Ross, jeez, didn't mean to put you to all this effort :( I have also been taking notes on what I have been doing, and looking where other docs are within forrest. I'm sure your notes will be more accurate. Hopefully once the docs up, someone will be able to test drive it for us. Did this document happen? The question is not meant to be pushy, it's just that I'm still trying to catch up after moving house and I would have easily missed it. I didn't get any useful results by creating a project based on trunk, regardless of the workspace location. I'm trying to achieve a useful setup for Forrest plugin development that makes use of Ivy. With all of trunk as one project, it seemed that my whiteboard plugin's Ivy details are lost. Yesterday I had it set up so that the plugin in question was a standalone project, and Ivy worked this way. I've made some changes today and I can't recreate the working configuration from yesterday. Does anyone else use Eclipse specifically for Forrest plugins? Brian
Re: Eclipse and forrest.
Gav... wrote: quote who=David Crossley Gav wrote: Yes, I will gladly do a document on getting eclipse installed and forrest installed into that. there are some docs around already that I have been looking at, so can amalgamate/update those. Great stuff. These gems are helping us all. As before, please focus on the Forrest-specific bits and keep documentation about supporting products to a minimum. We don't have the people-power to maintain such. No problem there, however I will unfortunatly have more questions, for instance I have now installed forrest-trunk into the eclipse workspace from svn and get 77 errors and many warnings before I even get to do anything. We need things like this cleared up for the docs also. You don't need to do anything with the warnings - they are warnings. The errors? I have 18 errors on Forrest trunk, all of them to do with Eclipses incorrect handling of imports in ANT build files. They look like this: Target ensure-nocontent does not exist in this project The other errors you have are to do with your configuration of the workspace. Have you added the jars to the build path? (right click on all the jars and select build path... - add to build path) If that's not your problem then lets start working through your errors by posting them up here. Ross
RE: Eclipse and forrest.
-Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 April 2007 4:22 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav... wrote: quote who=David Crossley Gav wrote: Yes, I will gladly do a document on getting eclipse installed and forrest installed into that. there are some docs around already that I have been looking at, so can amalgamate/update those. Great stuff. These gems are helping us all. As before, please focus on the Forrest-specific bits and keep documentation about supporting products to a minimum. We don't have the people-power to maintain such. No problem there, however I will unfortunatly have more questions, for instance I have now installed forrest-trunk into the eclipse workspace from svn and get 77 errors and many warnings before I even get to do anything. We need things like this cleared up for the docs also. You don't need to do anything with the warnings - they are warnings. The errors? I have 18 errors on Forrest trunk, all of them to do with Eclipses incorrect handling of imports in ANT build files. They look like this: Target ensure-nocontent does not exist in this project The other errors you have are to do with your configuration of the workspace. Have you added the jars to the build path? (right click on all the jars and select build path... - add to build path) Ok thanks, yes that seems to be most of my troubles. I have added all jar files from lib.core, lib-endorsed and lib.optional with the exception of one... With all jars but one I am now down to 2 errors and no warnings. The errors are :- 1. The project was not built since its build path is incomplete. Cannot find the class file for org.apache.xerces.xni.parser.XMLInputSource. Fix the build path then try building this project. 2. The type org.apache.xerces.xni.parser.XMLInputSource cannot be resolved. It is indirectly referenced from required .class files forrest_trunk/main/java/org/apache/forrest/sourcetype SourceTypeAction.java line 1 Obviously both are related to each other and also both are related to the missing jar file which is :- xercesImpl-2.8.0.jar So I know the two errors will go away when I add it to the build path. Unfortunatly when I do my errors increase from 2 to 3940 !! :( I can only see so far the first 100 errors which I have attached. A summary of which is , All errors end with '...cannot be resolved to a type' The ones I can see are in Whiteboard or tools/eclipse. If that's not your problem then lets start working through your errors by posting them up here. Thanks, hope I'm not too much trouble. Gav... Ross -- Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33 PM Severity and DescriptionPathResourceLocation Creation Time Id _a cannot be resolved forrest_trunk/whiteboard/forrestdoc/src/test/resources/javasrc/packB Bone.java line 27 1176896283140 62914 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core Controller.java line 2031176896284375 64082 The field Priority.DEBUG is deprecated forrest_trunk/tools/forrestbot/webapp/src/java/org/apache/forrest/forrestbot/webapp/util Executor.java line 84 1176896284500 64382 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core Controller.java line 2141176896284375 64084 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core Controller.java line 2181176896284375 64088 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core Controller.java line 2201176896284375 64089 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core IController.javaline 42 1176896284343 64007 AbstractInputPlugin cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/test/org/apache/forrest/test/core/plugins/input HelloWorldInputPlugin.java line 30 1176896284015 63700 AbstractMatcher cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core/locationMap AbstractSourceNode.java line 1231176896284218 63974 AbstractMatcher cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core/locationMap LocationNode.java line 41 1176896284187 63954 AbstractMatcher cannot be resolved to a type forrest_trunk/whiteboard/forrest2/core/src/core/org/apache/forrest/core/locationMap LocationNode.java line 45
Re: Eclipse and forrest.
I'm going to have to come back to you on this. I'll set up my eclipse from scratch and take notes. You can then work through those notes and turn them into a clearer doc. Ross
RE: Eclipse and forrest.
-Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 April 2007 8:42 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. I'm going to have to come back to you on this. I'll set up my eclipse from scratch and take notes. You can then work through those notes and turn them into a clearer doc. Ross Thanks Ross, jeez, didn't mean to put you to all this effort :( I have also been taking notes on what I have been doing, and looking where other docs are within forrest. I'm sure your notes will be more accurate. Hopefully once the docs up, someone will be able to test drive it for us. Gav... -- Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33 PM
Re: Eclipse and forrest.
Ross Gardler wrote: Gav wrote: 2. Do you use the subclipse plugin to use SVN, if not, how do you keep Eclipse upto date with trunk. Subclipse is OK for updating from SVN, but I don't like it for committing changes. It seems to get all tied up in knots far too often and the GUI makes it too easy to make mistakes. I use subclipse to update and for working with diffs, but I've switched back to using the command line for committing. Yes, GUIs seem to be too dangerous. I love the command-line for committing. I don't provide a message. This deliberately open my text editor where i can create/paste my message. Importantly this enables me to simply quit the editor without writing, which enables me to abort the commit. It is incredible how often i use that feature. The act of committing seems to make one think more about the consequences. -David
RE: Eclipse and forrest.
-Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 April 2007 7:33 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav wrote: I downloaded the latest Eclipse all-in-one package [1] that contains everything we need. ... 1. Workspace, do you point to the forrest trunk as your workspace or somewhere standalone. That's up to you. I'll tell you my setup - that works for me. I have all public source code in: ~/projects Inside there I have loads of project folders, the forrest ones are: ~/project/forrest-trunk ~/project/forrest-ivy-branch ~/project/apache-forrest-0.8 My eclipse workbench is set at ~/project I then use working sets to narrow down the projects I see at any one time (see eclipse help docs for that, but if you only have a handful of projects then you don't need to worry about it). If you already have the sources checked out into your workbench folder then simply create a new project in your workbench and give the new project the same name as the existing folder, i.e. forrest-trunk. Eclipse will spot there is already src here and work through an import wizard with your. I did point to my working trunk which I use with SVN, I didn't like the fact that eclipse then created a few more folders of its own inside my forrest SVN tree, could get messy. I'd rather not have versioned/unversioned stuff mixed up like that. This was the main reason for this question, thought I'd messed it up big time. The confusing thing for me then is, how do I work on trunk and debug it and update it etc whilst the workspace is pointing somewhere else, or is this a RTFM concidering I only installed it today? (I'm impatient, but that's hardly your problem). Or maybe, I do need this mixture of svn trunk and eclipse ? 2. Do you use the subclipse plugin to use SVN, if not, how do you keep Eclipse upto date with trunk. Subclipse is OK for updating from SVN, but I don't like it for committing changes. It seems to get all tied up in knots far too often and the GUI makes it too easy to make mistakes. I use subclipse to update and for working with diffs, but I've switched back to using the command line for committing. Thanks, makes sense. 3. Do you use it without the forrest eclipse plugin to debug work with forrest or with -- as far as I can see the forrest plugin only does a few simple actions -- but then I still haven't got that part working yet. No. The eclipse plugin is unmaintained and the project I created it for is now dead (well, they claim to be active but there has been no public activity for years). I have plans in this direction, but that is for post release discussion. Ok, so forget the Eclipse forrest plugin for now then, no problem. 4. Do you build your projects using eclipse. No, I use the command line for that, you could though. If you promise to document this (however roughly), I promise to carry on asking your questions. Thanks Ross, very much appreciated (and somehow knew it would be you yet again to answer my questions) Yes, I will gladly do a document on getting eclipse installed and forrest installed into that. there are some docs around already that I have been looking at, so can amalgamate/update those. Gav... Ross [1] - http://download.eclipse.org/webtools/downloads/drops/R1.5/R-1.5.3- 2007020820 48/ -- Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33 PM
Re: Eclipse and forrest.
Gav wrote: I downloaded the latest Eclipse all-in-one package [1] that contains everything we need. ... 1. Workspace, do you point to the forrest trunk as your workspace or somewhere standalone. That's up to you. I'll tell you my setup - that works for me. I have all public source code in: ~/projects Inside there I have loads of project folders, the forrest ones are: ~/project/forrest-trunk ~/project/forrest-ivy-branch ~/project/apache-forrest-0.8 My eclipse workbench is set at ~/project I then use working sets to narrow down the projects I see at any one time (see eclipse help docs for that, but if you only have a handful of projects then you don't need to worry about it). If you already have the sources checked out into your workbench folder then simply create a new project in your workbench and give the new project the same name as the existing folder, i.e. forrest-trunk. Eclipse will spot there is already src here and work through an import wizard with your. 2. Do you use the subclipse plugin to use SVN, if not, how do you keep Eclipse upto date with trunk. Subclipse is OK for updating from SVN, but I don't like it for committing changes. It seems to get all tied up in knots far too often and the GUI makes it too easy to make mistakes. I use subclipse to update and for working with diffs, but I've switched back to using the command line for committing. 3. Do you use it without the forrest eclipse plugin to debug work with forrest or with -- as far as I can see the forrest plugin only does a few simple actions -- but then I still haven't got that part working yet. No. The eclipse plugin is unmaintained and the project I created it for is now dead (well, they claim to be active but there has been no public activity for years). I have plans in this direction, but that is for post release discussion. 4. Do you build your projects using eclipse. No, I use the command line for that, you could though. If you promise to document this (however roughly), I promise to carry on asking your questions. Ross [1] - http://download.eclipse.org/webtools/downloads/drops/R1.5/R-1.5.3-2007020820 48/
Re: Eclipse and forrest.
Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 April 2007 7:33 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav wrote: I downloaded the latest Eclipse all-in-one package [1] that contains everything we need. ... 1. Workspace, do you point to the forrest trunk as your workspace or somewhere standalone. That's up to you. I'll tell you my setup - that works for me. I have all public source code in: ~/projects Inside there I have loads of project folders, the forrest ones are: ~/project/forrest-trunk ~/project/forrest-ivy-branch ~/project/apache-forrest-0.8 My eclipse workbench is set at ~/project I then use working sets to narrow down the projects I see at any one time (see eclipse help docs for that, but if you only have a handful of projects then you don't need to worry about it). If you already have the sources checked out into your workbench folder then simply create a new project in your workbench and give the new project the same name as the existing folder, i.e. forrest-trunk. Eclipse will spot there is already src here and work through an import wizard with your. I did point to my working trunk which I use with SVN, I didn't like the fact that eclipse then created a few more folders of its own inside my forrest SVN tree, could get messy. I'd rather not have versioned/unversioned stuff mixed up like that. This was the main reason for this question, thought I'd messed it up big time. Your working directory should not be your trunk checkout. If you set it up the way I suggested where (in my case) ~/project is the working directory and ~/project/forrest-trunk is the forrest project directory there is only one eclipse specific file to be created (.project) and you'll find this is already in svn:ignore The confusing thing for me then is, how do I work on trunk and debug it and update it etc whilst the workspace is pointing somewhere else, or is this a RTFM concidering I only installed it today? (I'm impatient, but that's hardly your problem). Or maybe, I do need this mixture of svn trunk and eclipse ? The eclipse workspace does not map to each project. The workspace is a collection of all projects you want to work with in eclipse. This is getting off topic for this list, if you need to know more about the specifics of eclipse workspaces see the eclipse docs. If you want to know more about how I work with Eclipse and Forrest I'll expand further, but I already told you my set up and don't really know what else to tell you at this stage. With respect to debugging, see Chris' reply for one option, or you can do what I do: start forrest in debug mode (see our faq) use the eclipse debugger by connecting to the running instance of forrest (I think there is a faq entry for that too, but I may be mistaken, more info if you need it) Ross
RE: Eclipse and forrest.
-Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 April 2007 8:27 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav wrote: -Original Message- From: Ross Gardler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 April 2007 7:33 PM To: dev@forrest.apache.org Subject: Re: Eclipse and forrest. Gav wrote: I downloaded the latest Eclipse all-in-one package [1] that contains everything we need. ... 1. Workspace, do you point to the forrest trunk as your workspace or somewhere standalone. That's up to you. I'll tell you my setup - that works for me. I have all public source code in: ~/projects Inside there I have loads of project folders, the forrest ones are: ~/project/forrest-trunk ~/project/forrest-ivy-branch ~/project/apache-forrest-0.8 My eclipse workbench is set at ~/project I then use working sets to narrow down the projects I see at any one time (see eclipse help docs for that, but if you only have a handful of projects then you don't need to worry about it). If you already have the sources checked out into your workbench folder then simply create a new project in your workbench and give the new project the same name as the existing folder, i.e. forrest-trunk. Eclipse will spot there is already src here and work through an import wizard with your. I did point to my working trunk which I use with SVN, I didn't like the fact that eclipse then created a few more folders of its own inside my forrest SVN tree, could get messy. I'd rather not have versioned/unversioned stuff mixed up like that. This was the main reason for this question, thought I'd messed it up big time. Your working directory should not be your trunk checkout. If you set it up the way I suggested where (in my case) ~/project is the working directory and ~/project/forrest-trunk is the forrest project directory there is only one eclipse specific file to be created (.project) and you'll find this is already in svn:ignore The confusing thing for me then is, how do I work on trunk and debug it and update it etc whilst the workspace is pointing somewhere else, or is this a RTFM concidering I only installed it today? (I'm impatient, but that's hardly your problem). Or maybe, I do need this mixture of svn trunk and eclipse ? The eclipse workspace does not map to each project. The workspace is a collection of all projects you want to work with in eclipse. This is getting off topic for this list, if you need to know more about the specifics of eclipse workspaces see the eclipse docs. If you want to know more about how I work with Eclipse and Forrest I'll expand further, but I already told you my set up and don't really know what else to tell you at this stage. With respect to debugging, see Chris' reply for one option, or you can do what I do: start forrest in debug mode (see our faq) use the eclipse debugger by connecting to the running instance of forrest (I think there is a faq entry for that too, but I may be mistaken, more info if you need it) Ross Ok, thanks Ross, I get it now :) Gav... -- Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007 3:33 PM
Re: Eclipse and forrest.
Gav wrote: Yes, I will gladly do a document on getting eclipse installed and forrest installed into that. there are some docs around already that I have been looking at, so can amalgamate/update those. Great stuff. These gems are helping us all. As before, please focus on the Forrest-specific bits and keep documentation about supporting products to a minimum. We don't have the people-power to maintain such. -David
Re: Eclipse and forrest.
quote who=David Crossley Gav wrote: Yes, I will gladly do a document on getting eclipse installed and forrest installed into that. there are some docs around already that I have been looking at, so can amalgamate/update those. Great stuff. These gems are helping us all. As before, please focus on the Forrest-specific bits and keep documentation about supporting products to a minimum. We don't have the people-power to maintain such. No problem there, however I will unfortunatly have more questions, for instance I have now installed forrest-trunk into the eclipse workspace from svn and get 77 errors and many warnings before I even get to do anything. We need things like this cleared up for the docs also. Gav... -David -- Gav...
