Community
Participate
Working Groups
Comparator in latest (M5) bases builder, apparently, flags a different "difference" than in the past ... specifically The manifest header "Eclipse-SourceReferences" has different values. This is (I think) normal (or, normal given other changes in "source references" format, so should be filtered out, I suspect. Or ... ntitai ... if it does represent a desired changed in format, we may need to retag everything to pick up the change?
This actually reveals a bug in our scripts. Sort of. I had changed scripts to use ":local" in place of ":pserver:dev.eclipse.org:" but now the "scm" statement is wrong. Can not longer be used to "import source". I'll change it back and/or find out if there is a safe place to change it to "local" or change it back to ":pserver:dev.eclipse.org:". new Eclipse-SourceReferences: scm:cvs:local:/cvsroot/webtools:sourceeditin g/plugins/org.eclipse.wst.html.ui;tag=v201101252005 old Eclipse-SourceReferences: scm:cvs:pserver:dev.eclipse.org:/cvsroot/web tools:sourceediting/plugins/org.eclipse.wst.html.ui;tag=v201101252005
I have changed back to not do a "re write" of map files, so :pserver:dev.eclipse.org: stays as it is. One consequence, though, is that now some bundles still have :local" in them, and will have to be retagged to pick up the now fixed bundles as being "more recent". I opened bug 338298 for org.eclipse.jpt.common.eclipselink.core org.eclipse.jpt.common.utility.tests I can re-tag these two: org.eclipse.wst.ws.explorer org.eclipse.wst.xml.xpath2.processor.tests
I've now retagged org.eclipse.wst.ws.explorer org.eclipse.wst.xml.xpath2.processor.tests
