[josm-dev] first impressions

Oliver Raupach oliver at raupach.cc
Tue Jan 10 15:11:51 GMT 2012


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.

Ant is no longer "state of the art". The syntax is hard to understand. 
It is too bad to maintain. There is no dependency management. It is no 
standard at all.
How about using maven?

I'm not sure, but was third-party software (oauth.*, org.apache.commons 
.*) included as source code? This is something I've never seen before. 
How is this maintained? This would be much easier with maven.

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....

*Oliver Raupach **
Java Entwickler*

Mobil: +49 (0) 170 18 38 4 99
Mail: oliver at raupach.cc
Web: http://www.oliver-raupach.de
Profil: http://www.oliver-raupach.de/profil/Profil_Oliver_Raupach.pdf

Am 10.01.2012 15:14, schrieb Paul Hartmann:
> On 01/10/2012 02:20 PM, Oliver Raupach wrote:
>> 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?
> What do you mean by this?
>> Are there any junit
>> tests?
> Yes, there are a few in the test folder.
>> Why everything is built with ant?
> Why not? What do you expect in particular and how would it improve our
> work-flow?
> Paul
> _______________________________________________
> josm-dev mailing list
> josm-dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/josm-dev

More information about the josm-dev mailing list