[
https://issues.apache.org/jira/browse/FELIX-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage updated FELIX-1355:
--------------------------------
Assignee: David Savage
Fix Version/s: sigil-1.0.0
> Provide common mechanism to configure repositories between server side build
> and eclipse integration
> ----------------------------------------------------------------------------------------------------
>
> Key: FELIX-1355
> URL: https://issues.apache.org/jira/browse/FELIX-1355
> Project: Felix
> Issue Type: Improvement
> Components: Sigil
> Reporter: David Savage
> Assignee: David Savage
> Fix For: sigil-1.0.0
>
>
> Sigil provides an API to configure resolvers to locate OSGi dependencies
> however the ivy build and eclipse build look in different places to find out
> which resolvers are enabled for a particular project.
> * The ivy build uses a properties file format that can be shared by nested
> sub projects
> * The eclipse build uses eclipse preferences to configure workspace specific
> configuration
> This involves duplication of effort on the part of developers using sigil.
> The shared properties file format is generally preferred as it enables
> checkin to version control mechanisms such as cvs, svn, git, etc also it
> reduces duplication of information at leaf nodes.
> The problem for the eclipse side of things is that eclipse has no notion of
> nested projects so if you were to import projects from different top level
> projects it is not intuitive to the developer which settings they are
> editting and whether edits will effect other projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
