George Gastaldi
George Gastaldi
Perhaps this project may give some ideas: https://github.com/square/javapoet
@lincolnthree yes, I discovered that through my investigation as well. The problem is that the comments are stored in the `CompilationUnit` but you can not modify them (or I haven't...
It's still not working. Unfortunately the solution with `Document` doesn't work when the class is created on-the-fly
@oc007us no evolution so far, unfortunately. Open for suggestions 😉
@oc007us I guess it depends on if the `MethodDeclaration` in JDT supports that, I am not a big fan of storing content that is not synchronized with the underlying JDT...
@asafbennatan If I understand it correctly, this won't solve the problem because in your `ParsingContext` implementation you're storing in a Map every .java file that was already parsed previously, therefore...
I think the `Roaster.parse` method needs a context object parameter that can provide implementations of `WildcardImportResolver`s and other features. For example, you could have something like: ```java ParsingContext context =...
> as for org.jboss.forge.roaster.spi.WildcardImportResolver - how should i test it with the service location feature ? - if i understand correctly you mean i have to implement WildcardImportResolver which will...
Right, now we'll need to define what's in the `ParsingContext` and how would it be used during the parsing
I like the idea of having a `ParsingContext` and building it (like adding `ImportResolvers` for example). That would provide a neat abstraction instead of having a default implementation storing parsed...