- This topic has 2 replies, 1 voice, and was last updated 15 years, 7 months ago by joehuangathome.
-
AuthorPosts
-
joehuangathomeMemberI specified POM_VERSION thru MyEclipse Run Configurations and specify the task to mvn install:install but failed to build a local artifact.
Error message is as follows:
[ERROR] Failed to read settings from: C:\Documents and Settings\Joseph.Huang\.m2\repository. Throwin
g IOException…
[ERROR] Failed to read settings from: C:\Documents and Settings\Joseph.Huang\.m2\repository. Throwin
g IOException…
[INFO] Scanning for projects…
[INFO] ————————————————————————
[INFO] Building ClaimsServices
[INFO]
[INFO] Id: com.viant.ViantCommon:ClaimsServices:jar:72.2.0.0
[INFO] task-segment: [org.apache.maven.plugins:maven-install-plugin:2.2:install, org.apache.maven.pl
ugins:maven-compiler-plugin:2.0.2:compile]
[INFO] ————————————————————————
[INFO] [install:install]
[ERROR]The following mojo encountered an error while executing:
Group-Id: org.apache.maven.plugins
Artifact-Id: maven-install-plugin
Version: 2.2
Mojo: install
brought in via: Direct invocationWhile building project:
Group-Id: com.viant.ViantCommon
Artifact-Id: ClaimsServices
Version: 72.2.0.0
From file: Q:\joseph.huang_Rel-72.2.0.0_sys04_2_int\ViantCommon\ClaimsServices\pom.xml
Reason: The packaging for this project did not assign a file to the build artifactPlease help, Thanks!
joehuangathomeMemberI made a dummy settings.xml file and the “Failed to read settings from” error messages are gone. But the last error message(about packaging) still remains.
joehuangathomeMemberI exhausted my research on “The packaging for this project did not assign a file to the build artifact ” error message on google and did not find any constructive tips or answers. My “mvn clean install -DPOM_VERSION=xxx -Dmaven.test.skip=true” worked perfectly in DOS command line. It just failed on MyEclipse using the Run Configuration. Any hints on this issue will be greatly appreciated!!
-
AuthorPosts