[ http://issues.apache.org/jira/browse/JS2-292?page=comments#action_12313873 ]
Ate Douma commented on JS2-292: ------------------------------- I think I'm gonna take David's advise and will pinpoint the perl bridge dependency on the jetspeed-rewriter-2.0-M3.jar for now, as its the easiest way out (for now). But Raphaël, could you elaborate a bit more about your option #3 suggestion: > - move rewriter to a new source root, either a Portals commons area or simply > Jakarta Commons > and release rewriter from there. ... > Now option #3 is very easy to do, we can use [EMAIL PROTECTED] as our > "commons" mailing list > just like I think "portlet-api" should be moved there. This isn't completely clear to me: are you suggesting now we create a new Portals Commons project in which we can host the portlet-api as well as generic components like the rewriter? I'm not saying I would be against it (on the contrary), but how is this (much) different from the Gems proposal? If you are serious about this, could you write up a formal proposal? > Remove jetspeed-2 rewriter component dependency from the perl bridge > -------------------------------------------------------------------- > > Key: JS2-292 > URL: http://issues.apache.org/jira/browse/JS2-292 > Project: Jetspeed 2 > Type: Sub-task > Components: Bridges > Versions: 2.0-M3 > Reporter: Ate Douma > Assignee: Roger Ruttimann > Priority: Blocker > Fix For: 2.0-M4 > > This dependency BLOCKS the move of the bridges to its own subproject! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
