Laurent ROMEO wrote:
>
> Hi all,
>
> What a lot of messages !
>
> I try to catch the discussion with Markus and Philippe
>
> 1. EXTERNALS JARS : This question is just about packaging. Fundamently, the
> is no problem for me to have externals jars. The problem is to document
> strictly which versions are supported. For example, Ant 1.2 is good but not
> Ant 1.3. More, what's the version of ejb.jar. Be sure the ejb v1.1 spec does
> not suit (MessageDriven*) and the 2.0 is not yet implemented ( expecially the
> locals intefaces ). So, if you consider to let these externals jar there, you
> should document them.
> It's right it's very practical for beginners to have a quick procedure to
> test the products. I've seen many products too complicated to install, that
> were not used.
> Nevertheless, for developpers, this architecture is not so practical when he
> wants to test other packages. For example, il I want to test if JOnAS is
> compliant with the EJB v2.0, I have to copy my jar on the last one ( in
> externals/j2ee ) and rebuild my distribution. It's why I had provided in my
> build.properties so many paths ! It is to allow a more flexible developping
> environment.
> Finally, the solution is simple with Ant. Either you build a 'dist-test'
> distribution with just classes and your own externals jars, or you build a
> 'dist-publ' distribution which a coarser-grained jar.
Don't you think that the work to do today is to be able to do exactly
the
same things we are able to do with make today when we do "make install"?
That's what I want as a JonAS developper.
I agree with you and Markus that we have to discuss the .jar problem:
- must we have only jonas.jar and not one for RMI one for Jeremie?
this is related to the jpp problem
- must we remove the externals .jar off the jonas.jar in order to be
able to
use different versions of these .jar.
I agree with you that we must found a packaging that make easier the
change of such .jar file, but I want to continue to have one version
of them for making easy installation for the new Jonas user
So, for me all this are open issues that must be discussed and we to
take time for it.
You know my position I like incremantal processes, first we replace make
by Ant without changing packaging or anything else, then we try
to solve the jpp problem, then we redefine the packaging.
About the ejb.jar. I would like to know what is the problem you have.
The ejb.jar which is integrated in the jonas.jar was EJB2.0
you can find in it the classes related to message driven bean.
It is possible that there is a new version of these classes
we have to check this.
> 2. For servlet.jar and SecurityCtxInterceptor32.java, thanks to Philippe to
> this additional comments. But it's a bit strange. If you can compile a
> jonas.jar without Tomcat classes, it will never work for Tomcat ?!? So,
> Tomcat has to be installed on the developping environment !!!!
We can change our politic about servlet.jar
> 3. For my '10 minutes' : it is the complete installation time : reading my
> doc, downloading ant, and compile with ant. Just compiling is only 1m49s !!!
>
> 4. I'm completely agree with Markus for the Test classes. Either theses
> classes are important, and have to be compiled, or we have to remove them
> from the CVS tree. Moreover, the errors are very simple to correct !
>
Me too! these tests are here for historical reasons! we have forgotten
to
update them. I think we can remove them or update OK, but I think
it is not a very important problem but we will fix it!
> I think it's all.
>
> Laurent.
--
Philippe
Philippe Coq Evidian Phone: (33) 04 76 29 78 49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
Download our EJBServer at http://www.objectweb.org
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
