|
|
|
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 Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
Leo,
Comments below.
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
first/initial startup?
> 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
is performed.
>
> Regards
> Leo
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Re: Maven import task not starting with startup trigger [message #1733775 is a reply to message #1733769] |
Tue, 31 May 2016 15:57 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
Leo,
But the Maven import task itself does things like create the .project
file, so I'm not sure that makes sense in such a case. And of course
without specialized SVN integration, we can't replicate this "Check out
action"...
On 31.05.2016 16:48, Leo Betz wrote:
> Hello Ed,
>
> ok I see. So my problem is different:
> The Maven Import Task is running.
> But it skips projects that already exist in the workspace.
> Of course, at least the root project exists after the project set
> import task. And so no maven nature is configured for that project.
> What I need is a way to have the same final result as if I choose
> "Check out as Maven Project..." in SVN perspective.
>
> Leo
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02926 seconds