activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Di Tolla (JIRA)" <>
Subject [jira] [Commented] (APLO-332) Apollo not starting with cygwin under windows7
Date Wed, 31 Jul 2013 21:25:49 GMT


Francesco Di Tolla commented on APLO-332:

I did a test and the fix works fine.

What's left is to change Create.scala such that it creates the script $APOLLO_HOME/bin/apollo-broker
even for windows or at least for windows with cygwin.
> Apollo not starting with cygwin under windows7
> ----------------------------------------------
>                 Key: APLO-332
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-cli
>    Affects Versions: 1.6
>         Environment: windows 7 32bit + cygwin + Java 1.7
>            Reporter: Francesco Di Tolla
>            Priority: Blocker
> the commands: "apollo" or "apollo create broker" fail with the error
> Exception in thread "main" java.lang.ClassNotFoundException: org.apache.activemq.apollo.cli.Apollo
> the problem seems to be related to the fact the $BOOTDIRS argument is passed as unix
> To fix this I modified by hand, in my istallation, the bin/apollo script adding
>       BOOTDIRS=`cygpath --path --windows "$BOOTDIRS"`
> in the if block for cygwin and it seems to work correctly.
> The "apollo create broker" command creates a script APOLLO_BASE/bin/apollo-broker.cmd,
and no unix-like apollo-broker script, which I created by hand.
> When $APOLLO_HOME/bin/apollo is called from the apollo-broker script,it fails again since
the APOLLO_BASE is set.
> This happens cause of the setting:
> wich is no convertet properly by cygpath.
> To fix it I changed again the definition of BOOTDIRS in the same place as above, i.e.
in the block for cygwin, as follows:
>      BOOTDIRS=`cygpath --path --windows "${APOLLO_BASE}/lib\:${APOLLO_HOME}/lib"`
> .

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message