Bug 455864 - target/m2e-wtp/web-resources/WEB-INF does not exist with Eclipse build actions
Summary: target/m2e-wtp/web-resources/WEB-INF does not exist with Eclipse build actions
Status: UNCONFIRMED
Alias: None
Product: M2E-WTP
Classification: Technology
Component: Core (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-20 14:09 EST by Jeff Jensen CLA
Modified: 2014-12-22 13:31 EST (History)
3 users (show)

See Also:


Attachments
sample app modules to use with the recipe (2.40 KB, application/octet-stream)
2014-12-20 14:09 EST, Jeff Jensen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Jensen CLA 2014-12-20 14:09:23 EST
Created attachment 249569 [details]
sample app modules to use with the recipe

The directory and files only exist after a CLI mvn clean build.  It's never recreated with any other clean build actions in Eclipse.

Recipe to see issue with the attached example project:
1. mvn clean install from the parent directory
2. Launch Eclipse Luna
3. Import as existing Maven projects
4. Almost always module-a/target/m2e-wtp/web-resources/WEB-INF does not exist
5. Restart Eclipse
6. module-a/target/m2e-wtp/web-resources/WEB-INF still does not exist
7. mvn clean install from the parent or module directory
8. module-a/target/m2e-wtp/web-resources/WEB-INF/classes finally exists
11. Project -> Clean... -> Clean all projects
12. module-a/target/m2e-wtp/web-resources/WEB-INF does not exist
    The only way to get it back is step 7

I expected module-a/target/m2e-wtp/web-resources/WEB-INF/classes/* to exist with an Eclipse clean build.

Is this a limitation of Eclipse platform or an issue in m2e-wtp?
Comment 1 Fred Bricon CLA 2014-12-22 09:08:48 EST
Looks like generated resources in a given build cycle are not being seen within the same cycle by the resource filtering step.

Easiest workaround is to run Maven Project Update having the "clean" option unchecked.

BTW, every time you clean your projects from CLI, the workspace will go out of sync and  you'll get in trouble.
Comment 2 Fred Bricon CLA 2014-12-22 09:20:19 EST
Works better if you use src/test/resources instead of the build output
Comment 3 Jeff Jensen CLA 2014-12-22 13:31:20 EST
(In reply to Fred Bricon from comment #1)
> Looks like generated resources in a given build cycle are not being seen
> within the same cycle by the resource filtering step.
> 
> Easiest workaround is to run Maven Project Update having the "clean" option
> unchecked.
>
> BTW, every time you clean your projects from CLI, the workspace will go out
> of sync and  you'll get in trouble.

Yes, well aware of that!  CLI clean is not a permanent option due to that.  Thanks for mentioning.


(In reply to Fred Bricon from comment #2)
> Works better if you use src/test/resources instead of the build output

That works *a lot* better!  It's 100% successful so far.  Thanks for tracking that down.