| 
| Eclipse 3.4 strange project naming upon import [message #327624] | Sat, 26 April 2008 15:19  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: peter.neubauer.jayway.se 
 Hi there,
 I am using Eclipse 3.4M6a to import a project in a "api" folder with a
 generated .project file from
 mvn eclipse:eclipse that looks like
 
 <?xml version="1.0" encoding="UTF-8"?>
 <projectDescription>
 <name>api-core</name>
 <comment></comment>
 <projects>
 </projects>
 <buildSpec>
 <buildCommand>
 <name>org.eclipse.jdt.core.javabuilder</name>
 <arguments>
 </arguments>
 </buildCommand>
 </buildSpec>
 <natures>
 <nature>org.eclipse.jdt.core.javanature</nature>
 </natures>
 </projectDescription>
 
 Now, when importing this ("Import existing project into workspace") I get
 the choice "api(api-core)" to import, resulting in the project being named
 "api" when in the .project file it is named "core-api"!
 
 Is this a new feature or a bug in Eclipse, and are there any preferences
 to enforce in order to take the .project name as the name instead of the
 folder?
 
 This is a behaviour I get in all 3.4 versions of Eclipse, furthermore,
 when renaming the project in the workbench with F2, the project name in
 project is updated, the workbench name is correctly reflecting that, but
 when closing and reimporting the renamed project, it again falls back to
 the containing folder name!
 
 
 /peter
 |  |  |  | 
|  | 
| 
| Re: Eclipse 3.4 strange project naming upon import [message #327657 is a reply to message #327624] | Mon, 28 April 2008 05:04   |  | 
| Eclipse User  |  |  |  |  | Peter Neubauer wrote: > Hi there,
 > I am using Eclipse 3.4M6a to import a project in a "api" folder with a
 > generated .project file from mvn eclipse:eclipse that looks like
 >
 > <?xml version="1.0" encoding="UTF-8"?>
 > <projectDescription>
 >        <name>api-core</name>
 >        <comment></comment>
 >        <projects>
 >        </projects>
 >        <buildSpec>
 >                <buildCommand>
 >                        <name>org.eclipse.jdt.core.javabuilder</name>
 >                        <arguments>
 >                        </arguments>
 >                </buildCommand>
 >        </buildSpec>
 >        <natures>
 >                <nature>org.eclipse.jdt.core.javanature</nature>
 >        </natures>
 > </projectDescription>
 >
 > Now, when importing this ("Import existing project into workspace") I
 > get the choice "api(api-core)" to import, resulting in the project
 > being named "api" when in the .project file it is named "core-api"!
 >
 > Is this a new feature or a bug in Eclipse, and are there any
 > preferences to enforce in order to take the .project name as the name
 > instead of the folder?
 See https://bugs.eclipse.org/bugs/show_bug.cgi?id=225754
 
 Dani
 >
 > This is a behaviour I get in all 3.4 versions of Eclipse, furthermore,
 > when renaming the project in the workbench with F2, the project name
 > in project is updated, the workbench name is correctly reflecting
 > that, but when closing and reimporting the renamed project, it again
 > falls back to the containing folder name!
 >
 >
 > /peter
 >
 |  |  |  | 
|  | 
Powered by 
FUDForum. Page generated in 0.44202 seconds