WTP and M2 Plugin.

[Alexander Vaysberg <wo...@vaisberg.de>]

Hi,

i have a problem with WTP and M2 Plugin. The problem is in file:- 
.settings/org.eclipse.wst.common.component. If you I use the project 
(web-project) without "Resolve dependencies from Workspace ..." it's 
work fine, but if i use the project with  "Resolve dependencies from 
Workspace ..." then i have a problem with jars for dependent projects 
which was created from maven or eclipse.
This is a context of the file:<
<?xml version="1.0" encoding="UTF-8"?>
    <project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="test-core">
    <wb-resource deploy-path="/" source-path="/src/main/java"/>
    <wb-resource deploy-path="/" source-path="/src/test/java"/>
    <wb-resource deploy-path="/" source-path="/src/test/resources"/>
</wb-module>
</project-modules>
The jar created from this file. In this case added the plugin test data 
in jars. The correct was the this data:-
    <wb-resource deploy-path="/" source-path="/src/test/java"/>
    <wb-resource deploy-path="/" source-path="/src/test/resources"/>
ignore. This only for test. But it was in jars added. Why?

Alexander Vaysberg




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: WTP and M2 Plugin.

[Kiss Tibor <ki...@gmail.com>]

Hi,
With similar issues I fought in july.
Unfortunately Eclipse does not have individual classpath for just testing,
therefore if the .classpath file has the test directories on sources, also
WTP will put in .settings/org.eclipse.wst.common.component too. and when the
dependencies are resolved from Workspace, the jar is created accordingly,
that's why you see tests in newly created jar.

Since WTP often writes in org.eclipse.wst.common.component, I cannot figure
out if m2eclipse can take over the control of this file. Therefore manually
I remove those tests web-resource lines. Until you don't update m2eclipse
project configuration or add new source directories, you don't have problem
with tests. At least our guys still using m2eclipse and I never heard
complains about this problems.

I know that this is just a workaround, but seems to work effectively.

Regards
Tibor



On Fri, Sep 11, 2009 at 3:00 PM, Alexander Vaysberg <wo...@vaisberg.de>wrote:

> Hi,
>
> i have a problem with WTP and M2 Plugin. The problem is in file:-
> .settings/org.eclipse.wst.common.component. If you I use the project
> (web-project) without "Resolve dependencies from Workspace ..." it's work
> fine, but if i use the project with  "Resolve dependencies from Workspace
> ..." then i have a problem with jars for dependent projects which was
> created from maven or eclipse.
> This is a context of the file:<
> <?xml version="1.0" encoding="UTF-8"?>
>   <project-modules id="moduleCoreId" project-version="1.5.0">
>   <wb-module deploy-name="test-core">
>   <wb-resource deploy-path="/" source-path="/src/main/java"/>
>   <wb-resource deploy-path="/" source-path="/src/test/java"/>
>   <wb-resource deploy-path="/" source-path="/src/test/resources"/>
> </wb-module>
> </project-modules>
> The jar created from this file. In this case added the plugin test data in
> jars. The correct was the this data:-
>   <wb-resource deploy-path="/" source-path="/src/test/java"/>
>   <wb-resource deploy-path="/" source-path="/src/test/resources"/>
> ignore. This only for test. But it was in jars added. Why?
>
> Alexander Vaysberg
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>