Home » Language IDEs » Java Development Tools (JDT) » Different New Java Project vs Plug-in Project Behavior...
| Different New Java Project vs Plug-in Project Behavior... [message #85106] |
Tue, 12 August 2003 21:46  |
Eclipse User |
|
|
|
Originally posted by: john.ellis.ascentialsoftware.com
Hi,
Using:
Version: 2.1.1
Build id: 200306271545
Wondering if the following is known behavior or a bug.
I have noticed different behavior b/w the new Java Project Wizard and the
new Plug-in Project Wizard.
Prior to running the New Project Wizard, I create the following directory
structure on disk somewhere.
+---eclipse
| \---projects
| \---com.finbar.myjavaproject
| \---com.finbar.myjavaproject2
I then use the New Java Project Wizard and specify project contents to be
the location created above i.e. I uncheck the "Use default" checkbox and
browse for a project location. Then follow the rest of the Wizard.
I repeat this for com.finbar.myjavaproject successfully.
The result is that I have two Java Projects in my workspace whose contents
is elsewhere. This allows me put the Java Projects in source control and
have them remain portable with the use of variables.
However, the above does not seem possible with Plug-in Projects. I cannot
create a Plug-in Project under eclipse\projects shown below b/c it overlaps
with existing Java Projects.
+---eclipse
| \---projects
| \---com.finbar.mypluginproject
| \---com.finbar.mypluginproject2
The questions are...Why will Eclipse allow Java Projects to reside in a
common external directory and not Plug-in Projects?
Cheers, John
|
|
|
| Re: Different New Java Project vs Plug-in Project Behavior... [message #85153 is a reply to message #85106] |
Tue, 12 August 2003 23:17  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NOSPAM.us.ibm.com
You can't have two projects that point to the same area on the disk. So
you can't create a JavaProject AND a Plugin Project that both come from
com.finbar.myjavaproject. That is because when you do what you did it
will actually modify the directory com.finbar.myjavaproject to put a
..classpath file, a .project file, and other control files. So it can't
put a different .project file in there because it is already used by the
javaproject.
PS: A plugin project is by default also a java project. You don't need
to create a separate project.
John Ellis wrote:
> Hi,
>
> Using:
> Version: 2.1.1
> Build id: 200306271545
>
> Wondering if the following is known behavior or a bug.
>
> I have noticed different behavior b/w the new Java Project Wizard and the
> new Plug-in Project Wizard.
>
> Prior to running the New Project Wizard, I create the following directory
> structure on disk somewhere.
>
> +---eclipse
> | \---projects
> | \---com.finbar.myjavaproject
> | \---com.finbar.myjavaproject2
>
> I then use the New Java Project Wizard and specify project contents to be
> the location created above i.e. I uncheck the "Use default" checkbox and
> browse for a project location. Then follow the rest of the Wizard.
>
> I repeat this for com.finbar.myjavaproject successfully.
>
> The result is that I have two Java Projects in my workspace whose contents
> is elsewhere. This allows me put the Java Projects in source control and
> have them remain portable with the use of variables.
>
> However, the above does not seem possible with Plug-in Projects. I cannot
> create a Plug-in Project under eclipse\projects shown below b/c it overlaps
> with existing Java Projects.
>
> +---eclipse
> | \---projects
> | \---com.finbar.mypluginproject
> | \---com.finbar.mypluginproject2
>
> The questions are...Why will Eclipse allow Java Projects to reside in a
> common external directory and not Plug-in Projects?
>
> Cheers, John
>
>
>
--
Thanks, Rich Kulp
|
|
|
| Re: Different New Java Project vs Plug-in Project Behavior... [message #85301 is a reply to message #85153] |
Wed, 13 August 2003 12:47 |
| Eclipse User |
|
|
|
Originally posted by: john.ellis.ascentialsoftware.com
I am not trying to create two projects in the same directory. I realize that
there cannot be two .project and .classpath files in the same directory.
I can create more than one Java Project using the New Project Wizard that
results in what I would expect below.
+---eclipse
| \---projects
| \---com.finbar.myjavaproject
| \.project
| \.classpath
| \---com.finbar.myjavaproject2
| \.project
| \.classpath
I understand that Plug-in projects are java projects, but the point is I
want to use the New Plug-in Project wizard to generate the project and
initial source. However, the New Plug-in Project Wizard will not allow me to
create the following
+---eclipse
| \---projects
| \---com.finbar.myjavaproject (SUCCEEDS:
File->New->Project->Java->Java Project)
| \.project
| \.classpath
| \---com.finbar.myjavaproject2 (SUCCEEDS:
File->New->Project->Java->Java Project)
| \.project
| \.classpath
| \---com.finbar.mypluginproject (FAILS: File->New->Project->Plug-in
Development->Plug-in Project)
| \.project
| \.classpath
If I use the default workspace for the location of projects above, both New
Project Wizards will succeed. However, this is not ideal because using -data
to point at a location in my CVS source tree means that developers need to
maintain the .metadata directory in a transient source structure.
The idea of the "Use default" checkbox, as I understand, is to locate any
project outside the default workspace.
Cheers, John
"Richard L. Kulp" <richkulp@NOSPAM.us.ibm.com> wrote in message
news:bhbsca$a4b$1@eclipse.org...
> You can't have two projects that point to the same area on the disk. So
> you can't create a JavaProject AND a Plugin Project that both come from
> com.finbar.myjavaproject. That is because when you do what you did it
> will actually modify the directory com.finbar.myjavaproject to put a
> .classpath file, a .project file, and other control files. So it can't
> put a different .project file in there because it is already used by the
> javaproject.
>
> PS: A plugin project is by default also a java project. You don't need
> to create a separate project.
>
> John Ellis wrote:
> > Hi,
> >
> > Using:
> > Version: 2.1.1
> > Build id: 200306271545
> >
> > Wondering if the following is known behavior or a bug.
> >
> > I have noticed different behavior b/w the new Java Project Wizard and
the
> > new Plug-in Project Wizard.
> >
> > Prior to running the New Project Wizard, I create the following
directory
> > structure on disk somewhere.
> >
> > +---eclipse
> > | \---projects
> > | \---com.finbar.myjavaproject
> > | \---com.finbar.myjavaproject2
> >
> > I then use the New Java Project Wizard and specify project contents to
be
> > the location created above i.e. I uncheck the "Use default" checkbox and
> > browse for a project location. Then follow the rest of the Wizard.
> >
> > I repeat this for com.finbar.myjavaproject successfully.
> >
> > The result is that I have two Java Projects in my workspace whose
contents
> > is elsewhere. This allows me put the Java Projects in source control and
> > have them remain portable with the use of variables.
> >
> > However, the above does not seem possible with Plug-in Projects. I
cannot
> > create a Plug-in Project under eclipse\projects shown below b/c it
overlaps
> > with existing Java Projects.
> >
> > +---eclipse
> > | \---projects
> > | \---com.finbar.mypluginproject
> > | \---com.finbar.mypluginproject2
> >
> > The questions are...Why will Eclipse allow Java Projects to reside in a
> > common external directory and not Plug-in Projects?
> >
> > Cheers, John
> >
> >
> >
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
| Re: Different New Java Project vs Plug-in Project Behavior... [message #85360 is a reply to message #85301] |
Wed, 13 August 2003 14:06 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
John Ellis wrote:
> I am not trying to create two projects in the same directory. I realize that
> there cannot be two .project and .classpath files in the same directory.
> I can create more than one Java Project using the New Project Wizard that
> results in what I would expect below.
> +---eclipse
> | ---projects
> | ---com.finbar.myjavaproject
> | .project
> | .classpath
> | ---com.finbar.myjavaproject2
> | .project
> | .classpath
> I understand that Plug-in projects are java projects, but the point is I
> want to use the New Plug-in Project wizard to generate the project and
> initial source. However, the New Plug-in Project Wizard will not allow me to
> create the following
> +---eclipse
> | ---projects
> | ---com.finbar.myjavaproject (SUCCEEDS:
> File->New->Project->Java->Java Project)
> | .project
> | .classpath
> | ---com.finbar.myjavaproject2 (SUCCEEDS:
> File->New->Project->Java->Java Project)
> | .project
> | .classpath
> | ---com.finbar.mypluginproject (FAILS: File->New->Project->Plug-in
> Development->Plug-in Project)
> | .project
> | .classpath
What are you typing in for the Project Name and Directory text boxes for
each of the projects? It works for me if I enter
eclipse/projects/com.finbar.my<java/pluginproject> in the Directory field
and give it a name in the Project Name field.
> If I use the default workspace for the location of projects above, both New
> Project Wizards will succeed. However, this is not ideal because using -data
> to point at a location in my CVS source tree means that developers need to
> maintain the .metadata directory in a transient source structure.
> The idea of the "Use default" checkbox, as I understand, is to locate any
> project outside the default workspace.
> Cheers, John
> "Richard L. Kulp" <richkulp@NOSPAM.us.ibm.com> wrote in message
> news:bhbsca$a4b$1@eclipse.org...
> > You can't have two projects that point to the same area on the disk. So
> > you can't create a JavaProject AND a Plugin Project that both come from
> > com.finbar.myjavaproject. That is because when you do what you did it
> > will actually modify the directory com.finbar.myjavaproject to put a
> > .classpath file, a .project file, and other control files. So it can't
> > put a different .project file in there because it is already used by the
> > javaproject.
> >
> > PS: A plugin project is by default also a java project. You don't need
> > to create a separate project.
> >
> > John Ellis wrote:
> > > Hi,
> > >
> > > Using:
> > > Version: 2.1.1
> > > Build id: 200306271545
> > >
> > > Wondering if the following is known behavior or a bug.
> > >
> > > I have noticed different behavior b/w the new Java Project Wizard and
> the
> > > new Plug-in Project Wizard.
> > >
> > > Prior to running the New Project Wizard, I create the following
> directory
> > > structure on disk somewhere.
> > >
> > > +---eclipse
> > > | ---projects
> > > | ---com.finbar.myjavaproject
> > > | ---com.finbar.myjavaproject2
> > >
> > > I then use the New Java Project Wizard and specify project contents to
> be
> > > the location created above i.e. I uncheck the "Use default" checkbox and
> > > browse for a project location. Then follow the rest of the Wizard.
> > >
> > > I repeat this for com.finbar.myjavaproject successfully.
> > >
> > > The result is that I have two Java Projects in my workspace whose
> contents
> > > is elsewhere. This allows me put the Java Projects in source control and
> > > have them remain portable with the use of variables.
> > >
> > > However, the above does not seem possible with Plug-in Projects. I
> cannot
> > > create a Plug-in Project under eclipseprojects shown below b/c it
> overlaps
> > > with existing Java Projects.
> > >
> > > +---eclipse
> > > | ---projects
> > > | ---com.finbar.mypluginproject
> > > | ---com.finbar.mypluginproject2
> > >
> > > The questions are...Why will Eclipse allow Java Projects to reside in a
> > > common external directory and not Plug-in Projects?
> > >
> > > Cheers, John
> > >
> > >
> > >
> >
> > --
> > Thanks, Rich Kulp
> >
> >
|
|
|
| Re: Different New Java Project vs Plug-in Project Behavior... [message #85412 is a reply to message #85360] |
Wed, 13 August 2003 14:42 |
| Eclipse User |
|
|
|
Originally posted by: john.ellis.ascentialsoftware.com
It doesn't matter what I type. There is an overlap detected when using the
New Plug-in wizard.
The difference b/w the New Java Project Wizard and the New Plug-in Project
Wizard is that the Plug-in Wizard will create a new directory under the
selected directory.
E.g. If I select eclipse/projects/com.finbar.mypluginproject as the location
the Plug-in Wizard will succeed. However, the directory structure ends up
being:
eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject
I simply want to to create:
eclipse/projects/com.finbar.mypluginproject/.project
eclipse/projects/com.finbar.mypluginproject/.classpath
What is it about Plug-in java Projects that make them different to regular
Java Projects that prevents my desired structure?
I'm beginning to think it is a defect in the Wizard. A simple test provided
me with some evidence of this possibility.
1. Create
eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject via
the Plug-in Wizard
2. Delete com.finbar.mypluginproject project from the workspace, but
leave contents of directory
3. Move contents of
eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject to
eclipse/projects/com.finbar.mypluginproject.save
4. Delete eclipse/projects/com.finbar.mypluginproject from file system
5. Rename eclipse/projects/com.finbar.mypluginproject.save to
eclipse/projects/com.finbar.mypluginproject
6. Import the project
7. Bingo! Now I have eclipse/projects/com.finbar.mypluginproject that is
just fine...
"Dave Wegener" <wegener@cboenospam.com> wrote in message
news:bhdgl0$nsi$1@eclipse.org...
> John Ellis wrote:
>
> > I am not trying to create two projects in the same directory. I realize
that
> > there cannot be two .project and .classpath files in the same directory.
>
> > I can create more than one Java Project using the New Project Wizard
that
> > results in what I would expect below.
>
> > +---eclipse
> > | ---projects
> > | ---com.finbar.myjavaproject
> > | .project
> > | .classpath
> > | ---com.finbar.myjavaproject2
>
> > | .project
> > | .classpath
>
> > I understand that Plug-in projects are java projects, but the point is I
> > want to use the New Plug-in Project wizard to generate the project and
> > initial source. However, the New Plug-in Project Wizard will not allow
me to
> > create the following
>
> > +---eclipse
> > | ---projects
> > | ---com.finbar.myjavaproject (SUCCEEDS:
> > File->New->Project->Java->Java Project)
> > | .project
> > | .classpath
> > | ---com.finbar.myjavaproject2 (SUCCEEDS:
> > File->New->Project->Java->Java Project)
>
> > | .project
> > | .classpath
> > | ---com.finbar.mypluginproject (FAILS:
File->New->Project->Plug-in
> > Development->Plug-in Project)
>
> > | .project
> > | .classpath
>
> What are you typing in for the Project Name and Directory text boxes for
> each of the projects? It works for me if I enter
> eclipse/projects/com.finbar.my<java/pluginproject> in the Directory field
> and give it a name in the Project Name field.
>
>
> > If I use the default workspace for the location of projects above, both
New
> > Project Wizards will succeed. However, this is not ideal because
using -data
> > to point at a location in my CVS source tree means that developers need
to
> > maintain the .metadata directory in a transient source structure.
>
> > The idea of the "Use default" checkbox, as I understand, is to locate
any
> > project outside the default workspace.
>
> > Cheers, John
>
> > "Richard L. Kulp" <richkulp@NOSPAM.us.ibm.com> wrote in message
> > news:bhbsca$a4b$1@eclipse.org...
> > > You can't have two projects that point to the same area on the disk.
So
> > > you can't create a JavaProject AND a Plugin Project that both come
from
> > > com.finbar.myjavaproject. That is because when you do what you did it
> > > will actually modify the directory com.finbar.myjavaproject to put a
> > > .classpath file, a .project file, and other control files. So it can't
> > > put a different .project file in there because it is already used by
the
> > > javaproject.
> > >
> > > PS: A plugin project is by default also a java project. You don't need
> > > to create a separate project.
> > >
> > > John Ellis wrote:
> > > > Hi,
> > > >
> > > > Using:
> > > > Version: 2.1.1
> > > > Build id: 200306271545
> > > >
> > > > Wondering if the following is known behavior or a bug.
> > > >
> > > > I have noticed different behavior b/w the new Java Project Wizard
and
> > the
> > > > new Plug-in Project Wizard.
> > > >
> > > > Prior to running the New Project Wizard, I create the following
> > directory
> > > > structure on disk somewhere.
> > > >
> > > > +---eclipse
> > > > | ---projects
> > > > | ---com.finbar.myjavaproject
> > > > | ---com.finbar.myjavaproject2
> > > >
> > > > I then use the New Java Project Wizard and specify project contents
to
> > be
> > > > the location created above i.e. I uncheck the "Use default" checkbox
and
> > > > browse for a project location. Then follow the rest of the Wizard.
> > > >
> > > > I repeat this for com.finbar.myjavaproject successfully.
> > > >
> > > > The result is that I have two Java Projects in my workspace whose
> > contents
> > > > is elsewhere. This allows me put the Java Projects in source control
and
> > > > have them remain portable with the use of variables.
> > > >
> > > > However, the above does not seem possible with Plug-in Projects. I
> > cannot
> > > > create a Plug-in Project under eclipseprojects shown below b/c it
> > overlaps
> > > > with existing Java Projects.
> > > >
> > > > +---eclipse
> > > > | ---projects
> > > > | ---com.finbar.mypluginproject
> > > > | ---com.finbar.mypluginproject2
> > > >
> > > > The questions are...Why will Eclipse allow Java Projects to reside
in a
> > > > common external directory and not Plug-in Projects?
> > > >
> > > > Cheers, John
> > > >
> > > >
> > > >
> > >
> > > --
> > > Thanks, Rich Kulp
> > >
> > >
>
>
|
|
|
| Re: Different New Java Project vs Plug-in Project Behavior... [message #85555 is a reply to message #85412] |
Wed, 13 August 2003 19:57 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
John Ellis wrote:
> It doesn't matter what I type. There is an overlap detected when using the
> New Plug-in wizard.
> The difference b/w the New Java Project Wizard and the New Plug-in Project
> Wizard is that the Plug-in Wizard will create a new directory under the
> selected directory.
I see what you mean now. I agree that this behavior is inconsistent. In
the New Java Project Wizard, the project is created in directory specified
in the directory name text box. In the New Plugin-in Project Wizard, a
subdirectory with the plugin name is created as a subdirectory of the
directory specified in the directory name box. This is confusing and as
you state leads to a redundant directory being created for plugin projects.
Interestingly, if the default location is used for a project, a new
directory with the projects name is created in the default workspace
location. In fact the directory name dialog box displays the new
directory as you type the name.
I would suggest that you open a bugzilla request asking for a more
consistent behavior. You can include the contents of this thread to
describe the problem.
> E.g. If I select eclipse/projects/com.finbar.mypluginproject as the location
> the Plug-in Wizard will succeed. However, the directory structure ends up
> being:
> eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject
> I simply want to to create:
> eclipse/projects/com.finbar.mypluginproject/.project
> eclipse/projects/com.finbar.mypluginproject/.classpath
> What is it about Plug-in java Projects that make them different to regular
> Java Projects that prevents my desired structure?
> I'm beginning to think it is a defect in the Wizard. A simple test provided
> me with some evidence of this possibility.
> 1. Create
> eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject via
> the Plug-in Wizard
> 2. Delete com.finbar.mypluginproject project from the workspace, but
> leave contents of directory
> 3. Move contents of
> eclipse/projects/com.finbar.mypluginproject/com.finbar.myplu ginproject to
> eclipse/projects/com.finbar.mypluginproject.save
> 4. Delete eclipse/projects/com.finbar.mypluginproject from file system
> 5. Rename eclipse/projects/com.finbar.mypluginproject.save to
> eclipse/projects/com.finbar.mypluginproject
> 6. Import the project
> 7. Bingo! Now I have eclipse/projects/com.finbar.mypluginproject that is
> just fine...
> "Dave Wegener" <wegener@cboenospam.com> wrote in message
> news:bhdgl0$nsi$1@eclipse.org...
> > John Ellis wrote:
> >
> > > I am not trying to create two projects in the same directory. I realize
> that
> > > there cannot be two .project and .classpath files in the same directory.
> >
> > > I can create more than one Java Project using the New Project Wizard
> that
> > > results in what I would expect below.
> >
> > > +---eclipse
> > > | ---projects
> > > | ---com.finbar.myjavaproject
> > > | .project
> > > | .classpath
> > > | ---com.finbar.myjavaproject2
> >
> > > | .project
> > > | .classpath
> >
> > > I understand that Plug-in projects are java projects, but the point is I
> > > want to use the New Plug-in Project wizard to generate the project and
> > > initial source. However, the New Plug-in Project Wizard will not allow
> me to
> > > create the following
> >
> > > +---eclipse
> > > | ---projects
> > > | ---com.finbar.myjavaproject (SUCCEEDS:
> > > File->New->Project->Java->Java Project)
> > > | .project
> > > | .classpath
> > > | ---com.finbar.myjavaproject2 (SUCCEEDS:
> > > File->New->Project->Java->Java Project)
> >
> > > | .project
> > > | .classpath
> > > | ---com.finbar.mypluginproject (FAILS:
> File->New->Project->Plug-in
> > > Development->Plug-in Project)
> >
> > > | .project
> > > | .classpath
> >
> > What are you typing in for the Project Name and Directory text boxes for
> > each of the projects? It works for me if I enter
> > eclipse/projects/com.finbar.my<java/pluginproject> in the Directory field
> > and give it a name in the Project Name field.
> >
> >
> > > If I use the default workspace for the location of projects above, both
> New
> > > Project Wizards will succeed. However, this is not ideal because
> using -data
> > > to point at a location in my CVS source tree means that developers need
> to
> > > maintain the .metadata directory in a transient source structure.
> >
> > > The idea of the "Use default" checkbox, as I understand, is to locate
> any
> > > project outside the default workspace.
> >
> > > Cheers, John
> >
> > > "Richard L. Kulp" <richkulp@NOSPAM.us.ibm.com> wrote in message
> > > news:bhbsca$a4b$1@eclipse.org...
> > > > You can't have two projects that point to the same area on the disk.
> So
> > > > you can't create a JavaProject AND a Plugin Project that both come
> from
> > > > com.finbar.myjavaproject. That is because when you do what you did it
> > > > will actually modify the directory com.finbar.myjavaproject to put a
> > > > .classpath file, a .project file, and other control files. So it can't
> > > > put a different .project file in there because it is already used by
> the
> > > > javaproject.
> > > >
> > > > PS: A plugin project is by default also a java project. You don't need
> > > > to create a separate project.
> > > >
> > > > John Ellis wrote:
> > > > > Hi,
> > > > >
> > > > > Using:
> > > > > Version: 2.1.1
> > > > > Build id: 200306271545
> > > > >
> > > > > Wondering if the following is known behavior or a bug.
> > > > >
> > > > > I have noticed different behavior b/w the new Java Project Wizard
> and
> > > the
> > > > > new Plug-in Project Wizard.
> > > > >
> > > > > Prior to running the New Project Wizard, I create the following
> > > directory
> > > > > structure on disk somewhere.
> > > > >
> > > > > +---eclipse
> > > > > | ---projects
> > > > > | ---com.finbar.myjavaproject
> > > > > | ---com.finbar.myjavaproject2
> > > > >
> > > > > I then use the New Java Project Wizard and specify project contents
> to
> > > be
> > > > > the location created above i.e. I uncheck the "Use default" checkbox
> and
> > > > > browse for a project location. Then follow the rest of the Wizard.
> > > > >
> > > > > I repeat this for com.finbar.myjavaproject successfully.
> > > > >
> > > > > The result is that I have two Java Projects in my workspace whose
> > > contents
> > > > > is elsewhere. This allows me put the Java Projects in source control
> and
> > > > > have them remain portable with the use of variables.
> > > > >
> > > > > However, the above does not seem possible with Plug-in Projects. I
> > > cannot
> > > > > create a Plug-in Project under eclipseprojects shown below b/c it
> > > overlaps
> > > > > with existing Java Projects.
> > > > >
> > > > > +---eclipse
> > > > > | ---projects
> > > > > | ---com.finbar.mypluginproject
> > > > > | ---com.finbar.mypluginproject2
> > > > >
> > > > > The questions are...Why will Eclipse allow Java Projects to reside
> in a
> > > > > common external directory and not Plug-in Projects?
> > > > >
> > > > > Cheers, John
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Thanks, Rich Kulp
> > > >
> > > >
> >
> >
|
|
|
Goto Forum:
Current Time: Thu Dec 26 14:41:21 GMT 2024
Powered by FUDForum. Page generated in 0.03643 seconds |
] 
Search
Help
Register
Login
Home
