Menu
▾
▴
[Openoss-devel] Fwd: Re: TIP Build Task updates and regression
|
From: Craig G. (opennms) <cg...@op...> - 2012-06-04 08:47:37
|
Hi, For regression, we need to bring the build scripts of all of the test projects up to the latest level and then build the models and check that everything works OK. I have already done this with RAM, MPAC and PM. To do this we need to use the Project Creator to create a new version of the project with the latest build files and resources and then use these as a template to compare with and update the trunk version of the test project you are updating. First check out the tigerstripe modules you need; Check out and install the latest tigerstripe profile https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Profile/trunk/TIP_Profile_Model Check out and install the latest tigerstripe generators ( remember to remove installed generators first ) https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Doc_Generator/trunk/TIP_Doc_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_EjbImpl_Generator/trunk/TIP_EjbImpl_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_JvtSpec_Generator/trunk/TIP_JvtSpec_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_SoapImpl_Generator/trunk/TIP_SoapImpl_Generator Check out all modules of the latest version of the test project following the process in http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Getting_Started For instance all the TIP_Fmk_Test1 project modules are all in https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ You may want to and do a manual tigerstripe generation of the model and dependency projects from the desktop. Follow the getting started instructions to do a maven build. If this fails, we will need to find out what is wrong with the model relative to the new generators. Regardless of any problems with the generators you should still update the project build files as describe below. We now need to update the project build files 1. obtain the latest snapshot project creator this can be found at http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/openoss/tip/TIP_Project_Creator/1.1.2-SNAPSHOT/ the latest project creator will be contained in a jar named like TIP_Project_Creator-1.1.2-20120604.074637-1-standard.jar where the middle numbers are the date and time of upload. Use the most recent snapshot. 2. create a new empty project in your workspace called something like 'misc' 3. move the project creator jar into this 'misc' folder in widows explorer 4. double click on the project creator jar to start it. 5. Fill in the following details; a) in the first panel replace the name TIP_ArchetypeProject with the name of the project you are updating b) replace the version numbers with the version number of the project you are updating c) open the MODEL tigerstripe.xml and find modelId. place this in the model id line of the first panel d) click through the rest of the panels and create the project in your misc directory you should now have a project with the same naming as the project your are updating. 6. compare and bring up to date each module in your main project a) refresh 'misc' in eclipse to see the project modules. b) for each module in the project you are updating , click to select the module then use 'control click' to select the same module in 'misc'. This should select ONLY the two modules you are comparing. c) right click on one of the modules and select Compare With>eachother d) eclipse should give you a diff between the modules. You then need to update the following in the trunk project - update the project pom.xml to match the misc pom.xml - update any resources / java file which are changed in the misc project - remove any resources / java files or packages from the trunk which don't exist in the new 'misc' project - add any new resources / java files or packages which don't exist in the 'trunk' project 7. New modules may have been added to the misc project created by the project creator which don't exist in the test project. If this is the cases, they need to be added to the /trunk subversion repository and checked out once you have successfully updated the project build , check it in - even if it doesn't completely work. We may have problems with the generators which are causing the build to fail. This is why we do regression tests. Note - very important; a) do not update or change the /src model classes in the MODEL or DEPENCENCIES projects . These are the one thing which carries over between the update b) do not replace or change the .classpath, .project, . properties which exist in your checked out project. These will not exist in the 'misc' modules c) by default the project creator create a BaseProject pom.xml with the java build modules disabled and only builds the specification and doumentation. Get these working first for all of the the projects before trying to get the java modules to work. I hope this is enough to get you going Craig On 31/05/2012 19:02, Pierre Gauthier wrote: > Hi, > > I would like to setup a meeting to discuss Kumar first task. > > Craig can you prepare a quick presentation highlighting what is required from > Kumar precisely ? A simple power point. > > I would like to go over the requirements with you and Kumar to make sure > that we both understand them and fix a schedule for the deliverables. > > > Are you both available tomorrow Morning Eastern Time Canada 10:00 AM ? > > Regards Pierre > > > |
