What does "Exclude exploded directorey from module content" do?

Does it run the module from your development directory directly? Isn't
this like not having an exploded directory? What is the benefit?

0
15 comments
Avatar
Permanently deleted user

Hi,

If we have separate web resource directory and exploded dir then the
same files are present in two places (e.g. jsps). To avoid confusion
(which file to edit) exploded directory is excluded from module source,
this would mean that we will see only one instance of the web resource
files.

Norris Shelton wrote:

Does it run the module from your development directory directly? Isn't
this like not having an exploded directory? What is the benefit?

0
Avatar
Permanently deleted user

Don’t know about you guys,
i some times use this to have a exploded environment in my Jboss server apart from that it gives me an over view of how things might look if all is build well if you have your sources spread accross various modules and physical locations

cheers,
parthi

0
Avatar
Permanently deleted user

Hi,

Deployment View in J2EE pane should suite this aim. Have you tried it?

parthis wrote:

Don?t know about you guys,
i some times use this to have a exploded environment in my Jboss server apart from that it gives me an over view of how things might look if all is build well if you have your sources spread accross various modules and physical locations

cheers,
parthi

0
Avatar
Permanently deleted user

yup and it works great. I used to exclude the directory from the paths, it's better to not be setting breakpoints in those jsps and such, better for people to use the original files for it all.

R

0
Avatar
Permanently deleted user

I still don't get it. I have always had my web resource directory as my
development directory and the exploded directory is where my external
tomcat pulls it's sources (sans CVS, etc). I have never had a problem
with this. How could you set-up a break point in one of the exploded
files? Mine don't even show up in CTRL-N or CTRL-SHIFT-N.

Robert S. Sfeir wrote:

>yup and it works great. I used to exclude the directory from the paths, it's better to not be setting breakpoints in those jsps and such, better for people to use the original files for it all.
>
>R

>

0
Avatar
Permanently deleted user

k...

I have my files in the order of:

jsps
media
images
css
resources
database
oracle
postgresql
ojb
ojb files here
struts
struts files here
web.xml
src
src-test

obviously this structure is not gonna work as is.

So when I deploy it builds the proper structure in a directory I call webroot. So that webroot has all the same files in the directories above, but only the files appropriate for the db/app combo I am running.

Now I can see my webroot directory in the list of files in the project pane, and to me that's useless. I know the directory's structure is OK because I can look in the J2EE tab in the project pane, and see what the structure of my deployment is/going to be.

The second thing that used to happen, is that by mistake I'd look in the webroot directory for the jsp file with the problem and set breakpoints in there, that caused me headaches.

Now from a seasoned idea developer's point of view, I think this is a 'so what' kind of reaction, from a novice user, hiding that directory by default would removed the issue of 'why is my stuff there and not here, and why is there this dir or that dir'.

It doesn't make anything better or worse, it just provides you with a way you're comfortable working.

Hope that makes more sense.
R

0
Avatar
Permanently deleted user

Hi,
For the breakpoints use the files in your source/resource directories.

Norris Shelton wrote:

I still don't get it. I have always had my web resource directory as my
development directory and the exploded directory is where my external
tomcat pulls it's sources (sans CVS, etc). I have never had a problem
with this. How could you set-up a break point in one of the exploded
files? Mine don't even show up in CTRL-N or CTRL-SHIFT-N.

Robert S. Sfeir wrote:

>> yup and it works great. I used to exclude the directory from the
>> paths, it's better to not be setting breakpoints in those jsps and
>> such, better for people to use the original files for it all.
>>
>> R
>>
>>


--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Avatar
Permanently deleted user

After reading Robert's response, I think I get it.

This is for people who an exploded directory that is the web resource
directory. Is that correct?

Maxim Mossienko wrote:

Hi,

>

If we have separate web resource directory and exploded dir then the
same files are present in two places (e.g. jsps). To avoid confusion
(which file to edit) exploded directory is excluded from module
source, this would mean that we will see only one instance of the web
resource files.

>

Norris Shelton wrote:

>
>> Does it run the module from your development directory directly?
>> Isn't this like not having an exploded directory? What is the benefit?
>

0
Avatar
Permanently deleted user

No,
When they differ (otherwise we still have one copy of the file and there
is no multiple file copies problem).

Norris Shelton wrote:

After reading Robert's response, I think I get it.

This is for people who an exploded directory that is the web resource
directory. Is that correct?

Maxim Mossienko wrote:

>> Hi,
>>
>> If we have separate web resource directory and exploded dir then the
>> same files are present in two places (e.g. jsps). To avoid confusion
>> (which file to edit) exploded directory is excluded from module
>> source, this would mean that we will see only one instance of the web
>> resource files.
>>
>> Norris Shelton wrote:
>>
>>> Does it run the module from your development directory directly?
>>> Isn't this like not having an exploded directory? What is the benefit?
>>
>>


--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Avatar
Permanently deleted user

If I follow this correctly, it is when both the web resource directory
and the exploded directory are found beneath the content root directory
and a copy of the exploded web directory is deployed to the app server.

Maxim Mossienko wrote:

No,
When they differ (otherwise we still have one copy of the file and there
is no multiple file copies problem).

