I'd like to discuss how we can resolve issue
http://issues.apache.org/jira/browse/JS2-292 which
in my opinion currently blocks moving Bridges out of Jetspeed-2.
I kindly ask to checkout this issue before responding.
Right now, the Perl Bridge depends on the J2 rewriter component.
AFAIK, the intend of the Bridges project is to be Portal independent, and as
such shouldn't contain
dependencies on for instance Pluto or J2.
But, J2 isn't just "one big jar" but actually composed of many smaller components, some of which
independent of the "portal" part of J2.
David Sean Taylor commented on the above issue that "Component JARs from the Jetspeed project will
NEVER be allowed in this project" would be very restrictive, and I agree with him.
But, I also don't like circular dependencies or having to resolve dependencies by using an "old"
version of a component to compile against.
The real solution I think (and I belief David agrees) would be having another place for components
that can be used by both Bridges and J2 (and Pluto and ...).
The Gems proposal could have provided us with such a place, but that one was
voted down.
Maybe another solution could be to allow components like the rewriter into
Bridges.
But it doesn't "feel" right unless we change the intend of the Bridges project.
Maybe something to consider as well?
Note: I don't think this is/will be an isolated case only, although it seems to
be one right now.
J2 already contains more generic components/features which could be (re)used
standalone or by Bridges.
Anyways, I urgently request all involved to comment on this list how we can resolve these two-ways
cross-project dependencies.
Regards, Ate
