Easy solution: Stop writing code that doesn't compile. ;-)
Hehe Yes that was my other thought. Ben On 5/30/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Easy solution: Stop writing code that doesn't compile. ;-) How in the world did you manage to get in this situation, with multiple files that just don't compile for some reason or another at any given time in a project? Wayne On 5/30/06, RobJac <[EMAIL PROTECTED]> wrote: > > i have checked it out, the exclude parameter tries to remove that file from > the build and thus avoid compiling that file. This leads to more > maintainance of the pom xml since i need to keep adding files to the pom xml > which are not compilable and then remove it once it becomes compilable. > -- > View this message in context: http://www.nabble.com/Bypass+compliation+error-t1705845.html#a4631357 > Sent from the Maven - Users forum at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
