geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-5306) Can't import Geronimo projects into eclipse, because two projects called 'client'.
Date Thu, 26 Jul 2012 07:47:34 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shawn Jiang resolved GERONIMO-5306.
-----------------------------------

    Resolution: Fixed
      Assignee: Shawn Jiang
    
> Can't import Geronimo projects into eclipse, because two projects called 'client'.
> ----------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5306
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5306
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>         Environment: Geronimo 2.2
>            Reporter: yuanyun.cn
>            Assignee: Shawn Jiang
>            Priority: Minor
>              Labels: Eclipse, Maven
>
> After run mvn eclipse:eclipse, and try to import the projects into eclipse, 
> It fails, and it reports: "Resource '/client' already exsits'.".
> This is because there are two projects called 'client'.
> search the source code, and find there are indeed two projects named 'client':
> ${geronimo_src_base_dir}\geronimo-2.2\plugins\client\client, in its generated .project
file:
> <projectDescription>
>   <name>client</name>
>   <comment>Client plugin</comment>
> ...
>   
> ${geronimo_src_base_dir}\geronimo-2.2\plugingroups\client, in its generated .project
file:
> <projectDescription>
>   <name>client</name>
>   <comment>This plugin group provides Client functionality.</comment>
> ...
> quick google search, and find http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
> seems to fix this problem, we can configure eclipse plugin to appende the groupId of
the artifact to the name of the generated Eclipse project.
> We can add the following section to outermost pom.xml:
> <build>
>     <pluginManagement>
>         <plugins>
>             <plugin>
>              <groupId>org.apache.maven.plugins</groupId>
>              <artifactId>maven-eclipse-plugin</artifactId>
>                 <configuration>
>                   <addGroupIdToProjectName>
>                     true
>                   </addGroupIdToProjectName>
>                 </configuration>
>             </plugin>
> ...
> </build>        
> so for each geronimo subproject - take ${geronimo_src_base_dir}\geronimo-2.2\plugins\client\client
as example, eclipse project name would be org.apache.geronimo.configs.client.
> ${geronimo_src_base_dir}\geronimo-2.2\plugingroups\client, in its generated .project
file:
> <projectDescription>
>   <name>org.apache.geronimo.configs.client</name>
>   <comment>Client plugin</comment>
>   
> Have verified the fix works, Geronimo projects can be successfully imported to eclipse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message