17 Feb
2012
17 Feb
'12
4:45 p.m.
For information, we successfully corrected this bug in this specific case.
But it might not be always possible to have it always true (meaning the bug
can reappear somewhere else)
The problem is one must think of verveineJ as a compiler, if one does not
provide the accessed libraries, it misses information necessary to create
correctly entities.
This may result in verveineJ sometimes creating a Type when it should create a
Class. Latter on, when the type is used somewhere else, we might require it to
be a class and the bug would reappear.
In the general case, I don't think it is possible to avoid these bugs in all
cases, so it is better to always give the needed libraries when using
verveineJ.
nicolas
On Thursday 16 February 2012 09:53:41 Nicolas Anquetil wrote:
thanks
we will have a look at it.
thank you for reporting the issue and helping us to improve the tool
nicolas
On Wednesday 15 February 2012 09:25:22 Holger Hans Peter Freyther wrote:
> On 02/15/2012 07:25 AM, Tudor Girba wrote:
> > Hi,
> >
> > Can you provide the scenario so that we can try to reproduce?
>
> Yeah, the private mail stephane forwarded had these two attachments...
>
> >>> <Example.java><workaround.diff>
>
> verveinej chokes when trying to resolve 'BackingStoreException' to a
> Class. I have attached the short example file and the local 'hack' I am
> using to get pass this issue.
>
> holger
--
Nicolas Anquetil -- RMod team
INRIA Lille Nord Europe