Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

\/libs/foundation/global.jsp can't be resolved

Avatar

Level 3

Hi, 

I created a new project based on the sample-project-archetype: 7 using the new AEM Eclipse plugin.

I also added the maven-jspc-plugin in order to compile JSPs during the Maven build. 

But when running the build, the plugin errors out with:

"Failed to execute goal org.apache.sling:maven-jspc-plugin:2.0.8:jspc (compile-jsp) on project aemdemo.ui.apps: file:./aemdemo/aemdemo/ui.apps/target/jsps-to-compile/apps/aemdemo/components/content/example.jsp(11,0) File "/libs/foundation/global.jsp" not found"

What am I missing? Is there way to exclude the include during compilation?

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Employee

You can copy the global.jsp in your project in /libs/components, and then not include it via the filter.xml.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

You can copy the global.jsp in your project in /libs/components, and then not include it via the filter.xml.

Avatar

Level 3

Thanks. I put the global.jsp in my project under apps/foundation. Eclipse is still not happy with the include but the maven JspC plugin compiles :)