b.lavit

Hi,

All our AM customers have a read access on the am-external git repo.

If you have a valid customer/partner account, you should be able to clone this repo.

If you can share your userID, I can double check the permissions.

Thanks,
Bruno (release manager)

Hi Arshad,

I did a quick check in Artifactory (our Maven repository manager) and your user (aazeem100) has a read access on the private-releases repo.

I’ve uploaded a template for the settings.xml file here:
http://maven.forgerock.org/repo/private-releases/settings.xml

Can you try to download this file in your ~/.m2 folder and make a new…[Read more]

@csanchezaustin Yes sorry I didn’t mention I’ve used an empty Maven cache to test the build:
mvn -U -Dmaven.repo.local=/tmp/.m2 clean verify

Because I’ve uploaded a new release of forgerock-launcher 1.2.0, you have to remove this component from your cache.

@csanchezaustin @sarankon-hir The OpenIDM build is now OK. I pushed a fix for the forgerock-launcher component in our Artifactory releases repo.

Please confirm you are now able to build OpenIDM 4 on your machines.

Hi,

We found an issue with the forgerock-launcher component.
The version 1.2.0 has been released with a SNAPSHOT dependency (org.forgerock.commons:forgerock-bom:pom:1.0.0-SNAPSHOT).
As our Maven snapshots repo is now private, it explains why you are not able to build OpenIDM 4 from the source code.
I’m now working with the OpenIDM development…[Read more]

Hi Anant,

I confirm we had some issues with our production Artifactory instance on Friday 4th November (between 5pm and 10pm UK time).

It should be now OK.

Thanks,
Bruno (release engineer at ForgeRock)

Thanks Peter, it’s really useful!

In your case, your Backstage userID is your email address.

But for most of our users (99,9%), it’s not the case: their userID are classic user login (not email address).

That’s why we said that in our guide to get the source code.

I’ll try to improve the guide for the special cases.

Cheers,
Bruno

Hi Robert,

I did a quick check in the Stash user directory and your userID is: [email protected]

Can you try to login with this userID?

The password should be the same than your Backstage account.

Cheers,
Bruno (Release Engineer at Forgerock)

You’re welcome :)

Hi,

If you want to build OpenDJ 3.0.0, you have to build the Git tag –> 3.0.0
The release/3.0.0 branch is a temporary branch we used to manage the release.
The Maven release plugin moved this branch to the next development version –> 3.0.1-SNAPSHOT.
FYI, we will delete this branch soon.

I hope it helps.

Cheers,
Bruno, Release engineer at…[Read more]

Hi Cyril,

I did some updates in the Stash permissions and you should be able to view the opendj-sdk repo.

Please confirm it’s working.

Cheers,
Bruno

Hi Cyril,

These OpenDJ projects moved into a new component: OpenDJ-SDK

You can find the sources here:
https://stash.forgerock.org/projects/OPENDJ/repos/opendj-sdk/browse

Cheers,
Bruno

Hi psvoa,
I did a quick check in our user directory and you have the relevant permissions (read access on all the public repositories).
When you are trying to log into Stash, are using your Backstage userID (psova)?
Please confirm that you’re able to login with this userID.
Cheers,
Bruno (release engineer at Forgerock)

A quick update on Hadi’s problem.

He was using the wrong user_id (his email) instead of his Backstage account (hahmadi).

Stash is using the same users directory than Backstage.

Thanks,
Bruno

Hi Hadi,

I’ve checked your Stash profile and you are in the relevant LDAP groups (all-users-virtual, customers, partners, …).

Can you send me your error message?

Thanks,
Bruno (release engineer at ForgeRock)