]
Andre Dietisheim commented on JBIDE-18397:
------------------------------------------
[~maxandersen] shouldnt new create an empty openshift profile? OpenShift will always try
to execute this profile, so imho having an empty stub is better than having nothing.
Furthermore shouldnt we inform the user that we could determine the output directory for
the war plugin?
Application wizard: openshift maven profile for WildFly cartridge
generates <outputDirectory>null</outputDirectory>
-------------------------------------------------------------------------------------------------------------------
Key: JBIDE-18397
URL:
https://issues.jboss.org/browse/JBIDE-18397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.CR1
Reporter: Fred Bricon
Assignee: Andre Dietisheim
Priority: Critical
Labels: application_wizard
Fix For: 4.2.0.CR2, 4.3.x
- Create a new maven war project testapp
- Add custom index.html
- Create new openshift application with WildFly 8.1 quickstart
- deploy testapp on openshift
- ASSERT your changes are published online
-> FAIL the default Wildfly 8 cartridge app is shown
This is caused by openshift tooling generating an invalid outputDirectory value (null)
instead of the expected one (deployments)
{noformat}<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>testapp</finalName>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.4</version>
<configuration>
<outputDirectory>null</outputDirectory>
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
{noformat}