Tomáš Kraus

@glassfishrobot Commented kohsuke said: Hmm. Would it be possible for you to try the latest nightly build? I remember fixing an issue like this some time ago, and I couldn't...

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=57) test class file which produces output

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=58) class file for first package

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=59) class file for second package

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=60) package info for second package

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=61) package info for first package

@glassfishrobot Commented ramazanyich2 said: Created an attachment (id=62) result of execution

@glassfishrobot Commented ramazanyich2 said: I tried it with lates build ( dated by 8 november) but in result I still have all namespaces. I attached all files to the issue....

@glassfishrobot Commented ktrapszo said: Using 4/19/2006 build, this is still an issue.

@glassfishrobot Commented kohsuke said: This is actually the expected behavior. In 1.0, we did what ramazanyich2 wanted us to do — namely, declare namespaces lazily on-demand, only when it's necessary....