[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12121:
-----------------------------------
Summary: The openshift profile is added to newly created maven projects, regardless of their packaging type
Key: JBIDE-12121
URL: https://issues.jboss.org/browse/JBIDE-12121
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Fred Bricon
Assignee: Andre Dietisheim
Fix For: 3.3.1
I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog)
This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project :
{code:xml}
<profiles>
<profile>
<!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
<!-- Use this profile for any OpenShift specific customization your app will need. -->
<!-- By default that is to put the resulting archive into the deployments folder. -->
<!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
<id>openshift</id>
<build>
<finalName>hello</finalName>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
{code}
Actually, it should :
- check the packaging type of *all* the generated projects
- if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) :
{code:xml}
<profile>
<id>openshift</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-ear-plugin</artifactId>
<version>2.7</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
{code}
- if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) :
{code:xml}
<profiles>
<profile>
<id>openshift</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.2</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
<!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
{code}
The finalName is irrelevant to openshift, only the warName counts.
--
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
11 years, 7 months
[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-12098:
--------------------------------------
Summary: OpenShift Explorer: Timeout exception when forcing domain deletion
Key: JBIDE-12098
URL: https://issues.jboss.org/browse/JBIDE-12098
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.CR1, 3.3.x
Attachments: deletedomain.png
Tried to force domain deletion while having (medium geared) application on OpenShift.
Screenshot:
!deletedomain.png|thumbnail!
Stack trace:
{code}
com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:109)
at com.openshift.internal.client.RestService.request(RestService.java:89)
at com.openshift.internal.client.RestService.request(RestService.java:74)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
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
11 years, 7 months
[JBoss JIRA] (JBIDE-12371) Update Eclipse Target Platform to use Graphiti 0.9
by Rob Cernich (JIRA)
Rob Cernich created JBIDE-12371:
-----------------------------------
Summary: Update Eclipse Target Platform to use Graphiti 0.9
Key: JBIDE-12371
URL: https://issues.jboss.org/browse/JBIDE-12371
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: SOA Tooling, SwitchYard, target-platform
Affects Versions: 3.3.x
Reporter: Rob Cernich
Assignee: Douglas Palmer
Priority: Critical
SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins.
If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9.
--
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
11 years, 7 months