[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-build] extension.name / apiPackage inconsistent between projects?
|
It would be great if the PMC could document these decisions and recommendations somewhere. Currently it is hard to find this information.
I believe the PMC decided that these should be jakarta.*, but didn't
require these to be changed for this release.
arjan tijms wrote on 1/3/19 6:58 AM:
Hi,
Quite a number of projects uses "javax" for the
extension.name
/ apiPackage. For instance:
<properties>
<non.final>false</non.final>
...
<artifactId>spec-version-maven-plugin</artifactId>
<version>1.5</version>
<configuration>
<specMode>jakarta</specMode>
<spec>
<groupIdPrefix>jakarta.</groupIdPrefix>
...
...
<instructions>
<Automatic-Module-Name>java.security.auth.message</Automatic-Module-Name>
<Bundle-Version>${spec.bundle.version}</Bundle-Version>
<Bundle-SymbolicName>${spec.bundle.symbolic-name}</Bundle-SymbolicName>
Should this stay at "javax" or become
"jakarta" after al?
Kind regards,
Arjan
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
--