| How can I create a Java Project programatically when running textual Eclipse? [message #30235] |
Mon, 19 May 2003 17:12  |
Eclipse User |
|
|
|
I don't have access to a Shell or anything. I simply tried
JavaCore.create(...) giving it an IProject, but the project that was created
was not a Java Project (although it was returned as IJavaProject, it's
classpath etc. weren't set, and so it wasn't considered a Java project by
some of the other projects and views). I looked at what the
NewProjectCreationWizardPage does to create an authentic Java Project. It's
delegating some crucial functionality to BuildPathsBlock, which I cannot use
since it is a mixture of UI and logic. Now, it seems, I cannot create a
Java project w/o copying large chunks of code from various places (in
NewProjectCreationWizardPage and BuildPathsBlock). Is there an easier way
to create a java project? Regardless, I must say that I'm surprised by the
poor quality of the code.
|
|
|
|
|
|
|
|
| Re: How can I create a Java Project programatically when running textual Eclipse? [message #43340 is a reply to message #30481] |
Thu, 29 May 2003 14:11  |
| Eclipse User |
|
|
|
> >Regardless, I must say that I'm surprised by the poor quality of the
code.
> eclipse has a couple hundred thousands users who think otherwise
Of course, Eclipse is a great product. As a user, I love it. But my
comment was regarding the quality of code and not the quality of the
product. Eclipse users don't see the code that the developers do. More
specifically, my comment was directed at BuildPathsBlock. I was genuinely
surprised to see that it violated one of the basic tenets of software
engineering -- always keep UI and logic separate. I just thought that all
open-source code would be top quality. Of course, that class is an internal
package, so whoever wrote it has some defence. Anyways, I wasn't looking to
offend anybody......like I said, I was genuinely surprised.
BTW, thanks for the tip about the JavaProjectHelper class. That was quite
useful. However, I noticed that it has its own rt.jar, and it doesn't load
one based on the settings in Eclipse and the JDK installed on the user's
computer. Also, is there a reason why a utility class like this is not
included in one of the regular JDT plug-ins that ship with Eclipse?
Pratik Shah
"Adam Kiezun" <adam.kiezun@gmx.net.remove> wrote in message
news:bablft$v2$1@rogue.oti.com...
> >Regardless, I must say that I'm surprised by the poor quality of the
code.
>
> eclipse has a couple hundred thousands users who think otherwise
>
> naturally, contibutions are more than welcome - it's open source
> we'll be quite happy to include your code, should it prove to be better
than the
> existing one
>
> look at how org.eclipse.jdt.testplugin.JavaProjectHelper creates and sets
up
> Java projects
>
> regards
> a.
> --
> eclipse.org
>
>
>
|
|
|
|
| Re: How can I create a Java Project programatically when running textual Eclipse? [message #255075 is a reply to message #43340] |
Wed, 16 July 2008 04:31 |
| Eclipse User |
|
|
|
Hi,
I'm of the same opinion as yours.
But jdt is not the only project which mixes up GUI and model.
the MVC pattern has not yet been well implemented by any of the
projects/eclipse plugins I have seen the source code.
By the way I have the same problem. I have seen the Helper class but I
don't know how you create the source container.
I create a Java Project programmatically. With the Java Capability
Wizard I configure it but afterwards no Source or Output Container is
created in any way.
Have I overseen something here?
Thanks for reply
Guenther Falk
Pratik Shah schrieb:
>>> Regardless, I must say that I'm surprised by the poor quality of the
> code.
>> eclipse has a couple hundred thousands users who think otherwise
>
> Of course, Eclipse is a great product. As a user, I love it. But my
> comment was regarding the quality of code and not the quality of the
> product. Eclipse users don't see the code that the developers do. More
> specifically, my comment was directed at BuildPathsBlock. I was genuinely
> surprised to see that it violated one of the basic tenets of software
> engineering -- always keep UI and logic separate. I just thought that all
> open-source code would be top quality. Of course, that class is an internal
> package, so whoever wrote it has some defence. Anyways, I wasn't looking to
> offend anybody......like I said, I was genuinely surprised.
>
> BTW, thanks for the tip about the JavaProjectHelper class. That was quite
> useful. However, I noticed that it has its own rt.jar, and it doesn't load
> one based on the settings in Eclipse and the JDK installed on the user's
> computer. Also, is there a reason why a utility class like this is not
> included in one of the regular JDT plug-ins that ship with Eclipse?
>
> Pratik Shah
>
>
> "Adam Kiezun" <adam.kiezun@gmx.net.remove> wrote in message
> news:bablft$v2$1@rogue.oti.com...
>>> Regardless, I must say that I'm surprised by the poor quality of the
> code.
>> eclipse has a couple hundred thousands users who think otherwise
>>
>> naturally, contibutions are more than welcome - it's open source
>> we'll be quite happy to include your code, should it prove to be better
> than the
>> existing one
>>
>> look at how org.eclipse.jdt.testplugin.JavaProjectHelper creates and sets
> up
>> Java projects
>>
>> regards
>> a.
>> --
>> eclipse.org
>>
>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.22462 seconds
Home