2015-01-20 2:13 GMT+01:00 sebb :
> On 20 January 2015 at 00:51, Phil Steitz wrote:
> > On 1/19/15 4:53 PM, sebb wrote:
> >> Building the full site for a component can be quite time-consuming,
> >> which makes checking the documentation build tedious.
> >>
> >> Almost all the reports have "skip" p
Hello Peter,
2015-01-20 1:05 GMT+01:00 Peter Ansell :
> On 20 January 2015 at 05:44, Jörg Schaible wrote:
> > Hi Gilles,
> >
> > Gilles wrote:
> >
> >> On Mon, 19 Jan 2015 10:50:52 -0700, Phil Steitz wrote:
> >>> On 1/19/15 10:33 AM, Gilles wrote:
> On Mon, 19 Jan 2015 12:15:42 -0500, Gary
I get 141 if the Fix Version is limited to 2.1
You can add
true
to the VFS pom (I recently did this for NET).
I don't know how to increase the JIRA limit or if it is possible - you
could raise an INFRA Jira.
On 19 January 2015 at 02:27, Bernd Eckenfels wrote:
> Hello,
>
> I added a commons.c
On 20 January 2015 at 00:51, Phil Steitz wrote:
> On 1/19/15 4:53 PM, sebb wrote:
>> Building the full site for a component can be quite time-consuming,
>> which makes checking the documentation build tedious.
>>
>> Almost all the reports have "skip" parameters, so it's possible to
>> build up a c
On 1/19/15 4:53 PM, sebb wrote:
> Building the full site for a component can be quite time-consuming,
> which makes checking the documentation build tedious.
>
> Almost all the reports have "skip" parameters, so it's possible to
> build up a command that only builds the component docs. This can be
On 20 January 2015 at 05:44, Jörg Schaible wrote:
> Hi Gilles,
>
> Gilles wrote:
>
>> On Mon, 19 Jan 2015 10:50:52 -0700, Phil Steitz wrote:
>>> On 1/19/15 10:33 AM, Gilles wrote:
On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
> On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz
>
Building the full site for a component can be quite time-consuming,
which makes checking the documentation build tedious.
Almost all the reports have "skip" parameters, so it's possible to
build up a command that only builds the component docs. This can be
saved as a shell script or alias. (Or def
>> There is the build system for some, for some it's the people - be it
>> just for oversight. And then there is the PMC and the board reports.
>
>
> Of course, there are some _administrative_ connections; it's very
> helpful to have a home for projects that by themselves wouldn't have
> the resour
On Mon, 19 Jan 2015 20:46:56 +, sebb wrote:
It looks as though the notifications@commons.a.o mailing list is
finally being used for:
buildbot commits
website publication
This should reduce the noise on the commits@ mailing list
considerably.
Thanks,
Gilles
[...]
-
On Mon, 19 Jan 2015 20:34:23 +0100, Torsten Curdt wrote:
...and it's still the term we are using:
http://commons.apache.org/components.html
You miss my point(s): It's totally clear what a component is,
as defined by "Commons". The issue is how it relates to the
"Commons project" management.
Thanks!
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 1/19/2015 12:46 PM, sebb wrote:
It looks as though the notifications@commons.a.o mailing list is
finally being used for:
buildbot commits
website publication
This should reduce the noise on the commits@ mailing list consider
Thanks, sebb!!
On 1/19/15 1:46 PM, sebb wrote:
> It looks as though the notifications@commons.a.o mailing list is
> finally being used for:
>
> buildbot commits
> website publication
>
> This should reduce the noise on the commits@ mailing list considerably.
>
> Website source file commit mails ar
It looks as though the notifications@commons.a.o mailing list is
finally being used for:
buildbot commits
website publication
This should reduce the noise on the commits@ mailing list considerably.
Website source file commit mails are not affected; they are sent to
commits@ as for any other sour
>> ...and it's still the term we are using:
>>
>> http://commons.apache.org/components.html
>
> You miss my point(s): It's totally clear what a component is,
> as defined by "Commons". The issue is how it relates to the
> "Commons project" management.
That does not sound like "totally clear" to me
On Mon, Jan 19, 2015 at 1:44 PM, Jörg Schaible
wrote:
> Hi Gilles,
>
> Gilles wrote:
>
> > On Mon, 19 Jan 2015 10:50:52 -0700, Phil Steitz wrote:
> >> On 1/19/15 10:33 AM, Gilles wrote:
> >>> On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
> On Mon, Jan 19, 2015 at 11:40 AM, Phil Ste
On 1/19/15 11:21 AM, Gilles wrote:
> On Mon, 19 Jan 2015 18:53:35 +0100, Torsten Curdt wrote:
>>> Words without semantics...
>>
>> ...and it's still the term we are using:
>>
>> http://commons.apache.org/components.html
>
> You miss my point(s): It's totally clear what a component is,
> as defined
Hi Gilles,
Gilles wrote:
> On Mon, 19 Jan 2015 10:50:52 -0700, Phil Steitz wrote:
>> On 1/19/15 10:33 AM, Gilles wrote:
>>> On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz
wrote:
> On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
On Mon, Jan 19, 2015 at 1:43 PM, Gary Gregory
wrote:
> I wonder how Apache DS deals with this. It's a TLP with lots of jars too.
>
Or Maven and Ant... I can't imagine there is a special ML for one 'special'
jar.
Gary
>
> Gary
>
> On Mon, Jan 19, 2015 at 1:21 PM, Gilles
> wrote:
>
>> On Mon,
I wonder how Apache DS deals with this. It's a TLP with lots of jars too.
Gary
On Mon, Jan 19, 2015 at 1:21 PM, Gilles
wrote:
> On Mon, 19 Jan 2015 18:53:35 +0100, Torsten Curdt wrote:
>
>> Words without semantics...
>>>
>>
>> ...and it's still the term we are using:
>>
>> http://commons.apache
On 19 January 2015 at 11:28, Benedikt Ritter wrote:
> Hi Bernd
>
> 2015-01-18 18:49 GMT+01:00 Bernd Eckenfels :
>
>> Hello Ben,
>>
>> I was actually looking for this switch before. After releasing VFS
>> there would be a few hundred closed bugs, so it comes in handy.
>>
>> However I dont see a bul
On Mon, 19 Jan 2015 18:53:35 +0100, Torsten Curdt wrote:
Words without semantics...
...and it's still the term we are using:
http://commons.apache.org/components.html
You miss my point(s): It's totally clear what a component is,
as defined by "Commons". The issue is how it relates to the
"Co
On Mon, 19 Jan 2015 10:50:52 -0700, Phil Steitz wrote:
On 1/19/15 10:33 AM, Gilles wrote:
On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz
wrote:
On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
> Le 19/01/2015 15:32, Benedikt Ritter a écrit :
>
> Words without semantics...
...and it's still the term we are using:
http://commons.apache.org/components.html
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apach
On 1/19/15 10:33 AM, Gilles wrote:
> On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
>> On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz
>> wrote:
>>
>>> On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
>>> > Le 19/01/2015 15:32, Benedikt Ritter a écrit :
>>> >
>>> >> Now the question is: do we want
On Mon, 19 Jan 2015 12:15:42 -0500, Gary Gregory wrote:
On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz
wrote:
On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
> Le 19/01/2015 15:32, Benedikt Ritter a écrit :
>
>> Now the question is: do we want to make an exception for the
Commons RDF
>> project?
>
On Mon, Jan 19, 2015 at 11:40 AM, Phil Steitz wrote:
> On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
> > Le 19/01/2015 15:32, Benedikt Ritter a écrit :
> >
> >> Now the question is: do we want to make an exception for the Commons RDF
> >> project?
> > I don't think we should make an exception. Settin
On Mon, 19 Jan 2015 09:40:54 -0700, Phil Steitz wrote:
On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
Le 19/01/2015 15:32, Benedikt Ritter a écrit :
Now the question is: do we want to make an exception for the
Commons RDF
project?
I don't think we should make an exception. Setting up mail filters
On 1/19/15 7:51 AM, Emmanuel Bourg wrote:
> Le 19/01/2015 15:32, Benedikt Ritter a écrit :
>
>> Now the question is: do we want to make an exception for the Commons RDF
>> project?
> I don't think we should make an exception. Setting up mail filters isn't
> that difficult.
+1
We don't have "subpr
On 17/01/15 12:00, Bruno P. Kinoshita wrote:
Hi Andy!
Jena can (and does) support multiple APIs over a common core.
A commons-rdf API can be added along side the existing APIs; that means
it is not a "big bang" to have commons-rdf interfaces supported.
That's great! Would the commons-rdf dep
Le 19/01/2015 15:52, Andy Seaborne a écrit :
> It might work to seek tags like "apache/commons/rdf" but I feel that
> asking people to get sophisticated (specialised) for one particular
> community (we are all in many communities) is yet another barrier.
The commit mails for the Git repositories
On 18/01/15 12:07, Benedikt Ritter wrote:
...
To sum this up: All that is blocking github commons rdf to join Apache
Commons is the mailing list thing?
>
> Regards,
> Benedikt
Some thinking out loud ... in email ...
There are two mailing lists issues : "dev" and "commits".
"commits" has some
Le 19/01/2015 15:32, Benedikt Ritter a écrit :
> Now the question is: do we want to make an exception for the Commons RDF
> project?
I don't think we should make an exception. Setting up mail filters isn't
that difficult.
Emmanuel Bourg
-
Hi all,
following up the discussion at [1] the folks from git github commons RDF
project [2] would like to join the Apache Commons Project, but they ask us
to create a separate mailing list for this component. Gilles has already
brought up this topic [3] and my feeling is, that we in general don't
On 18 January 2015 at 12:07, Benedikt Ritter wrote:
> There is a infra hook that can forward any comments on github issues to
> jira issues. I think this would be sufficient. Github mirrors are read
> only, so you will have to live with the manual merge approach...
Agreed - the infra-hook from gi
Hello.
Some time ago, we had a discussion about the "fluent API"
paradigm:
http://markmail.org/message/3fjvucyz7rax4cyi
The excerpt of the conversation below is typical of the antagonism
between proponents of the evolution of the library and proponents
of stability.
In particular, when most p
Hi Bernd
2015-01-18 18:49 GMT+01:00 Bernd Eckenfels :
> Hello Ben,
>
> I was actually looking for this switch before. After releasing VFS
> there would be a few hundred closed bugs, so it comes in handy.
>
> However I dont see a bulk operation interface. It is supposed to be
> under "Tools" and r
36 matches
Mail list logo
