When you create a new module, you have the option to import settings from an Eclipse project. Is that what you were looking for?
That's seriously limited, IMO, most of the time one would want an entire eclipse workspace imported into an IDEA project (including the dependencies between the eclipse projects). I need to point IDEA to an existing eclipse workspace, create an IDEA project out of it and go. Not possible with what we have now.
I've submitted some requests for enhancements a while ago (it was before jetbrains switched to JIRA), but haven't seen any updates.
Jetbrains, is the current functionality all we'll see for this? Do you still plan to enhance it with full workspace import, libraries configuration and such?
That appeared to be quite uneasy task as Eclipse workspaces are stored in some binary format thus import could be implemented as Eclipse plugin only. Thus we're unaware if we have enough resources to dig into writing Eclipse plugins before 5.0 release.
>> IDEA :) >> >> When you create a new module, you have the option to import settings >> from an Eclipse project. Is that what you were looking for? >>
That's seriously limited, IMO, most of the time one would want an entire eclipse workspace imported into an IDEA project (including the dependencies between the eclipse projects). I need to point IDEA to an existing eclipse workspace, create an IDEA project out of it and go. Not possible with what we have now.
I've submitted some requests for enhancements a while ago (it was before jetbrains switched to JIRA), but haven't seen any updates.
Jetbrains, is the current functionality all we'll see for this? Do you still plan to enhance it with full workspace import, libraries configuration and such?
That appeared to be quite uneasy task as Eclipse workspaces are stored in some binary format thus import could be implemented as Eclipse plugin only. Thus we're unaware if we have enough resources to dig into writing Eclipse plugins before 5.0 release.
That binary format is an incredible pain in the tush for me. I can generate IDEA projects for the 150 interdependent projects at one of my clients in under five seconds, and be coding away in IDEA in under a minute after someone changes the dep tree.
In Eclipse, this is a manual and tedious process. When I talked to some Eclipse people about it, they said "this is an easy plugin to write, probably a good learning project." Thing is, I do not have the time to do so at this exact moment, while the skills needed to transform and generate XML are marketable enough to justify the effort needed to write an IDEA project generator.
Further, there would be more demand for Eclipse at this client if there were more users, and there would be more users if getting started was not such an pain.
Why is this a rant relevant to JB? Because this is why there are two IDEA users there, and a whole bunch of ANT users. Without the ease of generation and plain old XML, I would not have gotten permission to create the project generation system. JB innovates by using an open format, and they get two customers out of it.
Eclipse chooses closed opaque formats, and we cannot use their system as easily.
Ant scripts, plugins, transforms, import wizards?
IDEA :)
When you create a new module, you have the option to import settings from an
Eclipse project. Is that what you were looking for?
Vince.
heh heh. oops.
What version is this present in? I'm still on 4.5, and didn't see it...
--peter
Please try the EAP version.
Tom
Hello Vincent,
That's seriously limited, IMO, most of the time one would want an entire
eclipse workspace imported into an IDEA project (including the dependencies
between the eclipse projects). I need to point IDEA to an existing eclipse
workspace, create an IDEA project out of it and go. Not possible with what
we have now.
I've submitted some requests for enhancements a while ago (it was before
jetbrains switched to JIRA), but haven't seen any updates.
Jetbrains, is the current functionality all we'll see for this? Do you still
plan to enhance it with full workspace import, libraries configuration and
such?
Best,
Andrei
That appeared to be quite uneasy task as Eclipse workspaces are stored in
some binary format thus import could be implemented as Eclipse plugin only.
Thus we're unaware if we have enough resources to dig into writing Eclipse
plugins before 5.0 release.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
>> IDEA :)
>>
>> When you create a new module, you have the option to import settings
>> from an Eclipse project. Is that what you were looking for?
>>
In article <c8a8a1bf93e98c718b7438287c7@news.jetbrains.com>,
Maxim Shafirov (JetBrains) <max@jetbrains.com> wrote:
That binary format is an incredible pain in the tush for me. I can
generate IDEA projects for the 150 interdependent projects at one of my
clients in under five seconds, and be coding away in IDEA in under a
minute after someone changes the dep tree.
In Eclipse, this is a manual and tedious process. When I talked to some
Eclipse people about it, they said "this is an easy plugin to write,
probably a good learning project." Thing is, I do not have the time to
do so at this exact moment, while the skills needed to transform and
generate XML are marketable enough to justify the effort needed to write
an IDEA project generator.
Further, there would be more demand for Eclipse at this client if there
were more users, and there would be more users if getting started was
not such an pain.
Why is this a rant relevant to JB? Because this is why there are two
IDEA users there, and a whole bunch of ANT users. Without the ease of
generation and plain old XML, I would not have gotten permission to
create the project generation system. JB innovates by using an open
format, and they get two customers out of it.
Eclipse chooses closed opaque formats, and we cannot use their system as
easily.
Ok - rant over.
Scott