Created attachment 135998 [details]
Proposed patch to fix the issue.

TopComponent creation wizard (New window) is not working in some Maven-based Netbeans projects containing (direct or indirect) dependencies on artifacts with non-numeric version numbers. The wizard does not allow to select mode for newly created component, list of available modes is empty.

The issue can be reproduced as follows:

1. Create a new Maven Netbeans Application project. Don't check "Allow OSGI bundles as dependencies" option, check "Create Module Project" option. Build the newly created project.
2. In the created mavenproject1-sample module's pom <dependencies> section add the following dependency:

        <dependency>
            <groupId>de.mukis</groupId>
            <artifactId>de.mukis.jama</artifactId>
            <version>2.0.0.M1</version>
        </dependency>

3. Clear and build the modified project. Dependencies will be downloaded.
4. Run the application. Main window will open. This is an important step!
5. Close the main window.
6. Right-click the "Source packages" node of the mavenproject-sample module and select New-Window...
7. The New window wizard opens with empty "Window position" combo box.Next and Finish buttons are disabled. The only possible action is to cancel the wizard. At the same time the following exception is thrown:

java.lang.NumberFormatException: For input string: "0-RC2"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:492)
	at java.lang.Integer.parseInt(Integer.java:527)
	at org.netbeans.modules.apisupport.project.api.ManifestManager.just3dots(ManifestManager.java:535)
	at org.netbeans.modules.apisupport.project.api.ManifestManager.getOSGiInstance(ManifestManager.java:509)
	at org.netbeans.modules.apisupport.project.api.ManifestManager.getInstance(ManifestManager.java:243)
	at org.netbeans.modules.apisupport.project.api.ManifestManager.getInstanceFromJAR(ManifestManager.java:202)
	at org.netbeans.modules.apisupport.project.spi.LayerUtil.layersOf(LayerUtil.java:97)
	at org.netbeans.modules.maven.apisupport.MavenNbModuleImpl.getEffectiveSystemFilesystem(MavenNbModuleImpl.java:649)
	at org.netbeans.modules.apisupport.project.ui.wizard.winsys.DesignSupport.existingModes(DesignSupport.java:159)
	at org.netbeans.modules.apisupport.project.ui.wizard.winsys.BasicSettingsPanel$1.construct(BasicSettingsPanel.java:139)
	at org.openide.util.AsyncInitSupport.run(AsyncInitSupport.java:168)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1432)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2042)

As can be seen from the exception report, when trying to find available modes, the NumberFormatException is thrown because of non-numeric part of the version number. 

Attached patch fixes the problem. When the exception is thrown, invalid part of the version number is replaced by zero.