May 2015 - jbosstools-issues - Jboss List Archives

[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 week, 5 days

2
2
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

3 months

2
2
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

5 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ PR https://github.com/jbosstools/jbosstools-target-platforms/pull/146 updated again to include new bits from: http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.2.0.2... http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-maven... > Create and use Mars RC2 target-platform > --------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. > However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3447) IzPack 4.3.5 binary no longer available: codehaus has shutdown

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3447?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3447. ---------------------------- Resolution: Done Builds OK locally so closing. Jenkins is still pulling from cached copy of IzPack-install-4.3.5.jar, but should be fine there too. > IzPack 4.3.5 binary no longer available: codehaus has shutdown > -------------------------------------------------------------- > > Key: JBDS-3447 > URL: https://issues.jboss.org/browse/JBDS-3447 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > http://dist.codehaus.org/izpack/releases/4.3.5/IzPack-install-4.3.5.jar no longer resolves to a jar. Instead the site just says: > {quote}Codehaus has shutdown - http://www.codehaus.org/{quote} > {quote} > The time has come to end the era of Codehaus. > All Codehaus services will be terminated progressively until May 31st 2015 > With increasing diversity in opensource hosting platforms like Github and Bitbucket - who are meeting the needs of 1000s of projects - it makes sense to end the opensource hosting services of Codehaus. > Codehaus has operated at a loss for several years now (we're not powered by venture capital), and can not compete with the army of developers and integrated product offerings that are now commonplace. > The platform was to be terminated at the end of February 2015, however SonarQube has graciously offered to sponsor Codehaus for a few months to aid in the transition. > {quote} -- http://www.codehaus.org/ > So, we need to build JBDS using IzPack from another location. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3447) IzPack 4.3.5 binary no longer available: codehaus has shutdown

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3447?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-3447: -------------------------------- Assignee: Nick Boldt (was: Denis Golovin) > IzPack 4.3.5 binary no longer available: codehaus has shutdown > -------------------------------------------------------------- > > Key: JBDS-3447 > URL: https://issues.jboss.org/browse/JBDS-3447 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > http://dist.codehaus.org/izpack/releases/4.3.5/IzPack-install-4.3.5.jar no longer resolves to a jar. Instead the site just says: > {quote}Codehaus has shutdown - http://www.codehaus.org/{quote} > {quote} > The time has come to end the era of Codehaus. > All Codehaus services will be terminated progressively until May 31st 2015 > With increasing diversity in opensource hosting platforms like Github and Bitbucket - who are meeting the needs of 1000s of projects - it makes sense to end the opensource hosting services of Codehaus. > Codehaus has operated at a loss for several years now (we're not powered by venture capital), and can not compete with the army of developers and integrated product offerings that are now commonplace. > The platform was to be terminated at the end of February 2015, however SonarQube has graciously offered to sponsor Codehaus for a few months to aid in the transition. > {quote} -- http://www.codehaus.org/ > So, we need to build JBDS using IzPack from another location. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- The latest response on tm-dev is: "That contribution in the XML is only there in order to handle cases where the old legacy view was open in a workspace at the time a user upgraded. The implementation of that view does nothing except closing itself. The view is hidden (by means of capability) in all menus and views." But I'm not experiencing this at all. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19784) Make runtime detection available from server view ?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19784?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19784. --------------------------------- Resolution: Rejected Also, even if I could get it to work, unfortunately both our wtp-tomcat integration (in jbosstools-server/wtp) and tomcat itself (upstream wtp) would recognize the same folder, and would create two tomcat servers. Honestly, I think the workflows are too different to be performed together. It has stubbornly resisted each and every one of my efforts to shoehorn them together, it has mocked my pain, and intentionally thrown up roadblocks at every turn as if I was a five-star thief in grand theft auto. > Make runtime detection available from server view ? > --------------------------------------------------- > > Key: JBIDE-19784 > URL: https://issues.jboss.org/browse/JBIDE-19784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > runtime detection is great but it's rather hidden. > Idea is to add a search glass to server view to trigger runtime detection. > Wdyt? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19784) Make runtime detection available from server view ?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19784?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19784: ------------------------------------- > Seems we could just call our runtimedetection and have it report allt he found server runtimes. This simply isn't going to work. The only workflow that our runtimelocator is called from is when the preference page for runtiems is up, and a progress-monitor dialog is on top of it. Opening a third dialog (our jbt runtime detection) will make the UI of the background pages (pref page, progress mon dialog) to appear frozen, EVEN if we're running the read-and-dispatch, since they're below us on the call stack. Furthermore, once our rt-detection finds some runtime definitions, and the user clicks "OK", it will create those runtimes nad servers. This will attempt to refresh the runtime preference page, which is actually 2 layers lower on the UI call stack, which simply freezes the UI entirely. Even if i could fix all that, I could maybe arrange a way to get a list of RuntimeDefinition objects that were found during scanning, but I wouldn't be able to get a list of wst.server runtimes that were found, since that's not part of the jbt runtime detection API. I had also considered simply firing a job to open the dialog, but the original wtp runtiem pref page will open an error message if no runtimes are found. So having an error message show up while we're showing up the jbt runtime detection page wouldn't work here either. > Make runtime detection available from server view ? > --------------------------------------------------- > > Key: JBIDE-19784 > URL: https://issues.jboss.org/browse/JBIDE-19784 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > runtime detection is great but it's rather hidden. > Idea is to add a search glass to server view to trigger runtime detection. > Wdyt? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19887) BRMS and Fuse examples should be hidden if Integration Stack is not available

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19887?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19887. --------------------------------- Resolution: Done Solution implemented in master > BRMS and Fuse examples should be hidden if Integration Stack is not available > ----------------------------------------------------------------------------- > > Key: JBIDE-19887 > URL: https://issues.jboss.org/browse/JBIDE-19887 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > > For BRMS and Fuse examples, the connectors requirements would let a user believe the proper features can be installed, but this is only true if the integration stack is available. If it's not, then an error would pop up as the missing connectors would not be installable. > We could check if jboss.discovery.site.integration-stack.url is empty and hide all examples containing a BRMS or FUSE tag -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 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 May 2015