Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] [ee4j-build] EE4J Parent pom.xml update
Hi,

On Fri, Nov 2, 2018 at 5:48 PM Romain Grécourt <romain.grecourt@xxxxxxxxx> wrote:
The outcome of that thread was a wiki page that Bill wrote to gather all the configuration required: https://wiki.eclipse.org/EE4J_Maven_Publishing

Yes, every project doing maven deployment will need to use that plugin so it makes sense to put that configuration in the ee4j parent pom.

That by itself sounds good to me, but I do feel reluctant updating all the projects I'm responsible for and having to beg and plea for PRs to them to be merged, and then when the parent pom has been updated with exactly that, remove it again from the poms and do the full round of begging en pleading again.

[small rant]
It might be helpful if the branch protected for EE4J branches, at least for selected people working on the jobs, is temporarily removed. I'm not sure how everyone else feels about this, but I'm not particularly happy with all the begging that needs to be done to get a PR merged. Dmitry for instance has been an extremely good help here, but I do feel somewhat troubled sending him mails all the time. Other committers in the projects likely don't even see the PR review requests. I often ask a review from the full group of 15 people (the max on GitHub), and just nobody responds.

Okay, enough ranting ;)

What would you suggest here? Update the poms first, or wait for that config to become available in the parent pom?

Thanks!

Kind regards,
Arjan






 

On Fri, Nov 2, 2018 at 8:18 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

This looks similar but not exactly the same as what Stuart found necessary to do for the Servlet API project:


The Servlet API project is not different from 90% of the other EE4J projects out there, so if Stuart found those changes necessary for Servlet to actually stage, and have that stage accessible, then shouldn't that be in the parent pom?

Compare the result of Stuart staging:


vs e.g. my co-worker Mark staging using the oss-release profile, but without the changes that Stuart did:


In Mark's staging you get a:

---
Access Denied

Please login before attempting further requests.
---

Kind regards,
Arjan




On Thu, Nov 1, 2018 at 4:05 PM Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Hi all

Romain fixed typo in staging profile in parent pom. It's released as 1.0.4 version so please update your poms.

"staging" profile will get usefull when working with new not yet released artifacts (e.g. jakarta.activation-api 1.2.1).


Tomas

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

Back to the top