[JBoss-dev] [ jboss-Bugs-682352 ] run-jboss target in build.xml doesn't work

2003-03-27 Thread SourceForge.net
Bugs item #682352, was opened at 2003-02-07 14:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_id=22866

Category: Build System
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Rod Burgett (rodburgett)
Assigned to: David Jencks (d_jencks)
Summary: run-jboss target in build.xml doesn't work

Initial Comment:
The run-jboss target in build.xml (3.2 and 4.0) execs 
run.bat/sh.  The run scripts work alone, but when using 
build.xml the run.bat file complains about not being able 
to find .\run.jar.  This is because the build target 
includes a 'dir=${run.home.dir}' attribute, but the run.jar 
is in run.bin.dir.

After this change, startup still fails.  Now run.bat 
complains about JAVA_HOME not being set.  
JAVA_HOME is clearly set, otherwise ant would have 
noticed.  But run.bat can't see is because of the 
'newenvironment=true' attribute in the exec tag.

Attached is a diff with these changes.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_id=22866


---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-682352 ] run-jboss target in build.xml doesn't work

2003-03-27 Thread SourceForge.net
Bugs item #682352, was opened at 2003-02-07 14:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_id=22866

Category: Build System
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Rod Burgett (rodburgett)
Assigned to: David Jencks (d_jencks)
Summary: run-jboss target in build.xml doesn't work

Initial Comment:
The run-jboss target in build.xml (3.2 and 4.0) execs 
run.bat/sh.  The run scripts work alone, but when using 
build.xml the run.bat file complains about not being able 
to find .\run.jar.  This is because the build target 
includes a 'dir=${run.home.dir}' attribute, but the run.jar 
is in run.bin.dir.

After this change, startup still fails.  Now run.bat 
complains about JAVA_HOME not being set.  
JAVA_HOME is clearly set, otherwise ant would have 
noticed.  But run.bat can't see is because of the 
'newenvironment=true' attribute in the exec tag.

Attached is a diff with these changes.


--

Comment By: David Jencks (d_jencks)
Date: 2003-03-27 19:09

Message:
Logged In: YES 
user_id=60525

fixed in 3.0, 3.2 and 4.0.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_id=22866


---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-682352 ] run-jboss target in build.xml doesn't work

2003-02-07 Thread SourceForge.net
Bugs item #682352, was opened at 2003-02-07 14:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_id=22866

Category: Build System
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Rod Burgett (rodburgett)
Assigned to: Jason Dillon (user57)
Summary: run-jboss target in build.xml doesn't work

Initial Comment:
The run-jboss target in build.xml (3.2 and 4.0) execs 
run.bat/sh.  The run scripts work alone, but when using 
build.xml the run.bat file complains about not being able 
to find .\run.jar.  This is because the build target 
includes a 'dir=${run.home.dir}' attribute, but the run.jar 
is in run.bin.dir.

After this change, startup still fails.  Now run.bat 
complains about JAVA_HOME not being set.  
JAVA_HOME is clearly set, otherwise ant would have 
noticed.  But run.bat can't see is because of the 
'newenvironment=true' attribute in the exec tag.

Attached is a diff with these changes.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=682352group_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