I think the differentiation between runtime and compile-time is
too one dimensional in the first place.
For example what is unit testing? It's not compiletime but it's not runtime either.
How about xdoclet stuff, that pre compiletime, the same with aspectj.
Those jars aren't needed for runtime at all!
What about text processing, or transformation of a generated docuemtent from
format x into format y. That's postcompile but not runtime.


Henri Yandell wrote:

Is there any time when a dependency is compile-time but not runtime? It
seems to me that all dependencies are needed at runtime.

On Sun, 23 Mar 2003, Paulo Silveira wrote:



I think it is not good to have so specific plugin tags inside the POM,
dont you think?

The good example is <war.bundle.jar>true</war.bundle.jar>
Why we couldnt have a tag that specifies if a dependecy is only runtime,
compiletime, or both? Maybe 2 tags

<dependency>
   <id>jarid</id>
   <version>jarversion</version>
   <compiletimedependency/>
   <runtimedependency/>
</dependency>

thanks

------------------------
Paulo Silveira
http://www.paulo.com.br/
http://www.guj.com.br/




--------------------------------------------------------------------- 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]



Reply via email to