Re: found fusion/pluto interaction bug
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! OK, moved the code the in J1 Fusion directly and updated the assembly accordingly. You can forget everything I've said about updating dependencies... I just need to catch up some sleep and start thinking straight :/ -- 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]
Re: found fusion/pluto interaction bug
Ate Douma wrote: 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]
Re: found fusion/pluto interaction bug
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. > > -- > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: found fusion/pluto interaction bug
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 :( -- 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]
Re: found fusion/pluto interaction bug
Raphaël Luta wrote: Let me know if I can do something now (or within the next 2 hours) else I'll at least test the cut release but probably not before Thursday. Thursday sounds more realistic Slim chance I'll finish anything today Still working thru some issues here, for example the tutorial is broken Just test it and fix anything you find -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: found fusion/pluto interaction bug
David Sean Taylor wrote: Raphaël Luta wrote: David Sean Taylor wrote: Moved this to Jetspeed-dev Raphaël Luta wrote: I thought we would first go through Release candidates for 1.6 before announcing an official "1.6" release ? im -1 on that because no one actually works on 1.6 anymore except myself There hasn't been any activity on the 1.6 branch for months My vote is to release it since I don't have the free tiem for a full RC cycle That's precisely why I think it's risky to call it a release directly. If there's any bug found in the 1.6 release, we'll get a whole lot a user queries on the list with few developers still actively working and supporting the 1.x branch. I'd like the 1.6 final release to be as stable as possible so that we don't *have* to cut a 1.6.1 for maintenance reasons because of some major issues in the release. For me reaching this goal means cut a release, calling it RC1, freeze the tree, ask all users to test it out for 2 weeks - 1 month and if no one comes back with a showstopper or major bug, recut a 1.6 release that can possibly be the same as 1.6 RC1 and publicly state that from then on Jetspeed 1 is in "maintenance mode" with no features added and that all users should consider upgrading. OK we can do this. Any help apprecated in making the release Today Ive come across a few things I'd like to fix in 1.6 If I get them all fixed, then I'll try to release an RC1 late tonight Otherwise its ready when its ready...but definitely by the weekend Let me know if I can do something now (or within the next 2 hours) else I'll at least test the cut release but probably not before Thursday. 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! -- 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]
Re: found fusion/pluto interaction bug
Raphaël Luta wrote: David Sean Taylor wrote: Moved this to Jetspeed-dev Raphaël Luta wrote: I thought we would first go through Release candidates for 1.6 before announcing an official "1.6" release ? im -1 on that because no one actually works on 1.6 anymore except myself There hasn't been any activity on the 1.6 branch for months My vote is to release it since I don't have the free tiem for a full RC cycle That's precisely why I think it's risky to call it a release directly. If there's any bug found in the 1.6 release, we'll get a whole lot a user queries on the list with few developers still actively working and supporting the 1.x branch. I'd like the 1.6 final release to be as stable as possible so that we don't *have* to cut a 1.6.1 for maintenance reasons because of some major issues in the release. For me reaching this goal means cut a release, calling it RC1, freeze the tree, ask all users to test it out for 2 weeks - 1 month and if no one comes back with a showstopper or major bug, recut a 1.6 release that can possibly be the same as 1.6 RC1 and publicly state that from then on Jetspeed 1 is in "maintenance mode" with no features added and that all users should consider upgrading. OK we can do this. Any help apprecated in making the release Today Ive come across a few things I'd like to fix in 1.6 If I get them all fixed, then I'll try to release an RC1 late tonight Otherwise its ready when its ready...but definitely by the weekend 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! -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: found fusion/pluto interaction bug
David Sean Taylor wrote: Moved this to Jetspeed-dev Raphaël Luta wrote: I thought we would first go through Release candidates for 1.6 before announcing an official "1.6" release ? im -1 on that because no one actually works on 1.6 anymore except myself There hasn't been any activity on the 1.6 branch for months My vote is to release it since I don't have the free tiem for a full RC cycle That's precisely why I think it's risky to call it a release directly. If there's any bug found in the 1.6 release, we'll get a whole lot a user queries on the list with few developers still actively working and supporting the 1.x branch. I'd like the 1.6 final release to be as stable as possible so that we don't *have* to cut a 1.6.1 for maintenance reasons because of some major issues in the release. For me reaching this goal means cut a release, calling it RC1, freeze the tree, ask all users to test it out for 2 weeks - 1 month and if no one comes back with a showstopper or major bug, recut a 1.6 release that can possibly be the same as 1.6 RC1 and publicly state that from then on Jetspeed 1 is in "maintenance mode" with no features added and that all users should consider upgrading. If we could get the fix in now I'd be glad to incorporate it in the release I can write it easily but I don't have currently the environment to test it :) I've not yet run Fusion... I'll commit a patch later this evening. send me a patch and i'll test it immediately 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 ? -- 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]
Re: found fusion/pluto interaction bug
Moved this to Jetspeed-dev Raphaël Luta wrote: I thought we would first go through Release candidates for 1.6 before announcing an official "1.6" release ? im -1 on that because no one actually works on 1.6 anymore except myself There hasn't been any activity on the 1.6 branch for months My vote is to release it since I don't have the free tiem for a full RC cycle If we could get the fix in now I'd be glad to incorporate it in the release I can write it easily but I don't have currently the environment to test it :) I've not yet run Fusion... I'll commit a patch later this evening. send me a patch and i'll test it immediately -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
