[
https://issues.apache.org/jira/browse/AMQ-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-1604.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: NEEDS_REVIEWED)
5.5.0
1. The activemq all jar will retain its version number
2. This has been fixed along with other updates to the run scripts.
> Please make the following configuration changes so releases into production
> are simpler
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-1604
> URL: https://issues.apache.org/jira/browse/AMQ-1604
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0.2, 4.1.0, 4.1.1, 5.0.0
> Environment: Linux
> Reporter: Denis Abramov
> Priority: Minor
> Fix For: 5.5.0
>
>
> (1) Please rename the activemq-all-<version>.jar to just activemq-all.jar. It
> will make it easier for users to switch version. We would generally put the
> activemq release on a shared drive and change the pointer "prod", "dev" or
> "staging" to point to the new directory. It would be nice if the
> activemq-all.jar was present in all releases so the link would be the only
> thing I would need to change.
> (2) Please change the log4j appender:
> log4j.appender.out.file=${activemq.base}/data/activemq.log
> Oftentimes activemq is in a protected directory on a network drive
> (${activemq.base}/) so many machines can use it. It would be better if the
> log file would log to /tmp or something else the user can configure. Maybe
> it can be configured in the activemq.xml file? (I always have to change this
> every time we upgrade to a new version)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
