/
NEWS
288 lines (183 loc) · 8.28 KB
/
NEWS
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
2.7.1
=====
Catalog format has changed again to add all missing information. Simply delete your existing
catalogs directory under your profile and recreate them in Jedi using Project / Update Catalogs.
2.7
===
Catalog format has changed. Simply delete your existing catalogs directory under your profile
and recreate them in Jedi using Project / Update Catalogs.
2.6.9
=====
Kernel format has changed. You will need to do a 'jam make cleankernel'. Note that this
will *not* delete compilation binaries.
2.6.6
=====
Catalog format has changed. Simply delete your existing catalogs directory under your profile
and recreate them in Jedi using Project / Update Catalogs.
2.6.5
=====
Kernel format has changed. You will need to do a 'jam make cleankernel'. Note that this
will *not* delete compilation binaries.
2.6.4
=====
The format for active-project in Workbench-Preferences has changed.
The full path to the project in the workbench is now needed.
2.6
===
Jazz and Jedi have finally been separated!
To install Jedi :
- clone or pull the latest code from http://github.com/jazzscheme/jedi.git
- cd into the directory
- execute: git submodule update --init
- execute: jam make
This should build a fully optimized Jedi at bin/jedi.
2.5.16
======
Catalog format has changed. Simply delete your existing catalogs directory under your profile
and recreate them in Jedi using the Tools / Catalogs Manager window.
2.5.15
======
The name of a catalog was changed to include the name of its parent projects. Because of this,
existing catalog output files won't be found when launching Jedi. Simply update your catalogs
using the Tools / Catalogs Manager window.
2.5.0
=====
Once you build the kernel, a new versionned settings directory will be created as ~/.jazz/2.5.0.
This infrastructure enables different versions of Jazz using incompatible settings to coexist.
A ~/.jedi/2.5.0 versioned directory will also be created. Jedi profiles are now cleanly stored
under this settings directory instead of in ~/jazz_user as they used to be.
2.4.20
======
A new infrastructure for the Jazz repository is now in place that uses
Git submodules to track Jazz's dependency to Gambit.
Having Gambit as a submodule of Jazz enables us to evolve Gambit independently
of the official version. Note that this is *not* a fork. We plan on working closely with
Marc Feeley to merge our changes back into Gambit's main trunk.
Jazz's build system is now invoked through a script named jam for Jazz Manager. This
script will automatically take care of bootstrapping gambit to build a totally self-contained
compiler and runtime in the gambit directory that it will then use. Apart from the bootstrapping
part, jam behaves exactly the same as the old approach of using gsc to invoke the build system.
2.4.18
======
Jazz now depends on Gambit-Jazz. It is possible to install it in a location not in your
PATH and use the GSC_JAZZ environment variable to point to the gsc executable. That way,
you don't need to replace your standard Gambit-C installation. To start the build system, you
must now use the jbs script which takes care of running the appropriate gambit executable.
It is now also required to have the msys bin directory in your path to allow execution of
msys shell by gambit-c open-process procedure.
2.4.17
======
Workspaces preferences have been moved out of Preferences.jml into their own Workspaces.jml file.
At the toplevel you will need to replace "<workspaces~>" with "<Workspaces-Preferences>".
Please update your profiles.
2.4.16
======
WebServers.jml settings file was renamed to Servers.jml.
You will also need to replace every "Web-Server" occurence in the file with just "Server".
Please update your profiles.
2.4.15
======
Renamed the previous 2.4.14 change from application to appl.
Please update your .package files.
2.4.14
======
The format of .package in jazz_user profiles has changed.
Here is an example of what you would need to add for a profile.me profile:
Before: (profiles (Me (unit profile.me)))
After: (profiles (Me (application jedi) (unit profile.me)))
2.4.12
======
Configuration destination alias jazz: was changed to build:.
Please update your ~/.jazz/.configurations file.
2.4.10
======
Changed the file: property of Favorite-Configuration to a more generic target: property.
Please update your Preferences.jml settings file.
2.4.1
=====
The minibuffer was moved into its own auto-show/hide toolbar. You will need to update
your profiles.
If you haven't customized any workspaces, simplest solution is to create a new profile,
edit its generated Preferences.jml file, copy the whole (<workspaces~> ...) section and
replace it in all your profiles.
2.4.0
=====
For each of your profiles you will need to update the workspace preferences located in
Preferences.jml as the format was changed in new multi-stage management 'a la emacs'.
Simplest solution is to create a new profile, edit its generated Preferences.jml
file, copy the whole (<workspaces~> ...) section and replace it in all your profiles.
2.1.27
======
In preparation for the new shared libraries, module has been renamed to
unit and library renamed to module. Please update your code.
To update your profiles, I suggest running a non-whole-word search & replace
on your profile directories replacing module by unit and library by module
searching every file including .package.
Note that the jazz.library import remains jazz.library.
2.1.25
======
The kludge of duplicating many action-items with an equivalent -aux was
replaced by a clean alternate-shortcut property of action-items.
Please update your Bindings.jml settings file.
2.1.23
======
Method propagation must now be explicit. Supported propagations are:
- final (the default)
- virtual
- override
This means that every test, test-shift, ... method in your profile class must
now add an explicit override modifier. For example:
(method override (test)
...)
2.1.21
======
Because a slot was added to the Lisp-Entry class, you will need to manually
delete your catalogs before launching Jedi.
2.1.16
======
The jazz.parse-verbose? setting was renamed to jazz.outline-verbose?. Please
update your HOME/.jazz/.jazzini file.
2.0.12
======
Due to packages beeing renamed from <package name>.pck to just .package, you
will need to do a make clean on your built configurations or manually rename
your already built packages. You will also need to manually rename your user
packages.
2.0.10
======
Renamed the user directory from HOME/jazz_projects to HOME/jazz_user in
preparation to it supporting more than user projects now that build output
goes to HOME/jazz_user/build.
2.0.9
=====
New profiles are now stored in their own package. For example, a new 'Me'
profile will end up creating a HOME/jazz_projects/lib/profile.me package.
Also, the system doesn't rely on a file system heuristic anymore to discover
profiles but on an explicit 'profiles' property of packages. This new approach
adds a lot of flexibility and makes it possible for instance to have a package
contain both its own code and a profile that developers of that package can
use when login in to Jedi.
To convert an existing profile lets say 'Me', we suggest you use the login
dialog to create a new 'Me' profile (note that this will not overwrite your
old profile) and then migrate your old 'Me' profile content into the new
'Me' profile manually.
2.0.5
=====
Starting from this release, Jedi now stores user projects in ~/jazz_projects
instead of ~/.jazz to reflect user projects beeing persistent entities with
invested work. This is in contrast to the ~/.jazz directory that can be deleted
without much lost.
To convert your projects, simply create a ~/jazz_projects directory and move the
existing ~/.jazz/lib directory to it.
2.0.4
=====
This release introduces a restructuration of projects by moving them in their
own 'project.' module for a clean separation between runtime and IDE code. These
changes will break any profile workbench that pointed to Jazz projects.
The simplest way to fix this is to :
- delete and recreate any profile that does not contain any important
customizations you wish to preserve or
- create a new profile, edit its settings/Workbench.jml file, copy every entry
related to Jazz projects in it (e.g. everything from Kernel-Project to
SRFI19-Manifest) and update any broken profile workbench with these correct
entries