[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.platform] Re: Source locations in target platform use absolute paths

Ed, thanks, I'm with you now!

On Thu, 19 Apr 2007 08:05:21 -0400, Ed Merks wrote:

> Petra,
> 
> All of us building plugins at Eclipse have this working the way I
> described.  I would expect your .classpath file to look something like
> this:
> 
>     <?xml version="1.0" encoding="UTF-8"?> <classpath>
>         <classpathentry kind="src" path="src"/> <classpathentry kind="con"
>     path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
>         <classpathentry kind="con"
>     path="org.eclipse.pde.core.requiredPlugins"/>
>         <classpathentry kind="output" path="bin"/>
>     </classpath>
> 
> There should be nothing in your project that prevents you from committing
> it to CVS and extracting it anywhere else.  As I say, we all do this
> today.  When a plugin is extracted from CVS, or extracted from an archive
> for that matter, the PDE will resolve all the required plugins (because of
> org.eclipse.pde.core.requiredPlugins) and compute the appropriate
> classpath for that installation.
> 
> What specifically are you seeing as a problem?