Hi all,

I am rebuilding an older version of CSpace for a client and have hit a
snag. The nightly.collectionspace.org artifactory repo is not available
right now. Any clue when it might get back up?

Thanks,

Jesse

Hi Jesse,
Can you give an example of an artifactory URL that is not working?

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of Jesse Martinez mjesse@gmail.com
Sent: Monday, November 30, 2020 3:53 PM
To: CollectionSpace Talk List
Subject: [Talk] nightly.collectionspace.org down

Hi all,

I am rebuilding an older version of CSpace for a client and have hit a snag. The nightly.collectionspace.orghttp://nightly.collectionspace.org artifactory repo is not available right now. Any clue when it might get back up?

Thanks,

Jesse

Hi Jesse,
I think this is one of those misleading maven error messages. When maven looks for an artifact, it looks in all of the repositories declared in pom.xml, in order, until it finds it. If it doesn't find it, the error message only mentions the last repository -- which is not necessarily where the artifact is -supposed- to be. (To be fair, maven doesn't know where the artifact is supposed to be, but we do). maven-surefire-plugin-2.13.pom should be on maven central. What might be happening is that maven central now requires https, and if you have an old pom.xml, it still has an http url. I did attempt to update pom.xml in all of the old release branches, so you may just need to pull. Or edit pom.xml, and change the maven central repository url to use https.

P.S. We did permanently eliminate the artifactory on nightly, but all the urls should now be redirecting to s3. I can tell that's working, because the bucket returns 403 instead of 404 when a file is not found, due to the way the permissions are set up.

Let me know if that helps.

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Jesse Martinez mjesse@gmail.com
Sent: Tuesday, December 1, 2020 10:11 AM
To: Ray Lee
Cc: CollectionSpace Talk List
Subject: Re: [Talk] nightly.collectionspace.org down

Hi Ray,

Here's the output I get from a build command:

[ERROR] Plugin org.apache.maven.plugins:maven-surefire-plugin:2.13 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-surefire-plugin:jar:2.13: Could not transfer artifact org.apache.maven.plugins:maven-surefire-plugin:pom:2.13 from/to collectionspace-remote-repos (http://nightly.collectionspace.org:8081/artifactory/remote-repos): Authorization failed for http://nightly.collectionspace.org:8081/artifactory/remote-repos/org/apache/maven/plugins/maven-surefire-plugin/2.13/maven-surefire-plugin-2.13.pom 403 Forbidden -> [Help 1]

Thanks,

Jesse

On Mon, Nov 30, 2020 at 4:27 PM Ray Lee <ray.lee@lyrasis.orgmailto:ray.lee@lyrasis.org> wrote:
Hi Jesse,
Can you give an example of an artifactory URL that is not working?

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.orgmailto:ray.lee@lyrasis.org

From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of Jesse Martinez <mjesse@gmail.commailto:mjesse@gmail.com>
Sent: Monday, November 30, 2020 3:53 PM
To: CollectionSpace Talk List
Subject: [Talk] nightly.collectionspace.orghttp://nightly.collectionspace.org down

Hi all,

I am rebuilding an older version of CSpace for a client and have hit a snag. The nightly.collectionspace.orghttp://nightly.collectionspace.orghttp://nightly.collectionspace.org artifactory repo is not available right now. Any clue when it might get back up?

Thanks,

Jesse

Following up on this, I just discovered that if you're building a sufficiently old version of CSpace that uses Java 1.7, you also need to add the argument -Dhttps.protocols=TLSv1.2 to your maven command, e.g.

mvn clean install -DskipTests -Dhttps.protocols=TLSv1.2

(This is in addition to ensuring the maven central repo urls in pom.xml are https instead of http).

Also, the pre-5.0 ui layer didn't explicitly declare any repositories, so if you have a sufficiently old version of maven, it may default to looking for artifacts on maven central using http. If that happens, you can explicitly declare the maven central repository in pom.xml, with the correct https url.

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of Ray Lee ray.lee@lyrasis.org
Sent: Wednesday, December 2, 2020 12:14 AM
To: Jesse Martinez
Cc: CollectionSpace Talk List
Subject: Re: [Talk] nightly.collectionspace.org down

Hi Jesse,
I think this is one of those misleading maven error messages. When maven looks for an artifact, it looks in all of the repositories declared in pom.xml, in order, until it finds it. If it doesn't find it, the error message only mentions the last repository -- which is not necessarily where the artifact is -supposed- to be. (To be fair, maven doesn't know where the artifact is supposed to be, but we do). maven-surefire-plugin-2.13.pom should be on maven central. What might be happening is that maven central now requires https, and if you have an old pom.xml, it still has an http url. I did attempt to update pom.xml in all of the old release branches, so you may just need to pull. Or edit pom.xml, and change the maven central repository url to use https.

P.S. We did permanently eliminate the artifactory on nightly, but all the urls should now be redirecting to s3. I can tell that's working, because the bucket returns 403 instead of 404 when a file is not found, due to the way the permissions are set up.

Let me know if that helps.

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Jesse Martinez mjesse@gmail.com
Sent: Tuesday, December 1, 2020 10:11 AM
To: Ray Lee
Cc: CollectionSpace Talk List
Subject: Re: [Talk] nightly.collectionspace.org down

Hi Ray,

Here's the output I get from a build command:

[ERROR] Plugin org.apache.maven.plugins:maven-surefire-plugin:2.13 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-surefire-plugin:jar:2.13: Could not transfer artifact org.apache.maven.plugins:maven-surefire-plugin:pom:2.13 from/to collectionspace-remote-repos (http://nightly.collectionspace.org:8081/artifactory/remote-repos): Authorization failed for http://nightly.collectionspace.org:8081/artifactory/remote-repos/org/apache/maven/plugins/maven-surefire-plugin/2.13/maven-surefire-plugin-2.13.pom 403 Forbidden -> [Help 1]

Thanks,

Jesse

On Mon, Nov 30, 2020 at 4:27 PM Ray Lee <ray.lee@lyrasis.orgmailto:ray.lee@lyrasis.org> wrote:
Hi Jesse,
Can you give an example of an artifactory URL that is not working?

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.orgmailto:ray.lee@lyrasis.org

From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of Jesse Martinez <mjesse@gmail.commailto:mjesse@gmail.com>
Sent: Monday, November 30, 2020 3:53 PM
To: CollectionSpace Talk List
Subject: [Talk] nightly.collectionspace.orghttp://nightly.collectionspace.org down

Hi all,

I am rebuilding an older version of CSpace for a client and have hit a snag. The nightly.collectionspace.orghttp://nightly.collectionspace.orghttp://nightly.collectionspace.org artifactory repo is not available right now. Any clue when it might get back up?

Thanks,

Jesse

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org