Ok, thanks. Comment added.
On Fri, 2006-03-17 at 03:59 -0600, Dimitris Andreadis wrote:
> http://jira.jboss.com/jira/browse/JBAS-2955
>
> If Franscisco wants to add any comments on the upgrade.
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On
> > B
It uses one gigantic RCS file with markers to distinguish the versions.
So if you have 10 updates to a 100 meg file, you get a gig file. So
don't ever store iso files in CVS :)
-Jason
> -Original Message-
> From: Dimitris Andreadis
> Sent: Saturday, March 18, 2006 2:59 AM
> To: Jason T.
Just ran into a new
behavior in the tomcat 5.5.16 regarding jsp errors that is pretty nice. Either a
compile or exception shows a line number delimited fragment of the jsp page that
caused the problem. For example:
org.apache.jasper.JasperException: Exception in JSP:
/jmx-test.jsp:31
28:
Ok, then leave .zip (+installer .jar) for the binary distro, and .zip and
.tar.gz for the sources.
This is %50 a reduction and they can't get it wrong (i.e. no .tar.gz binary
distro)
I'd be also tempted to remove the .zip sources just to know what a user has
downloaded by only looking at the
I've updated crusiecontrol to run the 4.0 testsuite every 4 hours.
-Original Message-
From: Dimitris Andreadis
Sent: Saturday, March 18, 2006 12:15 PM
To: 'jboss-development@lists.sourceforge.net'; QA
Cc: Scott M Stark; Ivelin Ivanov; Thomas Diesler; Ryan Campbell
Subject: 4.0.4.CR2 remai
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hi
de&sorter/order=DESC&sorter/field=priority&resolutionIds=-1&pid=10030&fi
xfor=12310573
The major things left are (a) use jbossretro for jbossws (b) the
installer (c) resolve existing testcases and any other failing tests
tha
The lack of correlation between a unit test in the jbossas/testsuite and
its associated deployment artifacts is rather severe. To pull together
everything in a given unit test currently requires:
1. Find the deployment artifacts in the test class
2. Look in testsuite/imports/sections/{org.jboss.te
I didn't realize they were versioned together, but this makes sense.
So the question is, is webservices ready for a 1.0.0.CR4?
I have tested webservices snapshot code with jboss-4.0/testsuite (weaved
with jbossretro and retrotranslator) and got the following error:
Suite: org.jboss.test
Ok, so I will perform the Javassist 3.2.0.CR1 release and will include
the change comments from Adrian's commits in the Readme.html unless he
sends me something different.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JavassistReleaseGuide
-Original Message-
From: Shigeru Chiba [mailto:[EMAIL
The check on the two AccessControlContexts in
ExecutorsTest.testPrivilegedThreadFactory is flawed because in order for the
ACCs to be equal, they have to have the same protection domains. This is false
because of how we have the unit test classes seperated from the core concurrent
classes. T
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060318090354Lbuild.1573
BUILD COMPLETE - build.1573Date of build: 03/18/2006 09:03:54Time to build: 24 minutes 51 secondsLast changed: 03/18/2006 06:56:16Last log entry: fix sampl
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060318085002
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line: /services/cruisecontrol/work
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060318084521
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:132: The following error occurred while executing this line: /services/cruisecontrol/wor
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060318060535
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060318054434
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060318050945
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
Jason, for every binary file, does it make a new physical file, or is it
one big file with some sort of marking to distinguish the entries? CVS
is really bad with binaries, more so big ones...
> -Original Message-
> From: Jason T. Greene
> Sent: 18 March, 2006 08:16
> To: jboss-developme
17 matches
Mail list logo
