[JBoss JIRA] (JBIDE-19615) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19615?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19615:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Base]
> ---------------------------------------------------
>
> Key: JBIDE-19615
> URL: https://issues.jboss.org/browse/JBIDE-19615
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Base]: 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 Base 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, 12 months
[JBoss JIRA] (JBIDE-19618) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19618?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19618:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JST]
> --------------------------------------------------
>
> Key: JBIDE-19618
> URL: https://issues.jboss.org/browse/JBIDE-19618
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [JST]: 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 JST 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, 12 months
[JBoss JIRA] (JBIDE-19617) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19617?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19617:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JavaEE]
> -----------------------------------------------------
>
> Key: JBIDE-19617
> URL: https://issues.jboss.org/browse/JBIDE-19617
> 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.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [JavaEE]: 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 JavaEE 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, 12 months
[JBoss JIRA] (JBIDE-19626) Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19626:
-------------------------------------
Fix Version/s: 4.3.0.Alpha2
Description:
# 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
Affects Version/s: 4.3.0.Alpha2
Component/s: openshift
> Explorer
> --------
>
> 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, 12 months
[JBoss JIRA] (JBIDE-19626) Explorer: Refresh has no visible effect for v3 connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19626:
-------------------------------------
Summary: Explorer: Refresh has no visible effect for v3 connections (was: Explorer)
> Explorer: Refresh has no visible effect for v3 connections
> ----------------------------------------------------------
>
> 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, 12 months
[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-19338 at 4/16/15 1:39 PM:
----------------------------------------------------------------
I tried jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar.
But I needed to install "JBoss Tools Java Standard Tools AngularJS" from update site https://devstudio.redhat.com/updates/9.0.0/jboss-devstudio-9.0.0.Alpha1-u...
(because of JBDS-3413)
Everything works just fine.
was (Author: dazarov):
I tried jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar.
But I needed to install "JBoss Tools Java Standard Tools AngularJS" from update site https://devstudio.redhat.com/updates/9.0.0/jboss-devstudio-9.0.0.Alpha1-u...
Everything works just fine.
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBDS-3413) Central Software/Update Connectors View is empty after installation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3413?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3413:
---------------------------------
Affects Version/s: 9.0.0.Alpha1
(was: 8.0.0.Alpha2)
> Central Software/Update Connectors View is empty after installation
> -------------------------------------------------------------------
>
> Key: JBDS-3413
> URL: https://issues.jboss.org/browse/JBDS-3413
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.0.0.Alpha1
> Environment: Windows 8, jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar
> Reporter: Daniel Azarov
> Attachments: NoConnectors.png
>
>
> {code}!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.841
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(Unknown Source)
> at java.net.URI.<init>(Unknown Source)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:61)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:28.417
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months