November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15677) Update to VJET 0.10.0.201309201624 in Central (for Beta1)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15677?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15677: ---------------------------------------- Description: VJET is a nightly build currently in Central - currently at VJET 0.10.??? Latest mirror is available here http://download.jboss.org/jbosstools/updates/requirements/vjet/0.10.0.201... was: As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. Latest mirror: http://download.jboss.org/jbosstools/updates/requirements/vjet/0.10.0.201... > Update to VJET 0.10.0.201309201624 in Central (for Beta1) > --------------------------------------------------------- > > Key: JBIDE-15677 > URL: https://issues.jboss.org/browse/JBIDE-15677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Beta1 > > > VJET is a nightly build currently in Central - currently at VJET 0.10.??? > Latest mirror is available here http://download.jboss.org/jbosstools/updates/requirements/vjet/0.10.0.201... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14122) Add VJET 0.10.0.201303191704 to Central (for 4.1.0.Beta1)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14122. ------------------------------ Resolution: Done > Add VJET 0.10.0.201303191704 to Central (for 4.1.0.Beta1) > --------------------------------------------------------- > > Key: JBIDE-14122 > URL: https://issues.jboss.org/browse/JBIDE-14122 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png > > > We should provide an ability to install VJET v.0.10 through Central > The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released > The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet: > {code:title=Orbit bundles for VJET} > <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/> > <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/> > <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/> > <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/> > <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/> > <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/> > <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/> > <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/> > <unit id="org.apache.xerces" version="2.9.0.v201101211617"/> > <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/> > <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/> > <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/> > <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/> > <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/> > <unit id="javax.xml" version="1.3.4.v201005080400"/> > <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/> > <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/> > {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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14764) Update to VJET 0.10.0.201307160408 in Central (Alpha2)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14764. ------------------------------ Resolution: Done > Update to VJET 0.10.0.201307160408 in Central (Alpha2) > ------------------------------------------------------ > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Alpha2 > > Attachments: JBIDE14764.png > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15864) Add dialog displaying errors when Plugins are added to Hybrid Mobile Project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15864?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15864: -------------------------------------- What causes the confusion?. Is it the dependencies of a plugin being installed or because what is displayed on the wizard is the ID and on the project explorer we display the name of a plugin > Add dialog displaying errors when Plugins are added to Hybrid Mobile Project > ---------------------------------------------------------------------------- > > Key: JBIDE-15864 > URL: https://issues.jboss.org/browse/JBIDE-15864 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Vlado Pakan > Fix For: 4.1.1.CR1 > > > Sometimes when adding Plugins to Hybrid Mobile project via Cordova Configuration Editor some errors are happening and added Plugins are different than Plugins selected to be added. This is very confusing for user. Would be nice to have some dialog explaining errors which happened while adding Plugins so user know what has happened -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15677) Update to VJET 0.10.0.201309201624 in Central (for Beta1)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15677?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15677: ------------------------------- Summary: Update to VJET 0.10.0.201309201624 in Central (for Beta1) (was: Update VJET in Central (Beta1)) > Update to VJET 0.10.0.201309201624 in Central (for Beta1) > --------------------------------------------------------- > > Key: JBIDE-15677 > URL: https://issues.jboss.org/browse/JBIDE-15677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Beta1 > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. > Latest mirror: http://download.jboss.org/jbosstools/updates/requirements/vjet/0.10.0.201... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14764) Update to VJET 0.10.0.201307160408 in Central (Alpha2)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14764: ------------------------------- Summary: Update to VJET 0.10.0.201307160408 in Central (Alpha2) (was: Update VJET in Central) > Update to VJET 0.10.0.201307160408 in Central (Alpha2) > ------------------------------------------------------ > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Alpha2 > > Attachments: JBIDE14764.png > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2691: ------------------------------ Fix Version/s: 8.0.0.GA > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 8.0.0.GA > > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2691: ------------------------------ Component/s: upstream > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2691) Incomplete build path for Spring Web Project when Spring plugins are installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2691?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2691: ----------------------------------- I opened https://issuetracker.springsource.com/browse/STS-3602 upstream > Incomplete build path for Spring Web Project when Spring plugins are installed > ------------------------------------------------------------------------------ > > Key: JBDS-2691 > URL: https://issues.jboss.org/browse/JBDS-2691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies, central, upstream > Affects Versions: 7.0.0.CR1 > Environment: JBDS 7.0.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Attachments: build-path-is-incomplete.png > > > Build path is incomplete. Cannot find class file for javax/servlet/ServletContext -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15635) Null Pointer when code assumes runtime type cannot be null

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15635: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.1.CR1) > Null Pointer when code assumes runtime type cannot be null > ---------------------------------------------------------- > > Key: JBIDE-15635 > URL: https://issues.jboss.org/browse/JBIDE-15635 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Mac OSX 10.8.5 > Oracle JDK 1.7.0_40 > JBoss Developer Studio > Version: 7.0.1.GA > Build id: GA-v20130930-2238-B7 > Build date: 20130930-2238 > Reporter: Cojan van Ballegooijen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png > > > - Installed JBoss Developer 7.0.0GA using > - Upgraded to 7.0.1GA > - Starting JBoss Developer Studio shows the following error window > An internal error occurred during: "Refreshing JBoss Tutorials...". > java.lang.NullPointerException > - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet" > - Starting a new Java EE Web project results in the following error > An error has occurred. See error log for more details. > java.lang.NullPointerException > No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files. > Found .log in ~/workspace/.metadata > !SESSION 2013-10-08 16:14:47.792 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation > !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252 > !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences > !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for ALT+COMMAND+Z: > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean, > Open CDI Named Bean, > Category(org.eclipse.ui.category.navigate,Navigate,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu, > Shows the Surround With quick menu, > Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for COMMAND+SHIFT+F10: > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service, > Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class., > Category(org.eclipse.ui.category.file,File,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu, > Show the system menu, > Category(org.eclipse.ui.category.window,Window,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158) > 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:248) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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, 5 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 November 2013