| Priority |
Normal |
| Type | Bug |
| State | Fixed |
| Assignee | Anton Makeev |
| Subsystem | Maven Integration |
| Affected versions |
No affected versions
|
| Fixed in |
No fix versions
|
| Fixed in build |
Next build |
| Build |
7027
|
| Fixed in build |
7589
|
| Severity |
0
|
IDEA-39513 |
Maven Import does not find projects |
|
maven_bug.zip
(6 KB)
|
Nice job, and good customer support.
What I understand from here is either stick to version 6.0 or to Eclipse 3.3, am I correct?
I have consulted with the author of Maven (Jason van Zyl). In fact Jason is sitting right beside me as I am typing this.
So here is what he said:
The Maven Embedder code included into IDEA integration does not support references to environment variables (${env.*), so your pom.xml files cannot even be validated.
The good news is that Jason is going to fix that in the Embedder, so we will have it fixed in the release version.
If it needed, I can publish this script.
I am finding that if a profiles.xml descriptor is present at all, the Maven Embedder chokes and IDEA fails to discover the Maven project. Since the profiles.xml cannot be used (I move it to the side), several properties don't get assigned, which then causes the first problem, unresolved variables. Unresolved variables also cause the Maven Embedder to choke, and IDEA fails to find the projects.
So what am I doing?
I have a profiles.xml with <activeProfile> declarations
I have matching profiles that set properties, such as <jdbc.artifactId>mysql-connector-java</jdbc.artifactId>
I have dependencies that use these values, such as <artifactId>${jdbc.artifactId}</artifactId>
This is used all over the place in the Appfuse project, so it is pretty important to get fixed if you want to support those users, as well as others that have picked up on that usage of Maven 2.
Sadly, this all worked in 7M2
you can use scripts which I has published in IDEA-40982
As for your pom files - after fixing several issues with <parent> properties (i've repointed from global_build/dev/pom.xml to global_build/pom.xml and have added relativePath to parent into servers/pom.xml) it was correctly imported.