Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] No Jetty Bom [was Re: Jetty 9.4.6 Released!]


On 8 June 2017 at 16:00, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
On Thu, Jun 8, 2017 at 4:13 AM, Olivier Lamy <olamy@xxxxxxxxxxx> wrote:


On Thu, Jun 8, 2017 at 6:11 PM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
I tried but failed to get the jetty-bom released for 9.4.6    
I got it to oss.sonatype, but it failed a rule on closing the staged repo.

which rule?

Cannot release the same version again.
If any artifact in your staging repository already exists on central, then that entire staging repository is invalid.


It's not being released again.  jetty-bom for 9.4.6 has never been released.

 

But why wasn't it updated?

 
That's the reason, since the jetty-bom is no longer participating in the hierarchy of the parent, its isolated, considered a separate release from the rest of the project.
The jetty-bom itself does not participate in the maven release process properly.

However, the other artifacts, that are part of the hierarchy are updated (example, the dependencies in the jetty-bom)


It simply cannot be part of the release and be unconnected from the hierarchy at the same time.

There are only 2 options left

1) jetty-bom as a standalone project with its own release

2) Generate the jetty-bom during the build and perform a pom artifact swap during install/deploy (like you can with the shade plugins)


I've seen other projects that have a sub-module that does not list a parent module.  

I still think something strange is going on here....   

I'll do some test release prepares in the next few days to work it out.

cheers
 


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users



--

Back to the top