Le dim. 11 sept. 2022 à 11:24, Christoph Läubrich a
écrit :
> > For me it means the user knows the dep as any generating plugin can
> imply deps (like jaxws implies jaxb for ex even if module is jaxb free
> with that plugin).
>
> This will only work if the dependencies are static and can not com
I notice the release process happened on the repository. Thank you! If you
need a volunteer to verify the release candidate or any help, please let me
know :)
Best,
tison.
tison 于2022年9月10日周六 17:16写道：
> Hi,
>
> Bump this thread as a kind reminder ;)
>
> Best,
> tison.
>
>
> Romain Manni-Bucau
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12351491
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C
> For me it means the user knows the dep as any generating plugin can
imply deps (like jaxws implies jaxb for ex even if module is jaxb free
with that plugin).
This will only work if the dependencies are static and can not come from
the reactor and can be determined *before* the data is actual
Le dim. 11 sept. 2022 à 09:05, Christoph Läubrich a
écrit :
> > Sounds like it breaks concurrency uofront scheduling no?
>
> For sure it will interfere with what the scheduler think is the best
> strategy, but not be a concern of the scheduler as it was explicitly
> request to change the build o
> Sounds like it breaks concurrency uofront scheduling no?
For sure it will interfere with what the scheduler think is the best
strategy, but not be a concern of the scheduler as it was explicitly
request to change the build order.
> When I had to do that I was referencing projects between th
