Hi SB
Firstly, could you always copy all questions to the openoss-devel list -
that way we have a record and others can jump in.
I have several suggestions to try.
Firstly, if you are building 1.1.2 models , have you updated to the latest
tigerstripe version in the JOSIF stream and are you using the latest soap
plugin from xose - he has been fixing bugs related to tigerstripe and the
'TigerstripeProjectHandle.getTSProject' looks like it could be related to
problems he had previously.
1. Have you got the latest 1.1.2 snapshot (trunk) tigerstripe plugins and
profile installed. You need to check these out from trunk and install the in
the workspace directly. You MUST uninstall the 1.1.1 plugins and profile
before installing the 1.1.2-snapshot plugins. Only these generators /
profile will work with trunk code.
1. Having run eclipse:eclipse, try importing the dependency project into
your workspace and running tigerstripe from the workspace UI on the
dependency model and see what happens. When you import the model, does it
have any errors? If the UI code generation works without errors, then the
build should be OK
3. sometimes (I don't know why), tigerstripe forgets about the dependency
jars it needs for a model. These are imported into the workspace and are
referenced from the tigerstripe.xml - but for some reason the tigerstripe
model artefacts show dependencies not satisfied. The quick fix to this is to
open tigerstripe.xml, unselect the dependencies and save the file ( this
will cause errors) then open the file and re-select the dependency models
and save. Tigerstripe is then happy. (there appears to be some sort of
intermittent class loading issues for dependency models). You can then
'team>revert' the tigerstripe.xml file - because you have actually done no
changes and you don't need to commit the latest version.
4. Sometimes this problem occurs if you run tigerstripe in a maven build at
the same time as having eclipse open in the workspace. Close eclipse before
you run the build..
5. Finally, if all else fails, it is sometimes necessary to close eclipse,
remove the .metadata from the project work space and re-create the work
space in eclipse. You don't need to delete and project files - just reimport
them into the new workspace.
Hope this helps
Craig
From: SB Mahapatra [mailto:sbm...@tm...]
Sent: 10 August 2012 08:06
To: Craig Gallen (opennms)
Cc: Sasi Podila (sbp...@gm...)
Subject: SPM and RAM Build failure
Hi Craig,
We are facing problem while executing the below command for RAM and SPM.
1. "mvn -U eclipse:eclipse"
2. "mvn clean install"
The above commands are executed in XXX_BaseProject directory and the error
log is attached. Please suggest any corrective action need to be taken.
Note : The above exercise is being done by taking the latest code from SVN
repository. The workbench installer
"TIP_Workbench_Installer-1.1.1-20120118-standard.jar"
https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA
/Interface/trunk/ - for RAM
Thanks and Regds,
SB
|
