20 comments
Comment actions Permalink

Yep. Forgot to mention in EAP release notes unfortunately.

-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hello linux_china,

l> What is it? Export eclipse project to IDEA's format?

It is piece of RoadMap for IDEA. Remember, long time ago, when IDEA was as
JBuilder plugin?
Where IDEA now and where JBuilder?
Look - here is new era of IDEA occupation. IDEA will work as plugin for Eclipse.
This will kill Eclipse as king of IDEs and IDEA will rule the World :)

--
Alexey Efimov, Java Developer
Tops BI


0
Comment actions Permalink

So how does it work? I am using WSAD 5.1 as well as IntelliJ and would love
to test this out.

Any install instructions?


"Maxim Shafirov (JetBrains)" <max@jetbrains.com> wrote in message
news:c8a8a1bfef788c74620879d4779@news.jetbrains.com...

Yep. Forgot to mention in EAP release notes unfortunately.

>

-------------------
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

>



0
Comment actions Permalink

It installs as usual eclipse plugin (copy somewhere, I'm not very certain)
and adds new menu item to Export menu.

-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Maxim, what happened to the old strategy of importing eclipse projects? Did you dump that in favor of this export plugin?

Now, I understand that's probably much easier to export from eclipse than to import from IDEA (the plugin probably has access to a lot more information), but unfortunately that doesn't hit the sweet spot.

I don't need to import eclipse projects because I use the two IDE's -- you won't find the smell of eclipse on my machine. Unfortunately, the world out there doesn't think the same and most of open source (or not) projects out there come with eclipse project descriptors -- it would be lovely if IDEA could import these projects, even in a simple "best efforts" way. Import what you can and tell the user what you couldn't figure out.

The current approaches to importing eclipse projects don't work for me. I'm an IntelliJ IDEA user, not an Eclipse user. I don't want to install eclipse.

0
Comment actions Permalink

I know that this is EAP, but is it stable?

Documentation for the plugin would be nice. Specifics as to what types of projects/modules
it supports as well as whether it includes things like the myEclipse and subclipse plugin
configurations.

I would like to have one of my coworkers use it to export their eclipse Web application
project and try it out on my IDEA, but I don't want to give them a bad impression of
IntelliJ if we can't figure it out or if it doesn't work smoothly and completely.

0
Comment actions Permalink

You are right, this is a plugin for Eclipse that exports Eclipse's
Workspace and Java Project to IDEA project and modules.

linux_china wrote:

What is it? Export eclipse project to IDEA's format?


--


Sergey Grigorchuk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Do you mean something like that: search this directory for .classpath and
.project files and create a project out of these modules? Sounds good to me.

Tom

0
Comment actions Permalink

More like this:

Here, take this directory. Now, search it for '.classpath' and '.project' files, creating a module for each pair found. To tie up, create a project containing with all modules created in this way.

I'd be happy if all we get is the first part (create a module from .classpath/.project).

0
Comment actions Permalink

Documentation will be available soon.

The first version supports just Java Projects, but if people want we
will support other types of projects.

What about your web applications? As I understand you use WSAD or
something like this and your projects are not simple Java Project.
Right? So now you cannot export your projects.



Tim Haley wrote:

I know that this is EAP, but is it stable?

Documentation for the plugin would be nice. Specifics as to what types
of projects/modules it supports as well as whether it includes things
like the myEclipse and subclipse plugin configurations.

I would like to have one of my coworkers use it to export their eclipse
Web application project and try it out on my IDEA, but I don't want to
give them a bad impression of IntelliJ if we can't figure it out or if
it doesn't work smoothly and completely.



--


Sergey Grigorchuk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Don't worry old strategy is alive. The main problem of the old strategy
is that Eclipse stores many preferences within binary files and we are
not sure that format of these files will not be changed in future (as
you know Eclipse 3.1 is coming).

Marcus Brito wrote:

Maxim, what happened to the old strategy of importing eclipse projects? Did you dump that in favor of this export plugin?

Now, I understand that's probably much easier to export from eclipse than to import from IDEA (the plugin probably has access to a lot more information), but unfortunately that doesn't hit the sweet spot.

I don't need to import eclipse projects because I use the two IDE's -- you won't find the smell of eclipse on my machine. Unfortunately, the world out there doesn't think the same and most of open source (or not) projects out there come with eclipse project descriptors -- it would be lovely if IDEA could import these projects, even in a simple "best efforts" way. Import what you can and tell the user what you couldn't figure out.

The current approaches to importing eclipse projects don't work for me. I'm an IntelliJ IDEA user, not an Eclipse user. I don't want to install eclipse.



--


Sergey Grigorchuk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Don't worry old strategy is alive. The main problem
of the old strategy
is that Eclipse stores many preferences within binary
files and we are
not sure that format of these files will not be
changed in future (as
you know Eclipse 3.1 is coming).


I'd say you shouldn't bother with those -- just extract as much information as your can for the eclipse ".classpath" and ".project" files. For anything fancier you'll need an eclipse installation, and if you're going to have to install that thing, better use the export plugin.

0
Comment actions Permalink

What about your web applications? As I understand you
use WSAD or
something like this and your projects are not simple
Java Project.
Right? So now you cannot export your projects.


IDEA could import "common" eclipse web project formats, those being projects created by MyEclipse[1] and WTP[2].

http://www.myeclipse-ide.com
http://www.eclipse.org/webtools

0
Comment actions Permalink

Sergey Grigorchuk (JetBrains) wrote:

Documentation will be available soon.

The first version supports just Java Projects, but if people want we
will support other types of projects.

What about your web applications? As I understand you use WSAD or
something like this and your projects are not simple Java Project.
Right? So now you cannot export your projects.


Yeah, they use the MyEclipse plugin for our web applications. We are also in the process of
migrating to subversion so the eclipse users would use the subclipse plugin to integrate that.

Without support for web applications it would not be very useful to me.

What would really be useful is round-trip support: Let me open an eclipse project work on
it in IDEA and then export an eclipse project with my changes so that the die-hard eclipse
users can work with my stuff. Probably not very likely, but it would be really useful.

Maybe in the future there will be a standard project/module configuration file format agreed
upon by the industry. Something like...Ant.

Round trip IDEA<>Ant and Eclipse<>Ant would probably be even better.

0
Comment actions Permalink

Maybe I did not describe it correctly, but we have the same expectation. It
also would be fine, if IDEA could find all own module files automatically.

Tom

0
Comment actions Permalink

In article <d9engf$31h$1@is.intellij.net>,
Tim Haley <ymaraner@yahoo.com> wrote:

What would really be useful is round-trip support: Let me open an eclipse
project work on it in IDEA and then export an eclipse project with my changes so that the
die-hard eclipse users can work with my stuff. Probably not very likely, but it would be
really useful.


I would love this too. The buckminster project at eclipse.org seems
like it might be a start on this direction. At the least, it lets you
build a workspace once you have .project and .classpath files.

Scott

--
Scott Ellsworth
scott@alodar.nospam.com
Java and database consulting for the life sciences

0
Comment actions Permalink

Maybe in the future there will be a standard
project/module configuration file format agreed
upon by the industry. Something like...Ant.


Ant doesn't really deal with project/module configuration -- it's more akin to "make", in the sense that it's actually a sequence of commands to execute.

As much as I hate to admit it, maven is more like what you're thinking about. You declare your project properties in a configuration file (the POM) and everyhting else is handled by maven.

0
Comment actions Permalink

I use Eclipse 3.1M5
I copied that plugin to \eclipse\plugins\com.intellij.eclipse.export_1.0.0\
started Eclipse

And I don't see any new plugin or menu item in Export.

What I'm missing?

0
Comment actions Permalink

There was a problem with configuration of plugin. It is fixed now,
please wait next release.

Also it has not been tested with Eclipse 3.1 (just Eclipse 3.0.X) so I
am not sure that it should work with your environment.


Michael Kor wrote:

I use Eclipse 3.1M5
I copied that plugin to \eclipse\plugins\com.intellij.eclipse.export_1.0.0\
started Eclipse

And I don't see any new plugin or menu item in Export.

What I'm missing?



--


Sergey Grigorchuk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Marcus Brito wrote:
>>Maybe in the future there will be a standard
>>project/module configuration file format agreed
>>upon by the industry. Something like...Ant.


Ant doesn't really deal with project/module configuration -- it's more akin to "make", in the sense that it's actually a sequence of commands to execute.

As much as I hate to admit it, maven is more like what you're thinking about. You declare your project properties in a configuration file (the POM) and everyhting else is handled by maven.


Yes, maven is more of a project/module config tool, but it isn't exactly an industry
standard yet. Although I have heard much about it (mostly negative or neutral), I haven't
had a chance to delve deeply into it myself.

And yes, ant is very similar to make, but if you structure your ant files reasonably and use
a standard naming convention, it can also be used for project/module configuration. The ant
build files generated by IDEA are relatively good in that regard. It seems that it wouldn't
be too difficult for IDEA to use an ant build file (or set of files) generated by IDEA for
project/module configuration. Then they could completely get rid of the ipr and iml files.

Maybe I should look into maven. Even if the product itself isn't a standard, it's POM
format could become one.

0

Please sign in to leave a comment.