> I would like also to say that I personally prefer to rely on > the make files > to pick up my component interfaces and do not see any added value > in separating them in two different packages. Yes, I use a script to extract the various class names from the deployment descriptors and generate makefile dependencies as well. This decouples the package conventions from the build process. - Avi -- This signature intentionally left blank. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
- each ejb having its own package Tinou Bao
- Re: each ejb having its own package Krishnan Subramanian
- Re: each ejb having its own package Tinou Bao
- Re: each ejb having its own package Avi Kivity
- Re: each ejb having its own package Avi Kivity
- Re: each ejb having its own package Ian McCallion
- Re: each ejb having its own package Crothers.Dean
- Re: each ejb having its own package Tinou Bao
- Re: each ejb having its own package Avi Kivity
- Re: each ejb having its own package Lo�c Planchenault
- Re: each ejb having its own package Avi Kivity
- Re: each ejb having its own package Gene Chuang
- Re: each ejb having its own package Cedric Beust
- Re: each ejb having its own package Gene Chuang
- Re: each ejb having its own package Tinou Bao
- Re: each ejb having its own package Gene Chuang
- Re: each ejb having its own package Cedric Beust
