[JBoss JIRA] (FORGE-2489) i18n and labels
by Aitor Fdez-Ceballos Jiménez (JIRA)
Aitor Fdez-Ceballos Jiménez created FORGE-2489:
--------------------------------------------------
Summary: i18n and labels
Key: FORGE-2489
URL: https://issues.jboss.org/browse/FORGE-2489
Project: Forge
Issue Type: Feature Request
Affects Versions: 2.19.2.Final
Reporter: Aitor Fdez-Ceballos Jiménez
It would be quite useful that forge scaffolding for JSF could generate the xhtml pages with all the labels replaced with #{messages['key']} and include in the project a properties file with the texts so you can easily change them globally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ROASTER-82) Var-args support
by Petr Janeček (JIRA)
Petr Janeček created ROASTER-82:
-----------------------------------
Summary: Var-args support
Key: ROASTER-82
URL: https://issues.jboss.org/browse/ROASTER-82
Project: Roaster
Issue Type: Feature Request
Components: API
Affects Versions: 2.16.0.Final
Reporter: Petr Janeček
There's currently no way to create methods with a var-args parameter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2488) JEE setup commands producing JEE6 even if project is JEE7
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2488?page=com.atlassian.jira.plugin... ]
George Gastaldi reopened FORGE-2488:
------------------------------------
> JEE setup commands producing JEE6 even if project is JEE7
> ---------------------------------------------------------
>
> Key: FORGE-2488
> URL: https://issues.jboss.org/browse/FORGE-2488
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.19.2.Final
> Reporter: Ivn Lahav
> Assignee: George Gastaldi
> Fix For: 2.20.0.Final
>
>
> Running 'javaee-setup --javaEEVersion 7' properly produces
> {code}
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> {code}
> in pom.xml. But then running
> 'jms-setup' or 'jta-setup' will produce JEE 6:
> {code}
> <dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-javaee-6.0</artifactId>
> <version>3.0.3.Final</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2488) JavaEE setup commands producing JavaEE 6 even if project is JavaEE 7
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2488?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2488.
----------------------------------
Resolution: Done
> JavaEE setup commands producing JavaEE 6 even if project is JavaEE 7
> --------------------------------------------------------------------
>
> Key: FORGE-2488
> URL: https://issues.jboss.org/browse/FORGE-2488
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.19.2.Final
> Reporter: Ivn Lahav
> Assignee: George Gastaldi
> Fix For: 2.20.0.Final
>
>
> Running 'javaee-setup --javaEEVersion 7' properly produces
> {code}
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> {code}
> in pom.xml. But then running
> 'jms-setup' or 'jta-setup' will produce JEE 6:
> {code}
> <dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-javaee-6.0</artifactId>
> <version>3.0.3.Final</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2488) JavaEE setup commands producing JavaEE 6 even if project is JavaEE 7
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2488?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2488:
-----------------------------------
Summary: JavaEE setup commands producing JavaEE 6 even if project is JavaEE 7 (was: JEE setup commands producing JEE6 even if project is JEE7)
> JavaEE setup commands producing JavaEE 6 even if project is JavaEE 7
> --------------------------------------------------------------------
>
> Key: FORGE-2488
> URL: https://issues.jboss.org/browse/FORGE-2488
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.19.2.Final
> Reporter: Ivn Lahav
> Assignee: George Gastaldi
> Fix For: 2.20.0.Final
>
>
> Running 'javaee-setup --javaEEVersion 7' properly produces
> {code}
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> {code}
> in pom.xml. But then running
> 'jms-setup' or 'jta-setup' will produce JEE 6:
> {code}
> <dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-javaee-6.0</artifactId>
> <version>3.0.3.Final</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2488) JEE setup commands producing JEE6 even if project is JEE7
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2488?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2488.
----------------------------------
Fix Version/s: 2.20.0.Final
Assignee: George Gastaldi
Resolution: Done
Fixed, Thanks for the feedback!
> JEE setup commands producing JEE6 even if project is JEE7
> ---------------------------------------------------------
>
> Key: FORGE-2488
> URL: https://issues.jboss.org/browse/FORGE-2488
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.19.2.Final
> Reporter: Ivn Lahav
> Assignee: George Gastaldi
> Fix For: 2.20.0.Final
>
>
> Running 'javaee-setup --javaEEVersion 7' properly produces
> {code}
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> {code}
> in pom.xml. But then running
> 'jms-setup' or 'jta-setup' will produce JEE 6:
> {code}
> <dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-javaee-6.0</artifactId>
> <version>3.0.3.Final</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> ...
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2488) JEE setup commands producing JEE6 even if project is JEE7
by Ivn Lahav (JIRA)
Ivn Lahav created FORGE-2488:
--------------------------------
Summary: JEE setup commands producing JEE6 even if project is JEE7
Key: FORGE-2488
URL: https://issues.jboss.org/browse/FORGE-2488
Project: Forge
Issue Type: Bug
Affects Versions: 2.19.2.Final
Reporter: Ivn Lahav
Running 'javaee-setup --javaEEVersion 7' properly produces
{code}
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>7.0</version>
<scope>provided</scope>
</dependency>
{code}
in pom.xml. But then running
'jms-setup' or 'jta-setup' will produce JEE 6:
{code}
<dependencyManagement>
<dependencies>
...
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<version>3.0.3.Final</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
...
<dependency>
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.1_spec</artifactId>
<scope>provided</scope>
</dependency>
</dependencies>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ROASTER-75) Encoding of source[?] code cannot be easily configured.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-75?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on ROASTER-75:
----------------------------------------
Let me know if this is a valid solution for you. Otherwise feel free to reopen this issue.
Thank you very much!
> 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
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 2.16.1.Final
>
>
> 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.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ROASTER-75) Encoding of source[?] code cannot be easily configured.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-75?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on ROASTER-75:
----------------------------------------
The solution is to use the {{Roaster.parse(String)}} method, by reading the source file beforehand. Roaster won't try to convert to another charset.
> 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
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 2.16.1.Final
>
>
> 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.4.11#64026)
9 years, 3 months
[JBoss JIRA] (ROASTER-75) Encoding of source[?] code cannot be easily configured.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-75?page=com.atlassian.jira.plugin... ]
George Gastaldi closed ROASTER-75.
----------------------------------
Assignee: George Gastaldi
Resolution: Done
> 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
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 2.16.1.Final
>
>
> 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.4.11#64026)
9 years, 3 months