Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=320304&projectId=155
Build statistics:
State: Failed
Previous State: Failed
Started at: Sat 10 Apr 2010 18:05:03 -0700
Finished at: Sat 10 Apr 2010 18:08:32 -0700
Total time: 3m 28s
Build Trigger: Schedule
+1
On 2010-04-10 17:16, sebb wrote:
> 22 commons-proper projects are still using non-standard source and
> test directories, i.e. they are using:
>
> src/java
> src/test
>
> rather than the default:
>
> src/main/java
> src/test/java
>
> Do we want to fix those?
>
> This would
> /me Puts on Tomcat hat
>
> Don't worry about us. We work with specific versions and can handle any
> changes when we next to an upgrade.
See? :)
Thanks, Mark
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For addi
>>> I think tomcat may still build repackaged versions of dbcp and pool
>>> classes from source and this change might break their builds. So -1
>>> for now for changing those.
>>
>> As much as I am for cross-project collaboration this reason for a "-1"
>> takes it a step too far IMO. If they reall
On 10/04/2010 17:33, Torsten Curdt wrote:
I think tomcat may still build repackaged versions of dbcp and pool
classes from source and this change might break their builds. So -1
for now for changing those.
As much as I am for cross-project collaboration this reason for a "-1"
takes it a step t
Torsten Curdt wrote:
>> I think tomcat may still build repackaged versions of dbcp and pool
>> classes from source and this change might break their builds. So -1
>> for now for changing those.
>
> As much as I am for cross-project collaboration this reason for a "-1"
> takes it a step too far IM
+1, I am all for it. I've never liked the lack of symmetry.
Gary Gregory
Senior Software Engineer
Seagull Software
email: ggreg...@seagullsoftware.com
email: ggreg...@apache.org
www.seagullsoftware.com
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Saturday, April 1
> I think tomcat may still build repackaged versions of dbcp and pool
> classes from source and this change might break their builds. So -1
> for now for changing those.
As much as I am for cross-project collaboration this reason for a "-1"
takes it a step too far IMO. If they really want to keep
configuration has been changed in the experimental branch. I wouldn't bother
with trunk.
Ralph
On Apr 10, 2010, at 8:16 AM, sebb wrote:
> 22 commons-proper projects are still using non-standard source and
> test directories, i.e. they are using:
>
>src/java
>src/test
>
> rather than t
sebb wrote:
> 22 commons-proper projects are still using non-standard source and
> test directories, i.e. they are using:
>
> src/java
> src/test
>
> rather than the default:
>
> src/main/java
> src/test/java
>
> Do we want to fix those?
>
> This would involve renaming the dire
22 commons-proper projects are still using non-standard source and
test directories, i.e. they are using:
src/java
src/test
rather than the default:
src/main/java
src/test/java
Do we want to fix those?
This would involve renaming the directories, removing the entries from
the p
11 matches
Mail list logo
