View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-serialization-testsuite?log=log20060504015916Lbuild.1
BUILD COMPLETE-build.1Date of build:05/04/2006 01:59:16Time to build:16 minutes 32 secondsLast changed:05/03/2006 17:50:15Last log entry:Added
Remoting
Serialization
Microcontainer
Jbossxb
Cache
(And JBossWS until recentrly)
All of the above have a snapshot release for development purposes, so
is this what Kabir needs?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Kabir Khan
Sent: 04
OK, so are you saying you would like what goes into
deploy/jboss-aop/deployer and deploy/jboss-aop-jdk50.deployer to go into the
repository as a zip file? I am training this week, but should be able to
make it happen in the next day or two.
-Original Message-
From: [EMAIL PROTECTED]
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060504021616
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:05/04/2006 02:16:16Time to build:Last changed:12/31/2005 20:37:24Last log entry:JBREM-272:Added tests for (clientPool
This is the current jboss project dependencies on JBoss 4.0.4.GA
componentref name=jboss/aop version=1.5.0-snapshot/
componentref name=jboss/backport-concurrent version=2.1.0.GA/
componentref name=jboss/cache version=1.2.4.SP2/
componentref name=jboss/microcontainer version=1.0.2/
componentref
Dimitris Andreadis wrote:
- JBossAS/WebServices are still on JBossXB snapshot which is actually
jbossxb 1.0.0.CR4. Can we safely update both, since 1.0.0.CR4 is the
version that will be used, or Alexey wants to make this 1.0.0.GA ?
Update jbossxb to a non-snapshot release
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060504051919
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:05/04/2006 05:19:19Time to build:Last changed:05/04/2006 02:22:51Last log entry:JBREM-431 - added ability for
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060504071929
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:175: The following error occurred while executing this line:
The tar dist was dropped because of complaints about all the old posix
tar implementations which could not handle the long file names that are
required for unpacked deployments containing classes.
The existence of dos crs should not be a function of the distribution
type. All the .sh files should
What do those releases have to do with aop? What I need is all of the
artifacts needed to incorporate a component into the jbossas release
install in the repository. Specifically the javaee5/java5 based
artifacts that can't be bundled with the jboss-4.0.x j2ee1.4 build.
-Original
I need all of the deployer artifacts and client jars in the aop binary
in the repository. This is what I'm currently testing:
[EMAIL PROTECTED] thirdparty]$ ls jboss/aop/lib/
common-softvaluehashmap.jar* jboss-aspect-jdk50-client.jar*
jboss-aop-jdk50-client.jar*
Nothing to do with aop. I am just wondering about the usefulness of a
X.Y.ZZ.SNAPSHOT release, since, from what I've seen from the listed
projects that just export a snapshot release for development purposes,
there will rarely be a need for releasing snapshots from multiple
branches, except the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060504080146
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line:
jbossretro should be 1.0.0.GA as there is no change relative to CR1
other than fixing the jar packaging.
-Original Message-
From: Dimitris Andreadis
Sent: Thursday, May 04, 2006 3:24 AM
To: Scott M Stark; Adrian Brock; Kabir Khan;
'[EMAIL PROTECTED]'; Thomas Diesler; Tom Elrod;
Its true about the comparision, but other than snapshot binaries, there
should be no component that is declared to be compatible with a snapshot
release in the public repository as this makes no sense. Use of
snapshots is a developer to developer exchange that requires a local
override. We need to
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060504090818
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
The only reason for snapshots is so one developer doesn't have to
wait for an official release of another project before
doing some work.
It is not intended that it gets released with an untagged
dependency.
Can't we add some validation that says a release
(including alpha, beta, CR)
is not
Yes,
http://jira.jboss.com/jira/browse/JBBUILD-316
Can't we add some validation that says a release (including
alpha, beta, CR) is not allowed to depend on snapshots?
---
Using Tomcat but need to do more? Need to support web services,
- JBossRemoting, (a) the version number shouldn't be 1.4.2.GA ??.
Second, I don't see any dependency in its component-info.xml on
JBossRemoting ?
Don't understand what you mean by the second point.
---
Using Tomcat but need to do more?
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060504102134Lbuild.1714
BUILD COMPLETE-build.1714Date of build:05/04/2006 10:21:34Time to build:31 minutes 20 secondsLast changed:05/04/2006 10:08:45Last log entry:The
Maybe Dimitris meant JBossRemoting should have a dependency on
JBossSerialization 1.0.0.GA declared
-Original Message-
From: Tom Elrod
Sent: Thursday, May 04, 2006 9:34 AM
To: Dimitris Andreadis
Cc: Scott M Stark; Adrian Brock; Kabir Khan; Alexey Loubyansky; Thomas
Diesler; Tom Elrod;
- JBossRemoting, (a) the version number shouldn't be 1.4.2.GA ??.
Second, I don't see any dependency in its component-info.xml on
JBossRemoting ?
Don't understand what you mean by the second point.
Hi Tom,
If remoting is using JBossSerialization, shouldn't the dependency be
Remoting changed to be 1.4.2.GA (as well as ws references)
Dimitris Andreadis wrote:
This is the current jboss project dependencies on JBoss 4.0.4.GA
componentref name=jboss/aop version=1.5.0-snapshot/
componentref name=jboss/backport-concurrent version=2.1.0.GA/
componentref name=jboss/cache
Anyone know why I seem to be losing the .svn/tmp dir in my eclipse
projects? The last thing I did was to delete and readd this project to
change its from from java to simple. I am running TortoiseSVN so maybe
that is interacting badly in some way.
propset svn:ignore
bin
output
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060504124824
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
Can I change the type of a project in eclipse? I currently have a simple
project that should be a java project. I don't see how to change this.
Scott Stark
VP Architecture Technology
JBoss Inc.
Well, if using jboss serialization, there is a dependency. However,
this is not the default (java serialization is). So should I include it
if there *may* be a dependency on it?
Clebert Suconic wrote:
Maybe Dimitris meant JBossRemoting should have a dependency on
JBossSerialization 1.0.0.GA
I think it should be declared, even if not configured by default, so a
possible version conflict with other components using a different
version of JBossSerialization can be detected.
-Original Message-
From: Tom Elrod
Sent: 04 May, 2006 21:39
To: Clebert Suconic
Cc: Tom Elrod;
No.
Best way I know:
Delete project in eclipse (without deleting the resources - eclipse will
ask you)
Remove the .project file
Create new java project and point the existing location.
/max
Can I change the type of a project in eclipse? I currently have a simple
project that should be
Ok. Have changed to following now:
project name=jboss/remoting-component-info
!-- --
!-- JBOSS REMOTING --
!-- --
On Thu, May 04, 2006 at 01:16:45PM -0500, Scott M Stark wrote:
Can I change the type of a project in eclipse? I currently have a simple
project that should be a java project. I don't see how to change this.
Edit the .project file by hand adding the necessary things for
a java project:
that is also an option ;)
/max
On Thu, May 04, 2006 at 01:16:45PM -0500, Scott M Stark wrote:
Can I change the type of a project in eclipse? I currently have a simple
project that should be a java project. I don't see how to change this.
Edit the .project file by hand adding the necessary
I have locally changed server/build.xml to include the 15 classes needed
from remoting into the jboss-minimal.jar. However, is going to still
need jboss serialization classes (see below). Should
jboss-serialization.jar be added to minimal lib directory?
14:14:29,494 INFO [NamingService]
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060504153703
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
I added the following files to the repostitory under
jboss/aop/1.5.0-snapshot/lib
jboss-aop-jdk50.deployer
jboss-aop.deployer
jboss-aspect-jdk50-client.jar
and added these files to the component-info.xml.
I've touched my local build/build-thirdparty.xml, deleted my
Kabir,
Take a look at the file /tools/etc/jbossbuild/tasks.xml
Grep it for the word deployer. Basically, we associate file types with
an output type. This mapping is used to determine where it looks for
things in the repository. In the current version of this file the
outputtype for deployer
Is JBossSerialization actually, or this is just the API, in which case
you can just bundle the missing classes?
JBossSerialization is about 121Kb, and jboss-minimal 190kb.
-Original Message-
From: Tom Elrod
Sent: 04 May, 2006 22:48
To: Dimitris Andreadis
Cc: Scott M Stark; Clebert
I meant actually used by remoting in this setup, sorry.
-Original Message-
From: Dimitris Andreadis
Sent: 04 May, 2006 23:34
To: Tom Elrod
Cc: Scott M Stark; Clebert Suconic; QA;
jboss-development@lists.sourceforge.net
Subject: RE: Problem with minimal config in Branch_4_0
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060504162821Lbuild.1715
BUILD COMPLETE-build.1715Date of build:05/04/2006 16:28:21Time to build:30 minutes 8 secondsLast changed:05/04/2006 16:11:16Last log entry:Enable
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060504173951
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
It's the problem with aop:
synchronize.jboss/aop.common-softvaluehashmap.jar:
[get] Getting:
http://repository.jboss.com/jboss/aop/1.5.0-snapshot/lib/common-softvaluehashmap.jar
[get] To:
/services/cruisecontrol/checkout/jboss-4.0.x/thirdparty/jboss/aop/lib/common-softvaluehashmap.jar
I'm fixing it as per Ruel's suggestion. The thirdparty
refreshes ok here now, and am doing a build. I should hopefully get this
commited in the next 30 mins
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dimitris AndreadisSent: 04 May 2006 23:00To:
Ive committed in the fix.
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kabir Khan
Sent: Thursday, May 04, 2006 5:08
PM
To:
Updating tasks.xml to use lib gives me the following error.
compile-classes:
[mkdir] Created dir:
C:\cygwin\home\Kabir\cvs\jboss-4.0\console\output\classes
[javac] Compiling 97 source files to
C:\cygwin\home\Kabir\cvs\jboss-4.0\console\output\classes
error: error reading
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060504183258Lbuild.1058
BUILD COMPLETE-build.1058Date of build:05/04/2006 18:32:58Time to build:28 minutes 13 secondsLast changed:05/04/2006 18:15:24Last log entry:fix output type
I added the .deployer files to jboss/aop/1.5.0-snapshot/bin, and put
tasks.xml back to the way it was, i.e.
artifacttype type=deployer outputtype=lib/
This works here
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Kabir Khan
Sent: 04 May 2006
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060504235143
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:53: Exit code: 1 See compile.log in Build Artifacts for details.Date of
Scott M Stark wrote:
The tar dist was dropped because of complaints about all the old posix
tar implementations which could not handle the long file names that are
required for unpacked deployments containing classes.
OK.
Not sure who created the .zip distro, but I would suggest that
next
48 matches
Mail list logo
