July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17831) Application wizard: stuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-17831: ---------------------------------------- Summary: Application wizard: stuck with application but existing project cannot be merged: uncommitted changes Key: JBIDE-17831 URL: https://issues.jboss.org/browse/JBIDE-17831 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Beta3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.2.0.Beta3 Attachments: cannot-create-server-adapter.png, git-log.png, import-failed-uncommitted-changes.png, import.png, push-force.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) Application wizard: 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: ------------------------------------- Summary: Application wizard: Cannot deploy git-based project to OpenShift (was: Cannot deploy git-based project to OpenShift) > Application wizard: 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: application_wizard, respin-a > Fix For: 4.2.0.Beta3 > > Attachments: cannot-create-server-adapter.png, git-log.png, import-failed-uncommitted-changes.png, import.png, push-force.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) Application wizard: 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: ------------------------------------- Labels: application_wizard respin-a (was: respin-a) > Application wizard: 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: application_wizard, respin-a > Fix For: 4.2.0.Beta3 > > Attachments: cannot-create-server-adapter.png, git-log.png, import-failed-uncommitted-changes.png, import.png, push-force.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-17830) ResourceException: Resource '<projectName>/plugins' does not exist

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-17830: -------------------------------------- Summary: ResourceException: Resource '<projectName>/plugins' does not exist Key: JBIDE-17830 URL: https://issues.jboss.org/browse/JBIDE-17830 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.CR1 Reporter: Alexey Kazakov I cloned and imported https://github.com/sebastienblanc/testionic Every time I run Eclipse I see the following exception in the log: {code} org.eclipse.core.internal.resources.ResourceException: Resource '/testionic/plugins' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:136) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:115) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.updatePluginList(CordovaPluginManager.java:428) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getInstalledPlugins(CordovaPluginManager.java:271) at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getCordovaPluginJSContent(CordovaPluginManager.java:300) at org.jboss.tools.aerogear.hybrid.core.internal.libraries.CordovaLibraryJsContainerInitializer.getPluginJsIncludePathEntry(CordovaLibraryJsContainerInitializer.java:99) at org.jboss.tools.aerogear.hybrid.core.internal.libraries.CordovaLibraryJsContainerInitializer.getIncludepathEntries(CordovaLibraryJsContainerInitializer.java:84) at org.eclipse.wst.jsdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2753) at org.eclipse.wst.jsdt.internal.core.ClasspathChange.generateDelta(ClasspathChange.java:206) at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1909) at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:156) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Marcel Neuwohner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Marcel Neuwohner commented on JBIDE-17724: ------------------------------------------ Max Rydahl Andersen, I already tried changing the Application Reload Pattern from \.jar$ to something else but it didn't change anything at all. We also have dozens of jars bundled in our war. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Priority: Blocker > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17823) Seam Wizard should set seam 2.3 as default with Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17823?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17823: ----------------------------------- Labels: (was: respin-a) > Seam Wizard should set seam 2.3 as default with Wildfly > ------------------------------------------------------- > > Key: JBIDE-17823 > URL: https://issues.jboss.org/browse/JBIDE-17823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.Beta3 > Reporter: Rastislav Wagner > 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] (JBIDE-17823) Seam Wizard should set seam 2.3 as default with Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17823?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17823: ----------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Seam Wizard should set seam 2.3 as default with Wildfly > ------------------------------------------------------- > > Key: JBIDE-17823 > URL: https://issues.jboss.org/browse/JBIDE-17823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.Beta3 > Reporter: Rastislav Wagner > 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] (JBIDE-17823) Seam Wizard should set seam 2.3 as default with Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17823?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17823: -------------------------------------- Assignee: Alexey Kazakov > Seam Wizard should set seam 2.3 as default with Wildfly > ------------------------------------------------------- > > Key: JBIDE-17823 > URL: https://issues.jboss.org/browse/JBIDE-17823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.Beta3 > Reporter: Rastislav Wagner > Assignee: Alexey Kazakov > 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] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Cody Lerum commented on JBIDE-17724: ------------------------------------ [~maxandersen] The project unfortunately closed. I can probably toss a sample ee6 project together to repo if necessary. There are 101 jars within the exploded war i.e. oss.war\WEB-INF\lib\*.jar these are brought in by maven. Java files from the project are at oss.war\WEB-INF\classes\*\*\*\*.class Not sure if it matters, but an edit to an .xhtml file causes the reload too. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Priority: Blocker > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17829) server adapter wizard has conflicitng UI/warning about runtime environment

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17829: --------------------------------------------- demo of funky validaiton: http://www.screencast.com/users/max.rydahl.andersen/folders/Jing/media/6f... screenshot of actual chosen runtime: http://screencast.com/t/o78SizRO and yeah it starts with Java 6. marking this a blocker. > server adapter wizard has conflicitng UI/warning about runtime environment > -------------------------------------------------------------------------- > > Key: JBIDE-17829 > URL: https://issues.jboss.org/browse/JBIDE-17829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > I have only Java 6 JDK in eclipse. > Create server > Wildfly 8 (download and install runtime now works sanely- yay!) > gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected. > and when I change to 1.8 it says it can't find one for 1.7...something is weird. > Then I add Java 7, choose Java 7 and save. > When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries. > So something is *really* wrong. -- 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