Bill Shannon wrote:
> A week ago I had everything working, I was able to run the quicklook
> tests (with some known failures) and I was ready to commit some
> changes. Then I got called away for a week and I'm back to pick
> up where I left off. But I decided I better update everything and
> run the tests again.
>
> I did a "maven bootstrap-all" and a bunch of "cvs update"s to
> make sure I was in sync. It builds fine but when I do "maven runtest"
> I get
I hope you did "maven clobber bootstrap-all" so that there are no
multiple manifests are present (if you have the build log saved you can
see some message while updating jar file). Did you update
"glassfish/bootstrap" module? since there are some binary component
versions also changed e.g. JAX*, WS* binary versions changed..
So to sync up the workspace to latest one, you can try following steps:
-Do cvs update on glassfish/bootstrap and glassfish/appserv-tests modules.
-run following command to get latest sources and build it from
glassfish/bootstrap directory.
% maven clean clobber
% maven checkout bootstrap-all build configure-runtime
% cd appserv-tests; maven runtest
thanks
Dinesh
> [java] startDomainUnix:
> [java] [exec] javax/jms/JMSException
> [java]
> [java] BUILD FAILED
> [java] /cache/tmp/glassfish/glassfish/appserv-tests/build.xml:36:
> The following error occurred while executing this line:
> [java] / s/config/run.xml:38: exec
> returned: 1
>
> When I try to start the app server I get:
>
> datsun$ bin/asadmin start-domain domain1
> javax/jms/JMSException
>
> There's nothing in the server log file.
>
> Did I do something wrong or is this a new bug in the build?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>