You're right: Errai should only be scanning jars that have an ErraiApp.properties at their root. Are you reporting this issue because of a specific error message you're getting at GWT compile time? If so, I'd like to take a look at the full error message and stack trace that you're getting (including any nested "caused by" exceptions). Hopefully that will lead us to understand why the GWTP jar is getting scanned.
Even once you get past this, there may be more conflicts with the interpretation of javax.inject annotations by both Gin and Errai IoC/CDI. If you do get something working, we'd definitely be interested in hearing how you've combined Errai and GWTP!
1 of 1 people found this helpful
I've added support for blacklisting classes and packages in Errai IOC. Please see the JIRA for details.
New 3.0-SNAPSHOTs have been deployed if you want to give it a try.
Thanks, I will try it later.
Could you tell when the next release is planned (2.x or 3.x)? I didn't find planned dates for next releases in JIRA.
Regarding the blacklisting feature, it will surely work. But if the project is very big and has many dependencies, I think it may become tedious to blacklist all unnecessary dependencies. And because IOC links all classes, the resulting JS may become big. May I propose to also add whitelisting feature with behavior similar to typical filesets. So all classes from whitelist are included (defaults to everything) as long as they are not blacklisted.
If everything goes well we plan to release 3.0.0.M2 tomorrow. Yes, I see a white list feature being useful as well. It's easy to implement and of course similar to the black listing feature.
Could you create a JIRA for us? Would you be interested in taking a stab at it and send us a pull request?