Nabble - RIFE - dev

Lets flirt or...

2009-09-25T00:57:15Z

Hello to group, Im new here.
Life is boring and uninteresting, entertain me :)

Lets flirt or maybe something more?
Im here:
http://camelliaelfr.150m.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-09T14:30:33Z

Hi Geert,

You're welcome! :)

These will be really nice to have for ongoing development. :)

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hi Josh,
>
> Looks all very good! Thanks!
>
> Take care,
>
> Geert
>
> On 09 Oct 2008, at 20:45, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> I've created two branches:
>> http://svn.rifers.org/rife/branches/maintenance-1.5.x/
>> http://svn.rifers.org/rife/branches/maintenance-1.6.x/
>>
>> They are based off of tags/release-1.5.1 and tags/release-1.6.1,
>> respectively.
>>
>> For reference, the command I used for the 1.6.x branch is:
>> $ svn copy http://svn.rifers.org/rife/tags/release-1.6.1
>> http://svn.rifers.org/rife/branches/maintenance-1.6.x -m "Maintenance
>> branch for 1.6.x."
>>
>> On my system here (Windows XP), I additionally needed to specify the
>> '--username' option.
>>
>> I haven't made any changes to them yet. Soon I will go begin porting
>> fixes from trunk to the 1.6.x branch.
>>
>> All the best,
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>>
>> Josh Hansen wrote:
>>> Hi Geert,
>>>
>>> Ok. Sounds good. :) BTW, I'll go with "maintenance-1.6.x" (note the
>>> "x") since the branch will cover all bugfix releases of a given minor
>>> version.
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>>>
>>> Geert Bevin wrote:
>>>> Hi Josh,
>>>>
>>>> I don't feel much like changing all existing tags. So imho,
>>>> "maintenance-1.6.1" is the best for branches. This also has the
>>>> advantage to clearly separate maintenance branches from other
>>>> branches.
>>>>
>>>> Take care,
>>>>
>>>> Geert
>>>>
>>>> On 08 Oct 2008, at 11:07, Josh Hansen wrote:
>>>>
>>>>> Hi Geert,
>>>>>
>>>>> If it were all up to me (uh oh -- watch out!), I was thinking
>>>>> that it
>>>>> would be nice to go with simply "1.5.x", and then switch the naming
>>>>> scheme for tags over to match (i.e. "1.5.1"). :) The rationale
>>>>> would be:
>>>>> * Less typing / shorter URLs.
>>>>>
>>>>> * Consistent w/ Subversion's own development scheme.
>>>>> I looked at three different projects (Subversion, Tomcat, and
>>>>> Jetty),
>>>>> and none of them were consistent [with each other]. Subversion and
>>>>> Jetty were closest.
>>>>>
>>>>> * They are automatically listed first when viewing the tree.
>>>>> This is pretty handy where there are a many branches, such as
>>>>> feature
>>>>> branches or developer branches. An example of this is the
>>>>> Subversion
>>>>> branch list:
>>>>> http://svn.collab.net/repos/svn/branches/
>>>>>
>>>>> On the whole either scheme would work and "maintenance-1.6.x" is
>>>>> more
>>>>> descriptive.
>>>>>
>>>>> Feeling swayed or convinced one way or another? :)
>>>>>
>>>>> Josh
>>>>> --
>>>>> Joshua Hansen
>>>>> Up Bear Enterprises
>>>>> (541) 760-7685
>>>>>
>>>>>
>>>>> Geert Bevin wrote:
>>>>>> Hi Josh,
>>>>>>
>>>>>> I never really thought about it, but I quite like
>>>>>> "maintenance-1.6.1".
>>>>>> What's your preference?
>>>>>>
>>>>>> Take care,
>>>>>>
>>>>>> Geert
>>>>>>
>>>>>> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>>>>>>
>>>>>>> Hi Geert,
>>>>>>>
>>>>>>> Ok. I'm ready to create the branches.
>>>>>>>
>>>>>>> One question:
>>>>>>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>>>>>>> "release-1.6.1", etc. For branches, do you have a preference or
>>>>>>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>>>>>>> simply
>>>>>>> "1.6.x", or something else entirely?
>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>
>>>>>>> As an example, the subversion project itself uses simple version
>>>>>>> numbers
>>>>>>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>>>>>>> http://svn.collab.net/repos/svn/branches/
>>>>>>> http://svn.collab.net/repos/svn/tags/
>>>>>>>
>>>>>>> Josh
>>>>>>> --
>>>>>>> Joshua Hansen
>>>>>>> Up Bear Enterprises
>>>>>>> (541) 760-7685
>>>>>>>
>>>>>>>
>>>>>>> Geert Bevin wrote:
>>>>>>>> Hi Joshua,
>>>>>>>>
>>>>>>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>>>>>>> responsibly! :)
>>>>>>>> I'm sure you will, you've shown great involvement and
>>>>>>>> responsibility
>>>>>>>> before :-)
>>>>>>>>
>>>>>>>>> Good to know about trunk and 1.7. I'll create branches for at
>>>>>>>>> least
>>>>>>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>>>>>>> Sounds good, thanks!
>>>>>>>>
>>>>>>>> Take care,
>>>>>>>>
>>>>>>>> Geert
>>>>>>>>
>>>>>>>>> All the best,
>>>>>>>>>
>>>>>>>>> Josh
>>>>>>>>> --
>>>>>>>>> Joshua Hansen
>>>>>>>>> Up Bear Enterprises
>>>>>>>>> (541) 760-7685
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Geert Bevin wrote:
>>>>>>>>>> Hey Josh,
>>>>>>>>>>
>>>>>>>>>> development for 1.7 has been happening in trunk. However,
>>>>>>>>>> since
>>>>>>>>>> I've
>>>>>>>>>> been the only one working on RIFE for quite a while and I've
>>>>>>>>>> had
>>>>>>>>>> barely time to do some 1.7 stuff, I never created any
>>>>>>>>>> maintenance
>>>>>>>>>> branches. You've given you commit rights to all of
>>>>>>>>>> svn.rifers.org.
>>>>>>>>>> You
>>>>>>>>>> should be able to create a maintenance branch for the
>>>>>>>>>> release you
>>>>>>>>>> want
>>>>>>>>>> to work on and commit your changes. After that, you can
>>>>>>>>>> merge the
>>>>>>>>>> diffs into trunk. Does that work for you?
>>>>>>>>>>
>>>>>>>>>> Take care,
>>>>>>>>>>
>>>>>>>>>> Geert
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Geert,
>>>>>>>>>>>
>>>>>>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>>>>>>> seems to
>>>>>>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Josh
>>>>>>>>>>> --
>>>>>>>>>>> Joshua Hansen
>>>>>>>>>>> Up Bear Enterprises
>>>>>>>>>>> (541) 760-7685
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Josh Hansen wrote:
>>>>>>>>>>>> Hi Geert,
>>>>>>>>>>>>
>>>>>>>>>>>> I'd like to do a little development and bug fixing against
>>>>>>>>>>>> the
>>>>>>>>>>>> 1.6.x
>>>>>>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>>>>>>
>>>>>>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>>>>>>> version, but
>>>>>>>>>>>> no branches (other than i18n):
>>>>>>>>>>>> http://svn.rifers.org/
>>>>>>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>>>>>>
>>>>>>>>>>>> Should I just code against the tagged versions (1.5.1 and
>>>>>>>>>>>> 1.6.1)
>>>>>>>>>>>> and
>>>>>>>>>>>> send you the diffs?
>>>>>>>>>>>>
>>>>>>>>>>>> Some branches for bugfix development on releases would be
>>>>>>>>>>>> nice... :)
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Josh
>>>>>>>>>>>> --
>>>>>>>>>>>> Joshua Hansen
>>>>>>>>>>>> Up Bear Enterprises
>>>>>>>>>>>> (541) 760-7685
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Geert Bevin
>>>>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>>>>> Music and words - http://gbevin.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Geert Bevin
>>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>>> Music and words - http://gbevin.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Geert Bevin
>>>>>> Terracotta - http://www.terracotta.org
>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>> RIFE Java application framework - http://rifers.org
>>>>>> Music and words - http://gbevin.com
>>>>>>
>>>>>>
>>>> --
>>>> Geert Bevin
>>>> Terracotta - http://www.terracotta.org
>>>> Uwyn "Use what you need" - http://uwyn.com
>>>> RIFE Java application framework - http://rifers.org
>>>> Music and words - http://gbevin.com
>>>>
>>>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Version number change on trunk and 1.6.x

2008-10-09T14:19:50Z

Oh yeah -- I've also begun merging changes from trunk to 1.6.x, so the
1.6.2-snapshot is an appropriate name. :)

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Josh Hansen wrote:

> Hi Geert,
>
> I've updated the version on the trunk from '1.6.2-snapshot' to
> '1.7.0-snapshot'.
>
> I've updated the version on branches/maintenance-1.6.x from '1.6.1' to
> '1.6.2-snapshot'.
>
> Whatever system is used to generate snapshots will need to be updated to
> include the branches now, so there should be at least three sets of
> snapshots:
> * trunk (1.7.0-snapshot)
> * branches/maintenance-1.6.x (1.6.2-snapshot)
> * branches/maintenance-1.5.x (1.5.1 -- no changes on this branch yet)
>
> Finally, since "1.6.2-snapshot" was used for a several snapshots on the
> trunk, a note should be added to the snapshots directory something like:
> README-rife-1.6.2_and_later_snapshots.txt:
> -----------------
> RIFE 1.6.2 snapshots 20080712, 20080731, and 20080801 actually include
> 1.7.0 features. For continuing snapshots with 1.7.0 features, see the
> 1.7.0 snapshots.
>
> All other RIFE 1.6.x snapshots do NOT include 1.7.0 features, and rather
> only include bug fixes or minor enhancements to the RIFE 1.6 branch.
>
> Joshua Hansen
> joshuah@...
> 9 Oct 2008
> Mailing list:
> rife-dev@...
> -----------------
>
> All the best,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-09T14:14:40Z

