Re: [ee4j-build] how to access staged artifacts?

[Romain Grécourt <romain.grecourt@xxxxxxxxx>]

You can pull artifacts from closed staging repositories using the staging group: https://oss.sonatype.org/content/groups/staging/

Note that the repository has to be closed (cf the other thread where we discussed that)

If you want to pull the staged artifacts from a Maven project that inherits the ee4j parent pom, you can simply use the "staging" profile.

I.e add "-Pstaging" to your maven command line.

You could also simply declare the staging group as a repository in your project, to avoid requiring a profile.

On Tue, Oct 30, 2018 at 12:24 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

I believe I've successfully deployed final artifacts to a staging repository.
How do I find that staging repository so I can download the artifacts manually
for testing?  If I use the URL that the artifacts are published to, it says I
need to login to oss.sonatype.org.  Is there no public access to these staged
artifacts?

For example, it's uploaded to:
https://oss.sonatype.org/service/local/staging/deploy/maven2/jakarta/activation/jakarta.activation-api/1.2.1/jakarta.activation-api-1.2.1.jar

Since the TCK doesn't run in Eclipse Jenkins yet, I want to download the
artifact and run the TCK locally.

Also, I believe there's some way to set up Jenkins so that artifacts from
the last build are accessible at a fixed URL.  How do I do that?
_______________________________________________
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