javax.inject module?
forax at univ-mlv.fr
forax at univ-mlv.fr
Wed Oct 4 18:36:01 UTC 2017
> De: "Lance Andersen" <Lance.Andersen at oracle.com>
> À: "Remi Forax" <forax at univ-mlv.fr>
> Cc: "Tom De Wolf" <tom.dewolf at aca-it.be>, "jigsaw-dev"
> <jigsaw-dev at openjdk.java.net>
> Envoyé: Mercredi 4 Octobre 2017 20:25:41
> Objet: Re: javax.inject module?
> Hi Remi,
> Sorry if my message was confusing.
it's not, it's my mind which is confused :)
> JEP 200, [ http://openjdk.java.net/jeps/200 | http://openjdk.java.net/jeps/200 ]
> , defines that:
>> ——————————————
>> Standard modules, whose specifications are governed by the JCP, have names
>> starting with the string "java." .
>> -----------------------------------------
> JSR 330 specifies the javax.inject package. The suggested module name would be
> java.inject.
> The hope is that the spec leads for JSR 330, will at a minimum update their API
> jar to include the MANIFEST attribute Automatic-Module-Name
> Automatic-Module-Name: java.inject
> This will help developers in the migration to modules.
thanks for the answer,
Rémi
> Best
> Lance
> On Oct 4, 2017, at 2:13 PM, Remi Forax < [ mailto:forax at univ-mlv.fr |
> forax at univ-mlv.fr ] > wrote:
>> Hi Lance,
>> i'm not sure you have the right to use java or jdk as prefix for your module, or
>> do you mean "javax.inject" ?
>> Rémi
>> ----- Mail original -----
>>> De: "Lance Andersen" < [ mailto:Lance.Andersen at oracle.com |
>>> Lance.Andersen at oracle.com ] >
>>> À: "Tom De Wolf" < [ mailto:tom.dewolf at aca-it.be | tom.dewolf at aca-it.be ] >
>>> Cc: "jigsaw-dev" < [ mailto:jigsaw-dev at openjdk.java.net |
>>> jigsaw-dev at openjdk.java.net ] >
>>> Envoyé: Mercredi 4 Octobre 2017 18:37:53
>>> Objet: Re: javax.inject module?
>>> You can grab the jar from maven central
>>> [ https://mvnrepository.com/artifact/javax.inject/javax.inject/1 |
>>> https://mvnrepository.com/artifact/javax.inject/javax.inject/1 ]
>>> The JSR can be found here https://jcp.org/en/jsr/detail?id=330.
>>> I am hoping to try and get the JSR 330 spec leads to support updating the
>>> implementation jar with an automatic module name if at all possible. The
>>> proposed module name is java.inject
>>> Best
>>> Lance
>>> On Oct 4, 2017, at 11:17 AM, Tom De Wolf <tom.dewolf at aca-it.be> wrote:
>>>> Hi,
>>>> Does someone know why the javax.inject annotations contained in for example
>>>> the following maven dependency are not part of the jdk?
>>>> <!-- https://mvnrepository.com/artifact/javax.inject/javax.inject -->
>>>> <dependency>
>>>> <groupId>javax.inject</groupId>
>>>> <artifactId>javax.inject</artifactId>
>>>> <version>1</version>
>>>> </dependency>
>>>> Who or which dependency/jar can be used to depend on this set of injection
>>>> annotations as an explicit module or a module with a reserved automatic
>>>> module name? Who is responsible to tackle this for javax.inject?
>>>> Thanks,
>>>> Tom De Wolf
>>>> Architect
>>>> ACA-IT Solutions
>>>> Belgium
>>> Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
>>> Oracle Java Engineering
>>> 1 Network Drive
>>> Burlington, MA 01803
>>> Lance.Andersen at oracle.com
> [ http://oracle.com/us/design/oracle-email-sig-198324.gif | Lance Andersen|
> Principal Member of Technical Staff | +1.781.442.2037Oracle Java Engineering 1
> Network Drive Burlington, MA 01803 ] [ mailto:Lance.Andersen at oracle.com |
> Lance.Andersen at oracle.com ]
More information about the jigsaw-dev
mailing list