You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2010/02/03 07:56:36 UTC
[jira] Assigned: (AMQ-1639) Include unix startup scripts in the
Windows .zip build
[ https://issues.apache.org/activemq/browse/AMQ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1639:
-------------------------------
Assignee: Rob Davies
> Include unix startup scripts in the Windows .zip build
> ------------------------------------------------------
>
> Key: AMQ-1639
> URL: https://issues.apache.org/activemq/browse/AMQ-1639
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.0.0
> Environment: ActiveMQ 5.x, Windows
> Reporter: Torsten Mielke
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.4.0
>
> Attachments: proposed_patch.diff
>
>
> The more recent versions of ActiveMQ do only come with one bin/activemq batch/script file, depending on the platform they were built for. I.e. for Windows there is only an activemq.bat and no equivalent unix shell script anymore (bin/activemq). Looks like a good idea at first, however I (and surely other) use ActiveMQ on Windows from cygwin and so far I have appreciated also having a unix shell script for starting ActiveMQ on Windows.
> So I suggest including the Unix shell script bin/activemq in the Windows build of ActiveMQ. Not sure if it makes sense the other way around (include activemq.bat in the .tar.gz file). Perhaps it does when considering virtualization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.