This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When creating a netbeans module from maven with external jar dependencies, the generated classpath contains an extra space in it, which breaks the harness build system in netbeans. Tested with 6.7 and 6.5.1 after mail-1.4.2 there is a blank space Class-Path: seds-2.01.06.jar jdom-1.0b8.jar log4j-1.2.9.jar mail-1.4.2 .jar activation-1.1.jar ojdbc14.jar-10.jar edbc-6.5.jar
this bug report belongs to http://jira.codehaus.org/browse/MNBMODULE, but anyway... what version of nbm-maven-plugin are you using? (the version of netbeans is irrelevant here) I could not find a place where we would place a space at the end of things. and after a close look I\ve noticed the space comes within a jar name. That's unlikely to be caused by the code in the nbm-plugin itself. I'm also curious how come the items on classpath don't have ext/ folder prepended as that's where the plugin generates them. Do you have the Class-Path entry in your manifest file that you pass to the nbm maven plugin? (i mean in your sources somewhere)
Created attachment 84966 [details] sample module with a lot of classpath dependencies
the attached sample project demonstrates the working of the current 3.0 version of the plugin. A generated long snippet of Class-Path for this particular module follows. Closing as worksforme, please reopen with a sample project that fails. Class-Path: ext/maven-core-2.2.0.jar ext/maven-settings-2.2.0.jar ext/ plexus-interpolation-1.11.jar ext/wagon-file-1.0-beta-6.jar ext/maven -plugin-parameter-documenter-2.2.0.jar ext/wagon-webdav-jackrabbit-1. 0-beta-6.jar ext/wagon-http-shared-1.0-beta-6.jar ext/xercesMinimal-1 .9.6.2.jar ext/nekohtml-1.9.6.2.jar ext/commons-httpclient-3.1.jar ex t/commons-codec-1.2.jar ext/jackrabbit-webdav-1.5.0.jar ext/jackrabbi t-jcr-commons-1.5.0.jar ext/slf4j-nop-1.5.3.jar ext/wagon-http-1.0-be ta-6.jar ext/slf4j-jdk14-1.5.6.jar ext/slf4j-api-1.5.6.jar ext/jcl-ov er-slf4j-1.5.6.jar ext/maven-reporting-api-2.2.0.jar ext/doxia-sink-a pi-1.1.jar ext/doxia-logging-api-1.1.jar ext/maven-profile-2.2.0.jar ext/maven-model-2.2.0.jar ext/maven-artifact-2.2.0.jar ext/wagon-prov ider-api-1.0-beta-6.jar ext/plexus-container-default-1.0-alpha-9-stab le-1.jar ext/junit-3.8.1.jar ext/maven-repository-metadata-2.2.0.jar ext/maven-error-diagnostics-2.2.0.jar ext/maven-project-2.2.0.jar ext /maven-plugin-registry-2.2.0.jar ext/commons-cli-1.2.jar ext/maven-pl ugin-api-2.2.0.jar ext/wagon-ssh-external-1.0-beta-6.jar ext/maven-pl ugin-descriptor-2.2.0.jar ext/plexus-interactivity-api-1.0-alpha-4.ja r ext/maven-artifact-manager-2.2.0.jar ext/backport-util-concurrent-3 .1.jar ext/maven-monitor-2.2.0.jar ext/wagon-ssh-1.0-beta-6.jar ext/j sch-0.1.38.jar ext/wagon-ssh-common-1.0-beta-6.jar ext/plexus-utils-1 .5.15.jar ext/classworlds-1.1.jar ext/plexus-sec-dispatcher-1.3.jar e xt/plexus-cipher-1.4.jar
Created attachment 84977 [details] project2 depends on projject 1
The bug occurs when there are two projects and when project two depends on project one. In the attachment there is a sample, the classpath in manifest file is: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: jbe Build-Jdk: 1.6.0_10 Class-Path: project_1-1.0.jar jdom-1.0.jar log4j-1.2.9.jar commons-col lections-3.2.jar I have found an old bug in the maven module, it was closed, maybe is a regression https://fisheye.codehaus.org/browse/MNBMODULE-7?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel the maven module version is: Version: 4.1.2 Source: NetBeans IDE 6.7 (Build 200906241340) Thank you.
thanks for the sample. You don't actually use the netbeans module maven plugin at all. That was confusion on my side. You just created a jar project with maven-jar-plugin configuration to add items to Class-Path. Then it's clearly an issu of the maven-jar-plugin that it generates stuff wrong (or the harness that it cannot read it, I can't decide) In any case not a netbeans maven support issue. closing as invalid. feel free to file an issue against the maven-jar-plugin.