Ah. Figured out what is going on. The top-level POM builds a combined
API and implementation JAR. Yuck.
Yes, another Yuck case!
Historically all the releases of _expression_ Language have been the combined one, but going forward I'd like to first remove the combined one, and then move the impl one, like JSP, to its own project.
But there are almost always more pressing issues...
Kind regards,
Arjan
I'll move this POM to a sub-directory for now although my instinct is to
remove it entirely. I'll create a new top-level POM based on
JSP/WebSocket that builds the individual modules (api, impl, spec)
Mark
>
> Mark
>
>
> On 08/06/2020 10:53, Mark Thomas wrote:
>> Hi all,
>>
>> Just an FYI that I'll be creating an RC2 shortly. The main reason is so
>> we have an up to date tag from which to generate the specification
>> document to include in the Jakarta EE milestone release.
>>
>> There are no externally visible changes in the API (just internal code
>> clean-up) so existing downstream dependencies won't need to update to
>> RC2 (but of course they can if they want to).
>>
>> Mark
>>
>> _______________________________________________
>> el-dev mailing list
>> el-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/el-dev
>>
>
> _______________________________________________
> el-dev mailing list
> el-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/el-dev
>
_______________________________________________
el-dev mailing list
el-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/el-dev
