[JBoss JIRA] (FORGE-565) Persistence plugin needs to better guide users through a custom database configuration
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-565?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-565.
---------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha11
(was: 1.x Future)
Resolution: Done
This is implemented using wizards in Forge 2
> Persistence plugin needs to better guide users through a custom database configuration
> --------------------------------------------------------------------------------------
>
> Key: FORGE-565
> URL: https://issues.jboss.org/browse/FORGE-565
> Project: Forge
> Issue Type: Enhancement
> Components: Builtin Plugins
> Affects Versions: 1.0.4.Final
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Priority: Minor
> Labels: Starter
> Fix For: 2.0.0.Alpha11
>
>
> In order to use the PostgreSQL (or any custom) database, you'll need to skip the --container JBOSS_AS7 parameter; otherwise, this will override the data-source configuration as seen in the INFO messages:
> {code}***INFO*** Setting transaction-type="JTA"
> ***INFO*** Using example data source [java:jboss/datasources/ExampleDS]{code}
> We should probably make this more clear, or perhaps create a warning or error scenario instead of INFO. When you remove the --container parameter.
> It should be much clearer that you may need to use some of the extended parameters like --jndiName and so forth.
> This can probably be done by updating the PersistencePlugin and related classes:
> https://github.com/forge/core/blob/master/javaee-impl/src/main/java/org/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (FORGE-1127) Refactor Files out of Furnace impl to Furnace API
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1127:
--------------------------------------
Summary: Refactor Files out of Furnace impl to Furnace API
Key: FORGE-1127
URL: https://issues.jboss.org/browse/FORGE-1127
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container)
Affects Versions: 2.0.0.Alpha10
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.0.0.Alpha11
org.jboss.forge.furnace.impl.util.Files should be deprecated in favor of the class in the API module
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (FORGE-926) It should be : maxlength instead of maxLength
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-926?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-926:
----------------------------------
Fix Version/s: 1.x Future
(was: 1.4.0.Final)
> It should be : maxlength instead of maxLength
> ---------------------------------------------
>
> Key: FORGE-926
> URL: https://issues.jboss.org/browse/FORGE-926
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.2.0.Final, 1.2.1.Final, 1.2.2.Final, 1.3.0.Final
> Environment: Any
> Reporter: Hanine Hanynowsky
> Assignee: Vineet Reynolds
> Priority: Minor
> Fix For: 1.x Future
>
>
> The JBoss Forge UI scaffold uses maxLength as the attribute name instead of maxlength, when generating <h:inpuText /> components, in .xhtml files.
> So this is a typo error (capital L instead of a lowercase l).
> People using Eclipse or JBoss developer might notice it since, these IDEs do not complain about it. If you use Netbeans or IntelliJidea, you would be prompted to correct the error.
> This has no critical consequences so far, but should be changed to correct name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months