July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12209) Cloning settings dialog is not clear when creating new application

by Dan Allen (JIRA)

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11904) OpenShift Express Tool: Rebranding from "OpenShift Express" to just plain "OpenShift"

by Nam Duong (JIRA)

Nam Duong created JBIDE-11904: --------------------------------- Summary: OpenShift Express Tool: Rebranding from "OpenShift Express" to just plain "OpenShift" Key: JBIDE-11904 URL: https://issues.jboss.org/browse/JBIDE-11904 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta2 Environment: Eclipse plugin Reporter: Nam Duong Assignee: Andre Dietisheim In early April, the OpenShift hosted PaaS product was rebranded from "OpenShift Express" and "OpenShift Flex" to just plain "OpenShift". We also updated the logo. This is a request to update the logo and brand on the JBoss Tools. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-11389) New OpenShift Express Application Wizard does not take into account that cartridge "RockMongo 1.1" depends from cartridge "MongoDB NoSQL Database 2.0"

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-11389: ------------------------------------- Summary: New OpenShift Express Application Wizard does not take into account that cartridge "RockMongo 1.1" depends from cartridge "MongoDB NoSQL Database 2.0" Key: JBIDE-11389 URL: https://issues.jboss.org/browse/JBIDE-11389 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Daniel Azarov Assignee: Andre Dietisheim Attachments: RockMongoCartridge.png !RockMongoCartridge.png! New OpenShift Express Application Wizard should have the same behavior as for cartridges "phpMyAdmin 3.4" and "MySQL Database 5.1" 1. when user selects cartridge "RockMongo 1.1" wizard should propose select cartridge "MongoDB NoSQL Database 2.0" 2. when user selects both cartridges wizard should add cartridge "MongoDB NoSQL Database 2.0" before "RockMongo 1.1" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11041) It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously

by bin zhao (JIRA)

bin zhao created JBIDE-11041: -------------------------------- Summary: It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously Key: JBIDE-11041 URL: https://issues.jboss.org/browse/JBIDE-11041 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago) 64 Bit Reporter: bin zhao Assignee: Andre Dietisheim Priority: Critical 1. Create a new Openshift application for example: phptest 2. nested rockmongo-1.1 and mongodb-2.0 to the application of the php type 3. Edit the application and select mongodb-2.0 and rockmongo-1.1 from the embeddable cartridge and click 'Finish'. Notes: It has also the same issue for nested rockmongo-1.1 individually. Actual Result: It will popup "problem occured" dialog... Expect Result: For individually nested rockmongo, it should popup "warning dialog" said that Mongodb must be embedded before rockmongo. For simultaneously nested mongodb and rockmongo, it should be successful without any error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-11084) OpenShift Express: Unable to alter the application due to UI redesign

by Attila Nagy (JIRA)

Attila Nagy created JBIDE-11084: ----------------------------------- Summary: OpenShift Express: Unable to alter the application due to UI redesign Key: JBIDE-11084 URL: https://issues.jboss.org/browse/JBIDE-11084 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Attila Nagy Assignee: Andre Dietisheim I'm unable to alter an existing application in the Application Wizard. When I import an existing OpenShift Express application I'm able to see the details, however I cannot make any modifications like Add / Remove embedded cartridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11296) Refresh button doesn't update the list of applications available

by Gianfranco Sigrisi (JIRA)

Gianfranco Sigrisi created JBIDE-11296: ------------------------------------------ Summary: Refresh button doesn't update the list of applications available Key: JBIDE-11296 URL: https://issues.jboss.org/browse/JBIDE-11296 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Gianfranco Sigrisi Assignee: Andre Dietisheim Description of problem: devenv: 1658 Using Jboss-tools: JBoss OpenShift Express Tools 2.3.0.v20120229-1405-H46-Beta1 Version-Release number of selected component (if applicable): How reproducible: 1. create an app using rhc command line tools 2. on Eclipse, click on: Refresh button close to the one saying: Connect to Openshift. 3. The new application created will not show up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12095) JAX-RS facet in JBoss Tools chokes on package-info.java

by Craig Ringer (JIRA)

