You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@portals.apache.org by Ate Douma <at...@douma.nu> on 2005/06/14 21:56:37 UTC
Issue JS2-292 blocks moving Bridges out of Jetspeed-2
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
Re: Issue JS2-292 blocks moving Bridges out of Jetspeed-2
Posted by Ate Douma <at...@douma.nu>.
Ate Douma wrote:
> 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
>
Maybe a different solution could be to provide separately
released components from the J2 project.
These then should be (able to) build independently from J2 and
have their own release cycle (and version).
Any thoughts?
Re: Issue JS2-292 blocks moving Bridges out of Jetspeed-2
Posted by Julie MacNaught <jm...@apache.org>.
Ate Douma wrote:
> As I want to move ahead, I'll take David's advise and depend the perl
> bridge
> on the jetspeed-rewriter-2.0-M3.jar for now and mark the issue as invalid
> once I committed the changes for JS2-284.
>
I'm not familiar with the J2 rewriter component per se, but your plan seems reasonable. I agree that having a dependency on J2 is not great, but it could be addressed later. Perhaps we will discover that we need some sort of commons area for stuff that overlaps projects. I don't claim to know if the J2 rewriter falls into this category.
Since we have a Bridges JIRA project, perhaps an issue should be created there so we don't lost track of this dependency going forward.
I think it's more important to get the project off the ground, even if there are a few loose ends here and there.
Thanks for taking on this transition. Bridges is an important project.
--Julie
--
Julie MacNaught
IBM Research
jmacna@apache.org
jmacna@us.ibm.com
DADB E3B5 8CB7 6B9B F4A0 8BF7 E830 1848 16A8 D3AB
Re: Issue JS2-292 blocks moving Bridges out of Jetspeed-2
Posted by Ate Douma <at...@douma.nu>.
Nobody seems to bother to respond to my questions so I guess I shouldn't
make such a big deal out of this...
As I want to move ahead, I'll take David's advise and depend the perl bridge
on the jetspeed-rewriter-2.0-M3.jar for now and mark the issue as invalid
once I committed the changes for JS2-284.
Ate Douma wrote:
> 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
>
>
>
>
>