Hi Dave, Hi Martin,

I’ve noticed today that the Kepler Release download location, http://download.eclipse.org/releases/kepler, does contain all TM Terminal Features except the org.eclipse.tm.terminal.core.sdk feature. However the TM Terminal Core SDK feature is the one we reference from the TCF Target Explorer project. Could this please be fixed?

Thanks, Best regards, Uwe J

Hi Dave,

I did this in the /home/data/httpd/download.eclipse.org/tools/tm area:

chgrp -R tools.tm .

chmod -R g+w .

This should give you permission on all the items that were owned by me.

A couple of items are still owned by others:

> find . -type d -ls | grep -v tools.tm

167690677    4 drwxrwxr-x   4 adushistova common       4096 Mar 24 21:36 ./builds

167692328    4 drwxrwxr-x   2 hudsonBuild callisto-dev     4096 May 31 16:46 ./builds/kepler/nightly/features

170196993    4 drwxrwxr-x   3 ddykstal common       4096 Jan 13 08:32 ./builds/juno/milestones

167690679    4 drwxrwxrwx   7 adushistova common       4096 May 22 17:35 ./builds/juno/nightly

167706651    4 drwxrwxr-x   2 hudsonBuild callisto-dev     4096 May 22 17:35 ./builds/juno/nightly/features

174596602    4 drwxr-xr-x   5 ddykstal common       4096 Feb 12 17:34 ./updates/3.4milestones/SR2_RC4b

170450945    4 drwxr-xr-x   5 ddykstal common       4096 Feb  7 11:48 ./updates/3.4milestones/SR2_RC4a

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

-----Original Message-----
From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx] On Behalf Of David Dykstal
Sent: Monday, June 10, 2013 12:07 AM
To: Target Management developer discussions
Subject: [tm-dev] downloads area cleanup

Martin --

I will be cleaning up our downloads area (archiving or deleting old

builds) over the next two weeks in preparation for GA. I suspect I will have some questions about why stuff is organized the way it is and what is safe to remove. There are some cases in the download area where I don't have permission to delete and will need you to take care of that.

We'll discuss over this mailing list if necessary.

-- Dave

_______________________________________________

tm-dev mailing list

tm-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/tm-dev

Hi Dave,

I haven’t tried that plugin myself, but I think the idea of it is that it “always runs” while editing code.

It decorates the project explorer with problem markers; so you should fix those before committing a change that affects versions.

you don’t run that plugin separately and you can’t integrate it with the build.

So this is something that we would run prior to a commit.

We should probably get into the habit of correctly updating version numbers in the first commit for a plugin after a release. I see several cases in the log where we updated the version numbers in a separate commit.

Hi all,

Remember that we discussed issues with POM.XML versions not matching MANIFEST.MF in the TM build ?

Here’s a tool from the Eclipse Platform / PDE team, to make sure that the versions in MANIFEST.MF and POM.XML match.

Hi,

The POM Version tool will warn you if the artifact version in a POM file (pom.xml) does not match the bundle version in the manifest (manifest.mf).  Having different versions in a bundle will cause the Eclipse builder to fail.

The tool was originally added to the PDE builder, but for the Kepler release it has been moved to Eclipse Releng Tools.  Eclipse Releng Tools can be installed from the Eclipse Project Updates p2 repository (http://download.eclipse.org/eclipse/updates/4.3-I-builds/).

The POM Version tool is off by default.  Go to Preferences > POM Version Tool and change the severity to error or warning to enable it for your workspace.

Curtis