Craig Ringer created JBIDE-12095: ------------------------------------ Summary: JAX-RS facet in JBoss Tools chokes on package-info.java Key: JBIDE-12095 URL: https://issues.jboss.org/browse/JBIDE-12095 Project: Tools (JBoss Tools) Issue Type: Bug Environment: $ uname -a Linux wallace.localnet 3.3.0-1.fc17.x86_64 #1 SMP Mon Mar 19 03:03:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a LSB Version: :core-4.0-ia32:core-4.0-noarch Distributor ID: Fedora Description: Fedora release 17 (Beefy Miracle) Release: 17 Codename: BeefyMiracle $ java -version java version "1.7.0_b147-icedtea" OpenJDK Runtime Environment (fedora-2.1.fc17.6-x86_64) OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode) Eclipse Java EE IDE for Web Developers. Version: Indigo Service Release 2 Build id: 20120216-1857 JBoss JAX-RS Tools 1.2.2.v20120514-1752-H106-Beta3 org.jboss.tools.ws.jaxrs.feature.feature.group JBoss by Red Hat Reporter: Craig Ringer Priority: Minor The JBoss Tools org.jboss.tools.ws.jaxrs.core component seems to choke on package-info.java files in my Maven (m2Eclipse) project, spitting errors in the IDE log when I do a compile run in Eclipse: "Java Model Exception: Java Model Status [[Working copy] package-info.java [in au.com.postnewspapers.nymm.database [in src/main/java [in nymm]]] does not exist]" JBoss Tools versions are current from Marketplace: JBoss JAX-RS Tools 1.2.2.v20120514-1752-H106-Beta3 org.jboss.tools.ws.jaxrs.feature.feature.group JBoss by Red Hat JBoss JAX-RS Tools 1.2.2.v20120514-1752-H106-Beta3 org.jboss.tools.ws.jaxrs.feature.feature.group JBoss by Red Hat JBoss Maven CDI Configurator 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.cdi.feature.feature.group JBoss by Red Hat JBoss Maven Hibernate Configurator 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.hibernate.feature.feature.group JBoss by Red Hat JBoss Maven Integration 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.feature.feature.group JBoss by Red Hat JBoss Maven JAX-RS Configurator 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.jaxrs.feature.feature.group JBoss by Red Hat JBoss Maven JPA Configurator 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.jpa.feature.feature.group JBoss by Red Hat JBoss Maven JSF Configurator 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.jsf.feature.feature.group JBoss by Red Hat JBoss Maven Project Examples 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.project.examples.feature.feature.group JBoss by Red Hat JBoss Packaging Maven Configurators 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.jbosspackaging.feature.feature.group JBoss by Red Hat JBoss Runtime AS Detector 1.3.0.v20120504-1621-H89-Beta3 org.jboss.tools.runtime.as.detector.feature.feature.group JBoss by Red Hat JBoss Runtime Detection Core 1.3.0.v20120504-1621-H89-Beta3 org.jboss.tools.runtime.core.feature.feature.group JBoss by Red Hat JBoss Tools Community Project Examples 1.2.1.v20120504-1659-H91-Beta3 org.jboss.tools.community.project.examples.feature.feature.group JBoss by Red Hat JBoss Tools EGit Integration (Experimental) 2.3.0.v20120510-2034-H93-Beta3 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat JBoss Tools Java Standard Tools 3.3.0.v20120504-2056-H66-Beta3 org.jboss.tools.jst.feature.feature.group null JBoss Tools JDT Extensions 3.3.0.v20120510-2001-H58-Beta3 org.jboss.tools.common.jdt.feature.feature.group JBoss by Red Hat JBoss Tools JSF 3.3.0.v20120504-0520-H88-Beta3 org.jboss.tools.jsf.feature.feature.group JBoss by Red Hat JBoss Tools RichFaces 3.3.0.v20120504-0520-H88-Beta3 org.jboss.tools.richfaces.feature.feature.group JBoss by Red Hat JBoss Tools Source Lookup 1.3.0.v20120514-1625-H96-Beta3 org.jboss.tools.maven.sourcelookup.feature.feature.group JBoss by Red Hat JBoss Tools Usage Reporting 1.1.0.v20120504-2022-H52-Beta3 org.jboss.tools.usage.feature.feature.group JBoss by Red Hat JBoss Tools Visual Page Editor 3.3.0.v20120504-2124-H75-Beta3 org.jboss.tools.vpe.feature.feature.group null JBoss WebServices Tools 1.2.2.v20120514-1752-H106-Beta3 org.jboss.tools.ws.feature.feature.group JBoss by Red Hat -- Error Details -- Date: Tue Jun 05 13:42:04 WST 2012 Message: Failed while processing Java changes Severity: Error Product: Eclipse 1.4.2.20120131-1457 (org.eclipse.epp.package.jee.product) Plugin: org.jboss.tools.ws.jaxrs.core Session Data: eclipse.buildId=M20120208-0800 java.version=1.7.0_b147-icedtea java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product Exception Stack Trace: Java Model Exception: Java Model Status [[Working copy] package-info.java [in au.com.postnewspapers.nymm.database [in src/main/java [in nymm]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:505) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:518) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241) at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218) at org.jboss.tools.ws.jaxrs.core.jdt.JavaAnnotationsVisitor.<init>(JavaAnnotationsVisitor.java:75) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAnnotation(JdtUtils.java:311) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAnnotation(JdtUtils.java:371) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createApplication(JaxrsElementFactory.java:305) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:259) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:126) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-11563) OpenShift wizard allows to deploy alredy versioned project

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11563: -------------------------------------- Summary: OpenShift wizard allows to deploy alredy versioned project Key: JBIDE-11563 URL: https://issues.jboss.org/browse/JBIDE-11563 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta2 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta3 Stack trace: {code} org.jboss.tools.openshift.express.internal.ui.OpenShiftUIException: Could not enable OpenShift on project poh5. Theres already a a remote called {1} that points to a differnt git repository. at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ConfigureGitSharedProject.addRemote(ConfigureGitSharedProject.java:126) at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ConfigureGitSharedProject.execute(ConfigureGitSharedProject.java:106) at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.configureGitSharedProject(OpenShiftExpressApplicationWizardModel.java:162) at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:307) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
24
0 / 0

