Weld 3.0 Beta1 release start Wednesday
by Antoine Sabot-Durand
Hi all,
Just to tell you that CDI 2.0 beta1 should be released on Wednesday. At
that time all PR with "riview_priority_major" should be merged, so please
continue the review work on the last 4 which are open.
Thanks,
Antoine
8 years
Clarification of BeanManager.getReference
by John Ament
All,
A discussion popped up on a recent CXF vote. As I understand it, per section 11.3.2 (from CDI 1.2), The Type parameter passed in to getReference is meant to be the class to proxy for the returned object, if the object requires a proxy (e.g. a normal scoped bean). Is that accurate? Or is the underlying type the type of the returned bean, from Bean.create(CreationalContext) ?
John
________________________________
NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.
8 years
[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:
---------------------------------
[~antoinesabot-durand] [~mkouba] Antoine, I propose to put the export package version in package-info.java instead of manifest.mf. In this way, it is much easier to maintain each individual package version. If you add some apis in one package, you will know you need to change the package version. Each package version should be maintained individually. We should use bnd to generate the manifest.mf instead of had baking each individual package and version. I'll open up a separate jira to get this done properly.
> 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
> Assignee: Antoine Sabot-Durand
> Fix For: 2.0 .Final
>
>
> Update or remove this javadoc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (CDI-477) Update outdated package-info.java in javax.enterprise.inject package
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-477?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand edited comment on CDI-477 at 12/9/16 5:17 AM:
-------------------------------------------------------------------
[~emilyj], I guess, your issue is probably related to section 10.3 of BND doc: http://bnd.bndtools.org/chapters/170-versioning.html
The doc talks of having version in package-info or manifest. We never had the version in package-info but in manifest, so removing the file won't change anything.
I suggest that we remove the file as Martin suggest it.
And if having the version in manifest and not in package-info is an issue, that issue has been here since version 1.0 and s not related to this ticket.
If so, feel free to create a specific ticket for this bnd / OSGi version tracking and detail why having version in manifest vs package-info is a issue.
was (Author: antoinesabot-durand):
[~emilyj] your issue is probably related to section 10.3 of BND doc: http://bnd.bndtools.org/chapters/170-versioning.html
I suggest that we remove the outdated content in this file and that you create a specific ticket for this bnd / OSGi version tracking, since it should be tracked clearly and not mix with documentation IMO.
> 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
> Assignee: Antoine Sabot-Durand
> Fix For: 2.0 .Final
>
>
> Update or remove this javadoc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years
[JBoss JIRA] (CDI-665) Annotated configurators - provide an easy way to remove repeatable annotations
by Martin Kouba (JIRA)
Martin Kouba created CDI-665:
--------------------------------
Summary: Annotated configurators - provide an easy way to remove repeatable annotations
Key: CDI-665
URL: https://issues.jboss.org/browse/CDI-665
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Martin Kouba
Fix For: 2.1 (Discussion)
Right now, all the configurators work with the "real" annotations, e.g. a predicate used in {{AnnotatedTypeConfigurator.remove(Predicate<Annotation>)}} will receive the container annotation and not the repeatable annotation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years