[JBoss JIRA] (FORGE-1229) Addon packaging of should be POM instead of JAR in the complex layout
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1229:
--------------------------------------
Summary: Addon packaging of should be POM instead of JAR in the complex layout
Key: FORGE-1229
URL: https://issues.jboss.org/browse/FORGE-1229
Project: Forge
Issue Type: Enhancement
Components: Brainstorming
Affects Versions: 2.0.0.Alpha12
Reporter: George Gastaldi
Priority: Minor
Fix For: 2.x Future
This is actually something we should think about.
In the complex layout structure, the addon project should not contain any java class, and the maven-jar-plugin configuration still creates a forge-addon jar when the classifier is specified in the pom.xml.
--
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
10 years, 7 months
[JBoss JIRA] (FORGE-1229) Addon packaging should be POM instead of JAR in the complex layout
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1229?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1229:
-----------------------------------
Summary: Addon packaging should be POM instead of JAR in the complex layout (was: Addon packaging of should be POM instead of JAR in the complex layout)
> Addon packaging should be POM instead of JAR in the complex layout
> ------------------------------------------------------------------
>
> Key: FORGE-1229
> URL: https://issues.jboss.org/browse/FORGE-1229
> Project: Forge
> Issue Type: Enhancement
> Components: Brainstorming
> Affects Versions: 2.0.0.Alpha12
> Reporter: George Gastaldi
> Priority: Minor
> Fix For: 2.x Future
>
>
> This is actually something we should think about.
> In the complex layout structure, the addon project should not contain any java class, and the maven-jar-plugin configuration still creates a forge-addon jar when the classifier is specified in the pom.xml.
--
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
10 years, 7 months
[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1228:
----------------------------------------
Fancy a pull request? That would speed up the resolution of this issue and most likely ensure that the fix is available in 1.4.2.Final.
> increase conversation timeout to 30 minutes
> -------------------------------------------
>
> Key: FORGE-1228
> URL: https://issues.jboss.org/browse/FORGE-1228
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.4.1.Final
> Reporter: Gerry Matte
> Priority: Minor
>
> The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods]
> After each conversation.begin() please insert:
> this.conversation.setTimeout(1800000);
> which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout)
> For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating !
--
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
10 years, 7 months
[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes
by Gerry Matte (JIRA)
Gerry Matte created FORGE-1228:
----------------------------------
Summary: increase conversation timeout to 30 minutes
Key: FORGE-1228
URL: https://issues.jboss.org/browse/FORGE-1228
Project: Forge
Issue Type: Enhancement
Components: Scaffold
Affects Versions: 1.4.1.Final
Reporter: Gerry Matte
Priority: Minor
The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods]
After each conversation.begin() please insert:
this.conversation.setTimeout(1800000);
which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout)
For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating !
--
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
10 years, 7 months
[JBoss JIRA] (FORGEPLUGINS-137) Upgrade to AngularJS 1.2
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGEPLUGINS-137:
--------------------------------------------
Summary: Upgrade to AngularJS 1.2
Key: FORGEPLUGINS-137
URL: https://issues.jboss.org/browse/FORGEPLUGINS-137
Project: Forge Plugins
Issue Type: Task
Components: AngularJS Scaffold
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
AngularJS 1.2 is currently in the RC phase. We should upgrade to it as soon as possible, once it is out.
--
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
10 years, 7 months