Issue #138 has been updated by Jonathan Clarke. Status changed from New to Feedback
As I understand this, it's a Maven version problem. 2.0.x works, but not 2.2.x. Right? The problem is only with the "src/impl" folder, which is only present in LSC 1.1.x, not in 1.2.x. Since 1.1.x is no longer actively developed, and this bug would be quite time-consuming, I think it's safe to say that users of 1.1.x must use Maven 2.0.x, or upgrade to 1.2 (see http://lsc-project.org/wiki/documentation/1.2/upgrade-from-1.1). Any objections? ---------------------------------------- Bug #138: Custom classes not packaged by Maven http://tools.lsc-project.org/issues/show/138 Author: Jérôme Schell Status: Feedback Priority: Normal Assigned to: Category: Sample Target version: 1.1.x branch When running commands "make-lsc-archive.sh" or "mvn package", custom classes located in src/impl are not taken into account. The problem seems a bit hard to reproduce. When running: <pre> mvn clean && ant lsc::jar && mvn package </pre> The file "target/lsc-sample-1.1.1.jar" contains the custom classes. When running: <pre> mvn clean && mvn package </pre> The file "target/lsc-sample-1.1.1.jar" does not contain the custom classes. Running a "Build project" on the lsc-sample project produces the following error: <pre> Build errors for lsc-sample; org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or missing parameters: [Mojo parameter [name: 'sources'; alias: 'null']] for mojo: org.codehaus.mojo:build-helper-maven-plugin:1.4:add-source </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