Hi Josh,

Looks all very good! Thanks!

Take care,

Geert

On 09 Oct 2008, at 20:45, Josh Hansen wrote:

>
> Hi Geert,
>
> I've created two branches:
> http://svn.rifers.org/rife/branches/maintenance-1.5.x/
> http://svn.rifers.org/rife/branches/maintenance-1.6.x/
>
> They are based off of tags/release-1.5.1 and tags/release-1.6.1,
> respectively.
>
> For reference, the command I used for the 1.6.x branch is:
> $ svn copy http://svn.rifers.org/rife/tags/release-1.6.1
> http://svn.rifers.org/rife/branches/maintenance-1.6.x -m "Maintenance
> branch for 1.6.x."
>
> On my system here (Windows XP), I additionally needed to specify the
> '--username' option.
>
> I haven't made any changes to them yet. Soon I will go begin porting
> fixes from trunk to the 1.6.x branch.
>
> All the best,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
>
> Josh Hansen wrote:
>> Hi Geert,
>>
>> Ok. Sounds good. :) BTW, I'll go with "maintenance-1.6.x" (note the
>> "x") since the branch will cover all bugfix releases of a given minor
>> version.
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>> Geert Bevin wrote:
>>> Hi Josh,
>>>
>>> I don't feel much like changing all existing tags. So imho,
>>> "maintenance-1.6.1" is the best for branches. This also has the
>>> advantage to clearly separate maintenance branches from other
>>> branches.
>>>
>>> Take care,
>>>
>>> Geert
>>>
>>> On 08 Oct 2008, at 11:07, Josh Hansen wrote:
>>>
>>>> Hi Geert,
>>>>
>>>> If it were all up to me (uh oh -- watch out!), I was thinking
>>>> that it
>>>> would be nice to go with simply "1.5.x", and then switch the naming
>>>> scheme for tags over to match (i.e. "1.5.1"). :) The rationale
>>>> would be:
>>>> * Less typing / shorter URLs.
>>>>
>>>> * Consistent w/ Subversion's own development scheme.
>>>> I looked at three different projects (Subversion, Tomcat, and
>>>> Jetty),
>>>> and none of them were consistent [with each other]. Subversion and
>>>> Jetty were closest.
>>>>
>>>> * They are automatically listed first when viewing the tree.
>>>> This is pretty handy where there are a many branches, such as
>>>> feature
>>>> branches or developer branches. An example of this is the
>>>> Subversion
>>>> branch list:
>>>> http://svn.collab.net/repos/svn/branches/
>>>>
>>>> On the whole either scheme would work and "maintenance-1.6.x" is
>>>> more
>>>> descriptive.
>>>>
>>>> Feeling swayed or convinced one way or another? :)
>>>>
>>>> Josh
>>>> --
>>>> Joshua Hansen
>>>> Up Bear Enterprises
>>>> (541) 760-7685
>>>>
>>>>
>>>> Geert Bevin wrote:
>>>>> Hi Josh,
>>>>>
>>>>> I never really thought about it, but I quite like
>>>>> "maintenance-1.6.1".
>>>>> What's your preference?
>>>>>
>>>>> Take care,
>>>>>
>>>>> Geert
>>>>>
>>>>> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>>>>>
>>>>>> Hi Geert,
>>>>>>
>>>>>> Ok. I'm ready to create the branches.
>>>>>>
>>>>>> One question:
>>>>>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>>>>>> "release-1.6.1", etc. For branches, do you have a preference or
>>>>>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>>>>>> simply
>>>>>> "1.6.x", or something else entirely?
>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>
>>>>>> As an example, the subversion project itself uses simple version
>>>>>> numbers
>>>>>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>>>>>> http://svn.collab.net/repos/svn/branches/
>>>>>> http://svn.collab.net/repos/svn/tags/
>>>>>>
>>>>>> Josh
>>>>>> --
>>>>>> Joshua Hansen
>>>>>> Up Bear Enterprises
>>>>>> (541) 760-7685
>>>>>>
>>>>>>
>>>>>> Geert Bevin wrote:
>>>>>>> Hi Joshua,
>>>>>>>
>>>>>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>>>>>> responsibly! :)
>>>>>>> I'm sure you will, you've shown great involvement and
>>>>>>> responsibility
>>>>>>> before :-)
>>>>>>>
>>>>>>>> Good to know about trunk and 1.7. I'll create branches for at
>>>>>>>> least
>>>>>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>>>>>> Sounds good, thanks!
>>>>>>>
>>>>>>> Take care,
>>>>>>>
>>>>>>> Geert
>>>>>>>
>>>>>>>> All the best,
>>>>>>>>
>>>>>>>> Josh
>>>>>>>> --
>>>>>>>> Joshua Hansen
>>>>>>>> Up Bear Enterprises
>>>>>>>> (541) 760-7685
>>>>>>>>
>>>>>>>>
>>>>>>>> Geert Bevin wrote:
>>>>>>>>> Hey Josh,
>>>>>>>>>
>>>>>>>>> development for 1.7 has been happening in trunk. However,
>>>>>>>>> since
>>>>>>>>> I've
>>>>>>>>> been the only one working on RIFE for quite a while and I've
>>>>>>>>> had
>>>>>>>>> barely time to do some 1.7 stuff, I never created any
>>>>>>>>> maintenance
>>>>>>>>> branches. You've given you commit rights to all of
>>>>>>>>> svn.rifers.org.
>>>>>>>>> You
>>>>>>>>> should be able to create a maintenance branch for the
>>>>>>>>> release you
>>>>>>>>> want
>>>>>>>>> to work on and commit your changes. After that, you can
>>>>>>>>> merge the
>>>>>>>>> diffs into trunk. Does that work for you?
>>>>>>>>>
>>>>>>>>> Take care,
>>>>>>>>>
>>>>>>>>> Geert
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>>>>>
>>>>>>>>>> Hi Geert,
>>>>>>>>>>
>>>>>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>>>>>> seems to
>>>>>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Josh
>>>>>>>>>> --
>>>>>>>>>> Joshua Hansen
>>>>>>>>>> Up Bear Enterprises
>>>>>>>>>> (541) 760-7685
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Josh Hansen wrote:
>>>>>>>>>>> Hi Geert,
>>>>>>>>>>>
>>>>>>>>>>> I'd like to do a little development and bug fixing against
>>>>>>>>>>> the
>>>>>>>>>>> 1.6.x
>>>>>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>>>>>
>>>>>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>>>>>> version, but
>>>>>>>>>>> no branches (other than i18n):
>>>>>>>>>>> http://svn.rifers.org/
>>>>>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>>>>>
>>>>>>>>>>> Should I just code against the tagged versions (1.5.1 and
>>>>>>>>>>> 1.6.1)
>>>>>>>>>>> and
>>>>>>>>>>> send you the diffs?
>>>>>>>>>>>
>>>>>>>>>>> Some branches for bugfix development on releases would be
>>>>>>>>>>> nice... :)
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Josh
>>>>>>>>>>> --
>>>>>>>>>>> Joshua Hansen
>>>>>>>>>>> Up Bear Enterprises
>>>>>>>>>>> (541) 760-7685
>>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Geert Bevin
>>>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>>>> Music and words - http://gbevin.com
>>>>>>>>>
>>>>>>>>>
>>>>>>> --
>>>>>>> Geert Bevin
>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>> Music and words - http://gbevin.com
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Geert Bevin
>>>>> Terracotta - http://www.terracotta.org
>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>> RIFE Java application framework - http://rifers.org
>>>>> Music and words - http://gbevin.com
>>>>>
>>>>>
>>> --
>>> Geert Bevin
>>> Terracotta - http://www.terracotta.org
>>> Uwyn "Use what you need" - http://uwyn.com
>>> RIFE Java application framework - http://rifers.org
>>> Music and words - http://gbevin.com
>>>
>>>
>>
>>>
>>
>
> >

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: rifers.org says reflects old CDDL/LGPL licensing rather than new Apache 2.0 licensing

2008-10-09T14:02:32Z

Hi Geert,

Whoops -- forgot it has been that long since a release. :)

It is an exciting change! I've been agonizing about some different
changes due to the CDDL/LGPL license.

All the best,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Yeah, I know, that's because there hasn't been a real release with the
> Apache 2.0 license yet. I know ... I'm a slacker :-/
>
> On 09 Oct 2008, at 22:31, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> The website still reflects the old licensing under CDDL/LGPL licensing
>> rather than new Apache 2.0 licensing.
>> http://www.rifers.org/license
>>
>> I'm personally excited that the project is licensed under the more
>> "liberal" Apache 2.0, and I had forgotten about this change until I
>> started merging fixes from the trunk to the maintenance branch.
>>
>> The SVN file to update is here:
>> http://svn.rifers.org/rifers/trunk/src/templates/pub/license.html
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Version number change on trunk and 1.6.x

2008-10-09T14:00:19Z

Hi Geert,

I've updated the version on the trunk from '1.6.2-snapshot' to
'1.7.0-snapshot'.

I've updated the version on branches/maintenance-1.6.x from '1.6.1' to
'1.6.2-snapshot'.

Whatever system is used to generate snapshots will need to be updated to
include the branches now, so there should be at least three sets of
snapshots:
* trunk (1.7.0-snapshot)
* branches/maintenance-1.6.x (1.6.2-snapshot)
* branches/maintenance-1.5.x (1.5.1 -- no changes on this branch yet)

