[JBoss JIRA] (FORGE-782) Forge should support multiple repositories
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-782?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III closed FORGE-782.
------------------------------------
Fix Version/s: 2.0.0.Alpha2
(was: 1.2.3.Final)
Resolution: Done
Fixed in Forge 2
> Forge should support multiple repositories
> ------------------------------------------
>
> Key: FORGE-782
> URL: https://issues.jboss.org/browse/FORGE-782
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin Repository
> Affects Versions: 1.2.0.Final
> Reporter: John Ament
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Alpha2
>
>
> Forge currently has a DEFAULT_PLUGIN_REPO but no way to have additional plugin repos. It should be possible for companies to have internal repositories for plugins that may not be open source.
> Workaround right now is to copy the yaml file locally and add other proprietary plugins to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-782) Forge should support multiple repositories
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-782?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-782:
----------------------------------------
Assignee: Lincoln Baxter III
> Forge should support multiple repositories
> ------------------------------------------
>
> Key: FORGE-782
> URL: https://issues.jboss.org/browse/FORGE-782
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin Repository
> Affects Versions: 1.2.0.Final
> Reporter: John Ament
> Assignee: Lincoln Baxter III
> Fix For: 1.2.3.Final
>
>
> Forge currently has a DEFAULT_PLUGIN_REPO but no way to have additional plugin repos. It should be possible for companies to have internal repositories for plugins that may not be open source.
> Workaround right now is to copy the yaml file locally and add other proprietary plugins to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-563) Create a class lookup index
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-563:
----------------------------------------
Assignee: George Gastaldi (was: Lincoln Baxter III)
> Create a class lookup index
> ---------------------------
>
> Key: FORGE-563
> URL: https://issues.jboss.org/browse/FORGE-563
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration
> Affects Versions: 1.0.4.Final
> Reporter: Jason Porter
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha2
>
>
> We need to support an index of classes and dependencies which contain them.
> This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc.
> We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-563) Create a class lookup index
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-563:
----------------------------------------
Assignee: Lincoln Baxter III
> Create a class lookup index
> ---------------------------
>
> Key: FORGE-563
> URL: https://issues.jboss.org/browse/FORGE-563
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration
> Affects Versions: 1.0.4.Final
> Reporter: Jason Porter
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Alpha2
>
>
> We need to support an index of classes and dependencies which contain them.
> This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc.
> We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months