Here's another one...
I tried using maven but I'm not happy how handles libraries not found
in the repositories (like the firebird jaybird driver). So I'm now
using the ant AssembleTask.
I've found a problem with the manifest:
Finding class org.apache.pluto.ant.AssembleTask
Loaded from
/home/phuber/Subversion/portlet/mainline/portal/lib/pluto-ant-tasks-1.1-SNAPSHOT.jar
org/apache/pluto/ant/AssembleTask.class
Exception reading component
/home/phuber/Subversion/portlet/mainline/portal/lib/pluto-ant-tasks-1.1-SNAPSHOT.jar
(reason: invalid header field)
The field Specification-Title spans multiple lines in the manifest.
And if I shorten the contents of that field so it spans only one line,
everything's fine.
Patrick
2005/12/6, David H. DeWolf <[EMAIL PROTECTED]>:
> FYI. . .
>
> it's using spring to inject those values now. . .take a look at the
> constructors and the following declaration:
>
> private static final String DEFAULT_SYS_DIR =
> System.getProperty("user.home") + "/.pluto/portal-driver/data";
>
> I'm a little swamped today. . .good luck. . .I'll check in when I can.
>
> David
> On 12/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi David,
> > > craig, I haven't seen any problems with the db creation. how does
> > > this relate to patrick's problem? or is it a seperate problem you're
> > having.
> > >
> >
> > I was able to get Pluto 1.1 up and running using a clean build and the Derby
> > database seems to be built OK.
> > But it is found in a subdirectory of the Tomcat's bin directory and that is
> > called:
> > databaseName=PLUTO_PORTAL_DRIVER;name=pluto_portal_driver;password=apachep0rtals;create=true
> >
> > It looks like you got a couple of the constants messed up in
> > EmbeddedDataSource (BTW, see DatabaseConfig that I put in the same dir).
> > When I get a chance, I'll change the directory location back to
> > <user.home>/.pluto/portal-driver/data if I get some free time today.
> >
> > > we can talk about user credentials. . .I implemented the security to
> > > resolve a jira issue -- maybe I tightened down the hatches too much.
> > > I'd definately like to stick with declarative security.
> > >
> >
> > Yes, decarative security is the way to go, but, IMHO, we shouldn't secure
> > the whole portal by default.
> >
> > > I'll do more testing after I get the snow cleaned off my driveway
> > > and make my way through the horrible traffic and into work :)
> >
> > At least in Maine we have no traffic and horrible snow (which I like since
> > I'm a skier).:)
> >
> > /Craig
> >
> > >
> > > David
> >
> > > On 12/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Patrick,
> > >
> > > I'm not sure what happened to the database creation code, but I ran
> > > a quick SVN update and build Pluto 1.1 this morning and a new
> > > database was not created after I deleted the old one. David, can you
> > > comment on this?
> > >
> > > The Pluto 1.1 portal is currently protected to only allow users with
> > > a role called 'pluto' (see web.xml), so you need to add that role
> > > and a user belonging to that role to tomcat-users.xml. I'd like to
> > > change that restriction and only require a login for the testsuite
> > > test of the PortletRequest.isUserInRole() functionality. When we get
> > > around to implementing admin portlets in Pluto 1.1, I'd like them
> > > restricted to a user in 'admin' role. David, please comment on this
> > too.
> > >
> > > Thank you for keeping us Pluto 1.1 developers on our toes!!
> > > /Craig
> > > ----------------------------------------------------
> > > Craig Doremus
> > > Senior J2EE Application Developer
> > > Hannaford Bros
> > > ----------------------------------------------------
> > >
> > >
> >
> > >
> > > Patrick Huber <[EMAIL PROTECTED]>
> > > 12/06/2005 01:28 AM
> > >
> > > Please respond to
> > > [email protected]
> > >
> > > To
> > >
> > > [email protected]
> > >
> > > cc
> > >
> > > Subject
> > >
> > > The new Pluto Portal
> > >
> > >
> > >
> > >
> > > Hi all
> > >
> > > I was trying to get the latest version of the pluto portal up and
> > > running. Deployment worked fine an tomcat picked the pluto and
> > > testsuite wars up.
> > >
> > > Now I'm wondering with what user I can log in to the portal. I tried a
> > > user with the manager role from tomcat-users.xml but I get a 403,
> > > access denied. I checked the source tree and found this one sql script
> > > where a db structure is added but it appears there is no explicit user
> > > table and no user data inserted.
> > >
> > > While trying to get this running I also deleted ${user.home}/.pluto
> > > since it helped before. Now that directory isn't being recreated.
> > > Neither during compile/deploy nor during tomcat startup.
> > >
> > > So I guess security is handled outside of the portal? How can I get
> > > this up and running?
> > >
> > > Thanks
> > > Patrick
> > >
> > > --
> > > "I love deadlines. I like the whooshing sound they make as they fly
> > > by." -- Douglas Adams
> >
>
--
"I love deadlines. I like the whooshing sound they make as they fly
by." -- Douglas Adams
