+1 to merge.
On Thu, Jun 25, 2020, 4:26 PM Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:
> +1 to merge them. It seems the simplest solution.
>
> On Thu, 25 Jun 2020 at 17:23, Colin Alworth wrote:
>
>> One potential option could be moving the tests into gwt-safecss, and only
>>
+1 to merge them. It seems the simplest solution.
On Thu, 25 Jun 2020 at 17:23, Colin Alworth wrote:
> One potential option could be moving the tests into gwt-safecss, and only
> release them together - the release process through sonatype will permit
> you to push more than one set of
One potential option could be moving the tests into gwt-safecss, and only
release them together - the release process through sonatype will permit
you to push more than one set of artifacts, test them in the staging repo,
and then release to central together. That would imply using either local
Not too much options I think, see
https://stackoverflow.com/questions/55429921/how-to-fix-cyclic-dependency-between-java-modules
Maybe a new common shared module (maven artifact in this case) or merge
safehtml and safecss into a new one and let them deprecated.
Juan
On Thu, 25 Jun 2020 at
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
