[jira] Commented: (MIDEA-102) Module filepath is generated incorrectly for sibling parent

["gotama (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131030#action_131030 ] 

gotama commented on MIDEA-102:
------------------------------


What is the status of this issue? 

I'm willing to forgo the whole implementation style argument for simply getting "A" fixed version of 2.2 out the door.

The current SNAPSHOT works, so I vote for releasing it, then later on revisiting the 3 different ways the paths can be corrected. The important thing is that it is fixed.

In the mean time, there are people out there trying to use Maven for the first time, and they will not be impressed when 'mvn idea:idea' does not work. This is one of the cool selling points of Maven to a team of developers and its been busted for a year.

Release 2.2...

Thanks.


> Module filepath is generated incorrectly for sibling parent
> -----------------------------------------------------------
>
>                 Key: MIDEA-102
>                 URL: http://jira.codehaus.org/browse/MIDEA-102
>             Project: Maven 2.x IDEA Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: $ mvn -v
> Maven version: 2.0.7
> Java version: 1.5.0_11
> OS name: "windows xp" version: "5.1" arch: "x86"
> cygwin
>            Reporter: Joern Huxhorn
>            Assignee: Dennis Lundberg
>             Fix For: 2.2
>
>         Attachments: maven-idea-plugin-MIDEA-102.patch
>
>
> I have a multi-module mvn project.
> When I do an mvn idea:clean idea:idea, the following ProjectModuleManager snippet in the top level .ipr is generated:
> <component name="ProjectModuleManager"> 
>     <modules> 
>       <!-- module filepath="$$PROJECT_DIR$$/${pom.artifactId}.iml"/ -->  
>       <module filepath="$PROJECT_DIR$/gateway.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml"/>
>       <module filepath="$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml"/>
>     </modules> 
>   </component>
> The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
> But this path is being appended in a hard-coded fashion after the $PROJECT_DIR entry.
> The symptom in Intellij is the following error message:
> Cannot load module: File C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not exist
> Would you like to remove the module from the project?
> The workaround is to delete the extra appended file path from each module entry in the above mentioned snippet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira