Details
-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: 1.0.0.Alpha1
-
Fix Version/s: 2.0.0.Alpha1
-
Component/s: Brainstorming, Plugin API
-
Labels:
-
Environment:All
Description
There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven.
Features Forge would need to provide:
1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity
------------------------------------------------------------------------------------------
$ forge plugin-find prettyfaces
Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts.
- http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1]
- http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0
$ forge plugin-install prettyfaces --version 3.1.0
**SUCCESS** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes.
$ forge plugin-list
Listing installed plugins:
- prettyfaces [3.1.0]
- forge-scaffold [1.0.0.Alpha1]
- forge-javaee6 [1.0.0.Alpha1]
- home-control [1.0.0.Alpha1]
$ forge plugin-remove prettyfaces
Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y
**SUCCESS** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes.
------------------------------------------------------------------------------------------
2) Plugin repository management (add/remove/edit/list current plugin repository targets.)
------------------------------------------------------------------------------------------
$ forge repo-list
Currently using the following plugin repositories:
- 1. https://repository.jboss.org/nexus/content/groups/public/
- 2. http://ocpsoft.com/repository
- 3. http://example.com/forge/plugin-repository
$ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen
$ forge repo-add http://javaee.org/forge/repository/
$ forge repo-list
Currently using the following plugin repositories:
- 1. https://repository.jboss.org/nexus/content/groups/public/
- 2. http://ocpsoft.com/repository
- 3. http://example.com/forge/plugin-repository
- 4. http://jboss.org/forge/repository/
- 5. http://javaee.org/forge/repository/
$ forge repo-del 5
**SUCCESS** removed repository http://javaee.org/forge/repository/. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove
{plugin-id}]
------------------------------------------------------------------------------------------
3) Auto-update functionality
Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins.
4) A meta-data system of identifying compatible versions of plugins w/running version of forge.
Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven.
Gliffy Diagrams
Issue Links
- is blocked by
-
FORGE-174
Ability to build/load/install plugins from the local filesystem, and from remote URLs
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
This has been partially implemented via:
$ forge find-plugin *
|
$ forge insall-plugin theplugin
|
https://raw.github.com/forge/plugin-repository/master/repository.yaml
We still need a way of automating the repository management tasks, and providing alternate repositories.
We can open additional issues for enhancements.
Lincoln Baxter III
added a comment - This has been partially implemented via:
$ forge find-plugin *
$ forge insall-plugin theplugin
https://raw.github.com/forge/plugin-repository/master/repository.yaml
We still need a way of automating the repository management tasks, and providing alternate repositories.
We can open additional issues for enhancements. As discussed in IRC channel with development team, to provide a forge plugin is required git as project repository, and to publish in a intranet needs a new repository.yaml file. It would be nice if we have a decentralized repository system, that doesn't depends on the project repository, opening possibilities to SVN, for example. I think the best solution is to delegate all of the artifact resolution and dependency management to Maven, as mentioned in this thread.
Alceu Medeiros
added a comment - As discussed in IRC channel with development team, to provide a forge plugin is required git as project repository, and to publish in a intranet needs a new repository.yaml file. It would be nice if we have a decentralized repository system, that doesn't depends on the project repository, opening possibilities to SVN, for example. I think the best solution is to delegate all of the artifact resolution and dependency management to Maven, as mentioned in this thread. Hey Alceu, in case I have forgotten, are you interested in developing the Maven plugin installation feature?
Lincoln Baxter III
added a comment - Hey Alceu, in case I have forgotten, are you interested in developing the Maven plugin installation feature? I can assign this issue to you if that's the case!
Lincoln Baxter III
added a comment - I can assign this issue to you if that's the case! This has been solved via Furnace Manager. The Repository will be implemented as part of the Forge 2 website launch.
Lincoln Baxter III
added a comment - This has been solved via Furnace Manager. The Repository will be implemented as part of the Forge 2 website launch. 
I think this would be a great addition, and another significant step in distancing Seam Forge from is competitors. With respect to 'the value of this type of feature', I would like to emphasise the 'search' aspect of 'search/install/remove/update': discoverability is important.
So it would be good to define a description for each plugin, and why I should download it, and maybe which companies provide (commerical) support for it (as an incentive for companies to produce Seam Forge plugins). And this description should be searchable. So that I could search for, say, 'validation' and see plugins for Hibernate Validator, Bean Validation, OVaL, Commons Validator, JGoodies Validator etc.