[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17741:
----------------------------------
Attachment: cartridges_decorator.png
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as it was in the previous versions, bcs. it is only description, not the cartridge name (or at least, it's internal cartridge name and it is not appropriate to show it to the users like this).
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-17741:
-------------------------------------
Summary: Embeddable cartridges description is not decorated
Key: JBIDE-17741
URL: https://issues.jboss.org/browse/JBIDE-17741
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta3
Reporter: Marián Labuda
Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as it was in the previous versions, bcs. it is only description, not the cartridge name (or at least, it's internal cartridge name and it is not appropriate to show it to the users like this).
!cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17740) Cannot deploy git-based project to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17740:
----------------------------------
Attachment: import.png
> Cannot deploy git-based project to OpenShift
> --------------------------------------------
>
> Key: JBIDE-17740
> URL: https://issues.jboss.org/browse/JBIDE-17740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: import.png
>
>
> It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
> See log
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
> !MESSAGE Could not import project to the workspace.
> !STACK 0
> org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> !import.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17740) Cannot deploy git-based project to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17740:
----------------------------------
Description:
It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
See log
{code}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
!MESSAGE Could not import project to the workspace.
!STACK 0
org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
Error shell:
!import.png!
was:
It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
See log
{code}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
!MESSAGE Could not import project to the workspace.
!STACK 0
org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
!import.png!
> Cannot deploy git-based project to OpenShift
> --------------------------------------------
>
> Key: JBIDE-17740
> URL: https://issues.jboss.org/browse/JBIDE-17740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: import.png
>
>
> It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
> See log
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
> !MESSAGE Could not import project to the workspace.
> !STACK 0
> org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
> at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> Error shell:
> !import.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17740) Cannot deploy git-based project to OpenShift
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-17740:
-------------------------------------
Summary: Cannot deploy git-based project to OpenShift
Key: JBIDE-17740
URL: https://issues.jboss.org/browse/JBIDE-17740
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta3
Reporter: Marián Labuda
Priority: Blocker
It is not possible to deploy existing git based project to the OpenShift instance. What's going to happen is that new OpenShift project is created, but existing git project is not merged. As result there is a project based on basic cartridge and not on existing project. There is a issue with git changes - uncommitted changes required to commit first, but it is not possible bcs. remote is still set to the old one git remote.
See log
{code}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2014-07-02 08:52:28.848
!MESSAGE Could not import project to the workspace.
!STACK 0
org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project jboss-javaee6-webapp has uncommitted changes. Please commit those changes first.
at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.MergeIntoGitSharedProject.execute(MergeIntoGitSharedProject.java:97)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.mergeIntoGitSharedProject(OpenShiftApplicationWizardModel.java:186)
at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:376)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
!import.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17635) EAP 6.0.x has wrong links in the runtime download table
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17635?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17635.
---------------------------------
Resolution: Done
PR accepted by Rafael
> EAP 6.0.x has wrong links in the runtime download table
> -------------------------------------------------------
>
> Key: JBIDE-17635
> URL: https://issues.jboss.org/browse/JBIDE-17635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
> Attachments: download-links.png, eap-6.0.0-downloads.png, eap-6.0.0-zip-page.png, eap-6.0.1-downloads.png, eap-6.0.1-zip-page.png, eap-product-page.png
>
>
> In JBIDE-17500, direct links to access.redhat.com for EAP 6.0.x download were added.
> These links show up nicely when you progress through the runtime download dialog - i.e. after you accept the license.
> But it shows up wrong in the table that lists all the available runtimes for download:
> !download-links.png!
> For some reason the download link shows as Project URL. And Download URL is empty.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17709) Application wizard, Explorer, Domain wizard: decorate domains (explorer), dont show domains without write permissions (app wizard)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17709?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-17709:
---------------------------------------
We should *not* go further? Isn't it a typo?
> Application wizard, Explorer, Domain wizard: decorate domains (explorer), dont show domains without write permissions (app wizard)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17709
> URL: https://issues.jboss.org/browse/JBIDE-17709
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Labels: application_wizard, domain_wizard, explorer
> Fix For: 4.3.x
>
>
> In JBDS-2777 we added a link to the web-ui where one can edit the domain members.
> We should not go further:
> * decorate domains in the explorer with icons that show your permissions (view/write)
> * dont show domains in application wizard, where we dont have write permissions
> * domain wizard should have a column with access-rights where the domains are listed
> * etc.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17735?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17735:
----------------------------------
Sprint: Sprint to Beta3 Release
> JAX-RS Application wizard: double comments in generated class
> -------------------------------------------------------------
>
> Key: JBIDE-17735
> URL: https://issues.jboss.org/browse/JBIDE-17735
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package.
> {code}
> @ApplicationPath("/rest")
> /**
> *
> */
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> When it is generated into user defined package, then there is just one java doc comment:
> {code}
> @ApplicationPath("/rest")
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years