portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaël Luta (JIRA) <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-292) Remove jetspeed-2 rewriter component dependency from the perl bridge
Date Thu, 16 Jun 2005 12:57:49 GMT
    [ http://issues.apache.org/jira/browse/JS2-292?page=comments#action_12313817 ] 

Raphaël Luta commented on JS2-292:

If I understand the discussion correctly, there's a build dependency oin the rewriter that
can only
be resolved by having the resolver released as an independant artefact that can be used by

both Jetspeed 2 and Bridges.

Is this correct ?

So our options for handling this are :
- keep it in Jetspeed, release it as a separate artefact and have Bridges build on it, dealing
 with the cyclical dependency in some way.
- move rewriter into Bridges, have it released from Bridges, have Jetspeed depend on this
artefact, no cyclical dependency
- move rewriter to a new source root, either a Portals commons area or simply Jakarta Commons

and release rewriter from there.

I honestly don't see it as a big issue since SVN allows anybody to check out directly
http://svn.apache.org/repos/asf/portals/jetspeed-2/trunk/components/rewriter/ and build it
there without checking out the whole J2 tree (assuming the maven config of rewriter can work

Now option #3 is very easy to do, we can use general@portals as our  "commons" mailing list
just like I think "portlet-api" should be moved there.

> 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:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message