[JBoss JIRA] (JBTIS-560) Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-560?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-560.
----------------------------
Fix Version/s: 4.3.1.Beta1b
Resolution: Done
https://github.com/jbosstools/jbosstools-integration-stack/commit/23e836f...
Found in devstudio production build - fixed in 4.3.1.Beta1b-SNAPSHOT
> Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-560
> URL: https://issues.jboss.org/browse/JBTIS-560
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.Beta1b
>
>
> *Reason:* Missing package org.jboss.tools.locus.mockito
> *Project page/sources:*
> *Version:* 1.9.5
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBTIS
> *Include in JBDS:* Yes JBDSIS
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> > org.jboss.tools.locus.mockito [1.9.5.v20131024-0922]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 1 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-560) Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-560?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-560:
-----------------------------
Description:
*Reason:* Missing package org.jboss.tools.locus.mockito
*Project page/sources:*
*Version:* 1.9.5
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBTIS
*Include in JBDS:* Yes JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
> org.jboss.tools.locus.mockito [1.9.5.v20131024-0922]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 1 unique IUs
{code}
was:
*Reason:* Missing package
*Project page/sources:*
*Version:* 3.1.1
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBTIS
*Include in JBDS:* Yes JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
org.jboss.ide.eclipse.as.dmr
{code}
> Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-560
> URL: https://issues.jboss.org/browse/JBTIS-560
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Missing package org.jboss.tools.locus.mockito
> *Project page/sources:*
> *Version:* 1.9.5
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBTIS
> *Include in JBDS:* Yes JBDSIS
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> > org.jboss.tools.locus.mockito [1.9.5.v20131024-0922]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 1 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-560) Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-560?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-560:
-----------------------------
Summary: Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation. (was: Add org.jboss.ide.eclipse.as.dmr bundle to the JBTIS TP (core dep).)
> Add bundle org.jboss.tools.locus.mockito for org.fusesource.ide.camel.validation.
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-560
> URL: https://issues.jboss.org/browse/JBTIS-560
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Missing package
> *Project page/sources:*
> *Version:* 3.1.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBTIS
> *Include in JBDS:* Yes JBDSIS
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> org.jboss.ide.eclipse.as.dmr
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21645) No build config warning dialog shown when opening Import Application... on OS3 connection
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21645?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21645:
---------------------------------------
[~fbricon] we could leave this open to enhance the workflow to add in a method for choosing the build config, but it would have to be post 4.3.x i think
> No build config warning dialog shown when opening Import Application... on OS3 connection
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-21645
> URL: https://issues.jboss.org/browse/JBIDE-21645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: import_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: no_build_config.png
>
>
> When I am trying to import a new application via connection context menu Import Application..., I get following warning dialog
> !no_build_config.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21742:
----------------------------------
Labels: connection openshift_v3 security_domain (was: )
> Secure storage of OpenShift 3 token does not work
> -------------------------------------------------
>
> Key: JBIDE-21742
> URL: https://issues.jboss.org/browse/JBIDE-21742
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: connection, openshift_v3, security_domain
>
> When I have already user secure storage in another session (password is set) and I fill in valid token and check checkbox to store token in secure storage, confirmation dialog of secure storage is shown upon hitting Finish button. Upon filling invalid secure storage password for first time, dialog is invoked again to enter password. After second filling of invalid password for secure storage, it looks like it passed - no other prompt nor error dialog (just in error log see stack trace) and even in Connection dialog (opened via Edit context menu item on the connection) is checkbox for secure storage checked, what is wrong, because it is not stored (checked secure storage preference page and its content and also after restart of eclipse it was not stored).
> {code}
> org.jboss.tools.openshift.internal.common.core.security.SecureStoreException: Could not store value token: iQKo-5jRkMeaegCi3mljsFsAXhNaogmzwaKeaQNUAxc
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:104)
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.put(SecureStore.java:57)
> at org.jboss.tools.openshift.core.connection.Connection.saveOrClear(Connection.java:187)
> at org.jboss.tools.openshift.core.connection.Connection.save(Connection.java:159)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:207)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:424)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:368)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:355)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:60)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:95)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110)
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:102)
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21742:
-------------------------------------
Summary: Secure storage of OpenShift 3 token does not work
Key: JBIDE-21742
URL: https://issues.jboss.org/browse/JBIDE-21742
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
When I have already user secure storage in another session (password is set) and I fill in valid token and check checkbox to store token in secure storage, confirmation dialog of secure storage is shown upon hitting Finish button. Upon filling invalid secure storage password for first time, dialog is invoked again to enter password. After second filling of invalid password for secure storage, it looks like it passed - no other prompt nor error dialog (just in error log see stack trace) and even in Connection dialog (opened via Edit context menu item on the connection) is checkbox for secure storage checked, what is wrong, because it is not stored (checked secure storage preference page and its content and also after restart of eclipse it was not stored).
{code}
org.jboss.tools.openshift.internal.common.core.security.SecureStoreException: Could not store value token: iQKo-5jRkMeaegCi3mljsFsAXhNaogmzwaKeaQNUAxc
at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:104)
at org.jboss.tools.openshift.internal.common.core.security.SecureStore.put(SecureStore.java:57)
at org.jboss.tools.openshift.core.connection.Connection.saveOrClear(Connection.java:187)
at org.jboss.tools.openshift.core.connection.Connection.save(Connection.java:159)
at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:207)
at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:424)
at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:368)
at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:355)
at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:60)
at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:95)
at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.
at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304)
at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224)
at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224)
at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110)
at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:102)
... 11 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3602:
------------------------------------
Yes - It's working now:
https://redhat.ctrlflow.com/community/#/incidents/KlY7xVgtidWyZMElwnlpR53...
> Error Reporting doesnt work since we do not set eclipse.buildid
> ---------------------------------------------------------------
>
> Key: JBDS-3602
> URL: https://issues.jboss.org/browse/JBDS-3602
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: aeri
> Affects Versions: 9.1.0.CR1
> Environment: JBDS 9.1.0.CR1-v20160222-0232-B335
> JBT Nightly (2016-02-22)
> both contains the same version of aeri plugins
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
>
> So I tied to evoke error reporting dialog with the following scenario:
> 1. import Java EE Web Project from central
> 2. right click in Project Explorer -> refactor -> rename
> 3. change name, hit OK which will result in errors from org.hibernate stuff
> In case of JBDS no error reporting dialog is shown, works in JBT
> I also tried org.eclipse stuff:
> 1. open Properties view
> 2. create JPA Project (File -> New -> Other... JPA Project)
> 3. open persistence.xml which will result in NPE from org.eclipse stuff
> And again in no error reporting dialog in case of JBDS but works in JBT
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21670) Remove ImageStreamTag from WatchManager
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21670?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21670.
---------------------------------
> Remove ImageStreamTag from WatchManager
> ---------------------------------------
>
> Key: JBIDE-21670
> URL: https://issues.jboss.org/browse/JBIDE-21670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> Watch of ImageStreamTags is unsupported by the server and causes:
> {{
> [DEBUG] 2016-02-09 10:39:33,901 com.openshift.internal.restclient.WatchClient - WatchSocket Error
> org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> [DEBUG] 2016-02-09 10:39:33,902 com.openshift.internal.restclient.WatchClient - WatchSocket Error
> org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.validateResponse(UpgradeConnection.java:314)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.read(UpgradeConnection.java:241)
> at org.eclipse.jetty.websocket.client.io.UpgradeConnection.onFillable(UpgradeConnection.java:163)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21628) Server Adapter: Service widget is empty
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21628?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21628.
---------------------------------
Verified on nightly build of JBT with OpenShift tooling B190.
> Server Adapter: Service widget is empty
> ---------------------------------------
>
> Key: JBIDE-21628
> URL: https://issues.jboss.org/browse/JBIDE-21628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: empty_service.png
>
>
> In OpenShift 3 Server Adapter overview are widgets with information related to server adapter. There is a text widget for a service but it is empty although server adapter is connected to a specific service. See following screenshot
> !empty_service.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month