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

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


I am running XP, Maven 2.0.8, Maven IDEA plugin 2.1 and Cygwin. When I issue 
'mvn idea:idea' on the XP command line my IDEA project file is fine. When I 
issue the same command in Cygwin, the paths are incorrect.

Using the 2.2-SNAPSHOT it works fine, except for the above noted conditions 
where the parent and module dirs are at the same level. This is a different bug.

This issue is working on over 8 months without a release, yet there is a fix 
for one of the show stopping bugs which prevents you from using the plugin. 2.2 
should be released as is now and a new fresh jira issue should be created to 
address the bug about the paths being incorrect for when the parents and 
modules are at the same level. This plugin is broken without releasing 2.2.

> CLONE -still broken - Module filepath is generated incorrectly
> --------------------------------------------------------------
>
>                 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

        

Reply via email to