[JBoss JIRA] (FORGE-1944) Create Junit commands
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1944?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1944:
------------------------------------------
Some ideas of command :
{code}
// Sets up JUnit
junit-setup --junitVersion
// Creates a new test case
junit-new-test --named TheClassNameTest
// Adds a new test to a test case
junit-add-test --named theMethodName --targetClass TheClassNameTes
// Generates a test case for a given class (generates one test per public method)
junit-create-test --targets TheClassToGenerateTests
...
{code}
> Create Junit commands
> ---------------------
>
> Key: FORGE-1944
> URL: https://issues.jboss.org/browse/FORGE-1944
> Project: Forge
> Issue Type: Feature Request
> Components: Developer Tools - Java
> Affects Versions: 2.7.0.Final
> Reporter: George Gastaldi
> Assignee: Ivan St. Ivanov
> Labels: Starter
> Fix For: 2.x Future
>
>
> Create a command to create a JUnit test case and setup Junit in a project
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FURNACE-69) Allow EventListeners to be registered as Services or SingletonServices
by George Gastaldi (JIRA)
George Gastaldi created FURNACE-69:
--------------------------------------
Summary: Allow EventListeners to be registered as Services or SingletonServices
Key: FURNACE-69
URL: https://issues.jboss.org/browse/FURNACE-69
Project: Forge: Furnace
Issue Type: Feature Request
Components: Container - Simple
Affects Versions: 2.20.1.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.20.2.Final
Simple container should allow {{EventListener}} implementations to be implemented as a {{Service}} or a {{SingletonService}} in addons using the simple container.
This is needed to allow singleton services to listen for {{PostStartup}} and {{PreShutdown}} events, for example
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (ROASTER-75) Encoding of source[?] code cannot be easily configured.
by Anonymous (JIRA)
[ https://issues.jboss.org/browse/ROASTER-75?page=com.atlassian.jira.plugin... ]
Issue was automatically transitioned when kuzukami.sh created pull request #40 in GitHub
----------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Encoding of source[?] code cannot be easily configured.
> -------------------------------------------------------
>
> Key: ROASTER-75
> URL: https://issues.jboss.org/browse/ROASTER-75
> Project: Roaster
> Issue Type: Enhancement
> Components: API, JDT
> Affects Versions: 2.14.0.Final, 2.15.0.Final
> Environment: Java 8 64bit, Eclipse Mars, Windows 8.1 Pro 64bit
> Reporter: Shoji Kuzukami
> Priority: Minor
> Fix For: 2.x Future
>
>
> The parser encoding for souce code can only be configured by the 'file.encoding' system parameter, as we can see in JavaParserImpl, "String encoding = System.getProperty("file.encoding", "ISO8859_1");".
> Even though the Roaster API can receive a 'String' source as "public static JavaType<?> parse(final String data)" in the 'Roaster.java', the 'String' of source can only contain "ISO8859_1" charsets if we don't change the "file.encoding".
> The parser SPI in 'JavaParser.java' is defined as "JavaUnit parseUnit(final InputStream data);" instead of "JavaUnit parseUnit(Reader source);". I think it is adequate considering that the Roaster API will accept some binary sources (such as bytecode) in near future.
> I recommend that the SPI "JavaUnit parseUnit(final InputStream data);" is expanded into "JavaUnit parseUnit(final InputStream data, Charset encodingIfText );" and some encoding refactors are done in the 'Roaster.java' without any change of semantics in the Roaster APIs except for the 'String' souce APIs as "public static JavaType<?> parse(final String data)".
> The 'Charset' argument is used only if the 'data' of InputStream must be interpreted as 'String' ( as a case of source code ).
> If this idea is accepted by this project design, I'll refactor the code and do a pull-requeust.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2419) Refactoring the JSF Commands
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2419?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2419:
-------------------------------------
Description:
Today the JSF methods {{FacesNewBeanCommand}}, {{FacesNewConverterCommand}} and {{FacesNewValidatorCommand}} use templating.
For the little amount of code that is generated, it would be better to use Roaster instead. And in the refactoring process, add some tests.
Today the JSF commands have the following hierarchy :
{code}
AbstractUICommand implements UICommand
AbstractProjectCommand
AbstractJavaEECommand
AbstractFacesCommand implements PrerequisiteCommandsProvider
FacesNewBeanCommand implements PrerequisiteCommandsProvider
FacesNewConverterCommand
FacesNewValidatorCommand
{code}
But most of the other Java EE commands extend {{AbstractJavaSourceCommand}} and not {{AbstractJavaEECommand}}
{code}
AbstractUICommand implements UICommand
AbstractProjectCommand
AbstractJavaSourceCommand<SOURCETYPE extends JavaSource<?>>
AbstractCDICommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
CDINewBeanCommand
CDINewDecoratorCommand
CDINewExtensionCommand
AbstractJPACommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
JPANewEntityCommand
JPANewEntityListenerCommand
JPANewMappedSuperclassCommand
AbstractServletNewCommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
ServletNewServletCommand
ServletNewFilterCommand
{code}
was:
Today the JSF methods {{FacesNewBeanCommand}}, {{FacesNewConverterCommand}} and {{FacesNewValidatorCommand}} use templating.
For the little amount of code that is generated, it would be better to use Roaster instead. And in the refactoring process, add some tests.
> Refactoring the JSF Commands
> ----------------------------
>
> Key: FORGE-2419
> URL: https://issues.jboss.org/browse/FORGE-2419
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.17.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Today the JSF methods {{FacesNewBeanCommand}}, {{FacesNewConverterCommand}} and {{FacesNewValidatorCommand}} use templating.
> For the little amount of code that is generated, it would be better to use Roaster instead. And in the refactoring process, add some tests.
> Today the JSF commands have the following hierarchy :
> {code}
> AbstractUICommand implements UICommand
> AbstractProjectCommand
> AbstractJavaEECommand
> AbstractFacesCommand implements PrerequisiteCommandsProvider
> FacesNewBeanCommand implements PrerequisiteCommandsProvider
> FacesNewConverterCommand
> FacesNewValidatorCommand
> {code}
> But most of the other Java EE commands extend {{AbstractJavaSourceCommand}} and not {{AbstractJavaEECommand}}
> {code}
> AbstractUICommand implements UICommand
> AbstractProjectCommand
> AbstractJavaSourceCommand<SOURCETYPE extends JavaSource<?>>
> AbstractCDICommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
> CDINewBeanCommand
> CDINewDecoratorCommand
> CDINewExtensionCommand
> AbstractJPACommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
> JPANewEntityCommand
> JPANewEntityListenerCommand
> JPANewMappedSuperclassCommand
> AbstractServletNewCommand<T extends JavaSource<?>> implements PrerequisiteCommandsProvider
> ServletNewServletCommand
> ServletNewFilterCommand
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2162) Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2162?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2162.
----------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Cannot Reproduce Bug
Closing it as cannot reproduce
> Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
> --------------------------------------------------------------------
>
> Key: FORGE-2162
> URL: https://issues.jboss.org/browse/FORGE-2162
> Project: Forge
> Issue Type: Bug
> Components: Database Tools
> Affects Versions: 2.12.0.Final, 2.12.3.Final
> Environment: Windows 7, JDK7, Jboss AS7 and Wildfly 8.1
> Reporter: Gerry Matte
> Attachments: config.xml, config.xml.saved
>
>
> The following two JIRA requests have now returned as bugs.
> FORGE-1984 : jpa-generate-entities-from-tables add parameter to select all tables without prompting (fixed in version 2.8.1)
> FORGE-1990 : connection-create-profile fails to retain the database connection password (fixed in version 2.9.2.Final)
> As noted in https://developer.jboss.org/message/912189#912189 forum posting, the successful commands to create a connectionProfile and generate jpa entities from a mysql databse worked without problems in version 2.10.0.Final
> On Dec 2, Bruce Link reported problems implementing commands identical to mine but using forge 2.12.0.Final.
> Repeating my own commands that were previously successful, I now encountered the same two errors that were previously fixed by the above two JIRAs.
> I tested with both 2.12.0.Final and with 2.12.3.Final. Both versions failed to retain the database user password and also failed select all database tables (although the connection failure may have triggered the second error message)
> Please reimplement the changes made with FORGE-1984 and FORGE-1990. I am happy to retest when you are ready.
> Gerry Matte
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2162) Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
by fname lname (JIRA)
[ https://issues.jboss.org/browse/FORGE-2162?page=com.atlassian.jira.plugin... ]
fname lname edited comment on FORGE-2162 at 8/8/15 2:09 PM:
------------------------------------------------------------
I had the same issue.
Finally it works:
removed ~/.forge
For connection I've used both: connectionProfilePassword and userPassword.
Here is it:
{code}$ connection-create-profile --name con --hibernateDialect org.hibernate.dialect.PostgreSQLDialect --driverClass org.postgresql.Driver --driverLocation postgresql-9.4-1201.jdbc41.jar --userName name --connectionProfilePassword password --saveUserPassword --userPassword password --jdbcUrl jdbc:postgresql://localhost:5432/db --verifyConnection{code}
was (Author: yaroska):
I had the same issue.
Finally it works:
removed ~/.forge
For connection I've used both: connectionProfilePassword and userPassword.
Here is it:
$ connection-create-profile --name con --hibernateDialect org.hibernate.dialect.PostgreSQLDialect --driverClass org.postgresql.Driver --driverLocation postgresql-9.4-1201.jdbc41.jar --userName name --connectionProfilePassword password --saveUserPassword --userPassword password --jdbcUrl jdbc:postgresql://localhost:5432/db --verifyConnection
> Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
> --------------------------------------------------------------------
>
> Key: FORGE-2162
> URL: https://issues.jboss.org/browse/FORGE-2162
> Project: Forge
> Issue Type: Bug
> Components: Database Tools
> Affects Versions: 2.12.0.Final, 2.12.3.Final
> Environment: Windows 7, JDK7, Jboss AS7 and Wildfly 8.1
> Reporter: Gerry Matte
> Fix For: 2.x Future
>
> Attachments: config.xml, config.xml.saved
>
>
> The following two JIRA requests have now returned as bugs.
> FORGE-1984 : jpa-generate-entities-from-tables add parameter to select all tables without prompting (fixed in version 2.8.1)
> FORGE-1990 : connection-create-profile fails to retain the database connection password (fixed in version 2.9.2.Final)
> As noted in https://developer.jboss.org/message/912189#912189 forum posting, the successful commands to create a connectionProfile and generate jpa entities from a mysql databse worked without problems in version 2.10.0.Final
> On Dec 2, Bruce Link reported problems implementing commands identical to mine but using forge 2.12.0.Final.
> Repeating my own commands that were previously successful, I now encountered the same two errors that were previously fixed by the above two JIRAs.
> I tested with both 2.12.0.Final and with 2.12.3.Final. Both versions failed to retain the database user password and also failed select all database tables (although the connection failure may have triggered the second error message)
> Please reimplement the changes made with FORGE-1984 and FORGE-1990. I am happy to retest when you are ready.
> Gerry Matte
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2162) Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
by fname lname (JIRA)
[ https://issues.jboss.org/browse/FORGE-2162?page=com.atlassian.jira.plugin... ]
fname lname commented on FORGE-2162:
------------------------------------
I had the same issue.
Finally it works:
removed ~/.forge
For connection I've used both: connectionProfilePassword and userPassword.
Here is it:
$ connection-create-profile --name con --hibernateDialect org.hibernate.dialect.PostgreSQLDialect --driverClass org.postgresql.Driver --driverLocation postgresql-9.4-1201.jdbc41.jar --userName name --connectionProfilePassword password --saveUserPassword --userPassword password --jdbcUrl jdbc:postgresql://localhost:5432/db --verifyConnection
> Two previous JIRA changes have been undone FORGE-1984 and FORGE-1990
> --------------------------------------------------------------------
>
> Key: FORGE-2162
> URL: https://issues.jboss.org/browse/FORGE-2162
> Project: Forge
> Issue Type: Bug
> Components: Database Tools
> Affects Versions: 2.12.0.Final, 2.12.3.Final
> Environment: Windows 7, JDK7, Jboss AS7 and Wildfly 8.1
> Reporter: Gerry Matte
> Fix For: 2.x Future
>
> Attachments: config.xml, config.xml.saved
>
>
> The following two JIRA requests have now returned as bugs.
> FORGE-1984 : jpa-generate-entities-from-tables add parameter to select all tables without prompting (fixed in version 2.8.1)
> FORGE-1990 : connection-create-profile fails to retain the database connection password (fixed in version 2.9.2.Final)
> As noted in https://developer.jboss.org/message/912189#912189 forum posting, the successful commands to create a connectionProfile and generate jpa entities from a mysql databse worked without problems in version 2.10.0.Final
> On Dec 2, Bruce Link reported problems implementing commands identical to mine but using forge 2.12.0.Final.
> Repeating my own commands that were previously successful, I now encountered the same two errors that were previously fixed by the above two JIRAs.
> I tested with both 2.12.0.Final and with 2.12.3.Final. Both versions failed to retain the database user password and also failed select all database tables (although the connection failure may have triggered the second error message)
> Please reimplement the changes made with FORGE-1984 and FORGE-1990. I am happy to retest when you are ready.
> Gerry Matte
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months