Pavol Srna created JBIDE-10918:
----------------------------------
Summary: Forge: item does not exist
Key: JBIDE-10918
URL: https://issues.jboss.org/browse/JBIDE-10918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 3.3.0.M5
Environment: JBDS 5 M5, forge 1.0.0.CR2 runtime
Reporter: Pavol Srna
Assignee: Koen Aers
Fix For: 3.3.0.Beta1
Attachments: forge-screen.png
I am seeing some errors in the err log when creating number fields, but the field is generated successfully. See screenshot attached. This happens occasionally.
--
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
Fred Bricon created JBIDE-10834:
-----------------------------------
Summary: Investigate use of m2e-jdt-compiler 1.0.0 in JBDS 5, JBoss Central, target platforms & composite reqs mirror
Key: JBIDE-10834
URL: https://issues.jboss.org/browse/JBIDE-10834
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng, maven, updatesite, UpStream
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 3.3.0.Beta1
m2e-wtp 0.15.0 is about to be released. It should be included in our target platforms and composite reqs mirrors
--
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
Len DiMaggio created JBDS-2079:
----------------------------------
Summary: JBDS5 does not recognize a CXF runtime in a SOA-P 5.2 server install
Key: JBDS-2079
URL: https://issues.jboss.org/browse/JBDS-2079
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Tooling / Platform
Affects Versions: 5.0.0.Beta3-SOA
Environment: Version: 5.0.0.Beta2
Build id: v20120328-1758-H123-Beta2
Build date: 20120328-1758
Reporter: Len DiMaggio
Assignee: Brian Fitzpatrick
Priority: Critical
Fix For: 5.0.0.Beta3-SOA
Attachments: Apache-CXF.png, SOA-CXF- Runtime.png, SOA-CXF-jars.png
See the attached screenshots - JBDS can recognized a CXF runtime in an Apache CXF install, but not a SOA-P server install.
--
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
Openshift service: flag to enable/disable debug output is a STRING whereas it should be a boolean
-------------------------------------------------------------------------------------------------
Key: JBIDE-9691
URL: https://issues.jboss.org/browse/JBIDE-9691
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: LATER
The current API doc at https://github.com/openshift/os-client-tools/blob/master/express/doc/API states the following:
{code}
JSON String:
{
...
'debug': 'true - An optional flag to get debug information returned'
...
}
{code}
There's a flag that would allow you to turn debug output on. This flag is a String whereas the Json standard clearly has a boolean value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Max Rydahl Andersen created JBIDE-10845:
-------------------------------------------
Summary: Application configuration UI issues
Key: JBIDE-10845
URL: https://issues.jboss.org/browse/JBIDE-10845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Attachments: screenshot0.png
this page has a set of UI challenges - putting them in subtasks
--
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
Max Rydahl Andersen created JBIDE-10879:
-------------------------------------------
Summary: cannot change remote name to use for importing existing application
Key: JBIDE-10879
URL: https://issues.jboss.org/browse/JBIDE-10879
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.Beta1
--
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
Andre Dietisheim created JBIDE-10899:
----------------------------------------
Summary: There are many deprecated classes that we should clean up
Key: JBIDE-10899
URL: https://issues.jboss.org/browse/JBIDE-10899
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Xavier Coulon
Fix For: 3.3.0.CR1
The old wizard and pages that we had before we redesigned the UI are stil present in our codebase. We kept them to be easily able to copy code over to the new UI. We should now clean that stuff up and remove those old classes.
--
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
Andre Dietisheim created JBIDE-10723:
----------------------------------------
Summary: Cannot provide a custom branch to clone from OpenShift
Key: JBIDE-10723
URL: https://issues.jboss.org/browse/JBIDE-10723
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta1
The new "Project Configuration" wizard page does not allow a user to select a custom branch that shall be cloned from OpenShift.
We may have to discuss this in our next sync call and see if we really need this. afaik the rhc-tooling (cli) does not offer that either. we offered it in the previous version)
--
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
The new git repo that is created when creating a new project/enable existing project do not show up in the git repository view
------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10561
URL: https://issues.jboss.org/browse/JBIDE-10561
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M5
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta2
Attachments: add-existing-repo.png, repo-destination.png, repo-not-showing-up.png
We currently create a local git repo when we create a new (workspace) project when importing the OpenShift demo app or enable a preexisting project to be pushed to OpenShift. When importing the demo app, we clone the OpenShift git repo. When enabling a preexisting project for OpenShift, we create a new local git repo.
In both cases, the git repo that is created does not show up in the "Git Repositories" view ("Git Repository Exploring" perspective).
--
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