September 2017 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2761) Provide compatibility with Java 9

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2761: -------------------------------------- Summary: Provide compatibility with Java 9 Key: FORGE-2761 URL: https://issues.jboss.org/browse/FORGE-2761 Project: Forge Issue Type: Feature Request Affects Versions: 3.7.2.Final Reporter: George Gastaldi Fix For: 3.x Future Forge should support building and running in JDK9 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-218) Scaffolded project doesn't correctly display in Browser SIM

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-218?page=com.atlassian.jira.... ] George Gastaldi closed FORGEPLUGINS-218. ---------------------------------------- Resolution: Rejected Not a bug > Scaffolded project doesn't correctly display in Browser SIM > ----------------------------------------------------------- > > Key: FORGEPLUGINS-218 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-218 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: AngularJS Scaffold > Environment: JBDS 10.4, EAP 6.4.2.GA, Forge 3.6.1.Final > Reporter: nicolas duminil > Assignee: Vineet Reynolds > Attachments: Capture.PNG, image-2017-09-16-14-01-24-528.png, image-2017-09-16-14-01-41-986.png > > > Greetings, > The project jboss-forge-html5, automatically generated by JBDS, correctly displays in the browser but not in the Browser SIM. I'm attaching a PNG file such that to demonstrate it. As shown, the main menu containing the logo and the button "Members" doesn't appear and, hence, it is not possible to navigate to it. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-218) Scaffolded project doesn't correctly display in Browser SIM

by nicolas duminil (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-218?page=com.atlassian.jira.... ] nicolas duminil commented on FORGEPLUGINS-218: ---------------------------------------------- Hi George, yes, you're right, it was hidden by the burger menu. Many thanks. Nicolas > Scaffolded project doesn't correctly display in Browser SIM > ----------------------------------------------------------- > > Key: FORGEPLUGINS-218 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-218 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: AngularJS Scaffold > Environment: JBDS 10.4, EAP 6.4.2.GA, Forge 3.6.1.Final > Reporter: nicolas duminil > Assignee: Vineet Reynolds > Attachments: Capture.PNG, image-2017-09-16-14-01-24-528.png, image-2017-09-16-14-01-41-986.png > > > Greetings, > The project jboss-forge-html5, automatically generated by JBDS, correctly displays in the browser but not in the Browser SIM. I'm attaching a PNG file such that to demonstrate it. As shown, the main menu containing the logo and the button "Members" doesn't appear and, hence, it is not possible to navigate to it. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-218) Scaffolded project doesn't correctly display in Browser SIM

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-218?page=com.atlassian.jira.... ] George Gastaldi commented on FORGEPLUGINS-218: ---------------------------------------------- Isn't the Members menu item hidden in the burger menu? > Scaffolded project doesn't correctly display in Browser SIM > ----------------------------------------------------------- > > Key: FORGEPLUGINS-218 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-218 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: AngularJS Scaffold > Environment: JBDS 10.4, EAP 6.4.2.GA, Forge 3.6.1.Final > Reporter: nicolas duminil > Assignee: Vineet Reynolds > Attachments: Capture.PNG, image-2017-09-16-14-01-24-528.png, image-2017-09-16-14-01-41-986.png > > > Greetings, > The project jboss-forge-html5, automatically generated by JBDS, correctly displays in the browser but not in the Browser SIM. I'm attaching a PNG file such that to demonstrate it. As shown, the main menu containing the logo and the button "Members" doesn't appear and, hence, it is not possible to navigate to it. > Kind regards, > Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-218) Scaffolded project doesn't correctly display in Browser SIM

by nicolas duminil (JIRA)

nicolas duminil created FORGEPLUGINS-218: -------------------------------------------- Summary: Scaffolded project doesn't correctly display in Browser SIM Key: FORGEPLUGINS-218 URL: https://issues.jboss.org/browse/FORGEPLUGINS-218 Project: Forge Plugins/Addons Issue Type: Bug Components: AngularJS Scaffold Environment: JBDS 10.4, EAP 6.4.2.GA, Forge 3.6.1.Final Reporter: nicolas duminil Assignee: Vineet Reynolds Attachments: Capture.PNG, image-2017-09-16-14-01-24-528.png, image-2017-09-16-14-01-41-986.png Greetings, The project jboss-forge-html5, automatically generated by JBDS, correctly displays in the browser but not in the Browser SIM. I'm attaching a PNG file such that to demonstrate it. As shown, the main menu containing the logo and the button "Members" doesn't appear and, hence, it is not possible to navigate to it. Kind regards, Nicolas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-125) Add APIs for class and member initializers

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-125?page=com.atlassian.jira.plugi... ] George Gastaldi commented on ROASTER-125: ----------------------------------------- Ah I ignore my question. I see you have introduced InitializerSource and InitializerHolderSource. That looks cool > Add APIs for class and member initializers > ------------------------------------------- > > Key: ROASTER-125 > URL: https://issues.jboss.org/browse/ROASTER-125 > Project: Roaster > Issue Type: Feature Request > Reporter: Aaron Tull > > There are gaps in the API JavaClassSource for finding the body of static and member initializers. For instance, the following class shows 3 code blocks which cannot be accessed from the API without delving into the AST internals. > {code:java} > public class TestSource { > { > // ... instance initialization block > } > static { > // ... static initialization block > } > > private Runnable innerMember = new Runnable() { > @Override > public void run() { > // ... member field initialization to anonymous class instance > } > } > > // class definition not found > private static Runnable nestedMember = new Runnable() { > @Override > public void run() { > // ... static field initialization to anonymous class instance > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-125) Add APIs for class and member initializers

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-125?page=com.atlassian.jira.plugi... ] George Gastaldi commented on ROASTER-125: ----------------------------------------- Kevin, Thanks for taking this issue. We really appreciate it. About #1, are you introducing any API changes? If so, you can leave the implementation in the common class and expose the interface with this new API only in the JavaClass and JavaEnum interfaces. > Add APIs for class and member initializers > ------------------------------------------- > > Key: ROASTER-125 > URL: https://issues.jboss.org/browse/ROASTER-125 > Project: Roaster > Issue Type: Feature Request > Reporter: Aaron Tull > > There are gaps in the API JavaClassSource for finding the body of static and member initializers. For instance, the following class shows 3 code blocks which cannot be accessed from the API without delving into the AST internals. > {code:java} > public class TestSource { > { > // ... instance initialization block > } > static { > // ... static initialization block > } > > private Runnable innerMember = new Runnable() { > @Override > public void run() { > // ... member field initialization to anonymous class instance > } > } > > // class definition not found > private static Runnable nestedMember = new Runnable() { > @Override > public void run() { > // ... static field initialization to anonymous class instance > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-125) Add APIs for class and member initializers

