Re: [jakarta.ee-spec.committee] Pushing EFTL and EFSL binaries to Maven

[Scott Stark <sstark@xxxxxxxxxx>]

We touch on this today on the call where I asked about allowing GAVs to update for the changes in the project names, and we did thing that was something that needed to be done, it did not need to be done for the EE 8 release. It could be addressed when we have a bunch of chaos around javax to jakarta.

On Jul 12, 2019, at 3:34 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

Posting this one deliberately on our private list due to legal nature.

Kevin had asked if jakarta.management.j2ee was the right groupId to publish the management-spec*.pdf.  Truthfully, there is no correct groupId to publish non-open source binaries to Maven Central, so I don't know there is a correct answer to that question.

Now we are right up against the wall on timing for this release, so I'm pragmatically ok with "oops" and fixing this later.  CDI creates two binaries, one ASL for Maven Central and one for the JCP which is not published, so this is definitely a solvable issue.

With that said, when we have open source licensed versions of spec and TCK to publish, I think putting them in jakarta.management.j2ee, etc, is fine.   At this moment, most people's specs are not aimed at the jakarta.* groupId.

What do other's think?

 - Look the other way yes/no or fix now with another round of PRs for all specs?

 - Does everyone need to consistently publish specs to the jakarta.* groupId? (another round of PRs)

-- 

David Blevins

http://twitter.com/dblevins
http://www.tomitribe.com

310-633-3852

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee