Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frascati
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 114
    • Issues 114
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • frascatifrascati
  • frascati
  • Issues
  • #15
Closed
Open
Issue created May 10, 2011 by Romain Rouvoy@rouvoyDeveloper

Reflecting FraSCAti modules as OSGi bundles

OSGi defines a standard packaging mechanism, which can be used to better isolate the loading of software modules within a standard Java Runtime Environment. FraSCAti «à la carte» could benefit from this mechanism to better control the loaded modules as well as their dependencies.

It would therefore be nice to consider the definition of OSGi-compliant manifest files for the module of the platform. Existing tools, such as BND [1] or Tycho [2] could facilitate this task by generating the manifest file from the Maven configuration file.

References

  1. BND. http://www.aqute.biz/Code/Bnd
  2. Tycho. http://tycho.sonatype.org

Romain Rouvoy

Assignee
Assign to
Time tracking