[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15318:
---------------------------------------
There was a problem when configurators were enabled during creating a project based on an archetype.
I can't remember details because the issue was fixed within JBIDE-10264 (Wizard-ify the project examples) that includes a rather big patch.
There are a lot of changes in JBT and m2e after this fix so I propose we to apply Denis's patch.
I have tested the patch and can't find any issues.
> Import Maven Archetype Project Example ignores JBoss Maven Integration preferences
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15318
> URL: https://issues.jboss.org/browse/JBIDE-15318
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI.
> This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called.
--
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, 8 months
[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-15158.
--------------------------------------
Resolution: Done
resolving since the dialog wont get shown any more (verified today).
> if I create a scalable application I get a non-useful dialog about HAProxy (watcher)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-15158
> URL: https://issues.jboss.org/browse/JBIDE-15158
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: ha-proxy-started.png
>
>
> How to reproduce:
> # ASSERT: make sure that you dont have any scalable application in your domain
> # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling*
> Result:
> You get a dialog which informs you that the HAProxy was started:
> !ha-proxy-started.png!
--
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, 8 months
[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-14765:
------------------------------------------
Description:
See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
Check satisfied and unsatisfied dependencies:
- @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection')
because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/>
- @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2)
- @Inject Bean3 bean3 - is unsatisfied
because of <weld:exclude name="exclude.p2.*"/>
- @Inject Bean4 bean4 - is satisfied
because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/>
- @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied
because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled
- @Inject Bean7 bean7 - is satisfied
because <weld:exclude name="exclude.p6.**"> is inactive.
Supported use-cases for <weld:exclude> are limited to use-cases for <exclude> in CDI, which does not support pattern, symbol ?, use of symbol * other than in suffixes .* and .**, etc.
was:
See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
Check satisfied and unsatisfied dependencies:
- @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection')
because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/>
- @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2)
- @Inject Bean3 bean3 - is unsatisfied
because of <weld:exclude name="exclude.p2.*"/>
- @Inject Bean4 bean4 - is satisfied
because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/>
- @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied
because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled
- @Inject Bean7 bean7 - is satisfied
because <weld:exclude name="exclude.p6.**"> is inactive.
> Support <weld:exclude>
> ----------------------
>
> Key: JBIDE-14765
> URL: https://issues.jboss.org/browse/JBIDE-14765
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
> 1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
> 2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
> Check satisfied and unsatisfied dependencies:
> - @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection')
> because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/>
> - @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2)
> - @Inject Bean3 bean3 - is unsatisfied
> because of <weld:exclude name="exclude.p2.*"/>
> - @Inject Bean4 bean4 - is satisfied
> because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/>
> - @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied
> because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled
> - @Inject Bean7 bean7 - is satisfied
> because <weld:exclude name="exclude.p6.**"> is inactive.
> Supported use-cases for <weld:exclude> are limited to use-cases for <exclude> in CDI, which does not support pattern, symbol ?, use of symbol * other than in suffixes .* and .**, etc.
--
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, 8 months
[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-14765:
------------------------------------------
Description:
See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
Check satisfied and unsatisfied dependencies:
- @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection')
because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/>
- @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2)
- @Inject Bean3 bean3 - is unsatisfied
because of <weld:exclude name="exclude.p2.*"/>
- @Inject Bean4 bean4 - is satisfied
because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/>
- @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied
because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled
- @Inject Bean7 bean7 - is satisfied
because <weld:exclude name="exclude.p6.**"> is inactive.
was:
See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
Check satisfied and unsatisfied dependencies:
@Inject Bean1 bean1; - is unsatisfied (has marker 'No bean is eligible for injection')
because beans.xml contains
> Support <weld:exclude>
> ----------------------
>
> Key: JBIDE-14765
> URL: https://issues.jboss.org/browse/JBIDE-14765
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html
> 1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1
> 2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml
> Check satisfied and unsatisfied dependencies:
> - @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection')
> because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/>
> - @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2)
> - @Inject Bean3 bean3 - is unsatisfied
> because of <weld:exclude name="exclude.p2.*"/>
> - @Inject Bean4 bean4 - is satisfied
> because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/>
> - @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied
> because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled
> - @Inject Bean7 bean7 - is satisfied
> because <weld:exclude name="exclude.p6.**"> is inactive.
--
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, 8 months
[JBoss JIRA] (JBIDE-15327) CDI Test failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-15327:
--------------------------------------
Summary: CDI Test failure
Key: JBIDE-15327
URL: https://issues.jboss.org/browse/JBIDE-15327
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 4.2.0.Alpha1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.Alpha1
Some times I see the following error when running cdi.core.tests:
{code}
Contains: Errors running builder 'JBoss Knowledge Base Builder' on project 'missingBeansXmlChildProject'.
java.lang.IllegalArgumentException: ImageRegistry key already in use: -1314270185
at org.eclipse.jface.resource.ImageRegistry.put(ImageRegistry.java:284)
at org.jboss.tools.common.model.icons.impl.XModelObjectIcon.getEclipseImage0(XModelObjectIcon.java:100)
at org.jboss.tools.common.model.undo.XChangeSetUndo.<init>(XChangeSetUndo.java:29)
at org.jboss.tools.common.model.undo.XChangeUndo.<init>(XChangeUndo.java:18)
at org.jboss.tools.common.model.impl.XModelImpl.changeObjectAttribute(XModelImpl.java:356)
at org.jboss.tools.common.model.impl.XModelImpl.changeObjectAttribute(XModelImpl.java:277)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.mergeAttributes(AbstractExtendedXMLFileImpl.java:407)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.merge(AbstractExtendedXMLFileImpl.java:390)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.mergeAll(AbstractExtendedXMLFileImpl.java:290)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:261)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:210)
at org.jboss.tools.common.model.loaders.impl.SimpleWebFileLoader.update(SimpleWebFileLoader.java:149)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.reload(FolderImpl.java:696)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:607)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateNew(FolderImpl.java:729)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:418)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:592)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:415)
at org.jboss.tools.common.model.util.EclipseResourceUtil.findResourceInFileSystem(EclipseResourceUtil.java:569)
at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:144)
at org.jboss.tools.jst.web.kb.internal.scanner.XMLScanner.isLikelyComponentSource(XMLScanner.java:82)
at org.jboss.tools.jst.web.kb.internal.KbResourceVisitor.visit(KbResourceVisitor.java:98)
at org.jboss.tools.jst.web.kb.internal.KbBuilder$SampleDeltaVisitor.visit(KbBuilder.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at org.jboss.tools.jst.web.kb.internal.KbBuilder.incrementalBuild(KbBuilder.java:151)
at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:114)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:114)
at org.jboss.tools.common.base.test.validation.TestUtil.validate(TestUtil.java:61)
at org.jboss.tools.cdi.core.test.tck.validation.MissingBeansXmlValidationTest.testCreatingBeansXml(MissingBeansXmlValidationTest.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
{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, 8 months