This is Scott's reponse: I think this is relevant to sail/pas developers as a whole, if you don't mind I'd recommend posting it to the pas and sail lists.
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) 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. 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. Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
