[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
The steps you gave above exactly match what I did. The only difference I can spot is that I had maven set to NOT include nested folders:
!maven-preferences-hide-children.png!
Maybe I should try with the latest CDI plugins? I'm currently running:
{code}
934 ACTIVE org.jboss.tools.cdi.core_1.5.1.CR1-v20131116-0535-B127
935 ACTIVE org.jboss.tools.cdi.xml_1.5.1.CR1-v20131116-0535-B127
948 ACTIVE org.jboss.tools.maven.cdi_1.6.0.Alpha1-v20131128-2129-B420
{code}
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16286:
-------------------------------------
Attachment: maven-preferences-hide-children.png
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Juraj Húska edited comment on JBIDE-16272 at 12/16/13 4:21 AM:
---------------------------------------------------------------
These are mine screenshots reproducing the issue:
*invoking autocompletion on a4j: (no scrolling)*
[^myAutocompletion1.png]
*invoking autocompletion on a4j: (with scrolling in suggestion list)*
[^myAutocompletion2.png]
*invoking autocompletion on a4j:ca*
[^myAutocompletion3.png]
Notice that the description of the tag is mentioning correctly {{rich:calendar}}.
was (Author: jhuska):
These are mine screenshots reproducing the issue:
*invoking autocompletion on a4j: (no scrolling)*
[^myAutocompletion1.png]
*invoking autocompletion on a4j: (with scrolling in suggestion list)*
[^myAutocompletion2.png]
*invoking autocompletion on a4j:ca*
[^myAutocompletion3.png]
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Juraj Húska commented on JBIDE-16272:
-------------------------------------
These are mine screenshots reproducing the issue:
*invoking autocompletion on a4j: (no scrolling)*
[^myAutocompletion1.png]
*invoking autocompletion on a4j: (with scrolling in suggestion list)*
[^myAutocompletion2.png]
*invoking autocompletion on a4j:ca*
[^myAutocompletion3.png]
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-15969) Investigate removing some m2e extensions for TP
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15969?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15969:
-------------------------------------
Yes, other JBT Maven plugins depend on these extensions to be present.
> Investigate removing some m2e extensions for TP
> -----------------------------------------------
>
> Key: JBIDE-15969
> URL: https://issues.jboss.org/browse/JBIDE-15969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.0.Alpha2
>
>
> It looks like m2e-wro4j is not used at all in JBoss Tools (only referenced in Central).
> It also appears that other m2e extensions (maven.apt and m2e.jdt) are not necessary to build JBT, and are only made available by default in JBDS installer and on Central.
> So I suggest the following changes:
> * Remove the 3 maven extensions (m2e.wro4j, maven.apt, m2e.jdt) from the JBT target-platform, and keep them only in Central
> * Remove m2e.wro4j from JBDS TP (as it's not part of installer)
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Juraj Húska updated JBIDE-16272:
--------------------------------
Attachment: myAutocompletion1.png
myAutocompletion2.png
myAutocompletion3.png
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Juraj Húska commented on JBIDE-16272:
-------------------------------------
>From the included screenshot I can see that you have tried to invoke autocompletion on {{a4j:}}.
I have tried as well, and to see suggestion {{a4j:calendar}}, I had to scroll a little bit in the suggestions. They are not alphabetically ordered in that case.
The suggestion is more visible (one does not have to scroll) when invoking autocompletion on {{a4j:c}} or better {{a4:ca}}.
Can you please see this behavior ? Or it still the same ...
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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
12 years, 4 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2745:
--------------------------------------
So "experimental" is the right category they would fall in to? I'm just trying to be sure we're not talking about yet another content type [1] for no reason.
[~maxandersen] - Include the BETA tooling in the Central as mark that as "Tech Preview"? At the moment we're giving the BETA tooling update site link to customer that raise cases related to this.
[1] https://devstudio.jboss.com/updates/7.0/central/
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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
12 years, 4 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2745:
-------------------------------------------
[~nickboldt] i'm not following what you mean with your last comment.
[~mmusaji] other examples than completely new things (like arquillian) is early versions of plugins that are being developed. i.e. SOA tooling were not ready for 7.0/7.1 but they did have an beta updatesite - could we find a way to make this more easily available to our users rather than having to manually install from external updatesite.
Another combination is making beta/alpha versions of a JBDS release train(like 7.1.1 in 7.x) available as an update to use from within Central.
The above have in discussions said it needs different or additional UI and some clear handling of users being made aware they are running a non-supported combination.
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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
12 years, 4 months