| source attachment with variable path [message #147512] |
Fri, 05 March 2004 14:14  |
|
Originally posted by: jpianezze.telephia.com
I want to attach source to a jar library.
It appears to be impossible to specify a source location relative to a
variable path name.
I can specify a location in the workspace, but the source is not usually in
the workspace.
I can specify a location somewhere in the file system, but I get a
hard-coded path in the .classpath file.
There are two types of such variables:
1. Linked Resources
2. Classpath variables.
It's not a classpath, it's really a linked resource. I can create a link for
each external toolkit for which I want to specify source, but this seems to
be a waste, and clutters the project.
John Pianezze
|
|
|
|
| Re: source attachment with variable path [message #147815 is a reply to message #147726] |
Mon, 08 March 2004 18:47  |
|
Originally posted by: jpianezze.telephia.com
I tried that.
I define a "classpath variable" here:
Windows -> Preferences -> Java -> Classpath Variables
called "JUNIT_HOME"
The I choose the jar file, right-click, choose "java source attachment"
I type in JUNIT_HOME/junit3.8.1/src.jar
It says "the path ..... does not exist"
I tried $JUNIT_HOME
I tried %JUNIT_HOME%
When creating a new project, I can use this variable: "JUNIT_HOME" but after
that, it always uses the actual hard path ( i know this is a current feature
enhancement request)
Any other can you assist further?
John Pianezze
"Darin Wright" <Darin_Wright@ca.ibm.com> wrote in message
news:c2i0hn$fjv$1@eclipse.org...
> You can use a classpath variable for this. Create the variable, and then
> attach the source using the variable as the prefix of the source
attachment
> path.
>
> Darin
>
> "John Pianezze" <jpianezze@telephia.com> wrote in message
> news:c2ajbu$f4u$1@eclipse.org...
> > I want to attach source to a jar library.
> >
> > It appears to be impossible to specify a source location relative to a
> > variable path name.
> >
> > I can specify a location in the workspace, but the source is not usually
> in
> > the workspace.
> > I can specify a location somewhere in the file system, but I get a
> > hard-coded path in the .classpath file.
> >
> > There are two types of such variables:
> > 1. Linked Resources
> > 2. Classpath variables.
> >
> > It's not a classpath, it's really a linked resource. I can create a link
> for
> > each external toolkit for which I want to specify source, but this seems
> to
> > be a waste, and clutters the project.
> >
> > John Pianezze
> >
> >
>
>
|
|
|
| Re: source attachment with variable path [message #148152 is a reply to message #147815] |
Thu, 11 March 2004 09:19 |
 Darin Wright
Messages: 454
Registered: July 2009 |
Senior Member |
|
|
Not sure I fully understand the problem. Please file a bug with an explicit
test case.
Darin
"John Pianezze" <jpianezze@telephia.com> wrote in message
news:c2j0f6$r8q$1@eclipse.org...
> I tried that.
>
> I define a "classpath variable" here:
> Windows -> Preferences -> Java -> Classpath Variables
> called "JUNIT_HOME"
>
> The I choose the jar file, right-click, choose "java source attachment"
> I type in JUNIT_HOME/junit3.8.1/src.jar
> It says "the path ..... does not exist"
>
> I tried $JUNIT_HOME
> I tried %JUNIT_HOME%
>
> When creating a new project, I can use this variable: "JUNIT_HOME" but
after
> that, it always uses the actual hard path ( i know this is a current
feature
> enhancement request)
>
> Any other can you assist further?
> John Pianezze
>
>
>
> "Darin Wright" <Darin_Wright@ca.ibm.com> wrote in message
> news:c2i0hn$fjv$1@eclipse.org...
> > You can use a classpath variable for this. Create the variable, and then
> > attach the source using the variable as the prefix of the source
> attachment
> > path.
> >
> > Darin
> >
> > "John Pianezze" <jpianezze@telephia.com> wrote in message
> > news:c2ajbu$f4u$1@eclipse.org...
> > > I want to attach source to a jar library.
> > >
> > > It appears to be impossible to specify a source location relative to a
> > > variable path name.
> > >
> > > I can specify a location in the workspace, but the source is not
usually
> > in
> > > the workspace.
> > > I can specify a location somewhere in the file system, but I get a
> > > hard-coded path in the .classpath file.
> > >
> > > There are two types of such variables:
> > > 1. Linked Resources
> > > 2. Classpath variables.
> > >
> > > It's not a classpath, it's really a linked resource. I can create a
link
> > for
> > > each external toolkit for which I want to specify source, but this
seems
> > to
> > > be a waste, and clutters the project.
> > >
> > > John Pianezze
> > >
> > >
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.01639 seconds
] 
Search
Help
Register
Login
Home
