Hello all!
In the directories under src (as well as for the projects from other
projects argouml-cpp, argouml-csharp etc), the ambition is that each
directory is self-contained except for explicit dependencies. If such a
subsystem requires a tool, that tool is located in that subsystem or in a
central place (the Eclipse set-up or tools in the top directory). If several
subsystems requires a tool, that tool is located in each of these subsystems
of in a central place.
If you are considering moving tools down to that level, make sure you don't
make the subsystems depend on each-other for these tools.
When building and running from within Eclipse I think it is just the
easymock and jdepend jars that are used from tools for the junit tests. All
other tools are either for building documentation or for the non-Eclipse
build.
Why was the cobertura added in this way? Isn't there an Eclipse cobertura
plug-in that works with JUnit configurations?
/Linus
2008/4/26 Tom Morris <[EMAIL PROTECTED]>:
> On Sat, Apr 26, 2008 at 5:50 AM, Dave Thompson <[EMAIL PROTECTED]> wrote:
> > Tom Morris wrote:
> >
> > > The way we have things set up now every
> > > build change has to be tested in two different configurations and I
> > > missed this.
> > >
> >
> > Is this even more reason to move the tools dir into src/?
>
> Actually I think it's just the same reason that I stated originally.
> I have a strong preference for having the on-disk layout be the same
> for Eclipse match the SVN layout (and thus the default layout that a
> user gets by checking out the whole tree at once).
>
> I haven't thought much about where it should move to. Perhaps
> argouml-core-infra/tools? Log4J seems awful lonely having an entire
> project to itself.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
