Home » Newcomers » Newcomers » Building into /com
| Building into /com [message #173014] |
Fri, 29 September 2006 13:49  |
Eclipse User |
|
|
|
Originally posted by: djb.email.gmail.com
Hello,
I am working with packages in a project that are setup something like
"com.abc.def". I am trying to migrate from our current IDE to eclipse, but
I run into problems caused by this naming convention. If my project is
named, say, MyProject and I specify the build path to be MyProject/com,
then all source will be in MyProject/com/com/abc/def, where I just want it
to be MyProject/com/abc/def, and I can't specify the build path to just be
/com because there is a conflict because all the source is in
MyProject/src.
I hope you see what I am trying to explain, does anyone have any ideas,
besides going back and renaming all of the packages?
|
|
|
| Re: Building into /com [message #173228 is a reply to message #173014] |
Mon, 02 October 2006 19:22  |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Dan B wrote:
> Hello,
> I am working with packages in a project that are setup something
> like "com.abc.def". I am trying to migrate from our current IDE to
> eclipse, but I run into problems caused by this naming convention. If my
> project is named, say, MyProject and I specify the build path to be
> MyProject/com, then all source will be in MyProject/com/com/abc/def,
> where I just want it to be MyProject/com/abc/def, and I can't specify
> the build path to just be /com because there is a conflict because all
> the source is in MyProject/src.
> I hope you see what I am trying to explain, does anyone have any ideas,
> besides going back and renaming all of the packages?
>
It is not really an issue of package naming, but rather that you want to
use the project root as the build output location. I could go into a
long rant about why that is a pretty bad idea, but the bottom line is
that Eclipse will not let you do that if you have source folders under
the project root, too.
I don't like to say this (because people usually don't take the advice
very well) but my overwhelming recommendation would be to "fix" your
project organization so that it uses a subdirectory of the project root
as the build location, instead of wanting to use the project root
itself. Not only will that satisfy Eclipse but it will be a more
standard and better organized project in general.
--
Hope this helps,
Eric
|
|
|
| Re: Building into /com [message #173370 is a reply to message #173228] |
Tue, 03 October 2006 11:02 |
| Eclipse User |
|
|
|
Originally posted by: dbeaulieu.byallaccounts.com
Thank you for the reply, I was afraid that is what I was going to hear.
This isn't something I can really change, as any changes I could make would
affect the build on production,
which I am not responsible for.
Also, I cross posted this into platform, just so you know, but thanks for
the help.
"Eric Rizzo" <eclipse4@rizzoweb.com> wrote in message
news:efs6jq$qli$1@utils.eclipse.org...
> Dan B wrote:
>> Hello,
>> I am working with packages in a project that are setup something like
>> "com.abc.def". I am trying to migrate from our current IDE to eclipse,
>> but I run into problems caused by this naming convention. If my project
>> is named, say, MyProject and I specify the build path to be
>> MyProject/com, then all source will be in MyProject/com/com/abc/def,
>> where I just want it to be MyProject/com/abc/def, and I can't specify the
>> build path to just be /com because there is a conflict because all the
>> source is in MyProject/src.
>> I hope you see what I am trying to explain, does anyone have any ideas,
>> besides going back and renaming all of the packages?
>>
>
> It is not really an issue of package naming, but rather that you want to
> use the project root as the build output location. I could go into a long
> rant about why that is a pretty bad idea, but the bottom line is that
> Eclipse will not let you do that if you have source folders under the
> project root, too.
> I don't like to say this (because people usually don't take the advice
> very well) but my overwhelming recommendation would be to "fix" your
> project organization so that it uses a subdirectory of the project root as
> the build location, instead of wanting to use the project root itself. Not
> only will that satisfy Eclipse but it will be a more standard and better
> organized project in general.
>
> --
> Hope this helps,
> Eric
|
|
|
| Re: Building into /com [message #173774 is a reply to message #173370] |
Fri, 06 October 2006 16:12 |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Dan B wrote:
> Thank you for the reply, I was afraid that is what I was going to hear.
> This isn't something I can really change, as any changes I could make would
> affect the build on production,
> which I am not responsible for.
> Also, I cross posted this into platform, just so you know, but thanks for
> the help.
Well, almost everything is work-aroundable when your hands are
completely tied. You might want to consider using linked resources for
your source directory.
Having said that, it seems that moving the build output for a project
into a sub-directory is a relatively minor change (not to mention good
for sanity ;-) - would it not be possible to discuss that change with
your team or whomever it is that would have to adapt?
BTW, aren't you using the same build script/process for production
builds as you are for development builds? If not, well I won't wave the
righteous finger at you, but you know that is a "best practice" in
general...
--
Hope this helps,
Eric
|
|
|
Goto Forum:
Current Time: Wed Jul 16 21:51:35 EDT 2025
Powered by FUDForum. Page generated in 0.11764 seconds |
Home