Santiago Gala wrote:
To be honest, the maintenance and handling of dependencies for such a big set is driving us crazy. We need to do something.
So its not just me? Glad to hear that :)
For this to be workable in the short term, if would be handy to have a way for the involved bridges demo to deliver PSML pages showing the portlets demoed. While this is not portable as of JSR-168, the PSML format is simple enough to be used as a mean to understand what is intended for demo in a war file. As already commented, we could just use pages in /WEB-INF/pages in the war, and the deployer *could* take care of creating them in the portal, or else the build process could take them from there to construct the demo portal.
I like this. Or maybe it would be as simple as dropping in psml files into the WEB-INF/deploy directory. I think either way will work With the new DB PSML manager (in developmental stages), we plan to support PSML 'drop in' via the deploy directory that will then import the PSML XML file into the database.
In following steps, we could try to have a repository where complex webapps could be maintained, starting with the admin portlets themselves (security, pam, palm)
When you say repository, you mean a remote maven repo?
Also, to clean, document and make sure that demo portlets are actually showcasing core portlet-api and jetspeed features, and that they serve this purpose with minimal fuss. I'd recommend starting with the easy steps: moving php, perl, struts-demo, jpetstore, jsf-demo, and jsf-demo-myfaces to places under portals-bridges/ In a first go, the psml pages using those portlets would remain in jetspeed/src/webapp/WEB-INF/pages
+1
I had the idea to move the wars to bridges/<framework>/src/webapp ..., but it would possibly be better something like bridges/<framework>/<framework>-demo instead. This can be done with a simple server side move, but the project.xml /properties would need some adjustment, both for jetspeed to depend and take the war artifacts in the "full" goals, and for bridges to build them. What do you think? Santiago
The demo code could be stored in bridges/<framework>/<framework-demo>, or if the application is useful enough, and is NOT just a demo, I prefer storing useful applications at Portals Applications, such as the RSS portlets for example are not really demos but more ready-to-use portlets.
The internal PAs (security, palm, pam) should remain in Jetspeed-2 svn. However I recommend merging them all into one war, such as "jetspeed-admin" -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