Finally, since "1.6.2-snapshot" was used for a several snapshots on the
trunk, a note should be added to the snapshots directory something like:
README-rife-1.6.2_and_later_snapshots.txt:
-----------------
RIFE 1.6.2 snapshots 20080712, 20080731, and 20080801 actually include
1.7.0 features. For continuing snapshots with 1.7.0 features, see the
1.7.0 snapshots.

All other RIFE 1.6.x snapshots do NOT include 1.7.0 features, and rather
only include bug fixes or minor enhancements to the RIFE 1.6 branch.

Joshua Hansen
joshuah@...
9 Oct 2008
Mailing list:
rife-dev@...
-----------------

All the best,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: rifers.org says reflects old CDDL/LGPL licensing rather than new Apache 2.0 licensing

2008-10-09T13:50:53Z

Yeah, I know, that's because there hasn't been a real release with the
Apache 2.0 license yet. I know ... I'm a slacker :-/

On 09 Oct 2008, at 22:31, Josh Hansen wrote:

>
> Hi Geert,
>
> The website still reflects the old licensing under CDDL/LGPL licensing
> rather than new Apache 2.0 licensing.
> http://www.rifers.org/license
>
> I'm personally excited that the project is licensed under the more
> "liberal" Apache 2.0, and I had forgotten about this change until I
> started merging fixes from the trunk to the maintenance branch.
>
> The SVN file to update is here:
> http://svn.rifers.org/rifers/trunk/src/templates/pub/license.html
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
> >

rifers.org says reflects old CDDL/LGPL licensing rather than new Apache 2.0 licensing

2008-10-09T13:31:50Z

Hi Geert,

The website still reflects the old licensing under CDDL/LGPL licensing
rather than new Apache 2.0 licensing.
http://www.rifers.org/license

I'm personally excited that the project is licensed under the more
"liberal" Apache 2.0, and I had forgotten about this change until I
started merging fixes from the trunk to the maintenance branch.

The SVN file to update is here:
http://svn.rifers.org/rifers/trunk/src/templates/pub/license.html

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-09T11:45:30Z

Hi Geert,

I've created two branches:
http://svn.rifers.org/rife/branches/maintenance-1.5.x/
http://svn.rifers.org/rife/branches/maintenance-1.6.x/

They are based off of tags/release-1.5.1 and tags/release-1.6.1,
respectively.

For reference, the command I used for the 1.6.x branch is:
$ svn copy http://svn.rifers.org/rife/tags/release-1.6.1
http://svn.rifers.org/rife/branches/maintenance-1.6.x -m "Maintenance
branch for 1.6.x."

On my system here (Windows XP), I additionally needed to specify the
'--username' option.

I haven't made any changes to them yet. Soon I will go begin porting
fixes from trunk to the 1.6.x branch.

All the best,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Josh Hansen wrote:

> Hi Geert,
>
> Ok. Sounds good. :) BTW, I'll go with "maintenance-1.6.x" (note the
> "x") since the branch will cover all bugfix releases of a given minor
> version.
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
> Geert Bevin wrote:
>> Hi Josh,
>>
>> I don't feel much like changing all existing tags. So imho,
>> "maintenance-1.6.1" is the best for branches. This also has the
>> advantage to clearly separate maintenance branches from other branches.
>>
>> Take care,
>>
>> Geert
>>
>> On 08 Oct 2008, at 11:07, Josh Hansen wrote:
>>
>>> Hi Geert,
>>>
>>> If it were all up to me (uh oh -- watch out!), I was thinking that it
>>> would be nice to go with simply "1.5.x", and then switch the naming
>>> scheme for tags over to match (i.e. "1.5.1"). :) The rationale
>>> would be:
>>> * Less typing / shorter URLs.
>>>
>>> * Consistent w/ Subversion's own development scheme.
>>> I looked at three different projects (Subversion, Tomcat, and Jetty),
>>> and none of them were consistent [with each other]. Subversion and
>>> Jetty were closest.
>>>
>>> * They are automatically listed first when viewing the tree.
>>> This is pretty handy where there are a many branches, such as feature
>>> branches or developer branches. An example of this is the Subversion
>>> branch list:
>>> http://svn.collab.net/repos/svn/branches/
>>>
>>> On the whole either scheme would work and "maintenance-1.6.x" is more
>>> descriptive.
>>>
>>> Feeling swayed or convinced one way or another? :)
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>>>
>>> Geert Bevin wrote:
>>>> Hi Josh,
>>>>
>>>> I never really thought about it, but I quite like
>>>> "maintenance-1.6.1".
>>>> What's your preference?
>>>>
>>>> Take care,
>>>>
>>>> Geert
>>>>
>>>> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>>>>
>>>>> Hi Geert,
>>>>>
>>>>> Ok. I'm ready to create the branches.
>>>>>
>>>>> One question:
>>>>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>>>>> "release-1.6.1", etc. For branches, do you have a preference or
>>>>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>>>>> simply
>>>>> "1.6.x", or something else entirely?
>>>>> http://svn.rifers.org/rife/tags/
>>>>>
>>>>> As an example, the subversion project itself uses simple version
>>>>> numbers
>>>>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>>>>> http://svn.collab.net/repos/svn/branches/
>>>>> http://svn.collab.net/repos/svn/tags/
>>>>>
>>>>> Josh
>>>>> --
>>>>> Joshua Hansen
>>>>> Up Bear Enterprises
>>>>> (541) 760-7685
>>>>>
>>>>>
>>>>> Geert Bevin wrote:
>>>>>> Hi Joshua,
>>>>>>
>>>>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>>>>> responsibly! :)
>>>>>> I'm sure you will, you've shown great involvement and
>>>>>> responsibility
>>>>>> before :-)
>>>>>>
>>>>>>> Good to know about trunk and 1.7. I'll create branches for at
>>>>>>> least
>>>>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>>>>> Sounds good, thanks!
>>>>>>
>>>>>> Take care,
>>>>>>
>>>>>> Geert
>>>>>>
>>>>>>> All the best,
>>>>>>>
>>>>>>> Josh
>>>>>>> --
>>>>>>> Joshua Hansen
>>>>>>> Up Bear Enterprises
>>>>>>> (541) 760-7685
>>>>>>>
>>>>>>>
>>>>>>> Geert Bevin wrote:
>>>>>>>> Hey Josh,
>>>>>>>>
>>>>>>>> development for 1.7 has been happening in trunk. However, since
>>>>>>>> I've
>>>>>>>> been the only one working on RIFE for quite a while and I've had
>>>>>>>> barely time to do some 1.7 stuff, I never created any maintenance
>>>>>>>> branches. You've given you commit rights to all of
>>>>>>>> svn.rifers.org.
>>>>>>>> You
>>>>>>>> should be able to create a maintenance branch for the release you
>>>>>>>> want
>>>>>>>> to work on and commit your changes. After that, you can merge the
>>>>>>>> diffs into trunk. Does that work for you?
>>>>>>>>
>>>>>>>> Take care,
>>>>>>>>
>>>>>>>> Geert
>>>>>>>>
>>>>>>>>
>>>>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>>>>
>>>>>>>>> Hi Geert,
>>>>>>>>>
>>>>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>>>>> seems to
>>>>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Josh
>>>>>>>>> --
>>>>>>>>> Joshua Hansen
>>>>>>>>> Up Bear Enterprises
>>>>>>>>> (541) 760-7685
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Josh Hansen wrote:
>>>>>>>>>> Hi Geert,
>>>>>>>>>>
>>>>>>>>>> I'd like to do a little development and bug fixing against the
>>>>>>>>>> 1.6.x
>>>>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>>>>
>>>>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>>>>> version, but
>>>>>>>>>> no branches (other than i18n):
>>>>>>>>>> http://svn.rifers.org/
>>>>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>>>>
>>>>>>>>>> Should I just code against the tagged versions (1.5.1 and
>>>>>>>>>> 1.6.1)
>>>>>>>>>> and
>>>>>>>>>> send you the diffs?
>>>>>>>>>>
>>>>>>>>>> Some branches for bugfix development on releases would be
>>>>>>>>>> nice... :)
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Josh
>>>>>>>>>> --
>>>>>>>>>> Joshua Hansen
>>>>>>>>>> Up Bear Enterprises
>>>>>>>>>> (541) 760-7685
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Geert Bevin
>>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>>> Music and words - http://gbevin.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Geert Bevin
>>>>>> Terracotta - http://www.terracotta.org
>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>> RIFE Java application framework - http://rifers.org
>>>>>> Music and words - http://gbevin.com
>>>>>>
>>>>>>
>>>> --
>>>> Geert Bevin
>>>> Terracotta - http://www.terracotta.org
>>>> Uwyn "Use what you need" - http://uwyn.com
>>>> RIFE Java application framework - http://rifers.org
>>>> Music and words - http://gbevin.com
>>>>
>>>>
>> --
>> Geert Bevin
>> Terracotta - http://www.terracotta.org
>> Uwyn "Use what you need" - http://uwyn.com
>> RIFE Java application framework - http://rifers.org
>> Music and words - http://gbevin.com
>>
>>
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-08T11:45:52Z

Hi Geert,

