dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #00638
Re: pom files
Hi Lars,
________________________________
From: Lars Helge Øverland <larshelge@xxxxxxxxx>
To: Bob Jolliffe <bobjolliffe@xxxxxxxxx>
Cc: Murodullo Latifov <murodlatifov@xxxxxxxxx>; dhis2-devs <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 14, 2009 4:04:32 PM
Subject: Re: [Dhis2-devs] pom files
On Tue, Apr 14, 2009 at 3:41 PM, Bob Jolliffe <bobjolliffe@xxxxxxxxx> wrote:
Hey Murod good to hear from you.
2009/4/14 Murodullo Latifov <murodlatifov@xxxxxxxxx>:
> Hi Bob,
>
> Yes, there changes to be made on poms to make dhis2 as single project. Also there are special requirements/plugins to get project into eclipse. I will write on mailing list soon on how to run/debug modules with WTP (develop as you deploy, maven-eclipse-tomcat), etc., but I need to discuss this with Lars before that. What I have done is on module level, projectwise it needs more work.
> Now I am working on webwork to struts2 migration as well as upgrading hibernate to latest release and use of annotations (JPA and Hibernate). These all should be discussed in mailing list before we take steps, because they are major changes and need surrow revision and testing.
>
> So, lets start on discussing these issues on WHYs, HOWs WHOs and WHENs scopes.
Murod,
- What do you mean by upgrading to the latest Hibernate release? We are already running the latest one in the maven repo, 3.2.6.ga.
- What would be the reason for switching to Hibernate/JPA annotations?
- Why are you working with struts2 migration? Have we decided to switch? Is this something we should prioritize right now as there are lots of pressing requirements, like the list we put down a few weeks ago?
Lars
Yes, we have a list of pressing requirements, one is implementing "easy-access-help" and the other is "datavalue-history". For implementing first one I had small discussion with you, and we decided that I will look shortly if migrating from webwork to struts2 is possible. I managed to migrate one module to run on struts2, it is possible but takes some time and efforts. As all of us know webwork is not updated since mid 2007. "easy access help" was implemented, now I am working on second one. Hibernate has support for auditing persistent objects ("datavalue history"), that is what we want. But it comes with annotations only, so I decided to change hibernate libraries to host annotations, this is the reason. I think using existing functionality is much better than hand crafting history object for datavalue table. Latest Hibernate Core is 3.3.1.GA and Hibernate Annotations is 3.4.0 GA.
Why I said to Bob I am wotrking on this and that is because I have all in my branch and cannot split easily what he wants (poms). I cannot distribute pom with new hibernate dependencies, struts2, etc. That's WHY I said lets discuss these issues before we have made such a change. It is better to discuss how to make these things happen, if they are useful. For hibernate I can say transision is transparent, we can move one object to annotation, while others are still in hbm.xml. For struts2 the same applies to some extend.
regards,
murod.
Follow ups
References