On Dec 12, 2005 03:39 PM, "Palic, Darko" <darko.palic at gmx.de> wrote:

> > > I'm tried to fix the issue with the hardcoded servlet context as Hans
> > has
> > > already mentioned.
> > > I have already changed the build process via ANT. Anyway I have some
> > > questions:
> > > - why is the build-process done via automake in a Java project?
> > 
> > Because of the openssl stuff which is written in C.
> > 
> > > - Is it possible to migrate the build from automake to ant (I would do
> > it,
> > > if someone supports me in the automake scripts)
> > Never tried this.
> >
> > > - would it outrange, if I already add the needed libs to the package
> > (except
> > > jdbc), so that the build process comes in a consistent version?
> > >
> > Most distributions have packages which are maintained. We would
> > break this concept by distributing external packages.
> 
> Ahh okay, anyway the risk of incompatible libs in the distributions to the
> openxchange build is another part, which also should be considered.
> I would suggest to make it comfortable to the user, that he only has to give
> the path to the jdbc. The other libs are already in the openxchange
> distribution. But, the libs should be configurable for the Linux
> Distribution vendors. This approach would meet both requirements, easy to
> install and the possibility to modify the build for linux distribution
> vendors or skilled Linuxuser.
> 



You mean you want an easy launch packet or a kind of 
installer for several distros ?

Then we should talk about this more detailed.
We spend already disk space for this and nobody 
used it before:

http://www.open-xchange.org/cgi-bin/viewcvs.cgi/?root=Eve+Community+Installer



> > > - are there any plans to migrate the architecture to JSF, or Struts+JSF,
> > or
> > > Tapestry?
> > 
> > Yes, there are thought. The next major version will have a
> > complete different design and we are considering such projects.
> > 
> > > - Is there any architectural overview of the Java code?
> > AFAIK, no.
> 
> Hmm okay, I will give it a try to reverse engineer it with together. Maybe I
> will find the concepts behind the code. Who could give me a bootstrap for
> the architecture?
> 



What we have (maybe you saw this already) is in the OXWiki:

http://www.open-xchange.org/oxwiki/ArchitectureOverview

some more can be found here:

http://www.open-xchange.org/oxwiki/OXInternals




> > >
> > > I would like to do more work, since I have experiences in ANT and
> > > build-automation.
> > 
> > Thats defently good to know.
> > 
> > > I would like to work on the automake, and to transform more to ANT.
> > 
> > Do you think that the openssl stuff can be handled by ant ?
> 
> Maybe, I have to give it a try. Anyway my thoughts are more to migrate the
> build more into ANT (Userinteraction for the libs, which I prefer compared
> to the --anyParam parameters/options in make) 
> 
>
> > 
> > > Could someone of the developer get in contact with me, to discuss
> > further
> > > work?
> > The question is what do we want to achieve and what is the
> > approach. If it will be easier and will not break our other
> > build processes and functionality lets move forward.
> > 
> 
> I hope so, anyway could someone take a look into my patches, and give me a
> feedback? I want be sure, that I am compliant to any development
> rules/guidelines in this project. (Is there any, if so there can I find it?)
> 



The only thing i have mentioned many times is that we have to
take care about our build processes and the overall functionality
which should not break - remember that there is a company which
depends on this build processes.

If you want to provide a kind of installer this opens
some space for discussions and for other directions.
If we have to bend the existing build process we have to take
a deeper look and we must discuss this very deeply. But if we keep
our process intact and only being flexible to integrate other
build processes this is fine. Gentoo for example is one distribution
is already using the current build process and these guys are able to
build OX from the source with their build system ... maybe there
are more and i am not sure how Balint creates his Debian packages ...


One approach could be:

1) make the build process more flexible without bending
 everything, because some existing build systems are already
 in place and nobody want to start again from scratch.

2) write an independent ant build process which is based on (1)
 and help people to install OX with all the ideas one can have,
 like prepared for several distros and all the other stuff 
 you have mentioned.




> I will wait for the first feedback of my patches, after on I will go further
> with my work on the build process.
> 
> I'm using Eclipse as my preferred IDE, Eclipse has a really easy integration
> of CVS/SVN and diff. Is it possible to get a read CVS access (read access is
> enough)? I could do my work and my patches against the HEAD without the need
> to get other peoples into merging my work into the HEAD.
> 



Didn't we discussed this last Friday together ? Not sure, but do you expect
different answers since 2 days ;-) ?



> Regards,
> Darko  
> 



Ciao,

Martin Kauss