Open GoogleCodeExporter opened 9 years ago
The same is true for generated sources, i.e. source code that is generated into
build/generated-sources/**
The source files from this folder are accessible through Netbeans (there is a
node
Generated Sources in the Projects view), but are marked with errors, and when
using
the generated classes in other code, autocompletion is not working.
Original comment by FlorianB...@gmail.com
on 12 Nov 2009 at 12:47
Original comment by laurent....@gmail.com
on 12 Nov 2009 at 1:33
I am also seeing problems with resolving imports in JSP pages when the classes
are in the ivy libraries. I had to add the .jar file stored in the ivy cache to
my project to get the import to resolve.
Original comment by br...@hulseware.com
on 12 Oct 2010 at 11:30
Predictably, the same thing happens when editing facelets for a JSF program.
I'm guessing that IvyBeans needs to publish these jars more widely to the
Netbeans framework.
Original comment by malcolm....@googlemail.com
on 9 Nov 2010 at 9:34
Um, hi, getting the same problems as above.
I'm trying to convince my colleagues that we should be using Ivy based
dependency management, but this bug makes it hard to get the Netbeans user's
convinced.
ANY chance there has been some progress on this?
Since you know, the dates here go back to 2009?
Original comment by hs.coet...@gmail.com
on 11 Feb 2011 at 8:50
Finally, I managed to dive into the source code and understand what is
happening. Please find attached a patch for this issue.
Original comment by florian....@3kraft.com
on 3 May 2011 at 12:08
Attachments:
Ok for WEB_INF and WEB_SOURCE but not for TEST_SOURCE.
Thanks for the patch.
Original comment by laurent....@gmail.com
on 20 Jul 2011 at 1:37
Original issue reported on code.google.com by
FlorianB...@gmail.com
on 9 Nov 2009 at 10:52