Re: Incremental builds with multiple svn locations + non-nested maven modules

[Christoph Kutzinski]

Interesting problem, but I see a problem with the proposed patch as it
changes the way how 'affected paths' are returned in a backwards
incompatible way. SO it could raise other issues at several places.

I propose, you raise this issue on the developer list or on the IRC
channel to maybe get other opinions on how to fix it.

cheers
Christoph

Am 15.06.2011 13:03, schrieb Justin:
> Hi,
>
> This looks like its been raised as https://issues.jenkins-ci.org/browse/JENKINS-9139
>
> I'm not able to log in and vote for this, wondering if it can be
> progressed?
>
> Its pretty easy to replicate, just create a maven job that includes
> all the individual svn locations of a multi-module maven project where
> the sub-projects are beside the parent instead of being nested inside
> it, thus you have to specify<relativePath>../Parent</relativePath>
> inside the<parent> section of the poms of the modules. Set it to
> build incrementally, make a change to a module + checkin, and it will
> build the wrong modules.
>
> Thanks if you can tell me how I can get this included in a subsequent
> release.
>
> Regards,
> Justin

[Justin]

Hi,

Just bumping this, any ideas how I can get it progressed?

Thanks,
Justin

On Jun 19, 8:35 am, Christoph Kutzinski <ku...@gmx.de> wrote:
> Interesting problem, but I see a problem with the proposed patch as it
> changes the way how 'affected paths' are returned in a backwards
> incompatible way. SO it could raise other issues at several places.
>
> I propose, you raise this issue on the developer list or on the IRC
> channel to maybe get other opinions on how to fix it.
>
> cheers
> Christoph
>
> Am 15.06.2011 13:03, schrieb Justin:
>
>
>
>
>
>
>
> > Hi,
>

> > This looks like its been raised ashttps://issues.jenkins-ci.org/browse/JENKINS-9139