You can no longer deploy a WAR which contains Vaadin 7.2 to JBoss EAP-6.0.0
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by nelsond6
When deploying a WAR that contains Vaadin 7.2 to JBoss, JBoss chokes on the deploy complaining about a logging.properties file being invalid in one of the Vaadin jar files. The logging.properties file which is causing the hang up is in the vaadin-sass-compiler-0.9.2.jar file.
A workaround to this problem is to configure the JBoss system property "org.jboss.as.logging.per-deployment" to false. But this might not be an option for everyone.
I am attaching my JBoss deployment logs.
Imported from https://dev.vaadin.com/ issue #14000
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached JBoss deployment logs and inspecting logging.properties inside vaadin-sass-compiler-0.9.2.jar. Reproduce deployment of a WAR containing Vaadin 7.2 on JBoss EAP-6.0.0; done means it deploys without requiring org.jboss.as.logging.per-deployment to be disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100