July 2014 - jbosstools-issues - Jboss List Archives

[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)

11 years, 9 months

1
0
0 / 0

[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)

11 years, 9 months

1
0
0 / 0

[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)

11 years, 9 months

1
0
0 / 0

[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)

11 years, 9 months

1
0
0 / 0

[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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17734) NPE when creating JAX-RS resource using undefined/empty Bean class

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17734?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17734: ---------------------------------- Sprint: Sprint to Beta3 Release > NPE when creating JAX-RS resource using undefined/empty Bean class > ------------------------------------------------------------------ > > Key: JBIDE-17734 > URL: https://issues.jboss.org/browse/JBIDE-17734 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3063) Java 6 warning disappears when you switch 32/64-bit in the installator

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3063?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3063: -------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/204 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/195) > Java 6 warning disappears when you switch 32/64-bit in the installator > ---------------------------------------------------------------------- > > Key: JBDS-3063 > URL: https://issues.jboss.org/browse/JBDS-3063 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > > This is a follow-up of this JIRA: > JBDS-2995 JBDS will not start with java 6 - a warning should be displayed during installation > When you get to Step 4 of the installer, where you select your Java VM, it shows a red warning if you select Java 6 and you cannot click Next unless you change to a supported java (7 or 8). That's ok. But if I change the 32/64-bit radio button, the warning will disappear. This is probably because we are dealing with another warning at the same time - VPE is not supported for selected Installation Type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17739) JUnit tests for jst.jsdt/tern adapters

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-17739: -------------------------------------- Summary: JUnit tests for jst.jsdt/tern adapters Key: JBIDE-17739 URL: https://issues.jboss.org/browse/JBIDE-17739 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3071: ------------------------------------- PR created to remove extra IU's https://github.com/jbdevstudio/jbdevstudio-product/pull/203 > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3071: -------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/196, https://github.com/jbdevstudio/jbdevstudio-product/pull/202, https://github.com/jbdevstudio/jbdevstudio-product/pull/203 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/196, https://github.com/jbdevstudio/jbdevstudio-product/pull/202) > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014