Ok. Sounds good. :) BTW, I'll go with "maintenance-1.6.x" (note the
"x") since the branch will cover all bugfix releases of a given minor
version.

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hi Josh,
>
> I don't feel much like changing all existing tags. So imho,
> "maintenance-1.6.1" is the best for branches. This also has the
> advantage to clearly separate maintenance branches from other branches.
>
> Take care,
>
> Geert
>
> On 08 Oct 2008, at 11:07, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> If it were all up to me (uh oh -- watch out!), I was thinking that it
>> would be nice to go with simply "1.5.x", and then switch the naming
>> scheme for tags over to match (i.e. "1.5.1"). :) The rationale
>> would be:
>> * Less typing / shorter URLs.
>>
>> * Consistent w/ Subversion's own development scheme.
>> I looked at three different projects (Subversion, Tomcat, and Jetty),
>> and none of them were consistent [with each other]. Subversion and
>> Jetty were closest.
>>
>> * They are automatically listed first when viewing the tree.
>> This is pretty handy where there are a many branches, such as feature
>> branches or developer branches. An example of this is the Subversion
>> branch list:
>> http://svn.collab.net/repos/svn/branches/
>>
>> On the whole either scheme would work and "maintenance-1.6.x" is more
>> descriptive.
>>
>> Feeling swayed or convinced one way or another? :)
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>> Geert Bevin wrote:
>>> Hi Josh,
>>>
>>> I never really thought about it, but I quite like
>>> "maintenance-1.6.1".
>>> What's your preference?
>>>
>>> Take care,
>>>
>>> Geert
>>>
>>> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>>>
>>>> Hi Geert,
>>>>
>>>> Ok. I'm ready to create the branches.
>>>>
>>>> One question:
>>>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>>>> "release-1.6.1", etc. For branches, do you have a preference or
>>>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>>>> simply
>>>> "1.6.x", or something else entirely?
>>>> http://svn.rifers.org/rife/tags/
>>>>
>>>> As an example, the subversion project itself uses simple version
>>>> numbers
>>>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>>>> http://svn.collab.net/repos/svn/branches/
>>>> http://svn.collab.net/repos/svn/tags/
>>>>
>>>> Josh
>>>> --
>>>> Joshua Hansen
>>>> Up Bear Enterprises
>>>> (541) 760-7685
>>>>
>>>>
>>>> Geert Bevin wrote:
>>>>> Hi Joshua,
>>>>>
>>>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>>>> responsibly! :)
>>>>> I'm sure you will, you've shown great involvement and
>>>>> responsibility
>>>>> before :-)
>>>>>
>>>>>> Good to know about trunk and 1.7. I'll create branches for at
>>>>>> least
>>>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>>>> Sounds good, thanks!
>>>>>
>>>>> Take care,
>>>>>
>>>>> Geert
>>>>>
>>>>>> All the best,
>>>>>>
>>>>>> Josh
>>>>>> --
>>>>>> Joshua Hansen
>>>>>> Up Bear Enterprises
>>>>>> (541) 760-7685
>>>>>>
>>>>>>
>>>>>> Geert Bevin wrote:
>>>>>>> Hey Josh,
>>>>>>>
>>>>>>> development for 1.7 has been happening in trunk. However, since
>>>>>>> I've
>>>>>>> been the only one working on RIFE for quite a while and I've had
>>>>>>> barely time to do some 1.7 stuff, I never created any maintenance
>>>>>>> branches. You've given you commit rights to all of
>>>>>>> svn.rifers.org.
>>>>>>> You
>>>>>>> should be able to create a maintenance branch for the release you
>>>>>>> want
>>>>>>> to work on and commit your changes. After that, you can merge the
>>>>>>> diffs into trunk. Does that work for you?
>>>>>>>
>>>>>>> Take care,
>>>>>>>
>>>>>>> Geert
>>>>>>>
>>>>>>>
>>>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>>>
>>>>>>>> Hi Geert,
>>>>>>>>
>>>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>>>> seems to
>>>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Josh
>>>>>>>> --
>>>>>>>> Joshua Hansen
>>>>>>>> Up Bear Enterprises
>>>>>>>> (541) 760-7685
>>>>>>>>
>>>>>>>>
>>>>>>>> Josh Hansen wrote:
>>>>>>>>> Hi Geert,
>>>>>>>>>
>>>>>>>>> I'd like to do a little development and bug fixing against the
>>>>>>>>> 1.6.x
>>>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>>>
>>>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>>>> version, but
>>>>>>>>> no branches (other than i18n):
>>>>>>>>> http://svn.rifers.org/
>>>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>>>
>>>>>>>>> Should I just code against the tagged versions (1.5.1 and
>>>>>>>>> 1.6.1)
>>>>>>>>> and
>>>>>>>>> send you the diffs?
>>>>>>>>>
>>>>>>>>> Some branches for bugfix development on releases would be
>>>>>>>>> nice... :)
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Josh
>>>>>>>>> --
>>>>>>>>> Joshua Hansen
>>>>>>>>> Up Bear Enterprises
>>>>>>>>> (541) 760-7685
>>>>>>>>>
>>>>>>> --
>>>>>>> Geert Bevin
>>>>>>> Terracotta - http://www.terracotta.org
>>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>>> RIFE Java application framework - http://rifers.org
>>>>>>> Music and words - http://gbevin.com
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Geert Bevin
>>>>> Terracotta - http://www.terracotta.org
>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>> RIFE Java application framework - http://rifers.org
>>>>> Music and words - http://gbevin.com
>>>>>
>>>>>
>>> --
>>> Geert Bevin
>>> Terracotta - http://www.terracotta.org
>>> Uwyn "Use what you need" - http://uwyn.com
>>> RIFE Java application framework - http://rifers.org
>>> Music and words - http://gbevin.com
>>>
>>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-08T11:08:39Z

Hi Josh,

I don't feel much like changing all existing tags. So imho,
"maintenance-1.6.1" is the best for branches. This also has the
advantage to clearly separate maintenance branches from other branches.

Take care,

Geert

On 08 Oct 2008, at 11:07, Josh Hansen wrote:

>
> Hi Geert,
>
> If it were all up to me (uh oh -- watch out!), I was thinking that it
> would be nice to go with simply "1.5.x", and then switch the naming
> scheme for tags over to match (i.e. "1.5.1"). :) The rationale
> would be:
> * Less typing / shorter URLs.
>
> * Consistent w/ Subversion's own development scheme.
> I looked at three different projects (Subversion, Tomcat, and Jetty),
> and none of them were consistent [with each other]. Subversion and
> Jetty were closest.
>
> * They are automatically listed first when viewing the tree.
> This is pretty handy where there are a many branches, such as feature
> branches or developer branches. An example of this is the Subversion
> branch list:
> http://svn.collab.net/repos/svn/branches/
>
> On the whole either scheme would work and "maintenance-1.6.x" is more
> descriptive.
>
> Feeling swayed or convinced one way or another? :)
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
> Geert Bevin wrote:
>> Hi Josh,
>>
>> I never really thought about it, but I quite like
>> "maintenance-1.6.1".
>> What's your preference?
>>
>> Take care,
>>
>> Geert
>>
>> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>>
>>> Hi Geert,
>>>
>>> Ok. I'm ready to create the branches.
>>>
>>> One question:
>>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>>> "release-1.6.1", etc. For branches, do you have a preference or
>>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>>> simply
>>> "1.6.x", or something else entirely?
>>> http://svn.rifers.org/rife/tags/
>>>
>>> As an example, the subversion project itself uses simple version
>>> numbers
>>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>>> http://svn.collab.net/repos/svn/branches/
>>> http://svn.collab.net/repos/svn/tags/
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>>>
>>> Geert Bevin wrote:
>>>> Hi Joshua,
>>>>
>>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>>> responsibly! :)
>>>> I'm sure you will, you've shown great involvement and
>>>> responsibility
>>>> before :-)
>>>>
>>>>> Good to know about trunk and 1.7. I'll create branches for at
>>>>> least
>>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>>> Sounds good, thanks!
>>>>
>>>> Take care,
>>>>
>>>> Geert
>>>>
>>>>> All the best,
>>>>>
>>>>> Josh
>>>>> --
>>>>> Joshua Hansen
>>>>> Up Bear Enterprises
>>>>> (541) 760-7685
>>>>>
>>>>>
>>>>> Geert Bevin wrote:
>>>>>> Hey Josh,
>>>>>>
>>>>>> development for 1.7 has been happening in trunk. However, since
>>>>>> I've
>>>>>> been the only one working on RIFE for quite a while and I've had
>>>>>> barely time to do some 1.7 stuff, I never created any maintenance
>>>>>> branches. You've given you commit rights to all of
>>>>>> svn.rifers.org.
>>>>>> You
>>>>>> should be able to create a maintenance branch for the release you
>>>>>> want
>>>>>> to work on and commit your changes. After that, you can merge the
>>>>>> diffs into trunk. Does that work for you?
>>>>>>
>>>>>> Take care,
>>>>>>
>>>>>> Geert
>>>>>>
>>>>>>
>>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>>
>>>>>>> Hi Geert,
>>>>>>>
>>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>>> seems to
>>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Josh
>>>>>>> --
>>>>>>> Joshua Hansen
>>>>>>> Up Bear Enterprises
>>>>>>> (541) 760-7685
>>>>>>>
>>>>>>>
>>>>>>> Josh Hansen wrote:
>>>>>>>> Hi Geert,
>>>>>>>>
>>>>>>>> I'd like to do a little development and bug fixing against the
>>>>>>>> 1.6.x
>>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>>
>>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>>> version, but
>>>>>>>> no branches (other than i18n):
>>>>>>>> http://svn.rifers.org/
>>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>>
>>>>>>>> Should I just code against the tagged versions (1.5.1 and
>>>>>>>> 1.6.1)
>>>>>>>> and
>>>>>>>> send you the diffs?
>>>>>>>>
>>>>>>>> Some branches for bugfix development on releases would be
>>>>>>>> nice... :)
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Josh
>>>>>>>> --
>>>>>>>> Joshua Hansen
>>>>>>>> Up Bear Enterprises
>>>>>>>> (541) 760-7685
>>>>>>>>
>>>>>> --
>>>>>> Geert Bevin
>>>>>> Terracotta - http://www.terracotta.org
>>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>>> RIFE Java application framework - http://rifers.org
>>>>>> Music and words - http://gbevin.com
>>>>>>
>>>>>>
>>>> --
>>>> Geert Bevin
>>>> Terracotta - http://www.terracotta.org
>>>> Uwyn "Use what you need" - http://uwyn.com
>>>> RIFE Java application framework - http://rifers.org
>>>> Music and words - http://gbevin.com
>>>>
>>>>
>>
>> --
>> Geert Bevin
>> Terracotta - http://www.terracotta.org
>> Uwyn "Use what you need" - http://uwyn.com
>> RIFE Java application framework - http://rifers.org
>> Music and words - http://gbevin.com
>>
>>
>>>
>>
>
> >

