Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Referenced Projects as Build Path 
So...
I get it working, I closed my already existing project and opened it again and it finally worked. So, there is something not working smoothly, however I'm happy this functionality is already built in. If I have a good idea for the UI I post into the respective bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=444226 

Thanks

Am 08.05.15 um 18:56 schrieb Thomas Gossmann:

David,

this is weird. I tried your example, it worked. I tried it with a
project already present in my eclipse, it didn't...

To be exactly: https://github.com/gossi/collection I have checked it
out, run composer install (to get all require-dev in) and referenced
this project from my project, which didn't get me auto-completion.

PS: I get this discussion back into pdt-dev (was using a wrong
email-address last time)

Am 08.05.15 um 18:26 schrieb Dawid Pakuła:

Hi,

prepare two PHP projects:
1. Parent
   Single index.php file in root (root marked as build path)
2. Module
   Single User.php in root with class User (root marked as build path)

Go to parent project preferences, include path, select projects tab, add
module project and save. Your .buildpath file should update.
Now You can open index.php and write, new |, User should be on the list

Current state it’s completely inconsistent, because :
1. Sources tab, it’s just include path
2. Projects tab add projects to build path
3. Libraries add libs and external dirs to build path
4. Build path tab operate only on build path source path (JDT class path
equivalent)

See also bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=444226

--
Dawid Pakuła
+48 795 996 064

On 8 May 2015 at 17:13:12, Thomas Gossmann (eclipse@xxxxxx
<mailto:eclipse@xxxxxx>) wrote:

> Hi,
>
> I give it a test-run. It works to add projects to the include list but
> that's for well... includes. That said I can type: include '<file|
> and trigger auto-complete at | position it will provide completions
> from included projects. What doesn't work is: $list = new |
> and trigger auto-complete here doesn't provide me with classes from
> included projects.
>
> Summary: include path != build path. Or did I do something wrong here?
>
> gossi
>
>
> Am 07.05.15 um 21:06 schrieb Dawid Pakuła:
> > Hi,
> >
> > as far as I know PDT support this, but because build path page
have own
> > place in php project preferences this is not clear.
> >
> > If you add project on include path page, will part of parent project
> > buildpath.
> >
> > --
> > Dawid Pakuła
> > +48 795 996 064
> >
> > On 7 May 2015 at 20:50:54, Thomas Gossmann (eclipse@xxxxxx
> > <mailto:eclipse@xxxxxx>) wrote:
> >
> > > Hey guys,
> > >
> > > I have an idea for PDT and would like to hear your feedback
about it.
> > > Eclipse supports referenced projects, in java you can even add
projects
> > > to the build path. I'd like to request the same for PDT. This is
> > > especially useful if project B is the dependency of project A.
Instead
> > > of having the build path entries twice in the IDE, this would
reduce it
> > > (I don't know anything about build path internals but I may rise
the
> > > idea it would result in a performance gain overall).
> > >
> > > Basically the ultimate idea (and that's basically why I am
writing) is
> > > that development with local dependencies runs through composer.
If I
> > > install a dependency which I can detect exists locally, it would
easy to
> > > add this project as build path instead of having entries in
there twice.
> > >
> > > I wrote an article about composer development with local
dependencies:
> > > http://gos.si/blog/composer-development-with-local-dependencies
> > >
> > > I hope someday this is working, with support from the Composer
Plugin
> > > handling all the references (See [1]). So, yes this is thought
ahead to
> > > an uncertain time in the future (if it ever gets there).
> > >
> > > gossi
> > >
> > > [1] https://github.com/composer/composer/issues/4011
> > > _______________________________________________
> > > pdt-dev mailing list
> > > pdt-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or
> > > unsubscribe from this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/pdt-dev
> >
> >
> > _______________________________________________
> > pdt-dev mailing list
> > pdt-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/pdt-dev
> >
>


_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev

Back to the top