[
https://issues.apache.org/jira/browse/DIRSTUDIO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142386#comment-14142386
]
Stefan Seelmann commented on DIRSTUDIO-995:
-------------------------------------------
I'd use Require-Bundle instead of Import-Package for all the ApacheDS
dependencies because we need to specify the exact version and normally we need
more than one package, then it is easier to use Require-Bundle.
For versions in manifest make sure to use the right format, For the API e.g.
1.0.0.M24 (note the dot before M24, a dash is not allowed at this position) or
2.0.0.M17 for ApacheDS.
Maybe try to import the plugin into your Eclipse workspace, there may be
other/better error indicators. Otherwise just commit your changes and I'll have
a look to the whole picture.
> 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
> ** 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)
