Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Shared Source Code Attachments

Shared Source Code Attachments [message #507739]

Thu, 14 January 2010 09:15

Eclipse User

I'm working at a team of software developers and we are Planing to use JDT for our future development.To version / share our code we are using SVN.

But I got to problem while setting up a base framework.
Our software will need many foreign libraries ( eg. Spring, AspectJ, ...).
In order to ease the debugging of errors, I have set source Attachments to all Libraries we are using.

But now I realize that this source attachments are not stored within the project. But I found the definition within the Eclipse Workspace .metadata in the "classpath.decorations.xml" file.

Is there ANY way to share this "source attachments" within the other developers? The best solution would be if i could add it to SVN anyway.

Thanks for helping.

Regards

Re: Shared Source Code Attachments [message #507887 is a reply to message #507739]

Thu, 14 January 2010 20:30

Eclipse User

bast.ralf@gmail.com wrote:
> I'm working at a team of software developers and we are Planing to use
> JDT for our future development.To version / share our code we are using
> SVN.
>
> But I got to problem while setting up a base framework.
> Our software will need many foreign libraries ( eg. Spring, AspectJ, ...).
> In order to ease the debugging of errors, I have set source Attachments
> to all Libraries we are using.
>
> But now I realize that this source attachments are not stored within the
> project. But I found the definition within the Eclipse Workspace
> .metadata in the "classpath.decorations.xml" file.
>
> Is there ANY way to share this "source attachments" within the other
> developers? The best solution would be if i could add it to SVN anyway.
>
> Thanks for helping.
>
> Regards
Source attachments are stored in the .classpath file. Make sure to
check the .classpath file into SVN.

You should be aware that unless the source path is within your project,
the source attachment will be an absolute path that may not be valid on
all developers workstations.

To get around this limitation, you can create a Resource link using a
variable to point to the source directory. You can then select the
linked folder from the Workspace on the attach source dialog.

Re: Shared Source Code Attachments [message #507913 is a reply to message #507887]

Fri, 15 January 2010 02:31

Eclipse User

Hmm, thats confusing me.

I've tried everything, but the source Attachment won't be stored in the .classpath.

Is there any option that i have to set, in order to store the source attachments in the .classpath file?

Or can someone simply give me the XML Tags, then i will add them manually.

Thanks.

Re: Shared Source Code Attachments [message #508101 is a reply to message #507913]

Fri, 15 January 2010 16:47

Eclipse User

<bast.ralf@gmail.com> wrote in message
news:hip5le$tra$1@build.eclipse.org...
> Hmm, thats confusing me.
>
> I've tried everything, but the source Attachment won't be stored in the
> .classpath.
>
> Is there any option that i have to set, in order to store the source
> attachments in the .classpath file?
>
> Or can someone simply give me the XML Tags, then i will add them
> manually.
>
> Thanks.

I think we're talking about two different concepts. I was talking about
adding external jar files to the classpath directly. I'm thinking that you
were talking about User Libraries defined in the Preferences area.

I haven't use User Libraries before. I've looked at them, but they don't
appear to be friendly to sharing between developers. Adding jar files
directly to the project or through linked resources allows you to specify
their location relative to a variable. This makes sharing them with
different developers much easier.

Re: Shared Source Code Attachments [message #516357 is a reply to message #507739]

Tue, 23 February 2010 12:19

Eclipse User

If you specify jar files as JAVA EE Module dependencies -> Web libraries, eclipse wtp would publish them in web-inf/lib if you run the web project under tomcat etc.

If you then go to java build path-> Libraries tab, you could add source attachment

This ends up being in classpath.decorations.xml in .metadata

not nice, because I cant add this to svn

Is there any solution to this problem?

Previous Topic:	Problem in configuring Tomcat5.5 Server
Next Topic:	using variable in build output path

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Apr 17 15:32:26 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter