[JBoss JIRA] (JBIDE-22724) ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22724?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22724:
----------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22724
> URL: https://issues.jboss.org/browse/JBIDE-22724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Marker id 139166 not found.
> {noformat}
> org.eclipse.core.internal.resources.ResourceException: Marker id 139166 not found.
> at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57)
> at org.eclipse.core.internal.resources.Marker.getAttribute(Marker.java:102)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.hasErrors(ArquillianBuilder.java:477)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:98)
> 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:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | MacOSX | 10.11.1 | 10.11.1 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5744cd67e4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22864) NullPointerException in ArquillianBuilder$3.visit
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22864?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22864:
----------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> NullPointerException in ArquillianBuilder$3.visit
> -------------------------------------------------
>
> Key: JBIDE-22864
> URL: https://issues.jboss.org/browse/JBIDE-22864
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.1.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$3.visit(ArquillianBuilder.java:731)
> at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:231)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
> at org.eclipse.jdt.core.dom.ReturnStatement.accept0(ReturnStatement.java:137)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
> at org.eclipse.jdt.core.dom.Block.accept0(Block.java:137)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:635)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.validateArchiveFileLocation(ArquillianBuilder.java:653)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:359)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> 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:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt.core | 3.12.0.v20160516-2131 | 3.12.0.v20160516-2131 |
> | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5786f2afe4b07f3dc2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22958) 3rd party caused NullPointerException below ArquillianUIUtil.addContainerProperties
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22958?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22958:
----------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> 3rd party caused NullPointerException below ArquillianUIUtil.addContainerProperties
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22958
> URL: https://issues.jboss.org/browse/JBIDE-22958
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message:
> {noformat}
> java.lang.NullPointerException: null
> at EXTERNAL.EXTERNAL(null:-1)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644)
> at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 6.3.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57a34e3ce4b084ea94...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22957) 3rd party caused CoreException below ArquillianUIUtil.getActiveType
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22957?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22957:
----------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> 3rd party caused CoreException below ArquillianUIUtil.getActiveType
> -------------------------------------------------------------------
>
> Key: JBIDE-22957
> URL: https://issues.jboss.org/browse/JBIDE-22957
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, upstream
> Affects Versions: 4.4.1.AM2
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: GAE SDK /Users/villevenalainen/.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.34/appengine-api-1.0-sdk-1.9.34.jar failed validation
> {noformat}
> org.eclipse.core.runtime.CoreException: SDK location '/Users/villevenalainen/.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.34/appengine-api-1.0-sdk-1.9.34.jar' is not a directory
> at EXTERNAL.EXTERNAL(null:-1)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation$1.run(ReconcileWorkingCopyOperation.java:258)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.notifyParticipants(ReconcileWorkingCopyOperation.java:245)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:95)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1265)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1224)
> at org.eclipse.jdt.internal.corext.util.JavaModelUtil.reconcile(JavaModelUtil.java:609)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:283)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:199)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:183)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getActiveType(ArquillianUIUtil.java:182)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:62)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:22)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:707)
> 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:4024)
> {noformat}
> Bundles:
> | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.0.v20150421-2214 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.e4.ui.workbench | 1.3.1.v20160203-0951 | 1.3.1.v20160203-0951 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v_OTDT_r242_201601310642 | 3.11.2.v_OTDT_r242_201601310642 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5791fa6fe4b07542de...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23068:
----------------------------------------
Ok, [~rob.stryker] can you help there?
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-23068:
------------------------------------------
[~mickael_istria]yes, i used this instruction always =)
and yes i have jbt-base in my workspace and see description - there are also problems with it
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23088) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [LiveReload]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23088:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [LiveReload]
Key: JBIDE-23088
URL: https://issues.jboss.org/browse/JBIDE-23088
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [LiveReload]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23082) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Forge]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23082:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Forge]
Key: JBIDE-23082
URL: https://issues.jboss.org/browse/JBIDE-23082
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [Forge]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23085) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Arquillian]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23085:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Arquillian]
Key: JBIDE-23085
URL: https://issues.jboss.org/browse/JBIDE-23085
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: arquillian
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [Arquillian]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23081) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JST]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23081:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JST]
Key: JBIDE-23081
URL: https://issues.jboss.org/browse/JBIDE-23081
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [JST]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months