I will do that then, that is, commit your work to change basedir from ".."
to "." and move the result from ../build to build.

        /Linus

2008/5/2, Dave Thompson <[EMAIL PROTECTED]>:
>
> Hi Linus,
>
> So argouml-build/build will be where the jar files go.  On an eclipse
> check-out they will simply be left at argouml-build/build, but on an SVN
> checkout the build directory, the trunk/src/build.xls file will instruct
> the files to be copied to <checkoutroot>/argouml/build as well.  This
> will help with integration.
>
> That all sounds fine to me!
>
> Dave
>
> On Fri, 2 May 2008 22:35:28 +0200, "Linus Tolke" <[EMAIL PROTECTED]>
>
> said:
> > Hello again Dave!
> >
> > What I want to see is as few references using .. and argo.*.dir as
> > possible.
> > References to the list of subsystem using ../argouml-core-wherever are
> > inevitable.
> >
> > For the resulting dir, and the distinction ../build against ../../build
> > they
> > are both bad. The best would be to put them in build (i.e.
> > <EclipseWorkspace>/argouml-build/build and
> > <checkoutroot>/argouml/src/argouml-build/build).
> >
> > On the other hand, I also would like to have the integration directory
> in
> > <checkoutroot>/argouml/build because all other Tigris subprojects rely
> on
> > that. That doesn't have to be taken care of by the
> > argouml-build/build.xml
> > though. Some other build.xml file can easily call
> argouml-build/build.xml
> > and then copy the result as I have suggested in the build.xml file I
> > committed.
> >
> > What do you think about this?
> >
> >         /Linus
> >
> >
> > 2008/5/2 Dave Thompson <[EMAIL PROTECTED]>:
> >
> > > Hi Linus,
> > >
> > > What I meant was that if you removed 'package', from
> > > argouml-build/build.xml.  You would end up having to remove most of
> the
> > > other targets, and be left with a non-functional build.xml.  You would
> > > not be able to build argouml from the command line any more on an
> > > eclipse check-out.
> > >
> > > So far, I've not worked with the other projects, and I have run 'build
> > > package' and 'build run' from the command line, to build argouml.
> > > These targets work ok without any of the jar files from the other
> Tigris
> > > projects.
> > >
> > > I don't know why the javadocs target depends on 'package', perhaps
> this
> > > dependency was added simply to make sure that the javadocs are only
> > > generated on code that actually compiles.  Or maybe it was a mistake.
> > > I'm afraid I don't know.
> > >
> > > Dave
> > >
> > > On Fri, 2 May 2008 09:29:10 +0200, "Linus Tolke" <[EMAIL PROTECTED]>
> > > said:
> > > > When running these targets (run, debug, info, clitests), do you
> expect
> > > > the
> > > > jar files from the other Tigris projects to be available?
> > > >
> > > > Why is this necessary for the javadocs targets? I don't think
> copying
> > > jar
> > > > files should be required.
> > > >
> > > >         /Linus
> > > >
> > > > 2008/5/1 Dave Thompson <[EMAIL PROTECTED]>:
> > > >
> > > > > Hi Linus,
> > > > >
> > > > > I can't see how removing the 'package' target from
> > > > > trunk/src/argouml-build/build.xml would work, because the 'run',
> > > > > 'debug', 'info', 'clitests', 'javadocs' and 'javadocs-api' targets
> > > > > all depend on it.
> > > > >
> > > > > Dave
> > > > >
> > > > > On Thu, 1 May 2008 08:13:16 +0200, "Linus Tolke"
> > > > > <[EMAIL PROTECTED]> said:
> > > > > > With that I think the package target (in
> > > src/argouml-build/build.xml)
> > > > > > can be removed. How do you feel about this Dave?
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to