I had a look at the
src/java/org/apache/avalon/meta/info/builder/tags/DependencyTag.java
file and found the following code:
/**
* Set the value of the composition method.
*/
private void setMethods()
{
m_methods = getLifecycleMethods( "compose",
COMPONENT_MANAGER_CLASS );
if ( m_methods.length == 0 )
{
m_methods = getLifecycleMethods(
"service", SERVICE_MANAGER_CLASS );
}
}
It seems that only @avalon.dependency tags under
either the compose() method or the service() method
would be processed. Here are my concerns:
1. If an abstract class is used to handle
lifecycle methods for components, the subclass does
not necessary has these two methods, and thus it would
be impossible to declare component dependencies. (of
course empty service() or compose() methods may be
declared, but that's like cutting toes to fit the
shoes).
2. Wouldn't it be better to have the option of
putting the dependency declaration under class level
javadoc, so that all major avalon related tags are
collected together?
3. If it is a must-have requirement to have
@avalon.dependency under these methods only, wouldn't
it be nice to document it somewhere? (Or maybe I have
missed it?)
I have been pulling my hair for a few days because
maven avalon:meta wouldn't generate the xinfo files
correctly due to this setup. I am sure others like me
would face the same problem. We will really
appreciate if this problem can be solved. :) Thanks.
Mandr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
