directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRSTUDIO-995) Migrate build system to use Tycho
Date Sun, 15 Mar 2015 21:02:38 GMT

     [ https://issues.apache.org/jira/browse/DIRSTUDIO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Seelmann updated DIRSTUDIO-995:
--------------------------------------
    Description: 
Just a TODO list for now...

* Manage 3rd party dependencies (/)
* Move tests to *.test fragments? (x) see DIRSTUDIO-1021
* Use Luna (/)
* Migrate plugins (/)
* Migrate features (/)
* Migrate RCP application / product (/)
* Migrate help plugins (/)
* Installers (Windows EXE, Mac DMG) (x) see DIRSTUDIO-1022
* Generate P2 repository / site, self-hosted (x) see DIRSTUDIO-1023
* P2 repository for API and ApacheDS bundles? (x)
* Migrate release process (x) see DIRSTUDIO-1024
* Document build system (x) see DIRSTUDIO-1024
* Cleanup POMs: RAT plugin configuration (x) see DIRSTUDIO-1025
* Cleanup old "repository" folder (x) see DIRSTUDIO-1025

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? (x) see DIRSTUDIO-1021
* Use Luna (/)
* Migrate plugins (/)
* Migrate features (/)
* Migrate RCP application / product (/)
* 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? (x) see DIRSTUDIO-1021
> * Use Luna (/)
> * Migrate plugins (/)
> * Migrate features (/)
> * Migrate RCP application / product (/)
> * Migrate help plugins (/)
> * Installers (Windows EXE, Mac DMG) (x) see DIRSTUDIO-1022
> * Generate P2 repository / site, self-hosted (x) see DIRSTUDIO-1023
> * P2 repository for API and ApacheDS bundles? (x)
> * Migrate release process (x) see DIRSTUDIO-1024
> * Document build system (x) see DIRSTUDIO-1024
> * Cleanup POMs: RAT plugin configuration (x) see DIRSTUDIO-1025
> * Cleanup old "repository" folder (x) see DIRSTUDIO-1025
> 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)

Mime
View raw message