01ea35ccb7
This change affects both top-level subdirectory names as well as Eclipse plug-in feature names. Perhaps it would have been possible to change only the latter, but I don't like the idea of the two being different. These name changes fix three Eclipse plug-in warnings of the form: Illegal value '...-feature' for attribute 'id'. Legal token characters are "a-z", "A-Z", "0-9", "_". Tokens must be separated by "." I'll be the first to admit that I know nearly nothing about Eclipse plug-in development. If changing these plug-in feature IDs has broader implications that the automated regression tests won't detect, then I probably overlooked them too. I would greatly appreciate skeptical review of this change by someone who knows Eclipse plug-in development well. Note that personal Eclipse workspaces may need some manual adjustment after this change. The three "...-feature" Eclipse projects should be removed from the workspace, and the three corresponding "..._feature" Eclipse projects should be added. If you do your git pull using Eclipse's team features, perhaps it is smart enough to do this for you? I don't know, but it wouldn't surprise me if fixing things manually were still needed even in that case.
15 lines
588 B
XML
15 lines
588 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
|
|
<modelVersion>4.0.0</modelVersion>
|
|
<parent>
|
|
<artifactId>WALA</artifactId>
|
|
<groupId>com.ibm.wala</groupId>
|
|
<version>0.0.1-SNAPSHOT</version>
|
|
</parent>
|
|
<groupId>com.ibm.wala</groupId>
|
|
<artifactId>com.ibm.wala.tests.ide</artifactId>
|
|
<version>1.1.3-SNAPSHOT</version>
|
|
<packaging>eclipse-feature</packaging>
|
|
</project>
|