Norris Shelton wrote:

>> After reading Robert's response, I think I get it.
>>
>> This is for people who an exploded directory that is the web resource
>> directory. Is that correct?
>>
>> Maxim Mossienko wrote:
>>
>>> Hi,
>>>
>>> If we have separate web resource directory and exploded dir then the
>>> same files are present in two places (e.g. jsps). To avoid confusion
>>> (which file to edit) exploded directory is excluded from module
>>> source, this would mean that we will see only one instance of the web
>>> resource files.
>>>
>>> Norris Shelton wrote:
>>>
>>>> Does it run the module from your development directory directly?
>>>> Isn't this like not having an exploded directory? What is the benefit?
>>>
>>>
>>>


0
Avatar
Permanently deleted user

Hi,
Consider example dir layout (current default for web module):
- Module Content Root
- Src (java)
- Web Resource (jsp, etc)
- Exploded (Excluded)
- WEB-INF
- classes

Since during build web resource are copied into exploded dir then there
are two places where our jsp could be : web resource and exploded
directory. To fight the problem the exploded directory is excluded (The
exploded directory is mounted for local j2ee server context).




Tim Haley wrote:

If I follow this correctly, it is when both the web resource directory
and the exploded directory are found beneath the content root directory
and a copy of the exploded web directory is deployed to the app server.

Maxim Mossienko wrote:

>> No,
>> When they differ (otherwise we still have one copy of the file and
>> there is no multiple file copies problem).
>>
>> Norris Shelton wrote:
>>
>>> After reading Robert's response, I think I get it.
>>>
>>> This is for people who an exploded directory that is the web resource
>>> directory. Is that correct?
>>>
>>> Maxim Mossienko wrote:
>>>
>>>> Hi,
>>>>
>>>> If we have separate web resource directory and exploded dir then the
>>>> same files are present in two places (e.g. jsps). To avoid confusion
>>>> (which file to edit) exploded directory is excluded from module
>>>> source, this would mean that we will see only one instance of the
>>>> web resource files.
>>>>
>>>> Norris Shelton wrote:
>>>>
>>>>> Does it run the module from your development directory directly?
>>>>> Isn't this like not having an exploded directory? What is the
>>>>> benefit?
>>>>
>>>>
>>>>
>>>>
>>
>>


--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Avatar
Permanently deleted user

Thanks. Now I get it. That is how JBuilder does their projects. I
didn't really care for the extra complexity, with no apparent benefit.
People who have their projects arranged like this should love that feature.

Maxim Mossienko wrote:

Hi,
Consider example dir layout (current default for web module):
- Module Content Root
- Src (java)
- Web Resource (jsp, etc)
- Exploded (Excluded)
- WEB-INF
- classes

>

Since during build web resource are copied into exploded dir then
there are two places where our jsp could be : web resource and
exploded directory. To fight the problem the exploded directory is
excluded (The exploded directory is mounted for local j2ee server
context).

>
>
>
>

Tim Haley wrote:

>
>> If I follow this correctly, it is when both the web resource
>> directory and the exploded directory are found beneath the content
>> root directory and a copy of the exploded web directory is deployed
>> to the app server.
>>
>> Maxim Mossienko wrote:
>>
>>> No,
>>> When they differ (otherwise we still have one copy of the file and
>>> there is no multiple file copies problem).
>>>
>>> Norris Shelton wrote:
>>>
>>>> After reading Robert's response, I think I get it.
>>>>
>>>> This is for people who an exploded directory that is the web
>>>> resource directory. Is that correct?
>>>>
>>>> Maxim Mossienko wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> If we have separate web resource directory and exploded dir then
>>>>> the same files are present in two places (e.g. jsps). To avoid
>>>>> confusion (which file to edit) exploded directory is excluded from
>>>>> module source, this would mean that we will see only one instance
>>>>> of the web resource files.
>>>>>
>>>>> Norris Shelton wrote:
>>>>>
>>>>>> Does it run the module from your development directory directly?
>>>>>> Isn't this like not having an exploded directory? What is the
>>>>>> benefit?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>

0
Avatar
Permanently deleted user

We do love it :)
It's incredibly useful when you work with portlets.
R

0
Avatar
Permanently deleted user

yes i have,
i just use it to give a kind of side effect to make the exploded dir as an exploded environment in my jboss server too since i can edit jsp's and make other small significant changes which can have an immediate effect without having to re-start my server.

Yes it some times feels like things which are meant to be used for something else are ended up used for something else,
I guess it boil downs to your choice and the amount of comfortableness you have over a particular feature.

gujals,
parthi


0
Avatar
Permanently deleted user

Hi, Excluding exploded directory setting is OPTIONAL, you can use set it
to whatever you want.

parthis wrote:

yes i have,
i just use it to give a kind of side effect to make the exploded dir as an exploded environment in my jboss server too since i can edit jsp's and make other small significant changes which can have an immediate effect without having to re-start my server.

Yes it some times feels like things which are meant to be used for something else are ended up used for something else,
I guess it boil downs to your choice and the amount of comfortableness you have over a particular feature.

gujals,
parthi




--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Please sign in to leave a comment.