+1
If you do all of them, then we should also add the agreed
checkstyle.xml or equivalent code style file, so that it's easy to
keep compliance.
+1 for checkstyle, -1 for any IDE depending files.
-- barthel
-
To unsubscrib
As Clirr is internally based on BCEL, I'd rather see us build a new
tool on top of ASM, which is very well maintained. Besides, that would
solve the license problem.
Sounds like a existing idea. I'm interested in to contribute.
-- barthel
-
+1 BUT only with a MAJOR version change.
-- barthel
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Apache Commons Crypto
> On 25 Mar 2016, at 15:04, Benedikt Ritter wrote:
>
> Hi,
>
> after we've accepted the Chimera project [1] as new Apache Commons project,
> it's time to decide on a name. I've used Apache Commons Crypto in the past,
> but some have argued that it isn't to the point.
> I
+1 (non-binding)
--
bart...@x-reizend.de
> On 21 Mar 2016, at 11:05, Sergio Fernández wrote:
>
> +1 (non-binding)
>
> On Mon, Mar 21, 2016 at 10:39 AM, Luc Maisonobe wrote:
>
>> +1 for new component.
>>
>> Luc
>>
>> Le 21/03/2016 09:57, Bernd Eckenfels a écrit :
>>> +1 Accept Chimera as
ary Gregory wrote:
>>> On Tue, Nov 24, 2015 at 11:57 PM, Uwe Barthel
>> wrote:
>>>
>>>>
>>>>> Do you like to start these changes before or after the release 1.4?
>>>>>>> I prefer to create the release as soon as possible and
> Do you like to start these changes before or after the release 1.4?
> I prefer to create the release as soon as possible and start rework on
that baseline.
Maybe my statement was a bit ambiguous. I'm fine with a Java version 1.6 or
1.7 but would not wait until the code is overall refurbishe
> I've updated JXPATH to Java 7. There is a lot of work to update the code
> base to use Java 7 languages features and APIs. I invite everybody to join
> me here…
Do you like to start these changes before or after the release 1.4?
I prefer to create the release as soon as possible and start rework
Java 1.6 would be old enough I think.
But, JXPath doesn't follow the three digit version schema.
So any change of Java dependency may should force a major change.
How will it handled in other Commons with projects two digit version schema?
Maybe should be used: http://www.mojohaus.org/animal-snif
Hi,
How is the road map for the 4.1 release or is there a plan to provide 4.0.1?
-- Uwe
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Hi,
https://issues.apache.org/jira/browse/JXPATH-170 (OPEN) is a verified duplicate
of https://issues.apache.org/jira/browse/JXPATH-142 (RESOLVED).
Please mark JXPATH-170 as fixed or close this item.
-- Uwe
-
To unsubscribe, e-
Hi,
I’ve opened the first 3 pull requests for JXPath.
All of these are patches or tests attached on JIRA items.
https://issues.apache.org/jira/browse/JXPATH-118
https://issues.apache.org/jira/browse/JXPATH-160
https://issues.apache.org/jira/browse/JXPATH-177
Maybe merge the pull requests provide
Hi,
I'm not a committer but interested and looking forward to work on/with both
solutions.
-- Uwe
On November 20, 2015 6:50:53 PM Phil Steitz wrote:
On 11/20/15 7:33 AM, Bertrand Delacretaz wrote:
Hi Eirik,
On Fri, Nov 20, 2015 at 7:52 AM, Eirik Bjørsnøs wrote:
...Do we need a declare
e and maybe used as baseline for a
code refurbishment.
-- Uwe
> On 18 Nov 2015, at 19:57, Benedikt Ritter wrote:
>
> 2015-11-18 16:45 GMT+01:00 Gary Gregory :
>
>> On Nov 18, 2015 4:18 AM, "Benedikt Ritter" wrote:
>>>
>>> Hello Uwe,
>>&g
Hi,
If there is any 1.4 release planned?
Not only this resolved item JXPATH-131 is really interesting to find in a new
release.
Which Apache Commons committer is ready to bring JXPath one step forward and
carry out a new release after more than 2 years?
I'll contribute/support if something to
Hi,
If there is any 1.4 release planned?
Not only this resolved item https://issues.apache.org/jira/browse/JXPATH-131 is
really interesting to find in a new release.
Which Apache Commons committer is ready to bring JXPath one step forward and
carry out a new release after more than 2 years?
I'
Thx Thomas.
The fix for the Java serialization vulnerability is on the way.
Now should we add some information on
http://commons.apache.org/security.html like Commons Compress did?
-- Uwe
On November 14, 2015 10:59:52 AM Thomas Neidhart
wrote:
On 11/13/2015 12:31 AM, Thomas Neidhart wr
+2 :-)
mit freundlichen Grüßen
Uwe Barthel
--
bart...@x-reizend.de
> On 13 Nov 2015, at 18:22, Jörg Schaible wrote:
>
> Hi Bertrand,
>
> Bertrand Delacretaz wrote:
>
>> Hi,
>>
>> I've just subscribed to this list after briefly discussing this with
rüßen
Uwe Barthel
--
bart...@x-reizend.de
> On 31 Oct 2015, at 11:01, Siegfried Goeschl
> wrote:
>
> Hi Uwe,
>
> for such small components Apache incubator is sort of overkill - setup can be
> daunting and Naomi is unlikely to attract a large community. That’s the
> r
this idea.
mit freundlichen Grüßen
Uwe Barthel
--
bart...@x-reizend.de
> On 30 Oct 2015, at 20:14, Gary Gregory wrote:
>
> On Fri, Oct 30, 2015 at 10:23 AM, Emmanuel Bourg wrote:
>
>> Le 30/10/2015 13:03, Dave Brosius a écrit :
>>
>>> I certainly respect yo
/foundation/how-it-works.html#incubator
mit freundlichen Grüßen
Uwe Barthel
--
bart...@x-reizend.de
> On 30 Oct 2015, at 01:42, Phil Steitz wrote:
>
> This is a VOTE to accept the code discussed in [1] and available for
> review using the git commands below. All are welcome to
21 matches
Mail list logo
