-
Bug
-
Resolution: Done
-
Critical
-
4.2.0.CR1
-
Workaround Exists
-
- 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)
<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-environments.html --> <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>
- is cloned by
-
JBIDE-18418 Application wizard: openshift maven profile for WildFly cartridge generates <outputDirectory>null</outputDirectory>
- Closed