jakartaee / jaf-api

Jakarta Activation Specification project

https://jakartaee.github.io/jaf-api/

jakartaee/jaf-api Issues

Could you please provide the source code for the tag 1.1.1 on GitHub?
Updated a month ago
Improve resource resolution
Updated 5 months ago6
Compatibility certification request for Eclipse Angus/Activation 2.0.2
Closed 4 months ago1
Support minimum JDK of 11+ and minimum of Android API 33+
Updated 5 months ago2
Jakarta Activation erroneously assumes that classes can be loaded from Thread#getContextClassLoader
Closed 6 months ago
Operational risk identified in Jakarta Activation
Closed 7 months ago1
Compatibility certification request for Eclipse Angus/Activation 2.0.1
Closed 7 months ago1
Remove SecurityManager references from API code in response to JEP 411
Updated a year ago
Add support for java.nio.Path
Closed a year ago
jakarta.activation-api is not a Multi Release JAR
Updated a year ago5
Compatibility certification request for Eclipse Angus/Activation 2.0.0
Closed a year ago1
Compatibility certification request for Eclipse Angus/Activation 1.1.0
Closed a year ago1
Project webpage is down
Closed 2 years ago3
JDK8: java.lang.ClassCastException: com.sun.activation.registries.MailcapFile cannot be cast to jakarta.activation.MailcapRegistry
Closed 2 years ago4
Drop Applet from the spec
Updated 2 years ago
MailcapCommandMap requires accessDeclaredMembers when Security Manager is enabled
Closed 2 years ago
TCK Challenge: TCK should not require JPMS module-info.class
Closed 2 years ago
Loading of service provider implementations needs to be done under doPriviledge
Closed 2 years ago
TCK Challenge: TCK should not require JPMS module-info.class
Closed a year ago25
Use OSGi service loader mediator instead of osgi resource locator
Closed 2 years ago1
Final steps for Jakarta Activation 2.1
Closed 2 years ago2
Compatibility certification request for Eclipse Angus/Activation 1.0.0
Closed 2 years ago1
Add jakarta.activation.spi to the spec
Closed 3 years ago
Move implementation out from the API repository
Closed 3 years ago4
Provide standalone implementation independent API jar
Closed 3 years ago
jakarta.activation-api 1.2.2 can't be used as OSGi bundle under JDK8
Updated 2 years ago5
Compatibility certification request for EE4J implementation of Jakarta Activation 2.0.1
Closed 3 years ago1
Release 2.0.1
Closed 3 years ago3
package-list and element-list are missing on the root of the Javadoc
Closed 4 years ago4
NoClassDefFoundError: com/sun/activation/registries/LogSupport
Closed 4 years ago3
Android compilation failure due to possible badly formed compiler args in pom.xml
Closed 4 years ago2
Tasks to complete the 2.0.0 release
Closed 4 years ago1
missing 2.0.0 release
Closed 4 years ago5
Add version string to generated javadoc
Closed 4 years ago
Update EFSL for Specifications and Javadoc
Closed 4 years ago1
rename javax.activation properties to jakarta.activation
Closed 4 years ago3
Update CONTRIBUTING.md for Specification Project's repositories
Closed 4 years ago
Deprecatation of PipedInputStream and PipedOutputStream
Updated 4 years ago1
Compatibility certification request for EE4J implementation of Jakarta Activation
Closed 4 years ago5
Two artifacts declare the same module name "jakarta.activation" – this does not work.
Closed 4 years ago12
JDK 9 set as minimal JavaSE in OSGi env
Closed 4 years ago5
Deliver Jakarta Activation Specification Version update for Jakarta EE 9
Closed 4 years ago4
Problems with MailcapCommandMap
Closed 4 years ago2
License specification is not clear
Closed 5 years ago1
Compatibility certification request for EE4J implementation of Jakarta Activation
Closed 4 years ago1
What about the term JavaBeans?
Closed 5 years ago5
Prepare Jakarta Activation for Jakarta EE 8 Release
Closed 5 years ago1
Convert "Eclipse Project for JAF" into a specification project
Closed 5 years ago4
Jakarta EE 8 TCK job
Closed 5 years ago2
Change project name to Jakarta Activation
Closed 5 years ago4