Description
Objective:
Motivation:
- support for custom solr/contrib/...-myteam modules where the custom modules have dependencies between them and the package structure is com.mycompany.myteam rather than org.apache.solr
Approach:
- step 1:
- in GetMavenDependenciesTask.java build a map out of all the ivy.xml files' info elements e.g.
<ivy-module version="2.0"> <info organisation="org.apache.lucene" module="core"/> </ivy-module>
- temporarily instrument GetMavenDependenciesTask.java to help determine how the info element mappings differ from the current in-code logic
- in GetMavenDependenciesTask.java build a map out of all the ivy.xml files' info elements e.g.
- step 2:
- adjust selected ivy.xml files to minimise differences
- step 3:
- switch over to 'new way' logic where this matches current in-code logic
- remove the temporary instrumentation