by Kevin Mian Kraiker (JIRA)

[ https://issues.jboss.org/browse/ROASTER-125?page=com.atlassian.jira.plugi... ] Kevin Mian Kraiker edited comment on ROASTER-125 at 9/11/17 8:41 AM: --------------------------------------------------------------------- Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this comment, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. And that's just for the initalization blocks, anonymous instances are still another mystery. was (Author: mismatch): Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this comment, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. And that's just for the initalization blocks, anonymous instances are still another mystery. > Add APIs for class and member initializers > ------------------------------------------- > > Key: ROASTER-125 > URL: https://issues.jboss.org/browse/ROASTER-125 > Project: Roaster > Issue Type: Feature Request > Reporter: Aaron Tull > > There are gaps in the API JavaClassSource for finding the body of static and member initializers. For instance, the following class shows 3 code blocks which cannot be accessed from the API without delving into the AST internals. > {code:java} > public class TestSource { > { > // ... instance initialization block > } > static { > // ... static initialization block > } > > private Runnable innerMember = new Runnable() { > @Override > public void run() { > // ... member field initialization to anonymous class instance > } > } > > // class definition not found > private static Runnable nestedMember = new Runnable() { > @Override > public void run() { > // ... static field initialization to anonymous class instance > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-125) Add APIs for class and member initializers

by Kevin Mian Kraiker (JIRA)

[ https://issues.jboss.org/browse/ROASTER-125?page=com.atlassian.jira.plugi... ] Kevin Mian Kraiker edited comment on ROASTER-125 at 9/11/17 8:41 AM: --------------------------------------------------------------------- Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this comment, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. And that's just for the initalization blocks, anonymous instances are still another mystery. was (Author: mismatch): Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this comment, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. > Add APIs for class and member initializers > ------------------------------------------- > > Key: ROASTER-125 > URL: https://issues.jboss.org/browse/ROASTER-125 > Project: Roaster > Issue Type: Feature Request > Reporter: Aaron Tull > > There are gaps in the API JavaClassSource for finding the body of static and member initializers. For instance, the following class shows 3 code blocks which cannot be accessed from the API without delving into the AST internals. > {code:java} > public class TestSource { > { > // ... instance initialization block > } > static { > // ... static initialization block > } > > private Runnable innerMember = new Runnable() { > @Override > public void run() { > // ... member field initialization to anonymous class instance > } > } > > // class definition not found > private static Runnable nestedMember = new Runnable() { > @Override > public void run() { > // ... static field initialization to anonymous class instance > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-125) Add APIs for class and member initializers

by Kevin Mian Kraiker (JIRA)

[ https://issues.jboss.org/browse/ROASTER-125?page=com.atlassian.jira.plugi... ] Kevin Mian Kraiker edited comment on ROASTER-125 at 9/11/17 8:40 AM: --------------------------------------------------------------------- Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this comment, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. was (Author: mismatch): Since I needed to work with initializers in a project that already used Roaster, I gave a try delving in this part of the issue - what I ended up with is available in the master branch of [https://github.com/CRC-Mismatch/roaster]. With the state as of this post, I found three main problems: # Only Classes and Enums allow initializer blocks, but the common AbstractJavaSourceMemberHolder super type is also extended by JavaInterfaceImpl, so it's not possible to simply implement an InitializerHolder in it. The only possible solutions I thought of were either implementing them separately in both JavaClassImpl and JavaEnumImpl (unmaintainable), creating an interface and using default implementations (hackish, I'm not sure how the BodyDeclaration could be accessed from it and would also require Java 1.8) or reorganizing the Abstract classes so that both JavaEnumImpl and JavaClassImpl extend a new Abstract class that JavaInterfaceImpl does not. # The order of initializer blocks is important, and also "interacts" with the order of the field declarations, so it's not as easy as using Lists. # The only way to refer to initializer blocks is by position and/or static modifier, so getting and removing intializer blocks depend on where they appear, and adding a new one must allow defining a position where to insert it. > Add APIs for class and member initializers > ------------------------------------------- > > Key: ROASTER-125 > URL: https://issues.jboss.org/browse/ROASTER-125 > Project: Roaster > Issue Type: Feature Request > Reporter: Aaron Tull > > There are gaps in the API JavaClassSource for finding the body of static and member initializers. For instance, the following class shows 3 code blocks which cannot be accessed from the API without delving into the AST internals. > {code:java} > public class TestSource { > { > // ... instance initialization block > } > static { > // ... static initialization block > } > > private Runnable innerMember = new Runnable() { > @Override > public void run() { > // ... member field initialization to anonymous class instance > } > } > > // class definition not found > private static Runnable nestedMember = new Runnable() { > @Override > public void run() { > // ... static field initialization to anonymous class instance > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2017