Re: [Openoss-devel] Tagging 1.1.2 now complete

[Craig G. (opennms) <cg...@op...>]

Hi,

Just tested work bench installer. Overall it appears to work OK but i 
did find a few problems and changes to address. See below.

Issues and changes found;
1. Sample project needs to be replaced with one created using the 
released project creator (i.e.1.1.2 not 1.1.2-SNAPSHOT).  Currently the 
sample project does not build and has Errors such as ReleaseNotes not 
found. This will be fixed with the correct project creator. Get this 
from 
https://sourceforge.net/projects/openoss/files/JOSIF/Platform/1.1.2/JOSIF%20Project%20Creator/ 


2. The tigerstripe-build.properties in the sample project needs to have 
variables which are modified to match the location of the installed 
eclipse and the location of the workspace - both of which can be 
modified during the install process. At a minimum if you can't get the 
installer to change the tigerstripe-build.properties file to match the 
settings, these should match the default locations used by the 
installer. (Currently they are set to D:\\. which is completely wrong)

3. Both the test dependencies and test model projects have no src 
folder. This causes the project import to fail in eclipse. This is not 
the case with the projects built using the project creator. I suggest 
you delete the current TIP_Test project and use the project creator to 
create a new TIP_Test project in the ws-ts-sample workspace and use this 
in the installer

4. remove the following files from the top level of the ws-ts-sample 
workspace - they are created by the project Creator but should not be 
included  in the sample project.
uninstaller (directory)Folding
.installationinformation
readme.txt
ReleaseNotes.txt

5. in the sample workspace please set the following Preferences as 
defaults ( this matches the Apache best practice); (Also set in default 
workspace if no sample project created)
Ant>Editor>Folding> UNCHECK 'enable folding'
Ant>editor>Formatter>indentation Tab size change from 4 to 2 and UNCHECK 
use tab characters instead of spaces. Set maximum line width to 160 
characters
XML>XML Editor. Set Line width to 160 characters. CHECK indent using 
spaces. Set indentation size to 2
General>Editors>Text Editors CHECK show line numbers

Other than that, the installer seems to work OK. Well done

Craig








On 01/10/2012 13:49, Flauw, Marc wrote:
> Tina,
>
> Kumar has published, through SB,  an installer for team review.
> I had only time today to validate the generators and SID import have same signatures as the ones I am currently using.
> I would be glad if it can be tested also by others as my availability for testing will be limited this week.
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Tina O Sullivan [mailto:tos...@tm...]
> Sent: Monday, October 01, 2012 2:42 PM
> To: Craig Gallen (opennms); Flauw, Marc; Pierre Gauthier; SB Mahapatra; Manikumar Reddy <ku...@nm...> (ku...@nm...)
> Subject: RE: Tagging 1.1.2 now complete
>
> Is it my understanding that Kumar with assistance from SB and crew will start the workbench installer element of this release?
>
> If this is correct,  Kumar are you comfortable to proceed?
>
> Many thanks,
> Tina.
>
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
> Sent: 30 September 2012 19:48
> To: openoss-devel; Marc Flauw; Tina O Sullivan; Pierre Gauthier; Craig Gallen (OpenNMS)
> Subject: Tagging 1.1.2 now complete
>
> Hi,
>
> I have just completed tagging the JOSIF 1.1.2 release and deployed the JOSIF  1.1.2 artefacts to maven.
>
> These are also available as zip files  in the Sourceforge files release system. https://sourceforge.net/projects/openoss/files/JOSIF/
> All that is needed is for the Workbench installer to be completed for the release to be complete.
>
> Release Tagging:
> If you look in the repository, all of Framework and Platform artefacts are numbered release 1.1.2 and moved to the RELEASE_1_1_2 tag The RAM, PM and MPAC projects have also been tagged as releases at their respective point numbers. They use the 1.1.2 Framework and Platform artefacts.
>
> Interface Tagging
> MPAC release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/MaintenanceProtectionAlarmControl/IA/InterfaceModel/tags/RELEASE_1_0_2/
>
> PM_Mon release 1.0.0 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/PerformanceManagement/IA/InterfaceModel_Collection/tags/RELEASE_1_0_0/TIP_PM_Mon_BaseProject
>
> RAM release 1.0.2 using JOSIF release 1.1.2 can be checked out from https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject
>
> Trunk Project Updating:
> The trunk Framework and Platform artefacts artefacts have all  been updated to 1.1.3-SNAPSHOT ready for the next sprint
>
> The trunk versions of the RAM, PM and MPAC projects have been updated to the next point snapshot. (I will also be updating the test project but some work is going on on these projects at present).
>
> You should perform a subversion update on the trunk projects in your workspace and then do a mvn clean install mvn eclipse:clean mvn eclipse:eclipse on each base project  in order to update the dependency versions
>
> Let me know how you get on
>
> Craig
>
>