Raphaël Luta said:
David Sean Taylor wrote:
I'm testing it in J2 right now... I'll ping you when it's done and committed and let you update the Fusion assembly file, ok ?
Great!
I've committed the patch in Jetspeed 2 but Fusion is built against J2-M2... either we have to upgrade the the dependency to J2-HEAD or generate a new J2-M3 artefact to build a proper dependency or add a new dependency on a "patch" artefact that only contains the FusionPathEncodingPortalURL class...
I can't say I'm thrilled with any of these options :(
Wouldn't it be easier to include the FusionPathEncodingPortalURL in J1 under the Fusion subproject instead of adding it to J2? I'm not sure who would ever need a Turbine compatible solution when not using Fusion.
Probably a more sensible option, I just took the lazy way out and did
not change the package
I will create a org.apache.jetspeed.fusion.container.url.impl package directly in fusion source and move out of J2 the code.
It's definitely cleaner this way.
-- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
