[JBoss JIRA] (JBIDE-16978) Update main template from latest version of community theme
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-16978:
-------------------------------------
Summary: Update main template from latest version of community theme
Key: JBIDE-16978
URL: https://issues.jboss.org/browse/JBIDE-16978
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: website
Affects Versions: 4.2.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta1
Based on a feedback mail from James Cobb:
{quote}
1) odd padding above the wrapper (putting space above the RH tab
2) odd padding on the left and write of the open tabbed content
3) missing the “A JBoss Project” tag to the left of the RH tab.
You can see how the tab is supposed to look here: http://example.jboss.org/
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Beta" stuff
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-16375:
--------------------------------------
Assignee: Mickael Istria
> Allow to extend Central extensions catalog with "Beta" stuff
> ------------------------------------------------------------
>
> Key: JBIDE-16375
> URL: https://issues.jboss.org/browse/JBIDE-16375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, discovery
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta2
>
>
> In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries.
> Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels.
> The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-2963) p2director compilation problem
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2963?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2963.
----------------------------
> p2director compilation problem
> -------------------------------
>
> Key: JBDS-2963
> URL: https://issues.jboss.org/browse/JBDS-2963
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 8.0.0.Beta1
>
>
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.19.0:compile (default-compile) on project com.jboss.devstudio.core.p2.director: Compilation failure: Compilation failure:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/p2-director/com.jboss.devstudio.core.p2.director/src/com/jboss/jbds/internal/p2/director/InstallerDirectorApplication.java:[301]
> [ERROR] private ProfileChangeRequest buildProvisioningRequest(IProfile profile, Collection<IInstallableUnit> installs, Collection<IInstallableUnit> uninstalls) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16976) OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16976:
------------------------------------------
This is what EGit is throwing. When reporting the error I add the reason "an exception occurred when creating the local git repository" and put the exception that's thrown to the error details. I guess that if I'd unpack what EGit throws I'd unveil a nested Auth error. Not sure if we really want to unpack exceptions thrown by EGit since the nesting is not API. We could - as a general rule - "unpack" TargetInvocationErrors and display the exception within it.
> OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16976
> URL: https://issues.jboss.org/browse/JBIDE-16976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Attachments: error_dialog.png
>
>
> When creating application and following import (git clone after creation process is completed) in case of no SSH key/not added into preferences dialog there is a error dialog with description, that something went wrong during git clone (respectively creating local git repo) and exception thrown.
> !error_dialog.png!
> It would be nice to have in the dialog, that problem is caused by missing SSH key or at least remove InvocationTargetException from error message - it is useless for user.
> Error log stack trace
> {code}
> java.lang.reflect.InvocationTargetException
> at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:176)
> at org.jboss.tools.openshift.egit.core.EGitUtils.cloneRepository(EGitUtils.java:270)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.AbstractImportApplicationOperation.cloneRepository(AbstractImportApplicationOperation.java:169)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:77)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.importProject(OpenShiftApplicationWizardModel.java:103)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:353)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.IllegalStateException: Preference node "null" has been removed.
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.checkRemoved(SecurePreferences.java:354)
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.nodeExists(SecurePreferences.java:100)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.nodeExists(SecurePreferencesWrapper.java:94)
> at org.eclipse.egit.core.securestorage.EGitSecureStore.clearCredentials(EGitSecureStore.java:108)
> at org.eclipse.egit.ui.internal.credentials.EGitCredentialsProvider.reset(EGitCredentialsProvider.java:142)
> at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:125)
> at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121)
> at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248)
> at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147)
> at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136)
> at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122)
> at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1111)
> at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130)
> at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:178)
> at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125)
> at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:156)
> ... 7 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months