If the Jars and code etc is the same, there must be an environmental
difference between the machines where the tests pass and where the
tests fail.

Are you building the Jar(s) repeatedly (on different machines) or just
building once and then re-using that built code in your various tests?
If you're not re-using the same Jar, then you really can't be sure
about anything. So build it once and then use that for testing.

Also, perhaps you should unzip a Jar that works and a Jar that doesn't
work, and run a diff/compare tool against the 2 directories. There
might be some differences that you weren't expecting.

Wayne

On 10/16/07, DCVer <[EMAIL PROTECTED]> wrote:
>
> Hi all,
> I have really strange error, which I try to solve for weeks. We have tested
> our software (mvn test or mvn install) on many machines, but if we deploy it
> on the server some of the tests fail. In fact all test, which fail need to
> communicate with the data base. Although we have configured the data base
> about 100 times and used our local databases, where local tests do not fail,
> we still receive errors from tests on deployment server. We use PostgreSQL
> (8.1) and Hibernate (version 3.2.5.ga of the dependency jar). So all signs
> on the sky suggest that this is a communication with the data base problem,
> although data base is installed on the same server and hibernate configs
> seems to be correct. Maybe this a Maven bug, which in some specific
> environment fails e.g. to copy resource file (with data base config) to jar
> or for test? Have no idea what else can be wrong ;(
> --
> View this message in context: 
> http://www.nabble.com/Strange-dataBase-error-tf4634191s177.html#a13233541
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to