Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8721649
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T07:15:20+00:00 2026-06-13T07:15:20+00:00

Using the maven-dotnet-plugin I am getting the error shown at the end of this

  • 0

Using the maven-dotnet-plugin I am getting the error shown at the end of this post.

The Jenkins workspace is set at C:\Jenkins

Does anyone know where or how to change the format of the pathnames for use in the dotnet plugin, or another way to get this to work?

The error I am getting is shown in detail below.

Parsing POMs
ERROR: Failed to parse POMs
java.io.FileNotFoundException: C:\Jenkins\ExternalFrame\au.com.bushlife.dotnet.revit:builder\builds\2012-09-20_17-10-03\log (The filename, directory name, or volume label syntax is incorrect)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at hudson.maven.MavenBuild$ProxyImpl2.<init>(MavenBuild.java:472)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:682)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
    at hudson.model.Run.execute(Run.java:1502)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:236)
FATAL: Failed to create a temporary file in C:\Jenkins\ExternalFrame\au.com.bushlife.dotnet.revit:builder\builds\2012-09-20_17-10-03
hudson.util.IOException2: Failed to create a temporary file in C:\Jenkins\ExternalFrame\au.com.bushlife.dotnet.revit:builder\builds\2012-09-20_17-10-03
    at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:67)
    at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:54)
    at hudson.XmlFile.write(XmlFile.java:174)
    at hudson.model.Run.save(Run.java:1638)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:991)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
    at hudson.model.Run.execute(Run.java:1527)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.IOException: The filename, directory name, or volume label syntax is incorrect
    at java.io.WinNTFileSystem.createFileExclusively(Native Method)
    at java.io.File.checkAndCreate(Unknown Source)
    at java.io.File.createTempFile(Unknown Source)
    at hudson.util.AtomicFileWriter.<init>(AtomicFileWriter.java:65)
    ... 9 more
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T07:15:21+00:00Added an answer on June 13, 2026 at 7:15 am

    The path being constructed is an invalid path due to the colons being placed in the path string. This is a plugin bug.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm using Maven with the Assembly plugin and would like to set the user
I am using maven-buildnumber-plugin version 1.0-beta-4. This works fine on a project checked out
im using maven-war-plugin and sometimes i get Unexpected end of ZLIB input stream when
using maven, what does the wtpversion mean in the Eclipse plugin?
I am using maven-shade-plugin for a simple maven project, the plugin successfully includes all
We're using Maven at work at quite regularly we get the error message The
I'm using Maven in the context of another build-tool (leiningen for Clojure, but this
I am using maven weblogic plugin 10.3.4. I have read the goal list of
I'm using maven-scm-plugin from within an own Maven Mojo via an injected ScmManager object
I'm using maven war plugin to build war package. Before package is build test

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.