Apache Commons Daemon 1.0.13 based on RC1 is ready.
It contains a fix for regression found in previous release(s).
Binaries and sources for testing are at [1], dist layout is at [2],
generated site can be found at [3]. Tag is [4] which will be renamed to
COMMONS_DAEMON_1_0_13 if voted.
Please v
On 02/06/2013 09:38 PM, sebb wrote:
On 6 February 2013 20:15, Mladen Turk wrote:
On 02/06/2013 07:26 PM, Mladen Turk wrote:
Perhaps you managed to lock out your account?
OK, I was able to upload using .zip file made manually from
my local ~/.m2.
So given all seems there are some serious in
On 02/06/2013 09:38 PM, sebb wrote:
On 6 February 2013 20:15, Mladen Turk wrote:
On 02/06/2013 07:26 PM, Mladen Turk wrote:
I have everything set up in maven config file as before when this
operation was successful.
Now I have different problem.
deploy constantly times out. It uploads few
Yup. I have no idea why I said that. While you can certainly pass the options
HttpClientFactory wouldn't do anything with them.
Ralph
On Feb 6, 2013, at 2:09 AM, Jean-Marc Borer wrote:
> I found this entry in JIRA:
>
> https://issues.apache.org/jira/browse/VFS-249
>
> Actually it is not tru
On 6 February 2013 20:15, Mladen Turk wrote:
> On 02/06/2013 07:26 PM, Mladen Turk wrote:
>>
>>
>> I have everything set up in maven config file as before when this
>> operation was successful.
>>
>
> Now I have different problem.
> deploy constantly times out. It uploads few files but then it jus
>
> As for efficiency (or faster execution, if you want), I don't see the
> point in doubting that tasks like global search (e.g. in a genetic
> algorithm) will complete in less time when run in parallel...
Just a quick note. This statement is incorrect. Parallelization should be done
at the co
On 02/06/2013 07:26 PM, Mladen Turk wrote:
I have everything set up in maven config file as before when this operation was
successful.
Now I have different problem.
deploy constantly times out. It uploads few files but then it just sits for
a minute a so and fails with timeout.
I have tried
On 6 February 2013 11:24, Simone Tripodi wrote:
>> Boolean.valueOf( false ) ) ); // or just valueOf( false )? ;-)
One should never do that. Just use Boolean.FALSE
> or just
>
> import static Boolean.FALSE
>
> then
>
> on( testBean ).invoke( "setBooleanProperty" ).with( argument( FALSE )
On 02/06/2013 07:26 PM, Mladen Turk wrote:
I have everything set up in maven config file as before when this operation was
successful.
Crap I have deleted my ~/.m2 directory together
with security-settings.xml. Sorry for the noise :)
Regards
--
^TM
-
Hi,
Exactly the same config as couple of weeks back now gives:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project commons-daemon: Failed to deploy artifacts: Could not transfer artifact commons-daemon:commons-daemon:jar:1.0.13 from/
On 2/6/13 9:03 AM, Gilles wrote:
> On Wed, 06 Feb 2013 07:19:47 -0800, Phil Steitz wrote:
>> On 2/5/13 6:08 AM, Gilles wrote:
>>> Hi.
>>>
>>> In the thread about "static import", Stephen noted that decisions
>>> on a
>>> component's evolution are dependent on whether the future of the
>>> Java
>>>
On Wed, Feb 6, 2013 at 12:03 PM, Gilles wrote:
> On Wed, 06 Feb 2013 07:19:47 -0800, Phil Steitz wrote:
>
>> On 2/5/13 6:08 AM, Gilles wrote:
>>
>>> Hi.
>>>
>>> In the thread about "static import", Stephen noted that decisions
>>> on a
>>> component's evolution are dependent on whether the future
On Wed, 06 Feb 2013 07:19:47 -0800, Phil Steitz wrote:
On 2/5/13 6:08 AM, Gilles wrote:
Hi.
In the thread about "static import", Stephen noted that decisions
on a
component's evolution are dependent on whether the future of the
Java
language is taken into account, or not.
A question on the sa
On 01/31/2013 12:01 AM, Jörg Schaible wrote:
> sebb wrote:
>
>> On 30 January 2013 18:18, Jörg Schaible wrote:
>>> Hi,
>>>
>>> sebb wrote:
>>>
>>> [snip]
>>>
>> /** a map of the required options */
>> +// N.B. This can contain either a String (addOption) or an
>> OptionGroup
On Wed, 06 Feb 2013 17:32:06 +0100, Thomas Neidhart wrote:
On 02/06/2013 05:28 PM, Gilles wrote:
On Wed, 06 Feb 2013 15:48:43 +0100, Thomas Neidhart wrote:
Hi,
well, I did not work much on cli, but lately I have cleanup up
together
with sebb the trunk, and I think it is in a state that could
On 02/06/2013 05:28 PM, Gilles wrote:
> On Wed, 06 Feb 2013 15:48:43 +0100, Thomas Neidhart wrote:
>> Hi,
>>
>> well, I did not work much on cli, but lately I have cleanup up together
>> with sebb the trunk, and I think it is in a state that could be released
>> soon:
>>
>> * there are no open maj
On Wed, 06 Feb 2013 15:48:43 +0100, Thomas Neidhart wrote:
Hi,
well, I did not work much on cli, but lately I have cleanup up
together
with sebb the trunk, and I think it is in a state that could be
released
soon:
* there are no open major issues (most issues are related to cli2)
Well, th
Local Maven 2 Build Definition (Java 1.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Continuum-Build-Host: vmbuild
X-Continuum-Project-Id: 129
X-Continuum-Project-Name: Commons VFS
Online report :
http://vmbuild.apache.org/continuum/bu
Hi,
I am curious also if anyone can confirm whether my understanding of
https://issues.apache.org/jira/browse/FILEUPLOAD-145 is correct.
My understanding is that previously when you used setMaxFileSize and
attempted to upload a file that exceeded the limit, an exception would not
be thrown unt
Hi,
2013/2/6 Gary Gregory
> IMO, any [commons] component can update it's Java requirement as it sees
> fit. I would rather see /one/ [math] component instead of two.
>
> My advise would be to (1) plan for a version 3.2 that is based Java 6 or 7
> and release 3.1.x versions for bug fixes only.
>
On 2/5/13 6:08 AM, Gilles wrote:
> Hi.
>
> In the thread about "static import", Stephen noted that decisions
> on a
> component's evolution are dependent on whether the future of the Java
> language is taken into account, or not.
> A question on the same theme also arose after the presentation of
>
And the tests that rely on internet: I have to use a web proxy with
authentication that seems not to work in the units tests...
On Wed, Feb 6, 2013 at 3:16 PM, Jean-Marc Borer wrote:
> Now it is fine. Let's see the remaining issues now. The only problem
> that remains is my corporate anti virus t
Now it is fine. Let's see the remaining issues now. The only problem
that remains is my corporate anti virus that will prevent the usage of
some ports...
On Wed, Feb 6, 2013 at 3:06 PM, Jean-Marc Borer wrote:
> Hmm. My trunk build fails:
>
> Failed to execute goal on project commons-vfs2: Could
Hmm. My trunk build fails:
Failed to execute goal on project commons-vfs2: Could not resolve
dependencies for project
org.apache.commons:commons-vfs2:jar:2.1-SNAPSHOT: The following
artifacts could not be resolved:
org.bouncycastle:bcprov-jdk15on:jar:1.46,
org.apache.jackrabbit:jackrabbit-standalo
I am currently trying to build trunk.
What I can say already is that I needed to patch VFS 2.0 from tag
(common-vfs2...). There my modifications worked perfectly.
Let's see if I can do the same for trunk.
On Wed, Feb 6, 2013 at 2:56 PM, Gary Gregory wrote:
> I've update my JIRA comment, please
IMO, any [commons] component can update it's Java requirement as it sees
fit. I would rather see /one/ [math] component instead of two.
My advise would be to (1) plan for a version 3.2 that is based Java 6 or 7
and release 3.1.x versions for bug fixes only.
Alternatively, you could (1) plan for a
On 02/05/2013 03:08 PM, Gilles wrote:
> Hi.
>
> In the thread about "static import", Stephen noted that decisions on a
> component's evolution are dependent on whether the future of the Java
> language is taken into account, or not.
> A question on the same theme also arose after the presentation
I've update my JIRA comment, please see
https://issues.apache.org/jira/browse/VFS-369?focusedCommentId=13566566&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13566566
Can you this please:
- Get the latest from trunk.
- Apply the patch
https://issues.apache.org/jira
Yup. Already fixed these issues in my code.
For example:
Element error =
davExc.toXml(DomUtil.BUILDER_FACTORY.newDocumentBuilder().newDocument());
becomes:
Element error = davExc.toXml(DomUtil.createDocument());
Not sure, but the patches provided in JIRA seem already to fix those issue.
On Wed
Hi,
well, I did not work much on cli, but lately I have cleanup up together
with sebb the trunk, and I think it is in a state that could be released
soon:
* there are no open major issues (most issues are related to cli2)
* no findbugs & checkstyle warnings anymore
* trunk contains lots of fix
Hi All,
Just wondering when FileUpload 1.3 is due to be released? In particular, I
am interested in the fix for
https://issues.apache.org/jira/browse/FILEUPLOAD-145 which is marked as
being fixed in 1.3.
>From http://commons.apache.org/fileupload/ it looks like that last release
was FileUploa
There are some adaptations to do, but then it works flawlessly with my
tests and WebDAV repositories.
On Wed, Feb 6, 2013 at 1:41 PM, Jean-Marc Borer wrote:
> Hello list guys,
>
> Has anyone something to say against updating the Jackrabbit version
> used in Commons VFS?
>
> There will be some sma
Hello list guys,
Has anyone something to say against updating the Jackrabbit version
used in Commons VFS?
There will be some small adaptations but 1.5.2 is becoming quiet old
now. Any counter arguments?
Cheers,
Jean-Marc
-
To
2013/2/6 Simone Tripodi
> > Haven't done that for implementation of setMapped(). Should I create an
> > issue
>
> That would be the always ideal case, so we have the complete
> perspective of things we've worked on.
>
> > and at least add it to changes.xml?
>
> Yes please, if you do have the tim
> Haven't done that for implementation of setMapped(). Should I create an
> issue
That would be the always ideal case, so we have the complete
perspective of things we've worked on.
> and at least add it to changes.xml?
Yes please, if you do have the time also to review past issues would be gre
Create a patch for trunk please.
Gary
On Feb 6, 2013, at 5:23, Jean-Marc Borer wrote:
> Hi Benedikt,
>
> When I will provide the patch, will it be integrated into VFS?
>
> As I use Maven to build my projects, I would like to see my patch
> beeing published then in the next release of VFS.
>
> H
2013/2/6 Simone Tripodi
> > Definitely a good idea. This is what we did for other parts of the API as
> > well.
>
> yup I didn't remember where/with who I discussed already that.
>
> Please back everything with an issue and don't forget to include the
> issue key in the commit message.
>
I'll do
2013/2/6 Simone Tripodi
> > Boolean.valueOf( false ) ) ); // or just valueOf( false )? ;-)
>
> or just
>
> import static Boolean.FALSE
>
> then
>
> on( testBean ).invoke( "setBooleanProperty" ).with( argument( FALSE )
> );
>
> which is less verbose and avoids the potential naming conflict
> Definitely a good idea. This is what we did for other parts of the API as
> well.
yup I didn't remember where/with who I discussed already that.
Please back everything with an issue and don't forget to include the
issue key in the commit message.
alles gute,
-Simo
http://people.apache.org/~si
> Boolean.valueOf( false ) ) ); // or just valueOf( false )? ;-)
or just
import static Boolean.FALSE
then
on( testBean ).invoke( "setBooleanProperty" ).with( argument( FALSE ) );
which is less verbose and avoids the potential naming conflict.
-Simo
http://people.apache.org/~simonetrip
Hi Benedikt,
When I will provide the patch, will it be integrated into VFS?
As I use Maven to build my projects, I would like to see my patch
beeing published then in the next release of VFS.
However do you know how long this takes usually? Is VFS releasing new
versions in short cycles or do we
https://issues.apache.org/jira/browse/VFS-453
Patch will come soon
On Wed, Feb 6, 2013 at 10:09 AM, Benedikt Ritter wrote:
> Hi Jean-Marc,
>
>
> 2013/2/6 Jean-Marc Borer
>
>> OK. You seem to like the feature.
>>
>> Can I provide the patch for integration then? To whom should I send it?
>>
>
> P
I found this entry in JIRA:
https://issues.apache.org/jira/browse/VFS-249
Actually it is not true that it is fixed. Looking at the code Ralph
Goers's explanation are not correct. It should be reopened.
I will create a new entry.
On Wed, Feb 6, 2013 at 9:51 AM, Jean-Marc Borer wrote:
> OK. You
Hi Jean-Marc,
2013/2/6 Jean-Marc Borer
> OK. You seem to like the feature.
>
> Can I provide the patch for integration then? To whom should I send it?
>
Please create an issue in JIRA [1] for vfs and attach your svn patch file
to it.
Benedikt
[1] https://issues.apache.org/jira/secure/Dashboa
OK. You seem to like the feature.
Can I provide the patch for integration then? To whom should I send it?
On Tue, Feb 5, 2013 at 10:06 PM, Mark Fortner wrote:
> Perhaps not for local file systems, but I would imagine that any kind of
> distributed file system would have need of a socket timeout.
2013/2/5 Benedikt Ritter
> Hi Simo,
>
>
> 2013/2/5 Simone Tripodi
>
>> Guten Tag, Bene,
>>
>> > I personally try to avoid static imports.
>> > Especially when you come to a legacy code base IMHO it makes the code
>> > harder to understand.
>>
>> as BU2 user, would you write the following sentenc
Hi Simo,
2013/2/6 Simone Tripodi
> Guten Morgen,
>
> > +/**
> > + * Use a custom {@link ClassLoader} for loading the class.
> > + *
> > + * @param classLoader the {@link ClassLoader} to load the class.
> > + * @return the {@link ClassAccessor} for the class being loaded.
> >
47 matches
Mail list logo
