Maybe the answer to the questions below is somewhere in this mailing list
archive, but unfortunately I could not find the search link at
1) Do we have somewhere [Eclipse] formatting and code template settings.
These are the configurations that can be imported and exported after going
to Window -> Preferences, then Java/Code Style/Formatter. I see that most
of the code differs from Eclipse's defaults (spaces vs tabs and opening
brace on a new line to name a few)
2) I see that most of the tests are run with Arquillian. Do we have
somewhere configuration for this framework? I remember that I had to create
arquillian.xml in order to specify the target container by declaring a
namespace. Is my Aruillian knowledge too old (I admit that I checked it at
its 1.0.4.ALPHA version)? Actually which is our target container? Embedded
I'm developing a Spring MVC plugin for Forge that will generate a basic
web application from an entity, much like the current Scaffold plugin
(except using Spring MVC). Currently, I am working on creating JSP
views for listing all entities in the database, viewing a single entity,
as well as a create view. I see that ScaffoldPlugin uses a
StaticHtmlMetawidget (as well as MVEL, I believe, in the .xhtml files)
to configure and generate displays.
I am wondering if this class can be used for JSP as well, or if its
implementation is specific to JSF. If it cannot be used, is there
another, similar Metawidget class that can be used?
I'm relatively new to Forge. However, I want to get started with it and I
decided to add the smallest possible feature. So I found one candidate and
I'd like to get whether it is useful and at all correct.
Right now when you create new project you have to enter top level package.
And at the end you have src/main/java and src/test/java directories created
for you. But you don't have your top level package directories created. And
later when you try to add an entity or an ejb or any Java type, you have to
first create the packages even though you have specified them already. So
besides using the top level package as artifact ID in maven, I guess that
Forge can as well create it automatically. Both in the sources and in the
test directories. Do you think this is a useful feature or you left it out
If you think it's fine, here is my proposal for implementing it. I spent
last night debugging and hacking and I think I got how creating new
projects works ;-)
So, I plan to extend the JavaSourceFacet interface with a new
method: public DirectoryResource createTopLevelPackage(String
topLevelPackage). In its [only] implementation (MavenJavaSourceFacet) I
will use the existing machinery to create directories under the test and
source maven directories and will return the created folder. Finally, in
NewProjectPlugin I will call the new method with the top level package
coming from the shell. I have already prepared a unit test
in NewProjectPluginTest, which in the good old TDD traditions is failing
epicly at the moment, as the functionality is not in place :-)
To summarize, my questions here are not about the tiny technical details,
but rather on the need of such functionality and whether it is fine to
extend the JavaSourceFacet interface with such operation.
BTW If you say that we need this functionality, should I create JIRA issue
or an eventual pull request once you agree with my proposal will be enough?
I have a fairly simple question which, I hope, has a simple answer. Is
there a Facet or similar tool which can be used in a Forge plugin to
modify the project's packaging? For example, changing the type of
project from a .jar to a .war.
So, I've been back working on Forge Core -- scripting and internal API improvements. One thing that upset me was that Forge lacked a sub-buffering facility for console output, so you could intercept console output and do fun stuff like add a status bar. Well, Forge has this limitation no longer -- at least not in my branch (https://github.com/mikebrock/core)
Haven't pushed the changes upstream, mainly because I don't know if they break JBoss Tools or not -- pretty sure they don't break anything else.
Anyways, here's my first demo plugin that takes advantage of these new features in the shell API: https://github.com/mikebrock/core