September 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-165: ------------------------------------ Affects Version/s: 4.1.2 > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Reporter: Andrej Podhradsky > Priority: Blocker > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15398: ------------------------------------- I will try to import in Eclipse Java version (no WTP, no JBT), Eclipse JavaEE (no JBT) and Eclipse JavaEE + CDI tools to compare build times > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-15398: ----------------------------------- Summary: CDI Builder is sloooow Key: JBIDE-15398 URL: https://issues.jboss.org/browse/JBIDE-15398 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.1.0.Final Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 Reporter: Fred Bricon After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2740: ---------------------------------------- [~burrsutter] yes "namespace" and "domain name" are equivalent. You can also see this in the Web-UI: !namespace.png! > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > Attachments: namespace.png > > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2740: ----------------------------------- Attachment: namespace.png > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > Attachments: namespace.png > > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2750) cannot log into OpenShift (even though credentials are valid)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2750?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2750: ---------------------------------------- I afaik dont have the perms to move, at least I didn't spot a corresponding field when editing. > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBDS-2750 > URL: https://issues.jboss.org/browse/JBDS-2750 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 6.0.x > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15155) LiveReload is not working with internal Web Browser

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15155: ------------------------------------- Test results with fresh workspace without running Browsersim: URL: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ Internal JBDS browser: no changes displayed after modification External browser: no changes displayed after modification URL: http://localhost:<proxy-port>/jboss-as-kitchensink-html5-mobile/ Internal JBDS browser: no changes displayed after modification External browser: changes are displayed after modification > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Vlado Pakan > Fix For: 4.1.x > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11319: ---------------------------------------- Fix for javaee build: https://github.com/jbosstools/jbosstools-javaee/pull/138 > Use Eclipse-SourceReferences > ---------------------------- > > Key: JBIDE-11319 > URL: https://issues.jboss.org/browse/JBIDE-11319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.0.Alpha1 > > > In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15368: ------------------------------------- IJBossToolingConstants is not truly intended to be implemented by clients, however, it contains a very very large number of constants, and some clients do implement it for convenience. To fix this specific issue, we will need to add @noimplement to IJBossToolingConstants and allow the warnings to propagate. Problem is this will make dev environment fail to compile. > jbosstools-server has API Compatibility problem > ----------------------------------------------- > > Key: JBIDE-15368 > URL: https://issues.jboss.org/browse/JBIDE-15368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Priority: Blocker > Labels: api-compatibility > Fix For: 4.1.1.Alpha1 > > > Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: > "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". > According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 > || Interface change || Conditions || Compatibility || > |Add API field|If interface not implementable by Clients | Binary compatible| > |Add API field|If interface implementable by Clients| Breaks compatibility (2)| > (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14530) Support 'Arquillian Cruiser' in standard 'Outline' view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14530?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14530: --------------------------------------------- This would be nice, but because outlines can't be extended, I think better option is to have arquillian cruiser react to selections in java editor or possibly extend the outline in the project explorer where common navigator is present which might allow for this kind of extension ? > Support 'Arquillian Cruiser' in standard 'Outline' view > ------------------------------------------------------- > > Key: JBIDE-14530 > URL: https://issues.jboss.org/browse/JBIDE-14530 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.1.x > > > Would it be possible to extend the normal 'Outline' view to specially handle 'Deployment methods' and add the option to continue drilling down into the content of the defined archive? -- 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, 7 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 September 2013