-- bumping to dev@ -- tl;dr Is it possible to write a test that validates a project has all its dependencies correct in the project.xml ?
The Apache Cassandra project has a netbeans project file ref: https://github.com/apache/cassandra/tree/trunk/ide/nbproject When the project adds/removes/updates dependencies in its ant build.xml file, we don't always remember to also update the netbeans project file. (Freeform projects don't support classpath wildcards afaik.) I'd like to write a simple unit test that ensures the netbeans project file is kept up to date, specifically that no error badges will exist on packages or files when opening the project in netbeans. I don't care if this is done via a command line script, or programmatically in a java unit test. regards, Mick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
