From: Sascha H. <sa...@xm...> - 2011-04-29 16:52:08
|
On Fri, Apr 29, 2011 at 6:39 PM, hka...@go... < hka...@go...> wrote: > Hello list, > > Sorry I've been away on business. > > First of all many thanks for the quick reply and also the effort in finding > the issue! > Here my answers and questions go... > > @Arno: the ant clean and the manual delete of xmlvm/.cache didn't change > anything. > > I am not sure why this is happening. The error basically tells me that a > loaded resources is null. I could get rid of the error message, but I think > there is another issue here. Can you pleaserun xmlvm using "--debug=all" and > send me the complete log? There might be a pointer earlier in the log that > might give more insight into what is going wrong here. This simple example > should certainly work. > > The bugs seems to be hunted, do you need the logs anyway? > What do you mean by the bugs are hunted? Is your error gone? If not, please send me the log so I can take a look. Thanks. > > > I was able to reproduce this problem and we will take a look at it. Thanks > for finding! > > > Okay thanks! Is there any workaround available or maybe the patch/fix > itself? > We will most probably remove target=c. > > >> Can you imaging, that is really frustrating trying something and the >> simpliest things aren't running? >> >> Please provide simple examples AND a running launch config. I think this >> would do a easy kick start for users like me. >> And I can tell you I have mulitple years of experience in programming. >> But I have not the time to struggle around to get the simpliest things - >> from user view point - running. Currently I am evaluating, if xmlvm >> could be a possible "invest" for my team. But in that project state of >> xmlvm... >> >> Maybe it is a missing documentation, maybe it is the missing simple >> example or maybe both. But I am sure, if you just invest 30 min of your >> current effort in the place to get new users started, new users wouldn't >> turn around and giving up so fast. >> >> So hopefully the developers of this list would here my crying and try to >> fix the issues. >> And maybe you should freeze a running version by tagging/branching or >> providing a zip/tag.gz for the users. >> >> best regards, >> Hans >> > Have you considered to freeze a stable state, so users could use a > running version without the newest - maybe buggy - features? > We have. However at the moment XMLVM can still be considered "early" in some cases, which is why our current model is to make sure the trunk is stable in general. Bigger developments that need testing are done in branches first. So trunk should always be as stable as it gets. We will probably move to versions at some point when functionality is more complete. > Additionally, have you considered to provide run-targets to execute some > very simple examples? > I agree that we should provide more exmaples, especially on our documentation page. Thanks for your feedback! // Sascha |