I've made some progress, see below:
Dietrich Schulten schrieb:
> Hi Fabrizio,
>
> thank you for your quick reply. Comments inline.
>
> Fabrizio Giustina schrieb:
>
>>On 10/18/05, Dietrich Schulten <[EMAIL PROTECTED]> wrote:
>>
>>
>>>how does the m2 eclipse plugin determine the path where it looks for web
>>>app libraries when used for dynamic web projects?
I added an additional deploy-path to the .classpath and Eclipse copies
the WEB-INF/lib jars from target/WEB-INF/lib to .deployables:
<wb-resource deploy-path="/WEB-INF/lib"
source-path="/target/my-webapp/WEB-INF/lib"/>
This seems to be exactly what is desirable:
Eclipse uses target/WEB-INF/lib for .deployables/WEB-INF/lib, and builds
src/main/java to .deployables/WEB-INF/classes.
One problem remains: You must make sure that Maven does not provide
project dependencies in target.
Do you agree that this would be a good solution? If so, I could try to
provide a patch for the plugin.
> I assumed, some magic might replace the artifactId for artifact. M2
> newbie question: Is it possible to refer to the artifactId, as if it
> were a variable, in the pom.xml?
${artifactId} does it
Regards
Dietrich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
