https://issues.jboss.org/browse/SEAMFORGE-196 Everyone on this list has access, but if you need it I can add you: - LightGuard <https://github.com/LightGuard> - aslakknutsen <https://github.com/aslakknutsen> - balunasj <https://github.com/balunasj> - bleathem <https://github.com/bleathem> - gastaldi <https://github.com/gastaldi> - johnament <https://github.com/johnament> - kenfinnigan <https://github.com/kenfinnigan> - lincolnthree <https://github.com/lincolnthree> - mojavelinux <https://github.com/mojavelinux> - paulbakker <https://github.com/paulbakker> - sbryzak <https://github.com/sbryzak> -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Ah, did I miss that? That's fine. Just let me know what you guys want. On Tue, May 31, 2011 at 1:28 PM, Paul Bakker <paul.bakker.nl(a)gmail.com&gt;wrote: > As far I've seen on the replies on the mailinglist I think the consensus > was to keep all the plugins separated and create a "super" plugin that can > install all others. So what shall we decide on this? I can pick this up > whenever we make a choice :-) > > Paul > > > On Tue, May 31, 2011 at 7:18 PM, Lincoln Baxter, III < > lincolnbaxter(a)gmail.com&gt; wrote: > >> https://issues.jboss.org/browse/SEAMFORGE-196 >> >> Everyone on this list has access, but if you need it I can add you: >> >> - LightGuard <https://github.com/LightGuard> >> - aslakknutsen <https://github.com/aslakknutsen> >> - balunasj <https://github.com/balunasj> >> - bleathem <https://github.com/bleathem> >> - gastaldi <https://github.com/gastaldi> >> - johnament <https://github.com/johnament> >> - kenfinnigan <https://github.com/kenfinnigan> >> - lincolnthree <https://github.com/lincolnthree> >> - mojavelinux <https://github.com/mojavelinux> >> - paulbakker <https://github.com/paulbakker> >> - sbryzak <https://github.com/sbryzak> >> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.com >> http://scrumshark.com >> "Keep it Simple" >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

+1 On 05/31/2011 01:54 PM, Paul Bakker wrote: > I would like to prototype a PluginPackage (one of the names we > discussed) and see how that works out. If we like that way we can keep > the plugins separated, otherwise we can re-consider. Shall I assign > the JIRA issue to myself? > > Paul _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

I think I've got a very simple solution for this working, have a look at this branch: https://github.com/paulbakker/core/commits/plugin-repo It's a new plugin, I added it to the core for now, and believe it belongs there. The plugin does nothing else than parse a remote xml file. The xml file looks as follows: <plugin> <name>Arquillian</name> <url>git://github.com/forge/plugin-arquillian.git</url> </plugin> <plugin> <name>OSGI</name> <url>git://github.com/forge/plugin-osgi.git</url> </plugin> It will than prompt the user: Which plugin do you want to install: 1 - [OSGI] 2 - [Arquillian] 3 - [Seam Persistence] After the user chooses a plugin it will install the plugin by executing "forge git-plugin [url]" If we add this to the core and keep the xml external a user is always able to install known plugins easily. New plugnis can be added to the xml file without rebuilding the source. If we go forward with this idea we can also add things like automatic updates for example. Thoughs? Paul On Sat, Jun 4, 2011 at 7:46 AM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; wrote: +1, let's see how it goes :) definitely open to options. On Tue, May 31, 2011 at 5:02 PM, Brian Leathem <bleathem(a)gmail.com&gt; wrote: +1 On 05/31/2011 01:54 PM, Paul Bakker wrote: > I would like to prototype a PluginPackage (one of the names we > discussed) and see how that works out. If we like that way we can keep > the plugins separated, otherwise we can re-consider. Shall I assign > the JIRA issue to myself? > > Paul _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev