[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] checkin - core consolidation, using Ant to install/build
|
Dave Shields wrote:
On Wed, Nov 27, 2002 at 11:22:18AM -0500, Jim Wright - IBM Research wrote:
Dave,
While syncing with CVS this morning, I noticed that you've created a file,
'build.xml', in org.eclipse.stellation.core. Previously, the build.xml (and
install.xml) used for command-line-related tasks were kept in
org.eclipse.stellation.misc.
Putting your build.xml in stellation.core creates an unfortuate name clash.
Eclipse uses and creates 'build.xml' files for its own Ant-related tasks
(including packaging a set of plugins into an installable 'Eclipse Feature'.
I'm planning to deploy most or all of our Eclipse components that way; I
have it more-or-less working now on our internal 'svc' server, and plan to
post it on eclipse.org as soon as we have a relatively stable build again
(and have hopefully worked out the 3rd-party-jar permissions issues).
As it happens Eclipse typically generates the build.xml file automatically,
and I've found that it's good practice to blow away the build.xml file
before building a packaged Feature
(because Eclipse doesn't always detect stale build.xml files). So, the name
clash (your build.xml vs. the Eclipse build.xml) isn't fatal; but it's
likely to cause confusion (and/or break the Feature build process on occasion).
Could we go back to keeping the files related to the command-line build and
install process in stellation.misc? That would avoid the problem described;
I will cheerfully promise not to tromple on stellation.misc :>
It is ludicrous to have the ant build file for the core in misc. The files for
the core should be in a single directory, not scattered about in two directories.
I think ludicrous is a bit strong. I agree that getting it out of misc
is a good thing; the
misc project is an unfortunate anachronism of the rush to set up our
project repository
on eclipse.org. But there was a rational reason for putting it there:
the core project
contained only eclipse stuff; the ant file was for use from the command
line outside of Eclipse, and so it belonged somewhere else. All of the
non-Eclipse stuff was put
into misc.
I also find it strange that Eclipse should make it impossible to use 'build.xml' for
the Ant build file.
It doesn't make it impossible. It assumes that if you're using Eclipse,
well then,
you're using Eclipse. Since Eclipse has started using ant internally for
build
management, it makes the entirely reasonable assumption that it can use
build.xml as the name of the build file. Then if you want to do builds from
the command line, you can do them using ant - and Eclipse takes care of
setting up the file for you.
They did not build their ant support with the idea that they needed to
support users who expected to be able to use both Eclipse-managed builds,
and simultaneously use their own non-eclipse ant builds.
From the Eclipse point of view, *we're* the ones doing something bizzare.
Sometime soon, I'm planning on starting the work involved in turning
core into a pure plugin - that is, pushing it totally into Eclipse, using
the Eclipse launcher, and the Eclipse builders. Once that's done, we
should be able to use the Eclipse ant build file for compilation, and we'll
need a separate file for installation.
-Mark