Re: Unsubscribe

2008-10-08T03:38:56Z

On 8 Oct 2008, at 09:43, Jay Jamba wrote:

Please give me the link.
i dont know the link to unsubscribe.

Send an email to rife-dev+unsubscribe@...

---

Understand that the right to choose your own path is a sacred privilege. Use it. Dwell in possibility. – Oprah Winfrey

Re: Unsubscribe

2008-10-08T03:01:31Z

On 8 Oct 2008, at 09:43, Jay Jamba wrote:

Please give me the link.
i dont know the link to unsubscribe.

Send an email to rife-dev+unsubscribe@...

---

Understand that the right to choose your own path is a sacred privilege. Use it. Dwell in possibility. – Oprah Winfrey

Re: Unsubscribe

2008-10-08T02:43:56Z

Please give me the link.

i dont know the link to unsubscribe.

----- Original Message ----
From: Emmanuel Okyere <eokyere@...>
To: rife-dev@...
Sent: Wednesday, 8 October, 2008 2:59:43 PM
Subject: Re: Unsubscribe

how about you do it youself? ;P

On 8 Oct 2008, at 09:20, Jay Jamba wrote:

Hi,

Unsubscribe me from this group.

Add more friends to your messenger and enjoy! Invite them now.

I think I could, if I only knew how to begin. - Alice, AiW

Add more friends to your messenger and enjoy! Invite them now.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Unsubscribe

2008-10-08T02:29:43Z

how about you do it youself? ;P

On 8 Oct 2008, at 09:20, Jay Jamba wrote:

Hi,
Unsubscribe me from this group.

Add more friends to your messenger and enjoy! Invite them now.

I think I could, if I only knew how to begin. - Alice, AiW

Unsubscribe

2008-10-08T02:20:09Z

Hi,

Unsubscribe me from this group.

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-08T02:07:35Z

Hi Geert,

If it were all up to me (uh oh -- watch out!), I was thinking that it
would be nice to go with simply "1.5.x", and then switch the naming
scheme for tags over to match (i.e. "1.5.1"). :) The rationale would be:
* Less typing / shorter URLs.

* Consistent w/ Subversion's own development scheme.
I looked at three different projects (Subversion, Tomcat, and Jetty),
and none of them were consistent [with each other]. Subversion and
Jetty were closest.

* They are automatically listed first when viewing the tree.
This is pretty handy where there are a many branches, such as feature
branches or developer branches. An example of this is the Subversion
branch list:
http://svn.collab.net/repos/svn/branches/

On the whole either scheme would work and "maintenance-1.6.x" is more
descriptive.

Feeling swayed or convinced one way or another? :)

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hi Josh,
>
> I never really thought about it, but I quite like "maintenance-1.6.1".
> What's your preference?
>
> Take care,
>
> Geert
>
> On 07 Oct 2008, at 23:45, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> Ok. I'm ready to create the branches.
>>
>> One question:
>> * The naming pattern in the 'tags' hierarchy is "release-1.6",
>> "release-1.6.1", etc. For branches, do you have a preference or
>> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
>> simply
>> "1.6.x", or something else entirely?
>> http://svn.rifers.org/rife/tags/
>>
>> As an example, the subversion project itself uses simple version
>> numbers
>> for both tags and branches ("1.5.1" and "1.5.x" respectively):
>> http://svn.collab.net/repos/svn/branches/
>> http://svn.collab.net/repos/svn/tags/
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>> Geert Bevin wrote:
>>> Hi Joshua,
>>>
>>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>>> responsibly! :)
>>> I'm sure you will, you've shown great involvement and responsibility
>>> before :-)
>>>
>>>> Good to know about trunk and 1.7. I'll create branches for at least
>>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>> Sounds good, thanks!
>>>
>>> Take care,
>>>
>>> Geert
>>>
>>>> All the best,
>>>>
>>>> Josh
>>>> --
>>>> Joshua Hansen
>>>> Up Bear Enterprises
>>>> (541) 760-7685
>>>>
>>>>
>>>> Geert Bevin wrote:
>>>>> Hey Josh,
>>>>>
>>>>> development for 1.7 has been happening in trunk. However, since
>>>>> I've
>>>>> been the only one working on RIFE for quite a while and I've had
>>>>> barely time to do some 1.7 stuff, I never created any maintenance
>>>>> branches. You've given you commit rights to all of svn.rifers.org.
>>>>> You
>>>>> should be able to create a maintenance branch for the release you
>>>>> want
>>>>> to work on and commit your changes. After that, you can merge the
>>>>> diffs into trunk. Does that work for you?
>>>>>
>>>>> Take care,
>>>>>
>>>>> Geert
>>>>>
>>>>>
>>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>>
>>>>>> Hi Geert,
>>>>>>
>>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>>> seems to
>>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Josh
>>>>>> --
>>>>>> Joshua Hansen
>>>>>> Up Bear Enterprises
>>>>>> (541) 760-7685
>>>>>>
>>>>>>
>>>>>> Josh Hansen wrote:
>>>>>>> Hi Geert,
>>>>>>>
>>>>>>> I'd like to do a little development and bug fixing against the
>>>>>>> 1.6.x
>>>>>>> versions, and possibly against 1.5.x.
>>>>>>>
>>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>>> version, but
>>>>>>> no branches (other than i18n):
>>>>>>> http://svn.rifers.org/
>>>>>>> http://svn.rifers.org/rife/tags/
>>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>>
>>>>>>> Should I just code against the tagged versions (1.5.1 and 1.6.1)
>>>>>>> and
>>>>>>> send you the diffs?
>>>>>>>
>>>>>>> Some branches for bugfix development on releases would be
>>>>>>> nice... :)
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Josh
>>>>>>> --
>>>>>>> Joshua Hansen
>>>>>>> Up Bear Enterprises
>>>>>>> (541) 760-7685
>>>>>>>
>>>>> --
>>>>> Geert Bevin
>>>>> Terracotta - http://www.terracotta.org
>>>>> Uwyn "Use what you need" - http://uwyn.com
>>>>> RIFE Java application framework - http://rifers.org
>>>>> Music and words - http://gbevin.com
>>>>>
>>>>>
>>> --
>>> Geert Bevin
>>> Terracotta - http://www.terracotta.org
>>> Uwyn "Use what you need" - http://uwyn.com
>>> RIFE Java application framework - http://rifers.org
>>> Music and words - http://gbevin.com
>>>
>>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-07T23:57:35Z

Hi Josh,

I never really thought about it, but I quite like "maintenance-1.6.1".
What's your preference?

Take care,

Geert

On 07 Oct 2008, at 23:45, Josh Hansen wrote:

>
> Hi Geert,
>
> Ok. I'm ready to create the branches.
>
> One question:
> * The naming pattern in the 'tags' hierarchy is "release-1.6",
> "release-1.6.1", etc. For branches, do you have a preference or
> recommendation for using "release-1.6.x", "maintenance-1.6.x", or
> simply
> "1.6.x", or something else entirely?
> http://svn.rifers.org/rife/tags/
>
> As an example, the subversion project itself uses simple version
> numbers
> for both tags and branches ("1.5.1" and "1.5.x" respectively):
> http://svn.collab.net/repos/svn/branches/
> http://svn.collab.net/repos/svn/tags/
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
> Geert Bevin wrote:
>> Hi Joshua,
>>
>>> Wow! All that power! :) Thanks -- I'll be sure to use it
>>> responsibly! :)
>>
>> I'm sure you will, you've shown great involvement and responsibility
>> before :-)
>>
>>> Good to know about trunk and 1.7. I'll create branches for at least
>>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>>
>> Sounds good, thanks!
>>
>> Take care,
>>
>> Geert
>>
>>> All the best,
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>>>
>>> Geert Bevin wrote:
>>>> Hey Josh,
>>>>
>>>> development for 1.7 has been happening in trunk. However, since
>>>> I've
>>>> been the only one working on RIFE for quite a while and I've had
>>>> barely time to do some 1.7 stuff, I never created any maintenance
>>>> branches. You've given you commit rights to all of svn.rifers.org.
>>>> You
>>>> should be able to create a maintenance branch for the release you
>>>> want
>>>> to work on and commit your changes. After that, you can merge the
>>>> diffs into trunk. Does that work for you?
>>>>
>>>> Take care,
>>>>
>>>> Geert
>>>>
>>>>
>>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>>
>>>>> Hi Geert,
>>>>>
>>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>>> seems to
>>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Josh
>>>>> --
>>>>> Joshua Hansen
>>>>> Up Bear Enterprises
>>>>> (541) 760-7685
>>>>>
>>>>>
>>>>> Josh Hansen wrote:
>>>>>> Hi Geert,
>>>>>>
>>>>>> I'd like to do a little development and bug fixing against the
>>>>>> 1.6.x
>>>>>> versions, and possibly against 1.5.x.
>>>>>>
>>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>>> version, but
>>>>>> no branches (other than i18n):
>>>>>> http://svn.rifers.org/
>>>>>> http://svn.rifers.org/rife/tags/
>>>>>> http://svn.rifers.org/rife/branches/
>>>>>>
>>>>>> Should I just code against the tagged versions (1.5.1 and 1.6.1)
>>>>>> and
>>>>>> send you the diffs?
>>>>>>
>>>>>> Some branches for bugfix development on releases would be
>>>>>> nice... :)
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Josh
>>>>>> --
>>>>>> Joshua Hansen
>>>>>> Up Bear Enterprises
>>>>>> (541) 760-7685
>>>>>>
>>>> --
>>>> Geert Bevin
>>>> Terracotta - http://www.terracotta.org
>>>> Uwyn "Use what you need" - http://uwyn.com
>>>> RIFE Java application framework - http://rifers.org
>>>> Music and words - http://gbevin.com
>>>>
>>>>
>>
>> --
>> Geert Bevin
>> Terracotta - http://www.terracotta.org
>> Uwyn "Use what you need" - http://uwyn.com
>> RIFE Java application framework - http://rifers.org
>> Music and words - http://gbevin.com
>>
>>
>>>
>>
>
> >

