I see the merge of both into one as the simplest solutions, so +1 to the merge
On Thursday, June 25, 2020 at 11:14:46 PM UTC+3, Frank Hossfeld wrote: > > To prepare GWT for j2cl we need to move the modules out of GWT, replace > generators with ATP, etc. This is in progress and the first modules > (SNAPSHOT) are released. > > Migrating gwt-safehtml and gwt-safecss runs into a problem, cause > gwt-safehtml depends on gwt-safecss and gwt-safecss depends on > gwt-safehtml. This is a serious issue, cause one can not be build and > tested without the other. > > To solve this issue, we are looking for solutions. > > One solution might be to move the tests out of gwt-safehtml. But then > gwt-safehtml needs to be build and deployed before the tests run and might > be deployed with failing tests. That looks like a bad solution. At the > moment the idea is to move the sources and tests from gwt-safecss into > gwt-safehtml and delete gwt-safecss. This will remove the cycle dependency > between these two modules, but doing so, the module will be the first > module that contains two old modules in one new. > > Any other ideas how to solve this issue? > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/052a3925-34b5-4ee1-b84b-c49a47c82a49o%40googlegroups.com.
