April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19627) JBoss Tools disables ability to select workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19627: ----------------------------------- Summary: JBoss Tools disables ability to select workspace (was: JBDS doesn't prompt for workspace) > JBoss Tools disables ability to select workspace > ------------------------------------------------ > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19627) JBDS doesn't prompt for workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-19627 at 4/16/15 2:45 PM: ----------------------------------------------------------------- I could reproduce it with JBoss Tools: * Get Mars M6 * Start: it asks for workspace * Restart: it asks for workspace * Install JBoss Tools Abrigged from snapshot build ( http://download.jboss.org/jbosstools/updates/nightly/mars/ ) * Restart: it doesn't ask for workspace, and selected $HOME/workspace as default. It might be an issue with some p2 touchpoint? /cc [~nickboldt] [~fbricon] was (Author: mickael_istria): I could reproduce it with JBDS Abbriged: * Get Mars M6 * Start: it asks for workspace * Restart: it asks for workspace * Install JBoss Tools Abbriged from Nighly * Restart: it doesn't ask for workspace, and selected $HOME/workspace as default. It might be an issue with some p2 touchpoint? /cc [~nickboldt] [~fbricon] > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19627) JBDS doesn't prompt for workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19627: ----------------------------------- Priority: Blocker (was: Major) > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19627) JBDS doesn't prompt for workspace

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19627: ------------------------------------- I don't know what a p2 touchpoint is TBH :-) > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19627) JBDS doesn't prompt for workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19627: ---------------------------------------- I could reproduce it with JBDS Abbriged: * Get Mars M6 * Start: it asks for workspace * Restart: it asks for workspace * Install JBoss Tools Abbriged from Nighly * Restart: it doesn't ask for workspace, and selected $HOME/workspace as default. It might be an issue with some p2 touchpoint? /cc [~nickboldt] [~fbricon] > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19627) JBDS doesn't prompt for workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19627?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19627: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-19627 (was: JBDS-3406) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: (was: 9.0.0.Alpha2) Component/s: (was: installer) Fix Version/s: 4.3.0.Alpha2 (was: 9.0.0.Alpha2) Docs QE Status: (was: NEW) > JBDS doesn't prompt for workspace > --------------------------------- > > Key: JBIDE-19627 > URL: https://issues.jboss.org/browse/JBIDE-19627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Linux, Mac OS X > Reporter: Pavol Srna > Fix For: 4.3.0.Alpha2 > > > When you install JBDS 9.0.0.Alpha2 nightly (including Eclipse Mars M6) and then you start it, it won't ask you for workspace and simply use the default. This applies to OS X. > This is probably caused by the changes in https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18096: -------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > could not complete update project configuration - illegalargumentexception > -------------------------------------------------------------------------- > > Key: JBIDE-18096 > URL: https://issues.jboss.org/browse/JBIDE-18096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.3.0.Beta1 > > > while trying to fix import of javaee-samples I bumped into this happening when running update project configuration. > java.lang.IllegalArgumentException > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150) > at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93) > at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318) > at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > It happened on ~100 projects so was quite invasive ;/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-19338 at 4/16/15 2:38 PM: ---------------------------------------------------------------- I tried jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar. Tested on Windows 8 and Mac. But I needed to install "JBoss Tools Java Standard Tools AngularJS" from update site https://devstudio.redhat.com/updates/9.0.0/jboss-devstudio-9.0.0.Alpha1-u... (because of JBDS-3413) Everything works just fine. was (Author: dazarov): I tried jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar. But I needed to install "JBoss Tools Java Standard Tools AngularJS" from update site https://devstudio.redhat.com/updates/9.0.0/jboss-devstudio-9.0.0.Alpha1-u... (because of JBDS-3413) Everything works just fine. > Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19338 > URL: https://issues.jboss.org/browse/JBIDE-19338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Check the button "Show only palette groups for which libraries are defined on the page" > ASSERT: No Palette groups are visible in HTML 5 Palette > 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: Following palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 4. Check the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed > 5. Uncheck the button "Show only palette groups for which libraries are defined on the page" > ERROR: Ionic palette is not displayed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19618) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19618?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19618: ---------------------------------------- Local build fails: {code} [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... [INFO] Adding repository http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'jbosstools-base' from location http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas...: No repository found at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas.... -> [Help 1] {code} > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JST] > -------------------------------------------------- > > Key: JBIDE-19618 > URL: https://issues.jboss.org/browse/JBIDE-19618 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19600) HTML5 Palette: Java crash while attempt to create WebKit browser on Windows

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19600?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19600: --------------------------------------- Tested on Mac, works fine > HTML5 Palette: Java crash while attempt to create WebKit browser on Windows > --------------------------------------------------------------------------- > > Key: JBIDE-19600 > URL: https://issues.jboss.org/browse/JBIDE-19600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: Windows 8, eclipse-SDK-4.5M6-win32 Mars (32bit) > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > if one of the following wizards run first: > NewRangeSliderWizardPage > NewTableWizardPage (html) > NewTableWizardPage (jquery) > NewTabsWizardPage > NewHeadingWizardPage > NewPanelWizardPage > NewMeterWizardPage > NewSpinnerWizardPage > Java Crashes: > {code} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c0e58c, pid=8152, tid=4044 > # > # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15) > # Java VM: Java HotSpot(TM) Client VM (24.79-b02 mixed mode windows-x86 ) > # Problematic frame: > # C 0x00c0e58c > # > # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows > # > # An error report file with more information is saved as: > # C:\Users\Daniil\Java\eclipse-SDK-4.5M6 Mars\hs_err_pid8152.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 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 April 2015