Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mvn clean verify fails when adding target-platform #24

Open
Maryam81609 opened this issue Jun 20, 2019 · 3 comments
Open

mvn clean verify fails when adding target-platform #24

Maryam81609 opened this issue Jun 20, 2019 · 3 comments

Comments

@Maryam81609
Copy link

Hi,

Running mvn clean verify I get the following error:

[INFO] Adding repository file:agree/repository/target/repository/
[ERROR] Failed to resolve target definition /home/maryam/formal-methods-workbench/tools/target-platform/com.collins.fmw.target.target: Failed to load p2 metadata repository from location file:agree/repository/target/repository/: URI is not hierarchical
.
.
.
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException

Thanks,
Maryam

@kfhoech
Copy link
Contributor

kfhoech commented Jul 17, 2019

Hopefully this is a temporary problem. The intent is that the AGREE and Resolute plugins will migrate to separate repositories and separate CI/CD builds. However, a prerequisite for this is having a location to host the update site for these plugins. Approval and funding for that has apparently been caught up in some delay.

@Maryam81609
Copy link
Author

Thanks for the response!
Do you have any idea how long it will take to be solved?

@dvanbrug
Copy link

This seems like it might be an error with the documentation.

Instead of following the README which just says to run mvn clean verify from within tools/, I instead used the following steps which I found in .tarvis.yml. These steps perform an individual build in both agree/ and resolute/ folders before I could complete the tools build:

  - pushd tools/agree
  - mvn clean verify
  - popd
  - pushd tools/resolute
  - mvn clean verify
  - popd

The URI error might just be because the repository directory does not exist under agree and resolute until you've performed the individual builds.

** I will also note that I had to change repository locations for the py4j packages to not use https but instead just http in order to get the builds to complete. However, that is unrelated to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants