Posts made by jndornbach_8182

Thank you very much! I'm curious about the release...

Hello Alana.

I just sent you an email with the requested Fiddler session recording file as well as the relevant excerpt of the console log of the run of mvn deploy.
I reproduced and captured the error with ProGet version 5.3.32 (Build 11) in contrast to the version I used in my initial thread posting.

The failing PUT request to http://127.0.0.1:8090/maven2/maven-feed/info/dornbach/testproject/maven-metadata.xml has the following content:

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>info.dornbach</groupId>
  <artifactId>testproject</artifactId>
  <versioning>
    <latest>1.0.0</latest>
    <release>1.0.0</release>
    <versions>
      <version>1.0.0</version>
    </versions>
    <lastUpdated>20210717092715</lastUpdated>
  </versioning>
</metadata>

Thank you!

@atripp Thank you very much! I upgraded to ProGet version 5.3.32 (Build 11) and the error is gone.

Hi,

I run a local ProGet installation (5.3.29 (Build 19)) with a Maven feed. When I click on the "Dependencies" button in the artifact's detail view of a deployed Maven artifact in the web UI, I get the following error page if the artifact uses Spring Boot:

In ProGet's logs, the following error message is logged:

An error occurred in the web application: Value cannot be null. (Parameter 'version')

with stack trace:

URL: http://proget.url/feeds/maven-releases/info.dornbach/projectname/1.0.0/dependencies
Referrer: https://proget.url/feeds/maven-releases/info.dornbach/projectname/1.0.0
User: dornbach
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15
Stack trace: at Inedo.ProGet.Feeds.Maven.MavenVersion.Parse(String version) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGetCoreEx\Feeds\Maven\MavenVersion.cs:line 56
at Inedo.ProGet.Feeds.Maven.CommonMavenPackageInfo.Dependency.get_LinkedPackage() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGetCoreEx\Feeds\Maven\CommonMavenPackageInfo.cs:line 111
at Inedo.ProGet.WebApplication.Pages.Packages.PackageDependenciesPage.AddContentControlsAsync(ContentContainer content) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGet.WebApplication\Pages\Packages\PackageDependenciesPage.cs:line 43
at Inedo.ProGet.WebApplication.Pages.Packages.PackagePageBase.CreateChildControlsAsync() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGet.WebApplication\Pages\Packages\PackagePageBase.cs:line 115
at Inedo.ProGet.WebApplication.Pages.ProGetSimplePageBase.InitializeAsync() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGet.WebApplication\Pages\ProGetSimplePageBase.cs:line 76
at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync()
at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync(HttpContext context)
at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)

I guess that this error may be caused by the (intentionally) missing version element in the project's pom.xml because its dependency versions are managed by the parent pom's dependencyManagement section (e.g. of Spring Boot).

Is there a way that ProGet can cope with "parent-managed" dependency versions in future or, at least, does not throw this error?

I run a local ProGet installation (5.3.29 (Build 19)) with a Maven feed. When I try to deploy via Maven (mvn deploy), the transfer of maven-metadata.xml fails with 500 Internal Server Error:

...
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ projectname ---
Uploading to maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/1.0.0/projectname-1.0.0.jar
Uploaded to maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/1.0.0/projectname-1.0.0.jar (17 kB at 24 kB/s)
Uploading to maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/1.0.0/projectname-1.0.0.pom
Uploaded to maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/1.0.0/projectname-1.0.0.pom (4.4 kB at 13 kB/s)
Downloading from maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/maven-metadata.xml
Downloaded from maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/maven-metadata.xml (273 B at 2.3 kB/s)
Uploading to maven-releases: https://proget.url/maven2/maven-releases/info/dornbach/projectname/maven-metadata.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  4.493 s
[INFO] Finished at: 2021-05-29T12:20:08+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project projectname: Failed to deploy metadata: Could not transfer metadata info.dornbach: projectname/maven-metadata.xml from/to maven-releases (https://proget.url/maven2/maven-releases/): transfer failed for https://proget.url/maven2/maven-releases/info/dornbach/projectname/maven-metadata.xml, status: 500 Internal Server Error

In ProGet's Diagnostic Center, the following corresponding error message is logged:

An error occurred processing a PUT request to http://proget.url/maven2/maven-releases/info/dornbach/projectname/maven-metadata.xml: Root element is missing.

The stack trace is as follows:

System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Load(Stream stream, LoadOptions options)
at System.Xml.Linq.XDocument.Load(Stream stream)
at Inedo.ProGet.WebApplication.FeedEndpoints.Maven.MavenFeedHandler.ProcessRequestAsync(HttpContext context, MavenFeed feed, String relativeUrl) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGet.WebApplication\FeedEndpoints\Maven\MavenFeedHandler.cs:line 173
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.ProcessRequestAsync(HttpContext context) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E131122\Src\ProGet.WebApplication\FeedEndpoints\FeedEndpointHandler.cs:line 121

The downloaded maven-metadata.xml is:

<metadata>
  <groupId>info.dornbach</groupId>
    <artifactId>projectname</artifactId>
    <versioning>
      <latest>1.0.0</latest>
      <versions>
        <version>1.0.0</version>
      </versions>
    <lastUpdated>20210529102007</lastUpdated>
  </versioning>
</metadata>

I am using Maven 3.8.1:

$ mvn -version
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /usr/local/Cellar/maven/3.8.1/libexec
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"

After the Error occurred and the Maven deploy step failed, the package is available in the Web-UI and for download.