To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs has an issue affecting its community integration.
This issue a
On 14 November 2010 03:31, Daniel F. Savarese wrote:
>
> In message ,
> sebb
> writes:
>>This is a vote to release Apache Commons NET 2.2.
>>[X ] -1 no, do not release it because...
>
> I object to commons-net-2.2-javadoc.jar and commons-net-2.2-sources.jar
> being included in and unnecessarily
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
The change of VFS package name has broken lots of Gump builds - which
is to be expected.
Looking at how this has been solved for other projects, one way to
solve this is to create a branch for the VFS 1.x code and use that for
the current VFS.
Then we create a build for VFS 2.
Gump does warn us t
On 14 November 2010 11:17, sebb wrote:
> The change of VFS package name has broken lots of Gump builds - which
> is to be expected.
>
> Looking at how this has been solved for other projects, one way to
> solve this is to create a branch for the VFS 1.x code and use that for
> the current VFS.
> T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-quartz has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
Just noticed that there are no @since markers for any of the additions
to the code made since 1.0.
I think these are important, and should be present.
I'm happy to add them to the code-base.
-
To unsubscribe, e-mail: dev-unsubsc
Hello,
One large change that was done for version 2.1 was to add a way to
compute the partial derivatives of an ODE final state with respect to
both its initial state and problem parameters. This was done by creating
a new ode.jacobians package.
As time as shown, this attempt is really clumsy. So
Hi Luc.
> Author: luc
> Date: Sun Nov 14 15:06:11 2010
> New Revision: 1035003
>
> URL: http://svn.apache.org/viewvc?rev=1035003&view=rev
> Log:
> fixed message building so the behavior matches the existing javadoc:
> general arguments are the ones remaining after the specific ones have been
> h
Le 14/11/2010 21:57, Gilles Sadowski a écrit :
> Hi Luc.
Hi Gilles,
>
>> Author: luc
>> Date: Sun Nov 14 15:06:11 2010
>> New Revision: 1035003
>>
>> URL: http://svn.apache.org/viewvc?rev=1035003&view=rev
>> Log:
>> fixed message building so the behavior matches the existing javadoc:
>> general
Le 14/11/2010 22:19, Luc Maisonobe a écrit :
> Le 14/11/2010 21:57, Gilles Sadowski a écrit :
>> Hi Luc.
>
> Hi Gilles,
>
>>
>>> Author: luc
>>> Date: Sun Nov 14 15:06:11 2010
>>> New Revision: 1035003
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1035003&view=rev
>>> Log:
>>> fixed message build
Hi.
> > [...]
> >
> > I'll revert the change and make the javadoc match the earlier code.
>
> It should be fixed now, in r1035072 and r1035073.
Thank you.
> I left the other change (allowing either specific or general to be null)
> as I still consider its worth providing both ways.
I don't un
Le 14/11/2010 23:22, Gilles Sadowski a écrit :
> Hi.
Hi,
>
>>> [...]
>>>
>>> I'll revert the change and make the javadoc match the earlier code.
>>
>> It should be fixed now, in r1035072 and r1035073.
>
> Thank you.
>
>> I left the other change (allowing either specific or general to be null)
Hi.
> [...]
>
> So what I propose the following set of constructors :
> - no argument
> -> this would lead to the default message USER_EXCEPTION
> - a throwable
> -> this would lead to the default message USER_EXCEPTION
> - a throwable and one pattern
> -> this would be used to
On Nov 14, 2010, at 5:09, "sebb" wrote:
> Just noticed that there are no @since markers for any of the additions
> to the code made since 1.0.
>
> I think these are important, and should be present.
>
> I'm happy to add them to the code-base.
+1. How about @author tags with ASF as the author f
"author tags are officially discouraged"
The board decided long ago that @author tags were discouraged. Let's
just remove them. If you want to credit someone, add their name to
the pom.xml file as a contributor.
On Sun, Nov 14, 2010 at 7:05 PM, Gary Gregory
wrote:
> On Nov 14, 2010, at 5:09, "
On Nov 14, 2010, at 16:28, "James Carman" wrote:
> "author tags are officially discouraged"
>
> The board decided long ago that @author tags were discouraged. Let's
> just remove them. If you want to credit someone, add their name to
> the pom.xml file as a contributor.
Yes I remember that bu
Checkstyle in VFS verifies that author tags are present as that is the default
setting. I don't see a checkstyle setting to enforce that they are not present.
However, I believe it can enforce that it match a fixed expression.
As part of cleaning up the checkstyle results I've added @author tag
On 15 November 2010 01:04, Ralph Goers wrote:
> Checkstyle in VFS verifies that author tags are present as that is the
> default setting. I don't see a checkstyle setting to enforce that they are
> not present. However, I believe it can enforce that it match a fixed
> expression.
>
> As part o
On Nov 14, 2010, at 3:43 AM, sebb wrote:
> On 14 November 2010 11:17, sebb wrote:
>> The change of VFS package name has broken lots of Gump builds - which
>> is to be expected.
>>
>> Looking at how this has been solved for other projects, one way to
>> solve this is to create a branch for the V
On Nov 14, 2010, at 17:20, "sebb" wrote:
> On 15 November 2010 01:04, Ralph Goers wrote:
>> Checkstyle in VFS verifies that author tags are present as that is the
>> default setting. I don't see a checkstyle setting to enforce that they are
>> not present. However, I believe it can enforce th
On 15 November 2010 01:23, Ralph Goers wrote:
>
> On Nov 14, 2010, at 3:43 AM, sebb wrote:
>
>> On 14 November 2010 11:17, sebb wrote:
>>> The change of VFS package name has broken lots of Gump builds - which
>>> is to be expected.
>>>
>>> Looking at how this has been solved for other projects, o
On 15 November 2010 01:32, Gary Gregory wrote:
> On Nov 14, 2010, at 17:20, "sebb" wrote:
>
>> On 15 November 2010 01:04, Ralph Goers wrote:
>>> Checkstyle in VFS verifies that author tags are present as that is the
>>> default setting. I don't see a checkstyle setting to enforce that they are
On Nov 14, 2010, at 5:34 PM, sebb wrote:
>
>
> IMO it's important to ensure that the package change really is necessary.
>
Somehow I thought that was accomplished by the last release candidate failing
to get the required votes due to the package name not being changed. If the
recommendatio
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Sunday, November 14, 2010 17:36
> To: Commons Developers List
> Subject: Re: [VFS] @since markers missing
>
> On 15 November 2010 01:32, Gary Gregory wrote:
> > On Nov 14, 2010, at 17:20, "sebb" wrote:
> >
> >> On 15 Nov
On Nov 14, 2010, at 5:41 PM, Gary Gregory wrote:
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: Sunday, November 14, 2010 17:36
>> To: Commons Developers List
>> Subject: Re: [VFS] @since markers missing
>>
>> On 15 November 2010 01:32, Gary Gregory wrote:
>>> On
On 15 November 2010 01:38, Ralph Goers wrote:
>
> On Nov 14, 2010, at 5:34 PM, sebb wrote:
>
>>
>>
>> IMO it's important to ensure that the package change really is necessary.
>>
>
> Somehow I thought that was accomplished by the last release candidate failing
> to get the required votes due to t
On Nov 14, 2010, at 5:51 PM, sebb wrote:
> On 15 November 2010 01:38, Ralph Goers wrote:
>>
>> On Nov 14, 2010, at 5:34 PM, sebb wrote:
>>
>>>
>>>
>>> IMO it's important to ensure that the package change really is necessary.
>>>
>>
>> Somehow I thought that was accomplished by the last rel
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-messenger has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-services has an issue affecting its community integration.
This is
On 15 November 2010 02:08, Ralph Goers wrote:
>
> On Nov 14, 2010, at 5:51 PM, sebb wrote:
>
>> On 15 November 2010 01:38, Ralph Goers wrote:
>>>
>>> On Nov 14, 2010, at 5:34 PM, sebb wrote:
>>>
IMO it's important to ensure that the package change really is necessary.
>>>
>>>
Starting a new thread because the original one drifted into @author tags.
I've been using clirr to report which classes and methods are new.
This works fine for classes, however Clirr does not seem to notice
when a private method becomes public - it just says the method has
been added, [even if o
On Nov 14, 2010, at 19:56, "sebb" wrote:
> Starting a new thread because the original one drifted into @author tags.
>
> I've been using clirr to report which classes and methods are new.
>
> This works fine for classes, however Clirr does not seem to notice
> when a private method becomes publ
On 15 November 2010 03:59, Gary Gregory wrote:
> On Nov 14, 2010, at 19:56, "sebb" wrote:
>
>> Starting a new thread because the original one drifted into @author tags.
>>
>> I've been using clirr to report which classes and methods are new.
>>
>> This works fine for classes, however Clirr does n
On Nov 14, 2010, at 7:43 PM, sebb wrote:
> On 15 November 2010 02:08, Ralph Goers wrote:
>>
>> On Nov 14, 2010, at 5:51 PM, sebb wrote:
>>
>>> On 15 November 2010 01:38, Ralph Goers wrote:
On Nov 14, 2010, at 5:34 PM, sebb wrote:
>
>
> IMO it's important to ensu
On Nov 14, 2010, at 8:04 PM, sebb wrote:
> On 15 November 2010 03:59, Gary Gregory wrote:
>> On Nov 14, 2010, at 19:56, "sebb" wrote:
>>
>>> Starting a new thread because the original one drifted into @author tags.
>>>
>>> I've been using clirr to report which classes and methods are new.
>>>
On Nov 14, 2010, at 20:04, "sebb" wrote:
> On 15 November 2010 03:59, Gary Gregory wrote:
>> On Nov 14, 2010, at 19:56, "sebb" wrote:
>>
>>> Starting a new thread because the original one drifted into @author tags.
>>>
>>> I've been using clirr to report which classes and methods are new.
>>>
On 15 November 2010 04:07, Ralph Goers wrote:
>
> On Nov 14, 2010, at 7:43 PM, sebb wrote:
>
>> On 15 November 2010 02:08, Ralph Goers wrote:
>>>
>>> On Nov 14, 2010, at 5:51 PM, sebb wrote:
>>>
On 15 November 2010 01:38, Ralph Goers wrote:
>
> On Nov 14, 2010, at 5:34 PM, sebb wrot
On 15 November 2010 04:16, Gary Gregory wrote:
> On Nov 14, 2010, at 20:04, "sebb" wrote:
>
>> On 15 November 2010 03:59, Gary Gregory wrote:
>>> On Nov 14, 2010, at 19:56, "sebb" wrote:
>>>
Starting a new thread because the original one drifted into @author tags.
I've been using
On Nov 14, 2010, at 20:08, "Ralph Goers" wrote:
>
> On Nov 14, 2010, at 7:43 PM, sebb wrote:
>
>> On 15 November 2010 02:08, Ralph Goers wrote:
>>>
>>> On Nov 14, 2010, at 5:51 PM, sebb wrote:
>>>
On 15 November 2010 01:38, Ralph Goers wrote:
>
> On Nov 14, 2010, at 5:34 PM, s
On Nov 14, 2010, at 20:23, "sebb" wrote:
> On 15 November 2010 04:16, Gary Gregory wrote:
>> On Nov 14, 2010, at 20:04, "sebb" wrote:
>>
>>> On 15 November 2010 03:59, Gary Gregory
>>> wrote:
On Nov 14, 2010, at 19:56, "sebb" wrote:
> Starting a new thread because the origina
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs has an issue affecting its community integration.
This issue a
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs-sandbox has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-junit has an issue affecting its community
integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-antlr has an issue affecting its community
integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-betwixt has an issue affecting its community
integrati
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-log has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-dynabean has an issue affecting its community
integrat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-email has an issue affecting its community
integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-interaction has an issue affecting its community
integ
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-swt has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-memory has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-regexp has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-sql has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-threads has an issue affecting its community
integrati
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-id has an issue affecting its community integration.
This issue af
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-util has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-beanshell has an issue affecting its community
integra
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-avalon has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-xml has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jms has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-velocity has an issue affecting its community
integrat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-quartz has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-bean has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-ant has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-define has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-fmt has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jsl has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jsl-test has an issue affecting its community
integrat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jface has an issue affecting its community
integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-swing has an issue affecting its community
integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-html has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-define-test has an issue affecting its community
integ
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jmx has an issue affecting its community integration.
T
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-xmlunit has an issue affecting its community
integrati
78 matches
Mail list logo