Re: Branch development of 1.6.x vs 1.7.x?

2008-10-07T14:45:01Z

Hi Geert,

Ok. I'm ready to create the branches.

One question:
* The naming pattern in the 'tags' hierarchy is "release-1.6",
"release-1.6.1", etc. For branches, do you have a preference or
recommendation for using "release-1.6.x", "maintenance-1.6.x", or simply
"1.6.x", or something else entirely?
http://svn.rifers.org/rife/tags/

As an example, the subversion project itself uses simple version numbers
for both tags and branches ("1.5.1" and "1.5.x" respectively):
http://svn.collab.net/repos/svn/branches/
http://svn.collab.net/repos/svn/tags/

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hi Joshua,
>
>> Wow! All that power! :) Thanks -- I'll be sure to use it
>> responsibly! :)
>
> I'm sure you will, you've shown great involvement and responsibility
> before :-)
>
>> Good to know about trunk and 1.7. I'll create branches for at least
>> 1.5.x and 1.6.x, as well as merging any changes to trunk.
>
> Sounds good, thanks!
>
> Take care,
>
> Geert
>
>> All the best,
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>> Geert Bevin wrote:
>>> Hey Josh,
>>>
>>> development for 1.7 has been happening in trunk. However, since I've
>>> been the only one working on RIFE for quite a while and I've had
>>> barely time to do some 1.7 stuff, I never created any maintenance
>>> branches. You've given you commit rights to all of svn.rifers.org.
>>> You
>>> should be able to create a maintenance branch for the release you
>>> want
>>> to work on and commit your changes. After that, you can merge the
>>> diffs into trunk. Does that work for you?
>>>
>>> Take care,
>>>
>>> Geert
>>>
>>>
>>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>>
>>>> Hi Geert,
>>>>
>>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>>> seems to
>>>> be 1.6.x (1.6.2 at the moment)... :)
>>>>
>>>> Regards,
>>>>
>>>> Josh
>>>> --
>>>> Joshua Hansen
>>>> Up Bear Enterprises
>>>> (541) 760-7685
>>>>
>>>>
>>>> Josh Hansen wrote:
>>>>> Hi Geert,
>>>>>
>>>>> I'd like to do a little development and bug fixing against the
>>>>> 1.6.x
>>>>> versions, and possibly against 1.5.x.
>>>>>
>>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>>> version, but
>>>>> no branches (other than i18n):
>>>>> http://svn.rifers.org/
>>>>> http://svn.rifers.org/rife/tags/
>>>>> http://svn.rifers.org/rife/branches/
>>>>>
>>>>> Should I just code against the tagged versions (1.5.1 and 1.6.1)
>>>>> and
>>>>> send you the diffs?
>>>>>
>>>>> Some branches for bugfix development on releases would be
>>>>> nice... :)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Josh
>>>>> --
>>>>> Joshua Hansen
>>>>> Up Bear Enterprises
>>>>> (541) 760-7685
>>>>>
>>> --
>>> Geert Bevin
>>> Terracotta - http://www.terracotta.org
>>> Uwyn "Use what you need" - http://uwyn.com
>>> RIFE Java application framework - http://rifers.org
>>> Music and words - http://gbevin.com
>>>
>>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-09-28T23:46:40Z

Hi Joshua,

> Wow! All that power! :) Thanks -- I'll be sure to use it
> responsibly! :)

I'm sure you will, you've shown great involvement and responsibility
before :-)

> Good to know about trunk and 1.7. I'll create branches for at least
> 1.5.x and 1.6.x, as well as merging any changes to trunk.

Sounds good, thanks!

Take care,

Geert

>
> All the best,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
> Geert Bevin wrote:
>> Hey Josh,
>>
>> development for 1.7 has been happening in trunk. However, since I've
>> been the only one working on RIFE for quite a while and I've had
>> barely time to do some 1.7 stuff, I never created any maintenance
>> branches. You've given you commit rights to all of svn.rifers.org.
>> You
>> should be able to create a maintenance branch for the release you
>> want
>> to work on and commit your changes. After that, you can merge the
>> diffs into trunk. Does that work for you?
>>
>> Take care,
>>
>> Geert
>>
>>
>> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>>
>>> Hi Geert,
>>>
>>> Oh yeah: where is development towards 1.7 happening? "trunk"
>>> seems to
>>> be 1.6.x (1.6.2 at the moment)... :)
>>>
>>> Regards,
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>>>
>>> Josh Hansen wrote:
>>>> Hi Geert,
>>>>
>>>> I'd like to do a little development and bug fixing against the
>>>> 1.6.x
>>>> versions, and possibly against 1.5.x.
>>>>
>>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>>> version, but
>>>> no branches (other than i18n):
>>>> http://svn.rifers.org/
>>>> http://svn.rifers.org/rife/tags/
>>>> http://svn.rifers.org/rife/branches/
>>>>
>>>> Should I just code against the tagged versions (1.5.1 and 1.6.1)
>>>> and
>>>> send you the diffs?
>>>>
>>>> Some branches for bugfix development on releases would be
>>>> nice... :)
>>>>
>>>> Regards,
>>>>
>>>> Josh
>>>> --
>>>> Joshua Hansen
>>>> Up Bear Enterprises
>>>> (541) 760-7685
>>>>
>>
>> --
>> Geert Bevin
>> Terracotta - http://www.terracotta.org
>> Uwyn "Use what you need" - http://uwyn.com
>> RIFE Java application framework - http://rifers.org
>> Music and words - http://gbevin.com
>>
>>
>>>
>>
>
> >

Re: Branch development of 1.6.x vs 1.7.x?

2008-09-28T08:20:17Z

Hi Geert,

Wow! All that power! :) Thanks -- I'll be sure to use it responsibly! :)

Good to know about trunk and 1.7. I'll create branches for at least
1.5.x and 1.6.x, as well as merging any changes to trunk.

All the best,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hey Josh,
>
> development for 1.7 has been happening in trunk. However, since I've
> been the only one working on RIFE for quite a while and I've had
> barely time to do some 1.7 stuff, I never created any maintenance
> branches. You've given you commit rights to all of svn.rifers.org. You
> should be able to create a maintenance branch for the release you want
> to work on and commit your changes. After that, you can merge the
> diffs into trunk. Does that work for you?
>
> Take care,
>
> Geert
>
>
> On 28 Sep 2008, at 03:16, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> Oh yeah: where is development towards 1.7 happening? "trunk" seems to
>> be 1.6.x (1.6.2 at the moment)... :)
>>
>> Regards,
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>
>> Josh Hansen wrote:
>>> Hi Geert,
>>>
>>> I'd like to do a little development and bug fixing against the 1.6.x
>>> versions, and possibly against 1.5.x.
>>>
>>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>>> version, but
>>> no branches (other than i18n):
>>> http://svn.rifers.org/
>>> http://svn.rifers.org/rife/tags/
>>> http://svn.rifers.org/rife/branches/
>>>
>>> Should I just code against the tagged versions (1.5.1 and 1.6.1) and
>>> send you the diffs?
>>>
>>> Some branches for bugfix development on releases would be nice... :)
>>>
>>> Regards,
>>>
>>> Josh
>>> --
>>> Joshua Hansen
>>> Up Bear Enterprises
>>> (541) 760-7685
>>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Re: Fisheye down?

2008-09-28T08:11:09Z

Hi Geert,

Hmmm -- sorry to hear that it's unstable and requires manual care
taking. Good to know.

Thanks for getting it back up -- it's really nice to be able to review
activity on the branches. :)

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Geert Bevin wrote:

> Hey Josh,
>
> yeah, Fisheye/Crucible is terribly unstable and need manual care
> taking. I've downloaded the latest version and started that one up in
> the hope that things have improved. That's what I've been doing for
> the last couple of years ;-)
>
> Take care,
>
> Geert
>
> On 28 Sep 2008, at 03:03, Josh Hansen wrote:
>
>> Hi Geert,
>>
>> This link has been down for a while. Any idea on when it will be
>> back up?
>>
>> http://rifers.org/fisheye/browse/rifers
>>
>> Linked from here:
>> http://rifers.org/sourcerepository
>>
>> Regards,
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
> >
>

Re: Branch development of 1.6.x vs 1.7.x?

2008-09-28T01:32:31Z

Hey Josh,

development for 1.7 has been happening in trunk. However, since I've
been the only one working on RIFE for quite a while and I've had
barely time to do some 1.7 stuff, I never created any maintenance
branches. You've given you commit rights to all of svn.rifers.org. You
should be able to create a maintenance branch for the release you want
to work on and commit your changes. After that, you can merge the
diffs into trunk. Does that work for you?

Take care,

Geert

On 28 Sep 2008, at 03:16, Josh Hansen wrote:

