[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26751:
-----------------------------------------
[~odockal]
*Red Hat CodeReady Studio*
Version: 12.13.0.AM1
Build id: AM1-v20190720-1320-B4681
Build date: 20190720-1320
> Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26751
> URL: https://issues.jboss.org/browse/JBIDE-26751
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Environment: OS X 10.14.6
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png
>
>
> When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26751:
---------------------------------------
[~zcervink] What version of codereadystudio was this reproduced on?
> Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26751
> URL: https://issues.jboss.org/browse/JBIDE-26751
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Environment: OS X 10.14.6
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png
>
>
> When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ]
nimo stephan edited comment on JBIDE-26740 at 7/26/19 6:20 PM:
---------------------------------------------------------------
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed.
It makes sense that "Every change in deployment should trigger a wildfly restart automatically."..especially while developing. Having an option for this would be good. Doing the restart manually is awkward..
was (Author: nimo22):
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed.
It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward..
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.jboss.org/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Critical
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ]
nimo stephan commented on JBIDE-26740:
--------------------------------------
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed.
It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward..
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.jboss.org/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Critical
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ]
nimo stephan edited comment on JBIDE-26741 at 7/26/19 6:10 PM:
---------------------------------------------------------------
+1.First, what type of project are you using?+
It's a maven project from a maven archetype (weld-jee).
+2. Do you have m2e-wtp installed?+
yes, along with actual "eclipse jee" and actual "jboss tools"
I click on "publish to server" and the exloded war is deployed but not its lib-folder.
+3. If you're using a standard "Dynamic Web Project"+
No. It's a typical maven project (wildfly-jee-archetype), nothing special.
was (Author: nimo22):
+1.First, what type of project are you using?+
It's a maven project from a maven archetype (weld-jee).
+2. Do you have m2e-wtp installed?+
yes, along with actual "eclipse jee" and actual "jboss tools"
I click on "publish to server" and it's all the exloded war is deployed but not the lib-folder.
+3. If you're using a standard "Dynamic Web Project"+
No. It's a typical maven project (wildfly-jee-archetype), nothing special.
> WEB_INF/lib is not transmitted after full publishing
> ----------------------------------------------------
>
> Key: JBIDE-26741
> URL: https://issues.jboss.org/browse/JBIDE-26741
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Major
>
> I am using
> Eclipse IDE for Enterprise Java Developers.
> Version: 2019-06 (4.12.0)
> with actual Jboss Tools.
>
> When publising war archives
> to "Wildfly 17 Server" with *"Full Publish"* (or "Incremental Publish"),
> the *WEB_INF/lib* folder is *not* transferred.
> I guess, it s a bug..
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ]
nimo stephan commented on JBIDE-26741:
--------------------------------------
+1.First, what type of project are you using?+
It's a maven project from a maven archetype (weld-jee).
+2. Do you have m2e-wtp installed?+
yes, along with actual "eclipse jee" and actual "jboss tools"
I click on "publish to server" and it's all the exloded war is deployed but not the lib-folder.
+3. If you're using a standard "Dynamic Web Project"+
No. It's a typical maven project (wildfly-jee-archetype), nothing special.
> WEB_INF/lib is not transmitted after full publishing
> ----------------------------------------------------
>
> Key: JBIDE-26741
> URL: https://issues.jboss.org/browse/JBIDE-26741
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Major
>
> I am using
> Eclipse IDE for Enterprise Java Developers.
> Version: 2019-06 (4.12.0)
> with actual Jboss Tools.
>
> When publising war archives
> to "Wildfly 17 Server" with *"Full Publish"* (or "Incremental Publish"),
> the *WEB_INF/lib* folder is *not* transferred.
> I guess, it s a bug..
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by Robert Stryker (Jira)
[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ]
Robert Stryker commented on JBIDE-26740:
----------------------------------------
Unfortunately, JBoss Tools has no ability to modify the "Publishing" section of the editor. It is automatically added by WTP webtools. A feature request like this would need to be made at the WTP level.
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.jboss.org/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Critical
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-26741) WEB_INF/lib is not transmitted after full publishing
by Robert Stryker (Jira)
[ https://issues.jboss.org/browse/JBIDE-26741?page=com.atlassian.jira.plugi... ]
Robert Stryker commented on JBIDE-26741:
----------------------------------------
I think we're going to need more information here on your project structure and what exactly you are publishing.
First, what type of project are you using? Is it a wtp-style faceted project? Or is it a maven project? Do you have m2e-wtp installed? Or are you trying to publish a completed .war file by right-clicking it and using the "make deployable" action?
If you're using a standard "Dynamic Web Project", is this issue replicatable with a small simple example project? Can you attach such a project or provide a set of instructions to replicate the issue? A lot of WTP logic depends on the exact structure of the project, so replicating it can be hard without knowing exactly what you're doing. =/
> WEB_INF/lib is not transmitted after full publishing
> ----------------------------------------------------
>
> Key: JBIDE-26741
> URL: https://issues.jboss.org/browse/JBIDE-26741
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Major
>
> I am using
> Eclipse IDE for Enterprise Java Developers.
> Version: 2019-06 (4.12.0)
> with actual Jboss Tools.
>
> When publising war archives
> to "Wildfly 17 Server" with *"Full Publish"* (or "Incremental Publish"),
> the *WEB_INF/lib* folder is *not* transferred.
> I guess, it s a bug..
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-24963:
------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954, https://github.com/jbosstools/jbosstools-integration-tests/pull/1957, https://github.com/jbosstools/jbosstools-integration-tests/pull/1958, https://github.com/jbosstools/jbosstools-integration-tests/pull/1959, https://github.com/jbosstools/jbosstools-integration-tests/pull/1960, https://github.com/jbosstools/jbosstools-integration-tests/pull/1961, https://github.com/jbosstools/jbosstools-integration-tests/pull/1962, https://github.com/jbosstools/jbosstools-integration-tests/pull/1963 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954, https://github.com/jbosstools/jbosstools-integration-tests/pull/1957, https://github.com/jbosstools/jbosstools-integration-tests/pull/1958, https://github.com/jbosstools/jbosstools-integration-tests/pull/1959, https://github.com/jbosstools/jbosstools-integration-tests/pull/1960, https://github.com/jbosstools/jbosstools-integration-tests/pull/1961, https://github.com/jbosstools/jbosstools-integration-tests/pull/1962)
> Create CDI 2 integration tests
> ------------------------------
>
> Key: JBIDE-24963
> URL: https://issues.jboss.org/browse/JBIDE-24963
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi, integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Lukáš Valach
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> The support for CDI 2.0 has been added recently, see JBIDE-24949.
> Spec:
> http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html
> Change log:
> https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months