You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Runing build-all task from top-level build.xml file not succeed.
The first error is :
BUILD FAILED
/shared/apache/hackystat/build.xml:381: The following error occurred while
executing this line:
/shared/apache/hackystat/hackystat-sensorbase-postgres/jar.build.xml:6: The
following error occurred while executing this line:
/shared/apache/hackystat/hackystat-sensorbase-postgres/build.xml:21: This
package requires the Postgres JDBC Connector to be installed and
env.POSTGRES_DRIVER_HOME defined
Second try, after remove hackystat-sensorbase-postgres from build-all task,
fail again:
BUILD FAILED
/shared/apache/hackystat/build.xml:386: The following error occurred while
executing this line:
/shared/apache/hackystat/hackystat-sensor-ant/jar.build.xml:29: Error while
expanding /shared/apache/hackystat/hackystat-sensor-ant/thirdpartyjars/JRCS.jar
java.io.FileNotFoundException:
/shared/apache/hackystat/hackystat-sensor-ant/thirdpartyjars/JRCS.jar (No
such file or directory)
After remove sensor-ant as well, the build pass.
* 1. ivy for hackystat-sensorbase-postgres need to be fixed.
* 2. hackystat-sensor-ant's jar task need to be fixed.
Original issue reported on code.google.com by zsxking on 30 Jan 2010 at 3:10
The text was updated successfully, but these errors were encountered:
Hi Shaoxuan,
1. The postgres JDBC driver has licensing issues that prevents it from being in
IvyRoundup. So, we still have to download it manually.
2. The problem is the jar.build.xml referencses JRCS.jar, but the file is named
jrcs.jar. I frankly don't understand why this has worked until now! You can
just
commit a change to the jar.build.xml that changes JRCS to jrcs. Maybe Ant 1.8
is more
strict about file names?
Original issue reported on code.google.com by
zsxking
on 30 Jan 2010 at 3:10The text was updated successfully, but these errors were encountered: