| Inclusions of only certain packages. [message #68168] |
Thu, 26 June 2003 11:30  |
Eclipse User |
|
|
|
Originally posted by: alan_wood.yahoo.com
Okay, I have a java project. It has one source dir, and I can setup
exclusions on the project so that I only get the packages I want. However,
in this case it is VERY cumbersome to do this.
My dir tree looks like this (and can't be modified since eclipse has to
co-exist with other tools)
ProjectDir (No project here for eclipse)
eclipse
BaseJar (Project for "base" packages)
AuxJar (Project for "aux" packages)
source
java
com
businessname
package1
auxpackage
package2
auxpackage
package3
auxpackage
Okay, each project links to the source dir via a path variable. So far so
good.
The first project (BaseJar) is easy to define.
Sourcepath = ProjectDir/source/java
Exclusions = **/auxpackage/
The second project is a pain....
Sourcepath = ProjectDir/source/java
Exclusions = **/businessname/package1/*
**/businessname/package2/*
**/businessname/package3/*
Can a feature be put in to do this:
Sourcepath = ProjectDir/source/java
Exclusions = **
Inclusions = **/auxpackage/
??
Seems more orthogonal and would help my situation tremendously.
Is there another way to specify what packages you want besides excluding the
ones you don't want? (Packages in the base level are added all the time for
us, and we have to manage that exlusion list now)
Alan
|
|
|
|
| Re: Inclusions of only certain packages. [message #70958 is a reply to message #70914] |
Tue, 01 July 2003 09:53  |
| Eclipse User |
|
|
|
Sorry Alan, there is nothing to ease the pain right now. Inclusion filters
are considered for 3.0 (see
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.0/m
ain.html#release-plan)
Jerome
"Alan Wood" <alan_wood@yahoo.com> wrote in message
news:bds1tc$41o$1@rogue.oti.com...
> Does anyone have any suggestions on this problem?
>
> Alan
>
> "Alan Wood" <alan_wood@yahoo.com> wrote in message
> news:bdf3j9$kg9$1@rogue.oti.com...
> > Okay, I have a java project. It has one source dir, and I can setup
> > exclusions on the project so that I only get the packages I want.
> However,
> > in this case it is VERY cumbersome to do this.
> >
> > My dir tree looks like this (and can't be modified since eclipse has to
> > co-exist with other tools)
> >
> > ProjectDir (No project here for eclipse)
> > eclipse
> > BaseJar (Project for "base" packages)
> > AuxJar (Project for "aux" packages)
> >
> > source
> > java
> > com
> > businessname
> > package1
> > auxpackage
> > package2
> > auxpackage
> > package3
> > auxpackage
> >
> > Okay, each project links to the source dir via a path variable. So far
so
> > good.
> >
> > The first project (BaseJar) is easy to define.
> > Sourcepath = ProjectDir/source/java
> > Exclusions = **/auxpackage/
> >
> > The second project is a pain....
> > Sourcepath = ProjectDir/source/java
> > Exclusions = **/businessname/package1/*
> > **/businessname/package2/*
> > **/businessname/package3/*
> >
> > Can a feature be put in to do this:
> > Sourcepath = ProjectDir/source/java
> > Exclusions = **
> > Inclusions = **/auxpackage/
> >
> > ??
> >
> > Seems more orthogonal and would help my situation tremendously.
> >
> > Is there another way to specify what packages you want besides excluding
> the
> > ones you don't want? (Packages in the base level are added all the time
> for
> > us, and we have to manage that exlusion list now)
> >
> > Alan
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04176 seconds
Home