How to keep forge addons uptodate/in-sync to keep working together:
Not exactly sure what you mean here, but this is something we are still talking about. Right now we are using hard version numbers in POMs to ensure build stability, but I have been playing with the idea of actually using the thing nobody ever uses in Maven (version ranges) - now, before you try to kill me, I'm aware of the downsides, but am weighing the benefits since in a modular environment things are a bit different. We aren't really building JARs when we're building addons. We're building addons that happen to have a JAR or more. So thoughts are welcome on this.
Support a "multi-step wizard" approach for one and combined forge commands:
Would love your feedback on this API. And the Command Abstraction API as a whole. Note that this is just the developer facing API, there must be a corresponding implementation for the given GUI (Shell, Eclipse, Netbeans, Etc.)
How to not have too many hard requirements of the sequence or if possibly any need of Forge setup commands to use Forge to simply generate code:
If you want a plugin/addon that generates code without doing inspection, there's nothing in the way of this. Forge 2.0 caters very well to this scheme as well, since startup time is so fast and addons are extremely modular, you'll barely even notice a delay. To make things even better, we are playing with a mode where forge only loads addons requested by the specified command, then shuts down. This would mean you should be able to run Forge from the command line, and load only the addons necessary for the requested execution, or start Forge from the IDE, and have it load only the addons necessary to execute on the given wizard inputs.
One approach I had in mind here is if like Forge (at least in theory?) could be made to support Gradle and the plugins would still work - could we get Forge to grok Eclipse Projects natively
On 20 Dec 2012, at 11:47, Max Rydahl Andersen <max.andersen@redhat.com> wrote:
> The primary usecase for Forge from my POV is being able to reuse scaffolding and code generation as a replacement of Seam Gen functionality we have in Eclipse and
> right now Forge is not there yet and I fear it won't be there within the next 1-2 months where we actually need to make progress on scaffolding and generation for things like
> HTML5 and more. I'm wondering if we need to readjust our approach to how we use forge and its addons - maybe the "old" approach of sharing code/templates is a better one
> instead of requiring a full running Forge to make it work ?
and just rely on already loaded and ready project information inside Eclipse ?
Things like dependency management would have to be delegated to the real maven or gradle or whatever in play here but I think in majority of cases for code generation this step is
just a one-off thus not necessary to do.
WDYT ?
/max
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev