On Aug 28, 2006, at 10:27 AM, [EMAIL PROTECTED] wrote:

Last Wednesday I did commit a patch to the PortalURLParser class that was submitted by David Hay in PLUTO-246. Before the commit, I made sure the trunk built without error and the testsuite passed all its tests. I will also try to take a look at this issue tonight. If this is a real issue, maybe we need an addition to the testsuite to test for it.

It builds fine, comes up fine (the default pages render beautifully) but when you switch pages on the drop-down it happens.  My patch is a workaround but not likely the right thing in the long run.

I did a build this morning on Windows 2000 without any problems using Maven 2.0.4.

Ah - I am MVN 2.0 - Shall make that change and report back.

The duplication of version numbers to all child pom.xml files is a pain. Is there a way of using a
variable in the pom.xml project/parent/version element value for all the pluto-* modules?

In Sakai, we got repeatedly killed by scattered constants - finally we simply "included" something like ../project.xml for these "variables" - that of course is Maven 1 speak - but until we centralized this version nuber one place - we never could get anything to properly release.

It seemed that hard-coding *where* the constant came from (like ../xyz.xml or ../../xyz.xml) while brittle was a small price to pay.

/Chuck

Reply via email to