[JBoss JIRA] (JBIDE-12301) OpenShift server adapter fails to publish recreated project

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12301: -------------------------------------- Summary: OpenShift server adapter fails to publish recreated project Key: JBIDE-12301 URL: https://issues.jboss.org/browse/JBIDE-12301 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Final Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.x, 3.4.0.M1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
8
0 / 0

[JBoss JIRA] (JBIDE-12150) Git repository is sometimes corrupted after application creation

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12150: ------------------------------------- Summary: Git repository is sometimes corrupted after application creation Key: JBIDE-12150 URL: https://issues.jboss.org/browse/JBIDE-12150 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Blocker Fix For: 3.3.0.CR1 Attachments: JBIDE-12150.patch Steps to reproduce: create myapp in tools with openshift in ~/git/myapp take the git url and clone the app into a separate directory (to simulate other changes) mkdir temp cd temp git clone ssh:<specifichost>/myapp.git/ cd myapp edit README or some other existing file git commit -m "external change" README git push <ton of output> cd ~/git/myapp git push will now fail with something like: $ git push ~/git/appmy To ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/ ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'ssh://b8ab8a46a2984d16b1666f3b172c4199@appmy-man.rhcloud.com/~/git/appmy.git/' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes (e.g. 'git pull') before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details. Thus when trying to publish from tools it should not let you push and it should ask you before pushing with force. After [https://issues.jboss.org/browse/JBIDE-12138] has been fixed, user is prompted with a dialog that proposes to perform a "push force". While the operation seems to execute correctly, the following error is reported in the Error Log: {code} org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of push command at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:156) at org.eclipse.egit.core.op.PushOperation.run(PushOperation.java:194) at org.jboss.tools.openshift.egit.core.EGitUtils.push(EGitUtils.java:429) at org.jboss.tools.openshift.egit.core.EGitUtils.pushForce(EGitUtils.java:418) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.commitAndPushProject(ExpressPublishMethod.java:237) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishFinish(ExpressPublishMethod.java:80) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishFinish(DeployableServerBehavior.java:94) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishFinish(DelegatingServerBehavior.java:147) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:974) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.jgit.errors.TransportException: ssh://7ddb1e3809e54c969a568dd03889e90f@as-minipaas.example.com/~/git/as.git/: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:186) at org.eclipse.jgit.transport.BasePackPushConnection.push(BasePackPushConnection.java:126) at org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:141) at org.eclipse.jgit.transport.Transport.push(Transport.java:1120) at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:152) ... 14 more Caused by: org.eclipse.jgit.errors.MissingObjectException: Missing tree ecdd261c53993ae777f379662b52ceec35c2f7ed at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:126) at org.eclipse.jgit.revwalk.ObjectWalk.newTreeVisit(ObjectWalk.java:726) at org.eclipse.jgit.revwalk.ObjectWalk.nextObject(ObjectWalk.java:378) at org.eclipse.jgit.storage.pack.PackWriter.findObjectsToPack(PackWriter.java:1706) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:707) at org.eclipse.jgit.storage.pack.PackWriter.preparePack(PackWriter.java:670) at org.eclipse.jgit.transport.BasePackPushConnection.writePack(BasePackPushConnection.java:265) at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:168) ... 18 more {code} Going back to cmdline, it seems that the git repository is corrupted: {code} $ git fsck broken link from commit 70b2d1cf4705c118e5cac62d0c754df69f09fa32 to tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e missing blob 244cfe40684de36646d426ace17041cd25605cb2 missing tree b0e5eab13c7d5ca0d3e5b22418234bfb2b57e91e {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
45
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 2012