October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2733: -------------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Fix For: 7.1.0.Beta1 > > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15482: ---------------------------------------- Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- 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-15427) BrowserSim performance and livereload issues seen on RHEL6 relative to MacOS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15427?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15427: ---------------------------------------- Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > BrowserSim performance and livereload issues seen on RHEL6 relative to MacOS > ---------------------------------------------------------------------------- > > Key: JBIDE-15427 > URL: https://issues.jboss.org/browse/JBIDE-15427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Environment: Version: 7.0.0.Beta1 > Build id: Beta1-v20130529-0631-B257 > Build date: 20130529-0631 > Reporter: Len DiMaggio > Assignee: Yahor Radtsevich > Priority: Critical > Fix For: 4.1.1.Beta1 > > Attachments: MAC_1.png, RHEL_1.png, RHEL_2.png > > > Seeing slow performance (on screen refresh), lack or responsiveness and failure to live-update on RHEL6. These issues are not being seen on other OS's. > See attached screenshots for a comparison of RHEL6 to Mac OSX. > Related to: https://issues.jboss.org/browse/JBIDE-14731 -- 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-13790) Prepare fast-filter script for integration-stack-tests split

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13790: ---------------------------------------- Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- 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-15580) Run version comparisons to check components have been updated

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15580?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15580: ---------------------------------------- Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > Run version comparisons to check components have been updated > ------------------------------------------------------------- > > Key: JBIDE-15580 > URL: https://issues.jboss.org/browse/JBIDE-15580 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Max Rydahl Andersen > Assignee: Jiri Peterka > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > Can you run a version check to ensure all componnents have actually bumped their micro version before release? -- 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-2799) Better contextual menu for JAXRS

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created JBDS-2799: --------------------------------------- Summary: Better contextual menu for JAXRS Key: JBDS-2799 URL: https://issues.jboss.org/browse/JBDS-2799 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 7.0.1.GA Reporter: Emmanuel Hugonnet Priority: Minor Attachments: jbosstools_jaxrs.png When right clicking on the "JAX-RS Web Services" resources view I expect a create new RestFull Web Service entry in the menu. -- 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-2799) Better contextual menu for JAXRS

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBDS-2799?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet updated JBDS-2799: ------------------------------------ Attachment: jbosstools_jaxrs.png Menu where I expect the entries > Better contextual menu for JAXRS > -------------------------------- > > Key: JBDS-2799 > URL: https://issues.jboss.org/browse/JBDS-2799 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 7.0.1.GA > Reporter: Emmanuel Hugonnet > Priority: Minor > Attachments: jbosstools_jaxrs.png > > > When right clicking on the "JAX-RS Web Services" resources view I expect a create new RestFull Web Service entry in the menu. -- 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-2798) Better contextual menu

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created JBDS-2798: --------------------------------------- Summary: Better contextual menu Key: JBDS-2798 URL: https://issues.jboss.org/browse/JBDS-2798 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 7.0.1.GA Reporter: Emmanuel Hugonnet As a user I want to add a new JAXRS webservice to my Web application When I right click on my project selecting the "new" entry,the first element is project (which is strange since I have already selected a project), then File, Folder and SQL Files which are not quite relevant in the context of a web application. I would expect more web related entries in the top most, and less entries as a whole. If I right click without selecting my current project then the new project entry becomes relevant. -- 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-11301) no stacktrace when junit tests fail

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-11301. ------------------------------------ Resolution: Won't Fix Marking it as "Won't fix" because we wont make efforts regarding that request. Stacks can be found in the surefire-reports files, as you can read in Maven log after a test failed. Logs can be found in target/work/data/.metadata/.log. > no stacktrace when junit tests fail > ----------------------------------- > > Key: JBIDE-11301 > URL: https://issues.jboss.org/browse/JBIDE-11301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 3.3.0.Beta3 > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Priority: Minor > Fix For: LATER > > > If I run JBT tycho build locally for trunk, for example: > mvn clean install -fae -e -P default -f cdi/tests/pom.xml > and there is some test failures then I don't see any stacktrace in console. Just a text message from the JUnit test assert. > -Dsurefire.useFile=false does not help. > But I see the stacktrace in <target>/surefire-reports > In Beta1 branch it works fine. > I don't see stacktrace in console output in Hudson either but I'm not sure it's a problem there. > For example https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... > But for local builds it's very useful to see the full stacktrace in console. -- 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-15651) EAP 6.2 cannot be connected to in MBean Explorer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15651?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15651: --------------------------------------- So the conclusion here is that this regression is probably caused by library/protocol changes/inconsistencies. And since connection with credentials still works, we will stick with that for now. > EAP 6.2 cannot be connected to in MBean Explorer > ------------------------------------------------ > > Key: JBIDE-15651 > URL: https://issues.jboss.org/browse/JBIDE-15651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.1.1.Alpha2 > Environment: JBDS 7.1.0.Alpha2 B431 > Reporter: Martin Malina > Fix For: 4.1.1.Beta1 > > > When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect. -- 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