I see the button in the paths dialog, but it's not very self-explanatory.
Pressing small P button located near each source folder allows you to enter package prefix for this source root. I.e. if you have the following file tree structure:
src
editor
Editor.java
and the Editor.java actually contains com.intellij.editor.Editor class you're to set com.intellij package prefix for src source root in order to things work right.
-- Maxim Shafirov IntelliJ Labs / JetBrains Inc. http://www.intellij.com "Develop with pleasure!"
I still can't believe that people have not had enough time to move their directories around to match the way the rest of the world does java development.
Norris Shelton Sun Certified Java Programmer
Maxim Shafirov (JetBrains) wrote:
Russell Egan wrote:
> >> I see the button in the paths dialog, but it's not very >> self-explanatory. >
Pressing small P button located near each source folder allows you to enter package prefix for this source root. I.e. if you have the following file tree structure:
>
src | editor | Editor.java
>
and the Editor.java actually contains com.intellij.editor.Editor class you're to set com.intellij package prefix for src source root in order to things work right.
I still can't believe that people have not had enough time to move their directories around to match the way the rest of the world does java development.
I just ran into the same situation yesterday. The project was created in Java 1.0 days (and it's still going strong!) when there was no real standard directory structure, and it really does not fit well in IDEA's view of how a project should be structured. Much folder exclusion had to be performed so that IDEA was usable and did not crash with an OOME.
Ciao, Gordon
-- Gordon Tyler (Software Developer) Quest Software <http://java.quest.com/> 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: 416-643-4846 | Fax: 416-594-1919
NO! The request was mainly caused by those HUGE projects that have almost everything under one com/** directory and if you are about to work on few packages you HAVE to have a chance to add just those as src.
This was possible in IDEA 3 (little ugly) and not in IDEA 4 (reworked modules). Now, this seems to be the right approach solving the problem.
r.
Gordon Tyler wrote:
Norris Shelton wrote:
>> I still can't believe that people have not had enough time to move >> their directories around to match the way the rest of the world does >> java development.
I just ran into the same situation yesterday. The project was created in Java 1.0 days (and it's still going strong!) when there was no real standard directory structure, and it really does not fit well in IDEA's view of how a project should be structured. Much folder exclusion had to be performed so that IDEA was usable and did not crash with an OOME.
Our project is about 6 years old or so and has been passed from one development team to another with little continuity. And we're on a once-per-quarter release schedule, with maintenance releases in between. Everyone is just afraid to touch the thing.
NO! The request was mainly caused by those HUGE projects that have almost everything under one com/** directory and if you are about to work on few packages you HAVE to have a chance to add just those as src.
Sorry if I wasn't clear but that is the problem I faced. Additionally, off the same parent directory as the com/... were various non-Java directories which had to be excluded. Basically, there was no "java" subdirectory which could be added as the source root.
This was possible in IDEA 3 (little ugly) and not in IDEA 4 (reworked modules). Now, this seems to be the right approach solving the problem.
I agree, being able to select any folder as source and indicate what its package prefix should be far more flexible.
Ciao, Gordon
-- Gordon Tyler (Software Developer) Quest Software <http://java.quest.com/> 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: 416-643-4846 | Fax: 416-594-1919
NO! The request was mainly caused by those HUGE projects that have almost everything under one com/** directory and if you are about to work on few packages you HAVE to have a chance to add just those as src.
This was possible in IDEA 3 (little ugly) and not in IDEA 4 (reworked modules). Now, this seems to be the right approach solving the problem.
Thanks Richard. It is not often that someone says anything good about reworked modules ;)
Cheers, Dmitry -- Dmitry Lomov Software Developer JetBrains Inc. http://www.jetbrains.com "Develop with pleasure!"
Ah, ha. Very interesting. It needs to have a drop-down to allow you to select from one of the present packages.
Norris Shelton Sun Certified Java Programmer
Richard Nemec wrote:
NO! The request was mainly caused by those HUGE projects that have almost everything under one com/** directory and if you are about to work on few packages you HAVE to have a chance to add just those as src.
>
This was possible in IDEA 3 (little ugly) and not in IDEA 4 (reworked modules). Now, this seems to be the right approach solving the problem.
>
r.
>
Gordon Tyler wrote:
> >> Norris Shelton wrote: >> >>> I still can't believe that people have not had enough time to move >>> their directories around to match the way the rest of the world does >>> java development. >> >> >> >> I just ran into the same situation yesterday. The project was created >> in Java 1.0 days (and it's still going strong!) when there was no >> real standard directory structure, and it really does not fit well in >> IDEA's view of how a project should be structured. Much folder >> exclusion had to be performed so that IDEA was usable and did not >> crash with an OOME. >> >> Ciao, >> Gordon >>
I'd love to work on a project with that much flexibility, but this ain't it.
One of us niavely tried moving a few class files into an appropriate package. Turns out, some other code had hard-coded the original names and package locations into string it used to launch new jvms. Also turned out that a bunch of nt .bat files also referred to the original names, but were not picked up on search because the .bat files are generated by the Installshield script at install time. I know, I know, it's all awful, but that's what we have to work with, and no has time to properly test changes like that.
Don't get me wrong, if I were the only person working on the project, rip it apart and restructure it in a couple days, but the realities of a big, old, fragile codebase, a 20 person team, and feature-bloated release schedule, and a lack of QA resources simply don't allow it.
Russell Egan wrote:
Pressing small P button located near each source folder allows you to enter package prefix for this source root.
I.e. if you have the following file tree structure:
src
editor
Editor.java
and the Editor.java actually contains com.intellij.editor.Editor class you're to set com.intellij package prefix for src
source root in order to things work right.
--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
I still can't believe that people have not had enough time to move their
directories around to match the way the rest of the world does java
development.
Norris Shelton
Sun Certified Java Programmer
Maxim Shafirov (JetBrains) wrote:
>
>> I see the button in the paths dialog, but it's not very
>> self-explanatory.
>
>
>
>
Norris Shelton wrote:
I just ran into the same situation yesterday. The project was created in
Java 1.0 days (and it's still going strong!) when there was no real
standard directory structure, and it really does not fit well in IDEA's
view of how a project should be structured. Much folder exclusion had to
be performed so that IDEA was usable and did not crash with an OOME.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
NO! The request was mainly caused by those HUGE projects that have
almost everything under one com/** directory and if you are about to work
on few packages you HAVE to have a chance to add just those as src.
This was possible in IDEA 3 (little ugly) and not in IDEA 4 (reworked
modules). Now, this seems to be the right approach solving the problem.
r.
Gordon Tyler wrote:
>> I still can't believe that people have not had enough time to move
>> their directories around to match the way the rest of the world does
>> java development.
Our project is about 6 years old or so and has been passed from one development team to another with little continuity. And we're on a once-per-quarter release schedule, with maintenance releases in between. Everyone is just afraid to touch the thing.
Richard Nemec wrote:
Sorry if I wasn't clear but that is the problem I faced. Additionally,
off the same parent directory as the com/... were various non-Java
directories which had to be excluded. Basically, there was no "java"
subdirectory which could be added as the source root.
I agree, being able to select any folder as source and indicate what its
package prefix should be far more flexible.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
refactor! Just add the com.xyz dir, and move everything into it. That should work the first time out, at least from my experience.
R
Ah, ha. That's what I said.
Norris Shelton
Sun Certified Java Programmer
Robert S. Sfeir wrote:
>refactor! Just add the com.xyz dir, and move everything into it. That should work the first time out, at least from my experience.
>
>R
>
Richard Nemec wrote:
Thanks Richard.
It is not often that someone says anything good about reworked modules ;)
Cheers,
Dmitry
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
For old EAPers modules was not so easy to accept and many of them keep crying about it :), more interesting what new users think.
TIA,
Dmitry
Ah, ha. Very interesting. It needs to have a drop-down to allow you to
select from one of the present packages.
Norris Shelton
Sun Certified Java Programmer
Richard Nemec wrote:
>
>
>
>
>> Norris Shelton wrote:
>>
>>> I still can't believe that people have not had enough time to move
>>> their directories around to match the way the rest of the world does
>>> java development.
>>
>>
>>
>> I just ran into the same situation yesterday. The project was created
>> in Java 1.0 days (and it's still going strong!) when there was no
>> real standard directory structure, and it really does not fit well in
>> IDEA's view of how a project should be structured. Much folder
>> exclusion had to be performed so that IDEA was usable and did not
>> crash with an OOME.
>>
>> Ciao,
>> Gordon
>>
I'd love to work on a project with that much flexibility, but this ain't it.
One of us niavely tried moving a few class files into an appropriate package. Turns out, some other code had hard-coded the original names and package locations into string it used to launch new jvms. Also turned out that a bunch of nt .bat files also referred to the original names, but were not picked up on search because the .bat files are generated by the Installshield script at install time. I know, I know, it's all awful, but that's what we have to work with, and no has time to properly test changes like that.
Don't get me wrong, if I were the only person working on the project, rip it apart and restructure it in a couple days, but the realities of a big, old, fragile codebase, a 20 person team, and feature-bloated release schedule, and a lack of QA resources simply don't allow it.
Dmitry Kashin wrote:
Many other old EAPers were crying without them :)
Cheers,
Dmitry
P.S.
What does TIA mean in this context?
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Hi Dmitry,
Of cource I mean it too. EAPers so sentimental.
As noticed in http://www.intellij.net/forums/thread.jsp?forum=42&thread=90187&tstart=0&trange=15#3313931 it can mean "http://www.acronymfinder.com/ ... "Terrorism Information Awareness"
Thanks In Advance,
Dmitry