t; From: Igor Fedorenko
> To: dev@maven.apache.org
> Cc:
> Sent: Friday, September 7, 2012 11:44 PM
> Subject: Re: [incremental build] Detect leftovers from a previous build
>
>
>
> On 12-09-07 2:37 AM, Mark Struberg wrote:
>>> I may be missing something, but if a
. sources
and external dependencies, contributed to each generated .class to
guarantee correct output.
--
Regards,
Igor
LieGrue, strub >
- Original Message -
From: Igor Fedorenko
To: dev@maven.apache.org
Cc:
Sent: Friday, September 7, 2012 4:14 AM
Subject: Re: [incremental build] Det
nothing to be on the safe side.
>
> LieGrue,
> strub
>
>
>
>
> - Original Message -
> > From: Romain Manni-Bucau
> > To: Mark Struberg ; Maven Developers List <
> dev@maven.apache.org>
> > Cc:
> > Sent: Friday, September 7, 2012 8:48 AM
> &
t; To: Mark Struberg ; Maven Developers List
>
> Cc:
> Sent: Friday, September 7, 2012 8:48 AM
> Subject: Re: [incremental build] Detect leftovers from a previous build
>
> How? If i change a class in main/java but the test is done by reflection
> youll miss it
> Le 7 s
cau
> >To: Mark Struberg ; Maven Developers List <
> dev@maven.apache.org>
> >Sent: Friday, September 7, 2012 8:41 AM
> >Subject: Re: [incremental build] Detect leftovers from a previous build
> >
> >
> >You cant do it dor surefire. Tests are sometimes don
rue,
strub
>
> From: Romain Manni-Bucau
>To: Mark Struberg ; Maven Developers List
>
>Sent: Friday, September 7, 2012 8:41 AM
>Subject: Re: [incremental build] Detect leftovers from a previous build
>
>
>You cant do it dor surefire. T
t; Subject: Re: [incremental build] Detect leftovers from a previous build
>
> How will this help if I delete an old file, one that simply hasnt been
> changed? Also, won't the list just grow infinitely ?
>
> re executions; search for "a tribute to Linus Torvalds" in the
>
From: Igor Fedorenko
> > To: dev@maven.apache.org
> > Cc:
> > Sent: Friday, September 7, 2012 4:14 AM
> > Subject: Re: [incremental build] Detect leftovers from a previous build
> >
> > I may be missing something, but if all plugins implement this logic,
> > h
Igor Fedorenko
> To: dev@maven.apache.org
> Cc:
> Sent: Friday, September 7, 2012 4:14 AM
> Subject: Re: [incremental build] Detect leftovers from a previous build
>
> I may be missing something, but if all plugins implement this logic,
> how it will be different from implicit
How will this help if I delete an old file, one that simply hasnt been
changed? Also, won't the list just grow infinitely ?
re executions; search for "a tribute to Linus Torvalds" in the
surefire source to find a really neat workaround that solves several
of your other problems..
Kristian
Den 6.
I may be missing something, but if all plugins implement this logic,
how it will be different from implicitly doing "clean" during each
build? Or, put differently, are there plugins that do not need to clean
their previous output to be absolutely sure they properly handle
incremental rebuilds?
--
Answers inside.
LieGrue,
strub
- Original Message -
> From: Anders Hammar
> To: Maven Developers List ; Mark Struberg
>
> Cc:
> Sent: Thursday, September 6, 2012 9:51 PM
> Subject: Re: [incremental build] Detect leftovers from a previous build
>
> Wha
in sources + dependencies for that module) - and that is
actually the most expensive part of a build.
LieGrue,
strub
- Original Message -
> From: Vincent Latombe
> To: Maven Developers List
> Cc:
> Sent: Thursday, September 6, 2012 9:37 PM
> Subject: Re: [increm
What you talk about here is something that BuildContext should
provide, if we stay with that. There's a scanner for changes and a
deleteScanner.
The really tricky thing is when one source file has more than one
output/target file (like inner classes). The plugin needs some way of
knowing what targe
t step (aka
> > B.).
> >
> > LieGrue,
> > strub
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Incremental+Builds
> >
> >
> > >____
> > > From: Romain Manni-Bucau
> > >
first step (aka
> B.).
>
> LieGrue,
> strub
>
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Incremental+Builds
>
>
> >
> > From: Romain Manni-Bucau
> >To: Mark Struberg ; Maven Developers List <
> dev@maven
; Maven Developers List
>
>Sent: Thursday, September 6, 2012 8:59 PM
>Subject: Re: [incremental build] Detect leftovers from a previous build
>
>
>What about browsing the build tree to detect the dep modules which needs to be
>built (avoid a real clean which can cost reall
What about browsing the build tree to detect the dep modules which needs to
be built (avoid a real clean which can cost really too much to make incr
feature useful)? Can be done in parallel and can be pretty fast
Le 6 sept. 2012 20:53, "Mark Struberg" a écrit :
>
>
> Hi!
>
> I had some idea for d
Hi!
I had some idea for detecting stale changes in maven which is pretty generic
The problem hits us if you compile BeanA and BeanA2 in a project where BeanA2
is using BeanA.
On a
$> mvn clean compile
you will get both BeanA.class and BeanA2.class in target/classes
Now delete BeanA.java
Cu
19 matches
Mail list logo
