March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-7727) Add Hudson job which runs JBDS SWTBot tests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7727?page=com.atlassian.jira.plugin... ] Pavol Srna closed JBIDE-7727. ----------------------------- > Add Hudson job which runs JBDS SWTBot tests > ------------------------------------------- > > Key: JBIDE-7727 > URL: https://issues.jboss.org/browse/JBIDE-7727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 3.2.0.Beta2, 3.3.0.M3 > Reporter: Vlado Pakan > Assignee: Pavol Srna > Fix For: 4.1.2.CR1 > > > We need Hudson job which will run JBDS/JBT SWTBot tests. > Job should be started manually for the beginning because we will have to change tests to run correctly on Hudson. Once we will have SWTBot tests running correctly we will start this job automatically. > Job should just run SWTBot tests not build complete JBT/JBDS. We need to minimize time taken by job. It will make developing SWTBot tests much faster. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16364) Use Pagespeed to see if loading could be improved.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16364?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16364: ---------------------------------------- Parent: (was: JBIDE-12355) Issue Type: Feature Request (was: Sub-task) > Use Pagespeed to see if loading could be improved. > -------------------------------------------------- > > Key: JBIDE-16364 > URL: https://issues.jboss.org/browse/JBIDE-16364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16014) create wiki replacement

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16014?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16014: ---------------------------------------- Parent: (was: JBIDE-12355) Issue Type: Feature Request (was: Sub-task) > create wiki replacement > ----------------------- > > Key: JBIDE-16014 > URL: https://issues.jboss.org/browse/JBIDE-16014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Priority: Minor > Fix For: 4.0.x > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16015) Add a "provided by" link on features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16015?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16015: ---------------------------------------- Parent: (was: JBIDE-12355) Issue Type: Feature Request (was: Sub-task) > Add a "provided by" link on features > ------------------------------------ > > Key: JBIDE-16015 > URL: https://issues.jboss.org/browse/JBIDE-16015 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Beta1 > > > features coming form JBT-IS/JBDS-IS should be marked as such. > Note, some things are only in JBT-IS (like arquillian is only in JBT but not in JBDS) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16608) Central tab is empty for IS and Core download

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16608?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16608: ---------------------------------------- Assignee: Nick Boldt > Central tab is empty for IS and Core download > --------------------------------------------- > > Key: JBIDE-16608 > URL: https://issues.jboss.org/browse/JBIDE-16608 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > Expected the central tab to actually describe how to use Central to get IS (similar to marketplace) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16577) Remove remote JBoss Archetype catalog

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16577?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-16577. ------------------------------------ verified in JBDS 7.1.1 GA-v20140303-1841-B672 > Remove remote JBoss Archetype catalog > ------------------------------------- > > Key: JBIDE-16577 > URL: https://issues.jboss.org/browse/JBIDE-16577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.2.CR1 > > > The JBoss remote archetype catalog was added with JBIDE-12094 to mitigate the loss of functionality caused by the removal of the JBoss nexus index (which caused JBIDE-12066) > Problem is, m2e tries to check the origin of a given archetype several (3 minimum) times during the creation process. It tries to lookup any selected archetype in all remote repositories in order to get the matching remote url if possible. > Problem is, JBoss Nexus is super super slow. Each lookup takes between 5 and 10 seconds (or more!). Given most archetypes come from Maven central this is a waste of time. When removed, creating any project from either JBoss Central or the Maven Wizard becomes much, much, *much* faster. > I have some work in progress to fix the dubious lookup logic in m2e but that won't be available before next june. > I believe even switchyard archetypes are now synch'ed to Maven central so the JBoss Archetype Catalog is not relevant anymore. I propose we remove it from the JBoss Maven Integration plugin. [~rcernich] WDYT? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16697) make sure features content has complete pages

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16697: ------------------------------------------- Summary: make sure features content has complete pages Key: JBIDE-16697 URL: https://issues.jboss.org/browse/JBIDE-16697 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Reporter: Max Rydahl Andersen make sure /feature content gets updated with pages that is complete, remove those that are incomplete. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

by Edoardo Barolo (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16689?page=com.atlassian.jira.plugi... ] Edoardo Barolo commented on JBIDE-16689: ---------------------------------------- Yes I used firstly JBOSS DEV STUDIO 64 bit ... Having many problems with that (crashes just reported) I fall back to a normal eclipse juno 32 bit with jboss tools installed. The situation then seems normalized. > Crash after CTRL + rightclick + find implementation > --------------------------------------------------- > > Key: JBIDE-16689 > URL: https://issues.jboss.org/browse/JBIDE-16689 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Edoardo Barolo > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16015) Add a "provided by" link on features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16015?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16015: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.0.x) > Add a "provided by" link on features > ------------------------------------ > > Key: JBIDE-16015 > URL: https://issues.jboss.org/browse/JBIDE-16015 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Beta1 > > > features coming form JBT-IS/JBDS-IS should be marked as such. > Note, some things are only in JBT-IS (like arquillian is only in JBT but not in JBDS) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ] Lukáš Fryč commented on JBIDE-14964: ------------------------------------ Some grammar fix, sorry. :-) I was reviewing this issue and it seems as it is no longer so fatal issue as it was back then. With JBDS 7.1.0 and WildFly 8.0 I can turn on "automatic publishing" while JRebel is enabled and I get modifications live-reloaded and updated correctly. I will keep testing it and will try with EAP 6.2 as well. > LiveReload doesn't reload when JRebel is used, because resources are "never published automatically" > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-14964 > URL: https://issues.jboss.org/browse/JBIDE-14964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Lukáš Fryč > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.x > > > When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings. > In this mode, LiveReload does not work, because new resources are never published according to the IDE. > However JRebel reloads those resources in a background. > ---- > In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally which might not be related to JRebel usage. -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2014