[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-80) Configurable classpaths for Forge

Dan Allen (JIRA) jira-events at lists.jboss.org
Mon Mar 21 19:25:45 EDT 2011

    [ https://issues.jboss.org/browse/SEAMFORGE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589492#comment-12589492 ] 

Dan Allen commented on SEAMFORGE-80:

Perhaps instead of bundling the artifacts, there should be a dependency file that forge will use to resolve artifacts from the Maven repository. This is sort of along the line of Groovy grapes.


> Configurable classpaths for Forge
> ---------------------------------
>                 Key: SEAMFORGE-80
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-80
>             Project: Seam Forge
>          Issue Type: Feature Request
>            Reporter: Shane Bryzak
> Currently Forge automatically scans the lib folder for libraries, however in the Seam bundled distribution there are also separate primary module libraries contained in the artifacts folder, which may be required by Forge.  Directory structure looks something like this:
> /seam-3.0.0.CR3
>    /artifacts
>       seam-catch.jar
>       seam-faces.jar
>       seam-solder.jar
>       (etc)
>    /forge
>       forge
>       forge.bat
>    /lib
>       (all other libraries)
> It would be nice to be able to configure additional locations for Forge to scan.  One suggestion for doing this might be to allow a file called forgeclasspath.conf in the /forge directory, which the forge bootstrap can read to determine other paths to scan.

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