[jira] [Commented] (DIRSTUDIO-995) Migrate build system to use Tycho

["Stefan Seelmann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194328#comment-14194328 ] 

Stefan Seelmann commented on DIRSTUDIO-995:
-------------------------------------------

I think we don't need the apacheds-launcher plugin anymore. For the apacheds.v15x plugins we used the apacheds-launcher (version 1.2.0 and 1.5.0) to start the server. But since apacheds.v200 we use the UberjarMain class from the server to launch the server. So let's kick it out.

> Migrate build system to use Tycho
> ---------------------------------
>
>                 Key: DIRSTUDIO-995
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-995
>             Project: Directory Studio
>          Issue Type: Task
>    Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>            Priority: Blocker
>             Fix For: 2.0.0-M9
>
>
> Just a TODO list for now...
> * Manage 3rd party dependencies
> * Move tests to *.test fragments?
> * Use Luna
> * Migrate plugins
> ** Done:common,core, common.ui, connection.core, connection.ui, ldifparser, ldifeditor, ldapbrowser.core, ldapbrowser.common, ldapbrowser.ui, valueeditors, aciitemeditor, schemaeditor, apacheds.configuration, apacheds.configuration.v2, ldapservers, ldapservers.apacheds.v153, ldapservers.apacheds.v154, ldapservers.apacheds.v155, ldapservers.apacheds.v156, ldapservers.apacheds.v157, ldapservers.apacheds.v200
> ** In progess: rcp
> * Migrate features
> ** Done: 
> ** In progress: ldifeditor, ldapbrowser, rcp
> * Migrate RCP application / product: in progress
> * Migrate help plugins
> * Installers (Windows EXE, Mac DMG)
> * Generate P2 repository / site, self-hosted
> * P2 repository for API and ApacheDS bundles?
> * Migrate release process
> * Document build system
> * Cleanup POMs: RAT plugin configuration
> * Cleanup old "repository" folder
> Tycho Pros:
> * Easy to consume Eclipse dependencies from p2 repo
> * Easy to produce p2 repo
> * Widely used
> * Small POMs
> Tycho Cons:
> * Managing versions in MANIFEST.MF
> * 3rd party dependencies not available in any p2 repo
> * No "Standard" Maven build, e.g. tests should reside in separate modules



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)