Details
-
Type:
Enhancement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 0.2
-
Fix Version/s: 0.3
-
Component/s: tooling
-
Labels:None
Description
We need to upgrade our tooling to Forge Beta 3. Talking to Lincoln, there are going to be some changes in terms of how we package our plugins and possibly API changes as well. There are two parts to this JIRA:
1) Our plugins need to work with Beta 3, so any changes it takes to make things work the same. This includes the ability to install plugins from our distribution into an existing Forge install.
2) Add support for the ability to install plugins from a Git repository and add our plugins to the Forge CPI.
Here's some background info on #2.
https://docs.jboss.org/author/display/SEAMFORGE/Make+your+Plugin+available+to+Forge
https://docs.jboss.org/author/display/SEAMFORGE/Add+your+Plugin+to+the+Central+Plugin+Index+%28CPI%29
Please note that I want to continue to support the existing process (copy Forge plugins to $FORGE_HOME/lib) as closely as possible. I don't want users that have already downloaded our distribution to have to then install all of the plugins from a remote Git repo as well (this involves more downloading and building).
Gliffy Diagrams
Issue Links
- blocks
-
SWITCHYARD-509
Add @SetupCommand to forge plugins
-
- Open
-
-
SWITCHYARD-508
Make switchyard-forge-plugin build from source-plugin
-
- Closed
-
- relates to
-
SWITCHYARD-524
Move the template resources to the same package as caller class in bean service
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
It looks like we are good to go with Beta 3 now. Tom - if there's something I missed, feel free to reopen this JIRA.