December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18934) Arquillian New and Noteworthy for 4.2.1.Final

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18934?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-18934: ------------------------------------- Assignee: Alexey Kazakov (was: Snjezana Peco) Could you, please, review the PR? > Arquillian New and Noteworthy for 4.2.1.Final > --------------------------------------------- > > Key: JBIDE-18934 > URL: https://issues.jboss.org/browse/JBIDE-18934 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.2.1.Final > > > This [query|https://issues.jboss.org/issues/?jql=((project%20in%20(JBDS)%20and%...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=((project%20in%20(JBDS)%20and%...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian 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.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-18711: ------------------------------------- [~vineet.reynolds] QE is verifying each resolved Jira so once JBIDE-18952 is resolved and build of particular version is available for QE it will be verified > Cordova plugin addition and removal fails when config.xml is in a linked folder > ------------------------------------------------------------------------------- > > Key: JBIDE-18711 > URL: https://issues.jboss.org/browse/JBIDE-18711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace). > This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications. > To verify > 1. create a new project > 2. copy www folder to an alternate location > 3. remove www folder > 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location) > 5. add cordova plugins to the project. [Check they are added] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18952) Project Import is not possible when 'www' is an Eclipse linked folder

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18952?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-18952: ------------------------------------ Steps to Reproduce: 1. Create a Cordova project where www is an Eclipse linked folder. 2. Close the project and re-import it. Re-import is not possible, as the Cordova project is not listed in the Project Import dialog. Use TicketMonster 2.7.0.ER2 as an example: http://download.devel.redhat.com/composes/candidates/JBWFK/2.7.0.ER2/jbos... was: 1. Create a Cordova project where www is an Eclipse linked folder. 2. Close the project and re-import it. Re-import is not possible, as the Cordova project is not listed in the Project Import dialog. > Project Import is not possible when 'www' is an Eclipse linked folder > --------------------------------------------------------------------- > > Key: JBIDE-18952 > URL: https://issues.jboss.org/browse/JBIDE-18952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Reporter: Vineet Reynolds > > Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. It seems like Eclipse linked folders are not resolved in the project import dialog. > Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18952) Project Import is not possible when 'www' is an Eclipse linked folder

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18952?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-18952: ------------------------------------ Steps to Reproduce: 1. Create a Cordova project where www is an Eclipse linked folder. 2. Close the project and re-import it. Re-import is not possible, as the Cordova project is not listed in the Project Import dialog. was: 1. Create a Cordova project where www is an Eclipse linked folder. 2. Close the project and re-import it. Re-import is not possible. > Project Import is not possible when 'www' is an Eclipse linked folder > --------------------------------------------------------------------- > > Key: JBIDE-18952 > URL: https://issues.jboss.org/browse/JBIDE-18952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Reporter: Vineet Reynolds > > Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. It seems like Eclipse linked folders are not resolved in the project import dialog. > Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18262) exception on startup

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18262. ------------------------------ I'm closing this one. If you experience this issue, feel free to reopen. > exception on startup > -------------------- > > Key: JBIDE-18262 > URL: https://issues.jboss.org/browse/JBIDE-18262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Labels: need-info, respin-b > Fix For: 4.2.0.CR1 > > > not sure what causes it but I'm getting this: > java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1" > at org.osgi.framework.Version.validate(Version.java:205) > at org.osgi.framework.Version.<init>(Version.java:156) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-18711: ----------------------------------------- [~tkriz], [~vpakan], please also verify JBIDE-18952 (a related issue involving import of projects with linked folders) in 4.2.1. This is a separate use-case though. > Cordova plugin addition and removal fails when config.xml is in a linked folder > ------------------------------------------------------------------------------- > > Key: JBIDE-18711 > URL: https://issues.jboss.org/browse/JBIDE-18711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace). > This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications. > To verify > 1. create a new project > 2. copy www folder to an alternate location > 3. remove www folder > 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location) > 5. add cordova plugins to the project. [Check they are added] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18952) Project Import is not possible when 'www' is an Eclipse linked folder

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18952?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-18952: ------------------------------------ Description: Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. It seems like Eclipse linked folders are not resolved in the project import dialog. Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. was: Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. > Project Import is not possible when 'www' is an Eclipse linked folder > --------------------------------------------------------------------- > > Key: JBIDE-18952 > URL: https://issues.jboss.org/browse/JBIDE-18952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Reporter: Vineet Reynolds > > Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. It seems like Eclipse linked folders are not resolved in the project import dialog. > Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18952) Project Import is not possible when 'www' is an Eclipse linked folder

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-18952: --------------------------------------- Summary: Project Import is not possible when 'www' is an Eclipse linked folder Key: JBIDE-18952 URL: https://issues.jboss.org/browse/JBIDE-18952 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.Final Reporter: Vineet Reynolds Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18919) Weak performance on Software/Update tab features loading

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18919?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18919: ----------------------------------- Fix Version/s: 4.2.2.Final 4.3.0.Alpha1 (was: 4.2.1.Final) > Weak performance on Software/Update tab features loading > -------------------------------------------------------- > > Key: JBIDE-18919 > URL: https://issues.jboss.org/browse/JBIDE-18919 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > It takes about ~1 minute to load content into Software/Update tab in central. > Some of my colleagues noticed this too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3249: ---------------------------------- Could someone please define the following subjective terms: * easily - what is considered easy? * install - do you mean an installer jar? Marketplace entry? Central connectors? * unnecessary - what do you consider unnecessary? * intermediate - which steps are intermediate? Maybe a user story / steps to reproduce the BAD workflow would be useful here, as well as a suggested vision for a GOOD workflow. > As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3249 > URL: https://issues.jboss.org/browse/JBDS-3249 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, integration-platform, updatesite > Reporter: Max Rydahl Andersen > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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