You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by th...@apache.org on 2012/05/11 13:06:56 UTC
svn commit: r1337109 -
/cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml
Author: thorsten
Date: Fri May 11 11:06:56 2012
New Revision: 1337109
URL: http://svn.apache.org/viewvc?rev=1337109&view=rev
Log:
white noise - formating changes
Modified:
cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml
Modified: cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml
URL: http://svn.apache.org/viewvc/cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml?rev=1337109&r1=1337108&r2=1337109&view=diff
==============================================================================
--- cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml (original)
+++ cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml Fri May 11 11:06:56 2012
@@ -60,7 +60,7 @@
/ = anon
/admin = authc, roles[admin]
/secure/** = authc
- /** = anon
+ /** = anon
# more URL-to-FilterChain definitions here
</value>
</property>
Re: [C3] Time to define a roadmap
Posted by Reinhard Pötz <re...@apache.org>.
On 05/21/2012 08:58 AM, Francesco Chicchiriccò wrote:
> On 20/05/2012 16:54, Reinhard Pötz wrote:
>> On 05/14/2012 09:04 AM, Francesco Chicchiriccò wrote:
>>> Hi all,
>>> it's been quite a while since our latest C3 release (July 1st, 2011)
>>> [1]; even though I personally believe we should at least fix some
>>> aspects before cutting next release, I also think it would be nice to
>>> provide a roadmap for all people - including me - that are already using
>>> C3 on some of their own projects.
>>>
>>> Hence:
>>>
>>> 1. what will we include in beta-1? Is JIRA updated in this respect [2]?
>>> There are quite some other unplanned issues [3].
>>> 2. what will we plan after beta-1? beta-2? and afterwards?
>>> 3. do we want to consider some milestone release (M1 / M2 / ...)
>>> instead, maybe even BEFORE beta-1, so that we can provide some "stable"
>>> reference for external project relying upon C3?
>>
>> IMO the most important missing thing before going beta is supporting
>> alternative output types than OutputStream and to get rid of "throws
>> Exception" which is actually of no value.
>>
>> The latter is rather simple to achieve, the first change needs (a lot
>> of) more work, especially regarding caching. Steven and I have started
>> to work on a proposal for dynamic output types but we haven't had
>> enough time yet to commit it to the whiteboard and write a proposal
>> email.
>>
>
> Reinhard, I see your point: do you think it would be possible to release
> something like a milestone in the meanwhile? We would be able, in this
> way, to either not yet fall into beta and to provide C3 users out there
> with a rather "stable" reference for their projects.
Yes, the "milestone / release candidate" scheme has worked very well for
us in the past and is currently also used by e.g. Eclipse, Spring or
Wicket. Many users should be familiar with that.
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: [C3] Time to define a roadmap
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 20/05/2012 16:54, Reinhard Pötz wrote:
> On 05/14/2012 09:04 AM, Francesco Chicchiriccò wrote:
>> Hi all,
>> it's been quite a while since our latest C3 release (July 1st, 2011)
>> [1]; even though I personally believe we should at least fix some
>> aspects before cutting next release, I also think it would be nice to
>> provide a roadmap for all people - including me - that are already using
>> C3 on some of their own projects.
>>
>> Hence:
>>
>> 1. what will we include in beta-1? Is JIRA updated in this respect [2]?
>> There are quite some other unplanned issues [3].
>> 2. what will we plan after beta-1? beta-2? and afterwards?
>> 3. do we want to consider some milestone release (M1 / M2 / ...)
>> instead, maybe even BEFORE beta-1, so that we can provide some "stable"
>> reference for external project relying upon C3?
>
> IMO the most important missing thing before going beta is supporting
> alternative output types than OutputStream and to get rid of "throws
> Exception" which is actually of no value.
>
> The latter is rather simple to achieve, the first change needs (a lot
> of) more work, especially regarding caching. Steven and I have started
> to work on a proposal for dynamic output types but we haven't had
> enough time yet to commit it to the whiteboard and write a proposal
> email.
>
Reinhard, I see your point: do you think it would be possible to release
something like a milestone in the meanwhile? We would be able, in this
way, to either not yet fall into beta and to provide C3 users out there
with a rather "stable" reference for their projects.
WDYT?
Regards.
--
Francesco Chicchiriccò
Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: [C3] Time to define a roadmap
Posted by Reinhard Pötz <re...@apache.org>.
On 05/14/2012 09:04 AM, Francesco Chicchiriccò wrote:
> Hi all,
> it's been quite a while since our latest C3 release (July 1st, 2011)
> [1]; even though I personally believe we should at least fix some
> aspects before cutting next release, I also think it would be nice to
> provide a roadmap for all people - including me - that are already using
> C3 on some of their own projects.
>
> Hence:
>
> 1. what will we include in beta-1? Is JIRA updated in this respect [2]?
> There are quite some other unplanned issues [3].
> 2. what will we plan after beta-1? beta-2? and afterwards?
> 3. do we want to consider some milestone release (M1 / M2 / ...)
> instead, maybe even BEFORE beta-1, so that we can provide some "stable"
> reference for external project relying upon C3?
IMO the most important missing thing before going beta is supporting
alternative output types than OutputStream and to get rid of "throws
Exception" which is actually of no value.
The latter is rather simple to achieve, the first change needs (a lot
of) more work, especially regarding caching. Steven and I have started
to work on a proposal for dynamic output types but we haven't had enough
time yet to commit it to the whiteboard and write a proposal email.
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
[C3] Time to define a roadmap [WAS Re: svn commit: r1337109 - /cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml]
Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi all,
it's been quite a while since our latest C3 release (July 1st, 2011)
[1]; even though I personally believe we should at least fix some
aspects before cutting next release, I also think it would be nice to
provide a roadmap for all people - including me - that are already using
C3 on some of their own projects.
Hence:
1. what will we include in beta-1? Is JIRA updated in this respect [2]?
There are quite some other unplanned issues [3].
2. what will we plan after beta-1? beta-2? and afterwards?
3. do we want to consider some milestone release (M1 / M2 / ...)
instead, maybe even BEFORE beta-1, so that we can provide some "stable"
reference for external project relying upon C3?
Please share your thoughts, thanks.
Regards.
[1] http://cocoon.apache.org/news-c3-alpha-3-released.html
[2]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+COCOON3+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+COCOON3+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide>
[3]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+COCOON3+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+COCOON3+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide>
On 12/05/2012 07:53, Jos Snellings wrote:
> I wish that would be real soon.
> I have a C3 application live. Based on my best judgement, I decided
> that the beta version was stable enough.
> Last winter I was bad-mouthed by some colleagues for having done this.
>
> Jos
>
>
> On Fri, May 11, 2012 at 9:04 PM, Michael Müller
> <michael.mueller@mueller-bruehl.de
> <ma...@mueller-bruehl.de>> wrote:
>
> Hi Thorsten (and other cocoon developers),
>
> I recognized some activities (svn commits etc.). On the other
> hand, cocoon 3.0 is in alpha and beta stage for a long time,
> feeling like ages.
> Is there a roadmap available? When might it be release?
>
> Herzliche Grüße - Best Regards,
> Michael Müller
>
>
> Am 11.05.2012 13:06, schrieb thorsten@apache.org
> <ma...@apache.org>:
>
> Author: thorsten
> Date: Fri May 11 11:06:56 2012
> New Revision: 1337109
>
> URL: http://svn.apache.org/viewvc?rev=1337109&view=rev
> <http://svn.apache.org/viewvc?rev=1337109&view=rev>
> Log:
> white noise - formating changes
>
--
Francesco Chicchiriccò
Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Re: svn commit: r1337109 - /cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml
Posted by Jos Snellings <jo...@upperware.biz>.
I wish that would be real soon.
I have a C3 application live. Based on my best judgement, I decided that
the beta version was stable enough.
Last winter I was bad-mouthed by some colleagues for having done this.
Jos
On Fri, May 11, 2012 at 9:04 PM, Michael Müller <
michael.mueller@mueller-bruehl.de> wrote:
> Hi Thorsten (and other cocoon developers),
>
> I recognized some activities (svn commits etc.). On the other hand, cocoon
> 3.0 is in alpha and beta stage for a long time, feeling like ages.
> Is there a roadmap available? When might it be release?
>
> Herzliche Grüße - Best Regards,
> Michael Müller
>
>
> Am 11.05.2012 13:06, schrieb thorsten@apache.org:
>
>> Author: thorsten
>> Date: Fri May 11 11:06:56 2012
>> New Revision: 1337109
>>
>> URL: http://svn.apache.org/viewvc?**rev=1337109&view=rev<http://svn.apache.org/viewvc?rev=1337109&view=rev>
>> Log:
>> white noise - formating changes
>>
>
--
The doctrine of human equality reposes on this: that there is no man
really clever who has not found that he is stupid.
-- Gilbert K. Chesterson
Re: svn commit: r1337109 - /cocoon/cocoon3/trunk/cocoon-shiro-sample/src/main/resources/META-INF/cocoon/spring/block-application-context.xml
Posted by Michael Müller <mi...@mueller-bruehl.de>.
Hi Thorsten (and other cocoon developers),
I recognized some activities (svn commits etc.). On the other hand,
cocoon 3.0 is in alpha and beta stage for a long time, feeling like ages.
Is there a roadmap available? When might it be release?
Herzliche Grüße - Best Regards,
Michael Müller
Am 11.05.2012 13:06, schrieb thorsten@apache.org:
> Author: thorsten
> Date: Fri May 11 11:06:56 2012
> New Revision: 1337109
>
> URL: http://svn.apache.org/viewvc?rev=1337109&view=rev
> Log:
> white noise - formating changes