Re: [jakartaee-platform-dev] Publishing Question Regarding POMs

[Paul Nicolucci <pnicolucci@xxxxxxxxx>]

Hi,

The tlddoc artifact was a very old project that was leveraged by the Jakarta Tags project to generate TLD documentation. It hasn't been maintained in 15+ years: https://mvnrepository.com/artifact/taglibrarydoc/tlddoc

Given changes in Jakarta EE we need a way to update tlddoc. The project forked the code to make changes to ensure that the documentation can still be generated as we make updates for the current and newer versions of Jakarta EE.

If we don't publish the forked version to maven central then no one else will be able to generate the tlddocs of the implementation if they wanted to. I don't know if this is a big deal or not since we publish them as part of the release: https://jakarta.ee/specifications/tags/2.0/tagdocs/

If we publish @volodymyr I think starting at a new version makes sense. If published it will be alongside the implementation artifacts in maven central.

Thoughts?

Regards,

Paul Nicolucci

On Tue, Feb 1, 2022 at 9:35 AM Volodymyr Siedlecki <volosied@xxxxxxxxx> wrote:

Hi,

I'm not sure if I could call it the next release of TLDDoc. We'll also likely use different coordinates when publishing the artifact.

Thank you for your help. We'll likely publish our version then.

Volodymyr

On Mon, Jan 31, 2022 at 1:00 PM Erik Brangs <erik.brangs@xxxxxx> wrote:

Hi,

On 31.01.22 15:44, Volodymyr Siedlecki wrote:
> Can we publish an artifact if the included pom.xml relies on an internal (i.e. not published) dependency?  For instance, If someone tried to build this component from the source jar (by relying on the META-INF/maven.org.glassfish.web.jakarta.servlet.jsp.jstl/pom.xml), is it okay if a dependency fails to resolve?
>
> For some context: our next JSTL release will be built using our local version TLDDoc  (the last published version, 1.3, is incompatible with the jakarta namespaces). As we update TLDoc in our jstl-api project, the question is whether we should also publish our version or not. TLDDoc is used solely for generating TLD documentation (hence the dependency).
>
> The TLDDoc Code Port issue for reference: https://github.com/eclipse-ee4j/jstl-api/issues/195 <https://github.com/eclipse-ee4j/jstl-api/issues/195>
>
> Appreciate any help here.

If I understand the context correctly, TLDDoc was part of Java EE. Therefore, it's now part of Jakarta EE.

So what you've been working on isn't a "local" or "internal" version but the next release of TLDDoc. Therefore, it ought to be public.


Kind regards,

Erik Brangs
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev