The dependencies in the parent pom are default scope:
<dependency>
<groupId>org.apache.tiles</groupId>
<artifactId>tiles-jsp</artifactId>
<version>${tiles.version}</version>
</dependency>
Gert-Jan
On Oct 5, 2012, at 4:40 PM, Joakim Erdfelt wrote:
> <build><dependencies> from a parent pom are resolved at the validate phase of
> the maven lifecycle.
> Doing a build hierarchy resolution of dependencies at the validate is
> standard maven.
>
> https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
>
> When a plugin runs, it will perform *another* dependency resolution that
> includes the entire project build hierarchy + plugin itself's downstream
> dependencies + any user configured plugin dependencies from the build
> hierarchy as well (all while taking scope of execution into account).
>
> The jetty jspc maven plugin executes way down at the process-classes phase
> (this is declared in the jetty jspc maven plugin's metadata), the parent pom
> resolution will have occurred already at this point.
> You can always see what the resolution is with the dependency plugin on the
> command line.
>
> $ mvn dependency:tree
>
> This incidentally runs at the validate phase (again, this phase is declared
> in the dependency tree's metadata)
>
> Now, back to your situation, the dependencies that are not being found by the
> jetty jspc maven plugin, were those declared with default scope? or something
> else? (like system scope or provided or runtime?)
>
> --
> Joakim Erdfelt <[email protected]>
> www.webtide.com
> Developer advice, services and support
> from the Jetty & CometD experts.
>
>
>
> On Fri, Oct 5, 2012 at 7:09 AM, Gert-Jan van de Streek <[email protected]>
> wrote:
>
> Turns out that dependencies declared in a parent pom do not get found by
> jspc. Simply repeating them in the pom, or plugin dependencies works around
> that.
>
>
> On Oct 5, 2012, at 3:23 PM, Gert-Jan van de Streek wrote:
>
>>
>> I am using the jetty precompiler from maven as documented at
>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Jspc_Maven_Plugin.
>>
>> The compiled jsp's however contain unresolved tags:
>> <div><tiles:insertAttribute name="body" /></div>
>> The tiles one obviously hurts the most. It resembles what is described in
>> JETTY-1480, but I assume that was correctly merged for Jetty 8.
>>
>> java version "1.6.0_35"
>> jetty version <jetty.version>8.1.7.v20120910</jetty.version>
>> jscp version same as jetty.version
>>
>> Thanks,
>>
>> Gert-Jan van de Streek
>>
>>
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
