|Re: Maven import task not starting with startup trigger [message #1733270 is a reply to message #1733223]
||Thu, 26 May 2016 03:47
| Ed Merks
Registered: July 2009
On 25.05.2016 22:38, Leo Betz wrote:
> Hello Ed,
> I have the same problem.
> The thing is that I have a subversion repo where I want to "Checkout
> as Maven Project" with Oomph.
> Unfortunately there is no SVN checkout task so the only way I found is
> to use a Project Set Import Task to checkout the projects. But after
> that at least the root project is created in workspace and I don't
> know any way to prevent this.
I see. But all the task's isNeeded checks are done before any of them
are performed. So for this task, if the workspace is empty, as is the
case initially when creating a new installation for a Project setup, it
should return true.
> So if I run the Maven Import Task afterwards it always skips because
> of the existing (non-maven) project.
By after, you mean in the same Project setup as the one that contains
Project Set Import task? And that is doesn't perform during the
> Do you see any solution for this problem?
Is this a problem during initial startup?
> Is there a possibility to change the isNeeded() method in a way that
> it only looks on projects with activated Maven nature?
Perhaps, but I'm trying to understand why it's a problem at all. In
particular, why isn't the workspace empty initially when isNeeded is
tested the first time, which is even before the Project Set Import task
Powered by FUDForum
. Page generated in 0.01621 seconds