[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21719:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Final)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22477) For JBIDE 4.4.0.Final: Prepare for Final/GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22477?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22477:
------------------------------------
As of 5:08pm EST on Thu Jun 2:
{code}
$➔ getBranches44
[1] aerogear ... OK
[2] arquillian ... OK
[3] base ... NO
[4] browsersim ... OK
[5] build ... OK
[6] build-ci ... OK
[7] build-sites ... OK
[8] central ... NO
[9] devdoc ... OK
[10] discovery ... OK
[11] download.jboss.org ... OK
[12] forge ... OK
[13] freemarker ... OK
[14] hibernate ... OK
[15] integration-tests ... OK
[16] javaee ... OK
[17] jst ... OK
[18] livereload ... OK
[19] maven-plugins ... OK
[20] openshift ... NO
[21] server ... NO
[22] versionwatch ... OK
[23] vpe ... OK
[24] webservices ... OK
OK: 20 of 24
{code}
> For JBIDE 4.4.0.Final: Prepare for Final/GA
> -------------------------------------------
>
> Key: JBIDE-22477
> URL: https://issues.jboss.org/browse/JBIDE-22477
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. 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...]
> See also: JBDS-3920
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22507:
-----------------------------------------------
Method ModuleLaunchConfigurationProvider.getLaunchConfiguration may be called with ILaunchTarget target null, according to code of LaunchBarManager.launchDescriptorMatches, then check for null is needed in line 76.
{code}
wc.setAttribute(ServerLaunchBarDelegate.ATTR_TARGET_NAME, target.getName());
{code}
> Debugging: cannot debug kitchensink, no breakpoint is being hit
> ---------------------------------------------------------------
>
> Key: JBIDE-22507
> URL: https://issues.jboss.org/browse/JBIDE-22507
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: debug, openshift_v3
> Fix For: 4.4.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22355.
------------------------------
Fix Version/s: 4.4.0.Final
(was: 4.4.x)
Resolution: Out of Date
Closing. Future work will be done in JBIDE-13671.
My fond hope is that after 4.4.0.Final, we'll stop using BUILD_ALIAS or if we have to keep using them, we'll switch to sprint numbers so we can differentiate between milestones in ide-config.properties.
> JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22355
> URL: https://issues.jboss.org/browse/JBIDE-22355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Final
>
>
> Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1.
> All those should be moved to Alpha2 (they should be moved just when branching/releasing actually)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22470?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22470:
------------------------------------
As you can see from the log, $\{eclipseName} is not defined.
{code}
Connecting to filemgmt.jboss.org...
Changing to: /downloads_htdocs/tools/
sftp> mkdir ${eclipseName}
Couldn't create directory: Failure
Connecting to filemgmt.jboss.org...
Changing to: /downloads_htdocs/tools/
sftp> mkdir ${eclipseName}/snapshots
Couldn't create directory: Failure
Connecting to filemgmt.jboss.org...
Changing to: /downloads_htdocs/tools/
sftp> mkdir ${eclipseName}/snapshots/updates
Couldn't create directory: Failure
Connecting to filemgmt.jboss.org...
Changing to: /downloads_htdocs/tools/
sftp> mkdir ${eclipseName}/snapshots/updates/integration-tests
Couldn't create directory: Failure
Connecting to filemgmt.jboss.org...
Changing to: /downloads_htdocs/tools/
sftp> mkdir ${eclipseName}/snapshots/updates/integration-tests/master
Couldn't create directory: Failure
[INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/${eclipseName}/snapshots/updates/integration-tests/master/
rsync: mkdir "/downloads_htdocs/tools//snapshots/updates/integration-tests/master" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(576) [receiver=3.0.6]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]
rsync: mkdir "/downloads_htdocs/tools//snapshots/updates/integration-tests/master/logs" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(576) [receiver=3.0.6]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]
[INFO] ------------------------------------------------------------------------
{code}
PR: https://github.com/jbosstools/jbosstools-integration-tests/pull/1521/files
> Integration tests not published to snapshots update site
> --------------------------------------------------------
>
> Key: JBIDE-22470
> URL: https://issues.jboss.org/browse/JBIDE-22470
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.0.Final
>
>
> For some reason the update site here is outdated (from March 9):
> http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t...
> We consume it here:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> The build is building just fine:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati...
> And the result is here:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int...
> But for some reason it's not propagated to the standard url.
> Can you please check why that is? I checked the config but could not understand what's wrong.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20026 at 6/2/16 4:17 PM:
------------------------------------------------------------------
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
The persistence is not implemented and handling of the most recently used connection is incorrect, it will store the most recently created connection (not the most recently used one).
{quote}
(10:09:01 PM) adietisheim: slava_: i see the wizard calling the model in ConnectionWizardPage#onPageDeactivated
(10:09:22 PM) adietisheim: slava_: but the code in the model to save it via ConnectionsRegistry#setRecent is commented
(10:10:10 PM) adietisheim: ConnectionsWizardPageModel#saveRecentConnection is commented
(10:11:57 PM) adietisheim: ah, persistence isnt impl'd at all, code is only holding it for the session.
(10:12:35 PM) adietisheim: slava_: ConnectionsRegistry#setRecent is not persisting it, it is only holding it for the current Eclipse session
(10:12:56 PM) adietisheim: but recentConnection is set when a new conn is created
(10:13:06 PM) adietisheim: so the logic is bullock at best
(10:13:24 PM) adietisheim: it's not the most recently used, but the most recently created connection
(10:13:42 PM) adietisheim: and then only for the current Eclipse session
{quote}
was (Author: adietish):
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
The persistence is not implemented and handling of the most recently used connection is incorrect, it will store the most recently created connection (not the most recently used one).
{quote}
(10:09:01 PM) adietisheim: slava_: i see the wizard calling the model in ConnectionWizardPage#onPageDeactivated
(10:09:22 PM) adietisheim: slava_: but the code in the model to persist it via ConnectionsRegistry (that has the impl) is commented
(10:09:35 PM) adietisheim: slava_: so I'd think that it's not being persisted, no
(10:10:10 PM) adietisheim: ConnectionsWizardPageModel#saveRecentConnection is commented
(10:11:57 PM) adietisheim: ah, persistence isnt impl'd at all, code is only holding it for the session. But the conn page isnt even calling it
(10:12:56 PM) adietisheim: but recentConnection is set when a new conn is created
(10:13:06 PM) adietisheim: so the logic is bullock at best
(10:13:24 PM) adietisheim: it's not the most recently used, but the most recently created connection
(10:13:42 PM) adietisheim: and then only for the current Eclipse session
{quote}
> Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20026 at 6/2/16 4:15 PM:
------------------------------------------------------------------
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
The persistence is not implemented and handling of the most recently used connection is incorrect, it will store the most recently created connection (not the most recently used one).
{quote}
(10:09:01 PM) adietisheim: slava_: i see the wizard calling the model in ConnectionWizardPage#onPageDeactivated
(10:09:22 PM) adietisheim: slava_: but the code in the model to persist it via ConnectionsRegistry (that has the impl) is commented
(10:09:35 PM) adietisheim: slava_: so I'd think that it's not being persisted, no
(10:10:10 PM) adietisheim: ConnectionsWizardPageModel#saveRecentConnection is commented
(10:11:57 PM) adietisheim: ah, persistence isnt impl'd at all, code is only holding it for the session. But the conn page isnt even calling it
(10:12:56 PM) adietisheim: but recentConnection is set when a new conn is created
(10:13:06 PM) adietisheim: so the logic is bullock at best
(10:13:24 PM) adietisheim: it's not the most recently used, but the most recently created connection
(10:13:42 PM) adietisheim: and then only for the current Eclipse session
{quote}
was (Author: adietish):
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
The connection wizard isnt saving the most recently used connection though. The code for it is commented, while the ConnectionsRegistry has the persistence implemented.
But this isnt urgent for 4.4.0.Final
> Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months