On Fri, Jan 29, 2010 at 12:31:06PM +0100, Christoph Kutzinski wrote:
> Why do you want to do this? Why not just fix the compile errors?
Likely the same reason that compiler writers have spent so much time
studying error recovery in parsers: to discover as many errors as
possible in one iteration.
Eduardo-
AFAIK, the behavior you are seeing is the behavior of javac, not Maven. As
you note, the Eclipse compiler does something different, so if that's the
behavior you want, use the Eclipse compiler.
Justin
On Fri, Jan 29, 2010 at 8:21 AM, Eduardo M KALINOWSKI <
edua...@kalinowski.com.br> wrot
2010/1/29 Eduardo M KALINOWSKI :
> For example, a method name may be
> changed. This will break everywhere that calls the method.
Refactoring anyone? Or deprecations?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
F
On Sex, 29 Jan 2010, Christoph Kutzinski wrote:
Sounds to me like you should modularize the application, make a
multi-module project of it (if not already) and then add only those
modules on which you're working currently to the section
of the parent POM and leave out all the others for the
Sounds to me like you should modularize the application, make a
multi-module project of it (if not already) and then add only those
modules on which you're working currently to the section of
the parent POM and leave out all the others for the moment.
Just a quick idea from the top of my head.
On Sex, 29 Jan 2010, Christoph Kutzinski wrote:
The obvious counter question is:
Why do you want to do this? Why not just fix the compile errors?
To make a long story short: we received this project from another
company, and we have to fix it and complete the parts that are missing.
We are
2010/1/29 Eduardo M KALINOWSKI :
> One possible way to solve the problem would be to manually list the files to
> be excluded, and remove them from the list as they get fixed. But this is
> tedious and error-prone, so I wonder if there is a better way.
Sure, complain with your team. Having a proje
Hi Eduardo,
a solution would be
+) create a project in the IDE of your choice
+) fix the errors incrementally
Cheers,
Siegfried Goeschl
Eduardo M KALINOWSKI wrote:
> Is there a way to configure Maven to ignore source files that present
> errors during compilation, and compile everything that i
The obvious counter question is:
Why do you want to do this? Why not just fix the compile errors?
Eduardo M KALINOWSKI schrieb:
Is there a way to configure Maven to ignore source files that present
errors during compilation, and compile everything that is possible (that
is, has no error)?
I'v
Is there a way to configure Maven to ignore source files that present
errors during compilation, and compile everything that is possible
(that is, has no error)?
I've set maven-compiler-plugin's failOnError option to "false", and
the build is considered successful despite the errors. Howeve
10 matches
Mail list logo
