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
On 12/10/12 5:10 PM, Ralph Goers wrote:
> On Dec 10, 2012, at 4:12 PM, sebb wrote:
>
>> On 10 December 2012 21:53, Phil Steitz wrote:
>>> On 12/10/12 1:27 PM, Ralph Goers wrote:
Yes, I think you are missing something fundamental.
If you check in "the whole mess" you will never again
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-dbutils has an issue affecting its community integration.
This iss
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
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-chain2 has an issue affecting its community integration.
This issu
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-digester3 has an issue affecting its community integration.
This i
I downloaded the tag and ran "mvn clean site" and got 4 test failures:
Tests run: 14, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.902 sec
<<< FAILURE!
testEmbedUrl(org.apache.commons.mail.HtmlEmailTest) Time elapsed: 4505
sec <<< FAILURE!
junit.framework.AssertionFailedError: Should have
On the same page under "Development", is all this info up to date?
Gary
On Mon, Dec 10, 2012 at 9:53 PM, Gary Gregory wrote:
> This page is wrong:
>
> https://people.apache.org/builds/commons/email/1.3/RC4/building.html
>
> "You must be using JDK 1.4 or higher to successfully complete this targe
This page is wrong:
https://people.apache.org/builds/commons/email/1.3/RC4/building.html
"You must be using JDK 1.4 or higher to successfully complete this target."
The text should read "JDK 5".
Gary
On Mon, Dec 10, 2012 at 5:28 PM, Thomas Neidhart
wrote:
> Hi,
>
> I would like to call a vot
On Mon, Dec 10, 2012 at 9:10 PM, sebb wrote:
> On 11 December 2012 01:07, Gary Gregory wrote:
> > On Mon, Dec 10, 2012 at 5:28 PM, Thomas Neidhart
> > wrote:
> >
> >> Hi,
> >>
> >> I would like to call a vote from commons-email-1.3 based on RC4.
> >>
> >> The files:
> >>
> >> The artifacts are d
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-exec-test has an issue affecting its community integration.
This i
On 11 December 2012 01:07, Gary Gregory wrote:
> On Mon, Dec 10, 2012 at 5:28 PM, Thomas Neidhart
> wrote:
>
>> Hi,
>>
>> I would like to call a vote from commons-email-1.3 based on RC4.
>>
>> The files:
>>
>> The artifacts are deployed to Nexus:
>> https://repository.apache.org/content/repositori
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-dbcp2 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-dbcp has an issue affecting its community integration.
This issue
On Dec 10, 2012, at 4:12 PM, sebb wrote:
> On 10 December 2012 21:53, Phil Steitz wrote:
>> On 12/10/12 1:27 PM, Ralph Goers wrote:
>>> Yes, I think you are missing something fundamental.
>>>
>>> If you check in "the whole mess" you will never again be able to properly
>>> build a sub-project'
On Mon, Dec 10, 2012 at 5:28 PM, Thomas Neidhart
wrote:
> Hi,
>
> I would like to call a vote from commons-email-1.3 based on RC4.
>
> The files:
>
> The artifacts are deployed to Nexus:
> https://repository.apache.org/content/repositories/orgapachecommons-135/
>
> The tag:
> http://svn.apache.org
On 10 December 2012 22:28, Thomas Neidhart wrote:
> Hi,
>
> I would like to call a vote from commons-email-1.3 based on RC4.
>
> The files:
>
> The artifacts are deployed to Nexus:
> https://repository.apache.org/content/repositories/orgapachecommons-135/
>
> The tag:
> http://svn.apache.org/viewv
On 10 December 2012 21:53, Phil Steitz wrote:
> On 12/10/12 1:27 PM, Ralph Goers wrote:
>> Yes, I think you are missing something fundamental.
>>
>> If you check in "the whole mess" you will never again be able to properly
>> build a sub-project's site with Maven. This is because the process of
Hi,
I would like to call a vote from commons-email-1.3 based on RC4.
The files:
The artifacts are deployed to Nexus:
https://repository.apache.org/content/repositories/orgapachecommons-135/
The tag:
http://svn.apache.org/viewvc/commons/proper/email/tags/EMAIL_1_3_RC4/
The site:
http://people.a
On 12/10/12 1:27 PM, Ralph Goers wrote:
> Yes, I think you are missing something fundamental.
>
> If you check in "the whole mess" you will never again be able to properly
> build a sub-project's site with Maven. This is because the process of
> updating the site would require first doing a diff
Ralph,
Thanks for your response, and sorry if I'm still being dense, but let's
just use the [lang] component as an example. Why can't I, at any point,
generate the component's site locally, then surgically modify svn so that
lang/ from the content root now contains the generated content? Where
Yes, I think you are missing something fundamental.
If you check in "the whole mess" you will never again be able to properly build
a sub-project's site with Maven. This is because the process of updating the
site would require first doing a diff and then deleting items that are not
included i
I don't think there's much percentage in moving to the CMS with a structure
like that of Commons. That said, checking in the whole mess, as Phil
suggests, seems perfectly doable and should not preclude updating parts of
the tree in quite a similar fashion as how updating a given component's
site i
On 12/10/12 11:40 AM, Phil Steitz wrote:
> On 12/10/12 10:50 AM, Ralph Goers wrote:
>> All the sub-sites are hooked off the main site. I would have no idea how to
>> migrate anything without migrating the main site first.
> Having now looked at [1], it looks to me like we can solve the
> immediat
On Mon, Dec 10, 2012 at 8:40 PM, Phil Steitz wrote:
> On 12/10/12 10:50 AM, Ralph Goers wrote:
>> All the sub-sites are hooked off the main site. I would have no idea how to
>> migrate anything without migrating the main site first.
>
> Having now looked at [1], it looks to me like we can solve
On 12/10/12 10:50 AM, Ralph Goers wrote:
> All the sub-sites are hooked off the main site. I would have no idea how to
> migrate anything without migrating the main site first.
Having now looked at [1], it looks to me like we can solve the
immediate problem using svn pub-sub. The docs are not c
On Mon, Dec 10, 2012 at 7:50 PM, Ralph Goers wrote:
> All the sub-sites are hooked off the main site. I would have no idea how to
> migrate anything without migrating the main site first.
>
> I suppose it is possible to point to the sub-sites in their current location
> but in logging we found
They should all be built w/ Maven AFAIK.
Matt
On Mon, Dec 10, 2012 at 12:50 PM, Ralph Goers wrote:
> All the sub-sites are hooked off the main site. I would have no idea how
> to migrate anything without migrating the main site first.
>
> I suppose it is possible to point to the sub-sites in t
All the sub-sites are hooked off the main site. I would have no idea how to
migrate anything without migrating the main site first.
I suppose it is possible to point to the sub-sites in their current location
but in logging we found it more beneficial to simply copy the content under the
main
On 12/10/12 7:55 AM, Ralph Goers wrote:
> That is what we did in logging. Changing it at the end is fairly easy.
> However, we don't have much time for testing.
Do we really have to do it all at once?
IIUC (which is quite possibly false), the intent here is to get
everyone onto svn pub-sub and
That is what we did in logging. Changing it at the end is fairly easy.
However, we don't have much time for testing.
Ralph
On Dec 10, 2012, at 4:34 AM, Christian Grobmeier wrote:
> On Mon, Dec 10, 2012 at 1:32 PM, Gary Gregory wrote:
>> Well, we have to start somewhere. This is going to be a
Hm... or publish to SVN until we have it all and then switch, until then
the site will be static.
G
On Mon, Dec 10, 2012 at 7:34 AM, Christian Grobmeier wrote:
> On Mon, Dec 10, 2012 at 1:32 PM, Gary Gregory
> wrote:
> > Well, we have to start somewhere. This is going to be a lot of work,
> >
On Mon, Dec 10, 2012 at 1:32 PM, Gary Gregory wrote:
> Well, we have to start somewhere. This is going to be a lot of work,
> we have many components, unless you see a short cut.
I thought we would create: commons-test.apache.org
move all components to there and then make a switch from
commons.ap
Well, we have to start somewhere. This is going to be a lot of work,
we have many components, unless you see a short cut.
Gary
On Dec 10, 2012, at 7:13, Christian Grobmeier wrote:
> On Mon, Dec 10, 2012 at 1:07 PM, Gary Gregory wrote:
>> Bah, let's pick one component and start there and skip a
On Mon, Dec 10, 2012 at 1:07 PM, Gary Gregory wrote:
> Bah, let's pick one component and start there and skip a test site.
But then there is only one component visible under the new commons.a.o?
> Gary
>
> On Dec 10, 2012, at 3:08, Christian Grobmeier wrote:
>
>> starting from 1. January. Just
Bah, let's pick one component and start there and skip a test site.
Gary
On Dec 10, 2012, at 3:08, Christian Grobmeier wrote:
> starting from 1. January. Just saw a final reminder from Infra.
>
> Commons is surely a LOT of work.
>
> I would like to suggest we act immediately.
>
> In other terms
On Mon, Dec 10, 2012 at 09:07:32AM +0100, Christian Grobmeier wrote:
> starting from 1. January. Just saw a final reminder from Infra.
>
> Commons is surely a LOT of work.
>
> I would like to suggest we act immediately.
>
> In other terms: let us request a commons-test cms where we can try thing
starting from 1. January. Just saw a final reminder from Infra.
Commons is surely a LOT of work.
I would like to suggest we act immediately.
In other terms: let us request a commons-test cms where we can try things
out and prepare the new sites.
As Ralph Goers has already mentioned, we have a s
38 matches
Mail list logo
