July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2922) Epic to cover issues related to 3rd party content that does not fit in specific epic

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2922?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2922: -------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > Epic to cover issues related to 3rd party content that does not fit in specific epic > ------------------------------------------------------------------------------------ > > Key: JBDS-2922 > URL: https://issues.jboss.org/browse/JBDS-2922 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2922) Epic to cover issues related to 3rd party content that does not fit in specific epic

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2922?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2922: -------------------------------------- Fix Version/s: 8.0.0.GA > Epic to cover issues related to 3rd party content that does not fit in specific epic > ------------------------------------------------------------------------------------ > > Key: JBDS-2922 > URL: https://issues.jboss.org/browse/JBDS-2922 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16303) Maven Pop-up should enable/expose mvn clean package

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16303?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-16303. ------------------------------------ Verified in JBDS 8.0.0.Beta3-v20140706-0939-B172 > Maven Pop-up should enable/expose mvn clean package > --------------------------------------------------- > > Key: JBIDE-16303 > URL: https://issues.jboss.org/browse/JBIDE-16303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Reporter: Jim Tyrrell > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > Attachments: mavenclean.png, Screen shot 2013-12-13 at 6.16.55 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When building and importing projects, every so often something goes sideways in the import/building of a project. I have to jump to the mvn command line and often I need to run mvn clean package to execute a "build" that re-sets whatever went sideways. Generally if the network goes away the above command will enable it to work. > If you know of other commands that should be exposed please let me know. > I wonder if Update Project should execute this command? I don't know enough about maven to know if this makes sense. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17795) JBoss Central New and Noteworthy for 4.2.0.Beta3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17795?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-17795. ------------------------------- Release Notes Text: (was: Central only has a bunch of bug fixes for Early Access and has angularjs-eclipse version bumped to 0.4. Doesn't deserve a N&N blurb IMO. closing.) Resolution: Rejected Central only has a bunch of bug fixes for Early Access and has angularjs-eclipse version bumped to 0.4. Doesn't deserve a N&N blurb IMO. closing. > JBoss Central New and Noteworthy for 4.2.0.Beta3 > ------------------------------------------------ > > Key: JBIDE-17795 > URL: https://issues.jboss.org/browse/JBIDE-17795 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17795) JBoss Central New and Noteworthy for 4.2.0.Beta3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17795?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-17795. ------------------------------- Release Notes Text: Central only has a bunch of bug fixes for Early Access and has angularjs-eclipse version bumped to 0.4. Doesn't deserve a N&N blurb IMO. closing. Resolution: Done > JBoss Central New and Noteworthy for 4.2.0.Beta3 > ------------------------------------------------ > > Key: JBIDE-17795 > URL: https://issues.jboss.org/browse/JBIDE-17795 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17740: ------------------------------------- Attachment: cannot-create-server-adapter.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 > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > Attachments: cannot-create-server-adapter.png, import-failed-uncommitted-changes.png, 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17740: ------------------------------------- Steps to Reproduce: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. EXPECTED RESULT: Question shell is shown or wizard is completed successfully and application on OpenShift is that one from the workspace (merged successfully). RESULT: There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). !import-failed-uncommitted-changes.png! Workaround via manually creating server adapter and pushing unfortunately wont work either: the existing project in the workspace does not have the openshift settings and wont be recognized as valid workspace for the server adapter: !cannot-create-server-adapter.png! was: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. EXPECTED RESULT: Question shell is shown or wizard is completed successfully and application on OpenShift is that one from the workspace (merged successfully). RESULT: There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). !import-failed-uncommitted-changes.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 > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > Attachments: import-failed-uncommitted-changes.png, 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-17393) Show on main Central page the "Early Access" status

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17393?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17393: ---------------------------------------- {quote}Wow! You guys don't make things simple do you {quote} We try to do our best ;) What do you think is too complicated? What do you suggest instead? Would you rather get Early Access automatically uninstalled when disabling it? That was my initial suggestion but for some reason, it was left aside. [~maxandersen] Do you remember why we chose to keep EA stuff installed? {quote}'Early Access features installed but disabled{quote} I don't think it's explicit? What's disabled, the features or Early Access? > Show on main Central page the "Early Access" status > --------------------------------------------------- > > Key: JBIDE-17393 > URL: https://issues.jboss.org/browse/JBIDE-17393 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > > The main Central page (not Software one) should show the "Early Access" status. It can be one of > * No Early Access component installed, no Early Access enabled (shows nothing) > * No Early Access component installed, Early Access enabled (shows Early Access enabled) > * at least 1 Early Access component installed, Early Access Enabled > * at least 1 Early Access component installed, Early Access not Enabled -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17740: ------------------------------------- Attachment: import-failed-uncommitted-changes.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 > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > Attachments: import-failed-uncommitted-changes.png, 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17740?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17740: ------------------------------------- Steps to Reproduce: EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). EXEC: Choose basic cartridge and click Next button (ex. EAP 6). EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. EXPECTED RESULT: Question shell is shown or wizard is completed successfully and application on OpenShift is that one from the workspace (merged successfully). RESULT: There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). !import-failed-uncommitted-changes.png! was: EXEC: Import a git based project into the workspace in JBT. EXEC: Launch New application wizard from OpenShift explorer. EXEC: Choose basic cartridge (I chose EAP) and click Next button. EXEC: Fill in name on the next wizard page and click Next. EXEC: Choose Use existing project and select the existing git based project. EXEC: Finish the wizard. EXEC: Wait for the Import application shell and confirm. EXPECTED RESULT: Question shell is shown or wizard is completed successfully and application on OpenShift is that one from the workspace (merged successfully). RESULT: There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > 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 > Assignee: Andre Dietisheim > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > Attachments: import-failed-uncommitted-changes.png, 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

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