You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2014/10/02 12:51:34 UTC
[jira] [Updated] (DIRSTUDIO-995) Migrate build system to use Tycho
[ https://issues.apache.org/jira/browse/DIRSTUDIO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSTUDIO-995:
----------------------------------------
Description:
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
** In progess:
* Migrate features
** Done:
** In progress: ldifeditor, ldapbrowser
* Migrate RCP application
* 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
was:
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
** In progess:
* Migrate features
** Done:
** In progress: ldifeditor, ldapbrowser
* Migrate RCP application
* 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
> 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
> ** In progess:
> * Migrate features
> ** Done:
> ** In progress: ldifeditor, ldapbrowser
> * Migrate RCP application
> * 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)