October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15549) After project build, the JAX-RS node remains at "Loading..."

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15549?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-15549. ----------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-15599 > After project build, the JAX-RS node remains at "Loading..." > ------------------------------------------------------------ > > Key: JBIDE-15549 > URL: https://issues.jboss.org/browse/JBIDE-15549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15606: --------------------------------------------- when you mean publish what do you mean here ? we do have all the internal build sites for each component - trying to grok what it is you otherwise use ? > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13208) Allow custom 'standalone' mode directory in AS7 server plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13208?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13208: ---------------------------------------- Labels: f2f2012 new_and_noteworthy (was: f2f2012) > Allow custom 'standalone' mode directory in AS7 server plugin > ------------------------------------------------------------- > > Key: JBIDE-13208 > URL: https://issues.jboss.org/browse/JBIDE-13208 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Mac OS-X 10.8.2, Java 6, Java 7, JBoss AS 7.x, JBoss EAP 6, JBDS 5.0.1 > Reporter: Duncan Doyle > Assignee: Rob Stryker > Labels: f2f2012, new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > As with JBoss EAP5.x, I have the habit of working in a copy of a 'profile' directory. With JBoss AS7/EAP6 I therefore work in copies of 'standalone' and 'domain' (depending on the operational mode). When I start AS/EAP, I reference the correct server directory with the 'jboss.server.base.dir' or 'jboss.domain.base.dir' system property. This allows me, among other things, to run multiple AS/EAP instances from a single JBoss AS/EAP installation. > It seems that the JBDS AS7 plugin only allows me to reference the default 'standalone' directory. I'm not able to select a different directory in the 'JBoss Runtime' configuration screen. I would propose to add the possibility to start a JBoss AS7/EAP6 instance from a different directory than 'standalone'. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-182) Publish to ModeShape: Finish Button Disabled

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/JBTIS-182?page=com.atlassian.jira.plugin.... ] Lucie Fabrikova updated JBTIS-182: ---------------------------------- Attachment: modeshape.png > Publish to ModeShape: Finish Button Disabled > -------------------------------------------- > > Key: JBTIS-182 > URL: https://issues.jboss.org/browse/JBTIS-182 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 4.1.3 > Environment: JBDS 7.0.0.GA, JBoss Tools 4.1.3.Beta3, EAP 6.1 (in DV 6.0.0) > Reporter: Lucie Fabrikova > Attachments: modeshape.png > > > If no publish area is created, it cannot be created in dialog "Publish to ModeShape", via rght-click Modeshape->Publish. > 1. start EAP 6.1 server > 2. create new Modeshape server (http://localhost:8080/modeshape-rest, admin/admin) > 3. rght-click a project, Modeshape -> Publish > 4. dialog "Publish to ModeShape" appears, with warning "A publish area must be selected. If there aren't any to choose from, you can create one here or in the ModeShape View" > 5. click to add new Publish Area > 6. button "Finish" is still disabled -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-182) Publish to ModeShape: Finish Button Disabled

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created JBTIS-182: ------------------------------------- Summary: Publish to ModeShape: Finish Button Disabled Key: JBTIS-182 URL: https://issues.jboss.org/browse/JBTIS-182 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Components: modeshape Affects Versions: 4.1.3 Environment: JBDS 7.0.0.GA, JBoss Tools 4.1.3.Beta3, EAP 6.1 (in DV 6.0.0) Reporter: Lucie Fabrikova If no publish area is created, it cannot be created in dialog "Publish to ModeShape", via rght-click Modeshape->Publish. 1. start EAP 6.1 server 2. create new Modeshape server (http://localhost:8080/modeshape-rest, admin/admin) 3. rght-click a project, Modeshape -> Publish 4. dialog "Publish to ModeShape" appears, with warning "A publish area must be selected. If there aren't any to choose from, you can create one here or in the ModeShape View" 5. click to add new Publish Area 6. button "Finish" is still disabled -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13106) Change icon and tooltip for "close console" to better show difference to closing view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-13106: --------------------------------------- Definitely agree. This is unambiguous and as a new openshift QE. Many users should find difficult to find out, how to close session while tailing files. I was surprised, why closing console didn't closed session. After explanation and point to this JIRA it comes clear. And those "X" is grey - another reason to change it - easily overlooked. > Change icon and tooltip for "close console" to better show difference to closing view > ------------------------------------------------------------------------------------- > > Key: JBIDE-13106 > URL: https://issues.jboss.org/browse/JBIDE-13106 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.2.x > > Attachments: different-close-actions.png > > > The Server Log console has 2 distinct actions that are labeled "close console". > !different-close-actions.png! > 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation > 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern. > We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15500) Let the user choose which gear from which to 'tail' logs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15500?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15500: ------------------------------------- Priority: Optional (was: Major) > Let the user choose which gear from which to 'tail' logs > --------------------------------------------------------- > > Key: JBIDE-15500 > URL: https://issues.jboss.org/browse/JBIDE-15500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Priority: Optional > > the 'rhc tail' command provides the user with a '--gear' (singular) option to let the user choose which gear logs she wants to 'tail'. > The wizard should provide a similar feature, but this may require enhancements in the java client, first. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15500) Let the user choose which gear from which to 'tail' logs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15500?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15500: ------------------------------------- Priority: Major (was: Optional) > Let the user choose which gear from which to 'tail' logs > --------------------------------------------------------- > > Key: JBIDE-15500 > URL: https://issues.jboss.org/browse/JBIDE-15500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > > the 'rhc tail' command provides the user with a '--gear' (singular) option to let the user choose which gear logs she wants to 'tail'. > The wizard should provide a similar feature, but this may require enhancements in the java client, first. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13964) Support "tail log files" when application is runs on multiple gears

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13964?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-13964. -------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) Resolution: Duplicate Issue This is duplicate to JBIDE-15484 > Support "tail log files" when application is runs on multiple gears > ------------------------------------------------------------------- > > Key: JBIDE-13964 > URL: https://issues.jboss.org/browse/JBIDE-13964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > At the moment, "tail log files" only works on the first application gear, thus, there's no way to read the logs from other gears if the application is scaled. > The REST API should provide the id of all gears and from that, we could connect with SSH and issue the "tail" command and display all in a single console (with filters) or in separate consoles. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2779) Widget shrinked after attempt to expand it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2779?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-2779: ------------------------------------- Probably happens in JBT 4.1.0.1 too, so move under JBIDE should be considered (probably it is, after all, upstream bug). Also, I didn't set up target release and it automatically choose bad one, please fix it. > Widget shrinked after attempt to expand it > ------------------------------------------ > > Key: JBDS-2779 > URL: https://issues.jboss.org/browse/JBDS-2779 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 7.0.0.GA > Reporter: Marián Labuda > Priority: Minor > Attachments: 37.png, 56.png > > > Sometimes widgets collaps or shrinked itself to line and it is impossible to expand it. Mostly if was undeterministic, but now I have found reproducible one. See attached images. > It's possible to close such widget by press Esc. -- 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, 6 months

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 October 2013