Re: Cocoon Build : deprecated block necessary ?
Not sure what you mean by squeeze the depends clause, but the root problem needs to get fixed. It either means removing the tests for deprecated items, or modifying the build to exclude deprecated tests when deprecated is excluded (which means creating a deprecated test directory somewhere and moving the offending items there) or, moving the deprecated tests to their new home (because IIRC, the items have not been truly deprecated but moved to excalibur??) Patches or specific suggestions will be very welcome. Geoff At 08:31 AM 6/23/2003, you wrote: Hi all, I'm trying to build a mini-clean webapp, but the compile-tests target seems to depend on deprecated stuffs, as said in the comment of the build file. What is the cleanest solution ? Is this target necessary to build the webapp, or not ? Can I squeeze the depends clause of compile target ? Thanks in advance ! -- Olivier Billard Jouve SI - 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]
Re: Cocoon Build : deprecated block necessary ?
Thanks for your answer Geoff ! By squeeze, I thought brutaly delete the compile-tests depends clause in the compile targer, to avoid the problem. As I didn't get deep into this tests, I don't know what could depend on this. But why is compile-tests not optional, as compile-deprecated ? No need for this ? Thanks in advance... Geoff Howard wrote: Not sure what you mean by squeeze the depends clause, but the root problem needs to get fixed. It either means removing the tests for deprecated items, or modifying the build to exclude deprecated tests when deprecated is excluded (which means creating a deprecated test directory somewhere and moving the offending items there) or, moving the deprecated tests to their new home (because IIRC, the items have not been truly deprecated but moved to excalibur??) Patches or specific suggestions will be very welcome. Geoff At 08:31 AM 6/23/2003, you wrote: Hi all, I'm trying to build a mini-clean webapp, but the compile-tests target seems to depend on deprecated stuffs, as said in the comment of the build file. What is the cleanest solution ? Is this target necessary to build the webapp, or not ? Can I squeeze the depends clause of compile target ? Thanks in advance ! -- Olivier Billard Jouve SI - 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]
Re: Cocoon Build : deprecated block necessary ?
Well, I think that compiling and running the tests is not optional because if something is failing a unit test, you'd want to know. However, the present problem is not a real problem but a fake one! My understanding is that it's just a problem of the real package having moved without its tests. If you get a chance to look into where these things should go, let me know. Someone will be looking at it - perhaps even me - eventually. It's going to get more important once beta stage hits real soon now. For now, if you want to hack out the test stuff, it won't cause harm. You could also remove the specific offending tests (I don't even know which ones they are) and leave the depends target alone. Geoff At 09:31 AM 6/23/2003, you wrote: Thanks for your answer Geoff ! By squeeze, I thought brutaly delete the compile-tests depends clause in the compile targer, to avoid the problem. As I didn't get deep into this tests, I don't know what could depend on this. But why is compile-tests not optional, as compile-deprecated ? No need for this ? Thanks in advance... Geoff Howard wrote: Not sure what you mean by squeeze the depends clause, but the root problem needs to get fixed. It either means removing the tests for deprecated items, or modifying the build to exclude deprecated tests when deprecated is excluded (which means creating a deprecated test directory somewhere and moving the offending items there) or, moving the deprecated tests to their new home (because IIRC, the items have not been truly deprecated but moved to excalibur??) Patches or specific suggestions will be very welcome. Geoff At 08:31 AM 6/23/2003, you wrote: Hi all, I'm trying to build a mini-clean webapp, but the compile-tests target seems to depend on deprecated stuffs, as said in the comment of the build file. What is the cleanest solution ? Is this target necessary to build the webapp, or not ? Can I squeeze the depends clause of compile target ? Thanks in advance ! -- Olivier Billard Jouve SI - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Build : deprecated block necessary ?
Ok thanks Geoff I'll let you know if I get into a clean patch. Thanks again ! Geoff Howard wrote: Well, I think that compiling and running the tests is not optional because if something is failing a unit test, you'd want to know. However, the present problem is not a real problem but a fake one! My understanding is that it's just a problem of the real package having moved without its tests. If you get a chance to look into where these things should go, let me know. Someone will be looking at it - perhaps even me - eventually. It's going to get more important once beta stage hits real soon now. For now, if you want to hack out the test stuff, it won't cause harm. You could also remove the specific offending tests (I don't even know which ones they are) and leave the depends target alone. Geoff At 09:31 AM 6/23/2003, you wrote: Thanks for your answer Geoff ! By squeeze, I thought brutaly delete the compile-tests depends clause in the compile targer, to avoid the problem. As I didn't get deep into this tests, I don't know what could depend on this. But why is compile-tests not optional, as compile-deprecated ? No need for this ? Thanks in advance... Geoff Howard wrote: Not sure what you mean by squeeze the depends clause, but the root problem needs to get fixed. It either means removing the tests for deprecated items, or modifying the build to exclude deprecated tests when deprecated is excluded (which means creating a deprecated test directory somewhere and moving the offending items there) or, moving the deprecated tests to their new home (because IIRC, the items have not been truly deprecated but moved to excalibur??) Patches or specific suggestions will be very welcome. Geoff At 08:31 AM 6/23/2003, you wrote: Hi all, I'm trying to build a mini-clean webapp, but the compile-tests target seems to depend on deprecated stuffs, as said in the comment of the build file. What is the cleanest solution ? Is this target necessary to build the webapp, or not ? Can I squeeze the depends clause of compile target ? Thanks in advance ! -- Olivier Billard Jouve SI - 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] - 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]
