getNodeObjectSourceRef build error
I am posting here on the off chance I am wrong and this is not a build environment error.
I have been trying to run a full build of the 1.8Dev branch and it runs fine until it reaches the openvpms-web component specifically the openvpms-web-workspaces .....
At which point the build fails with
Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project openvpms-web-workspaces: Compilation failure
org/openvpms/web/workspace/patient/history/PatientHistoryFilter.java:[118,42] error: cannot find symbol
-> [Help 1]
For some bizarre reason the changes to the Framework where the getNodeObjectSourceRef method was added to ImObjectBean which is present in my framework is not being inherited to the subclass ActBean.
I am assuming it some sort of build issue on my system. So far I have deleted my entire maven repo, and rebuilt the lot with a new priming build and built it on a second system (both run nbeans) and still get the same compile error.
I am going to post on Stack and see if I can get some sort of fix.
Re: getNodeObjectSourceRef build error
Make sure you don't have multiple versions of the openvpms-framework jar in your classpath.
Re: getNodeObjectSourceRef build error
The maven repo will have multiple versions but each would be prefixed with the various versions.
aside from that mvn clean will remove previously generated jars.
I will add that netbeans reports this error in the GUi well before I try and compile.
are you referring to the classpath that is used to run netbeans?
Re: getNodeObjectSourceRef build error
Yes. If you can build openvpms-web using mvn from the command line then its a netbeans issue. You may need to clear netbeans' cache: http://wiki.netbeans.org/FaqWhatIsUserdir
Re: getNodeObjectSourceRef build error
Unfortunately compiling using mvn at the command line failed as well..same exact error....
Re: getNodeObjectSourceRef build error
IMObjectBean.getNodeSourceObjectRef(..) was added in revision 5923 on 13/5 on the 1.8-dev branch. The other recent change to framework was in revision 5930, to make RemoteLookup public for org.openvpms.web.component.im.lookup.LookupPropertyEditorFactory
If the latter doesn't given you an error then I'm not sure what the problem is.
Re: getNodeObjectSourceRef build error
Its wierd as I said
I took a look at the compiled code in the local maven repo opening
C:\Users\benjamincharlton\.m2\repository\org\openvpms\openvpms-framework\1.8-SNAPSHOT
IMObjectBean.class
has getNodeSourceObjectRef present...also the sources.jar has the correct sources.
so the maven install on the framework works fine......its the web-workspace that just wont see the new method.
Re: getNodeObjectSourceRef build error
The remotelookup is erroring as well.
of course the error there is that remoteLookup cannot be access outside the package.
*** numerous swear words from me***
Re: getNodeObjectSourceRef build error
Well I found the issue...I am really going to have to just rebuild my versioning system...git-svn sucks.
it cant pull remote tags and branchs from more than 1 svn module at a time and merge it. hence I need 7 git repos....
Somehow git merged a branch of the framework into archetypes...
hence archetypes had an entire copy of the framework in it.. I have no idea how that even happens
Tomorrow I will roll it all back and walk back through the merges..
Stupid git
I wonder if I can just layer the versioning on top one big git project and then use svn to drag in the updates...to each the main branch and commit them all back to git.
I would lose the ability to see your commits like i can currently on github...
(I am still hopefully that eventually you will move to github and I can just fork :P)
Re: getNodeObjectSourceRef build error
We will move the svn repository to github eventually, but keep JIRA at openvpms.org.