Re: typedef onerror default

2005-09-03 Thread Steve Loughran
Jose Alberto Fernandez wrote: Steve Loughran wrote: Why is the onerror default of typedef "fail" and not "failall"? The effect is that a typedef like this will warn but not fail if the property file is missing. Surely a missing declaration file is important enough that the default sho

RE: typedef onerror default

2005-08-31 Thread Jose Alberto Fernandez
> Steve Loughran wrote: > > > Why is the onerror default of typedef "fail" and not "failall"? > > > > The effect is that a typedef like this > > > uri="antlib:com.puppycrawl.checkstyle" > > /> > > > > will warn but not fail if the property file is missing. Surely a > > missi

Re: typedef onerror default

2005-08-31 Thread Peter Reilly
Steve Loughran wrote: Why is the onerror default of typedef "fail" and not "failall"? It was for BC reasons. i.e. this is the behaviour for 1.5 when resource was used. Peter The effect is that a typedef like this will warn but not fail if the property file is missing. Surely a missi

typedef onerror default

2005-08-18 Thread Steve Loughran
Why is the onerror default of typedef "fail" and not "failall"? The effect is that a typedef like this will warn but not fail if the property file is missing. Surely a missing declaration file is important enough that the default should be "fail the build right now". proposal -we chang