createProjectFromXML is not supposed to be called for a project which already exists, but failed to enforce this.

If TopLevelItemDescriptor.newInstance throws a RuntimeException, why are we wrapping it in an IllegalArgumentException?
Let it throw something like Failure and control the rendering.

Otherwise get e.g.:
java.lang.IllegalArgumentException: java.lang.NullPointerException
	at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:253)
	at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:175)
	at jenkins.model.Jenkins.doCreateItem(Jenkins.java:2827)
	at jenkins.model.Jenkins.doCreateItem(Jenkins.java:308)
	at …
Caused by: java.lang.NullPointerException
	at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:251)
	... 65 more

- The caller is no longer responsible as the listener is actually invoked from the method

For example, a new job might have a trigger setting to begin with,
or it might resolve a reference that was previously failing (for
example, 'up' job referring to 'down' job and the 'down' job is newly
created.)

define new extension point to define ProjectNamingStrategy and add two implementations: Default and Pattern

extracted the commonality into ViewGroupMixIn, much like we have ItemGroupMixIn. This makes reuse in plugins easier, too.

Just import changes, from hudson.model.Jenkins -> jenkins.model.Jenkins,
and Javadoc comments.
Signed-off-by: NNigel Magnay <nigel.magnay@gmail.com>

Signed-off-by: NNigel Magnay <nigel.magnay@gmail.com>

older plugins.

git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@15081 71c3de6d-444a-0410-be80-ed276b4c234a

initial commit for the multi-config matrix project type, which is useful for running tests and builds on a large number of semi-identical (but different) configurations.


git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@3525 71c3de6d-444a-0410-be80-ed276b4c234a