"David H. DeWolf" <[EMAIL PROTECTED]> wrote on 08/28/2006 07:56:00 AM:

>
>
> Charles Severance wrote:
>
> >
> > The trunk has a bug where PageId's end up with a prefix of a "/" and so
> > the configuration can never find find pages - and things blow up horribly.
>
> Are you seeing this with the trunk?  Craig committed a patch that seems
> related just a few days ago.   I'll take a look at it tonight if you are.
>
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.


> >
> > ======= Neither trunk nor beta1 will build unless maven.test.skip=true
> > ========
> >
>
> I can't duplicate this.  It builds fine for me on the following:
>
> - Mac OSX - upon which it was never before installed
> - Windows XP - upon which it has been installed before
>
> Both using: Maven version: 2.0.4
>

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

> >
> >
> > ===== The beta1 tag builds but will not pluto:install =======
> >
> > The key here is that you need to clean out your maven repo before doing
> > install and pluto:install.
> >
> > cd ~/.m2
> > rm -rf `find . -name '*SNAPSHOT*'`
> >
>
> This is because we're using 1.1.0-SNAPSHOT as the version in trunk which
>   has been hard coded (yuck) in the install goal as the dependent
> version.    I recommend that we look into finding a more elegant
> approach to managing plugin dependencies.
>
> Just in case anyone is wondering, I don't recommend that we modify the
> tag since it represents a release.  Let's just upgrade the trunk.
>
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?

>
> David

Reply via email to