[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7581:
Fix Version/s: HTL Maven Plugin 1.1.8-1.4.0
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.16, HTL Maven Plugin
> 1.1.0
>Reporter: Santiago García Pimentel
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.26-1.4.0, HTL Maven
> Plugin 1.1.8-1.4.0
>
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7581:
Affects Version/s: HTL Maven Plugin 1.1.0
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.16, HTL Maven Plugin
> 1.1.0
>Reporter: Santiago García Pimentel
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.26-1.4.0, HTL Maven
> Plugin 1.1.8-1.4.0
>
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7581:
Fix Version/s: Scripting HTL Java Compiler 1.0.26-1.4.0
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.16
>Reporter: Santiago García Pimentel
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.26-1.4.0
>
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7581:
Affects Version/s: (was: Scripting HTL Compiler 1.0.16)
Scripting HTL Java Compiler 1.0.16
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.16
>Reporter: Santiago García Pimentel
>Priority: Major
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7581:
---
Component/s: Scripting
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Compiler 1.0.16
>Reporter: Santiago García Pimentel
>Priority: Major
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7581:
---
Description:
If you have an HTL file with two data-sly-use with classes with the same name
HTL will generate a java file which cannot be compiled.
e.g.
{code}
data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
data-sly-use.second="com.client.project.Page"
{code}
Will generate
{code}
import com.client.project.Page;
import com.adobe.cq.wcm.core.components.models.Page;
...
...
_global_first= renderContext.call("use", Page.class.getName(), obj());
_global_second = renderContext.call("use", Page.class.getName(), obj());
{code}
Causing a compilation error as Page is not fully qualified in the code and
therefore an ambiguous reference (due to the two imports of same class names)
This seems to have been introduced by SLING-7205 .
was:
If you have an HTL file with two data-sly-use with classes with the same name
HTL will generate a java file which cannot be compiled.
e.g.
{code}
data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
data-sly-use.second="com.client.project.Page"
{code}
Will generate
{code}
import com.client.project.Page;
import com.adobe.cq.wcm.core.components.models.Page;
...
...
_global_first= renderContext.call("use", Page.class.getName(), obj());
_global_second = renderContext.call("use", Page.class.getName(), obj());
{code}
Causing a compilation error.
The import com.adobe.cq.wcm.core.components.models.Page collides with another
import statement.
This seems to have been introduced by SLING-7205 .
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
>Affects Versions: Scripting HTL Compiler 1.0.16
>Reporter: Santiago García Pimentel
>Priority: Major
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error as Page is not fully qualified in the code and
> therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code
[
https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7581:
---
Description:
If you have an HTL file with two data-sly-use with classes with the same name
HTL will generate a java file which cannot be compiled.
e.g.
{code}
data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
data-sly-use.second="com.client.project.Page"
{code}
Will generate
{code}
import com.client.project.Page;
import com.adobe.cq.wcm.core.components.models.Page;
...
...
_global_first= renderContext.call("use", Page.class.getName(), obj());
_global_second = renderContext.call("use", Page.class.getName(), obj());
{code}
Causing a compilation error.
The import com.adobe.cq.wcm.core.components.models.Page collides with another
import statement.
This seems to have been introduced by SLING-7205 .
was:
If you have a sightly file with two data-sly-use with classes with the same
name. Sightly will generate a java file which cannot be compiled.
e.g.
data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
data-sly-use.second="com.client.project.Page"
Will generate
import com.client.project.Page;
import com.adobe.cq.wcm.core.components.models.Page;
...
...
_global_first= renderContext.call("use", Page.class.getName(), obj());
_global_second = renderContext.call("use", Page.class.getName(), obj());
Causing a compilation error.
The import com.adobe.cq.wcm.core.components.models.Page collides with another
import statement.
This seems to have been introduced by SLING-7205 .
> Using data-sly-use with two classes with same name will generate uncompilable
> code
> --
>
> Key: SLING-7581
> URL: https://issues.apache.org/jira/browse/SLING-7581
> Project: Sling
> Issue Type: Bug
>Affects Versions: Scripting HTL Compiler 1.0.16
>Reporter: Santiago García Pimentel
>Priority: Major
>
> If you have an HTL file with two data-sly-use with classes with the same name
> HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
> ...
> ...
> _global_first= renderContext.call("use", Page.class.getName(), obj());
> _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code}
> Causing a compilation error.
>
> The import com.adobe.cq.wcm.core.components.models.Page collides with another
> import statement.
> This seems to have been introduced by SLING-7205 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
