[news.eclipse.tools.jdt] Re: Use of variables on org.eclipse.jdt.launchi

[Clebert Suconic <clebert.suconic@xxxxxxxxx>]

This is buggy actually...

I set the variable, right click on the test... it works...


then I go to the run button (next to the debug button), and I get an 
error... Variable project_name not defined.



On 08/21/2009 10:37 AM, Clebert Suconic wrote:
> I found a way...
>
>
> I could define it as:
>
> <attribute
> name="org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY"
> value="${project_name}/native/bin"/>
>
>
>
> However.. there is a bug on the user interface. It tells me: Project
> location doesn't exist.. but it works fine when I run the test.
>
>
>
>
> On 08/20/2009 06:40 PM, Clebert Suconic wrote:
> > I'm using org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY at
> > my project, to bind the JNI directory used on the testsuite.
> >
> >
> > It happens that (as documented) the JNI path defined here is relative to
> > the worksapce.
> >
> >
> > However, I have no control of how my project will be downloaded on the
> > workspace. A developer may call it trunk, others may call it messaging,
> > jbm, or bananas.. whatever.. I have no control.
> >
> >
> > You can download my project and check how it is set if you want:
> >
> > svn co http://anonsvn.jboss.org/repos/messaging/trunk/
> >
> >
> > if you look at the .classpath:
> >
> > http://anonsvn.jboss.org/repos/messaging/trunk/.classpath
> >
> >
> > If the user checks out the trunk as messaging, or jbm, or
> > jbossmessaging. The binding to JNI won' t work.
> >
> >
> > It would be better if the JNI path here was related to the project. but
> > as that' s not possible. is there a way to use a variable that would
> > return the project name?
> >
> >
> > I couldn't find anywhere. I couldn't find an easy documented list of
> > pre-defined variables. Or maybe there isn' t such thing?
> >
> >
> >
> > Thanks, and I appreciate for any help.
> >
> >
> > Clebert