[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-21742:
------------------------------------------
Attachment: SecureStorageAccessFailure.png
> 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
> Fix For: 4.3.1.CR1
>
> Attachments: SecureStorageAccessFailure.png
>
>
> 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-21680) Trouble installing Hibernate Tools
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21680?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21680:
----------------------------------------
cc: [~nickboldt]
> Trouble installing Hibernate Tools
> ----------------------------------
>
> Key: JBIDE-21680
> URL: https://issues.jboss.org/browse/JBIDE-21680
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.1.Beta2
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.1.CR1
>
>
> Hello,
> I was attempting to install the Hibernate Tools for a quick demo but it somehow managed to confuse me.. I probably should know better, but I imagine this could represent quite some population out there.
> I headed for the Eclipse marketplace (not the web page but the UI element within Eclipse) after a clean installation of Eclipse Mars update 1.
> I search for "Hibernate Tools", and then it seems I have to choose between "Indigo" and "Helios".
> TBH I didn't remember that those were Eclipse codename versions, so that's one problem.. I get in trouble trying to install either of course and it takes me a while to figure I need to search for "JBoss Tools" instead.. and probably reinstall my whole IDE to clean the mess.
> Searching for "JBoss Tools" isn't great either BTW as the correct result is just third, which means it's not even visible without using the scrollbar..
> I understand we want to push the "JBoss Tools" portfolio but ultimately I think we'd be better off by making sure that people get the right stuff when searching for "Hibernate Tools", as lots of people are accustomed to this name nowadays?
> Thanks,
> Sanne
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21759) Rename JBoss Perspective into Red Hat perspective?
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21759:
-----------------------------------
Summary: Rename JBoss Perspective into Red Hat perspective?
Key: JBIDE-21759
URL: https://issues.jboss.org/browse/JBIDE-21759
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 4.3.1.Beta2
Reporter: Fred Bricon
Given that we're supposed to use the JBoss brand to reference products only, I believe the JBoss Perspective just then be renamed to Red Hat Perspective. Amirite?
cc: [~maxandersen], [~crobson]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21733) Docker connection does not work with CDK build 2016-02-19
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21733?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-21733:
-------------------------------------------
{quote}
this has been fixed in linked issue
{quote}
nice
> Docker connection does not work with CDK build 2016-02-19
> ---------------------------------------------------------
>
> Key: JBIDE-21733
> URL: https://issues.jboss.org/browse/JBIDE-21733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-02-19 in JBDS 9.1.0.Beta2:
> When I started this from JBDS, it worked, but the Docker connection could not be established.
> It gives me this error:
> {code}
> com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:779)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:742)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider$1$1.run(DockerImagesContentProvider.java:71)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:772)
> ... 27 more
> Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070)
> ... 29 more
> Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517)
> at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523)
> at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1506)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469)
> ... 20 more
> Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
> at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1488)
> ... 39 more
> Caused by: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
> at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
> at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
> ... 45 more
> Caused by: java.security.SignatureException: Signature does not match.
> at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:449)
> at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166)
> at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147)
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
> ... 50 more
> {code}
> To be sure, I also tried the other cdk from https://github.com/redhat-developer-tooling/openshift-vagrant and that worked. Then I tried back the official cdk and that didn't work.
> I'm pretty sure that this worked for me with the previous build. Not sure what changed.
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3602:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> 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] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3602:
-----------------------------
> 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-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21734:
----------------------------------------
Just as a hint. It would be useful to see screenshots of new UI stuff you are adding/changing ;)
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: ambiguous_connection.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21757) Rename JBoss Central into Red Hat Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21757?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21757:
--------------------------------
Description:
Need to rename JBoss Central into Red Hat Central
- change all text references of Central in plugins
- change all text references of Central in webpage
- use Red Hat icon for Central tab in Eclipse
- make Eclipse point to new version of webpage in ide-config.properties
was:
Need to rename JBoss Central into Red Hat Central
- change all text references
- use Red Hat icon for Central tab in Eclipse
> Rename JBoss Central into Red Hat Central
> -----------------------------------------
>
> Key: JBIDE-21757
> URL: https://issues.jboss.org/browse/JBIDE-21757
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Need to rename JBoss Central into Red Hat Central
> - change all text references of Central in plugins
> - change all text references of Central in webpage
> - use Red Hat icon for Central tab in Eclipse
> - make Eclipse point to new version of webpage in ide-config.properties
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month