Plugin is only a problem because we're now talking about normal plugins and "uber" / ageration plugins. So what about calling plugins that aggregate other plugins (such as the proposed Seam3 plugin) PluginPack?PaulOn Fri, May 27, 2011 at 8:31 AM, Koen Aers <koen.aers@gmail.com> wrote:
In the Eclipse ecosystem such addons are called fragments.But then I don't know if we want to add to the overload of Eclipse nomenclature... ;-)Regards,Koen
On Thu, May 26, 2011 at 7:34 PM, Jason Porter <lightguard.jp@gmail.com> wrote:
I like extension, because it's extending what's there, but naming
conflicts arise with both Addon and Extension :( ExtensionPack maybe
or similar?
--
On Thursday, May 26, 2011, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:
> " Keep the Seam plugins small and
> isolated, yet have a single plugin that is used"
>
> I think we need a new name for "Plugin"... we might have to use "Addon"
> or "Extension" to refer to the bundle that may or may not contain an
> actual org.jboss.forge.plugins.Plugin
>
> Thoughts?
> ~Lincoln
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
>
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev