[JBoss JIRA] Created: (JBIDE-8736) Sometimes injections do not resolve to produced bean with restricted generic type
by Viacheslav Kabanovich (JIRA)
Sometimes injections do not resolve to produced bean with restricted generic type
---------------------------------------------------------------------------------
Key: JBIDE-8736
URL: https://issues.jboss.org/browse/JBIDE-8736
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M1
Injection point is not resolved in the following case:
public class Test {
@Produces @Typed(List.class)
private ArrayList<Boolean> producer = new ArrayList<Boolean>();
@Inject
List<Boolean> injected;
}
For the current implementation, it is important here that List and ArrayList are library types. If a generic type and subtype defined in local project are used, then injection is resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8790) Cannot find runtimes due to missing drools
by Lukas Jungmann (JIRA)
Cannot find runtimes due to missing drools
------------------------------------------
Key: JBIDE-8790
URL: https://issues.jboss.org/browse/JBIDE-8790
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.2.1.M1
Reporter: Lukas Jungmann
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.2.1.M1
-install JBT (All JBoss Tools 3.2.0) from http://download.jboss.org/jbosstools/builds/nightly/3.2_stable_branch/201...
-restart ide
-open Window -> Preferences and select JBoss Tools -> JBoss Tools Runtime
-add there some path
=> no runtimes are found, in the IDE log there is:
java.lang.NoClassDefFoundError: org/drools/eclipse/util/DroolsRuntimeManager
at org.jboss.tools.runtime.handlers.DroolsHandler.droolsExists(DroolsHandler.java:67)
at org.jboss.tools.runtime.handlers.DroolsHandler.exists(DroolsHandler.java:119)
at org.jboss.tools.runtime.ui.RuntimeUIActivator.runtimeCreated(RuntimeUIActivator.java:422)
at org.jboss.tools.runtime.ui.dialogs.SearchRuntimePathDialog.getServerDefinitions(SearchRuntimePathDialog.java:312)
at org.jboss.tools.runtime.ui.dialogs.SearchRuntimePathDialog.finishedRun(SearchRuntimePathDialog.java:256)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:510)
at org.jboss.tools.runtime.ui.RuntimeUIActivator.refreshRuntimes(RuntimeUIActivator.java:214)
at org.jboss.tools.runtime.ui.preferences.RuntimePreferencePage$5.widgetSelected(RuntimePreferencePage.java:373)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8737) Simple Web Service wizard prevents creating sample in Dynamic Web Project if web.xml is missing
by Brian Fitzpatrick (JIRA)
Simple Web Service wizard prevents creating sample in Dynamic Web Project if web.xml is missing
-----------------------------------------------------------------------------------------------
Key: JBIDE-8737
URL: https://issues.jboss.org/browse/JBIDE-8737
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.1, 3.3.0.M1
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
While doing some testing of the Simple Web Service wizard, I discovered that if a project doesn't have even an empty web.xml, you can't create the sample service. In the case of AS 5, you need the web.xml, but in the case of AS 6 and up, you don't need the web.xml, so this is definitely a bug.
To reproduce, create a new Dynamic Web Project without a web.xml (if you create one in Indigo/Eclipse 3.7, this seems to occur automatically) and then use the Web Services->Simple Web Service wizard to try and create a JAX-WS sample. It complains that it's an invalid Dynamic Web Project because the web.xml is missing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8771) org.jboss.tools.cdi.ui.test.wizard.NewCDIWizardTest.testNewInterceptorBindingWizardWithBinding failure.
by Alexey Kazakov (JIRA)
org.jboss.tools.cdi.ui.test.wizard.NewCDIWizardTest.testNewInterceptorBindingWizardWithBinding failure.
-------------------------------------------------------------------------------------------------------
Key: JBIDE-8771
URL: https://issues.jboss.org/browse/JBIDE-8771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.1.M1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.1.M1
Tests run: 27, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 68.71 sec <<< FAILURE!
testNewInterceptorBindingWizardWithBinding(org.jboss.tools.cdi.ui.test.wizard.NewCDIWizardTest) Time elapsed: 0.097 sec <<< FAILURE!
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:214)
at junit.framework.Assert.assertNotNull(Assert.java:207)
at org.jboss.tools.cdi.ui.test.wizard.NewCDIWizardTest.testNewInterceptorBindingWizardWithBinding(NewCDIWizardTest.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8785) The requested profile "local.site" could not be activated because it does not exist
by Alexey Kazakov (JIRA)
The requested profile "local.site" could not be activated because it does not exist
-----------------------------------------------------------------------------------
Key: JBIDE-8785
URL: https://issues.jboss.org/browse/JBIDE-8785
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Nick Boldt
I'm trying to build JBT using the three steps from http://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3
a) {noformat}mvn clean install -f build/parent/pom.xml -Dmaven.repo.local=.repository{noformat}
b) {noformat} mvn clean install -f build/target-platform/pom.xml -Pget.local.target -Dmaven.repo.local=.repository{noformat}
c) {noformat} mvn clean install -U -B -fae -e -P local.site -f build/target-platform/pom.xml -Dlocal.site=file://home/igels/Projects/jbt-3.3/trunk/build/target-platform/REPO/ -Dmaven.repo.local=.repository{noformat}
a) and b) are successful but on the step c) I got:
{noformat}
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss Tools Target Platform Definition 0.0.2-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ org.jboss.tools.target.platform ---
[INFO]
[INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ org.jboss.tools.target.platform ---
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.jboss.tools.target.platform ---
[INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/pom.xml to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT.pom
[INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/multiple.target to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-multiple.target
[INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/unified.target to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-unified.target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.495s
[INFO] Finished at: Mon Apr 25 10:49:46 PDT 2011
[INFO] Final Memory: 3M/119M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "local.site" could not be activated because it does not exist.
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-4039) Drools Runtime version checks during Drools project creation.
by Aliaksey Nis (JIRA)
Drools Runtime version checks during Drools project creation.
-------------------------------------------------------------
Key: JBIDE-4039
URL: https://jira.jboss.org/jira/browse/JBIDE-4039
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.0.0.GA
Environment: WindowsXP SP2
JBoss Developer Studio
Version: 2.0.0.GA
Build id: jbdevstudio-eap-win32-2.0.0.GA-R200903141247-H4
JRE 1.5_08
Reporter: Aliaksey Nis
Attachments: DroolsExc1.txt, DroolsExc2.txt
EXECUTE: Install studio, during installation add jboss-soa-p.4.3.0 server.
ASSERT: Studio created drools runtime - Drools - jboss-soa-p.4.3.0.
EXECUTE: New project > Drools Project.
EXECUTE: Input name, press Next 2 times.
FAILURE: In step 3 enabled default checkbox with "Drools - jboss-soa-p.4.3.0" runtime(4.x drools runtime). And selected code compatibility with drools 5.x. No sights of warning about wrong Drools version.
EXECUTE: Press Finish.
ASSERT: Project created with error multiply markers(because wrong drools runtime used).
EXECUTE: Go to Preferences > Drools > Drools Runtimes. Create new Drools 5.x runtime.
EXECUTE: Right click on Drools project. Select Properties > Drools.
EXECUTE: Enable Settings checkbox, select Drools 5.x runtime. Press Ok.
FAILURE: Exception thrown in error log(DroolsExc1.txt).
EXECUTE: Right click on Drools project. Select Properties > Drools.
EXECUTE: Disable Settings checkbox. Press Ok.
FAILURE: Each time you press Ok button - exception thrown in error log(DroolsExc21.txt). It's imposible to disable Project specific settings now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months