One thing we ran into with chianti was problems in the build due to
the availability of dependencies that are only used in a few places.
For example, there were repeated problems building the JAXB
databinding due to downtime at java.net. This isn't new - for
example, I remember in M1 we had problems building SDO due to issues
with the Eclipse repository.
I like the idea of being able to build everything in one go. That's
what happens now when you type mvn at the root of a fresh checkout
and I think that should still work. The problem comes when it doesn't
and new users end up fighting just to get their first build done.
We also have some fairly large areas that are independent of each
other. For example, I think someone interested in SDO should be able
to check out just the sdo tree and have that build on its own.
There are some dependencies though between these areas - for example,
the current sca trunk depends on the sdo trunk (specifically the 1.0-
SNAPSHOT version). These are not so coupled that they need the
absolute latest code so one way to handle that would be to publish
nightly (or other unstable) builds to the apache snapshot repository.
This is not a release and hence does not need a vote etc.
We can tackle the build problems this way as well. For example,
modules that have dependencies whose availability is flakey could be
moved to a section of the build that was optional and which could be
enabled or disabled using maven profiles.
Is this kind of modularization worth tackling?
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
