#7860 - Maven project import problems.

I am using 7.0.4 build #7860 on Mac OS X 10.5.3 and am having problems with importing a large multi-module Maven project. When I use Create New Project, import project from external model, Maven, the project does get created but some problems occur. Our parent pom was recently updated with some dependency management options.

1. The only facet detected is WEB on the module that produces a war.
2. The Spring, Hibernate, and JPA facets are not detected on the various modules where they used to be.
3. Even though the maven projects tab appears, I've lost the ability to configure a RUN option for Maven. As well as the ability to run a maven goal before executing a unit test.

Like I said, this problem has occurred after the parent pom was updated with dependency management.

Any suggestions?

5 comments
Comment actions Permalink

Maven plugin directly supports only WAR, JAR, EAR and GWT facets.
Facets such as Hibernate, JPA are not imported from maven. Though, they should be automatically detected on project opening.

0
Comment actions Permalink

exactly, I realize that the JPA, Hibernate, and Spring facets are not specified in the Maven pom.xml. What I was saying is that they are no longer detected when the project is opened.

I've since upgraded to the latest build, #7878, and now have additional problems. Upon import, some projects are ending up with no dependencies!

I will try to package up our pom's and file a jira issue.

0
Comment actions Permalink

Perhaps facet auto-detection is disabled in your project. Unfortunately the only way to enable auto-detection again in IDEA 7.0.x is manual editing of
ipr-file. Find the following tag in ipr-file

... and see if it contains subtags like ]]>.

exactly, I realize that the JPA, Hibernate, and Spring facets are not specified in the Maven pom.xml. What I was saying is that they are no longer detected when the project is opened.

I've since upgraded to the latest build, #7878, and now have additional problems. Upon import, some projects are ending up with no dependencies!

I will try to package up our pom's and file a jira issue.



--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Checked the ipr file and it does have this

]]>

So do I simply remove this component completely or partially?

0
Comment actions Permalink

According to this file auto-detection is disabled only for Web facets in module squid so it fails to explain the fact that spring and hibernate facets
aren't detected. Are spring and hibernate config files located under content roots of your module?

Checked the ipr file and it does have this

<component name="FacetAutodetectingManager">
<autodetection-disabled>
<facet-type id="web">
<modules>
<module name="squid" />
</modules>
</facet-type>
</autodetection-disabled>
</component>

So do I simply remove this component completely or partially?



--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.