[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-07 Thread gotama (JIRA)

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

gotama commented on MIDEA-102:
--

http://cygwin.com/setup.exe 

... just click through 'next' on everything and get the basic install. quick 
easy setup... beats the windows prompt for those on the corporate XP system! :)




 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-06 Thread gotama (JIRA)

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

gotama commented on MIDEA-102:
--


Actually, I just tested Roman's code above - adding it to the latest 
2.2-SNAPSHOT and the paths are correct for an idea project with the parent and 
modules at the same level. The modules paths are correctly relative using ../.

Someone should throw that code in there, close this out and release 2.2. WFM.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-06 Thread Geoffrey De Smet (JIRA)

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

Geoffrey De Smet commented on MIDEA-102:


bq. Someone should throw that code in there, close this out and release 2.2.

I couldn't agree more :)

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-06 Thread gotama (JIRA)

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

gotama commented on MIDEA-102:
--


I would add it - but I'm new to this project so I don't know how to get 
permissions to check in code and what the official release process is. How do 
you become a committer?

Also, someone should check out the ClassWorlds dependency for the tests. The 
tests fail because they are missing the ClassWorlds dependency.

  dependency
groupIdclassworlds/groupId
artifactIdclassworlds/artifactId
version1.1/version
  scopetest/scope
  /dependency  


 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-06 Thread Dennis Lundberg (JIRA)

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

Dennis Lundberg commented on MIDEA-102:
---

Thanks for trying the patch. As I don't have a cygwin environment I have not 
been able to verify the patch. I'll have a look at the patch.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-03-05 Thread gotama (JIRA)

[ 
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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2008-02-02 Thread Daniel Frey (JIRA)

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

Daniel Frey commented on MIDEA-102:
---

Hi there

I just tested it with the 2.2-SNAPSHOT and got a wrong result! My project 
structure is:

ch.ki.ras/
ch.ki.ras.monitor/
ch.ki.ras.om/

where the first directory contains the master POM. What I get in the project 
file ch.ki.ras/ch.ki.ras.ipr is 

module filepath=$PROJECT_DIR$/ch.ki.ras.iml/
module filepath=$PROJECT_DIR$/monitor/ch.ki.ras.monitor.iml/
module filepath=$PROJECT_DIR$/om/ch.ki.ras.om.iml/

So not only the path is not relative to the main POM, but also the path 
information is trucated. Instead it should be 

module filepath=$PROJECT_DIR$/ch.ki.ras.iml/
module filepath=$PROJECT_DIR$/../ch.ki.ras.monitor/ch.ki.ras.monitor.iml/
module filepath=$PROJECT_DIR$/../ch.ki.ras.om/ch.ki.ras.om.iml/

Would be wunderful to get a new SNAPSHOT soon!

Thanks
Daniel Frey

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-12-01 Thread Roman Platonov (JIRA)

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

Roman Platonov commented on MIDEA-102:
--

Hello!
My fix is more simple, but it's works...

class AbstractIdeaMojo:

protected String toRelative( File basedir, String absolutePath )
{
String relative = null;
String convertedBasedirAbsolutePath = convertDriveLetter( 
basedir.getAbsolutePath() );
String convertedAbsolutePath = convertDriveLetter( absolutePath );

String fileSeparator = System.getProperty(file.separator);
String upPrefix = ;
while (convertedBasedirAbsolutePath.indexOf(fileSeparator)  0) {
if (convertedAbsolutePath.startsWith(convertedBasedirAbsolutePath)
 convertedAbsolutePath.length()  
convertedBasedirAbsolutePath.length()) {
relative = upPrefix + 
convertedAbsolutePath.substring(convertedBasedirAbsolutePath.length() + 1);
break;
} else {
convertedBasedirAbsolutePath = 
convertedBasedirAbsolutePath.substring(0,

convertedBasedirAbsolutePath.lastIndexOf(fileSeparator));
upPrefix += ../;
}
}
if (relative == null) {
relative = convertedAbsolutePath;
}

relative = StringUtils.replace( relative, \\, / );

if ( getLog().isDebugEnabled() )
{
getLog().debug( toRelative( + basedir + ,  + absolutePath + ) 
=  + relative );
}

return relative;
}


 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-09-24 Thread Geoffrey De Smet (JIRA)

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

Geoffrey De Smet commented on MIDEA-102:


Confirming it doesn't work for idea 2.0 or 2.1. It's maven 2.0.7 and win xp 
combination that is breaking.

Workaround
==

Make sure you still have maven 2.0.6 still installed.
Do this in your cygwin shell:

export M2_HOME=/cygdrive/c/develop/build/maven-2.0.6
mvn idea:idea

or if you're using cmd:
set M2_HOME=C:\develop\build\maven-2.0.6
mvn idea:idea

Afterwards throw away that shell instance, as it won't be using maven 2.0.7.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-08-25 Thread Geoffrey De Smet (JIRA)

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

Geoffrey De Smet commented on MIDEA-102:


same here: win xp + idea 6 + maven 2.0.7 + maven-idea-plugin 2.1 (and 2.0 too I 
believe) = wrong iml paths in the ipr of a multimodule project.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-08-07 Thread Kristian Nordal (JIRA)

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

Kristian Nordal commented on MIDEA-102:
---

I'm experiencing the same. It works with 2.0.6, not with 2.0.7. It does works 
in os x  though (with 2.0.7), but not in Windows (cmd and cygwin). 

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-07-31 Thread Lars Duvaas (JIRA)

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

Lars Duvaas commented on MIDEA-102:
---

It appears that the bug only occurs in maven 2.0.7.. When I run the goal in 
maven 2.0.6 it works fine.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-07-27 Thread Joern Huxhorn (JIRA)

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

Joern Huxhorn commented on MIDEA-102:
-

To clarify my point a little more: calling toRelative(C:\Foo\bar1, 
C:\Foo\bar2) must return ../bar2 but currently returns C:/Foo/bar2.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-07-26 Thread Dennis Lundberg (JIRA)

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

Dennis Lundberg commented on MIDEA-102:
---

Which issue was this cloned from? Please create a link to it.

 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




[jira] Commented: (MIDEA-102) CLONE -still broken - Module filepath is generated incorrectly

2007-07-26 Thread Joern Huxhorn (JIRA)

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

Joern Huxhorn commented on MIDEA-102:
-

I'd also suggest to change
protected String toRelative( File basedir, String absolutePath )
to
static String toRelative( File basedir, String absolutePath )

and write some tests. I didn't want to change too much, though.

 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