On 30/10/18 21:36, Romain Grécourt wrote:
> There are 2 different "deployment" repositories: one for SNAPSHOT
> version and one for release version (i.e non SNAPSHOT version).
> See the EE4J parent
> pom: http://repo1.maven.org/maven2/org/eclipse/ee4j/project/1.0.2/project-1.0.2.pom
>
> In short staging repositories are for release version only.
>
> SNAPSHOT artifacts are deployed against and available from this
> repository: https://oss.sonatype.org/content/repositories/snapshots/
Just to check I am understanding this correctly:
1. I haven't messed up because we want what will hopefully be the 3.0.2
release here:
https://oss.sonatype.org/content/groups/staging/jakarta/el/jakarta.el-api/
and that is what we have currently got.
2. If we found an issue with that artefact we'd drop the repository, fix
the issue and follow the same process we used to get to this point?
You can.
If the intent is to re-release the same version be aware of the side effects: If anybody has pulled the "stale" artifacts, they will need to prune their local repository.
Thanks,
Mark
>
> On Tue, Oct 30, 2018 at 2:25 PM Mark Thomas <markt@xxxxxxxxxx
> <mailto:markt@xxxxxxxxxx>> wrote:
>
> Hi,
>
> I'm in need of some help/advice.
>
> I've just managed to get EL 3.0.2 visible here:
> https://oss.sonatype.org/content/groups/staging/jakarta/el/jakarta.el-api/
>
> However, it doesn't have the snapshot marker in the version. What have I
> done wrong and how do I fix it?
>
> Mark
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx <mailto: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
>
