Hi,
I've just finished watching the first time the code for this project and
I am a little confused.
Is there a hudson/jenkins build for this project? Are there any junit
tests? Why everything is built with ant?
--
*Oliver Raupach **
Java Entwickler*
Mobil: +49 (0) 170 18 38 4 99
Mail:
Hi,
Jenkins is a continuous integration tool. I think it definitely makes
sense to build projects with Jenkins.
- The tests are executed.
- The software is built.
- Errors are reported.
- All automatically after each commit.
- Jenkins can also run tools like checkstyle, sonar or findbugs.
On Tue, 10 Jan 2012, Oliver Raupach wrote:
I mean, there's surely a reason for everything. That was just my first
impressions when I viewed the source codeand tried to create a plugin
There is a very simple reason. It works and is simple. The more
complicated the build system gets the
Hi,
On 01/10/12 16:11, Oliver Raupach wrote:
I mean, there's surely a reason for everything.
The main reason is that most of us are not Java developers by trade, but
instead many of us are allround developers who happen to code Java among
other things.
We also try to attract people from
Hi,
I have hudson running at my laptop that builds josm and plugins and
also checks for changes in josm that breaks backward compatibility
with plugins. Problem is that it's broken all the time (either
compilation error in plugins or some change in josm that breaks some
plugins) so I basically
Hi,
whenver a license change layer is active and you have lots of
objects loaded, JOSM becomes noticeably slower.
I could use a little help here. Since many of you have tweaked JOSM's
drawing performance in the past, maybe you only need to take a quick
look at this drawing code
On Tue, 10 Jan 2012, Jiri Klement wrote:
I have hudson running at my laptop that builds josm and plugins and
also checks for changes in josm that breaks backward compatibility
with plugins. Problem is that it's broken all the time (either
compilation error in plugins or some change in josm that