February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10963) Visual Editor Component N&N for 3.3.0.Beta1

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-10963: ---------------------------------------- Summary: Visual Editor Component N&N for 3.3.0.Beta1 Key: JBIDE-10963 URL: https://issues.jboss.org/browse/JBIDE-10963 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core, Visual Page Editor Templates Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.0.M5 labels = new_and_noteworthy AND project="JBIDE" AND fixVersion="3.3.0.M3" AND (component = "Visual Page Editor core" or component="Visual Page Editor Templates") -- 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

12 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9581) Create vanilla Seam getting started project

by Nick Boldt (JIRA)

Create vanilla Seam getting started project ------------------------------------------- Key: JBIDE-9581 URL: https://issues.jboss.org/browse/JBIDE-9581 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 3.3.0.M4 (From JBDS-1814 - see https://issues.jboss.org/browse/JBDS-1814?focusedCommentId=12623742&page=...) Concerning the Getting Started Guide content: * for Tools 3.3/JBDS 5, we will want to have a vanilla EE6 getting started project as well as the Seam one. Those project templates are spelled out in the JBDS 5.0 planning docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
9
0 / 0

[JBoss JIRA] (JBIDE-10339) after installing JBT Abridged cateogy (including m2e connectors) lots of console errors logged

by Nick Boldt (Created) (JIRA)

after installing JBT Abridged cateogy (including m2e connectors) lots of console errors logged ---------------------------------------------------------------------------------------------- Key: JBIDE-10339 URL: https://issues.jboss.org/browse/JBIDE-10339 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven, updatesite, UpStream Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 3.3.0.Beta1 See parent jira JBIDE-10336 for steps to reproduce. Full log is here: https://issues.jboss.org/secure/attachment/12349551/eclipse.log.Sun_Dec4_... This could be an upstream issue, but I wanted to make sure you were aware of it in case it was because of something we're doing w/ m2e on first startup of JBT after install. Or perhaps because of a missing dependency? -- 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

12 years, 4 months

5
9
0 / 0

[JBoss JIRA] (JBIDE-9875) Ideas about publish ui for openshift servers

by Max Rydahl Andersen (Created) (JIRA)

Ideas about publish ui for openshift servers -------------------------------------------- Key: JBIDE-9875 URL: https://issues.jboss.org/browse/JBIDE-9875 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, openshift Reporter: Max Rydahl Andersen Assignee: Rob Stryker Attachments: openshift_publishoptions.bmml Mock (see attached) for how to present the various commit/push options. -- 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

12 years, 4 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-10690) deprecate & remove all refs to ~/trunk/build/build.xml

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10690: ---------------------------------- Summary: deprecate & remove all refs to ~/trunk/build/build.xml Key: JBIDE-10690 URL: https://issues.jboss.org/browse/JBIDE-10690 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 Pretty sure this old ant script is no longer needed. It should be removed, albeit carefully. -- 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

12 years, 4 months

2
15
0 / 0

[JBoss JIRA] (JBIDE-10965) add JSLint to JBT/JBDS Central

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10965: ---------------------------------- Summary: add JSLint to JBT/JBDS Central Key: JBIDE-10965 URL: https://issues.jboss.org/browse/JBIDE-10965 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, updatesite, UpStream Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 JSLint is in JBDS Extras. It should also be in both JBT (Core) and JBDS (Core) Central. -- 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

12 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9801) CDI Searcher doesn't look for beans in dependent projects

by Alexey Kazakov (JIRA)

CDI Searcher doesn't look for beans in dependent projects --------------------------------------------------------- Key: JBIDE-9801 URL: https://issues.jboss.org/browse/JBIDE-9801 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M4 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M4 EXECUTE: Create two CDI projects: ProjectA and ProjectB. ProjectB depends on ProjectA. EXECUTE: Create a bean in ProjectA: {code} @Named("cdiBean") public class CDIBeanTest { } {code} EXECUTE: Create another bean in ProjectB: {code} public class TestBean { @Inject @Named("cdiBean") Object foo; } {code} EXECUTE: Select CDIBeanTest class name in CDIBeanTest.java and press Ctrl+Shift+G ASSERT: TestBean.foo should be found as an injection point which gets the wanted bean. Now it's working only if you have both beans in the same project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
7
0 / 0

