Hello Tom!
I don't understand this. Here we have a file that performs things that are
not used in the Eclipse layout, and as we have previously concluded, it
risks to confuse or destroy the workspaces or root for anyone using it from
the Eclipse layout. Furthermore, the most convenient place from the
repository layout is to place it outside the Eclipse layout. Why is that a
problem, or rather, why would anyone want to use or access that file from
the Eclipse layout?
I had not planned to move to an Eclipse-based release process in the 0.26
release. I think that would be too much work and I don't feel I have the
right competence for that. Did you plan for such a move?
Because of this, the old, ant-built release is what I plan to use to release
the 0.26 version. My plan is now to get it to work again after the changes.
This means that I will try to defer any new big changes to the layout until
after the 0.26 release.
/Linus
2008/4/30 Tom Morris <[EMAIL PROTECTED]>:
> On Wed, Apr 30, 2008 at 10:36 AM, Linus Tolke <[EMAIL PROTECTED]> wrote:
>
> > Another thing to consider is perhaps the role of the
> > /trunk/src/argouml-build/build.xml. The reason for moving it lower is to
> > allow it to be checked out on the same level as the Eclipse
> > projects/subsystems. This is to be able to run the targets that builds
> every
> > subsystem and runs the tests in every subsystem.
> >
> > The target that copies everything from each subsystem to whatever export
> > directory is not applicable. Perhaps we should split that file and move
> the
> > copying to /trunk/build.xml to make the argouml project work just like
> the
> > other projects for the non-Eclipse checkout. The build.xml will then
> contain
> > more or less:
> > build each subsystem
> > copy the result of the builds to build.
> > It could also contain a run-all-tests target to increase the similarity
> with
> > the build.xml files of the other Tigris projects. I will make an attempt
> at
> > creating the /trunk/build.xml.
>
> Where does this file live in the Eclipse checkout directory structure?
> It needs to live in a project, not directly in the <workspace> root
> directory.
>
> > Unless you fix this, Dave, I will fix it for the release 0.25.5 to avoid
> > having to change the 10 or more other Tigris projects that relies on
> having
> > the files in argouml/build to be built. After the 0.26 release we could
> > revisit this again.
>
> If things are required to stay unchanged until after 0.26, why did we
> make ourselves endure two rounds of massive changes? That's a huge
> waste of time.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
