laurel wrote: > > You are not the only one. As we have discussed, the current setup is > really hard to use. I still have plans to make the eclipse and maven > integration better. And in a few months I should have enough support > to > make that happen. But since that isn't going to happen for a while, we > need to decide if we can wait. > > We had been planning to meet on this 2 months ago but we didn't find a > time when everyone was around, and then the issue was forgotten. > > Laurel, one question I never asked: how do your other projects which > use > eclipse and maven do this? I seem to remember you saying they did, and > I was under the impression they worked better. > - how do they handle thirdparty deps (both in eclispe and in maven) > - how do they handle intra project dependencies (both in eclipse and in > maven)
I think Cynick would be a better person to speak to this, as I was never really involved in the setup of any of the projects in maven, only their use. I do know that we worked with Maven from the command line with four separate but dependent projects. The impact of changes in a project were visible within eclipse (ie. compile errors, etc.) Tests needed to be run for all four projects before any code could be committed, to ensure that a change to one project did not break others. I recall that it was somewhat tricky but not too formidable. I did find I needed to go back to the documentation fairly frequently to remind me how to work with Maven on the command line (my brain doesn't retain that stuff as well as it used to). > > It would be good to start a wiki page with the different options for > eclipse and maven setups. We might even be able to make a table to do > a > feature and pitfall comparison of each. That will be useful to us in > deciding what to do and the wider eclipse and maven community. > If you had time to start that page with the current set up, I'd be happy to contribute. > For this immediate problem, your best bet is to modify the eclipse > build > path for pas author runtime. You should add the pas learner runtime as > a eclipse project dependency. And then you need to change the order of > the dependencies so this new dependency is higher than the maven > dependencies for the pas author runtime. > Thanks for your advice. The setup was as you describe above but I was still having problems (thus the frustrated tone of my original email). Some hints from Tony lead me to look at the RUN configuration, where you can also change the ordering of dependencies in the classpath. Putting the learner runtime above the author runtime seemed to solve the problem in this case. I do find that opening and closing of the project over and over again to force maven to do it's thing is counter intuitive, since I don't "Really" know what the close and open does or how maven responds. I think personally I'd prefer to go to the command line and type maven commands, since then I can actually see the impact of the command (ie. new downloads, etc.). This may not be everyone's preference. However it would be useful for me to see documentation in the wiki for the command line options for working with the projects, since I'm still not all that familiar with working with maven, and would like a document to refer to when I forget what needs to be done. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
