
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Mac OS X 10.4.8, JSE 6, Maven 2.0.5
|
|
|
- using Appfuse 2.0-m4-SNAPSHOT
- create spring-modular project
- run mvn package on web project
- the hibernate.cfg.xml file from appfuse-web-common is included in the war file at WEB-INF/classes
- follow the tutorial, create a hibernate.cfg.xml in core/src/main/resources
- run mvn package on the web module
- the hibernate.cfg.xml file from appfuse-web-common is included in the war file at WEB-INF/classes which masks the one in the core jar file in WEB-INF/lib
If I'm not mistaken, fixing this behavior in the warpath plugin will break the project when it's first created because the war file won't have a hibernate.cfg.xml file out of the box anymore. The archetype should probably create the project correctly with the starter hibernate.cfg.xml file in core/src/main/resources
|
|
Description
|
- using Appfuse 2.0-m4-SNAPSHOT
- create spring-modular project
- run mvn package on web project
- the hibernate.cfg.xml file from appfuse-web-common is included in the war file at WEB-INF/classes
- follow the tutorial, create a hibernate.cfg.xml in core/src/main/resources
- run mvn package on the web module
- the hibernate.cfg.xml file from appfuse-web-common is included in the war file at WEB-INF/classes which masks the one in the core jar file in WEB-INF/lib
If I'm not mistaken, fixing this behavior in the warpath plugin will break the project when it's first created because the war file won't have a hibernate.cfg.xml file out of the box anymore. The archetype should probably create the project correctly with the starter hibernate.cfg.xml file in core/src/main/resources
|
Show » |
Sort Order:
|