[JBoss JIRA] Created: (SEAMFORGE-336) Need a way of supplying JARs to Plugins (e.g. Hibernate Tools)
by Lincoln Baxter III (JIRA)
Need a way of supplying JARs to Plugins (e.g. Hibernate Tools)
---------------------------------------------------------------
Key: SEAMFORGE-336
URL: https://issues.jboss.org/browse/SEAMFORGE-336
Project: Seam Forge
Issue Type: Feature Request
Components: Plugin API, Usability
Affects Versions: 1.0.0.Beta2
Reporter: Lincoln Baxter III
You could (in theory) add a JAR to the plugin module where it is installed:
.forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-***
and also add that jar as a resource in the module.xml file
.forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-***/modules.xml
That should do it, but it's not easy. This needs to be streamlined
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-379) Add user profiles
by Pete Muir (Created) (JIRA)
Add user profiles
-----------------
Key: FORGE-379
URL: https://issues.jboss.org/browse/FORGE-379
Project: Forge
Issue Type: Feature Request
Affects Versions: 1.0.0.Beta3
Reporter: Pete Muir
Assignee: Lincoln Baxter III
At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] Created: (SEAMFORGE-342) Get online help from plugin's javadoc
by Jonathan Fuerth (JIRA)
Get online help from plugin's javadoc
-------------------------------------
Key: SEAMFORGE-342
URL: https://issues.jboss.org/browse/SEAMFORGE-342
Project: Seam Forge
Issue Type: Feature Request
Components: Plugin API
Reporter: Jonathan Fuerth
Priority: Minor
IDEs already have lots of great tooling to help write good javadoc and keep it neatly formatted and up to date. It would be excellent if forge's source of help text for plugins came straight from the javadoc. This could be done either via a doclet that operates on the Java source code, or by scraping the output of the default doclet (like Eclipse will do if you attach generated JavaDoc rather than library source code).
Lowering the barrier to providing high-quality documentation should help encourage plugin authors to provide good help, and in turn that should help everyone pick up and learn Forge faster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct
by Pete Muir (Created) (JIRA)
Add "environments" as a first class construct
---------------------------------------------
Key: FORGE-378
URL: https://issues.jboss.org/browse/FORGE-378
Project: Forge
Issue Type: Feature Request
Reporter: Pete Muir
Assignee: Lincoln Baxter III
For example:
{code}
set environment JBOSS_AS7 --version 7.1.0.Final
{code}
Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7.
For example, the persistence plugin could read from this, changing
{code}
persistence setup --provider HIBERNATE --container JBOSS_AS7
{code}
to
{code}
persistence setup
{code}
Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use.
Lot's of other places where this could provide better defaulting, or remove the need to ask questions.
This also seems fairly consistent with the Forge approach - good understanding of the project in question.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding
by Richard Kennard (Created) (JIRA)
Return list of properties based on higher-level understanding
-------------------------------------------------------------
Key: FORGE-368
URL: https://issues.jboss.org/browse/FORGE-368
Project: Forge
Issue Type: Feature Request
Reporter: Richard Kennard
Assignee: Lincoln Baxter III
Hi guys,
As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say...
field string --named foo
...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do...
org.jboss.forge.parser.java.JavaClass.getMethods()
...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do...
org.jboss.forge.parser.java.JavaClass.getFields()
...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored).
Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter?
If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months