September 2012 - jbosstools-issues

[JBoss JIRA] (JBDS-2292) JBoss Central appears in small dialog on startup screen - JBDS 6.0.alpha2

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2292: ---------------------------------- Summary: JBoss Central appears in small dialog on startup screen - JBDS 6.0.alpha2 Key: JBDS-2292 URL: https://issues.jboss.org/browse/JBDS-2292 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.0.0.Alpha2 Environment: Version: 6.0.0.Alpha2 Build id: Alpha2-v20120924-2110-B28 Build date: 20120924-2110 http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.0.Alpha2a.e... Reporter: Len DiMaggio Assignee: Snjezana Peco Priority: Blocker Fix For: 6.0.0.Alpha2 See the attached 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

13 years, 4 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12587) JBTValidationException while removing CDI support

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-12587: ------------------------------------- Summary: JBTValidationException while removing CDI support Key: JBIDE-12587 URL: https://issues.jboss.org/browse/JBIDE-12587 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 4.0.0.Alpha1 Reporter: Daniel Azarov Assignee: Alexey Kazakov EXECUTE: 1. Create CDI Project 2. Create Bean: {code} package com.test; import javax.enterprise.inject.Produces; import javax.inject.Inject; public class Test { @Inject String injectionPoint; @Produces public String value1() { return null; } @Produces public String value2() { return null; } } {code} 3. Open Test bean in Java Editor 4. Remove CDI support FAIL: {code} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:179) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:198) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:191) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:232) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.internal.core.impl.CDIProjectAsYouType.<init>(CDIProjectAsYouType.java:86) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:507) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:174) ... 10 more {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

13 years, 4 months

5
6
0 / 0

[JBoss JIRA] (JBIDE-12711) Wizard suggests to open README.md of another project

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-12711: ---------------------------------------- Summary: Wizard suggests to open README.md of another project Key: JBIDE-12711 URL: https://issues.jboss.org/browse/JBIDE-12711 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.0.0.Alpha2 Reporter: Rastislav Wagner Assignee: Snjezana Peco Fix For: 4.0.0.Beta1 -- 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

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12721) Deleted project cannot be managed by Project Archives view anymore

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12721: ----------------------------------------- Summary: Deleted project cannot be managed by Project Archives view anymore Key: JBIDE-12721 URL: https://issues.jboss.org/browse/JBIDE-12721 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Alpha2 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Priority: Critical Fix For: 4.0.0.Alpha2 This issue was caught by swtbot tests, where importing and deleting the same projects is done very often -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12408) Trying to deploy a developed maven app to OpenShift doesn't work

by Isaac Rooskov (JIRA)

Isaac Rooskov created JBIDE-12408: ------------------------------------- Summary: Trying to deploy a developed maven app to OpenShift doesn't work Key: JBIDE-12408 URL: https://issues.jboss.org/browse/JBIDE-12408 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Final Reporter: Joel Tosi Assignee: Andre Dietisheim Priority: Critical *From Bugzilla* Description of problem: We were running an open source development day in Cincinnati. As part of it, the attendees were given a maven project to import into JBDS and then deploy to OpenShift. When a user tried to deploy to OpenShift, they kept getting validation errors in JBDS. Creating a new OpenShift application in JBDS and then importing the project worked fine Version-Release number of selected component (if applicable): JBDS 5 Beta 3 (universal installer) How reproducible: Import a maven project Add OpenShift Server Try to deploy to OpenShift Steps to Reproduce: 1. Import a maven project 2. Add OpenShift Server to servers 3. Try to deploy maven project to OpenShift Actual results: Validation errors Expected results: Application deploys Isaac's note: Joel Tosi was the reporter in bugzilla so setting him as the reporter here -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12541) Add requirement for m2e-wtp for examples

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-12541: ---------------------------------------- Summary: Add requirement for m2e-wtp for examples Key: JBIDE-12541 URL: https://issues.jboss.org/browse/JBIDE-12541 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: project-examples Affects Versions: 4.0.0.Alpha1 Reporter: Rastislav Wagner Assignee: Snjezana Peco Fix For: 4.0.0.Alpha2 Examples now have requirement for m2eclipse-wtp, we should change this condition to require m2eclipse-wtp or m2e-wtp. -- 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

13 years, 4 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-12495) Weird behaviour when deploying archives

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12495: ----------------------------------------- Summary: Weird behaviour when deploying archives Key: JBIDE-12495 URL: https://issues.jboss.org/browse/JBIDE-12495 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.M1 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 4.0.0.M1 I am facing very weird behaviour when trying to deploy archives into JBoss AS 7. To reproduce this issue, you will need two fresh workspaces and the newest archive trunk build installed in eclipse juno. -- 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, 4 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-12659) new fileset wizard preview fails

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12659: ----------------------------------- Summary: new fileset wizard preview fails Key: JBIDE-12659 URL: https://issues.jboss.org/browse/JBIDE-12659 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.Alpha2 The preview always shows up blank -- 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

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-12336) org.jboss.ide.eclipse.archives.core bundles some old/obselete jars

by Gerard Ryan (JIRA)

Gerard Ryan created JBIDE-12336: ----------------------------------- Summary: org.jboss.ide.eclipse.archives.core bundles some old/obselete jars Key: JBIDE-12336 URL: https://issues.jboss.org/browse/JBIDE-12336 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Environment: Fedora Reporter: Gerard Ryan Assignee: Rob Stryker As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for Fedora, and the bundled jars in the lib/ directory of the org.jboss.ide.eclipse.archives.core plugin are causing me some trouble. The root of the issue is that Fedora packages disallow bundled dependencies; and when new packages are being created, only the latest version of the software must be packaged. This was not too much of a problem for the truezip dependency, even though some things did need to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2]. It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen any activity in quite a while, and it depends on the seemingly obselete (this may not be the best description) jboss-reflect. jboss-reflect, in its current state, cannot be included in Fedora for reasons listed in the review for the package that I proposed for it[3]. I'm trying to find the optimal solution to this problem. What I would really like to know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there anything else that would work as a dropin replacement, or any other workaround possible? Since development of jbossxb seems dormant, not having to package it for Fedora would be the best solution for me. I realise that it may be necessary though, but I thought I would bring it up here, before I go looking for the jbossxb developers, in case my best case scenario is a possibility! Thanks in advance for any insight/help you can provide! :) [1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html [2] http://truezip.java.net/migration.html [3] https://bugzilla.redhat.com/show_bug.cgi?id=836404 -- 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, 4 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-11371) Move JBoss Quickstarts from developers workspace in svn somewhere else (maybe download.jboss.org/jbosstools/examples)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-11371: ---------------------------------- Summary: Move JBoss Quickstarts from developers workspace in svn somewhere else (maybe download.jboss.org/jbosstools/examples) Key: JBIDE-11371 URL: https://issues.jboss.org/browse/JBIDE-11371 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, project-examples Affects Versions: 3.3.0.Beta1 Reporter: Radim Hopp Assignee: Snjezana Peco Fix For: 3.3.0.Beta2, 3.3.0.Beta3 Now, quicksarts are being downloaded from http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/jbossas7-examp.... Wouldn't be better to have them somewhere else? Maybe put the quickstarts to https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool... for automatic push to download.jboss.org? -- 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, 4 months

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