>
> Hi Geert,
>
> Oh yeah: where is development towards 1.7 happening? "trunk" seems to
> be 1.6.x (1.6.2 at the moment)... :)
>
> Regards,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
>
> Josh Hansen wrote:
>> Hi Geert,
>>
>> I'd like to do a little development and bug fixing against the 1.6.x
>> versions, and possibly against 1.5.x.
>>
>> I can see tags for 1.5.1, and 1.6.1, and there is the trunk
>> version, but
>> no branches (other than i18n):
>> http://svn.rifers.org/
>> http://svn.rifers.org/rife/tags/
>> http://svn.rifers.org/rife/branches/
>>
>> Should I just code against the tagged versions (1.5.1 and 1.6.1) and
>> send you the diffs?
>>
>> Some branches for bugfix development on releases would be nice... :)
>>
>> Regards,
>>
>> Josh
>> --
>> Joshua Hansen
>> Up Bear Enterprises
>> (541) 760-7685
>>
>>>
>>
>
> >

Re: Fisheye down?

2008-09-28T01:20:04Z

Hey Josh,

yeah, Fisheye/Crucible is terribly unstable and need manual care
taking. I've downloaded the latest version and started that one up in
the hope that things have improved. That's what I've been doing for
the last couple of years ;-)

Take care,

Geert

On 28 Sep 2008, at 03:03, Josh Hansen wrote:

>
> Hi Geert,
>
> This link has been down for a while. Any idea on when it will be
> back up?
>
> http://rifers.org/fisheye/browse/rifers
>
> Linked from here:
> http://rifers.org/sourcerepository
>
> Regards,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
> >

Re: Branch development of 1.6.x vs 1.7.x?

2008-09-27T18:16:13Z

Hi Geert,

Oh yeah: where is development towards 1.7 happening? "trunk" seems to
be 1.6.x (1.6.2 at the moment)... :)

Regards,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

Josh Hansen wrote:

> Hi Geert,
>
> I'd like to do a little development and bug fixing against the 1.6.x
> versions, and possibly against 1.5.x.
>
> I can see tags for 1.5.1, and 1.6.1, and there is the trunk version, but
> no branches (other than i18n):
> http://svn.rifers.org/
> http://svn.rifers.org/rife/tags/
> http://svn.rifers.org/rife/branches/
>
> Should I just code against the tagged versions (1.5.1 and 1.6.1) and
> send you the diffs?
>
> Some branches for bugfix development on releases would be nice... :)
>
> Regards,
>
> Josh
> --
> Joshua Hansen
> Up Bear Enterprises
> (541) 760-7685
>
> >
>

Fisheye down?

2008-09-27T18:03:35Z

Hi Geert,

This link has been down for a while. Any idea on when it will be back up?

http://rifers.org/fisheye/browse/rifers

Linked from here:
http://rifers.org/sourcerepository

Regards,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Branch development of 1.6.x vs 1.7.x?

2008-09-27T18:01:53Z

Hi Geert,

I'd like to do a little development and bug fixing against the 1.6.x
versions, and possibly against 1.5.x.

I can see tags for 1.5.1, and 1.6.1, and there is the trunk version, but
no branches (other than i18n):
http://svn.rifers.org/
http://svn.rifers.org/rife/tags/
http://svn.rifers.org/rife/branches/

Should I just code against the tagged versions (1.5.1 and 1.6.1) and
send you the diffs?

Some branches for bugfix development on releases would be nice... :)

Regards,

Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

access cookie which is set in child site.

2008-03-24T00:52:34Z

Hi all,
I ' ve developed one sample application using
RIFE Framework. In the application there is one
parent site and one subsite. I'm setting the username
as a cookie in subsite, and now i want to access this
cookie in the parent site but m not able to access :(

I have used incookie and outcookie in one of subsite's
element and have used incookie in element in parent
site, but when the control comes to the parent site
the cookie it gets is null.

I'm pasting the code of parent & subsite xml below:-

PARENT SITE:-

<site>
<arrival destid="MAINMENU"/>
<element id="MAINMENU" implementation="tutorial.friends.MainMenu" url="main">

<incookie name="username"/>

</element>
.
.
.
</site>

SUBSITE:-

<site>
<element id="MENU" implementation="tutorial.friends.Menu" url="menu">
.
.

<incookie name="username"/>
<outcookie name="username"/>
</element>
.
.
.
</site>

Problem using Continuations under JDK 1.5

2008-01-16T10:07:29Z

Hi,

I have now moved to a JDK 1.5 and am trying to use continuations as a
part of a recursive algorithm.

The problem is that the recursion after the pause() enters at the
wrong plance and ultimately leads to a stack overflow as the basis is
never evaluated.

Any Help?

Cheers

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: New to group

2008-01-10T10:11:42Z

Hi Geert,

I moved to a Solaris 10.2 and moved up to JDK 1.5 and the newer version of the continuations package.

If you remember I was attempting to use recursion and am still running into stack overflow problems even with the new version.

the problem seems to be in calling recursively after the pause() it re-enters the execute after the pause() and not at the start of the function which means that the basis is never evaluated.

Hope you have some time to help me out with this one.

Happy New Year and Cheers

On 11/26/07, Frederick Isaac <freddyisaac@...> wrote:

hi,

Just tried the code on another JDK 1.4 and it worked in both classic and non-classic mode, so you were right it must be my jvm.

thanks for all the help - I will move to another system with a different jvm and try it there or just continue in class mode :-)

cheers

On 11/26/07, Geert Bevin <gbevin@...> wrote:

Hi,

this is normal since the basic continuations runner uses the default
constructor to create a new instance of each continuation class. If
this is a non static inner class, this can't be done.

HTH,

Geert

> Sorry I didn't mean to gie the impression that the execute method
> was static. I meant to ask if the inner class which contains the
> execute method is required to be static. If not I get the exception
>
> java.lang.InstantiationException: TestPause$innerPauseInWhile
>         at java.lang.Class.newInstance0(Class.java:291)
>         at java.lang.Class.newInstance(Class.java:259)
>         at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.run(BasicContinuableRunner.java :172)
>         at

> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.start(BasicContinuableRunner.java:85)
>         at TestPause.testPause(TestPause.java:23)
>         at mainTest.main(mainTest.java:17)
>
> I am including the example which is the simplest case I can give
> you. The jar has both the .java and .class files as created by my
> compiler.
>
> Thanks very much for all your help and thanks for the advice I will
> try to build an example that takes parameters.
>
> Cheers
>
>
>
>
>
>
> On 11/21/07, Geert Bevin <gbevin@...> wrote:
> Hi Frederick,
>
> > I have determined that it only works if I run under 1.4 with the -
> > classic option, otherwise it crashes the jvm and forces a core
> > dumped which is stopped in an infinite loop. Bug in the jvm or some
> > other problem? I didn't experience this under the earlier rife 1.4
> > always run with JDK1.4 hotspot no problems.
>
> This is certainly a JDK bug, core dumps always are. However, it could
> be that some byte-code instructions causes this bug to create a
> segfault instead of having proper error messages for this. There are
> several ways to track this down, the easiest is to try to run the same
> code on another JDK or even a later version, just to see if that
> works. you can also try to reproduce the segfault with the smallest
> possible class. If you send me that, I can look at the byte code to
> see what could be the cause and maybe figure out a workaround.
>
> >  How can the execute method of the class with the continuation be
> > made anything other than static. It seems to throw an exception if
> > this is the case.
>
> What is the exception? The execute method should actually not be
> static.
>
> > Can the execute method be passed parameters?
>
> Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
> . You'll have to write the proper runner logic to provide the
> arguments to the entry method. The easiest way to do this is by
> extending BasicContinuableRunner and overridding the
> executeContinuable method.
>
> Hope this helps,
>
> Geert
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
>
> >
> <simple_example.jar>

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: New to group

2007-11-26T10:17:27Z

hi,

Just tried the code on another JDK 1.4 and it worked in both classic and non-classic mode, so you were right it must be my jvm.

thanks for all the help - I will move to another system with a different jvm and try it there or just continue in class mode :-)

cheers

On 11/26/07, Geert Bevin <gbevin@...> wrote:

Hi,

this is normal since the basic continuations runner uses the default
constructor to create a new instance of each continuation class. If
this is a non static inner class, this can't be done.

HTH,

Geert

> Sorry I didn't mean to gie the impression that the execute method
> was static. I meant to ask if the inner class which contains the
> execute method is required to be static. If not I get the exception
>
> java.lang.InstantiationException: TestPause$innerPauseInWhile
>         at java.lang.Class.newInstance0(Class.java:291)
>         at java.lang.Class.newInstance(Class.java:259)
>         at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.run(BasicContinuableRunner.java :172)
>         at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.start(BasicContinuableRunner.java:85)
>         at TestPause.testPause(TestPause.java:23)
>         at mainTest.main(mainTest.java:17)
>
> I am including the example which is the simplest case I can give
> you. The jar has both the .java and .class files as created by my
> compiler.
>
> Thanks very much for all your help and thanks for the advice I will
> try to build an example that takes parameters.
>
> Cheers
>
>
>
>
>
>
> On 11/21/07, Geert Bevin <gbevin@...> wrote:
> Hi Frederick,
>
> > I have determined that it only works if I run under 1.4 with the -
> > classic option, otherwise it crashes the jvm and forces a core
> > dumped which is stopped in an infinite loop. Bug in the jvm or some
> > other problem? I didn't experience this under the earlier rife 1.4
> > always run with JDK1.4 hotspot no problems.
>
> This is certainly a JDK bug, core dumps always are. However, it could
> be that some byte-code instructions causes this bug to create a
> segfault instead of having proper error messages for this. There are

