Changes

Update version to snapshot (#450)

* Update version to SNAPSHOT

* Fix Travis build - use JDK 8 and 11, remove build notifications, always build javadoc

* Travis - force javadoc build on PRs to verify that it works correctly.

* Fix Javadoc build with JDK 11, define javadoc plugin version.

Add EJB dependency only as JavaDoc dep. (#449)

[Issue-457] Observer resolution - assignability clarification

Signed-off-by: Lin Gao <aoingl@gmail.com>

Throw an exception without setting configuredProvider to null when getCDI returns null

Signed-off-by: Benjamin Confino <benjamic@uk.ibm.com>

Fix XML descriptor

Signed-off-by: Thiago Henrique Hupner <thihup@gmail.com>

Refer to Jakarta DI instead of JSR330

Signed-off-by: Jonathan Coustick <jonathan.coustick@payara.fish>

Removal of deprecated APIs: Bean.isNullable()

Removal of deprecated APIs: BeanManager.fireEvent()

Removal of deprecated APIs: BeanManager.createInjectionTarget()

Removal of deprecated APIs: BeforeBeanDiscovery.addAnnotatedType()

Removal of deprecated APIs: Compatibility with 1.0 perception of no beans.xml

Removal of deprecated APIs: @New

Change development version to 4.0.0-SNAPSHOT.

cdi-468 Split Spec doc to introduce CDI Lite

Signed-off-by: antoinesd <antoine@sabot-durand.net>

cdi-468 Split Spec doc to introduce CDI Lite
additional split

Signed-off-by: antoinesd <antoine@sabot-durand.net>

Contributing suggested changes.

Incorporate additional changes - move specialization to Full; change Modularity paragraph.

Attempt to make the Full part more readable - merge decorator limitations into one chapter. Add multiple notions of Full - specific rules cak to original chapters and note that this behaviour is not in Lite.

Split interceptors chapter into Lite and Full, state that Lite only support inteception declaring with bindings.

comprehensive review and various Lite/Full split changes

remove duplicate interceptors_full inclusion

actually include the beanmanager_lite.asciidoc file

Rename occurrences of BeanManagerLite to BeanContainer.

fix some typos and clumsy wording

Draft Lite version of BeanManager, add ability to obtain this BM version from CDI class.

initial Build Compatible Extension API proposal

Signed-off-by: Ladislav Thon <lthon@redhat.com>

Prepare for release of 4.0.0.Alpha1

Switch back to development version 4.0.0-SNAPSHOT.

Correction to wording of EventMetadata#getInjectionPoint

Add getBeanContainer() method to SeContainer for consistency

A new method called getBeanContainer() was added to the CDI type. For consistency this PR adds the same method to the SeContainer interface.

Create GH actions file, remove travis file.

Fixes #502

Start cleanup of AnnotationTarget

remove App{Archive,ArchiveConfig,Deployment}, rename AppArchiveBuilder and ContextBuilder

The `AppArchive`, `AppArchiveConfig` and `AppDeployment` types
were redundant. Moreover, they looked like they can access whole
world, which prevents certain kinds of implementations. (Some
effort was made to design the API in these types so that whole
world access is not necessary, but it's a leaky abstraction.)
For those reasons, these types are removed altogether.

The `AppArchiveBuilder` type is renamed to `ScannedClasses`,
which is more descriptive (and shorter). The `addSubtypesOf`
method is removed, because it can't be implemented in certain
environments (notably, Portable Extensions).

The `ContextBuilder` type is renamed to `ContextConfig`, because
it isn't really used in the usual builder way and is quite close
to the other existing `*Config` types.

Additionally, some documentation is improved, especially for
types in the `@Discovery` phase.

remove Annotations and add AnnotationBuilder

The `Annotations` API was a provisional solution for creating
annotation instances. This commit replaces it with a simpler,
more traditional builder API: `AnnotationBuilder`. Considering
that `AnnotationInfo.target()` was dropped, the builder can
simply produce `AnnotationInfo` instances, which allows
simplification of other APIs that expect users to pass
annotation instances (annotation transformation and synthetic
component registration).

Additionally, this commit tries to establish a convention
for documenting `null` handling:

- if the user is forbidden to pass `null`, we say "must not
  be null" and we don't have to document that a NPE will be
  thrown;
- if the API guarantees that `null` will never be returned,
  we simply say "never null".

remove AnnotationMember

rename AnnotationMemberValue to AnnotationMember

add SCM info to the POM

[maven-release-plugin] prepare release 4.0.0.Alpha2

[maven-release-plugin] prepare for next development iteration

extension API improvements

That is specifically:

- change the `*Config` types to no longer inherit from the corresponding
  `*Info` types; instead, they provide an `info()` method
- rename `AnnotationConfig` to `DeclarationConfig` for symmetry
  between `*Info` and `*Config` types
- change the annotation transformation methods on `DeclarationConfig`
  to return `this` to allow fluent usage
- allow additional parameter types for `@Enhancement` methods:
  `DeclarationConfig`, `DeclarationInfo`, `ClassInfo`, `MethodInfo`,
  and `FieldInfo` (`*Info` types are useful when only collecting
  information during `@Enhancement`, not modifying anything)
- remove useless type parameters from `AnnotationInfo`, `ClassInfo`,
  `MethodInfo`, `FieldInfo`, `ClassConfig`, `MethodConfig`, `FieldConfig`,
  `BeanInfo`, and `ObserverInfo`; the `SyntheticBeanBuilder` type
  still has a type parameter, which remains an open question
- add a lot of documentation

Make AnnotationLiteral lazy

Cleanup Types interface / add forName

Add BuildServices interface

Add ofClass(String)

Change definitons of explicit/implicit archive, add notion about backwards compatibility.

improve extension API documentation and resolve some open questions

- renamed/moved `AnnotationInfo.MEMBER_VALUE` to `AnnotationMember.VALUE`
- replaced the phrase "component type" with "element type" when speaking
  about arrays, because JLS uses both and each has a different meaning
- removed `ContextConfig`, custom context registration is now fully
  handled in `MetaAnnotations`
- removed unnecessarily concrete language from `@SkipIfPortableExtensionPresent`
- methods in the `Types` class now have more specific return types
- implementations of `AnnotationInfo`, `AnnotationMember` and `AnnotationTarget`
  are now required to define `equals` and `hashCode`, and are explicitly
  not required to use a single object to represent a single construct
- the `ClassInfo` declaration is now required to return annotations
  `@Inherited` from a superclass, per `@Inherited` spec and CDI spec
- explicitly documented that `ClassInfo` doesn't provide access to nested
  classes or an enclosing class, and `PackageInfo` doesn't provide access
  to package members
- corrected some language to distinguish between generic classes (before
  type argument application) and parameterized types (after type argument
  application)
- specified meaning of `MethodInfo.name` and `returnType` for constructors,
  mirroring what reflection does (returning the declaring class)
- defined how implicit bounds are represented in `TypeVariable`
  and `WildcardType`
- removed `ObserverInfo.id()`
- usage of `Optional` was eliminated everywhere
- instead of "`void` type", we now always use "`void` pseudo-type"
- added `@since 4.0` tags everywhere
- changed `@link` tags to `@linkplain` if the link text isn't an identifier

Initial beans_4_0.xsd (#517)

* Add a beans_4_0.xsd file and document changes in CDI Lite and default beans-discovery-mode
Addresses #497

Signed-off-by: Scott M Stark <starksm64@gmail.com>

Update beans_4_0.xsd

Fix a 3.0 reference and improve the wording in the bean-discovery-mode attribute doc

improve extension API documentation and resolve some open questions

- documentation added for synthetic beans and observers; this was
  the last place where proper documentation was missing
- `DeclarationConfig` is no longer generic and `{Class,Method,Field}Config`
  explicitly override the configuration methods, so that users don't have to
  declare a useless type argument when using `DeclarationConfig`
- `AnnotationMember.as*` methods don't perform type conversions
- added `MethodInfo.isConstructor` to distinguish constructors
  from regular methods

fix SyntheticObserverBuilder copy&paste mistake

Remove TODO referring to singleton as potential bean defining annotation.

Replace BeanManager#getEvents with reference to BeanContainer.

Align wording in unsatisfied and ambig dependencies with that in ambiguous names.

Allow using @Priority within stereotypes.

API changes for allowing @Priority on stereotypes

Adjust wording of specification and API around @Priority usage on stereotypes.

add BeanConfigurator.priority

This is to allow setting a priority for synthetic beans created
using `BeanConfigurator`.

I briefly considered if `priority` should be added to
`BeanAttributesConfigurator` as well, but that would have
a ripple effect. It also doesn't reflect the present reality.
A custom `Bean` implementation can be added a priority
by implementing the `Prioritized` interface. Adding only
`BeanConfigurator.priority` is a perfect mirror of that
in the configurator API.

[maven-release-plugin] prepare release 4.0.0.Alpha3

[maven-release-plugin] prepare for next development iteration

add specification text for BeanConfigurator.priority

improve extension API

- explicitly specified that CDI implementations don't have to accept
  custom implemetations of the `jakarta.enterprise.lang.model` and
  `jakarta.enterprise.inject.build.compatible.spi` interfaces
- moved to Jakarta Annotation 2.1.0-B1, removed `@ExtensionPriority`
  and specified that `@Priority` should be used on extension methods
- specified that `AnnotationBuilder.build` will throw if some members
  of the annotation type were not defined
- adjusted `AnnotationBuilder` so that its methods no longer accept
  varargs; arrays must be passed in explicitly to avoid ambiguity
  in case of single-element arrays
- added `InterceptorInfo` (extending `BeanInfo`) to provide
  information about interceptors, and allowed `@Processing` methods
  to declare parameters of type `InterceptorInfo`
- adjusted `@Enhancement` so that parameters of type  `DeclarationInfo`
  and `DeclarationConfig` can no longer be declared; it is not clear
  what is the full set of matching values
- replaced the use of `Map<String, Object>` in synthetic components
  functions by a dedicated `Parameters` interface
- adjusted synthetic component builders to allow defining a parameter
  of an enum type, as well as using `ClassInfo` for defining a parameter
  of a `Class` type
- improved `ParameterizedType` to provide access to the type (`ClassType`)
  of the generic class, in addition to the declaration (`ClassInfo`)
- replaced abbreviated forms "isn't", "doesn't" and "can't"
  with their longer forms "is not", "does not" and "cannot"

improve extension API documentation and resolve some open questions

- modified the `@Processing` phase to also execute for synthetic beans
  and observers, after `@Synthesis` is finished
- added annotation transformations for method parameters (`ParameterConfig`)
- changed `ArrayType` to use a component type representation,
  instead of a representation with element type + number of dimensions
- clarified what happens with non-existing annotation members defined
  using `AnnotationBuilder` in the resulting `AnnotationInfo`
- clarified the set of error conditions for `Types.ofArray()`
- settled on the current design for `Parameters`, removed the comment
  that outlines another possible design
- removed some TODOs where alternative design options exist, but they
  have no obvious advantage (one design simply has to be chosen)

add support for records to the language model

Programmatic lookup improvements, introduce Handle interface.

Address the TODO in preface.

Address TODO in inter-module injection.

Explicitly state that Java SE impl of CDI has to be Full implementation.

Decide on other mentions of Full-only concepts in the CDI Lite spec part.

Address remaining TODOs for passivation mentions.

Introduce observable CDI events representing container state.

improve extension API and resolve all remaining open questions

- settled on the name "Build Compatible Extensions"
- renamed `@Processing` to `@Registration`, because if we ever want
  to introduce an extension phase for modifying beans before they
  are registered, _that_ should be called `@Processing`
- moved the synthetic bean creation/destruction functions from
  the `CreationalContext` style to the `Instance` style
- specified precisely how `ClassInfo.methods` and `fields` work,
  specified that `ClassConfig` behaves identically, and specified
  that an extension methods with parameters of type `MethodInfo`
  or `FieldInfo` also behave identically
- removed the `@ExactType` and `@SubtypesOf` annotations and moved
  type queries directly to the `@Enhancement` and `@Registration`
  annotations
- moved the `MetaAnnotations` API from accepting a callback
  to directly returning `ClassConfig`
- specified lifecycle of `SyntheticBean{Creator,Disposer}` and
  `SyntheticObserver`
- specified that `Messages.error` is treated as a deployment problem

Change BeanManager treatment in CDI Lite

Previously, the specification downright disallowed obtaining
a `BeanManager` in CDI Lite. This makes portability from CDI Full
to CDI Lite harder, which also manifests in the CDI TCK.

Wit this commit, CDI Lite applications may obtain a `BeanManager`,
but may only call methods inherited from `BeanContainer`.

Draft changes for packaging/deployment/lifecycle.

Rename files and chapter refereces to align with rest of the specification

Rename files and chapter refereces to align with rest of the specification

Move certain parts of the specification from Lite to Full

That is, specifically, parts that mentioned Portable Extensions
yet still belonged to the Lite part of the specification.

This commit resolves a lot of remaining TODO items.

CDI Lite packaging, deployment and lifecycle specification

Create an extra chapter "Context management for custom scopes"

Describe in more depth what kind of interception is supported in Lite.

Create _config.yml

Create 2021-10-25-coming-soon-post.adoc

Create index.md

Get the pages content working

Signed-off-by: Scott M Stark <starksm64@gmail.com>

Fix the description

Signed-off-by: Scott M Stark <starksm64@gmail.com>

Add url setting

Signed-off-by: Scott M Stark <starksm64@gmail.com>

Update baseurl to /cdi

Signed-off-by: Scott M Stark <starksm64@gmail.com>

Fix nokogiri security alert

Signed-off-by: starksm64 <starksm64@gmail.com>

Rename the comming soon doc

Signed-off-by: starksm64 <starksm64@gmail.com>

Revert to simple markdown as asciidoc plugin is not supported by github pages natively

Signed-off-by: starksm64 <starksm64@gmail.com>

Fix the post header

Signed-off-by: starksm64 <starksm64@gmail.com>

Add the way to cdi 4 content from @manovotn for preview

Signed-off-by: starksm64 <starksm64@gmail.com>

Mark the page as unpublished

Signed-off-by: starksm64 <starksm64@gmail.com>

Add the on the way to cdi post by @manovotn
Add author info/links

Signed-off-by: starksm64 <starksm64@gmail.com>

Add author collections

Signed-off-by: starksm64 <starksm64@gmail.com>

Fix site authors page links

Signed-off-by: starksm64 <starksm64@gmail.com>

Change headers and nested lists to markdown syntax. (#550)

Fix the copy/paste errors in the README.md

Signed-off-by: starksm64 <starksm64@gmail.com>

Correct the readme url in 2021-10-25-pages-here.md (#551)

Update the root readme

Signed-off-by: starksm64 <starksm64@gmail.com>

Remove the notion of version from Packaging and deployment for CDI Full.

[maven-release-plugin] prepare release 4.0.0.Beta1

[maven-release-plugin] prepare for next development iteration

Correct GH pages post links to markdown syntax.

Add a recommendation for bean archive portability between Lite and Full

Adjust Handle.get() behavior - throw exception if attempting to get() reference which was destroyed.

Separate the language model to a dedicated module

Also add `package-info.java` and `overview.html` files,
so that the generated javadoc looks a bit better.

Clarify how conflicting default scopes and priorities on stereotypes work

Language model only returns runtime-retained annotations in build compatible extensions (#554)

The language model API itself doesn't specify what annotations are
accessible. In the CDI context, only runtime-retained annotations
make sense, because that's the only way all implementation strategies
can be consistent. That's because:

- purely runtime implementations, such as Weld, only have access
  to runtime-retained annotations;
- bytecode-based implementations, such as ArC, only have access
  to runtime-retained and class-retained annotations, but don't
  have access to source-retained annotations;
- annotation processing-based implementations, such as ODI, have
  access to all annotations.

An alternative would be to specify that the language model _always_
returns only runtime-retained annotations. That would be just fine
strictly from the CDI perspective, but unforeseen cases may exist
where the language model API would be useful, but nothing would
prevent providing access to class-retained or even source-retained
annotations. Hence, I believe it is better to make the restriction
on the CDI level, and not on the language model level.

Update asciidoc plugins, config (#559)

* Update asciidoc plugin and config for #558
* Add explicit asciidoctorj version and dependency, update sourceDirectory and imagesdir
* Correct the revnumber and revdate

Signed-off-by: starksm64 <starksm64@gmail.com>

Language model and build compatible extensions API clarifications

- renamed `BeanInfo.getName()` to `name()` for consistency
- renamed `ObserverInfo.observedType()` to `eventType()` for clarity
- added `SyntheticComponents.addObserver(Type)` to allow registering
  synthetic observers of parameterized types
- changed `WildcardType` representation to always include an upper
  bound; the `? extends Object` type is no longer represented as `?`
  because the upper bound may be annotated
- improved specification of `AnnotationTarget`, especially around
  repeatable annotation types
- improved specification of `ClassInfo` and `MethodInfo`, especially
  around implicit declarations and `abstract` classes/methods