Version: 2.2.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.28-13-generic 1) File->New 2)Save->... 3)Code->Import classes-> Select file with follo
> Select file with follo ? Looks truncated to me; please complete.
Created attachment 35816 [details] umbrello stack trace
Created attachment 35817 [details] the java-file I want to import
the bug is reproducable on windows using recent svn msvc build
Created attachment 66219 [details] patch fixing the runtime error The problem here is that the java importer crashes when a java file is imported from a location outside the regular java package hierachy. While finding unknown classes the parser tries to step up in the package hierachy to find the package root, which fails with a runtime error when the path do not fit into the package hierachy. Because java package hierachy is very important for the java import I suggest to add a user warning if file pathes of imported files are outside the java package hierachy.
fixed in svn
set version-fixed-in from 4.8.0 changelog
Hello, Now I have a computer with ubuntu 14.04 LTS 64 bit and I have the same probleme with the umbrello 4.4.13-0 ubuntu0.1 package. Could you help me please Best regards mparchet
Created attachment 88821 [details] List view after import of attachment 35817 [details] (In reply to mparchet from comment #8) > > Now I have a computer with ubuntu 14.04 LTS 64 bit and I have the same > probleme with the umbrello 4.4.13-0 ubuntu0.1 package. Cannot reproduce using umbrello-2.14.x: * Download attachment 35817 [details] * mkdir -p de/jjae/util/metaprogramming/set * mv SetOperationForDouble.java de/jjae/util/metaprogramming/set/ * Start Umbrello * In Code -> Activate Language select Java * In Code -> Import Project... navigate to the "de" directory created above * Press <OK> * No crash, list view appears as in this screenshot.
(In reply to juergen.jaeschke from comment #2) > Created attachment 35816 [details] > umbrello stack trace Your stack trace begins as follows: > This backtrace appears to be of no use. > This is probably because your packages are built in a way which prevents creation of proper > backtraces, or the stack frame was seriously corrupted in the crash. It is impossible to tell what really happened here.
Hello, To reporoduce this bug. 1.