> several ways to track this down, the easiest is to try to run the same
> code on another JDK or even a later version, just to see if that
> works. you can also try to reproduce the segfault with the smallest
> possible class. If you send me that, I can look at the byte code to
> see what could be the cause and maybe figure out a workaround.
>
> >  How can the execute method of the class with the continuation be
> > made anything other than static. It seems to throw an exception if
> > this is the case.
>
> What is the exception? The execute method should actually not be
> static.
>
> > Can the execute method be passed parameters?
>
> Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
> . You'll have to write the proper runner logic to provide the
> arguments to the entry method. The easiest way to do this is by
> extending BasicContinuableRunner and overridding the
> executeContinuable method.
>
> Hope this helps,
>
> Geert
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
>
> >
> <simple_example.jar>

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: New to group

2007-11-26T02:31:35Z

Hi,

this is normal since the basic continuations runner uses the default
constructor to create a new instance of each continuation class. If
this is a non static inner class, this can't be done.

HTH,

Geert

> Sorry I didn't mean to gie the impression that the execute method
> was static. I meant to ask if the inner class which contains the
> execute method is required to be static. If not I get the exception
>
> java.lang.InstantiationException: TestPause$innerPauseInWhile
> at java.lang.Class.newInstance0(Class.java:291)
> at java.lang.Class.newInstance(Class.java:259)
> at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.run(BasicContinuableRunner.java :172)
> at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.start(BasicContinuableRunner.java:85)
> at TestPause.testPause(TestPause.java:23)
> at mainTest.main(mainTest.java:17)
>
> I am including the example which is the simplest case I can give
> you. The jar has both the .java and .class files as created by my
> compiler.
>
> Thanks very much for all your help and thanks for the advice I will
> try to build an example that takes parameters.
>
> Cheers
>
>
>
>
>
>
> On 11/21/07, Geert Bevin <gbevin@...> wrote:
> Hi Frederick,
>
> > I have determined that it only works if I run under 1.4 with the -
> > classic option, otherwise it crashes the jvm and forces a core
> > dumped which is stopped in an infinite loop. Bug in the jvm or some
> > other problem? I didn't experience this under the earlier rife 1.4
> > always run with JDK1.4 hotspot no problems.
>
> This is certainly a JDK bug, core dumps always are. However, it could
> be that some byte-code instructions causes this bug to create a
> segfault instead of having proper error messages for this. There are
> several ways to track this down, the easiest is to try to run the same
> code on another JDK or even a later version, just to see if that
> works. you can also try to reproduce the segfault with the smallest
> possible class. If you send me that, I can look at the byte code to
> see what could be the cause and maybe figure out a workaround.
>
> > How can the execute method of the class with the continuation be
> > made anything other than static. It seems to throw an exception if
> > this is the case.
>
> What is the exception? The execute method should actually not be
> static.
>
> > Can the execute method be passed parameters?
>
> Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
> . You'll have to write the proper runner logic to provide the
> arguments to the entry method. The easiest way to do this is by
> extending BasicContinuableRunner and overridding the
> executeContinuable method.
>
> Hope this helps,
>
> Geert
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
>
> >
> <simple_example.jar>

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: New to group

2007-11-23T01:54:54Z

Which JDK version are you using exactly? Seems there are many reports
of such a core dump which has been fixed in later versions of the 1.4
JDK: http://bugs.sun.com/bugdatabase/search.do?process=1&keyword=SIGBUS

Is it possible for you to upgrade?

Maybe search the bug database with more detailed information from the
core dump itself, there could be a similar issue with possibly a fix/
workaround.

On 22 Nov 2007, at 09:10, Frederick Isaac wrote:

> Hi again,
>
> The core dump is a SIGBUS. On my platform this generally means that
> there are too many mappings to a page.
> I do have access to another JDK 1.4 as it requires another platform
> which would be AIX. As soon as I have tested I will confirm with you.
>
> Sorry I didn't mean to gie the impression that the execute method
> was static. I meant to ask if the inner class which contains the
> execute method is required to be static. If not I get the exception
>
> java.lang.InstantiationException: TestPause$innerPauseInWhile
> at java.lang.Class.newInstance0(Class.java:291)
> at java.lang.Class.newInstance(Class.java:259)
> at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.run(BasicContinuableRunner.java :172)
> at
> com
> .uwyn
> .rife
> .continuations
> .basic.BasicContinuableRunner.start(BasicContinuableRunner.java:85)
> at TestPause.testPause(TestPause.java:23)
> at mainTest.main(mainTest.java:17)
>
> I am including the example which is the simplest case I can give
> you. The jar has both the .java and .class files as created by my
> compiler.
>
> Thanks very much for all your help and thanks for the advice I will
> try to build an example that takes parameters.
>
> Cheers
>
>
>
>
>
>
> On 11/21/07, Geert Bevin <gbevin@...> wrote:
> Hi Frederick,
>
> > I have determined that it only works if I run under 1.4 with the -
> > classic option, otherwise it crashes the jvm and forces a core
> > dumped which is stopped in an infinite loop. Bug in the jvm or some
> > other problem? I didn't experience this under the earlier rife 1.4
> > always run with JDK1.4 hotspot no problems.
>
> This is certainly a JDK bug, core dumps always are. However, it could
> be that some byte-code instructions causes this bug to create a
> segfault instead of having proper error messages for this. There are
> several ways to track this down, the easiest is to try to run the same
> code on another JDK or even a later version, just to see if that
> works. you can also try to reproduce the segfault with the smallest
> possible class. If you send me that, I can look at the byte code to
> see what could be the cause and maybe figure out a workaround.
>
> > How can the execute method of the class with the continuation be
> > made anything other than static. It seems to throw an exception if
> > this is the case.
>
> What is the exception? The execute method should actually not be
> static.
>
> > Can the execute method be passed parameters?
>
> Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
> . You'll have to write the proper runner logic to provide the
> arguments to the entry method. The easiest way to do this is by
> extending BasicContinuableRunner and overridding the
> executeContinuable method.
>
> Hope this helps,
>
> Geert
>
> --
> Geert Bevin
> Terracotta - http://www.terracotta.org
> Uwyn "Use what you need" - http://uwyn.com
> RIFE Java application framework - http://rifers.org
> Music and words - http://gbevin.com
>
>
>
> >
> <simple_example.jar>

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: New to group

2007-11-22T00:10:53Z

Hi again,

The core dump is a SIGBUS. On my platform this generally means that there are too many mappings to a page.

I do have access to another JDK 1.4 as it requires another platform which would be AIX. As soon as I have tested I will confirm with you.

Sorry I didn't mean to gie the impression that the execute method was static. I meant to ask if the inner class which contains the execute method is required to be static. If not I get the exception

java.lang.InstantiationException: TestPause$innerPauseInWhile

        at java.lang.Class.newInstance0(Class.java:291)
        at java.lang.Class.newInstance(Class.java:259)
        at com.uwyn.rife.continuations.basic.BasicContinuableRunner.run(BasicContinuableRunner.java :172)
        at com.uwyn.rife.continuations.basic.BasicContinuableRunner.start(BasicContinuableRunner.java:85)
        at TestPause.testPause(TestPause.java:23)
        at mainTest.main(mainTest.java:17)

I am including the example which is the simplest case I can give you. The jar has both the .java and .class files as created by my compiler.

Thanks very much for all your help and thanks for the advice I will try to build an example that takes parameters.

Cheers

On 11/21/07, Geert Bevin <gbevin@...> wrote:

Hi Frederick,

> I have determined that it only works if I run under 1.4 with the -
> classic option, otherwise it crashes the jvm and forces a core
> dumped which is stopped in an infinite loop. Bug in the jvm or some
> other problem? I didn't experience this under the earlier rife 1.4
> always run with JDK1.4 hotspot no problems.

This is certainly a JDK bug, core dumps always are. However, it could
be that some byte-code instructions causes this bug to create a
segfault instead of having proper error messages for this. There are
several ways to track this down, the easiest is to try to run the same
code on another JDK or even a later version, just to see if that
works. you can also try to reproduce the segfault with the smallest
possible class. If you send me that, I can look at the byte code to
see what could be the cause and maybe figure out a workaround.

> How can the execute method of the class with the continuation be
> made anything other than static. It seems to throw an exception if
> this is the case.

What is the exception? The execute method should actually not be static.

> Can the execute method be passed parameters?

Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
. You'll have to write the proper runner logic to provide the
arguments to the entry method. The easiest way to do this is by
extending BasicContinuableRunner and overridding the
executeContinuable method.

Hope this helps,

Geert

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

simple_example.jar (13K) Download Attachment

Re: New to group

2007-11-21T03:01:49Z

Hi Frederick,

> I have determined that it only works if I run under 1.4 with the -
> classic option, otherwise it crashes the jvm and forces a core
> dumped which is stopped in an infinite loop. Bug in the jvm or some
> other problem? I didn't experience this under the earlier rife 1.4
> always run with JDK1.4 hotspot no problems.

This is certainly a JDK bug, core dumps always are. However, it could
be that some byte-code instructions causes this bug to create a
segfault instead of having proper error messages for this. There are
several ways to track this down, the easiest is to try to run the same
code on another JDK or even a later version, just to see if that
works. you can also try to reproduce the segfault with the smallest
possible class. If you send me that, I can look at the byte code to
see what could be the cause and maybe figure out a workaround.

> How can the execute method of the class with the continuation be
> made anything other than static. It seems to throw an exception if
> this is the case.

What is the exception? The execute method should actually not be static.

> Can the execute method be passed parameters?

Yes it can, set this up with the http://rifers.org/docs/api/com/uwyn/rife/continuations/ContinuationConfigInstrument.htmlclass
. You'll have to write the proper runner logic to provide the
arguments to the entry method. The easiest way to do this is by
extending BasicContinuableRunner and overridding the
executeContinuable method.

Hope this helps,

Geert

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-dev" group.
To post to this group, send email to rife-dev@...
To unsubscribe from this group, send email to rife-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-dev?hl=en
-~----------~----~----~----~------~----~------~--~---