October 2014 - jbosstools-issues - Jboss List Archives

[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

3 weeks, 5 days

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, 3 weeks

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 weeks

3
3
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 weeks

3
7
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by William DeCoste (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] William DeCoste commented on JBIDE-18723: ----------------------------------------- Is this sufficient? https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html... > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by William DeCoste (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] William DeCoste commented on JBIDE-18723: ----------------------------------------- Sounds reasonable to me! I'll work it from the OpenShift side and respond asap. > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18723: --------------------------------------------- the documentation we got states there is no welldefined format we can rely on to do this reliably since the format is highly dependent on the cartridge running on the server. If you have info on how we can make these reliable and not having to implement multiple variations and updates every time an update is out for the cartridge we are definitely interested. > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by William DeCoste (JIRA)

William DeCoste created JBIDE-18723: --------------------------------------- Summary: Binary deployment from current JBDS state Key: JBIDE-18723 URL: https://issues.jboss.org/browse/JBIDE-18723 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.2.0.Final Reporter: William DeCoste Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3193) JBDS 8 generates .attach_pid* file if IDE is started with a new workspace

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3193?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3193: -------------------------------- Fix Version/s: 9.0.x > JBDS 8 generates .attach_pid* file if IDE is started with a new workspace > ------------------------------------------------------------------------- > > Key: JBDS-3193 > URL: https://issues.jboss.org/browse/JBDS-3193 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.0.0.GA > Environment: Fedora 20 x86_64 + Java 1.8.0_20 + JBDS 8.0.0.GA > Reporter: Andrej Podhradsky > Priority: Minor > Labels: fedora, java8 > Fix For: 9.0.x > > > JBDS 8 always generates .attach_pidXXXX. The file is empty and it is generated in the folder from where you executed the JBDS. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3193) JBDS 8 generates .attach_pid* file if IDE is started with a new workspace

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3193?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3193: -------------------------------- Labels: fedora java8 (was: ) > JBDS 8 generates .attach_pid* file if IDE is started with a new workspace > ------------------------------------------------------------------------- > > Key: JBDS-3193 > URL: https://issues.jboss.org/browse/JBDS-3193 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.0.0.GA > Environment: Fedora 20 x86_64 + Java 1.8.0_20 + JBDS 8.0.0.GA > Reporter: Andrej Podhradsky > Priority: Minor > Labels: fedora, java8 > > JBDS 8 always generates .attach_pidXXXX. The file is empty and it is generated in the folder from where you executed the JBDS. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 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 2014