Hi,

Something confusing (for me) in OpenJUMP code structure, is that code is separated in two main packages :
- one for the historical JUMP code (com.vividsolutions.*),
- and one for Jump Pilot project (now OpenJUMP) (org.*)
there are many dependencies between these packages, and no real way to guess in which one is the class you're looking for, only historical reasons. Too bad, would be difficult to improve this now, but maybe worthwhile if we had more manpower. There used to be two jar files until 1.4.1 (com and org), but we did a single jar file in 1.4.2

Build system is quite simple. The reference build file is the ant build.xml in etc directory, and all dependencies are in the lib directory. OpenJUMP has few contributors. We have already made several releases but as far as I know we have never used branches and merges, just trunk and new tags at release time. Introduction of Maven is quite recent in the project and has just been installed, I think, to manage the NB.

My experience with svn, maven and continuous integration tools is very limited, but Ede does a good job to improve things and your help is welcome ;-)

Michaël


Le 12/10/2011 23:07, G. Allegri a écrit :
Thanks Michaël for the clear reply.
I appreciate very much your precious work on OJ, but my impression (coming from other OS projects) is that OJ misses a coherent naming and code structure. I feel that having a cleaner model would help very much potential developers and power users. I think that a maven build system, with various profiles, should automate the most possible, otherwise it can be very confusing where to pick the required libs, extensions, etc. Anyway, I know that it isn't an easy task. The other way could be to set up a clear documentation (even a single page) where the actual structure(s) are explained:

 - what is a user/developer expected to find in the X build
 - the relation between builds and SVN branches/tags/trunk

At least a common naming should be found to title downloadable builds, and maven build profiles.
Another hint: find a coherent naming for plugins.
I know you're working on this. They're not critics but hints. They're my two cents after having browsed the various Sourceforge pages and SVN for some days ;)

giovanni


