Project Read Error In Maven
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the could not read maven project eclipse workings and policies of this site About Us Learn more about Stack could not read pom xml eclipse Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs
Maven Import Could Not Read Pom Xml
Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join
Artifact Descriptor Exception Failed To Read
them; it only takes a minute: Sign up Error opening Maven POM file dependency hierarchy in Eclipse - “Project read error” up vote 17 down vote favorite 5 When I open a POM file and click on the "Dependency Hierarchy" tab at the bottom, it gives me the error, "Project read error". It works with other projects in the org.eclipse.m2e.logback.appender unable to configure same workspace, just not with this one. Any ideas? EDIT In response to @Yhn's answer. Running the compile and package phases outside of Eclipse from the command-line work as expected. It compiles the application and builds the final WAR file. Eclipse is indeed pointing to the default location of the Maven settings.xml file, so it should be aware of the custom repositories that are defined in it (my company has its own Maven repository). I can open and edit the POM file from Eclipse, so it must have read/write permissions to the file. The project is not configured in Eclipse as a Maven project, so I cannot run the package phase from Eclipse (I can only run it from the command-line). I wonder if it has anything to do with the fact that I was having trouble building the project with Maven 3 because apparently some of the transitive dependencies are configured for Maven 1, which Maven 3 does not support (this is my theory anyway, based on some of the error messages). I can b
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies
Failed To Read Artifact Descriptor
of this site About Us Learn more about Stack Overflow the company maven eclipse plugin Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users maven tutorial Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a http://stackoverflow.com/questions/6427212/error-opening-maven-pom-file-dependency-hierarchy-in-eclipse-project-read-err minute: Sign up m2e gives inscrutable “project read error” up vote 10 down vote favorite 1 I just started to use m2e to try to build the sample travellog elastic beanstalk project. On the console I'm getting "[ERROR] Project read error". This also appears in red on the "Dependency Hierarchy" tab. What does this mean and how do I find out more http://stackoverflow.com/questions/10788023/m2e-gives-inscrutable-project-read-error details? Edit: Adding pom.xml
Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet Eclipse Newsletter Videos Participate Report a Bug Forums Mailing Lists Wiki IRC How to Contribute Working Groups Automotive Internet of Things LocationTech https://www.eclipse.org/forums/index.php/t/230370/ Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search Help Register Login Home Home» Archived» Maven Integration (M2E)» pom file shows missing artifact errors(My imported project seems to fine except eclipse (Indigo 3.7) is showing errors for missing artifacts ) Show: Today's Messages :: Show Polls :: Message Navigator pom file shows missing artifact could not errors [message #709403] Wed, 03 August 2011 22:12 Ara BulbulianMessages: 2Registered: August 2011 Junior Member using Indigo 3.7 (m2e integrated in) I would think this would be something simple to fix, but I can't seem to understand why Eclipse can't find the artifacts (all listed as missing) listed in my POM file. So I have a long list of errors in my Eclipse 'Problems' tab and my could not read POM.xml I was able to run mvn commands from the command line just fine and all the dependencies were created in my /.m2/repository/ dir. What is it that eclipse is using to try and validate my pom.xml? Very annoying that even the error messages are almost meaningless. All are 'Missing artifacts...' and are on line 1 of my pom.xml? Other developers using eclipse 3.4 and even 3.7 (Pulse build) don't seem to have my same issue. A few things I already checked: 1) eclipse -> preferences -> maven -> installation: Embedded 3.0.2 2) eclipse -> preferences -> maven -> user settings: local repository looks correct 3) eclipse -> preferences -> java -> build path -> classpath variables: M2_REPO which points to the same dir in my user settings (#2). 4) all the Maven Dependencies in my Java Build Path -> Libraries are happy (no errors) ** also when I click to view the pom.xml in eclipse it gives me a read error when clicking on the 'Dependency Hierarchy'. So whatever eclipse (plug-in is trying to parse the pom files seems to be having issues. Please response with anything that might help me solve t