You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bridges-dev@portals.apache.org by Ate Douma <at...@douma.nu> on 2010/04/09 09:55:53 UTC
Re: edit_defaults
On 04/09/2010 01:13 AM, David Sean Taylor wrote:
> On Thu, Apr 8, 2010 at 4:06 PM, Ate Douma<at...@douma.nu> wrote:
>> On 04/08/2010 06:17 AM, David Sean Taylor wrote:
>>>
>>> A minor complication to any portlets using the Velocity Bridge with
>>> the edit_defaults auto switch, seems we need to patch the bridge in
>>> GenericVelocityPortlet.java
>>> And require another release of this bridge if we want to properly
>>> support edit_defaults auto switch .....
>>
>> Maybe we should consider upgrading bridges also to use portals-pom and
>> release using Nexus.
>> If we combine that will separated and independent release versions for each
>> bridges component like we now do with APA, e.g. start defining versions like
>> bridges-common-1.0.5, bridges-velocity-1.0.5 etc. in APA JIRA, and have them
>> all have their separate svn trunk/branches/tags folder, we could turn out a
>> bridges-velocity-1.0.5 (and at least bridges-common-1.0.5 for proper Maven-2
>> dependency resolution) pretty quickly.
>> Doing the ground work starting with only bridges-common and bridges-velocity
>> probably can be done in matter of hours.
>> WDYT?
>>
> +1 on velocity and common bridges
OK.
Assuming lazy consensus on this for now then I'll start on this right away.
Actually I already did some preliminary work locally and got things converted and working within half an hour :)
The restructuring of svn itself probably will take most of the time.
As I think these new bridges versions should all assume portlet 2.0 runtime environments, we better bump their major version to indicate
this, e.g. bridges-common-2.0 and bridges-velocity-2.0
I plan to do the following:
- create a PB JIRA issue for all this
- create new PB JIRA versions bridges-pom-1.0, bridges-common-2.0, bridges-velocity-2.0 and bridges-site as a start
- create a new portals svn site subproject for bridges and (start) moving the little bridges xdocs we have over (maven-2, no multiproject)
- create new svn /bridges-pom, /bridges-common and /bridges-velocity project trees with their own trunk/branches/tags folders
- create a new bridges-pom:1.0:pom project
- move current bridges/trunk /common/* under /bridges-common/trunk and /velocity/* under bridges-velocity/trunk,
- for commons and velocity, remove their maven-1 configurations *and* their xdocs and update their maven-2 pom.xml
- adjust the current bridges/trunk maven-1 and maven-2 projects to accomodate for these components been moved out
All in all, this should take a few hours the most and allow us to release new bridges-pom, bridges-common and bridges-velocity shortly.
Other bridges which qualify for updating and subsequent 2.x releases like maybe struts and groovy can follow later on.
Regards,
Ate
>
> I've only tested with the velocity bridge with regards to the
> edit_defaults issue. Perhaps I should test some other bridges as
> well....
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
Re: edit_defaults
Posted by David Taylor <da...@bluesunrise.com>.
On Mon, Apr 19, 2010 at 4:38 PM, Woonsan Ko <wo...@yahoo.com> wrote:
> Hi Ate/All,
>
>
> ----- Original Message ----
>> From: Ate Douma <at...@douma.nu>
>> To: Jetspeed Developers List <je...@portals.apache.org>
>> Cc: Bridges Developers List <br...@portals.apache.org>
>> Sent: Fri, April 9, 2010 1:18:02 PM
>> Subject: Re: edit_defaults
>>
>
> I also committed an initial fix for the
>> GenericVelocityPortlet almost like what you proposed earlier on this email (and
>> which was the
> trigger for all this), see:
>> http://issues.apache.org/jira/browse/PB-103
>
> I'm leaving the root JIRA
>> issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as
>> there still remains work to be done on
> especially the bridges-site (only the
>> groundwork has been done so far) and pending possible migration of other bridges
>> like maybe the groovy
> and struts
>> bridge.
>
> I think it would be better to move out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply add jruby or jython supports there as well as groovy in the similar way.
>
sounds good, its either that or creating a jruby and jython bridges
separately, im fine with your proposal
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by Ate Douma <at...@douma.nu>.
On 04/19/2010 05:07 PM, Woonsan Ko wrote:
>
>
>
>
> ----- Original Message ----
>> From: Ate Douma<at...@douma.nu>
>> To: Jetspeed Developers List<je...@portals.apache.org>
>> Sent: Mon, April 19, 2010 4:46:00 PM
>> Subject: Re: edit_defaults
>>
>> On 04/19/2010 04:38 PM, Woonsan Ko wrote:
>> Hi
>> Ate/All,
>>
>>
>> ----- Original Message ----
>>> From:
>> Ate Douma<
>> href="mailto:ate@douma.nu">ate@douma.nu>
>>> To: Jetspeed
>> Developers List<
>> href="mailto:jetspeed-dev@portals.apache.org">jetspeed-dev@portals.apache.org>
>>>
>> Cc: Bridges Developers List<
>> ymailto="mailto:bridges-dev@portals.apache.org"
>> href="mailto:bridges-dev@portals.apache.org">bridges-dev@portals.apache.org>
>>>
>> Sent: Fri, April 9, 2010 1:18:02 PM
>>> Subject: Re:
>> edit_defaults
>>>
>>
>> I also committed an initial fix for
>> the
>>> GenericVelocityPortlet almost like what you proposed earlier on
>> this email (and
>>> which was the
>> trigger for all this),
>> see:
>>> http://issues.apache.org/jira/browse/PB-103
>>
>> I'm
>> leaving the root JIRA
>>> issue for this,
>> http://issues.apache.org/jira/browse/PB-98, open for now as
>>> there
>> still remains work to be done on
>> especially the bridges-site (only
>> the
>>> groundwork has been done so far) and pending possible migration
>> of other bridges
>>> like maybe the groovy
>> and
>> struts
>>> bridge.
>>
>> I think it would be better to move
>> out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply
>> add jruby or jython supports there as well as groovy in the similar way.
> I
>> think that could make sense from a *bridge* development/maintenance
>> POV.
>
> One thing to consider though is if the end-user of such a bridge
>> would want/need to use like all three scripting engines (groovy, jruby,
>>
> jython) at the same time?
> If not, bundling them all together might not be
>> optimal because of all the (runtime) dependencies being pulled in to support all
>> of them.
> In that case providing dedicated "engine" specific bridges only
>> needed that engine specific dependencies might be preferred.
>
> Maybe a more
>> abstract main "scripting-bridge" with specific implementation sub bridges (e.g.
>> groovy, jruby, etc.) could be done instead.
> Maybe something like how slf4j
>> works with separated back-end logging engine specific
>> implementations.
>
> Thanks for the response.
> I thought we could have *provided* dependencies for the physical scripting engine libraries.
> For example, if a user wants to use bridges-scripts with jruby, then the user should provide jruby runtime libraries.
> I thought this would make it simpler than having multiple projects for each scripting engine. This approach is the same way as springframework does for script beans support.
Yes, that would be a good solution too, I didn't think of that!
Great, I'm +1 on using that solution.
Ate
> I'm not sure what others feel like though.
>
> Regards,
>
> Woonsan
>
>
>
> Regards,
>
> Ate
>
>>
>> Kind
>> regards,
>>
>> Woonsan
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To
>> unsubscribe, e-mail:
>> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
>> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
>>
>> For additional commands, e-mail:
>> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
>> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To
>> unsubscribe, e-mail:
>> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
>> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
> For
>> additional commands, e-mail:
>> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
>> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by Woonsan Ko <wo...@yahoo.com>.
----- Original Message ----
> From: Ate Douma <at...@douma.nu>
> To: Jetspeed Developers List <je...@portals.apache.org>
> Sent: Mon, April 19, 2010 4:46:00 PM
> Subject: Re: edit_defaults
>
> On 04/19/2010 04:38 PM, Woonsan Ko wrote:
> Hi
> Ate/All,
>
>
> ----- Original Message ----
>> From:
> Ate Douma<
> href="mailto:ate@douma.nu">ate@douma.nu>
>> To: Jetspeed
> Developers List<
> href="mailto:jetspeed-dev@portals.apache.org">jetspeed-dev@portals.apache.org>
>>
> Cc: Bridges Developers List<
> ymailto="mailto:bridges-dev@portals.apache.org"
> href="mailto:bridges-dev@portals.apache.org">bridges-dev@portals.apache.org>
>>
> Sent: Fri, April 9, 2010 1:18:02 PM
>> Subject: Re:
> edit_defaults
>>
>
> I also committed an initial fix for
> the
>> GenericVelocityPortlet almost like what you proposed earlier on
> this email (and
>> which was the
> trigger for all this),
> see:
>> http://issues.apache.org/jira/browse/PB-103
>
> I'm
> leaving the root JIRA
>> issue for this,
> http://issues.apache.org/jira/browse/PB-98, open for now as
>> there
> still remains work to be done on
> especially the bridges-site (only
> the
>> groundwork has been done so far) and pending possible migration
> of other bridges
>> like maybe the groovy
> and
> struts
>> bridge.
>
> I think it would be better to move
> out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply
> add jruby or jython supports there as well as groovy in the similar way.
I
> think that could make sense from a *bridge* development/maintenance
> POV.
One thing to consider though is if the end-user of such a bridge
> would want/need to use like all three scripting engines (groovy, jruby,
>
jython) at the same time?
If not, bundling them all together might not be
> optimal because of all the (runtime) dependencies being pulled in to support all
> of them.
In that case providing dedicated "engine" specific bridges only
> needed that engine specific dependencies might be preferred.
Maybe a more
> abstract main "scripting-bridge" with specific implementation sub bridges (e.g.
> groovy, jruby, etc.) could be done instead.
Maybe something like how slf4j
> works with separated back-end logging engine specific
> implementations.
Thanks for the response.
I thought we could have *provided* dependencies for the physical scripting engine libraries.
For example, if a user wants to use bridges-scripts with jruby, then the user should provide jruby runtime libraries.
I thought this would make it simpler than having multiple projects for each scripting engine. This approach is the same way as springframework does for script beans support.
I'm not sure what others feel like though.
Regards,
Woonsan
Regards,
Ate
>
> Kind
> regards,
>
> Woonsan
>
>
>
>
>
> ---------------------------------------------------------------------
> To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
>
> For additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
For
> additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by Ate Douma <at...@douma.nu>.
On 04/19/2010 04:38 PM, Woonsan Ko wrote:
> Hi Ate/All,
>
>
> ----- Original Message ----
>> From: Ate Douma<at...@douma.nu>
>> To: Jetspeed Developers List<je...@portals.apache.org>
>> Cc: Bridges Developers List<br...@portals.apache.org>
>> Sent: Fri, April 9, 2010 1:18:02 PM
>> Subject: Re: edit_defaults
>>
>
> I also committed an initial fix for the
>> GenericVelocityPortlet almost like what you proposed earlier on this email (and
>> which was the
> trigger for all this), see:
>> http://issues.apache.org/jira/browse/PB-103
>
> I'm leaving the root JIRA
>> issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as
>> there still remains work to be done on
> especially the bridges-site (only the
>> groundwork has been done so far) and pending possible migration of other bridges
>> like maybe the groovy
> and struts
>> bridge.
>
> I think it would be better to move out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply add jruby or jython supports there as well as groovy in the similar way.
I think that could make sense from a *bridge* development/maintenance POV.
One thing to consider though is if the end-user of such a bridge would want/need to use like all three scripting engines (groovy, jruby,
jython) at the same time?
If not, bundling them all together might not be optimal because of all the (runtime) dependencies being pulled in to support all of them.
In that case providing dedicated "engine" specific bridges only needed that engine specific dependencies might be preferred.
Maybe a more abstract main "scripting-bridge" with specific implementation sub bridges (e.g. groovy, jruby, etc.) could be done instead.
Maybe something like how slf4j works with separated back-end logging engine specific implementations.
Regards,
Ate
>
> Kind regards,
>
> Woonsan
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by David Taylor <da...@bluesunrise.com>.
On Mon, Apr 19, 2010 at 4:38 PM, Woonsan Ko <wo...@yahoo.com> wrote:
> Hi Ate/All,
>
>
> ----- Original Message ----
>> From: Ate Douma <at...@douma.nu>
>> To: Jetspeed Developers List <je...@portals.apache.org>
>> Cc: Bridges Developers List <br...@portals.apache.org>
>> Sent: Fri, April 9, 2010 1:18:02 PM
>> Subject: Re: edit_defaults
>>
>
> I also committed an initial fix for the
>> GenericVelocityPortlet almost like what you proposed earlier on this email (and
>> which was the
> trigger for all this), see:
>> http://issues.apache.org/jira/browse/PB-103
>
> I'm leaving the root JIRA
>> issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as
>> there still remains work to be done on
> especially the bridges-site (only the
>> groundwork has been done so far) and pending possible migration of other bridges
>> like maybe the groovy
> and struts
>> bridge.
>
> I think it would be better to move out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply add jruby or jython supports there as well as groovy in the similar way.
>
sounds good, its either that or creating a jruby and jython bridges
separately, im fine with your proposal
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
Re: edit_defaults
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi Ate/All,
----- Original Message ----
> From: Ate Douma <at...@douma.nu>
> To: Jetspeed Developers List <je...@portals.apache.org>
> Cc: Bridges Developers List <br...@portals.apache.org>
> Sent: Fri, April 9, 2010 1:18:02 PM
> Subject: Re: edit_defaults
>
I also committed an initial fix for the
> GenericVelocityPortlet almost like what you proposed earlier on this email (and
> which was the
trigger for all this), see:
> http://issues.apache.org/jira/browse/PB-103
I'm leaving the root JIRA
> issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as
> there still remains work to be done on
especially the bridges-site (only the
> groundwork has been done so far) and pending possible migration of other bridges
> like maybe the groovy
and struts
> bridge.
I think it would be better to move out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply add jruby or jython supports there as well as groovy in the similar way.
Kind regards,
Woonsan
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
Re: edit_defaults
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi Ate/All,
----- Original Message ----
> From: Ate Douma <at...@douma.nu>
> To: Jetspeed Developers List <je...@portals.apache.org>
> Cc: Bridges Developers List <br...@portals.apache.org>
> Sent: Fri, April 9, 2010 1:18:02 PM
> Subject: Re: edit_defaults
>
I also committed an initial fix for the
> GenericVelocityPortlet almost like what you proposed earlier on this email (and
> which was the
trigger for all this), see:
> http://issues.apache.org/jira/browse/PB-103
I'm leaving the root JIRA
> issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as
> there still remains work to be done on
especially the bridges-site (only the
> groundwork has been done so far) and pending possible migration of other bridges
> like maybe the groovy
and struts
> bridge.
I think it would be better to move out the groovy bridge to /portals/bridges/trunk/bridges-scripts; We can simply add jruby or jython supports there as well as groovy in the similar way.
Kind regards,
Woonsan
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by Ate Douma <at...@douma.nu>.
On 04/09/2010 09:55 AM, Ate Douma wrote:
> On 04/09/2010 01:13 AM, David Sean Taylor wrote:
>> On Thu, Apr 8, 2010 at 4:06 PM, Ate Douma<at...@douma.nu> wrote:
>>> On 04/08/2010 06:17 AM, David Sean Taylor wrote:
>>>>
>>>> A minor complication to any portlets using the Velocity Bridge with
>>>> the edit_defaults auto switch, seems we need to patch the bridge in
>>>> GenericVelocityPortlet.java
>>>> And require another release of this bridge if we want to properly
>>>> support edit_defaults auto switch .....
>>>
>>> Maybe we should consider upgrading bridges also to use portals-pom and
>>> release using Nexus.
>>> If we combine that will separated and independent release versions
>>> for each
>>> bridges component like we now do with APA, e.g. start defining
>>> versions like
>>> bridges-common-1.0.5, bridges-velocity-1.0.5 etc. in APA JIRA, and
>>> have them
>>> all have their separate svn trunk/branches/tags folder, we could turn
>>> out a
>>> bridges-velocity-1.0.5 (and at least bridges-common-1.0.5 for proper
>>> Maven-2
>>> dependency resolution) pretty quickly.
>>> Doing the ground work starting with only bridges-common and
>>> bridges-velocity
>>> probably can be done in matter of hours.
>>> WDYT?
>>>
>> +1 on velocity and common bridges
> OK.
> Assuming lazy consensus on this for now then I'll start on this right away.
>
> Actually I already did some preliminary work locally and got things
> converted and working within half an hour :)
> The restructuring of svn itself probably will take most of the time.
> As I think these new bridges versions should all assume portlet 2.0
> runtime environments, we better bump their major version to indicate
> this, e.g. bridges-common-2.0 and bridges-velocity-2.0
>
> I plan to do the following:
> - create a PB JIRA issue for all this
> - create new PB JIRA versions bridges-pom-1.0, bridges-common-2.0,
> bridges-velocity-2.0 and bridges-site as a start
> - create a new portals svn site subproject for bridges and (start)
> moving the little bridges xdocs we have over (maven-2, no multiproject)
> - create new svn /bridges-pom, /bridges-common and /bridges-velocity
> project trees with their own trunk/branches/tags folders
> - create a new bridges-pom:1.0:pom project
> - move current bridges/trunk /common/* under /bridges-common/trunk and
> /velocity/* under bridges-velocity/trunk,
> - for commons and velocity, remove their maven-1 configurations *and*
> their xdocs and update their maven-2 pom.xml
> - adjust the current bridges/trunk maven-1 and maven-2 projects to
> accomodate for these components been moved out
>
> All in all, this should take a few hours the most and allow us to
> release new bridges-pom, bridges-common and bridges-velocity shortly.
> Other bridges which qualify for updating and subsequent 2.x releases
> like maybe struts and groovy can follow later on.
I've completed most of the work now.
bridges-pom:1.0-SNAPSHOT:pom, portals-bridges-common:2.0-SNAPSHOT:jar and portals-bridges-velocity:2.0-SNAPSHOT:jar projects are now
available and already setup to build automatically on Hudson.
As soon as these initial Hudson builds are completed (pending), we can start upgrading our current bridges-common and bridges-velocity
dependencies in APA, J2-admin and Jetspeed itself.
I also committed an initial fix for the GenericVelocityPortlet almost like what you proposed earlier on this email (and which was the
trigger for all this), see: http://issues.apache.org/jira/browse/PB-103
I'm leaving the root JIRA issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as there still remains work to be done on
especially the bridges-site (only the groundwork has been done so far) and pending possible migration of other bridges like maybe the groovy
and struts bridge.
Regards,
Ate
>
> Regards,
>
> Ate
>>
>> I've only tested with the velocity bridge with regards to the
>> edit_defaults issue. Perhaps I should test some other bridges as
>> well....
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
Re: edit_defaults
Posted by Woonsan Ko <wo...@yahoo.com>.
+1 on your plan. Cool!
Woonsan
----- Original Message ----
> From: Ate Douma <at...@douma.nu>
> To: Jetspeed Developers List <je...@portals.apache.org>
> Cc: Bridges Developers List <br...@portals.apache.org>
> Sent: Fri, April 9, 2010 9:55:53 AM
> Subject: Re: edit_defaults
>
> On 04/09/2010 01:13 AM, David Sean Taylor wrote:
> On Thu, Apr 8, 2010 at
> 4:06 PM, Ate Douma<
> href="mailto:ate@douma.nu">ate@douma.nu> wrote:
>> On
> 04/08/2010 06:17 AM, David Sean Taylor wrote:
>>>
>>> A
> minor complication to any portlets using the Velocity Bridge
> with
>>> the edit_defaults auto switch, seems we need to patch the
> bridge in
>>> GenericVelocityPortlet.java
>>> And
> require another release of this bridge if we want to properly
>>>
> support edit_defaults auto switch .....
>>
>> Maybe we should
> consider upgrading bridges also to use portals-pom and
>> release using
> Nexus.
>> If we combine that will separated and independent release
> versions for each
>> bridges component like we now do with APA, e.g.
> start defining versions like
>> bridges-common-1.0.5,
> bridges-velocity-1.0.5 etc. in APA JIRA, and have them
>> all have
> their separate svn trunk/branches/tags folder, we could turn out a
>>
> bridges-velocity-1.0.5 (and at least bridges-common-1.0.5 for proper
> Maven-2
>> dependency resolution) pretty quickly.
>> Doing the
> ground work starting with only bridges-common and bridges-velocity
>>
> probably can be done in matter of hours.
>> WDYT?
>>
>
> +1 on velocity and common bridges
OK.
Assuming lazy consensus on this for
> now then I'll start on this right away.
Actually I already did some
> preliminary work locally and got things converted and working within half an
> hour :)
The restructuring of svn itself probably will take most of the
> time.
As I think these new bridges versions should all assume portlet 2.0
> runtime environments, we better bump their major version to indicate
this,
> e.g. bridges-common-2.0 and bridges-velocity-2.0
I plan to do the
> following:
- create a PB JIRA issue for all this
- create new PB JIRA
> versions bridges-pom-1.0, bridges-common-2.0, bridges-velocity-2.0 and
> bridges-site as a start
- create a new portals svn site subproject for
> bridges and (start) moving the little bridges xdocs we have over (maven-2, no
> multiproject)
- create new svn /bridges-pom, /bridges-common and
> /bridges-velocity project trees with their own trunk/branches/tags folders
-
> create a new bridges-pom:1.0:pom project
- move current bridges/trunk
> /common/* under /bridges-common/trunk and /velocity/* under
> bridges-velocity/trunk,
- for commons and velocity, remove their maven-1
> configurations *and* their xdocs and update their maven-2 pom.xml
- adjust
> the current bridges/trunk maven-1 and maven-2 projects to accomodate for these
> components been moved out
All in all, this should take a few hours the
> most and allow us to release new bridges-pom, bridges-common and
> bridges-velocity shortly.
Other bridges which qualify for updating and
> subsequent 2.x releases like maybe struts and groovy can follow later
> on.
Regards,
Ate
>
> I've only tested with the
> velocity bridge with regards to the
> edit_defaults issue. Perhaps I
> should test some other bridges as
> well....
>
>
> ---------------------------------------------------------------------
> To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
>
> For additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
For
> additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org
Re: edit_defaults
Posted by Woonsan Ko <wo...@yahoo.com>.
+1 on your plan. Cool!
Woonsan
----- Original Message ----
> From: Ate Douma <at...@douma.nu>
> To: Jetspeed Developers List <je...@portals.apache.org>
> Cc: Bridges Developers List <br...@portals.apache.org>
> Sent: Fri, April 9, 2010 9:55:53 AM
> Subject: Re: edit_defaults
>
> On 04/09/2010 01:13 AM, David Sean Taylor wrote:
> On Thu, Apr 8, 2010 at
> 4:06 PM, Ate Douma<
> href="mailto:ate@douma.nu">ate@douma.nu> wrote:
>> On
> 04/08/2010 06:17 AM, David Sean Taylor wrote:
>>>
>>> A
> minor complication to any portlets using the Velocity Bridge
> with
>>> the edit_defaults auto switch, seems we need to patch the
> bridge in
>>> GenericVelocityPortlet.java
>>> And
> require another release of this bridge if we want to properly
>>>
> support edit_defaults auto switch .....
>>
>> Maybe we should
> consider upgrading bridges also to use portals-pom and
>> release using
> Nexus.
>> If we combine that will separated and independent release
> versions for each
>> bridges component like we now do with APA, e.g.
> start defining versions like
>> bridges-common-1.0.5,
> bridges-velocity-1.0.5 etc. in APA JIRA, and have them
>> all have
> their separate svn trunk/branches/tags folder, we could turn out a
>>
> bridges-velocity-1.0.5 (and at least bridges-common-1.0.5 for proper
> Maven-2
>> dependency resolution) pretty quickly.
>> Doing the
> ground work starting with only bridges-common and bridges-velocity
>>
> probably can be done in matter of hours.
>> WDYT?
>>
>
> +1 on velocity and common bridges
OK.
Assuming lazy consensus on this for
> now then I'll start on this right away.
Actually I already did some
> preliminary work locally and got things converted and working within half an
> hour :)
The restructuring of svn itself probably will take most of the
> time.
As I think these new bridges versions should all assume portlet 2.0
> runtime environments, we better bump their major version to indicate
this,
> e.g. bridges-common-2.0 and bridges-velocity-2.0
I plan to do the
> following:
- create a PB JIRA issue for all this
- create new PB JIRA
> versions bridges-pom-1.0, bridges-common-2.0, bridges-velocity-2.0 and
> bridges-site as a start
- create a new portals svn site subproject for
> bridges and (start) moving the little bridges xdocs we have over (maven-2, no
> multiproject)
- create new svn /bridges-pom, /bridges-common and
> /bridges-velocity project trees with their own trunk/branches/tags folders
-
> create a new bridges-pom:1.0:pom project
- move current bridges/trunk
> /common/* under /bridges-common/trunk and /velocity/* under
> bridges-velocity/trunk,
- for commons and velocity, remove their maven-1
> configurations *and* their xdocs and update their maven-2 pom.xml
- adjust
> the current bridges/trunk maven-1 and maven-2 projects to accomodate for these
> components been moved out
All in all, this should take a few hours the
> most and allow us to release new bridges-pom, bridges-common and
> bridges-velocity shortly.
Other bridges which qualify for updating and
> subsequent 2.x releases like maybe struts and groovy can follow later
> on.
Regards,
Ate
>
> I've only tested with the
> velocity bridge with regards to the
> edit_defaults issue. Perhaps I
> should test some other bridges as
> well....
>
>
> ---------------------------------------------------------------------
> To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
>
> For additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
For
> additional commands, e-mail:
> ymailto="mailto:jetspeed-dev-help@portals.apache.org"
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: edit_defaults
Posted by Ate Douma <at...@douma.nu>.
On 04/09/2010 09:55 AM, Ate Douma wrote:
> On 04/09/2010 01:13 AM, David Sean Taylor wrote:
>> On Thu, Apr 8, 2010 at 4:06 PM, Ate Douma<at...@douma.nu> wrote:
>>> On 04/08/2010 06:17 AM, David Sean Taylor wrote:
>>>>
>>>> A minor complication to any portlets using the Velocity Bridge with
>>>> the edit_defaults auto switch, seems we need to patch the bridge in
>>>> GenericVelocityPortlet.java
>>>> And require another release of this bridge if we want to properly
>>>> support edit_defaults auto switch .....
>>>
>>> Maybe we should consider upgrading bridges also to use portals-pom and
>>> release using Nexus.
>>> If we combine that will separated and independent release versions
>>> for each
>>> bridges component like we now do with APA, e.g. start defining
>>> versions like
>>> bridges-common-1.0.5, bridges-velocity-1.0.5 etc. in APA JIRA, and
>>> have them
>>> all have their separate svn trunk/branches/tags folder, we could turn
>>> out a
>>> bridges-velocity-1.0.5 (and at least bridges-common-1.0.5 for proper
>>> Maven-2
>>> dependency resolution) pretty quickly.
>>> Doing the ground work starting with only bridges-common and
>>> bridges-velocity
>>> probably can be done in matter of hours.
>>> WDYT?
>>>
>> +1 on velocity and common bridges
> OK.
> Assuming lazy consensus on this for now then I'll start on this right away.
>
> Actually I already did some preliminary work locally and got things
> converted and working within half an hour :)
> The restructuring of svn itself probably will take most of the time.
> As I think these new bridges versions should all assume portlet 2.0
> runtime environments, we better bump their major version to indicate
> this, e.g. bridges-common-2.0 and bridges-velocity-2.0
>
> I plan to do the following:
> - create a PB JIRA issue for all this
> - create new PB JIRA versions bridges-pom-1.0, bridges-common-2.0,
> bridges-velocity-2.0 and bridges-site as a start
> - create a new portals svn site subproject for bridges and (start)
> moving the little bridges xdocs we have over (maven-2, no multiproject)
> - create new svn /bridges-pom, /bridges-common and /bridges-velocity
> project trees with their own trunk/branches/tags folders
> - create a new bridges-pom:1.0:pom project
> - move current bridges/trunk /common/* under /bridges-common/trunk and
> /velocity/* under bridges-velocity/trunk,
> - for commons and velocity, remove their maven-1 configurations *and*
> their xdocs and update their maven-2 pom.xml
> - adjust the current bridges/trunk maven-1 and maven-2 projects to
> accomodate for these components been moved out
>
> All in all, this should take a few hours the most and allow us to
> release new bridges-pom, bridges-common and bridges-velocity shortly.
> Other bridges which qualify for updating and subsequent 2.x releases
> like maybe struts and groovy can follow later on.
I've completed most of the work now.
bridges-pom:1.0-SNAPSHOT:pom, portals-bridges-common:2.0-SNAPSHOT:jar and portals-bridges-velocity:2.0-SNAPSHOT:jar projects are now
available and already setup to build automatically on Hudson.
As soon as these initial Hudson builds are completed (pending), we can start upgrading our current bridges-common and bridges-velocity
dependencies in APA, J2-admin and Jetspeed itself.
I also committed an initial fix for the GenericVelocityPortlet almost like what you proposed earlier on this email (and which was the
trigger for all this), see: http://issues.apache.org/jira/browse/PB-103
I'm leaving the root JIRA issue for this, http://issues.apache.org/jira/browse/PB-98, open for now as there still remains work to be done on
especially the bridges-site (only the groundwork has been done so far) and pending possible migration of other bridges like maybe the groovy
and struts bridge.
Regards,
Ate
>
> Regards,
>
> Ate
>>
>> I've only tested with the velocity bridge with regards to the
>> edit_defaults issue. Perhaps I should test some other bridges as
>> well....
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org