[forge-dev] [JBoss JIRA] Closed: (SEAMFORGE-85) Forge should support dynamic loading of plugin library dependencies

Lincoln Baxter III (JIRA) jira-events at lists.jboss.org
Thu Aug 4 11:50:27 EDT 2011

     [ https://issues.jboss.org/browse/SEAMFORGE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lincoln Baxter III closed SEAMFORGE-85.

    Fix Version/s: 1.0.0.Beta1
       Resolution: Done

This has been resolved by integrating maven and jboss modules into the forge plugin installation process. Currently supported are Git hosted plugins, and plugins installed directly from source code.

> Forge should support dynamic loading of plugin library dependencies
> -------------------------------------------------------------------
>                 Key: SEAMFORGE-85
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-85
>             Project: Seam Forge
>          Issue Type: Feature Request
>          Components: Plugin API
>    Affects Versions: 1.0.0.Alpha2
>            Reporter: Lincoln Baxter III
>            Assignee: Lincoln Baxter III
>             Fix For: 1.0.0.Beta1
> Right now, Forge extensions must use the maven shade-plugin to package referenced dependencies of plugins. It would greatly enhance developer experience if referenced plugins or libraries could be dynamically loaded from the local maven repository, even if built with Git.
> A META-INF/dependencies file could be used to list runtime dependencies of the plugin. Or the POM files of each plugin (META-INF/pom...) could be scanned and parsed to determine required libs.
> A third option, programmatic declaration of runtime dependencies might also be an option if it can be worked into Java from Groovy: http://groovy.codehaus.org/Grape
> Benefits of these approaches are:
> * Reduced size deliverable ZIPfile
> * ...

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the forge-dev mailing list