[JBoss JIRA] (JBIDE-18489) JavaModelException while editing code in sample project
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18489?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-18489:
-----------------------------------------------
BeanMember.getTypeDeclaration() catches JavaModelException, logs it and returns null.
> JavaModelException while editing code in sample project
> -------------------------------------------------------
>
> Key: JBIDE-18489
> URL: https://issues.jboss.org/browse/JBIDE-18489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> Not sure what are the steps to reproduce this problem, but here's what I had in the Error Log while testing on a sample project:
> {code}
> Java Model Exception: Java Model Status [listenToEvents(BikeStation) [in BikeStationRefreshServiceTest [in [Working copy] BikeStationRefreshServiceTest.java [in org.sample.citibikenyc.service [in src/test/java [in citibikesnyc]]]]] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:568)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.SourceMethod.getReturnType(SourceMethod.java:188)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.getTypeDeclaration(BeanMember.java:67)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:50)
> at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68)
> at org.jboss.tools.cdi.internal.core.impl.ClassBean.cleanCache(ClassBean.java:642)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1270)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1172)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:419)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:247)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18474) For JBIDE 4.2.0.CR2: Prepare for CR2 release [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18474?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-18474.
----------------------------------
Assignee: Alexey Kazakov
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [JavaEE]
> -----------------------------------------------------
>
> Key: JBIDE-18474
> URL: https://issues.jboss.org/browse/JBIDE-18474
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [JavaEE]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18491) JBTValidationException while moving CDI beans into another package
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18491?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18491:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
> JBTValidationException while moving CDI beans into another package
> ------------------------------------------------------------------
>
> Key: JBIDE-18491
> URL: https://issues.jboss.org/browse/JBIDE-18491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> I think this exception occurred when moving CDI-annotated classes in another package (or removing an empty package that previously contained the CDI-annotated classes)
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> 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.CDIProject.getAnnotationDeclarationKey(CDIProject.java:663)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.getAnnotationDeclarationKey(CDIProject.java:651)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.areMatchingQualifiers(CDIProject.java:571)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:435)
> at org.jboss.tools.cdi.internal.core.impl.CDIProjectAsYouType.getBeans(CDIProjectAsYouType.java:348)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1816)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:753)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:622)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:555)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18491) JBTValidationException while moving CDI beans into another package
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18491?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18491:
--------------------------------------
Assignee: Viacheslav Kabanovich
> JBTValidationException while moving CDI beans into another package
> ------------------------------------------------------------------
>
> Key: JBIDE-18491
> URL: https://issues.jboss.org/browse/JBIDE-18491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> I think this exception occurred when moving CDI-annotated classes in another package (or removing an empty package that previously contained the CDI-annotated classes)
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> 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.CDIProject.getAnnotationDeclarationKey(CDIProject.java:663)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.getAnnotationDeclarationKey(CDIProject.java:651)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.areMatchingQualifiers(CDIProject.java:571)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:435)
> at org.jboss.tools.cdi.internal.core.impl.CDIProjectAsYouType.getBeans(CDIProjectAsYouType.java:348)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1816)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:753)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:622)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:555)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18459) MacBook Pro Retina Display Font
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18459?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18459:
----------------------------------------
We are working on getting rid this text in palette images (for 4.3.0) - JBIDE-18462
> MacBook Pro Retina Display Font
> -------------------------------
>
> Key: JBIDE-18459
> URL: https://issues.jboss.org/browse/JBIDE-18459
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, forge, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Environment: MacBook Pro 15" mid-2014 Retina set at "Best for Display" (default)
> Reporter: Burr Sutter
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: Screenshot 2014-09-30 13.58.59.png, Screenshot 2014-09-30 14.04.34.png
>
>
> Some fonts are "fuzzy".
> Screenshot 1
> - under "JBoss Buzz"
> - under "Start from a sample" and Portal Applications
> - the open cheatsheet.xml (AngularJS Forge)
> Screenshot 2
> - jQuery Mobile and Ionic Palettes
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18489) JavaModelException while editing code in sample project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18489?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18489:
--------------------------------------
Assignee: Viacheslav Kabanovich
> JavaModelException while editing code in sample project
> -------------------------------------------------------
>
> Key: JBIDE-18489
> URL: https://issues.jboss.org/browse/JBIDE-18489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> Not sure what are the steps to reproduce this problem, but here's what I had in the Error Log while testing on a sample project:
> {code}
> Java Model Exception: Java Model Status [listenToEvents(BikeStation) [in BikeStationRefreshServiceTest [in [Working copy] BikeStationRefreshServiceTest.java [in org.sample.citibikenyc.service [in src/test/java [in citibikesnyc]]]]] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:568)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.SourceMethod.getReturnType(SourceMethod.java:188)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.getTypeDeclaration(BeanMember.java:67)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:50)
> at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68)
> at org.jboss.tools.cdi.internal.core.impl.ClassBean.cleanCache(ClassBean.java:642)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1270)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1172)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:419)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:247)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18489) JavaModelException while editing code in sample project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18489?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18489:
----------------------------------------
Yes, such exception may happen because Java Model can might have been changed since we got it and started to use in our CDI builder.
It's not critical because we will get this change in next building iteration and everything will be updated accordingly in CDI model. The only downside is an exception in the Log.
But we should make sure we handle such exception properly in our code.
Slave, could you please take a look at this particular case?
> JavaModelException while editing code in sample project
> -------------------------------------------------------
>
> Key: JBIDE-18489
> URL: https://issues.jboss.org/browse/JBIDE-18489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> Not sure what are the steps to reproduce this problem, but here's what I had in the Error Log while testing on a sample project:
> {code}
> Java Model Exception: Java Model Status [listenToEvents(BikeStation) [in BikeStationRefreshServiceTest [in [Working copy] BikeStationRefreshServiceTest.java [in org.sample.citibikenyc.service [in src/test/java [in citibikesnyc]]]]] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:568)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.SourceMethod.getReturnType(SourceMethod.java:188)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.getTypeDeclaration(BeanMember.java:67)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:50)
> at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68)
> at org.jboss.tools.cdi.internal.core.impl.ClassBean.cleanCache(ClassBean.java:642)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1270)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1172)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:419)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:247)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18489) JavaModelException while editing code in sample project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18489?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18489:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
> JavaModelException while editing code in sample project
> -------------------------------------------------------
>
> Key: JBIDE-18489
> URL: https://issues.jboss.org/browse/JBIDE-18489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> Not sure what are the steps to reproduce this problem, but here's what I had in the Error Log while testing on a sample project:
> {code}
> Java Model Exception: Java Model Status [listenToEvents(BikeStation) [in BikeStationRefreshServiceTest [in [Working copy] BikeStationRefreshServiceTest.java [in org.sample.citibikenyc.service [in src/test/java [in citibikesnyc]]]]] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:568)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.SourceMethod.getReturnType(SourceMethod.java:188)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.getTypeDeclaration(BeanMember.java:67)
> at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:50)
> at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68)
> at org.jboss.tools.cdi.internal.core.impl.ClassBean.cleanCache(ClassBean.java:642)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1270)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1172)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:419)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:247)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18477) For JBIDE 4.2.0.CR2: Prepare for CR2 release [BrowserSim]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18477?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov closed JBIDE-18477.
------------------------------------------
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [BrowserSim]
> ---------------------------------------------------------
>
> Key: JBIDE-18477
> URL: https://issues.jboss.org/browse/JBIDE-18477
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [BrowserSim]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months