[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.resource.RARDeployer -- RARDeployerMBean qualified to RARDeployerMBean
org.jboss.resource.adapter.jms.JmsConnectionFactory -- TopicConnectionFactory
qualified to TopicConnectionFactory
org.jboss.resource.adapter.jms.JmsConnectionFactory -- QueueConnectionFactory
qualified to QueueConnectionFactory
org.jboss.resource.adapter.jms.JmsSessionFactory -- Connection qualified to Connection
org.jboss.resource.adapter.jms.JmsSessionFactory -- TopicConnection qualified to
TopicConnection
org.jboss.resource.adapter.jms.JmsSessionFactory -- QueueConnection qualified to
QueueConnection
org.jboss.resource.connectionmanager.BaseConnectionManager2 --
BaseConnectionManager2MBean qualified to BaseConnectionManager2MBean
org.jboss.resource.connectionmanager.CachedConnectionManager --
CachedConnectionManagerMBean qualified to CachedConnectionManagerMBean
org.jboss.resource.connectionmanager.JBossManagedConnectionPool --
JBossManagedConnectionPoolMBean qualified to JBossManagedConnectionPoolMBean
org.jboss.resource.connectionmanager.LocalTxConnectionManager --
LocalTxConnectionManagerMBean qualified to LocalTxConnectionManagerMBean
org.jboss.resource.connectionmanager.TxConnectionManager -- TxConnectionManagerMBean
qualified to TxConnectionManagerMBean
org.jboss.resource.connectionmanager.NoTxConnectionManager --
BaseConnectionEventListener qualified to BaseConnectionEventListener
org.jboss.resource.connectionmanager.XATxConnectionManager --
XATxConnectionManagerMBean qualified to XATxConnectionManagerMBean
org.jboss.resource.endpoint.JBossMessageEndpointFactory --
JBossMessageEndpointFactoryMBean qualified to JBossMessageEndpointFactoryMBean
org.jboss.resource.work.BaseWorkManager -- BaseWorkManagerMBean qualified to
BaseWorkManagerMBean
compile-source-jdbc3:
[echo] jdbc3
[copy] Copying 5 files to
/home/jboss/jbossci/jboss-head/connector/output/gen/classes
compile-classes:
[mkdir] Created dir: /home/jboss/jbossci/jboss-head/connector/output/classes
[javac] Compiling 65 source files to
/home/jboss/jbossci/jboss-head/connector/output/classes
/home/jboss/jbossci/jboss-head/connector/src/main/org/jboss/resource/endpoint/JBossMessageEndpointFactory.java:132:
cannot resolve symbol
symbol : variable TX_REQUIRED
location: class org.jboss.metadata.MetaData
if (bmd.getMethodTransactionType(onMessage, new Class[] {Message.class},
InvocationType.LOCAL) == MetaData.TX_REQUIRED);
^
/home/jboss/jbossci/jboss-head/connector/output/gen/classes/org/jboss/resource/adapter/jdbc/WrappedPreparedStatement.java:524:
warning: setUnicodeStream(int,java.io.InputStream,int) in java.sql.PreparedStatement
has been deprecated
public void setUnicodeStream(int parameterIndex, InputStream stream, int length)
throws SQLException
^
/home/jboss/jbossci/jboss-head/connector/output/gen/classes/org/jboss/resource/adapter/jdbc/WrappedPreparedStatement.java:529:
warning: setUnicodeStream(int,java.io.InputStream,int) in java.sql.PreparedStatement
has been deprecated
ps.setUnicodeStream(parameterIndex, stream, length);
^
/home/jboss/jbossci/jboss-head/connector/output/gen/classes/org/jboss/resource/adapter/jdbc/WrappedCallableStatement.java:976:
warning: getBigDecimal(int,int) in java.sql.CallableStatement has been deprecated
public BigDecimal getBigDecimal(int parameterIndex, int scale) throws SQLException
^
/home/jboss/jbossci/jboss-head/connector/output/gen/classes/org/jboss/resource/adapter/jdbc/WrappedCallableStatement.java:66:
warning: setUnicodeStream(int,java.io.InputStream,int) in java.sql.PreparedStatement
has been deprecated
public class WrappedCallableStatement
^
/home/jboss/jbossci/jboss-head/connector/output/gen/classes/org/jboss/resource/adapter/jdbc/WrappedCallableStatement.java:980:
warning: getBigDecimal(int,int) in java.sql.CallableStatement has been deprecated
return cs.getBigDecimal(parameterIndex, scale);
^
1 error
5 warnings
BUILD FAILED
file:/home/jboss/jbossci/jboss-head/connector/build.xml:196: Compile failed; see the
compiler error output for details.
Total time: 2 minutes 17 seconds
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
[JBoss-dev] [ jboss-Bugs-680951 ] generated files should be in workspace
Bugs item #680951, was opened at 2003-02-05 16:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=680951group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Xavier Poinsard (xpoinsard) Assigned to: Nobody/Anonymous (nobody) Summary: generated files should be in workspace Initial Comment: I mentionned the problem in the forum : http://www.jboss.org/forums/thread.jsp?forum=162thread=27744 In short, the jboss-ide plugin is generating files when preferences are changed. Since those files are user-related, they should go in the workspace. Lots of plugin have files in workspace/.metadata/.plugins/ They shouldn't go in eclipse/plugin directory. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=680951group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-680956 ] TxCapsule.doBeforeCompletion: exception swallowed
Bugs item #680956, was opened at 2003-02-05 16:04
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=680956group_id=22866
Category: JBossTX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Jakob Spies (jspies)
Assigned to: Nobody/Anonymous (nobody)
Summary: TxCapsule.doBeforeCompletion: exception swallowed
Initial Comment:
OS: Mac OS X 10.2.3
JDK 1.3.1
The method org.jboss.tm.TxCapsule.doBeforeCompletion in
JBoss 3.0.4 contains the following code:
try
{
if (trace)
{
log.trace(calling sync + i + ,
+ sync[i]);
} // end of if ()
sync[i].beforeCompletion();
} catch (Throwable t)
{
if (trace)
{
log.trace(failed before completion, t);
}
status = Status.STATUS_MARKED_ROLLBACK;
break;
}
}
This means that if sync[i].beforeCompletion() throws an
exception and trace == false, the exception with all
its error information is thrown into the bit bucket. I
consider this a bug.
(In my case e.g., sync[i] represents a JCA resource
adapter for JDO, and I would not have been able to find
the cause (a database issue) for a transaction rollback
without debugging into JBoss.)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=680956group_id=22866
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Jboss.net undeployment
Hi, Currently, I have to restart jboss to undeploy/redeploy webservices. Hot-deployment works fine, but can not be repeated without a restart. I noticed in the axis doco that they use an undeployment descriptor. Would something similar work for jboss-net? Thanks, fawce --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-681013 ] Patch for bug #664400 - JNDIView.listXML output ill-formed
Bugs item #681013, was opened at 2003-02-05 16:00 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681013group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Rod Burgett (rodburgett) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for bug #664400 - JNDIView.listXML output ill-formed Initial Comment: If JNDIView.listXML() encounters an error, the output string is ill-formed XML. See bug for detailed problem description. The essential problem is the try/catch blocks are too big, not specific enough. The attached diff file essentially refactors try/catch handling to make sure XML tags are paired properly. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681013group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JMS usability
Hello,
I'm having real trouble here trying to make JBoss 3.0.4 compiled and run
with JDK 1.4.0 send messages to a remote queue (on another computer).
I've asked on the JBoss-user list and received no answer, so I'm trying
here too. I heard somebody say he's using JBossMQ on production machines
- maybe he can share this with us? We have purchased the JBoss manuals,
but they aren't any good at explaining this.
Here is my original post:
Hello folks, I'm using JBoss 3.0.4 with the 1.4.0 JDK from Sun, compiled
from sources, with jbossmq as the JMS implementation. I'm running
everything on a Mandrake Linux 9.0. The remote computer uses the same
versions of JBoss and JDK.
I'm trying to send a message to a queue on a different computer here;
trouble is, I can't find the exact steps to take to do that in the docs.
The approach I've been trying is using JNP to find the JNDI provider on
the remote computer (jnp://192.168.192.252:1099), access the queue by
it's name (say queue/B), and try to send it a message. But trouble is
both lookup(ConnectionFactory) and lookup(queue/B) return null. When
an office mate tries to send a message to me, the message gets through,
but the JBoss console says something about an exception: Cannot connect
to the ConnectionReceiver/Server. I'm using localhost:8080/jmx-console
to verify that messages get through. I'm trying to send messages from a
client application, not from an enterprise bean.
Here's what I do:
env.put(Context.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
env.put(Context.PROVIDER_URL, jnp://merlin:1099);
env.put(Context.URL_PKG_PREFIXES,
org.jboss.naming:org.jnp.interfaces);
env.put( Context.SECURITY_PRINCIPAL, john );
env.put( Context.SECURITY_CREDENTIALS, neddle );
InitialContext iniCtx = new InitialContext(env);
System.out.println (New context: + iniCtx + env: + env);
QueueConnectionFactory qcf = (QueueConnectionFactory)
iniCtx.lookup(ConnectionFactory);
if (qcf == null) {
System.out.println (OOPS);
//return ;
}
What am I doing wrong? Any ideas?
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head/4.0.oalpha, jmx-console, jboss-web.xml
The jmx-console's jboss-web.xml is missing in my build of jboss-head. This is because the web-inf element is missing in from the war instruction in varia/build.xml I notice because I have a buildfile which inserts security stuff into this file... Intention or oversight ? Cheers, Jules This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JMS usability
Your login credentials have a type-o should be john,needle.
Also, reference the queue or topic name without the queue/ prefix.
Lastly, I would consult the extensive examples in the testsuite under
jbossmq, since you are doing a lot of environment setup that has much
more convenient (and portable) access via the JMS objects themselves.
Also, I would make sure you understand the implications of using
john,needle account, since it is a durable subscriber with a
pre-configured id. You may get some undesirable behavior, since I
believe the point of the preconfigured id is to prevent multiple
concurrent logins.
Hope this is helpful (and accurate),
fawce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Stefan Puiu
Sent: Wednesday, February 05, 2003 11:24 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] JMS usability
Hello,
I'm having real trouble here trying to make JBoss 3.0.4 compiled and run
with JDK 1.4.0 send messages to a remote queue (on another computer).
I've asked on the JBoss-user list and received no answer, so I'm trying
here too. I heard somebody say he's using JBossMQ on production machines
- maybe he can share this with us? We have purchased the JBoss manuals,
but they aren't any good at explaining this.
Here is my original post:
Hello folks, I'm using JBoss 3.0.4 with the 1.4.0 JDK from Sun, compiled
from sources, with jbossmq as the JMS implementation. I'm running
everything on a Mandrake Linux 9.0. The remote computer uses the same
versions of JBoss and JDK.
I'm trying to send a message to a queue on a different computer here;
trouble is, I can't find the exact steps to take to do that in the docs.
The approach I've been trying is using JNP to find the JNDI provider on
the remote computer (jnp://192.168.192.252:1099), access the queue by
it's name (say queue/B), and try to send it a message. But trouble is
both lookup(ConnectionFactory) and lookup(queue/B) return null. When
an office mate tries to send a message to me, the message gets through,
but the JBoss console says something about an exception: Cannot connect
to the ConnectionReceiver/Server. I'm using localhost:8080/jmx-console
to verify that messages get through. I'm trying to send messages from a
client application, not from an enterprise bean.
Here's what I do:
env.put(Context.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
env.put(Context.PROVIDER_URL, jnp://merlin:1099);
env.put(Context.URL_PKG_PREFIXES,
org.jboss.naming:org.jnp.interfaces);
env.put( Context.SECURITY_PRINCIPAL, john );
env.put( Context.SECURITY_CREDENTIALS, neddle );
InitialContext iniCtx = new InitialContext(env);
System.out.println (New context: + iniCtx + env: + env);
QueueConnectionFactory qcf = (QueueConnectionFactory)
iniCtx.lookup(ConnectionFactory);
if (qcf == null) {
System.out.println (OOPS);
//return ;
}
What am I doing wrong? Any ideas?
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-681216 ] JBossQL Limit/Offset support
Change Notes item #681216, was opened at 2003-02-05 12:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=381174aid=681216group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Priority: 5 Submitted By: Jeremy Boynes (jboynes) Assigned to: Nobody/Anonymous (nobody) Summary: JBossQL Limit/Offset support Initial Comment: Support has been added for restricting the amount of data fetched from a JDBC database. JBossQL now supports optional OFFSET and LIMIT parameters supplied at the end of a query. An example would be SELECT OBJECT(o) FROM Order o WHERE o.status = ?1 ORDER BY o.orderDate OFFSET ?2 LIMIT ?3 This works by discarding rows until offset rows have been fetched and then returning immedately once another limit rows have been fetched. This simple mechanism is intended to preserve portability across database vendors. Other approaches including scrollable cursors or database-specific syntax may be considered later. Currently the parameters passed to LIMIT and OFFSET must be int values (or Integer for DynamicQL) as in the finder Collection findAllOrders(String status, int offset, int limit) throws FinderException; -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=381174aid=681216group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 5-February-2003
JBoss daily test results SUMMARY Number of tests run: 1026 Successful tests: 1023 Errors:2 Failures: 1 [time of test: 2003-02-05.12-05 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1_03-69] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.2.3] See http://users.jboss.org/~starksm/Branch_3_0/2003-02-05.12-05 for details of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: LocalWrapperCleanupUnitTestCase Test: testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: Row committed, autocommit still on! - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: BeanStressTestCase Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: expected a client deadlock for AB BA - --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-681284 ] jboss 3.0.6 Shutdown.jar does not work
Bugs item #681284, was opened at 2003-02-05 16:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681284group_id=22866 Category: JBossServer Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mike Karrys (mkarrys) Assigned to: Nobody/Anonymous (nobody) Summary: jboss 3.0.6 Shutdown.jar does not work Initial Comment: In jboss-3.0.6 the shutdown.jar has stopped working. I am running Linux 2.4.18 with jdk 1.4.1_01 and I cannot shutdown the system. The shutdown says that it worked but the JVM continues to run. I have been using 3.0.2 thru 3.0.5 on this system and they all have shutdown fine. I even reveted back to 3.0.5 and it shutdown. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681284group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-681284 ] jboss 3.0.6 Shutdown.jar does not work
Bugs item #681284, was opened at 2003-02-05 14:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681284group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Mike Karrys (mkarrys) Assigned to: Scott M Stark (starksm) Summary: jboss 3.0.6 Shutdown.jar does not work Initial Comment: In jboss-3.0.6 the shutdown.jar has stopped working. I am running Linux 2.4.18 with jdk 1.4.1_01 and I cannot shutdown the system. The shutdown says that it worked but the JVM continues to run. I have been using 3.0.2 thru 3.0.5 on this system and they all have shutdown fine. I even reveted back to 3.0.5 and it shutdown. -- Comment By: Scott M Stark (starksm) Date: 2003-02-05 14:34 Message: Logged In: YES user_id=175228 This is already fixed. Just pass in -p anything to get it to work. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=681284group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-675987 ] jboss 3.2 RC1.: Error in client/auth.conf:
Bugs item #675987, was opened at 2003-01-28 01:47
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=675987group_id=22866
Category: JBossSX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Roland Haag (rhaag)
Assigned to: Scott M Stark (starksm)
Summary: jboss 3.2 RC1.: Error in client/auth.conf:
Initial Comment:
Hi,
in client/auth.conf:
---
other {
// Example client auth.conf for using the
SRPLoginModule
// rhaag: Changed from
//org.jboss.srp.jaas.SRPLoginModule required
// to
org.jboss.security.srp.jaas.SRPLoginModule required
---
org.jboss.srp.jaas.SRPLoginModule does no longer exist.
Using org.jboss.security.srp.jaas.SRPLoginModule
results in another error.
We have swing applications using security contexts,
which do not work with jboss 3.x - jboss 2.x works fine.
Thanks
Ciao
Roland
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=675987group_id=22866
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-679841 ] build init creates error in local.properties
Bugs item #679841, was opened at 2003-02-03 21:59
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=679841group_id=22866
Category: Build System
Group: CVS HEAD
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Elo (elosf)
Assigned to: David Jencks (d_jencks)
Summary: build init creates error in local.properties
Initial Comment:
I installed a clean 1.5.1 version of Ant and I use JSDK
1.4.1. I checked out the JBoss source and ran:
./build/build.sh init
and this created a file with the line:
xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet-
xdoclet
I was also getting a failure to define Ant task jmxdoclet,
which I attributed to Ant not finding the XDoclet libs. (I
do not define a classpath environment variable as I
prefer to keep things in source files as much as
possible.)
Anyway, I went and tweaked that line in local.properties
to be:
xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet/xd
oclet
where I changed the last '-' to a '/' after looking at the
thirdparty directory and seeing that there is a lib
directory under xdoclet/xdoclet.
The old error went away, but now I am throwing:
java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
so I think there are more pervasive classpath problems.
All of these .jars exist in the thirdparty directory, so I'm
not sure why they are not properly added into the ant
build environment.
Help would be very appreciated to: [EMAIL PROTECTED]
--
Comment By: Elo (elosf)
Date: 2003-02-05 23:55
Message:
Logged In: YES
user_id=703778
The problem was the following line of text from the CVS
configuration guide:
CVS Modules:
jboss-all : Everything required to build JBoss.
I used:
cvs co jboss-all
cd build
./build.sh
I have now used the jboss-head module to successfully
build. Thank you for pointing out the correct module.
Place I looked for information related to this:
Sourceforge.net JBoss Mailing List Archives
Instructions that I found on the web:
http://www.jboss.org/developers/sourcecode.jsp (CVS
configuration)
http://www.jboss.org/developers/guides/quickstart.jsp (build
instructions)
--
Comment By: David Jencks (d_jencks)
Date: 2003-02-03 23:58
Message:
Logged In: YES
user_id=60525
You did not check out the sources correctly, and have mixed versions. The
instructions seem to have disappeared or become hard to find on the website.
cvs ... co jboss-head
cvs ... co -r Branch_3_2 jboss-3.2
cvs ... co -r Branch_3_0 jboss-3.0
If these don't work for you reopen the bug with a really clear explanation of what you
checked out. Also search the lists and forums before filing a bug on something like
this.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=679841group_id=22866
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
