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,

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

Back to the top