You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Lukasz Lenart <lu...@apache.org> on 2013/03/01 07:56:58 UTC
Re: [OGNL] A new release
How can I update ognl website? Simple checkout [1] and update what I
need? and then what to do?
eg. RAT report is broken as it includes all the html files [2]
[1] https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-ognl/
[2] http://commons.apache.org/proper/commons-ognl/rat-report.html
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
https://issues.apache.org/jira/browse/OGNL-232
2013/3/26 Lukasz Lenart <lu...@apache.org>:
> Ok, done. Should I just commit the changes? Or do I have to register
> an issue first in JIRA? Maybe it will be better...
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/3/26 Lukasz Lenart <lu...@apache.org>:
>> I'm not sure what API should be removed/renamed/etc as almost
>> everything is public static ;-)
>>
>> Anyway, I'm trying to remove two deprecated classes right now.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/3/8 Christian Grobmeier <gr...@gmail.com>:
>>> On Wed, Mar 6, 2013 at 10:11 AM, sebb <se...@gmail.com> wrote:
>>>> On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
>>>>> Hi,
>>>>>
>>>>> I was checking out what should be solved before releasing a new
>>>>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>>>>> "These nested if statements could be combined" should be resolved, but
>>>>> the rest I don't see a point instead of just satisfying PMD itself.
>>>>>
>>>>> Some of the Findbugs [2] errors are related to generated classes,
>>>>> should I exclude them?
>>>>>
>>>>> Another thing is Checkstyle [3], especially "Missing a Javadoc
>>>>> comment." - I don't know what to put as it without analysing source
>>>>> code deeply.
>>>>>
>>>>> My question is what really should be solved to be ready to release a
>>>>> new version?
>>>>
>>>> I don't personally worry too much about PMD or Checkstyle; they depend
>>>> so much on the rules chosen.
>>>
>>> Guess we need to decide on a few rules here. If they are somehow
>>> connected to method naming et al we should look at them more closely
>>>
>>>
>>>> Findbugs is more useful, but it looks like most of the errors are for
>>>> generated code.
>>>>
>>>> Bugs can be fixed by a new release, but future binary compatibility
>>>> can easily be compromised.
>>>>
>>>> Once a bad or broken API is released, it's very difficult to fix it.
>>>>
>>>> So I would say the most important aspect to get right is to fix
>>>> anything that makes it more difficult to maintain binary compatibility
>>>> in future.
>>>>
>>>> For example, if one of the new methods has a name that is
>>>> non-standard, it is easy to change it now.
>>>> Likewise, if there is a new public method which should be private or
>>>> package protected, do it now.
>>>>
>>>> Or new non-private mutable variables - they make thread-safety - and
>>>> testing - much more difficult
>>>
>>> +1
>>> We should look over all of our methods right now and discuss
>>> everything which is public.
>>>
>>>> Speaking of which, there does not seem to be a Clirr report.
>>>
>>> I have added the clirr report plugin right now. I doesn't report for
>>> the first build, as it cannot compare to anything.
>>> I am bit confused since there is basically no configuration necessary,
>>> just the plugin definition - is it correct?
>>>
>>>> That's very important.
>>>> Apart from checking for unintended compatibility issues, it is useful
>>>> in ensuring that new classes and methods etc. are annotated with
>>>> @since markers.
>>>
>>> We have moved OGNL to 4.0 and Apache - should we annotate everything
>>> with since 4.0.0 then?
>>> Imho it doesn't make much sense to annotate with 3.x, as the package
>>> has changed and both releases are not fully interchangeable
>>>
>>> Cheers
>>>
>>>
>>>>
>>>>> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
>>>>> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
>>>>> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>>>>>
>>>>>
>>>>> Regards
>>>>> --
>>>>> Łukasz
>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Christian Grobmeier <gr...@gmail.com>.
On Tue, Mar 26, 2013 at 9:53 AM, Lukasz Lenart <lu...@apache.org> wrote:
> 2013/3/26 Christian Grobmeier <gr...@gmail.com>:
>> +1, go for it.
>> Now its time to see if our testcases are good.
>
> They are, I made a slight mistake and tests showed that :-)
>
>> I also think we should test it in conjunction with struts.
>
> Not so easy, OGNL 4 is a different beast, but I'll try ;-)
You are not alone mate! :-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/3/26 Maurizio Cucchiara <mc...@apache.org>:
> Do you mean this [1] isEvalChain method?
>
> [1] https://svn.apache.org/repos/asf/commons/proper/ognl/trunk/src/main/java/org/apache/commons/ognl/SimpleNode.java
IDEA cheats me ;-) It used wrong version ;-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Maurizio Cucchiara <mc...@apache.org>.
Do you mean this [1] isEvalChain method?
[1] https://svn.apache.org/repos/asf/commons/proper/ognl/trunk/src/main/java/org/apache/commons/ognl/SimpleNode.java
On 26 March 2013 10:12, Lukasz Lenart <lu...@apache.org> wrote:
> isEvalChain() method isn't available in OGNL 4
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin :http://www.linkedin.com/in/mauriziocucchiara
VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
Maurizio Cucchiara
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/3/26 Maurizio Cucchiara <mc...@apache.org>:
> I thought that it won't be a piece of cake, but we might make it
> easier, for example what about to start a new branch on struts to
> integrate the new version of OGNL? (perhaps this is not the right
> place, or at least the only place, where this discussion should
> happen)
I have noticed one thing: isEvalChain() method isn't available in OGNL 4
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Lukasz Lenart
> Sent: Tuesday, December 31, 2013 8:37
>
> Did some cleanup in JIRA
>
> https://issues.apache.org/jira/browse/OGNL/fixforversion/12323958
OGNL-238, unless I am misreading it, is asking for capabilities that do not
exist in Java since the information is lost prior to runtime.
OGNL-145: is there a better primer on the issue besides what is in the ticket? I
would like to work it today/tomorrow.
>
> 2013/12/30 Lukasz Lenart <lu...@apache.org>:
> > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> >> There are a lot of formatting chenges between the version
> in git and apache svn.
> >> I am still looking for "patches" in git not yet applied to
> >> subversion, do you know of any?
> >
> > All should be already applied or don't affect Apache's version
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
Did some cleanup in JIRA
https://issues.apache.org/jira/browse/OGNL/fixforversion/12323958
2013/12/30 Lukasz Lenart <lu...@apache.org>:
> 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
>> There are a lot of formatting chenges between the version in git and apache svn.
>> I am still looking for "patches" in git not yet applied to subversion, do you
>> know of any?
>
> All should be already applied or don't affect Apache's version
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Lukasz Lenart
> Sent: Tuesday, December 31, 2013 8:40
>
> 2013/12/31 Benedikt Ritter <br...@apache.org>:
> >> > > The old OGNL (legacy) releases use the
> >> > >
> >> > > "package ognl;"
> >> > >
> >> > > declarations, where as the apache releases will use
> >> > >
> >> > > "package org.apache.commons.ognl;"
> >> > >
> >> > > I would create a set of proxy classes in the old package
> >> > space which
> >> > > call the classes in the new space.
> >> >
> >> > These will only be required for a small proportion of
> users, so I
> >> > suggest they are packaged in a separate jar.
> >>
> >> That was always assumed. The question would it be
> appropiate for an
> >> Apache release, or should it be released elsewhere.
> >>
> >
> > Our software usually uses the org.apache.commons namespace. I'm not
> > sure if this is an absolute requirement. To me it feels like these
> > adapters should be developed and maintained else where. Thoughts?
>
> Introducing that proxies is a bad idea - Apache Ognl is a bit
> different beast than original Ognl and it will never be a
> drop-in replacement, you will have to migrate your code anyway.
One less thing to do then. Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/12/31 Benedikt Ritter <br...@apache.org>:
>> > > The old OGNL (legacy) releases use the
>> > >
>> > > "package ognl;"
>> > >
>> > > declarations, where as the apache releases will use
>> > >
>> > > "package org.apache.commons.ognl;"
>> > >
>> > > I would create a set of proxy classes in the old package
>> > space which
>> > > call the classes in the new space.
>> >
>> > These will only be required for a small proportion of users,
>> > so I suggest they are packaged in a separate jar.
>>
>> That was always assumed. The question would it be appropiate for an Apache
>> release, or should it be released elsewhere.
>>
>
> Our software usually uses the org.apache.commons namespace. I'm not sure if
> this is an absolute requirement. To me it feels like these adapters should
> be developed and maintained else where. Thoughts?
Introducing that proxies is a bad idea - Apache Ognl is a bit
different beast than original Ognl and it will never be a drop-in
replacement, you will have to migrate your code anyway.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Benedikt Ritter
> Sent: Tuesday, December 31, 2013 6:05
>
> 2013/12/31 Jason Pyeron <jp...@pdinc.us>
>
> > > -----Original Message-----
> > > From: sebb
> > > Sent: Monday, December 30, 2013 17:17
> > >
> > > On 30 December 2013 21:21, Jason Pyeron <jp...@pdinc.us> wrote:
> > > >> -----Original Message-----
> > > >> From: Benedikt Ritter
> > > >> Sent: Monday, December 30, 2013 14:19
> > > >>
> > > >> Hello Jason,
> > > >>
> > > >> sorry, I don't understand what exactly you have in mind.
> > > Can you give
> > > >> some examples?
> > > >
> > > > The old OGNL (legacy) releases use the
> > > >
> > > > "package ognl;"
> > > >
> > > > declarations, where as the apache releases will use
> > > >
> > > > "package org.apache.commons.ognl;"
> > > >
> > > > I would create a set of proxy classes in the old package
> > > space which
> > > > call the classes in the new space.
> > >
> > > These will only be required for a small proportion of users, so I
> > > suggest they are packaged in a separate jar.
> >
> > That was always assumed. The question would it be appropiate for an
> > Apache release, or should it be released elsewhere.
> >
>
> Our software usually uses the org.apache.commons namespace.
> I'm not sure if this is an absolute requirement. To me it
> feels like these adapters should be developed and maintained
> else where. Thoughts?
The biggest user would be the struts group, that would be a strong reason for it
to be an Apache release.
A second reason for it to be an Apache release is, "why would a project switch
to the OGNL Commons release and then install a non Apache adapter?"
That being said, I would use an adaptor from a third party as long as the
license worked.
<snip/>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Benedikt Ritter <br...@apache.org>.
2013/12/31 Jason Pyeron <jp...@pdinc.us>
> > -----Original Message-----
> > From: sebb
> > Sent: Monday, December 30, 2013 17:17
> >
> > On 30 December 2013 21:21, Jason Pyeron <jp...@pdinc.us> wrote:
> > >> -----Original Message-----
> > >> From: Benedikt Ritter
> > >> Sent: Monday, December 30, 2013 14:19
> > >>
> > >> Hello Jason,
> > >>
> > >> sorry, I don't understand what exactly you have in mind.
> > Can you give
> > >> some examples?
> > >
> > > The old OGNL (legacy) releases use the
> > >
> > > "package ognl;"
> > >
> > > declarations, where as the apache releases will use
> > >
> > > "package org.apache.commons.ognl;"
> > >
> > > I would create a set of proxy classes in the old package
> > space which
> > > call the classes in the new space.
> >
> > These will only be required for a small proportion of users,
> > so I suggest they are packaged in a separate jar.
>
> That was always assumed. The question would it be appropiate for an Apache
> release, or should it be released elsewhere.
>
Our software usually uses the org.apache.commons namespace. I'm not sure if
this is an absolute requirement. To me it feels like these adapters should
be developed and maintained else where. Thoughts?
Benedikt
>
> >
> > >>
> > >> 2013/12/30 Jason Pyeron <jp...@pdinc.us>
> > >>
> > >> >
> > >> > > -----Original Message-----
> > >> > > From: Lukasz Lenart
> > >> > > Sent: Monday, December 30, 2013 10:51
> > >> > >
> > >> > > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> > >> > > > There are a lot of formatting chenges between the version
> > >> > > in git and apache svn.
> > >> > > > I am still looking for "patches" in git not yet applied to
> > >> > > subversion,
> > >> > > > do you know of any?
> > >> > >
> > >> > > All should be already applied or don't affect Apache's version
> > >> >
> > >> > I was thinking that a set of classes to wrap the
> > org.apache classes
> > >> > should be made for users of the legacy releases until they
> > >> are ready
> > >> > to update their code bases.
> > >> >
> > >> > What does anyone else think? Ping Struts folks...
> > >
> > > jpyeron@black /projects/struts
> > > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test <snip/>
> > >
> > ./struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/ognl/
> > > accessor/O bjectProxyPropertyAccessor.java:import ognl.OgnlContext;
> > > <snip/>
> > >
> > > jpyeron@black /projects/struts
> > > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test | wc -l
> > > 54
> > >
> > >> >
> > >> > Could those be an apache package? Or must they be from
> > "elsewhere"
> > >> > since they will have the non-conformant package names.
> > >> >
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
RE: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: sebb
> Sent: Monday, December 30, 2013 17:17
>
> On 30 December 2013 21:21, Jason Pyeron <jp...@pdinc.us> wrote:
> >> -----Original Message-----
> >> From: Benedikt Ritter
> >> Sent: Monday, December 30, 2013 14:19
> >>
> >> Hello Jason,
> >>
> >> sorry, I don't understand what exactly you have in mind.
> Can you give
> >> some examples?
> >
> > The old OGNL (legacy) releases use the
> >
> > "package ognl;"
> >
> > declarations, where as the apache releases will use
> >
> > "package org.apache.commons.ognl;"
> >
> > I would create a set of proxy classes in the old package
> space which
> > call the classes in the new space.
>
> These will only be required for a small proportion of users,
> so I suggest they are packaged in a separate jar.
That was always assumed. The question would it be appropiate for an Apache
release, or should it be released elsewhere.
>
> >>
> >> 2013/12/30 Jason Pyeron <jp...@pdinc.us>
> >>
> >> >
> >> > > -----Original Message-----
> >> > > From: Lukasz Lenart
> >> > > Sent: Monday, December 30, 2013 10:51
> >> > >
> >> > > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> >> > > > There are a lot of formatting chenges between the version
> >> > > in git and apache svn.
> >> > > > I am still looking for "patches" in git not yet applied to
> >> > > subversion,
> >> > > > do you know of any?
> >> > >
> >> > > All should be already applied or don't affect Apache's version
> >> >
> >> > I was thinking that a set of classes to wrap the
> org.apache classes
> >> > should be made for users of the legacy releases until they
> >> are ready
> >> > to update their code bases.
> >> >
> >> > What does anyone else think? Ping Struts folks...
> >
> > jpyeron@black /projects/struts
> > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test <snip/>
> >
> ./struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/ognl/
> > accessor/O bjectProxyPropertyAccessor.java:import ognl.OgnlContext;
> > <snip/>
> >
> > jpyeron@black /projects/struts
> > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test | wc -l
> > 54
> >
> >> >
> >> > Could those be an apache package? Or must they be from
> "elsewhere"
> >> > since they will have the non-conformant package names.
> >> >
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by sebb <se...@gmail.com>.
On 30 December 2013 21:21, Jason Pyeron <jp...@pdinc.us> wrote:
>> -----Original Message-----
>> From: Benedikt Ritter
>> Sent: Monday, December 30, 2013 14:19
>>
>> Hello Jason,
>>
>> sorry, I don't understand what exactly you have in mind. Can
>> you give some examples?
>
> The old OGNL (legacy) releases use the
>
> "package ognl;"
>
> declarations, where as the apache releases will use
>
> "package org.apache.commons.ognl;"
>
> I would create a set of proxy classes in the old package space which call the
> classes in the new space.
These will only be required for a small proportion of users, so I
suggest they are packaged in a separate jar.
>>
>> 2013/12/30 Jason Pyeron <jp...@pdinc.us>
>>
>> >
>> > > -----Original Message-----
>> > > From: Lukasz Lenart
>> > > Sent: Monday, December 30, 2013 10:51
>> > >
>> > > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
>> > > > There are a lot of formatting chenges between the version
>> > > in git and apache svn.
>> > > > I am still looking for "patches" in git not yet applied to
>> > > subversion,
>> > > > do you know of any?
>> > >
>> > > All should be already applied or don't affect Apache's version
>> >
>> > I was thinking that a set of classes to wrap the org.apache classes
>> > should be made for users of the legacy releases until they
>> are ready
>> > to update their code bases.
>> >
>> > What does anyone else think? Ping Struts folks...
>
> jpyeron@black /projects/struts
> $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test
> <snip/>
> ./struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/ognl/accessor/O
> bjectProxyPropertyAccessor.java:import ognl.OgnlContext;
> <snip/>
>
> jpyeron@black /projects/struts
> $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test | wc -l
> 54
>
>> >
>> > Could those be an apache package? Or must they be from "elsewhere"
>> > since they will have the non-conformant package names.
>> >
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Benedikt Ritter
> Sent: Monday, December 30, 2013 14:19
>
> Hello Jason,
>
> sorry, I don't understand what exactly you have in mind. Can
> you give some examples?
The old OGNL (legacy) releases use the
"package ognl;"
declarations, where as the apache releases will use
"package org.apache.commons.ognl;"
I would create a set of proxy classes in the old package space which call the
classes in the new space.
>
> 2013/12/30 Jason Pyeron <jp...@pdinc.us>
>
> >
> > > -----Original Message-----
> > > From: Lukasz Lenart
> > > Sent: Monday, December 30, 2013 10:51
> > >
> > > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> > > > There are a lot of formatting chenges between the version
> > > in git and apache svn.
> > > > I am still looking for "patches" in git not yet applied to
> > > subversion,
> > > > do you know of any?
> > >
> > > All should be already applied or don't affect Apache's version
> >
> > I was thinking that a set of classes to wrap the org.apache classes
> > should be made for users of the legacy releases until they
> are ready
> > to update their code bases.
> >
> > What does anyone else think? Ping Struts folks...
jpyeron@black /projects/struts
$ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test
<snip/>
./struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/ognl/accessor/O
bjectProxyPropertyAccessor.java:import ognl.OgnlContext;
<snip/>
jpyeron@black /projects/struts
$ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test | wc -l
54
> >
> > Could those be an apache package? Or must they be from "elsewhere"
> > since they will have the non-conformant package names.
> >
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Benedikt Ritter <br...@apache.org>.
Hello Jason,
sorry, I don't understand what exactly you have in mind. Can you give some
examples?
Benedikt
2013/12/30 Jason Pyeron <jp...@pdinc.us>
>
> > -----Original Message-----
> > From: Lukasz Lenart
> > Sent: Monday, December 30, 2013 10:51
> >
> > 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> > > There are a lot of formatting chenges between the version
> > in git and apache svn.
> > > I am still looking for "patches" in git not yet applied to
> > subversion,
> > > do you know of any?
> >
> > All should be already applied or don't affect Apache's version
>
> I was thinking that a set of classes to wrap the org.apache classes should
> be
> made for users of the legacy releases until they are ready to update their
> code
> bases.
>
> What does anyone else think? Ping Struts folks...
>
> Could those be an apache package? Or must they be from "elsewhere" since
> they
> will have the non-conformant package names.
>
> -Jason
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Apache-Legacy class adapters was RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Lukasz Lenart
> Sent: Monday, December 30, 2013 10:51
>
> 2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> > There are a lot of formatting chenges between the version
> in git and apache svn.
> > I am still looking for "patches" in git not yet applied to
> subversion,
> > do you know of any?
>
> All should be already applied or don't affect Apache's version
I was thinking that a set of classes to wrap the org.apache classes should be
made for users of the legacy releases until they are ready to update their code
bases.
What does anyone else think? Ping Struts folks...
Could those be an apache package? Or must they be from "elsewhere" since they
will have the non-conformant package names.
-Jason
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/12/30 Jason Pyeron <jp...@pdinc.us>:
> There are a lot of formatting chenges between the version in git and apache svn.
> I am still looking for "patches" in git not yet applied to subversion, do you
> know of any?
All should be already applied or don't affect Apache's version
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Lukasz Lenart
> Sent: Monday, December 30, 2013 2:33
>
> I think OGNL-239 and OGNL-240 are the only real
> (semi)blocking issues before we can start a new release.
>
Thankfully, they both have patches...
There are a lot of formatting chenges between the version in git and apache svn.
I am still looking for "patches" in git not yet applied to subversion, do you
know of any?
>
> Regards
> --
> Lukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/12/25 Jason Pyeron <jp...@pdinc.us>:
> >> -----Original Message-----
> >> From: Benedikt Ritter
> >> Sent: Wednesday, December 25, 2013 11:53
> >>
> >> You've set the issue to status resolved. That's propably the
> >
> > After adding the patch.
> >
> >> reason why nobody had a look at it.
> >> I don't know if there's anybody planing to roll out a release
> >> soon. But low svn activity indicates, that this is not the case...
> >
> > I took it as a stability indicator... [looks like is active on git
> >
> https://issues.apache.org/jira/browse/OGNL-145?focusedCommentI
d=13395741&page=co
> >
> m.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
#comment-13395741]
> >
> > I am willing to step up to the plate if there are steps or
> bugs blocking a
> > release. When looking through the open 4.0 issues I did not
> see any notable
> > blockers. OGNL-145 is a nice to have, and OGNL-238 may be a
> limit of Java.
> >
> > Either way I am going to browse the updates in
> > https://github.com/jkuhnert/ognl.git
> >
> >>
> >> Regards,
> >> Benedikt
> >>
> >> Send from my mobile device
> >>
> >> > Am 25.12.2013 um 06:06 schrieb "Jason Pyeron" <jp...@pdinc.us>:
> >> >
> >> > I have not seen any updates on subversion since September.
> >> Are there
> >> > any plans on a release?
> >> >
> >> > Either way, please commit the patch on
> >> > https://issues.apache.org/jira/i#browse/OGNL-240
> >> >
> >> > Is there something I can do for the project?
> >> >
> >> > -Jason
> >> >
> >> >> -----Original Message-----
> >> >> From: simone.tripodi@gmail.com
> >> >> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
> >> >> Sent: Thursday, March 28, 2013 10:35
> >> >> To: Commons Developers List
> >> >> Subject: Re: [OGNL] A new release
> >> >>
> >> >> Your are welcome, Javin!
> >> >>
> >> >> have a nice day, all the best,
> >> >> -Simo
> >> >>
> >> >> http://people.apache.org/~simonetripodi/
> >> >> http://simonetripodi.livejournal.com/
> >> >> http://twitter.com/simonetripodi
> >> >> http://www.99soft.org/
> >> >>
> >> >>
> >> >> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
> >> <sa...@gmail.com>
> >> >> wrote:
> >> >>> Thanks Simo, that's very neat.
> >> >>>
> >> >>> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
> >> >> <si...@apache.org>wrote:
> >> >>>
> >> >>>>> Is there list of changes, sort of a release notes?
> >> >>>>
> >> >>>> Sure, we track resolved issues with fix version:
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313
> >> > 525&versio
> >> > n=12323958
> >> >>>>
> >> >>>> HTH!
> >> >>>> -Simo
> >> >>>>
> >> >>>> http://people.apache.org/~simonetripodi/
> >> >>>> http://simonetripodi.livejournal.com/
> >> >>>> http://twitter.com/simonetripodi
> >> >>>> http://www.99soft.org/
> >> >>>>
> >> >>>>
> >> >>>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
> >> >> <sa...@gmail.com> wrote:
> >> >>>>> Is there list of changes, sort of a release notes?
> >> >>>>>
> >> >>>>> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
> >> >>>>> <lukaszlenart@apache.org
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>>> I have removed @Deprecated methods, tomorrow will
> >> >> review all the
> >> >>>>>> TODOs. After that we can start planning the release.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
I think OGNL-239 and OGNL-240 are the only real (semi)blocking issues
before we can start a new release.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/12/25 Jason Pyeron <jp...@pdinc.us>:
>> -----Original Message-----
>> From: Benedikt Ritter
>> Sent: Wednesday, December 25, 2013 11:53
>>
>> You've set the issue to status resolved. That's propably the
>
> After adding the patch.
>
>> reason why nobody had a look at it.
>> I don't know if there's anybody planing to roll out a release
>> soon. But low svn activity indicates, that this is not the case...
>
> I took it as a stability indicator... [looks like is active on git
> https://issues.apache.org/jira/browse/OGNL-145?focusedCommentId=13395741&page=co
> m.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13395741]
>
> I am willing to step up to the plate if there are steps or bugs blocking a
> release. When looking through the open 4.0 issues I did not see any notable
> blockers. OGNL-145 is a nice to have, and OGNL-238 may be a limit of Java.
>
> Either way I am going to browse the updates in
> https://github.com/jkuhnert/ognl.git
>
>>
>> Regards,
>> Benedikt
>>
>> Send from my mobile device
>>
>> > Am 25.12.2013 um 06:06 schrieb "Jason Pyeron" <jp...@pdinc.us>:
>> >
>> > I have not seen any updates on subversion since September.
>> Are there
>> > any plans on a release?
>> >
>> > Either way, please commit the patch on
>> > https://issues.apache.org/jira/i#browse/OGNL-240
>> >
>> > Is there something I can do for the project?
>> >
>> > -Jason
>> >
>> >> -----Original Message-----
>> >> From: simone.tripodi@gmail.com
>> >> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
>> >> Sent: Thursday, March 28, 2013 10:35
>> >> To: Commons Developers List
>> >> Subject: Re: [OGNL] A new release
>> >>
>> >> Your are welcome, Javin!
>> >>
>> >> have a nice day, all the best,
>> >> -Simo
>> >>
>> >> http://people.apache.org/~simonetripodi/
>> >> http://simonetripodi.livejournal.com/
>> >> http://twitter.com/simonetripodi
>> >> http://www.99soft.org/
>> >>
>> >>
>> >> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
>> <sa...@gmail.com>
>> >> wrote:
>> >>> Thanks Simo, that's very neat.
>> >>>
>> >>> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
>> >> <si...@apache.org>wrote:
>> >>>
>> >>>>> Is there list of changes, sort of a release notes?
>> >>>>
>> >>>> Sure, we track resolved issues with fix version:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313
>> > 525&versio
>> > n=12323958
>> >>>>
>> >>>> HTH!
>> >>>> -Simo
>> >>>>
>> >>>> http://people.apache.org/~simonetripodi/
>> >>>> http://simonetripodi.livejournal.com/
>> >>>> http://twitter.com/simonetripodi
>> >>>> http://www.99soft.org/
>> >>>>
>> >>>>
>> >>>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
>> >> <sa...@gmail.com> wrote:
>> >>>>> Is there list of changes, sort of a release notes?
>> >>>>>
>> >>>>> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
>> >>>>> <lukaszlenart@apache.org
>> >>>>> wrote:
>> >>>>>
>> >>>>>> I have removed @Deprecated methods, tomorrow will
>> >> review all the
>> >>>>>> TODOs. After that we can start planning the release.
>> >
>> > --
>> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> > - -
>> > - Jason Pyeron PD Inc. http://www.pdinc.us -
>> > - Principal Consultant 10 West 24th Street #100 -
>> > - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
>> > - -
>> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> > This message is copyright PD Inc, subject to license 20080407P00.
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>>
>
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Henri Yandell <fl...@gmail.com>.
JIRA issue reopened btw as I noticed it was still resolved.
On Wed, Dec 25, 2013 at 11:10 AM, Jason Pyeron <jp...@pdinc.us> wrote:
> > -----Original Message-----
> > From: Benedikt Ritter
> > Sent: Wednesday, December 25, 2013 11:53
> >
> > You've set the issue to status resolved. That's propably the
>
> After adding the patch.
>
> > reason why nobody had a look at it.
> > I don't know if there's anybody planing to roll out a release
> > soon. But low svn activity indicates, that this is not the case...
>
> I took it as a stability indicator... [looks like is active on git
>
> https://issues.apache.org/jira/browse/OGNL-145?focusedCommentId=13395741&page=co
>
> m.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13395741]
>
> I am willing to step up to the plate if there are steps or bugs blocking a
> release. When looking through the open 4.0 issues I did not see any notable
> blockers. OGNL-145 is a nice to have, and OGNL-238 may be a limit of Java.
>
> Either way I am going to browse the updates in
> https://github.com/jkuhnert/ognl.git
>
> >
> > Regards,
> > Benedikt
> >
> > Send from my mobile device
> >
> > > Am 25.12.2013 um 06:06 schrieb "Jason Pyeron" <jp...@pdinc.us>:
> > >
> > > I have not seen any updates on subversion since September.
> > Are there
> > > any plans on a release?
> > >
> > > Either way, please commit the patch on
> > > https://issues.apache.org/jira/i#browse/OGNL-240
> > >
> > > Is there something I can do for the project?
> > >
> > > -Jason
> > >
> > >> -----Original Message-----
> > >> From: simone.tripodi@gmail.com
> > >> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
> > >> Sent: Thursday, March 28, 2013 10:35
> > >> To: Commons Developers List
> > >> Subject: Re: [OGNL] A new release
> > >>
> > >> Your are welcome, Javin!
> > >>
> > >> have a nice day, all the best,
> > >> -Simo
> > >>
> > >> http://people.apache.org/~simonetripodi/
> > >> http://simonetripodi.livejournal.com/
> > >> http://twitter.com/simonetripodi
> > >> http://www.99soft.org/
> > >>
> > >>
> > >> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
> > <sa...@gmail.com>
> > >> wrote:
> > >>> Thanks Simo, that's very neat.
> > >>>
> > >>> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
> > >> <si...@apache.org>wrote:
> > >>>
> > >>>>> Is there list of changes, sort of a release notes?
> > >>>>
> > >>>> Sure, we track resolved issues with fix version:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313
> > > 525&versio
> > > n=12323958
> > >>>>
> > >>>> HTH!
> > >>>> -Simo
> > >>>>
> > >>>> http://people.apache.org/~simonetripodi/
> > >>>> http://simonetripodi.livejournal.com/
> > >>>> http://twitter.com/simonetripodi
> > >>>> http://www.99soft.org/
> > >>>>
> > >>>>
> > >>>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
> > >> <sa...@gmail.com> wrote:
> > >>>>> Is there list of changes, sort of a release notes?
> > >>>>>
> > >>>>> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
> > >>>>> <lukaszlenart@apache.org
> > >>>>> wrote:
> > >>>>>
> > >>>>>> I have removed @Deprecated methods, tomorrow will
> > >> review all the
> > >>>>>> TODOs. After that we can start planning the release.
> > >
> > > --
> > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > - -
> > > - Jason Pyeron PD Inc. http://www.pdinc.us -
> > > - Principal Consultant 10 West 24th Street #100 -
> > > - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> > > - -
> > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > This message is copyright PD Inc, subject to license 20080407P00.
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> >
>
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Benedikt Ritter
> Sent: Wednesday, December 25, 2013 11:53
>
> You've set the issue to status resolved. That's propably the
After adding the patch.
> reason why nobody had a look at it.
> I don't know if there's anybody planing to roll out a release
> soon. But low svn activity indicates, that this is not the case...
I took it as a stability indicator... [looks like is active on git
https://issues.apache.org/jira/browse/OGNL-145?focusedCommentId=13395741&page=co
m.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13395741]
I am willing to step up to the plate if there are steps or bugs blocking a
release. When looking through the open 4.0 issues I did not see any notable
blockers. OGNL-145 is a nice to have, and OGNL-238 may be a limit of Java.
Either way I am going to browse the updates in
https://github.com/jkuhnert/ognl.git
>
> Regards,
> Benedikt
>
> Send from my mobile device
>
> > Am 25.12.2013 um 06:06 schrieb "Jason Pyeron" <jp...@pdinc.us>:
> >
> > I have not seen any updates on subversion since September.
> Are there
> > any plans on a release?
> >
> > Either way, please commit the patch on
> > https://issues.apache.org/jira/i#browse/OGNL-240
> >
> > Is there something I can do for the project?
> >
> > -Jason
> >
> >> -----Original Message-----
> >> From: simone.tripodi@gmail.com
> >> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
> >> Sent: Thursday, March 28, 2013 10:35
> >> To: Commons Developers List
> >> Subject: Re: [OGNL] A new release
> >>
> >> Your are welcome, Javin!
> >>
> >> have a nice day, all the best,
> >> -Simo
> >>
> >> http://people.apache.org/~simonetripodi/
> >> http://simonetripodi.livejournal.com/
> >> http://twitter.com/simonetripodi
> >> http://www.99soft.org/
> >>
> >>
> >> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
> <sa...@gmail.com>
> >> wrote:
> >>> Thanks Simo, that's very neat.
> >>>
> >>> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
> >> <si...@apache.org>wrote:
> >>>
> >>>>> Is there list of changes, sort of a release notes?
> >>>>
> >>>> Sure, we track resolved issues with fix version:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313
> > 525&versio
> > n=12323958
> >>>>
> >>>> HTH!
> >>>> -Simo
> >>>>
> >>>> http://people.apache.org/~simonetripodi/
> >>>> http://simonetripodi.livejournal.com/
> >>>> http://twitter.com/simonetripodi
> >>>> http://www.99soft.org/
> >>>>
> >>>>
> >>>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
> >> <sa...@gmail.com> wrote:
> >>>>> Is there list of changes, sort of a release notes?
> >>>>>
> >>>>> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
> >>>>> <lukaszlenart@apache.org
> >>>>> wrote:
> >>>>>
> >>>>>> I have removed @Deprecated methods, tomorrow will
> >> review all the
> >>>>>> TODOs. After that we can start planning the release.
> >
> > --
> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > - -
> > - Jason Pyeron PD Inc. http://www.pdinc.us -
> > - Principal Consultant 10 West 24th Street #100 -
> > - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> > - -
> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > This message is copyright PD Inc, subject to license 20080407P00.
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Benedikt Ritter <be...@gmail.com>.
You've set the issue to status resolved. That's propably the reason why nobody had a look at it.
I don't know if there's anybody planing to roll out a release soon. But low svn activity indicates, that this is not the case...
Regards,
Benedikt
Send from my mobile device
> Am 25.12.2013 um 06:06 schrieb "Jason Pyeron" <jp...@pdinc.us>:
>
> I have not seen any updates on subversion since September. Are there any plans
> on a release?
>
> Either way, please commit the patch on
> https://issues.apache.org/jira/i#browse/OGNL-240
>
> Is there something I can do for the project?
>
> -Jason
>
>> -----Original Message-----
>> From: simone.tripodi@gmail.com
>> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
>> Sent: Thursday, March 28, 2013 10:35
>> To: Commons Developers List
>> Subject: Re: [OGNL] A new release
>>
>> Your are welcome, Javin!
>>
>> have a nice day, all the best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
>> <sa...@gmail.com> wrote:
>>> Thanks Simo, that's very neat.
>>>
>>> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
>> <si...@apache.org>wrote:
>>>
>>>>> Is there list of changes, sort of a release notes?
>>>>
>>>> Sure, we track resolved issues with fix version:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313525&versio
> n=12323958
>>>>
>>>> HTH!
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
>> <sa...@gmail.com> wrote:
>>>>> Is there list of changes, sort of a release notes?
>>>>>
>>>>> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
>>>>> <lukaszlenart@apache.org
>>>>> wrote:
>>>>>
>>>>>> I have removed @Deprecated methods, tomorrow will
>> review all the
>>>>>> TODOs. After that we can start planning the release.
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [OGNL] A new release
Posted by Jason Pyeron <jp...@pdinc.us>.
I have not seen any updates on subversion since September. Are there any plans
on a release?
Either way, please commit the patch on
https://issues.apache.org/jira/i#browse/OGNL-240
Is there something I can do for the project?
-Jason
> -----Original Message-----
> From: simone.tripodi@gmail.com
> [mailto:simone.tripodi@gmail.com] On Behalf Of Simone Tripodi
> Sent: Thursday, March 28, 2013 10:35
> To: Commons Developers List
> Subject: Re: [OGNL] A new release
>
> Your are welcome, Javin!
>
> have a nice day, all the best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul
> <sa...@gmail.com> wrote:
> > Thanks Simo, that's very neat.
> >
> > On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi
> <si...@apache.org>wrote:
> >
> >> > Is there list of changes, sort of a release notes?
> >> >
> >>
> >> Sure, we track resolved issues with fix version:
> >>
> >>
> >>
>
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313525&versio
n=12323958
> >>
> >> HTH!
> >> -Simo
> >>
> >> http://people.apache.org/~simonetripodi/
> >> http://simonetripodi.livejournal.com/
> >> http://twitter.com/simonetripodi
> >> http://www.99soft.org/
> >>
> >>
> >> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul
> <sa...@gmail.com> wrote:
> >> > Is there list of changes, sort of a release notes?
> >> >
> >> > On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart
> >> ><lukaszlenart@apache.org
> >> >wrote:
> >> >
> >> >> I have removed @Deprecated methods, tomorrow will
> review all the
> >> >> TODOs. After that we can start planning the release.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Simone Tripodi <si...@apache.org>.
Your are welcome, Javin!
have a nice day, all the best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Thu, Mar 28, 2013 at 1:49 PM, Javin Paul <sa...@gmail.com> wrote:
> Thanks Simo, that's very neat.
>
> On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi <si...@apache.org>wrote:
>
>> > Is there list of changes, sort of a release notes?
>> >
>>
>> Sure, we track resolved issues with fix version:
>>
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313525&version=12323958
>>
>> HTH!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul <sa...@gmail.com> wrote:
>> > Is there list of changes, sort of a release notes?
>> >
>> > On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart <lukaszlenart@apache.org
>> >wrote:
>> >
>> >> I have removed @Deprecated methods, tomorrow will review all the
>> >> TODOs. After that we can start planning the release.
>> >>
>> >>
>> >> Regards
>> >> --
>> >> Łukasz
>> >> + 48 606 323 122 http://www.lenart.org.pl/
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Thanks
>> > Javin
>> > http://javarevisited.blogspot.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> Thanks
> Javin
> http://javarevisited.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Javin Paul <sa...@gmail.com>.
Thanks Simo, that's very neat.
On Wed, Mar 27, 2013 at 8:39 PM, Simone Tripodi <si...@apache.org>wrote:
> > Is there list of changes, sort of a release notes?
> >
>
> Sure, we track resolved issues with fix version:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313525&version=12323958
>
> HTH!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul <sa...@gmail.com> wrote:
> > Is there list of changes, sort of a release notes?
> >
> > On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart <lukaszlenart@apache.org
> >wrote:
> >
> >> I have removed @Deprecated methods, tomorrow will review all the
> >> TODOs. After that we can start planning the release.
> >>
> >>
> >> Regards
> >> --
> >> Łukasz
> >> + 48 606 323 122 http://www.lenart.org.pl/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
> > --
> > Thanks
> > Javin
> > http://javarevisited.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thanks
Javin
http://javarevisited.blogspot.com/
Re: [OGNL] A new release
Posted by Simone Tripodi <si...@apache.org>.
> Is there list of changes, sort of a release notes?
>
Sure, we track resolved issues with fix version:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313525&version=12323958
HTH!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Wed, Mar 27, 2013 at 1:26 PM, Javin Paul <sa...@gmail.com> wrote:
> Is there list of changes, sort of a release notes?
>
> On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart <lu...@apache.org>wrote:
>
>> I have removed @Deprecated methods, tomorrow will review all the
>> TODOs. After that we can start planning the release.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> Thanks
> Javin
> http://javarevisited.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Javin Paul <sa...@gmail.com>.
Is there list of changes, sort of a release notes?
On Wed, Mar 27, 2013 at 7:09 PM, Lukasz Lenart <lu...@apache.org>wrote:
> I have removed @Deprecated methods, tomorrow will review all the
> TODOs. After that we can start planning the release.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thanks
Javin
http://javarevisited.blogspot.com/
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
I have removed @Deprecated methods, tomorrow will review all the
TODOs. After that we can start planning the release.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Maurizio Cucchiara <mc...@apache.org>.
FYI I've just started a new thread (http://goo.gl/cx1E5) on Struts dev list
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin :http://www.linkedin.com/in/mauriziocucchiara
VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
Maurizio Cucchiara
On 26 March 2013 10:11, Christian Grobmeier <gr...@gmail.com> wrote:
> On Tue, Mar 26, 2013 at 10:05 AM, Maurizio Cucchiara
> <mc...@apache.org> wrote:
>> I thought that it won't be a piece of cake, but we might make it
>> easier, for example what about to start a new branch on struts to
>> integrate the new version of OGNL? (perhaps this is not the right
>> place, or at least the only place, where this discussion should
>> happen)
>
> You are right, lets move it to the struts list.
> But I like the plan.
>
>>
>> Twitter :http://www.twitter.com/m_cucchiara
>> G+ :https://plus.google.com/107903711540963855921
>> Linkedin :http://www.linkedin.com/in/mauriziocucchiara
>> VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
>>
>> Maurizio Cucchiara
>>
>>
>> On 26 March 2013 09:53, Lukasz Lenart <lu...@apache.org> wrote:
>>> 2013/3/26 Christian Grobmeier <gr...@gmail.com>:
>>>> +1, go for it.
>>>> Now its time to see if our testcases are good.
>>>
>>> They are, I made a slight mistake and tests showed that :-)
>>>
>>>> I also think we should test it in conjunction with struts.
>>>
>>> Not so easy, OGNL 4 is a different beast, but I'll try ;-)
>>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Christian Grobmeier <gr...@gmail.com>.
On Tue, Mar 26, 2013 at 10:05 AM, Maurizio Cucchiara
<mc...@apache.org> wrote:
> I thought that it won't be a piece of cake, but we might make it
> easier, for example what about to start a new branch on struts to
> integrate the new version of OGNL? (perhaps this is not the right
> place, or at least the only place, where this discussion should
> happen)
You are right, lets move it to the struts list.
But I like the plan.
>
> Twitter :http://www.twitter.com/m_cucchiara
> G+ :https://plus.google.com/107903711540963855921
> Linkedin :http://www.linkedin.com/in/mauriziocucchiara
> VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
>
> Maurizio Cucchiara
>
>
> On 26 March 2013 09:53, Lukasz Lenart <lu...@apache.org> wrote:
>> 2013/3/26 Christian Grobmeier <gr...@gmail.com>:
>>> +1, go for it.
>>> Now its time to see if our testcases are good.
>>
>> They are, I made a slight mistake and tests showed that :-)
>>
>>> I also think we should test it in conjunction with struts.
>>
>> Not so easy, OGNL 4 is a different beast, but I'll try ;-)
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Maurizio Cucchiara <mc...@apache.org>.
I thought that it won't be a piece of cake, but we might make it
easier, for example what about to start a new branch on struts to
integrate the new version of OGNL? (perhaps this is not the right
place, or at least the only place, where this discussion should
happen)
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin :http://www.linkedin.com/in/mauriziocucchiara
VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
Maurizio Cucchiara
On 26 March 2013 09:53, Lukasz Lenart <lu...@apache.org> wrote:
> 2013/3/26 Christian Grobmeier <gr...@gmail.com>:
>> +1, go for it.
>> Now its time to see if our testcases are good.
>
> They are, I made a slight mistake and tests showed that :-)
>
>> I also think we should test it in conjunction with struts.
>
> Not so easy, OGNL 4 is a different beast, but I'll try ;-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/3/26 Christian Grobmeier <gr...@gmail.com>:
> +1, go for it.
> Now its time to see if our testcases are good.
They are, I made a slight mistake and tests showed that :-)
> I also think we should test it in conjunction with struts.
Not so easy, OGNL 4 is a different beast, but I'll try ;-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Christian Grobmeier <gr...@gmail.com>.
+1, go for it.
Now its time to see if our testcases are good.
I also think we should test it in conjunction with struts.
On Tue, Mar 26, 2013 at 9:31 AM, Lukasz Lenart <lu...@apache.org> wrote:
> Ok, done. Should I just commit the changes? Or do I have to register
> an issue first in JIRA? Maybe it will be better...
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/3/26 Lukasz Lenart <lu...@apache.org>:
>> I'm not sure what API should be removed/renamed/etc as almost
>> everything is public static ;-)
>>
>> Anyway, I'm trying to remove two deprecated classes right now.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/3/8 Christian Grobmeier <gr...@gmail.com>:
>>> On Wed, Mar 6, 2013 at 10:11 AM, sebb <se...@gmail.com> wrote:
>>>> On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
>>>>> Hi,
>>>>>
>>>>> I was checking out what should be solved before releasing a new
>>>>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>>>>> "These nested if statements could be combined" should be resolved, but
>>>>> the rest I don't see a point instead of just satisfying PMD itself.
>>>>>
>>>>> Some of the Findbugs [2] errors are related to generated classes,
>>>>> should I exclude them?
>>>>>
>>>>> Another thing is Checkstyle [3], especially "Missing a Javadoc
>>>>> comment." - I don't know what to put as it without analysing source
>>>>> code deeply.
>>>>>
>>>>> My question is what really should be solved to be ready to release a
>>>>> new version?
>>>>
>>>> I don't personally worry too much about PMD or Checkstyle; they depend
>>>> so much on the rules chosen.
>>>
>>> Guess we need to decide on a few rules here. If they are somehow
>>> connected to method naming et al we should look at them more closely
>>>
>>>
>>>> Findbugs is more useful, but it looks like most of the errors are for
>>>> generated code.
>>>>
>>>> Bugs can be fixed by a new release, but future binary compatibility
>>>> can easily be compromised.
>>>>
>>>> Once a bad or broken API is released, it's very difficult to fix it.
>>>>
>>>> So I would say the most important aspect to get right is to fix
>>>> anything that makes it more difficult to maintain binary compatibility
>>>> in future.
>>>>
>>>> For example, if one of the new methods has a name that is
>>>> non-standard, it is easy to change it now.
>>>> Likewise, if there is a new public method which should be private or
>>>> package protected, do it now.
>>>>
>>>> Or new non-private mutable variables - they make thread-safety - and
>>>> testing - much more difficult
>>>
>>> +1
>>> We should look over all of our methods right now and discuss
>>> everything which is public.
>>>
>>>> Speaking of which, there does not seem to be a Clirr report.
>>>
>>> I have added the clirr report plugin right now. I doesn't report for
>>> the first build, as it cannot compare to anything.
>>> I am bit confused since there is basically no configuration necessary,
>>> just the plugin definition - is it correct?
>>>
>>>> That's very important.
>>>> Apart from checking for unintended compatibility issues, it is useful
>>>> in ensuring that new classes and methods etc. are annotated with
>>>> @since markers.
>>>
>>> We have moved OGNL to 4.0 and Apache - should we annotate everything
>>> with since 4.0.0 then?
>>> Imho it doesn't make much sense to annotate with 3.x, as the package
>>> has changed and both releases are not fully interchangeable
>>>
>>> Cheers
>>>
>>>
>>>>
>>>>> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
>>>>> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
>>>>> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>>>>>
>>>>>
>>>>> Regards
>>>>> --
>>>>> Łukasz
>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
Ok, done. Should I just commit the changes? Or do I have to register
an issue first in JIRA? Maybe it will be better...
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/3/26 Lukasz Lenart <lu...@apache.org>:
> I'm not sure what API should be removed/renamed/etc as almost
> everything is public static ;-)
>
> Anyway, I'm trying to remove two deprecated classes right now.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/3/8 Christian Grobmeier <gr...@gmail.com>:
>> On Wed, Mar 6, 2013 at 10:11 AM, sebb <se...@gmail.com> wrote:
>>> On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
>>>> Hi,
>>>>
>>>> I was checking out what should be solved before releasing a new
>>>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>>>> "These nested if statements could be combined" should be resolved, but
>>>> the rest I don't see a point instead of just satisfying PMD itself.
>>>>
>>>> Some of the Findbugs [2] errors are related to generated classes,
>>>> should I exclude them?
>>>>
>>>> Another thing is Checkstyle [3], especially "Missing a Javadoc
>>>> comment." - I don't know what to put as it without analysing source
>>>> code deeply.
>>>>
>>>> My question is what really should be solved to be ready to release a
>>>> new version?
>>>
>>> I don't personally worry too much about PMD or Checkstyle; they depend
>>> so much on the rules chosen.
>>
>> Guess we need to decide on a few rules here. If they are somehow
>> connected to method naming et al we should look at them more closely
>>
>>
>>> Findbugs is more useful, but it looks like most of the errors are for
>>> generated code.
>>>
>>> Bugs can be fixed by a new release, but future binary compatibility
>>> can easily be compromised.
>>>
>>> Once a bad or broken API is released, it's very difficult to fix it.
>>>
>>> So I would say the most important aspect to get right is to fix
>>> anything that makes it more difficult to maintain binary compatibility
>>> in future.
>>>
>>> For example, if one of the new methods has a name that is
>>> non-standard, it is easy to change it now.
>>> Likewise, if there is a new public method which should be private or
>>> package protected, do it now.
>>>
>>> Or new non-private mutable variables - they make thread-safety - and
>>> testing - much more difficult
>>
>> +1
>> We should look over all of our methods right now and discuss
>> everything which is public.
>>
>>> Speaking of which, there does not seem to be a Clirr report.
>>
>> I have added the clirr report plugin right now. I doesn't report for
>> the first build, as it cannot compare to anything.
>> I am bit confused since there is basically no configuration necessary,
>> just the plugin definition - is it correct?
>>
>>> That's very important.
>>> Apart from checking for unintended compatibility issues, it is useful
>>> in ensuring that new classes and methods etc. are annotated with
>>> @since markers.
>>
>> We have moved OGNL to 4.0 and Apache - should we annotate everything
>> with since 4.0.0 then?
>> Imho it doesn't make much sense to annotate with 3.x, as the package
>> has changed and both releases are not fully interchangeable
>>
>> Cheers
>>
>>
>>>
>>>> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
>>>> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
>>>> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>>>>
>>>>
>>>> Regards
>>>> --
>>>> Łukasz
>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
I'm not sure what API should be removed/renamed/etc as almost
everything is public static ;-)
Anyway, I'm trying to remove two deprecated classes right now.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/3/8 Christian Grobmeier <gr...@gmail.com>:
> On Wed, Mar 6, 2013 at 10:11 AM, sebb <se...@gmail.com> wrote:
>> On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
>>> Hi,
>>>
>>> I was checking out what should be solved before releasing a new
>>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>>> "These nested if statements could be combined" should be resolved, but
>>> the rest I don't see a point instead of just satisfying PMD itself.
>>>
>>> Some of the Findbugs [2] errors are related to generated classes,
>>> should I exclude them?
>>>
>>> Another thing is Checkstyle [3], especially "Missing a Javadoc
>>> comment." - I don't know what to put as it without analysing source
>>> code deeply.
>>>
>>> My question is what really should be solved to be ready to release a
>>> new version?
>>
>> I don't personally worry too much about PMD or Checkstyle; they depend
>> so much on the rules chosen.
>
> Guess we need to decide on a few rules here. If they are somehow
> connected to method naming et al we should look at them more closely
>
>
>> Findbugs is more useful, but it looks like most of the errors are for
>> generated code.
>>
>> Bugs can be fixed by a new release, but future binary compatibility
>> can easily be compromised.
>>
>> Once a bad or broken API is released, it's very difficult to fix it.
>>
>> So I would say the most important aspect to get right is to fix
>> anything that makes it more difficult to maintain binary compatibility
>> in future.
>>
>> For example, if one of the new methods has a name that is
>> non-standard, it is easy to change it now.
>> Likewise, if there is a new public method which should be private or
>> package protected, do it now.
>>
>> Or new non-private mutable variables - they make thread-safety - and
>> testing - much more difficult
>
> +1
> We should look over all of our methods right now and discuss
> everything which is public.
>
>> Speaking of which, there does not seem to be a Clirr report.
>
> I have added the clirr report plugin right now. I doesn't report for
> the first build, as it cannot compare to anything.
> I am bit confused since there is basically no configuration necessary,
> just the plugin definition - is it correct?
>
>> That's very important.
>> Apart from checking for unintended compatibility issues, it is useful
>> in ensuring that new classes and methods etc. are annotated with
>> @since markers.
>
> We have moved OGNL to 4.0 and Apache - should we annotate everything
> with since 4.0.0 then?
> Imho it doesn't make much sense to annotate with 3.x, as the package
> has changed and both releases are not fully interchangeable
>
> Cheers
>
>
>>
>>> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
>>> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
>>> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Christian Grobmeier <gr...@gmail.com>.
On Wed, Mar 6, 2013 at 10:11 AM, sebb <se...@gmail.com> wrote:
> On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
>> Hi,
>>
>> I was checking out what should be solved before releasing a new
>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>> "These nested if statements could be combined" should be resolved, but
>> the rest I don't see a point instead of just satisfying PMD itself.
>>
>> Some of the Findbugs [2] errors are related to generated classes,
>> should I exclude them?
>>
>> Another thing is Checkstyle [3], especially "Missing a Javadoc
>> comment." - I don't know what to put as it without analysing source
>> code deeply.
>>
>> My question is what really should be solved to be ready to release a
>> new version?
>
> I don't personally worry too much about PMD or Checkstyle; they depend
> so much on the rules chosen.
Guess we need to decide on a few rules here. If they are somehow
connected to method naming et al we should look at them more closely
> Findbugs is more useful, but it looks like most of the errors are for
> generated code.
>
> Bugs can be fixed by a new release, but future binary compatibility
> can easily be compromised.
>
> Once a bad or broken API is released, it's very difficult to fix it.
>
> So I would say the most important aspect to get right is to fix
> anything that makes it more difficult to maintain binary compatibility
> in future.
>
> For example, if one of the new methods has a name that is
> non-standard, it is easy to change it now.
> Likewise, if there is a new public method which should be private or
> package protected, do it now.
>
> Or new non-private mutable variables - they make thread-safety - and
> testing - much more difficult
+1
We should look over all of our methods right now and discuss
everything which is public.
> Speaking of which, there does not seem to be a Clirr report.
I have added the clirr report plugin right now. I doesn't report for
the first build, as it cannot compare to anything.
I am bit confused since there is basically no configuration necessary,
just the plugin definition - is it correct?
> That's very important.
> Apart from checking for unintended compatibility issues, it is useful
> in ensuring that new classes and methods etc. are annotated with
> @since markers.
We have moved OGNL to 4.0 and Apache - should we annotate everything
with since 4.0.0 then?
Imho it doesn't make much sense to annotate with 3.x, as the package
has changed and both releases are not fully interchangeable
Cheers
>
>> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
>> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
>> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by sebb <se...@gmail.com>.
On 6 March 2013 06:49, Lukasz Lenart <lu...@apache.org> wrote:
> Hi,
>
> I was checking out what should be solved before releasing a new
> version and in my opinion most of PMD [1] errors can be omitted, maybe
> "These nested if statements could be combined" should be resolved, but
> the rest I don't see a point instead of just satisfying PMD itself.
>
> Some of the Findbugs [2] errors are related to generated classes,
> should I exclude them?
>
> Another thing is Checkstyle [3], especially "Missing a Javadoc
> comment." - I don't know what to put as it without analysing source
> code deeply.
>
> My question is what really should be solved to be ready to release a
> new version?
I don't personally worry too much about PMD or Checkstyle; they depend
so much on the rules chosen.
Findbugs is more useful, but it looks like most of the errors are for
generated code.
Bugs can be fixed by a new release, but future binary compatibility
can easily be compromised.
Once a bad or broken API is released, it's very difficult to fix it.
So I would say the most important aspect to get right is to fix
anything that makes it more difficult to maintain binary compatibility
in future.
For example, if one of the new methods has a name that is
non-standard, it is easy to change it now.
Likewise, if there is a new public method which should be private or
package protected, do it now.
Or new non-private mutable variables - they make thread-safety - and
testing - much more difficult
Speaking of which, there does not seem to be a Clirr report.
That's very important.
Apart from checking for unintended compatibility issues, it is useful
in ensuring that new classes and methods etc. are annotated with
@since markers.
> [1] http://commons.apache.org/proper/commons-ognl/pmd.html
> [2] http://commons.apache.org/proper/commons-ognl/findbugs.html
> [3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
Hi,
I was checking out what should be solved before releasing a new
version and in my opinion most of PMD [1] errors can be omitted, maybe
"These nested if statements could be combined" should be resolved, but
the rest I don't see a point instead of just satisfying PMD itself.
Some of the Findbugs [2] errors are related to generated classes,
should I exclude them?
Another thing is Checkstyle [3], especially "Missing a Javadoc
comment." - I don't know what to put as it without analysing source
code deeply.
My question is what really should be solved to be ready to release a
new version?
[1] http://commons.apache.org/proper/commons-ognl/pmd.html
[2] http://commons.apache.org/proper/commons-ognl/findbugs.html
[3] http://commons.apache.org/proper/commons-ognl/checkstyle.html
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/3/1 Olivier Lamy <ol...@apache.org>:
> to test website it's the usual: mvn clean site (then browse files in
> target/site/)
> to deploy: mvn clean site-deploy.
> and site-content must excluded from rat. Do you want to fix that ? If not I can.
I just moved site-content into target/ folder and that solved the
problem. But feel free to add the exclude, then I will learn something
new :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Olivier Lamy <ol...@apache.org>.
to test website it's the usual: mvn clean site (then browse files in
target/site/)
to deploy: mvn clean site-deploy.
and site-content must excluded from rat. Do you want to fix that ? If not I can.
2013/3/1 Lukasz Lenart <lu...@apache.org>:
> 2013/3/1 Lukasz Lenart <lu...@apache.org>:
>> How can I update ognl website? Simple checkout [1] and update what I
>> need? and then what to do?
>
> I found this [1], but I have one question, how to check locally how
> the site will look like before deploying it? I have the only solution:
>
> mvn clean site
> copy target/site into site-content
>
> is that ok?
>
> [1] http://commons.apache.org/site-publish.html
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [OGNL] A new release
Posted by Lukasz Lenart <lu...@apache.org>.
2013/3/1 Lukasz Lenart <lu...@apache.org>:
> How can I update ognl website? Simple checkout [1] and update what I
> need? and then what to do?
I found this [1], but I have one question, how to check locally how
the site will look like before deploying it? I have the only solution:
mvn clean site
copy target/site into site-content
is that ok?
[1] http://commons.apache.org/site-publish.html
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org