Re: Maven First installation on Windows Vista doesn't work as expected
Brian E. Fox wrote: You need to add the repo as a pluginRepository in addition to repository. -Original Message- From: Marco Tedone [mailto:[EMAIL PROTECTED] Sent: Saturday, October 04, 2008 4:28 PM To: Maven-Users Subject: Maven First installation on Windows Vista doesn't work as expected Hi everybody, I just installed Maven on a new laptop running Windows Vista (don't worry, this is not my production box :-) ). The problem is that when building a project a certain dependency is not downloaded from the artifactory. Running an help on the build I get: profiles profile activation activeByDefaulttrue/activeByDefault /activation repositories repository idrepo1/id urlhttp://repo1.maven.org/maven2/url /repository repository idcodehaus-snapshots/id urlhttp://snapshots.repository.codehaus.org/url /repository repository idjava.net.m2/id urlhttp://download.java.net/maven/2/url /repository repository idjava.net.m1/id urlhttp://download.java.net/maven/1/url /repository repository idjemos-repo/id urlhttp://jemoslinux:8081/artifactory/jemos-repo/url /repository repository idjemos-repo-ext/id urlhttp://jemoslinux:8081/artifactory/repo/url /repository /repositories iddefault/id /profile /profiles activeProfiles activeProfiledefault/activeProfile /activeProfiles pluginGroups pluginGroupuk.co.jemos.maven.plugins/pluginGroup /pluginGroups Please note that the dependency I'm referring can be seen both from jemos-repo and jemos-repo-ext (if you want to verify, just replace jemoslinux:8081 with http://www.jemos.co.uk However it appears that Maven tries to download the plugin from central only and then it fails (rather than trying on all other repositories). This is the exception message I get: [INFO] Downloading: http://repo1.maven.org/maven2/uk/co/jemos/maven/plugins/jeco-plugin/1.0. 1/jeco-plugin-1.0.1.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=uk.co.jemos.maven.plugins -DartifactId=jeco-plugin -Dversion=1.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=uk.co.jemos.maven.plugins -DartifactId=jeco-plugin -Dversion=1.0.1 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] uk.co.jemos.maven.plugins:jeco-plugin:maven-plugin:1.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) uk.co.jemos.maven.plugins:jeco-plugin:maven-plugin:1.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] But the jar is available at the following address (for instance): http://www.jemos.co.uk/artifactory/repo/uk/co/jemos/maven/plugins/jeco-p lugin/1.0.1/ Any idea as of why this is happening? Regards, M. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Brilliant, that'll do it. Thanks. M. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version conflict resolution and stable builds
On Sat, 04 Oct 2008 14:16:57 Keith Branton wrote: 1. Can anyone please tell me of a way to achieve this with 2.0.9 today? With the appropriate use of ranges you can do this and it resolves as described. There are about 11 gotchas to doing it though, all worked around by appropriate conventions. -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Couldn't find a version error
Hi all, http://www.nabble.com/file/p19825141/rcp_err.png There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my local repository. There is one dependency in its pom.xml: dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies The question: where should I search for [3.2.1-R32x_v20060814, 3.3.0-v20070522] and [3.4.0,4.0.0)??? :confused::confused::confused: Thanks beforehand, regards, buters -- View this message in context: http://www.nabble.com/%22Couldn%27t-find-a-version%22-error-tp19825141p19825141.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
Hi Buters, seems like it is not searching for equinox-common-3.2.* but for equinox-common-3.4.x, and fails to find a 3.4 or higher version, cause only 3.2.1 and 3.3.0 are present, both under the 3.4-4.0 range. Probably some other dependency is raising the minimum version range, and Maven will always try to fetch a recent version (3.4.x in this case) to avoid errors. You could try using mvn dependency:analyze goal to perform an analysis of all dependencies and see who is requiring equinox-common version 3.4 or better. See http://maven.apache.org/plugins/maven-dependency-plugin/ for more deails on how dependency plugin works. Also, running maven with the -X switch will give you detailed informations (debug stuff) where you can find why it decides to search for 3.4 instead of 3.2. Hope this helps, Simone buters wrote: Hi all, http://www.nabble.com/file/p19825141/rcp_err.png There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my local repository. There is one dependency in its pom.xml: dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies The question: where should I search for [3.2.1-R32x_v20060814, 3.3.0-v20070522] and [3.4.0,4.0.0)??? :confused::confused::confused: Thanks beforehand, regards, buters -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
Thank you, Simone, very much. :-) I think that the analyse is very helpful, but I guess that I have an another case. :-( I've looked at http://repo1.maven.org/maven2/org/eclipse/equinox/registry/ There are two artefact versions there: 3.2.1-R32x_v20060814 and 3.3.0-v20070522. I.e. exactly those ones that is displayed in the error. But the correct version of org.eclipse.equinox.registry, 3.4.0-v20080516-0950, exists only in my local repository and it's conform with the range [3.4.0,4.0.0). Also Maven is looking for in the remote repository and ignoring the version of the local one. Why? 8-O 8-O 8-O Simone Gianni-2 wrote: Hi Buters, seems like it is not searching for equinox-common-3.2.* but for equinox-common-3.4.x, and fails to find a 3.4 or higher version, cause only 3.2.1 and 3.3.0 are present, both under the 3.4-4.0 range. Probably some other dependency is raising the minimum version range, and Maven will always try to fetch a recent version (3.4.x in this case) to avoid errors. You could try using mvn dependency:analyze goal to perform an analysis of all dependencies and see who is requiring equinox-common version 3.4 or better. See http://maven.apache.org/plugins/maven-dependency-plugin/ for more deails on how dependency plugin works. Also, running maven with the -X switch will give you detailed informations (debug stuff) where you can find why it decides to search for 3.4 instead of 3.2. Hope this helps, Simone buters wrote: Hi all, http://www.nabble.com/file/p19825141/rcp_err.png There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my local repository. There is one dependency in its pom.xml: dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies The question: where should I search for [3.2.1-R32x_v20060814, 3.3.0-v20070522] and [3.4.0,4.0.0)??? :confused::confused::confused: Thanks beforehand, regards, buters -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/%22Couldn%27t-find-a-version%22-error-tp19825141p19826277.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Conditional dependencies
Hi all, I would like to include or exclude a dependency based on the presence of an artifact on the global class path. For example, I have a database project. The user will include a dependency on it in his own pom. The user will also add a JDBC driver artifact. My database project should be able to declare additional dependencies depending on the presence of specific JDBC drivers artifacts, for example a database-mysql-dialect if the mysql-connector is used, or the database-postgres-dialect if the postgres driver is used. Whle it is possible to check at runtime, using reflection and the like, the presence of a given class, it lacks versioning, it is not a clean way, it clutters the main package code with stuff that could (and should) be placed in different artifacts. I don't know any way to do this in Maven right now. Theoretically, it could be achieved with profile activation, if there was a profile activation based on the presence of an artifact or at least on the presence of classpath resources instead of plain files. Is it possible to implement such a profile activator? Has anybody ever done something like this? Has anybody had the same need and investigated a way to solve it? Thanks in advance, Simone -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
Hi Butlers, sorry, my mistake. In fact, watching better the error screenshot you posted, it is failing to find equinox-registry, which as you properly explained is in your local repository, and not equinox-common, which I thought about seeing that you posted that dependency. Are you sure the version element in the equinox-registry POM file in your local repository has the right gpoupid-artifactid-version in it? Seems like Maven is not seeing it, and going to the remote repository to find it. Can you post the pom file that should be on you hard disk in c:\Documents and settings\yourusername\.m2\repository\org\eclipse\equinox\registry\3.4.0-v20080516-0950\pom? Also, have you used maven to install it in your local repository? Or just copied the file over there by hand? Simone buters wrote: Thank you, Simone, very much. :-) I think that the analyse is very helpful, but I guess that I have an another case. :-( I've looked at http://repo1.maven.org/maven2/org/eclipse/equinox/registry/ There are two artefact versions there: 3.2.1-R32x_v20060814 and 3.3.0-v20070522. I.e. exactly those ones that is displayed in the error. But the correct version of org.eclipse.equinox.registry, 3.4.0-v20080516-0950, exists only in my local repository and it's conform with the range [3.4.0,4.0.0). Also Maven is looking for in the remote repository and ignoring the version of the local one. Why? 8-O 8-O 8-O Simone Gianni-2 wrote: Hi Buters, seems like it is not searching for equinox-common-3.2.* but for equinox-common-3.4.x, and fails to find a 3.4 or higher version, cause only 3.2.1 and 3.3.0 are present, both under the 3.4-4.0 range. Probably some other dependency is raising the minimum version range, and Maven will always try to fetch a recent version (3.4.x in this case) to avoid errors. You could try using mvn dependency:analyze goal to perform an analysis of all dependencies and see who is requiring equinox-common version 3.4 or better. See http://maven.apache.org/plugins/maven-dependency-plugin/ for more deails on how dependency plugin works. Also, running maven with the -X switch will give you detailed informations (debug stuff) where you can find why it decides to search for 3.4 instead of 3.2. Hope this helps, Simone buters wrote: Hi all, http://www.nabble.com/file/p19825141/rcp_err.png There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my local repository. There is one dependency in its pom.xml: dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies The question: where should I search for [3.2.1-R32x_v20060814, 3.3.0-v20070522] and [3.4.0,4.0.0)??? :confused::confused::confused: Thanks beforehand, regards, buters -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
Thank you, Simone, very much.:-D Also, 1. registry-3.4.0-v20080516-0950.pom: ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdorg.eclipse.equinox/groupId artifactIdregistry/artifactId nameExtension Registry Support/name version3.4.0-v20080516-0950/version licenses license nameEclipse Public License - v 1.0/name urlhttp://www.eclipse.org/org/documents/epl-v10.html/url /license /licenses dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies /project 2. I've created it with eclipse:to-maven and then copied in my local repository. 3. The problem is that my project isn't quite Maven project. It is RCP Project, that I want to build with Maven. I've created a simple Maven project with a dependency from org.eclipse.equinox.registry-3.4.0-v20080516-0950 and Maven has immediately found it. The error happens only if I try to build my RCP project, Maven cannot find this version in my local repository. %-| %-| %-| Buters Simone Gianni-2 wrote: Hi Butlers, sorry, my mistake. In fact, watching better the error screenshot you posted, it is failing to find equinox-registry, which as you properly explained is in your local repository, and not equinox-common, which I thought about seeing that you posted that dependency. Are you sure the version element in the equinox-registry POM file in your local repository has the right gpoupid-artifactid-version in it? Seems like Maven is not seeing it, and going to the remote repository to find it. Can you post the pom file that should be on you hard disk in c:\Documents and settings\yourusername\.m2\repository\org\eclipse\equinox\registry\3.4.0-v20080516-0950\pom? Also, have you used maven to install it in your local repository? Or just copied the file over there by hand? Simone buters wrote: Thank you, Simone, very much. :-) I think that the analyse is very helpful, but I guess that I have an another case. :-( I've looked at http://repo1.maven.org/maven2/org/eclipse/equinox/registry/ There are two artefact versions there: 3.2.1-R32x_v20060814 and 3.3.0-v20070522. I.e. exactly those ones that is displayed in the error. But the correct version of org.eclipse.equinox.registry, 3.4.0-v20080516-0950, exists only in my local repository and it's conform with the range [3.4.0,4.0.0). Also Maven is looking for in the remote repository and ignoring the version of the local one. Why? 8-O 8-O 8-O Simone Gianni-2 wrote: Hi Buters, seems like it is not searching for equinox-common-3.2.* but for equinox-common-3.4.x, and fails to find a 3.4 or higher version, cause only 3.2.1 and 3.3.0 are present, both under the 3.4-4.0 range. Probably some other dependency is raising the minimum version range, and Maven will always try to fetch a recent version (3.4.x in this case) to avoid errors. You could try using mvn dependency:analyze goal to perform an analysis of all dependencies and see who is requiring equinox-common version 3.4 or better. See http://maven.apache.org/plugins/maven-dependency-plugin/ for more deails on how dependency plugin works. Also, running maven with the -X switch will give you detailed informations (debug stuff) where you can find why it decides to search for 3.4 instead of 3.2. Hope this helps, Simone buters wrote: Hi all, http://www.nabble.com/file/p19825141/rcp_err.png There is org.eclipse.equinox.registry-3.4.0-v20080516-0950.jar In my local repository. There is one dependency in its pom.xml: dependencies dependency groupIdorg.eclipse.equinox/groupId artifactIdcommon/artifactId version[3.2.0,4.0.0)/version /dependency /dependencies The question: where should I search for [3.2.1-R32x_v20060814, 3.3.0-v20070522] and [3.4.0,4.0.0)??? :confused::confused::confused: Thanks beforehand, regards, buters -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/%22Couldn%27t-find-a-version%22-error-tp19825141p19828480.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For
Re: Couldn't find a version error
On Mon, 06 Oct 2008 08:53:04 buters wrote: 3. The problem is that my project isn't quite Maven project. It is RCP Project, that I want to build with Maven. I've created a simple Maven project with a dependency from org.eclipse.equinox.registry-3.4.0-v20080516-0950 and Maven has immediately found it. The error happens only if I try to build my RCP project, Maven cannot find this version in my local repository. %-| %-| %-| ranges are resolved from metadata you must have a valid maven-metadata-local.xml for range resolution to work... you should use install-file to install the file into your local repo not just copy it... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conditional dependencies
wrap the dependency for the db driver in a pom project that also depends upon the dialect e.g. example.company.db.posgresql - postgresql jdc driver - postgresql database dialect then example.company.applicationwithdb - example.company.db.postgresql profiles should not be used to munge up dependencies, it just makes it confusing for people to have side effects. On Mon, 06 Oct 2008 05:47:16 Simone Gianni wrote: Has anybody ever done something like this? Has anybody had the same need and investigated a way to solve it? -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
Thank you, Michael, very much. :-D Your advice has helped me, but I need another one. :-( I've converted all eclipse plugins in Maven plugins with the command: mvn eclipse:to-maven local:default:file://path/to/repository -DeclipseDir=. It creates maven-metadata.xml, but not maven-metadata-local.xml files. %-O How can I make it create a metadata-files with a correct name? :confused::confused::confused: Thanks beforehand, regards, buters Michael McCallum-3 wrote: On Mon, 06 Oct 2008 08:53:04 buters wrote: 3. The problem is that my project isn't quite Maven project. It is RCP Project, that I want to build with Maven. I've created a simple Maven project with a dependency from org.eclipse.equinox.registry-3.4.0-v20080516-0950 and Maven has immediately found it. The error happens only if I try to build my RCP project, Maven cannot find this version in my local repository. %-| %-| %-| ranges are resolved from metadata you must have a valid maven-metadata-local.xml for range resolution to work... you should use install-file to install the file into your local repo not just copy it... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/%22Couldn%27t-find-a-version%22-error-tp19825141p19829804.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Couldn't find a version error
I understood, It works with mvn eclipse:to-maven -DeclipseDir=. :jumping: buters wrote: Thank you, Michael, very much. :-D Your advice has helped me, but I need another one. :-( I've converted all eclipse plugins in Maven plugins with the command: mvn eclipse:to-maven local:default:file://path/to/repository -DeclipseDir=. It creates maven-metadata.xml, but not maven-metadata-local.xml files. %-O How can I make it create a metadata-files with a correct name? :confused::confused::confused: Thanks beforehand, regards, buters Michael McCallum-3 wrote: On Mon, 06 Oct 2008 08:53:04 buters wrote: 3. The problem is that my project isn't quite Maven project. It is RCP Project, that I want to build with Maven. I've created a simple Maven project with a dependency from org.eclipse.equinox.registry-3.4.0-v20080516-0950 and Maven has immediately found it. The error happens only if I try to build my RCP project, Maven cannot find this version in my local repository. %-| %-| %-| ranges are resolved from metadata you must have a valid maven-metadata-local.xml for range resolution to work... you should use install-file to install the file into your local repo not just copy it... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/%22Couldn%27t-find-a-version%22-error-tp19825141p19829930.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
zip instead of jar
Hi all, how can I create a zip-Archive instead of jar-one with Maven? Thanks beforehand, regards, butters. -- View this message in context: http://www.nabble.com/zip-instead-of-jar-tp19830308p19830308.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: zip instead of jar
On Sun, Oct 5, 2008 at 4:55 PM, buters [EMAIL PROTECTED] wrote: how can I create a zip-Archive instead of jar-one with Maven? You can use the Assembly plugin [1] to create zip files. ... and you might want to keep an eye on MNG-1683 [2] which adds zip as a packaging type. [1] http://maven.apache.org/plugins/maven-assembly-plugin [2] http://jira.codehaus.org/browse/MNG-1683 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem when mvn site:site `Generating Dependencies report'
Hello, I try use maven site plugin and it can generate project site well, but something wrong with dependencies report. there are some message : = [INFO] Generating Plugin Management report. [INFO] Generating Mailing Lists report. [INFO] Generating Continuous Integration report. [INFO] Generating Project License report. [INFO] Generating Project Team report. [INFO] Generating Source Repository report. [INFO] Generating Issue Tracking report. [INFO] Generating Project Summary report. [INFO] Generating Project Plugins report. [INFO] Generating Dependencies report. [WARNING] Unable to process class com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File C:\Documents and Settings\qty\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 60 at org.apache.bcel.classfile.Constant.readConstant(Constant.java:146) at org.apache.bcel.classfile.ConstantPool.init(ConstantPool.java:67) at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222) at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136) at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92) at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:285) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1278) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:423) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:268) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) = some JARs are unanalyzed. I try use mvn dpenedency:tree to see any problem with dependencies and everything is ok. Someone can tell me how to exclude JARs in dependencies report. Thank a lot. -- View this message in context: http://www.nabble.com/Problem-when-mvn-site%3Asite-%60Generating-%22Dependencies%22-report%27-tp19831145p19831145.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
