[JBoss JIRA] (JBIDE-23604) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [aerogear-hybrid]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23604:
-------------------------------------------
Summary: For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [aerogear-hybrid]
Key: JBIDE-23604
URL: https://issues.jboss.org/browse/JBIDE-23604
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid
Reporter: Friendly Jira Robot
Priority: Blocker
Fix For: 4.4.3.AM1
For JBIDE 4.4.3.AM1 [aerogear-hybrid]: Please perform the following tasks: 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.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig site *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 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 aerogear-hybrid 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)
7 years, 5 months
[JBoss JIRA] (JBIDE-23605) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [arquillian]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23605:
-------------------------------------------
Summary: For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [arquillian]
Key: JBIDE-23605
URL: https://issues.jboss.org/browse/JBIDE-23605
Project: Tools (JBoss Tools)
Issue Type: Task
Components: arquillian
Reporter: Friendly Jira Robot
Priority: Blocker
Fix For: 4.4.3.AM1
For JBIDE 4.4.3.AM1 [arquillian]: Please perform the following tasks: 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.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 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 arquillian 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)
7 years, 5 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21857:
---------------------------------------
[~adietish] well, although server adapter in Servers view shows Synchronized, check Debug view and Remote debugger of the application. It says, on the debugged thread, "out of synch" (it makes me bit dizzy seeing "synch" instead of "sync", but that would be for another issue. It does not look nice). So server adapter can be synchronized, but debugger isn't.
Also, my JMX is disconected, until I connect it manually.
And I wouldn't close this one, because those further HCR compatible changes you perform, show HCR Failed dialog, as you confirmed, but if you do not restart module (just push button Continue - it is not necessary to restart module with HCR compatible changes), your changes will not be applied (server will still use old code).
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23593:
---------------------------------------
org.jboss.tools.ui.bot.ext.test is a legacy bundle/library that was used by other tests. The code hasn't been changed in 5 years. I believe it doesn't contain any tests by default. Yes, it's not right for this bundle to be called *.test.
I wasn't sure if there was any test that would still use it. So I commented it out from tests/pom.xml and then ran "mvn clean verify -DskipTests" on the whole repo and it worked. So I think org.jboss.tools.ui.bot.ext.test is no longer used anywhere.
I think we should delete it. What do you think [~rawagner], [~psrna], [~jeffmaury]?
> Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test
> ---------------------------------------------------------------------
>
> Key: JBIDE-23593
> URL: https://issues.jboss.org/browse/JBIDE-23593
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: integration-tests
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Labels: integration, integration_tests
> Fix For: 4.4.3.AM1
>
>
> Maven command:
> {code}
> mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months