[JBoss JIRA] (JBIDE-14514) openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14514:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-14514
> URL: https://issues.jboss.org/browse/JBIDE-14514
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
>
> In the latest implementations the OpenShift broker returns the embedded cartridges within the application as follows:
> {code}
> "embedded":{
> "mongodb-2.2":{
> "connection_url":"mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/",
> "username":"admin",
> "password":"NNxXMT1z8dVj",
> "database_name":"springeap6",
> "info":"Connection URL: mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/"
> }
> },
> {code}
> Prior code was only returning the *info* property where we had to exctract the url via regex. The new broker is returning the *connection_url* which does not require any regex-treatment any more
> The code in openshift-java-client marks this workaround with a TODO:
> {code}
> protected EmbeddedCartridgeResource(final String name, final String displayName, final String description, final CartridgeType type, String info, final Map<String, Link> links,
> final Map<String, Message> messages, final ApplicationResource application) {
> super(application.getService(), links, messages);
> this.name = name;
> this.displayName = displayName;
> this.description = description;
> this.type = type;
> // TODO: fix this workaround once
> // https://bugzilla.redhat.com/show_bug.cgi?id=812046 is fixed
> this.url = extractUrl(info, messages);
> this.application = application;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (JBIDE-14720) No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14720?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14720:
---------------------------------------------
This looks like a compatibility issue somewhere in m2e.
Caused by: java.lang.RuntimeException: Property not located:JpaFacetInstallDataModelProperties.CREATE_ORM_XML
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.checkValidPropertyName(DataModelImpl.java:100)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getOwningDataModel(DataModelImpl.java:105)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:171)
at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getDataModel(JpaProjectConfigurator.java:176)
at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:131)
at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:98)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:245)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:102)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:780)
> No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1
> -------------------------------------------------------------------------------
>
> Key: JBIDE-14720
> URL: https://issues.jboss.org/browse/JBIDE-14720
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.1.0.Alpha2, 4.1.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Nick Boldt
> Attachments: jbosstools-diagnostics-20130601182344.zip, screenshot-after-wizard-has-completed.jpg
>
>
> 1) I'm using JBoss Tools version 2013-05-29_02-05-21-B272 which I got from http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core... and also the Java EE package for Kepler RC2.
> 2) I created a server config for JBossAS 7.1.0 (btw, same happens for EAP 6.1).
> 3) I created a new "Java EE Web Project".
> I'll attach a screenshot after the project wizard has completed, and also a "Help > Report Problem".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TOOLSDOC-353) Add info about how to update JBDS for minor releases
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-353?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-353:
------------------------------------------
See: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/README.md
{quote}
Update Red Hat JBoss Developer Studio
To update from one version of JBoss Developer Studio on the same stream to another (eg., from JBoss Developer Studio 6.0.0 to 6.0.1 or from 7.0.0 to 7.0.1):
Help > Install from the generated site in site/target/repository/ (or the installer jar, as noted above)
Uncheck the box for 'Group items by category'
Select the "JBoss Developer Studio (Branded Product)" feature
{quote}
> Add info about how to update JBDS for minor releases
> ----------------------------------------------------
>
> Key: TOOLSDOC-353
> URL: https://issues.jboss.org/browse/TOOLSDOC-353
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: Migration Guide
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> The Migration Guide contains info about moving between JBDS 6 to JBDS 7.
> Will need to add info to the guide on how to update from 7.0.0 to 7.0.x - is a fresh install required?
> Not necessary to do this for 7.0.0, but should do this in time for 7.0.1 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months