[JBoss JIRA] (JBIDE-11162) Allow java/maven projects to be used as *existing* projects
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-11162:
----------------------------------------
Summary: Allow java/maven projects to be used as *existing* projects
Key: JBIDE-11162
URL: https://issues.jboss.org/browse/JBIDE-11162
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta2
When enabling OpenShift on *existing projects*, one has to pick a project from its local workspace. We currently only allow Eclipse *WTP* (dynamic web) projects to be chosen. Since the OpenShift *server adapter* is now not bound to AS7 any more and does just git push behind the scenes, everything's ready so that we could now allow *java/maven* projects to be picked when chooing an existing project.
--
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, 10 months
[JBoss JIRA] (JBIDE-10666) Delete OpenShift domain with JBoss tooling
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-10666:
--------------------------------------
Summary: Delete OpenShift domain with JBoss tooling
Key: JBIDE-10666
URL: https://issues.jboss.org/browse/JBIDE-10666
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
OpenShift wizard should provide a way how to remove domain, as the CLI client supports it:
rhc-ctl-domain -l [-p ] (-a [-k ] | -r | -u [-k ])
-l|--rhlogin rhlogin Red Hat login (RHN or OpenShift login
with OpenShift Express access) (required)
-p|--password password RHLogin password (optional, will prompt)
-n|--namespace namespace Namespace for your application(s)
(alphanumeric - max 16 chars)
(required for destroying domain)
-a|--add-ssh-key key-name Add SSH key to the user account
(key-name is the user-specified
identifier for the key)
-r|--remove-ssh-key key-name Remove SSH key from the user account
-u|--update-ssh-key key-name Update SSH key for the user account
--destroy Destroys the domain and any added ssh
keys
-k|--ssh key-filepath SSH public key filepath
--config path Path of alternate config file
-d|--debug Print Debug info
-h|--help Show Usage info
--
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, 10 months
[JBoss JIRA] (JBIDE-11540) Bean stereotypes are computed incorrectly
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-11540:
---------------------------------------------
Summary: Bean stereotypes are computed incorrectly
Key: JBIDE-11540
URL: https://issues.jboss.org/browse/JBIDE-11540
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
If a bean is annotated by stereotype A it inherits all additional stereotypes declared in A (see 2.7.1.5). All those stereotypes are to be taken into account when computing bean name, scope, enablement, and looking for @alternative. Additional stereotypes are inherited independently of annotation @Inherit on stereotype, which only controls inheritance from super classes.
Test that shows the problem with named beans:
EXECUTE: Create stereotypes FirstStereotype, SecondStereotype and bean Bean
{code}
@Stereotype
@Named
@Target({ TYPE})
@Retention(RUNTIME)
@Documented
public @interface FirstStereotype {
}
{code}
{code}
@Stereotype
@FirstStereotype
@Target({ TYPE})
@Retention(RUNTIME)
@Documented
public @interface SecondStereotype {
}
{code}
{code}
@SecondStereotype
public class Bean {
}
{code}
ASSERT: EL name "bean" is available.
--
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, 10 months
[JBoss JIRA] (JBIDE-11236) gwt-kitchensink not working when deployed from within JBT
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-11236:
----------------------------------
Summary: gwt-kitchensink not working when deployed from within JBT
Key: JBIDE-11236
URL: https://issues.jboss.org/browse/JBIDE-11236
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.Beta1
Environment: JBT 3.3.0.Beta1e on eclipseEE indigo SR2
Fedora 16
Oracle java 1.7.0_02-b13 64b
Reporter: Radim Hopp
Assignee: Snjezana Peco
Fix For: 3.3.0.Beta1
Attachments: gwt-kitchensink.png
GWT Web Project is not working, when deployed from within JBDS or JBT (using steps described in README.md).
When deployed, only header, footed and the right "Find out more" panel is shown.
When deployed from command line using `mvn package` -> `mvn jboss-as:deploy` everything is working as expected.
--
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, 10 months