On Tue, 2007-04-03 at 08:54 -0700, David Sean Taylor wrote:
> On Mar 27, 2007, at 12:10 PM, Brice Lambi wrote:
> 
> > Hello,
> >
> > I have a few questions about the maven2 plugin for jetspeed.  I  
> > created
> > a new portlet app using the portal-application archetype.  The  
> > directory
> > structure created is not standard for maven2.  I get src/java  
> > instead of
> > src/main/java as the source directory.  Why is this?
> 
> This is because we are trying to keep with the Maven-1 standard
> With 2.1 we are stuck between two builds (Maven-1 and Maven-2)
> 2.2 will drop the Maven-1 build support, and move to a true Maven-2  
> build and directory structure
> 
> Anyway for a portlet-app I think many folks may prefer the directory  
> layout of an Eclipse web project
> 
> > This makes it
> > difficult to use this project outside of the jetspeed build.  If I  
> > move
> > everything to src/main, it complains about not being a web app.  It  
> > does
> > the same with the component-archetype.
> >
> 
> Understood.
> We will consider this in the new build refactoring, thanks
> 
> > Also, I added my new app to the app-server pom and the tomcat- 
> > build.xml
> > so that it will be deployed with the portal.  All I get is a failed to
> > retrieve portlet definition/access denied error(the only security
> > constraint I have is user).  Looking at the logs, I never see the
> > "JetspeedContainerServlet: starting initialization of Portlet
> > Application" notification.  Also manually deploying my app to
> > WEB-INF/deploy does nothing.  If I remove my app from the app- 
> > server pom
> > and tomcat-build.xml and then redeploy the portal and manually  
> > deploy my
> > app, it works fine.
> >
> 
> I don't remember ever having to modify the tomcat-build.xml
> Just make sure the applications/pom.xml includes your new module:
> 
>   <modules>
>          <module>myPA</module>
> 

The new docs don't mention editing tomcat-build.xml or any poms other
than adding the module to applications/pom.xml, but my portlet-app
wasn't being deployed.  So I followed the instructions on the wiki to
add my app to the poms and tomcat-build.xml and then it was being
deployed.  I still had the earlier problem.  I'll keep messing with it,
maybe I'm still using the 2.1-dev plugin.

> > Also, after deploying my portal I try to log in as manager and I  
> > all the
> > admin portlets I get access denied.  The admin account works just  
> > fine.
> >
> > The plugin looks great, if I can get these things worked out it will
> > greatly simplify my deployment process.
> 
> Not sure what is going on... did you configure your Maven-2  
> settings.xml?
> 

You're right, I didn't have the j2deployer account created on tomcat,
this might be the problem.

Thanks!
Brice

> 
> 
> ---------------------------------------------------------------------
> 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