2011/10/12 Michaël Michaud <michael.mich...@free.fr <mailto:michael.mich...@free.fr>>

    Hi Giovanni,

    -s refers to a special Sextante edition. Stefan has created this
    edition one or two years ago including OpenJUMP, Sextante, and
    many other plugins around there.

    I kept this formule for 1.4.1 and 1.4.2 version (1.4.1-s and
    1.4.2-s are available in
    https://sourceforge.net/projects/jump-pilot/files/OpenJUMP/),
    even if I changed significantly the list of included plugins.

    Recently, we had a discussion about ecw plugin distribution and
    decided that it will be included in the -s version, and Ede
    suggested to change the name of this version from -s to something
    else (Stefan has plenty of ideas, and the extension name, maybe
    PLUS to have something explicit in the build system has still to
    be choosen).

    Currently, included plugins are quite heterogeneous, and many of
    them are just available as is, with their source, on my website or
    on cadplan website.
    I put one of my plugin on OJ svn (graph toolbox), but others are
    still not and none of them are on maven repository.

    Is it important to have PLUS version plugins centralised or
    mavenized for you ?

    Michaël

    Le 12/10/2011 22:07, G. Allegri a écrit :
    I've just started following this mailing list and studying OJ
    build system.
    AFAIK you're setting up a maven to distinguish a CORE and PLUS
    build. Is the PLUS build supposed to include all the extension
    listed by Michaël? Sextante, graph-toolbox, etc. I mean, will
    they refer to maven public repositories, or will be put inside
    the OJ svn?

    A second question. I see you're talking about an "-s" edition. Is
    it already available? Does it correspond to the PLUS version?

    I will apreciate very much some clarification.
    Thanks,
    giovanni

    2011/10/12 Michaël Michaud <michael.mich...@free.fr
    <mailto:michael.mich...@free.fr>>

        Hi Ede,

        here is a list of extensions, dependencies and source
        location for -s
        (or whatever) OpenJUMP version.

        Not complete, sorry, but a good start.
        I think Sextante 0.6 has been put as is in the distro, and
        sextante
        bindings has been modified by Peppe (small modification to
        look for
        Sextante in a specific directory if I'm correct), not sure if
        I compiled
        it myself.

        aggregation-0.2.4
            author : michaël
            jar : included in openjump-1.4.2-s
            src : zipped on
        http://geo.michaelm.free.fr/OpenJUMP/resources/
            i18n : included in jar

        bsheditor4jump-0.2.1.jar
            author : michaël (it uses also old jedit code)
            jar : included in openjump-1.4.2-s
            src : version 0.2.0 zipped on
        http://geo.michaelm.free.fr/OpenJUMP/resources/ : TO BE UPDATED
            i18n : included in jar
            dependance : buoy.jar

        driver-dxf-0.7.3.jar
            author : michaël
            jar : included in openjump-1.4.2-s
            src : version 0.2.0 zipped on
        http://geo.michaelm.free.fr/OpenJUMP/resources/drivers

        graph-toolbox-0.1.2.jar
            author : michaël
            jar : included in openjump-1.4.2-s
            src : managed in JPP svn
            i18n : included in jar
            depends on jump-jgrapht-0.4.jar and jgrapht-jdk1.6.jar
                jump-jgrapht-0.4.jar src : version
        http://geo.michaelm.free.fr/OpenJUMP/resources/
                jgrapht-jdk1.6.jar src : http://jgrapht.sourceforge.net/

        JumpChart.jar and
        jumpPrinter.jar and
        VertexSymbols.jar
            author : cadplan
            jar : included in openjump-1.4.2-s
            sources available on http://www.cadplan.com.au/
            depends also on iText-2.1.5.jar

        PirolCsv.jar
            author :
        http://www.pirol.hs-osnabrueck.de/jump-download.html?&no_cache=1
        <http://www.pirol.hs-osnabrueck.de/jump-download.html?&no_cache=1>
            jar : included in openjump-1.4.2-s
            sources : included in the jar
            depends on pbaseClasses.jar (sources included)

        PostGISPlugIn-1.4.2alpha.jar
            authors : many
            jar : included in openjump-1.4.2-s
            sources : managed in JPP svn

        Sextante binding-0.6.1.jar
            author : Victor Olaya (small adaptation from Giuseppe)
            jar : included in openjump-1.4.2-s
            sources : included in jar

        TableLayout-bin-jdk1.5-2007-04-21.jar
            cannot remember which plugin depends on it

        topology-0.3.jar
            author : michaël
            jar : included in openjump-1.4.2-s
            src : zipped on
        http://geo.michaelm.free.fr/OpenJUMP/resources/
            i18n : included in jar

        txt-driver-0.3.0.jar
            author : michaël
            jar : included in openjump-1.4.2-s
            src : zipped on
        http://geo.michaelm.free.fr/OpenJUMP/resources/
            i18n : included in jar

        x-bean-2.2.0.jar
            cannot remember which plugin depends on it

        sextante directory
            author : Victor Olaya
            jar : 34 jars included in the directory
            src : http://sextante.forge.osor.eu/contact.html



        Le 12/10/2011 20:49, edgar.sol...@web.de
        <mailto:edgar.sol...@web.de> a écrit :
        > michael,
        >
        > could you please shortly summarize the incuded extensions
        and the locations of distro zips or their sources you use to
        compile sextante edition? i'd like to complete the plus
        snapshot definition.
        >
        > thanks ede
        >
        >
        
------------------------------------------------------------------------------
        > All the data continuously generated in your IT
        infrastructure contains a
        > definitive record of customers, application performance,
        security
        > threats, fraudulent activity and more. Splunk takes this
        data and makes
        > sense of it. Business sense. IT sense. Common sense.
        > http://p.sf.net/sfu/splunk-d2d-oct
        > _______________________________________________
        > Jump-pilot-devel mailing list
        > Jump-pilot-devel@lists.sourceforge.net
        <mailto:Jump-pilot-devel@lists.sourceforge.net>
        > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
        >
        >


        
------------------------------------------------------------------------------
        All the data continuously generated in your IT infrastructure
        contains a
        definitive record of customers, application performance, security
        threats, fraudulent activity and more. Splunk takes this data
        and makes
        sense of it. Business sense. IT sense. Common sense.
        http://p.sf.net/sfu/splunk-d2d-oct
        _______________________________________________
        Jump-pilot-devel mailing list
        Jump-pilot-devel@lists.sourceforge.net
        <mailto:Jump-pilot-devel@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




    
------------------------------------------------------------------------------
    All the data continuously generated in your IT infrastructure contains a
    definitive record of customers, application performance, security
    threats, fraudulent activity and more. Splunk takes this data and makes
    sense of it. Business sense. IT sense. Common sense.
    http://p.sf.net/sfu/splunk-d2d-oct


    _______________________________________________
    Jump-pilot-devel mailing list
    Jump-pilot-devel@lists.sourceforge.net  
<mailto:Jump-pilot-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel


    
------------------------------------------------------------------------------
    All the data continuously generated in your IT infrastructure
    contains a
    definitive record of customers, application performance, security
    threats, fraudulent activity and more. Splunk takes this data and
    makes
    sense of it. Business sense. IT sense. Common sense.
    http://p.sf.net/sfu/splunk-d2d-oct
    _______________________________________________
    Jump-pilot-devel mailing list
    Jump-pilot-devel@lists.sourceforge.net
    <mailto:Jump-pilot-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct


_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to