I believe there should be an error that there is a conflicting lifecycle
mapping

On 5 July 2011 13:52, Benjamin Bentmann <[email protected]> wrote:

> Rafał Krzewski wrote:
>
>  When I tried running my application I got the follwing error message:
>> "Specified working directory does not exist or is not a directory:
>> /home/rafal/workspaces/**cyklotron-indigo/cyklotron-**
>> webapp/target/m2e-webby"
>> which is quite correct, because I've blown away the target directory
>> more than a few times while tweaking module packaging. I'd expect to
>> Webby to re-create this directory behind the scenes and not bail out
>> like this.
>>
>
> Yes, that's a sane assumption and this is how Webby generally works.
> Considering that you have also installed/experimented with m2e-wtp, to me
> the question is: Does Webby still run at all on your project? For instance,
> if after a refresh-clean-build cycle on the web project, no
> target/m2e-webby/war directory shows up at all, that would be a clear
> indication that Webby, or at least its build relevant part, has been taken
> out of the game.
>
> By their nature, m2e-webby and m2e-wtp both report to m2e-core that they
> handle the maven-war-plugin. I currently can't tell what exactly is supposed
> to happen if two m2e extensions conflict like this.
>
>
>
>
> Benjamin
> ______________________________**_________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users>
>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to