Branch WFM and I like the EYODF approach: +1. Best to get it into the trunk so that we can wring out any other issues. I am very anxious to get the build stabilized.

Randy

Ate Douma wrote:

David Le Strat wrote:

See comments below.


I think we now have a very easy to use build for


integrators to create

new portals. And as you say, we are eating our own


dog food by using

that exact same build as integrators use for


building the default

system. This should make it very easy for new


users to get up and

running the right way: with the j2:genapp-portal


goal. In the docs, we

need to encourage this approach and discourage


working directly from a

distribution or the jetspeed source directory.



A big +1 there, this will greatly ease the getting
started process in my opinion.

Thanks for you vote too :-)


I am still testing and I have run into an issue with
the portal TestUserInfo test but have not had time to
look more into the issue.  I essentially get a
NullPointer.

We need to make sure that the unit tests pass (I am
not sure, if this has something to do with my setup or
not) otherwise I am definitely +1 on merging down to
HEAD.

I especially made sure they passed as we had soo many problems
the last few weeks with that.
So, my guess right now is it might be related to your configuration.
Can you provide stack trace where the NPE happens?



Regards,

David Le Strat.

________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com


____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to