Hi all,
If nobody objects, I will merge the client API refactoring branch into
trunk this Wednesday.
If there are any reasons not to merge, please let me know as soon as
possible!
Cheers,
Florian
Hi,
Could you give a very quick high-level view of what the refactoring
was about (besides TransientCmisObject)?
I'm asking because it's hard to follow with just the diffs in svn for
these kinds of changes.
Florent
On Fri, Nov 12, 2010 at 3:54 PM, Florian Müller
florian.muel...@alfresco.com
Sure. The refactoring covers three areas:
- It covers all modifications proposed in [1] with a few changes:
The lightweight versions of updateProperties, setContentStream and
deleteContentStream could not be attached to the Session interface because they
need access to the change token.
Hi Florian,
From my point of view please go ahead with integration to the trunk. I will
follow changes ASAP and provide feedback with that.
Regards,
Stephan
Am 15.11.2010 um 17:47 schrieb Florian Müller:
Sure. The refactoring covers three areas:
- It covers all modifications proposed in
Hi,
I should be fixing the rendition bug tonight or tomorrow, so a merge
on Wednesday is fine for me.
Florent
On Mon, Nov 15, 2010 at 2:50 PM, Florian Müller
florian.muel...@alfresco.com wrote:
Hi all,
If nobody objects, I will merge the client API refactoring branch into trunk
this
Hi Jeff,
I did create a Jira issue for this:
https://issues.apache.org/jira/browse/INFRA-3202
As soon as the environment is available I can volunteer to setup a Hudson build
job.
Regards,
Stephan
Am 10.11.2010 um 22:43 schrieb Niklas Gustavsson:
Please open a JIRA issue with this request.
Hi all,
I had another look at [1]. Unfortunately, it's an unsolvable problem.
I can think of three ways to cope with it:
1. We leave it like it is, although it is very, very confusing when you run
into this situation.
2. We don't cache by path. How would that affect applications?
3. When
