pro-spring-mvc-after.zip
pro-spring-mvc-before.zip
[GRADLE-2409] Incorrect Deployment Assembly with project dependencies Created: 31/Jul/12 Updated: 25/Jan/17 Resolved: 03/Jun/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 3.0-milestone-1, 3.0-rc-2 |
| Type: | Bug | ||
| Reporter: | Marten Deinum | Assignee: | Donát Csikós |
| Resolution: | Fixed | Votes: | 1 |
| Attachments: |
pro-spring-mvc-after.zip
pro-spring-mvc-before.zip
|
| Description |
|
When using the eclipse plugin (gradle cleanEclipse eclipse) the generated files aren't correct at least the Deployment Assembly is broken. It appears that in the shared projects the files 'org.eclipse.wst.common.component' and 'rg.eclipse.wst.common.project.facet.core.xml' are either missing or incorrectly generated. Next to that in the .classpath file of the web project it appears to be creating a wrong classpathentry [code] instead of the following. [code] We used Gradle for the sample project for our book (Pro Spring MVC) but although it works flawlessly from the command line using the IDE integration is a bit of a pain (at least the Eclipse integration). |
| Comments |
| Comment by Szczepan Faber [ 31/Jul/12 ] |
|
Can you submit a small project that demonstrates the issue? |
| Comment by Marten Deinum [ 01/Aug/12 ] |
|
I don't have a small project however the source code shipped with Pro Spring MVC: with Web Flow shows this issue. The project(s) can be found on https://github.com/mdeinum/pro-spring-mvc-code. We tried to fix it by patching the generated artifacts ourselves but this only partially solves the problem. |
| Comment by Marten Deinum [ 01/Aug/12 ] |
|
Here are the eclipse files before and after fixing it manually (as described here http://mdeinum.wordpress.com/2012/07/30/pro-spring-mvc-with-web-flow-sample-application-fails-to-start/). |
| Comment by Donát Csikós [ 01/Jun/16 ] |
|
The classpath attribute problem is fixed in the codebase and can be tested by using the latest snapshot. |