0

WSO2 has given a latest fix for Governance Registry5.3.0(Governance REST API Update issue). While building a code for applying a fix the below error is thrown.

Error when building code using Maven.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project  org.wso2.carbon.governance.api: Compilation failure: Compilation failure:
[ERROR] \Users\a596500\Downloads\carbon-governance-master\components\governance\org.wso2.carbon.governance.api\src\main\java\org\wso2\carbon\governance\api\util\CheckpointTimeUtils.java:[22,30] error: package org.apache.commons.lang does not exist
[ERROR] Failed to execute goal on project org.wso2.carbon.governance.api: Could not resolve dependencies for projectorg.wso2.carbon.governance:org.wso2.carbon.governance.api:bundle:4.7.2-SNAPSHOT: The following artifacts could not beresolved: org.wso2.carbon.registry:org.wso2.carbon.registry.extensions:jar:4.6.1-SNAPSHOT, org.wso2.carbon.registry:org.wso2.carbon.registry.common:jar:4.6.1-SNAPSHOT, org.wso2.carbon.registry:org.wso2.carbon.registry.admin.api:jar:4.6.1-SNAPSHOT
org.wso2.carbon.registry:org.wso2.carbon.registry.indexing:jar:4.6.1-SNAPSHOT: Could not find artifact org.wso2.carbon.registry:org.wso2.carbon.registry.extensions:jar:4.6.1-SNAPSHOT in nexuspro-level0 (https://repo.fmr.com/content/groups/level0/)
Community
  • 1
  • 1
Mathan Prasath
  • 27
  • 5
  • Are you building the entire repository? If not, please do. – Bee Sep 28 '16 at 05:28
  • I'm not building the entire repository. In fact I have reported a bug in WSo2 GREG and Chandana provided a fix lastweek https://github.com/wso2/carbon-governance hence trying to build only that. But today when I have visited the Master branch in the above specified URL he has reverted the changes he has done, I don't know why ? Could you please confirm asap. – Mathan Prasath Sep 28 '16 at 05:39
  • Please raise your question in the original question to which Chandana replied. – Bee Sep 29 '16 at 11:58

1 Answers1

2

Please clone below repos, Move to the relevant tag and run an mvn clean install -e on each and every repo accordingly.

To apply the fix and generate the latest jar you have to apply the fix manually to 5.3.0 tag from your local machine and build the source.

Community
  • 1
  • 1
tk_
  • 16,415
  • 8
  • 80
  • 90