Adding source path but not to project

Go to the Libraries tab (under Project Properties > Main Module) and click
the "Add Named Library..." button. You'll get a dialog asking you to choose
the classes for the library; after that there's another one which lets you
specify a name for the library. Once you got the library added, you can
attach source and javadoc folders to it using the appropriate buttons on the
right.

Hope that helps,
Vil.

Aye Thu wrote:

I haven't found a way to add source files (so that I can look up source files of libraries) without adding it to the project as Content. This used to be possible but in the last 3 or 4 builds, the changes in the structure of the Project properties screen has confused me a bit.

--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

This is FAR from intuitive (if it works, and it didn't, the last time I tried it).

From what I can gather, the whole project files management area is still under construction, and what we see now is (I hope!) quite different from the planned/final version.

As shown currently, I personally find the various names highly unintuitive. For example, what is a named library? Why isn't it just a library? What is considered content? Is my web app considered content that is different from my ejb sources?

Going beyond that, I think that the current method of attaching source to binary jars is very, very cumbersome, and gets in the way more often than not. Some cases where it fails:

j2ee: I have my J2EE jars in separate jars, but one source tree for all of them. Currently I have to add the same source dir 8-9 times.

versioning: I often upgrade the binary jar file used (different name), but the source tree is in the same location. Here I am forced to readd the source tree every time the binary changes

Going beyond that, I think that the current method of attaching source to

binary jars is very, very cumbersome,

Adding libs with source and/or javadoc entries only would solve your problem
(I think).

Do you have other ideas on how it should be done?

Hani Suleiman wrote:

This is FAR from intuitive (if it works, and it didn't, the last time I tried it).

I agree to some extent, although I'm not sure what you mean when you say it
doesn't work. The process I described works fine for me. Note that you can
actually remove the classes jar file after the library has been created, so
it -is- possible to have a named library with only source/javadoc entries.

I don't understand why the process of adding a named library doesn't use the
same library configuration dialog as global and project libraries though.

From what I can gather, the whole project files management area is still under construction, and what we see now is (I hope!) quite different from the planned/final version.

As shown currently, I personally find the various names highly unintuitive. For example, what is a named library? Why isn't it just a library? What is considered content? Is my web app considered content that is different from my ejb sources?

Yes. JetBrains have reassured us a couple of times now that it will all make
sense when we finally have multiple-module support. As we don't have that
yet, it still seems a bit confusing. I have high hopes though, given their
track record! :)

Going beyond that, I think that the current method of attaching source to binary jars is very, very cumbersome, and gets in the way more often than not. Some cases where it fails:

j2ee: I have my J2EE jars in separate jars, but one source tree for all of them. Currently I have to add the same source dir 8-9 times.

You can add multiple jars to a library, which I think would solve your
problem. Unless you have a specific reason for having each jar in a separate
message, that is.

versioning: I often upgrade the binary jar file used (different name), but the source tree is in the same location. Here I am forced to readd the source tree every time the binary changes

You don't have to create a new library for the new jar: you could just
replace the jar in the existing library.

Vil.
--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

What do you mean by adding source files? Is it a library or what?

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"

"Aye Thu" <thua@usa.redcross.org> wrote in message
news:21749107.1060788596888.JavaMail.itn@is.intellij.net...

I haven't found a way to add source files (so that I can look up source

files of libraries) without adding it to the project as Content. This used
to be possible but in the last 3 or 4 builds, the changes in the structure
of the Project properties screen has confused me a bit.
>

Also popup windows(like Generate Code and About) seem to appear and

disappear real quick. The problem is sometimes solved by moving the main
window around.. could be just an OS X weird behavior.
>

Running 896 on OS X.
Thanks!
Aye

Note that you can
actually remove the classes jar file after the library has been created,

so

it -is- possible to have a named library with only source/javadoc entries.

It's probably a bug that it does allow this. Actually it makes no sense
cause IDEA will not allow referencing such sources from your project - it
needs class files for the library.

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Vilya Harvey" <vilya.harvey@digitalsteps.com> wrote in message
news:bhedc3$9po$1@is.intellij.net...

Hani Suleiman wrote:

This is FAR from intuitive (if it works, and it didn't, the last time I

tried it).
>

I agree to some extent, although I'm not sure what you mean when you say

it

doesn't work. The process I described works fine for me. Note that you can
actually remove the classes jar file after the library has been created,

so

it -is- possible to have a named library with only source/javadoc entries.

>

I don't understand why the process of adding a named library doesn't use

the

same library configuration dialog as global and project libraries though.

>

From what I can gather, the whole project files management area is still

under construction, and what we see now is (I hope!) quite different from
the planned/final version.

>

As shown currently, I personally find the various names highly

unintuitive. For example, what is a named library? Why isn't it just a
library? What is considered content? Is my web app considered content that
is different from my ejb sources?
>

Yes. JetBrains have reassured us a couple of times now that it will all

make

sense when we finally have multiple-module support. As we don't have that
yet, it still seems a bit confusing. I have high hopes though, given their
track record! :)

>

Going beyond that, I think that the current method of attaching source

to binary jars is very, very cumbersome, and gets in the way more often than
not. Some cases where it fails:

>

j2ee: I have my J2EE jars in separate jars, but one source tree for all

of them. Currently I have to add the same source dir 8-9 times.
>

You can add multiple jars to a library, which I think would solve your
problem. Unless you have a specific reason for having each jar in a

separate

message, that is.

>

versioning: I often upgrade the binary jar file used (different name),

but the source tree is in the same location. Here I am forced to readd the
source tree every time the binary changes
>

You don't have to create a new library for the new jar: you could just
replace the jar in the existing library.

>

Vil.
--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

>

Disclaimer

>

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

>

By default I have the library JAR file in my apps LIB directory but the source files for the library exist somewhere else. So when I "jump" to one of the library's class file, it shows me the interface based on the JAR file. I want it to jump to the actually implementation source file.

I know it would be much simpler if the libray JAR file already contained the source but I have no control over the third party JAR which comes separate (classes and source). Hope this explains better.

Thanks!
Aye

Just go to the Project Properties, select the library jar in the "Libraries"
tab and click "Attach Source" button.

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"

"Aye Thu" <thua@usa.redcross.org> wrote in message
news:25376673.1061172088362.JavaMail.itn@is.intellij.net...

By default I have the library JAR file in my apps LIB directory but the

source files for the library exist somewhere else. So when I "jump" to one
of the library's class file, it shows me the interface based on the JAR
file. I want it to jump to the actually implementation source file.
>

I know it would be much simpler if the libray JAR file already contained

the source but I have no control over the third party JAR which comes
separate (classes and source). Hope this explains better.
>

Thanks!
Aye