[JBoss JIRA] (JBIDE-19625) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [LiveReload]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19625?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-19625.
---------------------------------------
Assignee: Max Rydahl Andersen
Resolution: Done
done - not tested due to build changes
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [LiveReload]
> ---------------------------------------------------------
>
> Key: JBIDE-19625
> URL: https://issues.jboss.org/browse/JBIDE-19625
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [LiveReload]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19626:
-------------------------------------
Summary: Explorer: If you have an erroring v3 connection, refresh has no visible effect (was: Explorer: Refresh has no visible effect for v3 connections)
> Explorer: If you have an erroring v3 connection, refresh has no visible effect
> ------------------------------------------------------------------------------
>
> Key: JBIDE-19626
> URL: https://issues.jboss.org/browse/JBIDE-19626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Fix For: 4.3.0.Alpha2
>
>
> # ASSERT: make sure that you have a connection to an openshift v3 server under your full control
> # ASSERT: make sure your connection to it was not unfolded/loaded yet
> # EXEC: shut down your local openshift v3 server so that it does not answer
> # EXEC: unfold your connection
> # ASSERT: the connection shows an error "child"
> # EXEC: re-start your local v3 server
> # EXEC: pick "Refresh" from the context menu of your connection
> Result:
> Nothing happens, the error "child" stays
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19621) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [BrowserSim]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19621?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-19621:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [BrowserSim]
> ---------------------------------------------------------
>
> Key: JBIDE-19621
> URL: https://issues.jboss.org/browse/JBIDE-19621
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [BrowserSim]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19611) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19611?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-19611:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE]
> --------------------------------------------------
>
> Key: JBIDE-19611
> URL: https://issues.jboss.org/browse/JBIDE-19611
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19622) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Webservices]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19622?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-19622.
---------------------------------------
Resolution: Done
Done - but could not successfully test due to missing server updatesites.
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Webservices]
> ----------------------------------------------------------
>
> Key: JBIDE-19622
> URL: https://issues.jboss.org/browse/JBIDE-19622
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Webservices]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-17698) Server view could show all deployed modules, obtained from the server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17698:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Server view could show all deployed modules, obtained from the server
> ---------------------------------------------------------------------
>
> Key: JBIDE-17698
> URL: https://issues.jboss.org/browse/JBIDE-17698
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> Pavol Srna pointed out to me that when he deletes a project in workspace while it's deployed on a running AS7, it disappears from the server view and he can't undeploy it from Eclipse.
> I understand that this is somewhat expected, but we have a suggestion: Could the server view get its deployed modules from the server via the management api and use that to show the modules? Similar to what the web console of AS7/WildFly/EAP6 shows.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-12352) Remote management connection to servers cannot be established with IPv6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12352?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-12352:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Remote management connection to servers cannot be established with IPv6
> -----------------------------------------------------------------------
>
> Key: JBIDE-12352
> URL: https://issues.jboss.org/browse/JBIDE-12352
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.1.Final
> Environment: JBDS 5.0.1
> Fedora 17 32bit
> OpenJDK 1.6
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX.
> When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error:
> {code}
> Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.3.GA
> Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.3.GA
> Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.7.GA
> Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months