June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2062) JSLint: jsLex app inconsistent behaviour

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBDS-2062: ------------------------------------ Summary: JSLint: jsLex app inconsistent behaviour Key: JBDS-2062 URL: https://issues.jboss.org/browse/JBDS-2062 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Beta1 Environment: JBDS 5.0.0.Beta1d Reporter: Stefan Bunciak Fix For: 5.0.0.Beta1 Clicked on <project> context menu -> 1) unzip jsLex then 2)Inject Performance Markers : * !jslint1.png|thumbnail! Clicked on <project> context menu -> 1) unzip jsLex then 2)Inject Performance Markers : * !jslint2.png|thumbnail! Do I miss something or is there a bug? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
17
0 / 0

[JBoss JIRA] (JBDS-2118) User is no longer (as of JBDS5 beta1) able to install multiple project examples at once

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2118: ---------------------------------- Summary: User is no longer (as of JBDS5 beta1) able to install multiple project examples at once Key: JBDS-2118 URL: https://issues.jboss.org/browse/JBDS-2118 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.Beta2, 5.0.0.Beta1, 5.0.0.Beta3 Environment: Version: 5.0.0.Beta3 Build id: v20120430-1703-H125-Beta3 Build date: 20120430-1703 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 5.0.0.GA This issue has been there since beta1 - installing example projects such as the ESB examples - must be done at a time. JBDS4 enabled the user to install multiple examples at once. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
9
0 / 0

[JBoss JIRA] (JBDS-2143) Inconsistency between build ID and install jar file name

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2143: ---------------------------------- Summary: Inconsistency between build ID and install jar file name Key: JBDS-2143 URL: https://issues.jboss.org/browse/JBDS-2143 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.GA Reporter: Len DiMaggio Assignee: Nick Boldt Fix For: LATER For beta3b, the 'about' dialog shows: Version: 5.0.0.Beta3 Build id: v20120514-2058-H159-Beta3 Build date: 20120514-2058 And the install jar file is named: jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201205141759M-H140-Beta3.jar Can we get the build id into the jar file name someday? Right now - the naming inconsistency can be confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBDS-1919) Uninstaller leaves behind empty jbdevstudio folder

by Nick Boldt (Created) (JIRA)

Uninstaller leaves behind empty jbdevstudio folder -------------------------------------------------- Key: JBDS-1919 URL: https://issues.jboss.org/browse/JBDS-1919 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 4.1.1.GA, 5.0.0.M4 Environment: Seen on Win7_64 w/ JDK 6u25 32-bit. May occur on other platforms too. Reporter: Nick Boldt Fix For: 5.0.0.Beta1 See JBDS-1918 for steps to repro. This might be an izpack bug or an installer/uninstaller config bug, but either way the install folder - though empty - persists after installation. If you double-click the uninstaller.jar, you'll end up with ~/jbdevstudio/ and ~/jbdevstudio/Uninstaller (both empty folders). If you run the uninstaller from the icon (having tweaked it as follows first), you'll get just the ~/jbdevstudio folder. {code} Target: "C:\Users\nboldt\jbdevstudio/Uninstaller\uninstaller.jar" Start in: (leave blank) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
9
0 / 0

[JBoss JIRA] (JBIDE-11432) NPE generating feature metadata / tycho bug?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11432: ---------------------------------- Summary: NPE generating feature metadata / tycho bug? Key: JBIDE-11432 URL: https://issues.jboss.org/browse/JBIDE-11432 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Mickael Istria Priority: Blocker Fix For: 3.3.0.Beta3 Consistently getting this failure for tests, jmx-bootstrap, and forge-bootstrap. {code} mvnn clean install -f build/pom.xml -Pdefault,local.site,tests [INFO] tests.all ......................................... SUCCESS [1:07.058s] [INFO] tests.plugins ..................................... SUCCESS [0.012s] [INFO] org.jboss.tools.tests ............................. SUCCESS [22.700s] [INFO] org.jboss.tools.ui.bot.ext ........................ SUCCESS [4.690s] [INFO] org.jboss.tools.ui.bot.ext.test ................... SUCCESS [0.333s] [INFO] tests.features .................................... SUCCESS [0.009s] [INFO] org.jboss.tools.test.feature ...................... FAILURE [0.300s] [INFO] tests.site ........................................ SKIPPED [INFO] org.jboss.tools.build ............................. SUCCESS [1.713s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10:48.118s [INFO] Finished at: Wed Mar 28 11:39:36 EDT 2012 [INFO] Final Memory: 39M/169M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:0.14.1:p2-metadata (default-p2-metadata) on project org.jboss.tools.test.feature: Execution default-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:0.14.1:p2-metadata failed. NullPointerException -> [Help 1] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
16
0 / 0

[JBoss JIRA] (JBIDE-11865) m2e-apt UI plugin missing provider and name

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11865: ---------------------------------- Summary: m2e-apt UI plugin missing provider and name Key: JBIDE-11865 URL: https://issues.jboss.org/browse/JBIDE-11865 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.CR1 !https://issues.jboss.org/secure/attachment/12354135/12354135_JBIDE11700-new-m2e-apt-connector-already-installed-in-JBDS.png! Probably just needs a tweak to the build.properties file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-1631) 3rd party cert: testng 6.0

by Nick Boldt (JIRA)

3rd party cert: testng 6.0 -------------------------- Key: JBDS-1631 URL: https://issues.jboss.org/browse/JBDS-1631 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Fix For: 5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1627) 3rd party certification for JBDS 5.x

by Nick Boldt (JIRA)

3rd party certification for JBDS 5.x ------------------------------------ Key: JBDS-1627 URL: https://issues.jboss.org/browse/JBDS-1627 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 4.x We should define what kind of certifications we want and then certify 3rd party plugins with JBDS Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees. For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] (JBDS-2196) Audit differences between Tycho-built product update site (.updatesite job) and PDE-built product update site (.product job)

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2196: -------------------------------- Summary: Audit differences between Tycho-built product update site (.updatesite job) and PDE-built product update site (.product job) Key: JBDS-2196 URL: https://issues.jboss.org/browse/JBDS-2196 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 5.0.0.CR1 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 5.0.0.GA Comparing the CR1a bits: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.CR1a.core... (built with .product job) vs. http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.CR1a.core... (build with .updatesite job) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11565) OpenShift fails to deploy a disconnected project

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11565: -------------------------------------- Summary: OpenShift fails to deploy a disconnected project Key: JBIDE-11565 URL: https://issues.jboss.org/browse/JBIDE-11565 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Stefan Bunciak I have failed to deploy a project which was previously deployed on OpenShift and then disconnected, so it was not versioned any more. Stack trace: {code} java.lang.NullPointerException at org.jboss.tools.openshift.egit.core.EGitUtils.getFailedUpdates(EGitUtils.java:568) at org.jboss.tools.openshift.egit.core.EGitUtils.getFailedUpdates(EGitUtils.java:563) at org.jboss.tools.openshift.egit.core.EGitUtils.getFailedUpdates(EGitUtils.java:557) at org.jboss.tools.openshift.egit.core.EGitUtils.hasFailedEntries(EGitUtils.java:551) at org.jboss.tools.openshift.egit.core.EGitUtils.push(EGitUtils.java:431) at org.jboss.tools.openshift.egit.core.EGitUtils.pushForce(EGitUtils.java:418) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.commitAndPushProject(ExpressPublishMethod.java:188) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishFinish(ExpressPublishMethod.java:70) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:88) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishFinish(DelegatingServerBehavior.java:140) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:974) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
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 June 2012