December 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-477: ---------------------------------- Well, this is some OSGi-specific stuff and I'm no OSGi expert. However, we have Specification-Version in MANIFEST.MF file. > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Emily Jiang (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Emily Jiang commented on CDI-477: --------------------------------- [~mkouba] sorry. I jumped to the conclusion and meant you tried to delete the version info in the package-info.java. I agree that you can go ahead to delete the other blobs of javadoc. However, we need to add the javadoc of mentioning version: /** * @version xx */ What are the version do you say for the api packages? We need to specify them accurately as they are used by OSGi environment. I'll raise a separate issue to cover that. Please don't delete this file though. > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-662) Fix Instance.isResolvable() text

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-662?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-662: ----------------------------- Summary: Fix Instance.isResolvable() text (was: Fix Instance.isResolvable() text and javadoc) > Fix Instance.isResolvable() text > -------------------------------- > > Key: CDI-662 > URL: https://issues.jboss.org/browse/CDI-662 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 2.0 .Final > > > A note that {{Instance.isResolvable()}} *IS* resolving ambiguities is missing in the spec text and javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-664) Rename SeContainerInitializer.addInterceptors()/addDecorators()/addAlternatives()/addAlternativeStereotypes() and clarify the purpose

by Martin Kouba (JIRA)

Martin Kouba created CDI-664: -------------------------------- Summary: Rename SeContainerInitializer.addInterceptors()/addDecorators()/addAlternatives()/addAlternativeStereotypes() and clarify the purpose Key: CDI-664 URL: https://issues.jboss.org/browse/CDI-664 Project: CDI Specification Issues Issue Type: Clarification Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 2.0 .Final These methods should not add any class to the set of bean classes for the synthetic bean archive. The purpose is solely to compensate the absence of the {{beans.xml}} descriptor. The propsal is to rename: * addInterceptors() -> enableInterceptors() * addDecorators() -> enableDecorators() * addAlternatives() -> selectAlternatives() * addAlternativeStereotypes() -> selectAlternativeStereotypes() The new names correspond to the spec wording (see for example 5.1.1. Declaring selected alternatives). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-477: ---------------------------------- [~emilyj] I'm sorry but which version? I'm talking about this file: https://github.com/cdi-spec/cdi/blob/master/api/src/main/java/javax/enter... > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Emily Jiang (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Emily Jiang commented on CDI-477: --------------------------------- IIUC, the version is must have in the package-info.java. The info is used by bnd to work out the package version and extremely useful in OSGi environment. Besides, we should maintain the version correctly according to semantic versioning whitepaper (https://www.osgi.org/wp-content/uploads/SemanticVersioning.pdf). > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Emily Jiang (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Emily Jiang edited comment on CDI-477 at 12/7/16 5:31 PM: ---------------------------------------------------------- IIUC, the version is a must have in the package-info.java. The info is used by bnd to work out the package version and extremely useful in OSGi environment. Besides, we should maintain the version correctly according to semantic versioning whitepaper (https://www.osgi.org/wp-content/uploads/SemanticVersioning.pdf). was (Author: emilyj): IIUC, the version is must have in the package-info.java. The info is used by bnd to work out the package version and extremely useful in OSGi environment. Besides, we should maintain the version correctly according to semantic versioning whitepaper (https://www.osgi.org/wp-content/uploads/SemanticVersioning.pdf). > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-477: ---------------------------------- I think we should remove this javadoc. Most users have never seen this and it would be harder and harder to keep it up-to-date. What do you think? > Update outdated package-info.java in javax.enterprise.inject package > -------------------------------------------------------------------- > > Key: CDI-477 > URL: https://issues.jboss.org/browse/CDI-477 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > Update or remove this javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-663) Usage of repeatable qualifiers contradicts several statements in the spec

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-663?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-663: --------------------------------- I personally think we should make these statements more explicit and keep this validation rule for non-repeating annotations. > Usage of repeatable qualifiers contradicts several statements in the spec > ------------------------------------------------------------------------- > > Key: CDI-663 > URL: https://issues.jboss.org/browse/CDI-663 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Fix For: 2.0 .Final > > > Using repeatable qualifier is in contradiction with {{11.3.12. Observer method resolution}}: > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{5.6.1. The Instance interface}}: > | If two instances of the same qualifier type are passed to select(), an IllegalArgumentException is thrown. > {{10.2.3. The Event interface}} > | If two instances of the same qualifier type are passed to select(), an llegalArgumentException is thrown. > {{11.3.6. Obtaining a Bean by type}} > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{11.3.13. Decorator resolution}} > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{11.3.14. Interceptor resolution}} > | If two instances of the same interceptor binding type are given, an IllegalArgumentException is thrown. > Should we remove this statement or make it more explicit by saying that this is true only for non-repeatable qualifiers/annotations? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (CDI-663) Usage of repeatable qualifiers contradicts several statements in the spec

by Tomas Remes (JIRA)

Tomas Remes created CDI-663: ------------------------------- Summary: Usage of repeatable qualifiers contradicts several statements in the spec Key: CDI-663 URL: https://issues.jboss.org/browse/CDI-663 Project: CDI Specification Issues Issue Type: Bug Reporter: Tomas Remes Using repeatable qualifier is in contradiction with {{11.3.12. Observer method resolution}}: | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. {{5.6.1. The Instance interface}}: | If two instances of the same qualifier type are passed to select(), an IllegalArgumentException is thrown. {{10.2.3. The Event interface}} | If two instances of the same qualifier type are passed to select(), an llegalArgumentException is thrown. {{11.3.6. Obtaining a Bean by type}} | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. {{11.3.13. Decorator resolution}} | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. {{11.3.14. Interceptor resolution}} | If two instances of the same interceptor binding type are given, an IllegalArgumentException is thrown. Should we remove this statement or make it more explicit by saying that this is true only for non-repeatable qualifiers/annotations? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2016