[JBoss JIRA] (JBIDE-10564) Open CDI Named Bean Toolbar button and navigaton Menu item is always visible (even if no CDI-related perspective is activated)

by Victor Rubezhny (Created) (JIRA)

Open CDI Named Bean Toolbar button and navigaton Menu item is always visible (even if no CDI-related perspective is activated) ------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-10564 URL: https://issues.jboss.org/browse/JBIDE-10564 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.3.0.Beta1 Open CDI Named Bean Toolbar button and navigaton Menu item is always visible. Even if CDI-related perspectives are closed. It should be visible when: - JBoss Perspective is active - JEE Perspective is active - Debug Perspective is active -- 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

12 years, 4 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10791) Null Pointer Exception in CDIProject class

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-10791: ------------------------------------- Summary: Null Pointer Exception in CDIProject class Key: JBIDE-10791 URL: https://issues.jboss.org/browse/JBIDE-10791 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 Test case: EXECUTE: 1. Create CDI Project 2. Create New CDI Qualifier: {code} import static java.lang.annotation.ElementType.FIELD; import static java.lang.annotation.ElementType.METHOD; import static java.lang.annotation.ElementType.PARAMETER; import static java.lang.annotation.ElementType.TYPE; import static java.lang.annotation.RetentionPolicy.RUNTIME; import java.lang.annotation.Documented; import java.lang.annotation.Retention; import java.lang.annotation.Target; import javax.inject.Qualifier; @Target( { TYPE, METHOD, PARAMETER, FIELD }) @Retention(RUNTIME) @Documented @Qualifier @interface Chunky { boolean realChunky() default true; boolean unrealChunky(); int number() default 5; int size(); long long_number() default 1000; long long_size(); short short_number() default 2; short short_size(); float probability() default (float)13.5; float probability2(); double double_probability() default 27.3; double double_probability2(); char charachter() default 'E'; char charachter2(); byte bbb() default (byte)3; byte bebebe(); } {code} 3. Create interface: {code} interface Animal { } {code} 4. Create CDI Bean: {code} @Chunky(bebebe = 10, charachter2 = 10, double_probability2 = 10, long_size = 10, probability2 = 10, short_size = 10, size = 10, unrealChunky = false) class Sheep implements Animal { } {code} 4. Create class: {code} import javax.inject.Inject; public class Farm_Broken1 { @SuppressWarnings("unused") @Inject private Animal animal; } {code} 5. Build project FAIL: org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.internal.core.impl.CDIProject.getAnnotationDeclarationKey(CDIProject.java:630) at org.jboss.tools.cdi.internal.core.impl.CDIProject.getAnnotationDeclarationKey(CDIProject.java:598) at org.jboss.tools.cdi.internal.core.impl.CDIProject.areMatchingQualifiers(CDIProject.java:517) at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:383) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1617) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:617) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:509) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:381) at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:116) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) -- 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

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10425) Sometimes, the 'JAX-RS REST Web Services' node remains in a 'Building..' state

by Xavier Coulon (Created) (JIRA)

Sometimes, the 'JAX-RS REST Web Services' node remains in a 'Building..' state ------------------------------------------------------------------------------ Key: JBIDE-10425 URL: https://issues.jboss.org/browse/JBIDE-10425 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Minor Fix For: 3.3.0.Beta1 This seems to happen only at the workbench start and only if the jax-rs metamodel is empty -> the UI is not notified of the build end because there is not element to display on the UI :-( A 'clean' build solves the issue and restore the project explorer view in its expected state, though.. Solution: should force the UI notification at the end of a 'full build' even if nothing needs to be displayed. -- 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

12 years, 4 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012