portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-292) Remove jetspeed-2 rewriter component dependency from the perl bridge
Date Wed, 15 Jun 2005 17:01:51 GMT
    [ http://issues.apache.org/jira/browse/JS2-292?page=comments#action_12313719 ] 

David Sean Taylor commented on JS2-292:
---------------------------------------

> The rewriter component is *part of* the Jetspeed-2 project, even if not dependent on
Jetspeed itself, and not released independently (right now).

Yes, and my argument is that a component jar from Jetspeed, being a POJO, can be used in other
portals.

>The Jetspeed-2 perl (demo) application depends on both the rewriter component and the
perl bridge.
> You can define a build dependency for the perl bridge on an "older" version of the rewriter
component as you suggest but then I expect you do want to build 
> the perl demo
> using the latest version of the rewriter component...
> Or, you must guarantee never to change the (used) rewriter api anymore.

This seems to fall under the general dependency chain problem space and its not specific to
Jetspeed

> Anyways, I do think this is an important structural issue.
> And I agree that the most logical solution would be having a common place for components
used by both Bridges and J2.
> The Gems proposal could have saved us here...

Ugh, don't get me started again. I just starting whining and someone will have to slap me
:)

> Maybe we can/should expand the charter of the Bridges project and allow components in
like the rewriter. But then, 
> "Bridges" isn't really covering the intend anymore. 

I have issue from the stand point of a Bridges developer.
I dont like having the restriction that I can't use components from the Jetspeed Portal.
Seems we are mixing two different things here:
1. The requirement for the Bridges project (which I support) that bridges should run in other
portals besides Jetspeed
2. The restriction that you cannot use Jetspeed components in a bridge




> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message