Hi Jeff, As I also stated, is that your approach still needs fixing the current test/build.xml to make sure you don't duplicate code.. The current way it is done, doesn't leave even room open to implement this, unless you like unecessery duplication work ;) So in short, you are going to end with a property somehow anyway.. The rest of my motivations are well expressed already in the earlier thread.
Mvgr, Martin On Wed, 2002-06-12 at 20:20, Brekke, Jeff wrote: > The general idea is you wouldn't want to produce the final jar if the unit > tests are failing. Wouldn't failing unit tests indicate the code is not > working properly? In reality you can proceed to build the site with failing > tests showing up in the report. The default jar target will not complete > though with failing unit tests. It's been brought up previously and I'm -1 > on allowing the user to change this behavior, but would be +0 to adding a > separate target ( ant maven:jar-not-tested ) to build the untested jar > without depending on the unit test target. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
