[JBoss JIRA] (ERT-457) "Tag Image" shell does not have a title [EBZ#508176]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-457:
---------------------------------------
Summary: "Tag Image" shell does not have a title [EBZ#508176]
Key: ERT-457
URL: https://issues.jboss.org/browse/ERT-457
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Priority: Minor
Image Tag shell does not have a title.
Steps to reproduce:
1. Click on any image under Images in Docker Explorer.
2. Select Add Tag
3. New window does not have a title (in vanilla eclipse neon.1 with latest Docker Tooling - 2.1.0.201611230758 is title <2>). In devstudio is not title empty.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-458) Add Refresh command on connection and as a button in Docker Explorer [EBZ#508177]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-458:
---------------------------------------
Summary: Add Refresh command on connection and as a button in Docker Explorer [EBZ#508177]
Key: ERT-458
URL: https://issues.jboss.org/browse/ERT-458
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Priority: Trivial
Please add refresh command on selected connection (as it is on Containers and Images).
There can also be button near buttons Add Connection, Remove Connection and Enable connection, which refreshes all connections.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4115) error running org.jboss.tools.aerogear.ui.bot.test - org.jboss.tools.aerogear.hybrid.feature not found
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4115?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4115.
------------------------------
Verified, Jenkins is able to build [aerogear tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/A...].
> error running org.jboss.tools.aerogear.ui.bot.test - org.jboss.tools.aerogear.hybrid.feature not found
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4115
> URL: https://issues.jboss.org/browse/JBDS-4115
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, target-platform
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 10.2.0.AM3
>
>
> {code}
> 12:09:37 [INFO] ------------------------------------------------------------------------
> 12:09:37 [INFO] Building org.jboss.tools.aerogear.ui.bot.test 4.4.2-SNAPSHOT
> 12:09:37 [INFO] ------------------------------------------------------------------------
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Deleting /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] The project's OSGi version is 4.4.2.v20160908-1258
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-packaging-plugin:0.26.0:validate-id (default-validate-id) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-packaging-plugin:0.26.0:validate-version (default-validate-version) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Setting property 'skipTestsOrITests' to ''.
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (warn-no-snapshots-AMx) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-no-snapshots-Final) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:prepare-agent (default) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] tycho.testArgLine set to -javaagent:/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/.repository/org/jacoco/org.jacoco.agent/0.7.1.201405082137/org.jacoco.agent-0.7.1.201405082137-runtime.jar=destfile=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/target/jacoco.exec,append=true,includes=org.jboss.tools.*
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
> 12:09:37 [INFO] skip non existing resourceDirectory /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/src/main/resources
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-compiler-plugin:0.26.0:compile (default-compile) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Compiling 18 source files to /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target/classes
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- maven-resources-plugin:2.4.1:testResources (default-testResources) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Using 'ISO-8859-1' encoding to copy filtered resources.
> 12:09:37 [INFO] skip non existing resourceDirectory /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/src/test/resources
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-source-plugin:0.26.0:plugin-source (plugin-source) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Building jar: /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target/org.jboss.tools.aerogear.ui.bot.test-4.4.2-SNAPSHOT-sources.jar
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- target-platform-configuration:0.26.0:target-platform (default-target-platform) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-packaging-plugin:0.26.0:package-plugin (default-package-plugin) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Building jar: /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target/org.jboss.tools.aerogear.ui.bot.test-4.4.2-SNAPSHOT.jar
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-p2-plugin:0.26.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- repository-utils:0.26.0-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-pack200a-plugin:0.26.0:normalize (pack200-normalize) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Pack200 normalizing jar /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target/org.jboss.tools.aerogear.ui.bot.test-4.4.2-SNAPSHOT.jar
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- exec-maven-plugin:1.2.1:exec (jarsign) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] skipping execute as per configuraion
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-pack200b-plugin:0.26.0:pack (pack200-pack) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] Pack200 packing jar /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/target/org.jboss.tools.aerogear.ui.bot.test-4.4.2-SNAPSHOT.jar
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-p2-plugin:0.26.0:p2-metadata (attached-p2-metadata) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] No baseline version MavenProject: org.jboss.tools.aerogear.tests:org.jboss.tools.aerogear.ui.bot.test:4.4.2-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/pom.xml
> 12:09:37 [INFO]
> 12:09:37 [INFO] --- tycho-p2-plugin:0.26.0:p2-metadata (p2-metadata) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:37 [INFO] No baseline version MavenProject: org.jboss.tools.aerogear.tests:org.jboss.tools.aerogear.ui.bot.test:4.4.2-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.aerogear.ui.bot.test/pom.xml
> 12:09:38 [INFO]
> 12:09:38 [INFO] --- tycho-surefire-plugin:0.26.0:test (default-test) @ org.jboss.tools.aerogear.ui.bot.test ---
> 12:09:38 [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
> 12:09:38 [ERROR] Cannot resolve project dependencies:
> 12:09:38 [ERROR] You requested to install 'org.jboss.tools.aerogear.hybrid.feature.feature.group 0.0.0' but it could not be found
> 12:09:38 [ERROR]
> 12:09:38 [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4116) error running org.jboss.tools.archives.ui.bot.test - org.eclipse.swt.SWTError: No more handles
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4116?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4116.
------------------------------
Verified in 10.2.0.GA
> error running org.jboss.tools.archives.ui.bot.test - org.eclipse.swt.SWTError: No more handles
> ----------------------------------------------------------------------------------------------
>
> Key: JBDS-4116
> URL: https://issues.jboss.org/browse/JBDS-4116
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 10.2.0.AM3
>
>
> {code}12:09:41 [INFO] --- tycho-surefire-plugin:0.26.0:test (default-test) @ org.jboss.tools.archives.ui.bot.test ---
> 12:09:41 [INFO] Expected eclipse log file: /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/target/work/data/.metadata/.log
> 12:09:41 [INFO] Command line:
> 12:09:41 [/qa/tools/opt/x86_64/jdk1.8.0_102/jre/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, -javaagent:/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/.repository/org/jacoco/org.jacoco.agent/0.7.1.201405082137/org.jacoco.agent-0.7.1.201405082137-runtime.jar=destfile=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/target/jacoco.exec,append=true,includes=org.jboss.ide.eclipse.archives.ui*, -Xms512m, -Xmx1024m, -XX:PermSize=256m, -XX:MaxPermSize=384m, -Djbosstools.test.jboss-as-7.1.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/target/requirements/jboss-as-7.1.1.Final, -Drd.config=target/classes/servers, -Dusage_reporting_enabled=false, -Dorg.jboss.tools.tests.skipPrivateRequirements=false, -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true, -Dosgi.clean=true, -Dorg.eclipse.update.reconcile=false, -jar, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.200.v20160318-1642/org.eclipse.equinox.launcher-1.3.200.v20160318-1642.jar, -data, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/target/work/data, -install, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161014-1217-B6204-installer-standalone, -configuration, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161014-1217-B6204-installer-standalone/configuration, -application, org.eclipse.tycho.surefire.osgibooter.uitest, -testproperties, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/target/surefire.properties, -product, com.jboss.devstudio.core.product, -nouithread, -pluginCustomization, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/../pluginCustomization.ini]
> 12:09:42 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
> 12:09:42 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0
> 12:09:46 An error has occurred. See the log file
> 12:09:46 /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.archives.ui.bot.test/target/work/data/.metadata/.log.{code}
> -->
> {code}org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
> at org.eclipse.swt.SWT.error(SWT.java:4559)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:958)
> at org.eclipse.swt.widgets.Display.create(Display.java:942)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:174)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:562)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:553)
> at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:789)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160)
> at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:168)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:111)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23533) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23533?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23533:
------------------------------------
Yes but that has been done on my behalf by a release script which does not yet store the JIRA number in the commit
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23533
> URL: https://issues.jboss.org/browse/JBIDE-23533
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [integration-tests]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23213:
---------------------------------------
Yeah, I was gonna say the same thing ;)
Current status is:
macOS (not that there is no space): done; support 10.11 and 10.12
Fedora: several people in the team are using Fedora 25 already, so we're confident that it's working correctly; so go ahead and make the change, i.e. support Fedora 24 and 25
Ubuntu: not sure yet - we should have Ubuntu 16.10 available in Central CI within a few days and then we can run some tests there
> Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23213
> URL: https://issues.jboss.org/browse/JBIDE-23213
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Labels: releasework
> Fix For: 4.4.2.Final
>
>
> It's time to review the available platforms on which we test devstudio / jbt.
> Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016.
> [0] https://wiki.ubuntu.com/Releases
> * Should we move to 16.04.1 LTS and 16.10?
> * Should we move to 14.04.5 LTS and 16.04.1 LTS ?
> * Should we move to 14.04.5 LTS and 16.10?
> Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1].
> [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio...
> But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right?
> [2] https://fedoraproject.org/wiki/Releases/25/Schedule
> * Should we move to F24 and F25?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23552) Easymport New and Noteworthy for 4.4.2.Final
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23552?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-23552.
----------------------------------
Resolution: Rejected
Nothing to change here. Also, I believe that the easymport componetn should be dropped from Jira as everything gets tracked upstream or in individual components (jee, js, maven...).
> Easymport New and Noteworthy for 4.4.2.Final
> -----------------------------------------------------
>
> Key: JBIDE-23552
> URL: https://issues.jboss.org/browse/JBIDE-23552
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: easymport
> Reporter: Jeff MAURY
> Assignee: Mickael Istria
> Priority: Critical
>
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Easymport JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Easymport, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Easymport by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Easymport4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Easymport for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Easymport, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23533) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23533?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23533:
---------------------------------------
[~jeffmaury], I noticed you already did that here:
https://github.com/jbosstools/jbosstools-integration-tests/commit/8f8cdd1...
I believe the hastags were supposed to add a comment here and then close the JIRA. But that will only work if the comment contains the JIRA number, no?
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23533
> URL: https://issues.jboss.org/browse/JBIDE-23533
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [integration-tests]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23533) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23533?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23533.
---------------------------------
Resolution: Done
Done.
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [integration-tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23533
> URL: https://issues.jboss.org/browse/JBIDE-23533
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [integration-tests]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.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.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.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.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months