On 22/04/2016 11:36, Paul Bakker wrote:
Thanks for the answer Remi. I'm wondering if a (optional) build step is
considered. During build the byte code analysis that jdeps does could be used
to generate better metadata for automatic modules. This would be a compromise
between using automatic m
Hi Alan,
Thanks, the -addmods hint is a very useful one, I had not tried that yet. After
adding the jackson.core and jackson.annotations explicitly to -addmods, I can
compile/run without depending on them in my demonstrator module. That's a good
workaround.
Paul
> On 22 Apr 2016, at 13:16,
On 22/04/2016 09:52, Paul Bakker wrote:
Why don't automatic modules take better care of transitive dependencies, so
that the application's module-info looks similar to what it would after
transforming the dependencies to named modules?
As Rémi said, there isn't any static analysis done at com
aul,
>
> - Mail original -
>> De: "Paul Bakker"
>> À: jigsaw-dev@openjdk.java.net
>> Envoyé: Vendredi 22 Avril 2016 10:52:23
>> Objet: requires public for automatic modules
>>
>> Hello,
>>
>> I'm experimenting with automat
Hi Paul,
- Mail original -
> De: "Paul Bakker"
> À: jigsaw-dev@openjdk.java.net
> Envoyé: Vendredi 22 Avril 2016 10:52:23
> Objet: requires public for automatic modules
>
> Hello,
>
> I'm experimenting with automatic modules again. I have a mo
Hello,
I'm experimenting with automatic modules again. I have a module "demonstrator"
that uses Jackson Databind.
import com.fasterxml.jackson.databind.ObjectMapper;
ObjectMapper mapper = new ObjectMapper();
String json = mapper.writeValueAsString(modularity
