If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

platform fails to build on fresh machine due to jBoss repository changes

RESOLVED FIXED in 1.0

Status

Mozilla QA
Case Conductor-Platform
--
major
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: carljm, Assigned: Vadim)

Tracking

unspecified

Details

(Reporter)

Description

6 years ago
On a fresh machine (with empty ~/.m2/repository) the platform is no longer able to build, because the repository previously located at http://repository.jboss.org/nexus no longer exists. It seems to have been split into a number of repositories (https://repository.jboss.org/nexus/index.html#view-repositories). It appears from searching at that site that the required versions of javax.jms (1.1) and quartz (1.6.0), at least, are supposed to now be found in the "jBoss Deprecated" repository at https://repository.jboss.org/nexus/content/repositories/deprecated/. The required version of jboss-common-core (2.2.14.GA) does not appear in search results there at all; I don't know where it can be found.

Either a TCM-specific public repo needs to be set up with the necessary versions of the needed jars, or the platform jar requirements need to be adjusted to match what is currently available in standard public repos.

Updated

6 years ago
Target Milestone: --- → 1.0
(Assignee)

Updated

6 years ago
Assignee: nobody → vadimk
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 1

6 years ago
This is not fixed with the latest code on github. The version for one dependency (jboss-common-core) was modified, but there are many more packages than that with problems. The first one to error out when running "mvn clean install" with no pre-existing ~/.m2/repository is quartz 1.6.0; last few lines of log pasted below.

Downloading: http://repository.jboss.com/maven2/quartz/quartz/1.6.0/quartz-1.6.0.jar
Downloading: http://repo1.maven.org/maven2//org/slf4j/slf4j-api/1.6.0/slf4j-api-1.6.0.jar
[WARNING] Unable to get resource 'quartz:quartz:jar:1.6.0' from repository repository.jboss.com (http://repository.jboss.com/maven2): Authorization failed: Access denied to: http://repository.jboss.com/maven2/quartz/quartz/1.6.0/quartz-1.6.0.jar
Downloading: http://repository.jboss.org/nexus/quartz/quartz/1.6.0/quartz-1.6.0.jar
        
325b downloaded  (quartz-1.6.0.jar)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'd8c63dbc5903ea967a6630f2572e243426a5dc7e'; remote = '<!DOCTYPE' - RETRYING
Downloading: http://repository.jboss.org/nexus/quartz/quartz/1.6.0/quartz-1.6.0.jar
325b downloaded  (quartz-1.6.0.jar)
       
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'd8c63dbc5903ea967a6630f2572e243426a5dc7e'; remote = '<!DOCTYPE' - IGNORING
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 10 source files to /home/carljm/projects/mozilla/tcmplatform/utest-domain-services/target/test-classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
error: error reading /home/carljm/.m2/repository/quartz/quartz/1.6.0/quartz-1.6.0.jar; error in opening zip file
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Updated

6 years ago
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
This is still not fixed.  One of the tests fails, which causes the build to fail:

Failed tests: 
  springTestContextPrepareTestInstance(com.utest.domain.service.TestCaseServiceIntegrationTest)

Tests run: 3, Failures: 1, Errors: 0, Skipped: 2



Vadim: have the requirements changed?  Should we not be using Maven 3 and JBoss 6?  Please advise.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 3

6 years ago
This error has nothing to do with the build process. It was some old test, which I removed, so everything should be fine now....

As far as upgrading to JBoss 6, I'm not even sure where this requirement came from... I know, that we're not upgrading anything here just yet....
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.