On Wed, May 01, 2002 at 01:34:46AM -0000, [EMAIL PROTECTED] wrote:
> kaz 02/04/30 18:34:46
>
> Modified: src/templates/build build.init.target
> Log:
> Backing out this change. It breaks iutest. In the meantime, the
> upgrading of a pom is failing (you can see this by changing your pom
> version to 1). We have to fix this.
The reason I backed out the change is that some of our Ant targets
depend on the POM being loaded before we load the default properties
(for example, the iutest.dir property in default.properties) expects
that it has access to ${integrationUnitTestSourceDirectory} which comes
from the POM. So the POM must be loaded before we load the
default.properties file.
However, in the current state (POM loaded first, then default
properties), the automatic updating of the POM does not work because
when the POM is loaded, it checks to see if the POM is up to date, if it
is not, then it tries to update the POM, which means it needs access to
the stylesheets which was recently changed to a property that is loaded
from default.properties which hasn't been loaded yet!
In any case, I have the solution, I'm going to remove the stylesheet
property as that was a temporary fix that was made until the ability to
alter the color scheme of the Maven web site was completed. Now that
has been completed, we can remove this temporary fix (and problem) as we
do not want the users to have the ability to change the style of the
site, only the colors, as one of the goals of Maven is to make it easy
for a user of one Maven project to use another Maven project.
Pete
