[
https://issues.jboss.org/browse/JBIDE-11152?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-11152 at 3/3/12 4:45 AM:
------------------------------------------------------------------
@Max: to me this looks like a bug in the pom merging process, looks like adding the
"openshift" profile is not working any longer. We should always be able to add
the "openshift" profile, regardless if the result is a buildable project or not.
Shouldn't we? What do I miss?
Btw. The richfaces project is the project I used to easily test if I could push force to
the PaaS. It used to work.
was (Author: adietish):
@Max: to me this looks like a bug in the pom merging process, looks like adding the
"openshift" profile is not working any longer. We should always be able to add
the "openshift" profile, regardless if the result is a buildable project.
Shouldn't we? What do I miss?
Btw. The richfaces project is the project I used to easily test if I could push force to
the PaaS. It used to work.
OpenShift profile is not merged into existing pom (of
richfaces-webapp)
-----------------------------------------------------------------------
Key: JBIDE-11152
URL:
https://issues.jboss.org/browse/JBIDE-11152
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Attachments: console-output-no-openshift-profile.png,
create-richfaces-demoapp.png, richfaces-existing-project.png
--
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