search

purepennons / gss

Automatically exported from code.google.com/p/gss
Other
0 stars 0 forks source link

ant install/run trouble #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. get gss source
2. set build.properties
3. try to run "ant install"

What is the expected output? What do you see instead?

Expected is build sucess. I do get that, but only config files are copied. 
Gss.ear is not built, and dependecies are not getting downloaded (says fetching 
dependencies only and nothing else). Ant run fails because I have gwt 2.0.0 
present on the host since I am currently running older gss build that required 
gwt 2.0.0. I checked build.xml and saw some new dependencies. I can manually 
download them and try to fix the issue, but would like to know if I am doing 
something wrong or not.

What version of the product are you using? On what operating system?

Os is centos 5 x64.

Please provide any additional information below.

My build.properties currently looks like:

jboss.home=/usr/local/jboss
gwt.path=/usr/local/gwt-2.0.0
gwt.workers=2
junit.path=/usr/share/java
hornetq.path=/usr/local/hornetq/
jboss_run_configuration=default-with-hornetq

I removed deps.dir=/root/gss-27082010/deps line since it did not work (deps dir 
exists inside gss folder, I manually created it, but no downloads seem to be 
there).

Regards,
Nikola

Original issue reported on code.google.com by ngara...@gmail.com on 27 Aug 2010 at 12:02

GoogleCodeExporter commented 8 years ago 
After refactoring the build script, I updated the BuildingAndDeploying wiki 
page with the current instructions. Check it out, but in short, you only need 
gwt.workers now (for speeding up the build) and maybe jboss.args and 
jboss.home. If you do specify jboss.home though, it should end with the 
standard folder name for now (jboss-5.1.0.GA).

This way you will no longer have to deal with changing dependencies in the 
future, and can always rely on the build script fetching anything it needs by 
itself. In all our development workstations we have removed every downloaded 
versions of gwt, jboss, hornetq and junit and rely on the build script to fetch 
everything and keep it up to date. Some of us don't even have a 
build.properties anymore. 

If you have local modifications, and I seem to remember that you do, you may 
have to override certain properties. One such modification that the script 
doesn't handle is that you deploy solr inside jboss, IIRC. I would suggest that 
you try removing build.properties (or replace it with one containing only 
gwt.workers) and run "ant install run" again. It should fetch everything 
needed, put it in the "dependencies" subfolder and launch the service. From 
then on, you can copy the solr bits from your current installation and the 
script will leave them alone (unless you do an "ant distclean").

Original comment by past...@gmail.com on 27 Aug 2010 at 12:25

GoogleCodeExporter commented 8 years ago 
To update the issue, ant install run works fine with updated info. Just have to 
figure out what to put where. Can I use all files from dependencies folder to 
replace  currently existing jboss server and other dependencies for previous 
gss build I was using? 

Regards,
Nikola

Original comment by ngara...@gmail.com on 16 Sep 2010 at 9:02

GoogleCodeExporter commented 8 years ago 
Sure. You can even set jboss.home in build.properties to your current 
installation path and the script will handle it. Just back up your current 
installation to keep the modifications with Solr, etc., set your jboss.path, do 
"ant deinstall" to remove the jboss.path and then "ant install" to copy 
everything back in there. Afterwards you may manually copy the Solr bits from 
your backup to jboss.home.

Original comment by past...@gmail.com on 16 Sep 2010 at 9:16

GoogleCodeExporter commented 8 years ago 
What is the difference between jboss.home and jboss.path?

Original comment by ngara...@gmail.com on 23 Sep 2010 at 1:15

GoogleCodeExporter commented 8 years ago 
Sorry, this was a typo on my part. There is no jboss.path, only jboss.home.

Original comment by past...@gmail.com on 23 Sep 2010 at 1:22

GoogleCodeExporter commented 8 years ago 
Thanks, I thought so.

Regards,
Nikola

Original comment by ngara...@gmail.com on 23 Sep 2010 at 1:31

GoogleCodeExporter commented 8 years ago 
AFAICT from other issues, you successfully installed the latest version, so I'm 
closing this.

Original comment by past...@gmail.com on 15 Oct 2010 at 8:01