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 implicitly doing clean during each
build? Or, put differently
be sufficient.
I'd at least try to get rid of unnecessary surefire executions.
LieGrue,
strub
- Original Message -
From: Igor Fedorenko i...@ifedorenko.com
To: dev@maven.apache.org
Cc:
Sent: Friday, September 7, 2012 4:14 AM
Subject: Re: [incremental build] Detect leftovers from
: [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
surefire source to find a really neat
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de; 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
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 done by reflection and
you cant ask a dep tree by test.in real world.
Le 7 sept. 2012 08:37, Mark
...@gmail.com
To: Mark Struberg strub...@yahoo.de; Maven Developers List
dev@maven.apache.org
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
Struberg strub...@yahoo.de; 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 done by reflection
and
you cant ask a dep
, contributed to each generated .class to
guarantee correct output.
--
Regards,
Igor
LieGrue, strub
- Original Message -
From: Igor Fedorenko i...@ifedorenko.com
To: dev@maven.apache.org
Cc:
Sent: Friday, September 7, 2012 4:14 AM
Subject: Re: [incremental build] Detect leftovers from
...@ifedorenko.com
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 all plugins implement this
logic, how it will be different
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 strub...@yahoo.de a écrit :
Hi!
I had some
strub...@yahoo.de; Maven Developers List
dev@maven.apache.org
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
] 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 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
/Incremental+Builds
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de; Maven Developers List
dev@maven.apache.org
Sent: Thursday, September 6, 2012 8:59 PM
Subject: Re: [incremental build] Detect leftovers from a previous build
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
: 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 really too much to make
incr
feature useful)? Can
Answers inside.
LieGrue,
strub
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Thursday, September 6, 2012 9:51 PM
Subject: Re: [incremental build] Detect leftovers from
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?
--
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.
18 matches
Mail list logo
