forked from mendix/m2ee-tools
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathNEWS
More file actions
56 lines (42 loc) · 2.48 KB
/
Copy pathNEWS
File metadata and controls
56 lines (42 loc) · 2.48 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
m2ee-tools 0.5.11.2, 19 Nov 2015
================================
The runtime_blocking_connector option is now disabled by default. It seems this
connector in Jetty has a bug that causes connections to the Runtime being
closed by Jetty while waiting for a response after issuing a HTTP request.
The option will probably removed altogether in the future.
m2ee-tools 0.5.11, 5 Jan 2015
=============================
The source of the munin plugin for m2ee and all documentation are now also
included in the m2ee source tree.
A new graph, a JVM Process Memory breakdown is included in the munin plugin.
Unfortunately, to be able to use this graph munin needs to be patched to set
group permissions correctly. See the munin page in the documentation for more
information about this.
m2ee-tools 0.5.9, 14 Apr 2014
=============================
The new -y (or --yolo) argument to m2ee can be used to suppress questions that
ask for confirmation when using commands like stop, unpack, emptydb and
restoredb. During start, activating yolo mode will even automatically execute
and save DDL commands, and change passwords of admin users to some random
password if the runtime refuses to start because they have password '1'.
This option can be used for quick and dirty automation of application
deployment using one-off m2ee commands, or it can be used when you're working in
some test or development environment where you don't need to be cautious at all
about throwing away data etc.
m2ee-tools 0.5.7, 27 Nov 2013
=============================
m2ee now has the possibility to download missing Mendix Runtime distributions on
demand.
In order to use this functionality, the mxjar_repo configuration setting (in the
mxnode section of the yaml configuration file) needs to have a user writable
location included. If a 'runtimes' directory exists under the app_base location,
as specified in the m2ee section below, it will be inserted at the front of the
mxjar_repo automatically, to facilitate runtime downloads on demand.
The new download_runtime command can be used without any argument, in which case
it will try downloading the Mendix Runtime for the current unpacked application
model, if it's missing.
When providing an argument to download_runtime, e.g. "download_runtime 4.7.1",
another Mendix Runtime can be downloaded. When preparing for a new application
release, this can be used to make sure the new version is already installed.
Also, see the documentation in examples/full-documented-m2ee.yaml about
configuring mxjar_repo