Thank you for driving this update Thomas. I noticed too late that
src/conf/MANIFEST.MF is missing from the sources, this breaks the Ant
build (which is still used in Debian).
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr
Hi,
I did not test the ant build, but I explicitly removed the MANIFEST.MF as
this has to be created by the relevant plugins as setup in the
commons-parent.pom (especially for proper OSGI metadata).
I will take a look this evening how to mitigate this.
Thomas
On Mon, Nov 16, 2015 at 11:19 AM, E
Would it be much effort to switch to a maven-style build as it is done
already for the commons-lang3 package in debian?
This release of commons-collections 3.2.2 depends on the latest
commons-parent, so the build should be pretty much the same as for lang
(especially as there are no special plugins
Le 16/11/2015 12:07, Thomas Neidhart a écrit :
> Would it be much effort to switch to a maven-style build as it is done
> already for the commons-lang3 package in debian?
It isn't difficult but the issue is the backport to the previous Debian
releases, the delta with the released versions should b
The problem is that the resulting manifest will be different for the ant
and maven builds (as for most other components).
Thomas
On Mon, Nov 16, 2015 at 12:18 PM, Emmanuel Bourg wrote:
> Le 16/11/2015 12:07, Thomas Neidhart a écrit :
> > Would it be much effort to switch to a maven-style build
Le 16/11/2015 12:33, Thomas Neidhart a écrit :
> The problem is that the resulting manifest will be different for the ant
> and maven builds (as for most other components).
The manifest can be slightly different, I just need the Ant build to
produce a jar without error, and the compiled classes in
I have the Debian builds still on my agenda but will not have the time to
work on that until end of the year.
2015-11-16 13:01 GMT+01:00 Emmanuel Bourg :
> Le 16/11/2015 12:33, Thomas Neidhart a écrit :
> > The problem is that the resulting manifest will be different for the ant
> > and maven bui
On 11/13/2015 08:12 AM, Gilles wrote:
On Mon, 9 Nov 2015 10:34:43 -0600, Ole Ersoy wrote:
If I'm interested in some functionality that is 'beta' then I first
have to realize that it's 'beta'...Maybe just tag the branch beta.
After that there's probably (Judging from the number of people
commun
2015-11-14 21:57 GMT+01:00 Gary Gregory :
> In trunk I get:
>
> Failed tests:
> org.apache.commons.beanutils.bugs.Jira422TestCase#testRootBean
> ComparisonFailure
> org.apache.commons.beanutils.bugs.Jira422TestCase#testSecondChildBean
> ComparisonFailure
> org.apache.commons.beanutils.Indexe
Hello Micha,
2015-11-15 1:47 GMT+01:00 Micha Pringle :
> I really apologize, it seems the link below still managed to include a
> period despite my best efforts. Please tryhttps://
> github.com/michapringle/fluentStringUtils
>
> Cheers,Micha From: Micha Pringle
> To: "dev@commons.apache.or
Hi Benedikt,
Thanks for the reply.
I will update the current code and make the following changes, then notify the
mail list when it is complete for further review.* Java 8 will be downgraded to
Java 6. That's my own fault for unit testing with lambda's.* I would prefer to
keep the annotations (e
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'
Hello again,
2015-11-16 20:22 GMT+01:00 Micha Pringle :
> Hi Benedikt,
>
> Thanks for the reply.
>
> I will update the current code and make the following changes, then notify
> the mail list when it is complete for further review.
> * Java 8 will be downgraded to Java 6. That's my own fault for
Am 16.11.2015 um 19:53 schrieb Benedikt Ritter:
> 2015-11-14 21:57 GMT+01:00 Gary Gregory :
>
>> In trunk I get:
>>
>> Failed tests:
>> org.apache.commons.beanutils.bugs.Jira422TestCase#testRootBean
>> ComparisonFailure
>> org.apache.commons.beanutils.bugs.Jira422TestCase#testSecondChildBean
Hi all,
In trying to solve some customer issues we're having, mainly to
do with trying to browse HDFS files when the Name Node is configured for
High-Availability, I found I needed to make some more changes/additions to the
VFS HDFS Provider. I have attached a diff/patch file.
I don't see the patch. It might be stripped off by the mail server.
From: Roger Whitcomb [mailto:roger.whitc...@actian.com]
Sent: Monday, November 16, 2015 5:12 PM
To: Commons Developers List
Subject: [VFS] Further changes to HDFS Provider for alternate configuration
support
Hi all,
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
17 matches
Mail list logo
