[ARCH-4] Issues on the "Developing Apps on the OpenDaylight controller" Page Created: 10/Feb/20  Updated: 03/Apr/20

Status: To Do
Project: archetypes
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: Jahveen Davis Assignee: Jamo Luhrsen
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-37-generic x86_64)

Apache Maven 3.6.0

Java version: 1.8.0_231, vendor: Oracle Corporation, runtime: /opt/jdk/jdk1.8.0_231/jre

Attachments: Text File archetype_build_success.txt     Text File example_error.txt     Text File missing_repositories.txt    

 Description   

version: Sodium
page: developer-guide/developing-apps-on-the-opendaylight-controller

 

When following steps of "Building an example module", step 4 is the instruction "mvn clean install". Upon running this, the attached file "example_error.txt" shows that there is a failure. The attachment "missing_repositories.txt" shows the files that were not downloaded into the ~/.m2/repositories/ folder.

 

Secondly, when this process has worked in the past, the odl-mdsal-apidocs feature is not installed, so step 1 of "Using the API Explorer through HTTP" cannot work.

 Comments   
Comment by Jahveen Davis [ 11/Feb/20 ]

I was able to get around the original issue by updating the pom.xml file and making the following change in order to resolve a "HTTPS Required" error detailed in "https://www.mail-archive.com/search?l=infrastructure@lists.opendaylight.org&q=subject:%22Re%5C%3A+%5C%5BOpenDaylight+Infrastructure%5C%5D+SFT+et+al.+failing+across+the+board%22&o=newest&f=1"

 

<parent>
<groupId>org.opendaylight.odlparent</groupId>
<artifactId>single-feature-parent</artifactId>
<version>5.0.2</version>
<relativePath/>
</parent>

 

to

 

<parent>
<groupId>org.opendaylight.odlparent</groupId>
<artifactId>single-feature-parent</artifactId>
<version>5.0.5</version>
<relativePath/>
</parent>

 

However, doing the same change in other feature folders did not fully resolve the issue, since changing the version has far-reaching implications that I cannot resolve with this change alone.

Comment by Jahveen Davis [ 25/Feb/20 ]

any update on this issue?

Comment by David Baugher [ 02/Apr/20 ]

This looks more like an error to the software, not necessarily the documentation

Comment by Jamo Luhrsen [ 03/Apr/20 ]

I tried to reproduce this by following the guide, but my build was successful. I attached my console log during that
process. Is there anything different you can tell that I am doing? Can you check again if you have the same problem?

Generated at Wed Feb 07 19:09:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.