February 2017 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

6 days, 13 hours

5
8
0 / 0

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM: ------------------------------------------------------------ Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ There are ways to achieve more-than-260-char paths, but do we want to? was (Author: nickboldt): Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... > Align installation default path with installer filename > ------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

1 month

4
4
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {code} -- 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

1 month

3
3
0 / 0

[JBoss JIRA] (JBIDE-19663) jst/jsf New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19663?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19663: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------- > > Key: JBIDE-19663 > URL: https://issues.jboss.org/browse/JBIDE-19663 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

1 month, 4 weeks

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

8 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-23889. ------------------------------------ Resolution: Done Build #27718 took place on Feb 8th, and job has looped failing at very high frequency (several times per minutes whereas expectation is every 30 minutes) for at least 2 days, until Build #29675. That is about ~2000 builds in two days. But it seems that the delay of 30 minutes is working properly again, so this issue seems fixed magically. > jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.4.AM1 > > Attachments: composite.png > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24014 at 2/28/17 2:34 PM: ------------------------------------------------------------- Pull request (master): https://github.com/jbosstools/jbosstools-base/pull/557 Pull request (4.4.x): https://github.com/jbosstools/jbosstools-base/pull/558 was (Author: nickboldt): Pull request: https://github.com/jbosstools/jbosstools-base/pull/557 > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24014: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24014: ------------------------------------ Pull request: https://github.com/jbosstools/jbosstools-base/pull/557 > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23652 at 2/28/17 2:18 PM: ------------------------------------------------------------- Same problem in * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (points to ../, which has no composite pointer to latest - need to copy same composite*.xml from non-static path here) * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) * https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ (composite out of date) Should have unchanging composites here, too: * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/development/updates/integration... (should point to /static path) Need to update staging script [1] and re-run it via Jenkins job [2] to verify fixed. [1] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-releng-pu... was (Author: nickboldt): Same problem in * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (points to ../, which has no composite pointer to latest - need to copy same composite*.xml from non-static path here) * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) Should have unchanging composites here, too: * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/development/updates/integration... (should point to /static path) Need to update staging script [1] and re-run it via Jenkins job [2] to verify fixed. [1] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-releng-pu... > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.4.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017