Re: [el-dev] Tagging RC2

[Mark Thomas <markt@xxxxxxxxxx>]

On 10/06/2020 14:35, Mark Thomas wrote:
> On 10/06/2020 13:46, arjan tijms wrote:
>> Hi,
>>
>> On Wed, Jun 10, 2020 at 1:59 PM Mark Thomas <markt@xxxxxxxxxx
>> <mailto:markt@xxxxxxxxxx>> wrote:
>>
>>     I think that is a Maven thing. I've seen parent POMs published
>>     elsewhere. I'm not really sure though as I am not that familiar with
>>     Maven.
>>
>>
>>
>> The parent pom only needs to be published if a child module explicitly
>> references it. In many of the API projects referencing the parent isn't
>> done (the child module directly references the EE4J pom as parent), or
>> when it's done, it's not rarely a mistake.
> 
> I'll see if I can find a way to use the el-parent without an explicit
> reference.

I don't believe this is possible.

So, I think we have, essentially, two options.

1. Stick with the current structure and publish the el-parent pom

2. Copy the information from el-parent into each of the module poms as
appropriate and have the module poms use org.eclipse.ee4j:project:1.0.6
as their parent

While 2 does result in some duplication, I think that is a better fit
for the medium term goal of moving the implementation off to a separate
project. If the spec moves (and I'm undecided on this) I think it would
only need to move to a separate repo (mainly so we can tag it separately).

The CI setup needs a little more thought. Currently it can build API
only or API + impl and they share a tagging / version numbering space.
Up until we do the first 4.0.0 release I think that is fine. Afterwards
is when they might diverge in terms of version numbers but that is also
the point the projects are likely to separate so I think we are OK for now.

So, thoughts on proceeding along the lines set out in 2?

Sorry for all the chopping and changing. A lot of this Maven stuff is
new to me and I'm still trying to get my head around the original
intention of how stuff has been set up and the best way of doing things
moving forward.

Mark