When doing this change I have not fixed up the build2 scripts. My ideas was
to remove them in favor of Eclipse configurations to do everything.
    

I'm not sure I understand how this is meant to work in practice.  How
does one run the regression test suite before committing a source code
change since, as far as I know, only one instance of Eclipse may be
using a workspace at a time?  Are people using JUnit test suites from
within Eclipse or picking tests to run by hand or just not running the
tests?

  
I'm running the full tests in the command line SVN checkout and the normal development in the Eclipse checkout. In Eclipse I just execute selected tests with the JUnit launch configurations.
The two examples that I looked most closely at were AndroMDA and
Eclipse itself.  Eclipse basically uses a project per plugin and uses
the plugin development environment (PDE) .  AndroMDA, as I recall, had
a top level project called something like andromda-all which could be
checked out if you wanted to get everything, but the more typical
environment which to check out individual modules underneath the top
level.  These two styles of checkouts were mutually exclusive.
AndroMDA used Maven for its builds and Eclipse uses the command line
Eclipse builder, so the two projects deal with this aspect
differently.  I'm sure there are many more examples of projects
available now than there were two years ago.

  
I think that what we now have is inline with the above thing you state regarding AndroMDA, with the obvious difference that we use Ant instead of Maven and that if I want I may use the SVN command line checkout in eclipse without much problems.

Luís
Tom
  
PS: I think that having an Ant setup is good to have the possibility to execute without replying on a big fat IDE and seamless integration with the command line. The last time I checked the Eclipse command line interface required having a workspace, but, I haven't look for long since I totally prefer Ant or some other make like utility.

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to