Attachments (0)
Change History (10)
follow-up: 4 comment:3 by , 13 years ago
Local build is fixed, I'm not sure about remote build, does it still use it's own script?
comment:4 by , 13 years ago
Replying to jttt:
Local build is fixed,
I still get runtime error
I'm not sure about remote build, does it still use it's own script?
Yes. Is debug.jar supposed to get distributed as part of the release?
follow-up: 8 comment:6 by , 13 years ago
Well, I don't really like that every dependency is copied into source tree, it's already quite a mess with all those externals. On the other hand, build scripts obviously can't copy referenced classes into one big josm-custom.jar and this is only one class so I'll copy it.
comment:8 by , 13 years ago
Replying to jttt:
Well, I don't really like that every dependency is copied into source tree, it's already quite a mess with all those externals. On the other hand, build scripts obviously can't copy referenced classes into one big josm-custom.jar and this is only one class so I'll copy it.
They can do so. But they can't evaluate what is really needed, which is possible when code is in SVN and compiled. The release version should be as small as possible and thus drops everything which is not really required.
comment:9 by , 13 years ago
ProGuard can also optimize jar file by removing unused class (and optionally also methods and do other optimizations) and it works on compiled classes. There is already ant task in build.xml - dist-optimized - that should create similar jar as is done on server for official builds.
comment:10 by , 13 years ago
Maybe we switch to ant in future. But currently I don't think it is necessary.
There is also one additional reason for using sources instead of jar files. I can see what a java file does, I can't do so for a jar file.
In [4721/josm]:
EDIT: commit is not related to this ticket