Should I change the artifact names? How choose group artifact and version names?
Keep the groupId and artifactId of the module(s) you change the same, but use a qualifier on the version to ensure that it is obvious it is a non-standard version, for example 1.0.0-simon. This is pretty common practice.
Should I import the whole source tree or be selective? Update based on your comment: Personally I'd only add the artifacts I've changed to my local source repository. If you change another artifact later then add it to your SCM then.
What if I can't get the build system working in full
Worry about that when it happens. If the project is built with Maven it should be straightforward for you to build only the artifacts you need. If it uses an uber-ant build which you can't get working with your changes, then consider paring the build down.
发布评论
评论（1）
保持您更改的模块的 groupId 和 artifactId 相同，但在版本上使用限定符以确保它明显是非标准版本，例如 1.0.0-simon。 这是很常见的做法。
？当它发生时请担心。 如果项目是使用 Maven 构建的，那么您应该可以直接构建您需要的工件。 如果它使用 uber-ant 构建，而您无法使用您的更改，那么请考虑削减构建。
Keep the groupId and artifactId of the module(s) you change the same, but use a qualifier on the version to ensure that it is obvious it is a non-standard version, for example 1.0.0-simon. This is pretty common practice.
Worry about that when it happens. If the project is built with Maven it should be straightforward for you to build only the artifacts you need. If it uses an uber-ant build which you can't get working with your changes, then consider paring the build down.