Re: .NET with Continuum
Not in 1.0.3 In 1.1, we have a link for a tests report, the report is generated from xml files in target/surefire-reports. I've never used NUnit so I don't know if it generate xml output files like junit, if it do it, report will can be shown in the build result page. Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : I have a scheduled task which runs a batch build/deploy script in Continuum. Is there a way to run Nunit tests in Continuum and display the results appropriately? Looking forward to your reply. Thanks. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Continuous deployment and intra-project dependencies
Hi, In our project we have Continuous integration with Maven 2.0.4 and Continuum 1.0.3 operational. Currently I'm trying to continuously deploy a WAR (containing a WebSphere portlet) to an IBM WebSphere Portal Server. This WAR depends on another (business) module, which is included in the WEB-INF/lib during the packaging stage. The question is: Suppose a modification has been checked in for the business module, how can we implement an automated subsequent deployment of the WAR containing this modified and hence newly built business module (JAR)? In the above scenario, Continuum only rebuilds the business module, leaving the WAR untouched. In Continuum, this looks as follows: -- OurProjectMain (with --non-recursive) | |-- business-module (included in the WAR) | |-- web-module (containing the portlet) | |-- other-module (omitted for the sake of simplicity) where the main project contains the root POM and a copy of the complete project tree from CVS (by default with the --non-recursive option in the build goal). Only this main project is triggered upon a SCM check-in of any of its submodules, so can be the only candidate to trigger the deployment. However, the WAR it would deploy this way would still contain the unmodified business JAR file in its WEB-INF/lib dir! So far, we could not find any resource that addresses this issue: we extensively searched the web and read relevant chapters from the Better builds with Maven book. Can anybody shed some light on this issue? Thanks in advance, Kind regards, Zeger Hendrikse. PS: At this moment we don't think that either a hierarchical or flat lay-out of the project structure is of any influence, but for the sake of completeness: we have a hierarchical lay-out. DISCLAIMER*** Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere aansprakelijkheid uit die voortvloeit uit electronische verzending. This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Fortis rules out any and every liability resulting from any electronic transmission. **
RE: Problem building with Continuum
I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157) ... 11 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:467) ... 12 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul tWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:124) ... 14 more settings.xml settings localRepository/maven/localRepository/localRepository mirrors mirror idBf proxy/id mirrorOfcentral/mirrorOf nameBF proxy repository/name
RE: Problem building with Continuum
I was able to build from my local machine. I had forgotten to change my settings.xml for maven. After copying the settings.xml from my continuum build box, I can successfully build via the command line. So this brings me back to a missing or corrupt setting in Continuum that is not looking at the right repo. Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:26 AM To: continuum-users@maven.apache.org Subject: RE: Problem building with Continuum I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157) ... 11 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:467)
RE: Problem building with Continuum
Problem resolved. The local system user on my build box was missing the repository folder under C:/Documents and Settings/Default User/.m2. The only file in this folder is the parent pom.xml. Does anyone know why this file must be in here instead of the 'regular' repositories? Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. 843-849-7476 ext. 6394 843-849-9485 (Fax) -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:45 AM To: continuum-users@maven.apache.org; users@maven.apache.org Subject: RE: Problem building with Continuum I was able to build from my local machine. I had forgotten to change my settings.xml for maven. After copying the settings.xml from my continuum build box, I can successfully build via the command line. So this brings me back to a missing or corrupt setting in Continuum that is not looking at the right repo. Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:26 AM To: continuum-users@maven.apache.org Subject: RE: Problem building with Continuum I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157)
Sequence of goal execution within a phase
Hello, Is there a way to enforce a sequence of goal executions within a phase? I have different custom plugins that expect other plugins to have produced some output. Any ideas? Cheers Jo
Re: Maven Webstart Plugin - some remarks
Jerome Lacoste schrieb: Please use the MOJO mailing list for comments on a MOJO project plugin. On 1/30/07, Mark Donszelmann [EMAIL PROTECTED] wrote: Hi 2. It would be handy if the $version could be added to the jnlp parsed values. this is fixed in 1.0-alpha-2-SNAPSHOT Hi, i tried the mentioned version of the plugin (1.0-alpha-2-SNAPSHOT), but the resolution of the $version in template.vm is not working. I just added the variable $version to the template file, or do i have to do something else? Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sequence of goal execution within a phase
Additional question.. One custom plugin called maven-ystr-plugin contains multiple mojo's that are bound to the generate-sources phase. One of them generates a new xsd schema for jaxb, the other modifies the generated jaxb code after the maven-jaxb1-plugin has run. How should i configure them so the execution sequence is like this within the generate-sources phase: 1. maven-ystr-plugin:enrichXsd 2. maven-jaxb1-plugin:generate 3. maven-ystr-plugin:enrichJaxb This would force me to define the same plugin (maven-ystr-plugin) twice in the build definition, is that possible somehow? Cheers Jo On 2/22/07, Jo Vandermeeren [EMAIL PROTECTED] wrote: Hello, Is there a way to enforce a sequence of goal executions within a phase? I have different custom plugins that expect other plugins to have produced some output. Any ideas? Cheers Jo
Re: unused dependencies
On 22/02/07, Tony Ambrozie [EMAIL PROTECTED] wrote: I believe the correct locations are: https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-dependency-analyzer-plugin/ and https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-dependency-analyzer/ Thanks, it was correct at the time of writing ;) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Formation rules for repositories
On 2/22/07, Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) [EMAIL PROTECTED] wrote: Thanks, Wendy. I'll have a look. I've written up a few things for my own use. It isn't complete, but it would be a start. I started a new one, with the info Carlos provided: http://docs.codehaus.org/display/MAVENUSER/Repository+Metadata -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] runtime scope but not transitive
I think provided is the right value for this Regards Rémy Sanlaville wrote: Anybody can help me (isn't it clear enough) ? any thoughts? Rémy -- --- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca Baleares - Spain Tel: +34 971 435 085 http://www.gridsystems.com/Fax: +34 971 435 082 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
unable to resolve artifact that is in local repo?
Hi all, for some reason my offline build fails. Maven reports ut can't resolve an artifact allthough it is in my local repo. Anyone knows what I might be doing wrong? I'm using maven 2.0.5. Aditional info below. regards, Bram == my settings.xml ... localRepositoryc:\path\to\maven2-repository/localRepository offlinetrue/offline ... == the local repo c:\path\to\maven2-repository\org\apache\maven\plugins\maven-assembly-plu gin\2.2-SNAPSHOT ... contains... 02/13/2007 11:10 AM 141,723 maven-assembly-plugin-2.2-20070112.063452-32.jar 02/13/2007 11:10 AM40 maven-assembly-plugin-2.2-20070112.063452-32.jar.sha1 02/13/2007 11:10 AM11,445 maven-assembly-plugin-2.2-20070112.063452-32.pom 02/13/2007 11:10 AM40 maven-assembly-plugin-2.2-20070112.063452-32.pom.sha1 02/13/2007 11:10 AM 141,723 maven-assembly-plugin-2.2-SNAPSHOT.jar 02/13/2007 11:10 AM11,445 maven-assembly-plugin-2.2-SNAPSHOT.pom 02/21/2007 07:04 PM 378 maven-metadata-apache.snapshots.xml 02/21/2007 07:04 PM40 maven-metadata-apache.snapshots.xml.sha1 02/22/2007 12:15 PM 189 maven-metadata-central.xml 02/21/2007 07:04 PM 189 maven-metadata-codehaus snapshot repository.xml 02/21/2007 07:04 PM 189 maven-metadata-gx-repository.xml 02/21/2007 07:04 PM 189 maven-metadata-safehaus.xml 02/22/2007 12:15 PM 189 maven-metadata-webmanager.repository.xml == mvn -s settings.xml validate [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-assembly-plugin Version: 2.2-SNAPSHOT Reason: System is offline. org.apache.maven.plugins:maven-assembly-plugin:pom:2.2-SNAPSHOT == mvn -s settings.xml -X validate [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.apache.maven.plugins:maven-assembly-plugin': POM 'org.apache.mav en.plugins:maven-assembly-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-assembly-plugin:pom:2.2-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1221) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:987) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.apache.maven.plugins:maven-assembly-plugin': POM 'org.apache. maven.plugins:maven-assembly-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-assembly-plugin:pom:2.2-SNAPSHOT at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(D efaultPluginManager.java:268) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:186) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:166) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1257) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven.plugins:maven-assembly-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-assembly-plugin:pom:2.2-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
Problem with resources plugin
Hi I've a fresh new maven 2.5 install with the following settings: - settings xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; localRepositoryw:/mvn-repository/localRepository usePluginRegistryfalse/usePluginRegistry interactiveModetrue/interactiveMode proxies proxy idxxs/id activetrue/active protocolhttp/protocol host172.31.22.1/host port8080/port /proxy /proxies mirrors mirror idibiblio.org/id nameibiblio Mirror of http://repo1.maven.org/maven2//name urlhttp://mirrors.ibiblio.org/pub/mirrors/maven2/url mirrorOfcentral/mirrorOf /mirror -- I'm trying to compile a project but when I did mvn compile I got the error: - mvn compile [INFO] Scanning for projects... [INFO] - --- [INFO] Building ws [INFO]task-segment: [compile] [INFO] - --- Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resour ces-plugin/2.0/maven-resources-plugin-2.0.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugi n:pom:2.0' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resour ces-plugin/2.0/maven-resources-plugin-2.0.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugi n:pom:2.0' from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repos itory: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 42 seconds [INFO] Finished at: Thu Feb 22 12:17:50 CET 2007 [INFO] Final Memory: 1M/4M [INFO] --- I've tried to delete maven-resources-plugin folder from plugins and the I did: mvn -X -cpu compile but I got the error: -- mvn -X -cpu compile + Error stacktraces are turned on. Maven version: 2.0.5 [DEBUG] Building Maven user-level plugin registry from: 'D:\asf1\usersnt\K049118 \.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'd:\maven\conf\plugin- registry.xml' [INFO] Scanning for projects... [INFO] - --- [INFO] Building ws [INFO]task-segment: [compile] [INFO] - --- [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resour ces-plugin/2.0/maven-resources-plugin-2.0.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugi n:pom:2.0' from repository central (http://repo1.maven.org/maven2) [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resour ces-plugin/2.0/maven-resources-plugin-2.0.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugi n:pom:2.0' from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repos itory: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.0 from
Suppressing [INFO] lines on scm diff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maven users, here is a quick question, which I was unable to find so far. To stay independent of the SCM, I would like users to use mvn scm:diff (insted of svn diff) to create patches. However, doing so will not only result in the diff, but also in all the standard maven [INFO] lines to be printed out. I've found an option for maven 1 to suppress the header, but what would be the right option for maven 2? Thanks mfG Max Berger e-mail: [EMAIL PROTECTED] - -- OpenPG ID: E81592BC Print: F489F8759D4132923EC4 BC7E072AB73AE81592BC For information about me and my work please see http://max.berger.name -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF3WuWkBxxyuhBA8QRApGjAJ4q0P/eaCwZVfJ8HZQPe39WywET5ACgqgwH owdAmpsxWFINslxhAdhtdfM= =jsLp -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: Problem building with Continuum
Below are emails I have sent to the Continuum mailing list, but since it seems that there is a problem with my maven repositories, at least one of them anyways, I thought I would forward these emails to this user-list as well. If anyone can provide any help I would greatly appreciate it. I am kind of in a bind due to several builds failing because of the error described below. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:26 AM To: continuum-users@maven.apache.org Subject: RE: Problem building with Continuum I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157) ... 11 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at
RE: Problem building with Continuum
I was able to build from my local machine. I had forgotten to change my settings.xml for maven. After copying the settings.xml from my continuum build box, I can successfully build via the command line. So this brings me back to a missing or corrupt setting in Continuum that is not looking at the right repo. Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:26 AM To: continuum-users@maven.apache.org Subject: RE: Problem building with Continuum I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157) ... 11 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:467)
Maven1's repo is more up-to-date than Maven2's repo? (missing jars in Maven2's repo)
Hi Ho! Why the public repository for Maven2 (http://repo1.maven.org/maven2/) does not contain all jars exists in the public repository for Maven1 (http://repo1.maven.org/maven/)? For example, in the Maven1's repo you can get maven-xdoclet-plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in the Maven2's repo in http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the latest version there is 1.2. My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's repo, right? Thank you very much for your explanation. -- View this message in context: http://www.nabble.com/Maven1%27s-repo-is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in-Maven2%27s-repo%29-tf3272775s177.html#a9099988 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
adding a resource file in POM.
Hi, I am using a ant task to run inside my pom, to run Jaxb1.0.4 compile task. I want to add jaxb,properties to the output jar with 'complete' path reference. Currently I am adding it as a resource, it is added to the jar but with out any path reference. resources resource directorytarget/generated-source/za/co/rmb/calypso/binding/extract/directory includes includejaxb.properties/include /includes /resource /resources How do I get the path reference correct in jar file.. Regards This e-mail is subject to a disclaimer, available at http://www.rmb.co.za/web/elements.nsf/online/disclaimer-communications.html
Fw: adding a resource file in POM.
Dont worry, got it right! - Forwarded by Vidya Mahavadi/RMB on 22/02/2007 15:57 - Vidya Mahavadi/RMB 22/02/2007 15:46 To maven users cc Subject adding a resource file in POM. Hi, I am using a ant task to run inside my pom, to run Jaxb1.0.4 compile task. I want to add jaxb,properties to the output jar with 'complete' path reference. Currently I am adding it as a resource, it is added to the jar but with out any path reference. resources resource directorytarget/generated-source/za/co/rmb/calypso/binding/extract/directory includes includejaxb.properties/include /includes /resource /resources How do I get the path reference correct in jar file.. Regards This e-mail is subject to a disclaimer, available at http://www.rmb.co.za/web/elements.nsf/online/disclaimer-communications.html
Re: Suppressing [INFO] lines on scm diff
according to scm doc, it also dumps the diff to a file http://maven.apache.org/scm/plugins/diff-mojo.html -D On 2/22/07, Max Berger [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear maven users, here is a quick question, which I was unable to find so far. To stay independent of the SCM, I would like users to use mvn scm:diff (insted of svn diff) to create patches. However, doing so will not only result in the diff, but also in all the standard maven [INFO] lines to be printed out. I've found an option for maven 1 to suppress the header, but what would be the right option for maven 2? Thanks mfG Max Berger e-mail: [EMAIL PROTECTED] - -- OpenPG ID: E81592BC Print: F489F8759D4132923EC4 BC7E072AB73AE81592BC For information about me and my work please see http://max.berger.name -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF3WuWkBxxyuhBA8QRApGjAJ4q0P/eaCwZVfJ8HZQPe39WywET5ACgqgwH owdAmpsxWFINslxhAdhtdfM= =jsLp -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to assemble collection of javadocs?
According to the maven-assembly-plugin website it does not handle collecting and packaging javadoc jars like it does for binaries sources. Additionally the web site says that the maven-javadoc-plugin provides this functionality. However the maven-javadoc-plugin web site does NOT say that it provides this functionality. It says it creates javadoc jar(s); normally one per module or if aggregated one per project. So what plugin collects javadoc jars created per module and packages them into folder, jar, etc? It seems the logical place for this is the assembly plugin since it is exactly what it does for sources and binaries. Can someone let me know if this functionality exists? -dh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Specifying a New Package Type
Have you set extensionstrue/extensions for the plugin execution (in the pom)? I'm not sure if this even applies for the case of a new packaging. I'm interested in how to get this sort of thing to work, though, since I think I'll be writing a custom packaging plugin before too long myself. ..David.. -Original Message- From: Ole Ersoy [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 2:06 PM To: Maven Users List Subject: Re: Specifying a New Package Type Oh oh - When I run the plugin for the new packaging, it runs fine, but when I run eclipse:eclipse it says that it can't find the lifecycle-mapping for the packaging. Ideas? Thanks, - Ole --- Ole Ersoy [EMAIL PROTECTED] wrote: Wait - Got it - I had META-INF/plexus/components.xml in the root of the plugin development directory instead of src/main/resources. Now it's here: src/main/resources/META-INF/plexus/components.xml and all is good. Cheers, - Ole --- Ole Ersoy [EMAIL PROTECTED] wrote: Hi, I'm trying to specify a new package type. I did everything the maven guide said, but maven still barks when I try to run the new lifecycle. So I tried looking at the webapp plugin, to see if it did anything different. In the guide it says to add a META-INF/plexus/components.xml to the plugin jar. However the maven war plugin does not have this. Any ideas on what the proper way to specify a new package type is? Thanks, - Ole Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=listsid=396546091 - 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]
Re: Do we allow to upload full asembly to maven central?
People can upload what they like provided they have a POM for it. Jason. On 22 Feb 07, at 2:40 AM 22 Feb 07, Dan Tran wrote: Carlos? :-) any thoughts? Thanks On 2/21/07, Dan Tran [EMAIL PROTECTED] wrote: Do we allow to upload full assembies such as those in http://db.apache.org/derby/releases/release-10.2.2.0.cgi ? This is helpful to unpack an application footprint like derby for integration testing purpose. -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven1's repo is more up-to-date than Maven2's repo? (missing jars in Maven2's repo)
On 22 Feb 07, at 8:39 AM 22 Feb 07, Eus wrote: Hi Ho! Why the public repository for Maven2 (http://repo1.maven.org/ maven2/) does not contain all jars exists in the public repository for Maven1 (http://repo1.maven.org/maven/)? For example, in the Maven1's repo you can get maven-xdoclet- plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in the Maven2's repo in http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the latest version there is 1.2. My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's repo, right? Thank you very much for your explanation. It means our conversion process is not working well enough for projects that don't have POMs. The XDoclet plugin you speak of doesn't look like it has a valid POM which makes it hard to convert. And right now if a POM is not available in conjunction with xdoclet stuff in m1, which is a mess BTW, results in it not getting converted. Maven 2.x is strict about having a POM. No POM, no place in the repository, that's how it works. So you have a couple options. Complain to the Xdoclet people to fix their projects and provide the correct metadata, or provide us with POMs to fix the problem. We cannot be watchdogs for everything though we will in the future have better reporting for things that are wrong with artifacts submitted. Jason. -- View this message in context: http://www.nabble.com/Maven1%27s-repo- is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in-Maven2% 27s-repo%29-tf3272775s177.html#a9099988 Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
Re: Maven1's repo is more up-to-date than Maven2's repo? (missing jars in Maven2's repo)
Isn't XDoclet an orphaned project? Are people still developing it? -K On 2/22/07 8:48 AM, Jason van Zyl [EMAIL PROTECTED] wrote: On 22 Feb 07, at 8:39 AM 22 Feb 07, Eus wrote: Hi Ho! Why the public repository for Maven2 (http://repo1.maven.org/ maven2/) does not contain all jars exists in the public repository for Maven1 (http://repo1.maven.org/maven/)? For example, in the Maven1's repo you can get maven-xdoclet- plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in the Maven2's repo in http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the latest version there is 1.2. My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's repo, right? Thank you very much for your explanation. It means our conversion process is not working well enough for projects that don't have POMs. The XDoclet plugin you speak of doesn't look like it has a valid POM which makes it hard to convert. And right now if a POM is not available in conjunction with xdoclet stuff in m1, which is a mess BTW, results in it not getting converted. Maven 2.x is strict about having a POM. No POM, no place in the repository, that's how it works. So you have a couple options. Complain to the Xdoclet people to fix their projects and provide the correct metadata, or provide us with POMs to fix the problem. We cannot be watchdogs for everything though we will in the future have better reporting for things that are wrong with artifacts submitted. Jason. -- View this message in context: http://www.nabble.com/Maven1%27s-repo- is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in-Maven2% 27s-repo%29-tf3272775s177.html#a9099988 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cargo maven 2 plugin : timeout when deploying to JBoss 4x
Hi,
We are in the process of creating an integration test suite for a J2EE
project using the Cargo Maven 2 plugin with a JBoss 4.0 container. When
we execute mvn integration-test, the jboss zip is correctly expanded and
our war is copied at the right place. The problem we have is that our
application takes more than 20 seconds to deploy and Cargo throws an
exception saying that the timeout is exceeded. I do not see any
configuration that can override the timeout for a deployable... is there
one? Or is there any workaround for that kind of problem?
Also, is there a way to tell to the installer (zipUrlInstaller) to force
a cleanup and a full reinstall (i.e. delete the install dir and
re-expand the zip file)?
Here is our plugin config in the pom.xml:
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
configuration
waitfalse/wait
container
containerIdjboss4x/containerId
zipUrlInstaller
urlfile:///${jboss.distribution.dir}/JBoss4.0.zip/url
installDir${installDir}/installDir
/zipUrlInstaller
log${log.dir}/cargo.log/log
output${log.dir}/jboss.log/output
/container
configuration
typeexisting/type
home${installDir}/jboss/server/default/home
/configuration
/configuration
executions
execution
idstart-container/id
phasepre-integration-test/phase
goals
goalstart/goal
goaldeploy/goal
/goals
configuration
deployer
deployables
deployable
groupIdorg.xyz/groupId
artifactIdmy-app/artifactId
typewar/type
pingURLhttp://localhost:8080/index.jsf/pingURL
/deployable
/deployables
/deployer
/configuration
/execution
execution
idstop-container/id
phasepost-integration-test/phase
goals
goalstop/goal
/goals
/execution
/executions
/plugin
Here is the error trace:
[INFO]
[INFO] Deployable failed to finish deploying within the timeout period
[2]. The Deployable state is thus unknown.
[INFO]
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Deployable failed to
finish deploying within the timeout period [2]. The Deployable state
is thus unknown.
at
org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(Deploye
rWatchdog.java:109)
at
org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watchForAvail
ability(DeployerWatchdog.java:78)
at
org.codehaus.cargo.container.spi.deployer.AbstractLocalDeployer.deploy(A
bstractLocalDeployer.java:98)
at
org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSing
leDeployable(DeployerDeployMojo.java:75)
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAl
lDeployables(AbstractDeployerMojo.java:106)
at
org.codehaus.cargo.maven2.AbstractDeployerMojo.execute(AbstractDeployerM
ojo.java:43)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at
Get the scm settings from plugin
I would like to be able to access the scm settings (connection, tag, etc) in the pom.xml from within a plugin. Is this possible? It seems like there should be an easy way to get access to all of the pom configuration from within a plugin, but I haven't found it yet. I tried looking in project.properties, but it was empty. Is project.properties used for anything? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HowTo access project version programmatically in application
Hi, HowTo access project version programmatically in application? At the moment we enter the version string manually in one of our classes. Is there a way to access the project version at runtime? One of my thoughts are to generate a Version class holding the version string, but is there a more convenient way? Thanks in advance Roland -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Get the scm settings from plugin
all you need is to have access to 'project' instance and use it to get pom's
info.
put the below fragment in your mojo
/**
* [EMAIL PROTECTED] expression=${project}
* [EMAIL PROTECTED]
*
*/
*protected* MavenProject project;
On 2/22/07, Paul Gier [EMAIL PROTECTED] wrote:
I would like to be able to access the scm settings (connection, tag,
etc) in the pom.xml from within a plugin. Is this possible? It seems
like there should be an easy way to get access to all of the pom
configuration from within a plugin, but I haven't found it yet. I tried
looking in project.properties, but it was empty. Is project.properties
used for anything?
Thanks!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to use groups in javadoc plugin?
I am trying to use the javadoc plugin group tag to separate the aggregated project's javadocs into two sections (groups). Using the following as an example: groups group titleCore Packages/title packagesorg.apache.maven.plugin.javadoc.test1/packages /group group titleExtension Packages/title packagesorg.apache.maven.plugin.javadoc.test2/packages /group /groups Questions: 1. Can I have more than one packages per group? It does not seem to allow this. It seems that packages should allow nested package where any namespace could be specified but it seems to require some entry for packages. It is not clear if this is supported somehow or not. 2. Can I use wildcards in the packages name? I.e. org.apache.maven.plugin.javadoc.* When I do this it excludes the base package! How can I say I want all javadocs for namespace org.apache.maven.plugin.javadoc and below? 3. If the answer to 1 is no then can I have groups with the same title? It does not seem to allow this. I am trying to use this to group the generated javadocs into logical sections but there is so little apparent flexibility I cannot achieve the desired results. Any help would be greatly appreciated. -dh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Get the scm settings from plugin
It seems project.properties will always be empty (I've been working on
that issue in the Mojo accessing project properties thread in this
forum).
However, what you want isn't in the properties anyway. What you want is
the project.scm value. Declare your plugin field like this:
/**
* Source control information.
* @parameter expression=${project.scm}
* @required
* @readonly
*/
private org.apache.maven.model.Scm scm;
You'll need to add maven-model as a dependency to your plugin as well:
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-model/artifactId
version2.0.4/version
/dependency
That should be enough to get the scm information in your plugin.
..David..
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 9:01 AM
To: users@maven.apache.org
Subject: Get the scm settings from plugin
I would like to be able to access the scm settings (connection, tag,
etc) in the pom.xml from within a plugin. Is this possible? It seems
like there should be an easy way to get access to all of the pom
configuration from within a plugin, but I haven't found it yet. I tried
looking in project.properties, but it was empty. Is project.properties
used for anything?
Thanks!
-
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]
Surefire 2.3
Hi, Is there any idea yet of when we can expect surefire 2.3 to be released? Looking at JIRA there are still a lot of tasks pending, but also quite a few fixes complete. Is it possible that some of these open issues could be pushed back to 2.4? The reason being that now Bamboo is 1.0 it is still suffering from this bug http://jira.atlassian.com/browse/BAM-732 which is caused by http://jira.codehaus.org/browse/SUREFIRE-122?rc=1 which is fixed. This makes all the nice reporting from Bamboo pointless as it thinks I have 24000 tests rather than 805. Thanks, Martin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 - POM inheritance issue with Developers Contributors sections?
Hey everyone. I have a quick question. Isn't the developers and contributors info supposed to be merged, not overridden from parent to child POMs? My project has a chief architect/developer over all of the sub-projects and I am trying to list him once in the parent POM, and then add developers working on specific sub-projects in the child POMs accordingly. His information is not being merged into the effective POM of the child projects. According to the Project Inheritance section of http://maven.apache.org/guides/introduction/introduction-to-the-pom.html this info should be merged. Has anyone else run into this? I searched JIRA and could not find an issue about this. Thanks, Brad P.S. I am using Maven 2.0.5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem building with Continuum
Problem resolved. The local system user on my build box was missing the repository folder under C:/Documents and Settings/Default User/.m2. The only file in this folder is the parent pom.xml. Does anyone know why this file must be in here instead of the 'regular' repositories? Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. 843-849-7476 ext. 6394 843-849-9485 (Fax) -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:45 AM To: continuum-users@maven.apache.org; users@maven.apache.org Subject: RE: Problem building with Continuum I was able to build from my local machine. I had forgotten to change my settings.xml for maven. After copying the settings.xml from my continuum build box, I can successfully build via the command line. So this brings me back to a missing or corrupt setting in Continuum that is not looking at the right repo. Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 7:26 AM To: continuum-users@maven.apache.org Subject: RE: Problem building with Continuum I can successfully build from the command line on the box where my repositories and continuum instances live, however, I cannot build from the command line from any other machine due to the same error. This would lead me to believe that there is a corruption in my maven install since it has been working fine for months. Any help would be greatly appreciated. Thanks, Doug Tanner Operations Engineer Benefitfocus.com, Inc. -Original Message- From: Doug Tanner [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 1:53 PM To: continuum-users@maven.apache.org Subject: Problem building with Continuum Today, I began experiencing build problems with Continuum due to the following error. The pom in question is in the repository. I have tried deleting the file from the repo and adding it back in to no avail. Below the error message is my m2 settings.xml file. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run()V(Unknown Source) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from D:\continuum\security\continuum-1.0.3\apps\continuum\working-directory\1 27\pom.xml (Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: bf.platform:bf.platform.parent for project: bf.enrollmentweb.portal:portal:war:SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'bf.platform:bf.platform.parent' not found in repository: Unable to download the artifact from any repository bf.platform:bf.platform.parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:1157)
Re: Surefire 2.3
On 22 Feb 07, at 11:30 AM 22 Feb 07, Martin Gilday wrote: Hi, Is there any idea yet of when we can expect surefire 2.3 to be released? Brett started looking at Surefire again and hopes to do a release as soon as he can. Looking at JIRA there are still a lot of tasks pending, but also quite a few fixes complete. Is it possible that some of these open issues could be pushed back to 2.4? The reason being that now Bamboo is 1.0 it is still suffering from this bug http://jira.atlassian.com/browse/BAM-732 which is caused by http://jira.codehaus.org/browse/SUREFIRE-122?rc=1 which is fixed. This makes all the nice reporting from Bamboo pointless as it thinks I have 24000 tests rather than 805. Yah, there are 20 or so issues that have been resolved and that probably does warrant a release before forging ahead. As I imagine it will take a least a week of work to make any headway with the issues that currently exist. I'll bring it up on the list and see if Brett will push you out a release before digging in. Thanks, Jason. Thanks, Martin. - 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]
Re: Surefire 2.3
Thanks for the update Jason, it is appreciated. - Original message - From: Jason van Zyl [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Date: Thu, 22 Feb 2007 11:37:10 -0500 Subject: Re: Surefire 2.3 On 22 Feb 07, at 11:30 AM 22 Feb 07, Martin Gilday wrote: Hi, Is there any idea yet of when we can expect surefire 2.3 to be released? Brett started looking at Surefire again and hopes to do a release as soon as he can. Looking at JIRA there are still a lot of tasks pending, but also quite a few fixes complete. Is it possible that some of these open issues could be pushed back to 2.4? The reason being that now Bamboo is 1.0 it is still suffering from this bug http://jira.atlassian.com/browse/BAM-732 which is caused by http://jira.codehaus.org/browse/SUREFIRE-122?rc=1 which is fixed. This makes all the nice reporting from Bamboo pointless as it thinks I have 24000 tests rather than 805. Yah, there are 20 or so issues that have been resolved and that probably does warrant a release before forging ahead. As I imagine it will take a least a week of work to make any headway with the issues that currently exist. I'll bring it up on the list and see if Brett will push you out a release before digging in. Thanks, Jason. Thanks, Martin. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HowTo access project version programmatically in application
Make your version a property, use the same property in your version element and when generating a manifest. Or, use maven-buildnumber-plugin. Kalle On 2/22/07, Roland Klein [EMAIL PROTECTED] wrote: Hi, HowTo access project version programmatically in application? At the moment we enter the version string manually in one of our classes. Is there a way to access the project version at runtime? One of my thoughts are to generate a Version class holding the version string, but is there a more convenient way? Thanks in advance Roland -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven1's repo is more up-to-date than Maven2's repo? (missing jars in Maven2's repo)
you are talking about a maven 1 plugin. M1 plugins don't work with m2, that's why is not in the maven2 repository On 2/22/07, Eus [EMAIL PROTECTED] wrote: Hi Ho! Why the public repository for Maven2 (http://repo1.maven.org/maven2/) does not contain all jars exists in the public repository for Maven1 (http://repo1.maven.org/maven/)? For example, in the Maven1's repo you can get maven-xdoclet-plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in the Maven2's repo in http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the latest version there is 1.2. My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's repo, right? Thank you very much for your explanation. -- View this message in context: http://www.nabble.com/Maven1%27s-repo-is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in-Maven2%27s-repo%29-tf3272775s177.html#a9099988 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven1's repo is more up-to-date than Maven2's repo? (missing jars in Maven2's repo)
On 22 Feb 07, at 12:08 PM 22 Feb 07, Carlos Sanchez wrote: you are talking about a maven 1 plugin. M1 plugins don't work with m2, that's why is not in the maven2 repository They need to be as we're eventually going to serve everything from the m2 repository. So they need to be there. A mod_proxied request will go to the m2 repository and it may very well need m1 plugins. Jason. On 2/22/07, Eus [EMAIL PROTECTED] wrote: Hi Ho! Why the public repository for Maven2 (http://repo1.maven.org/ maven2/) does not contain all jars exists in the public repository for Maven1 (http://repo1.maven.org/maven/)? For example, in the Maven1's repo you can get maven-xdoclet- plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in the Maven2's repo in http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the latest version there is 1.2. My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's repo, right? Thank you very much for your explanation. -- View this message in context: http://www.nabble.com/Maven1%27s- repo-is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in- Maven2%27s-repo%29-tf3272775s177.html#a9099988 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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]
Problem re-signing a jar file
Im building an applet using maven2 and in order to have an easier time
deploying it, I want to integrate all of it's dependencies along with
the applet code into a single jar using the dependency plugin.
One of those dependencies is a signed applet and of course the
certificate and the signatures are also unpacked by the dependency
plugin.
Now I'm trying to sign my applet using jar:sign and here a problem
appears: the jar plugin reports an error saying jarsigner:
java.lang.SecurityException: Invalid signature file digest for Manifest
main attributes.
Configuring verify to false doesn't help - the jarsigner is always run
with the -verify flag.
Signing the same file by hand poses no problems as long as I avoid using
the -verify flag.
Any clues what I could do to avoid this failure?
Cheers,
Gottfried
P.S.:
Find attached my POM and an error log produced by mvn -X
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdde.haufe.iDesk/groupId
artifactIdShellExecuteApplet/artifactId
packagingjar/packaging
version1.0/version
nameShellExecuteApplet/name
urlhttp://www.haufe.de/url
dependencies
dependency
groupIdde.haufe.iDesk.jar/groupId
artifactIdjShellExecute/artifactId
typejar/type
version1.0/version
scopecompile/scope
/dependency
/dependencies
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.4/source
target1.4/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
goals
goalsign/goal
/goals
/execution
/executions
configuration
alias${signature.alias}/alias
type${haufe.keystore.type}/type
storepass${haufe.storepass}/storepass
keystore${haufe.keystore}/keystore
verbosetrue/verbose
verifyfalse/verify
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy/id
phasecompile/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdde.haufe.iDesk.dll/groupId
artifactIdjShellExecute/artifactId
version1.0/version
typedll/type
outputDirectorytarget/classes/outputDirectory
overWritetrue/overWrite
destFileNamejShellExecute.dll/destFileName
/artifactItem
/artifactItems
/configuration
/execution
execution
idunpack/id
phasecompile/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdde.haufe.iDesk.jar/groupId
artifactIdjShellExecute/artifactId
version1.0/version
typejar/type
outputDirectorytarget/classes/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
/plugins
/build
distributionManagement
repository
idlocal/id
nameHelios/name
urlscpexe://helios.haufe-ep.de/home/maven/maven-proxy/target/repo/url
/repository
/distributionManagement
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: HowTo access project version programmatically in application
On 22 Feb 07, at 11:02 AM 22 Feb 07, Roland Klein wrote: Hi, HowTo access project version programmatically in application? Every JAR created with Maven embeds a properties which you can use to get the version from. This is what we do: http://svn.apache.org/repos/asf/maven/components/trunk/maven-core/src/ main/java/org/apache/maven/execution/DefaultRuntimeInformation.java Jason. At the moment we enter the version string manually in one of our classes. Is there a way to access the project version at runtime? One of my thoughts are to generate a Version class holding the version string, but is there a more convenient way? Thanks in advance Roland -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571 - 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]
Re: [M2] runtime scope but not transitive
Thanks Rodrigo for your reply. I think provided is the right value for this I prefer to say provided is the best solution (compared with the others) but not the right. Why ? Because if you need my warModule, you will see that it has a dependency to implJarModule with the provided scope. So you will think that implJarModule is needed for compilation. But it's not true, because warModule just need it for runtime. As a result, you will add a dependency for implJarModule with a compile scope rather than a runtime scope. Regards, Rémy
Finding where the jar came from...
Can anyone tell me the quick-n-dirty way to figure out which dependency is responsible for a jar that is being transitively downloaded/included in the project? For instance, I see the servlet-api jar showing up in my assembly, but don't need it. I've already excluded it once from the spring dependency like so: dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.2/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency I just need to find out if another one of my dependencies depends on the servlet-api. Could it be the case that the assembly plugin doesn't grock that I said to exclude when I specified the spring dependency? TIA... Bryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mojo accessing project properties
Adding @requiresProject does nothing. Interestingly, I'm getting the
dependencies just fine without having @requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Anyway, I think I've found the problem with project.properties showing
up empty in the plugin. The problem is in the Plexus code. I will post
my findings in a separate email.
..David..
-Original Message-
From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 11:02 PM
To: Maven Users List
Subject: Re: Mojo accessing project properties
Hi, you need annotate you mojo with @requiresProject tag:
/**
* Verifies that the dependencies of the project are official.
*
* @goal verify
*
* @phase validate
* @requiresProject
* @requiresDependencyResolution
*/
public class VerifyDependenciesMojo extends AbstractMojo { ... }
So, maven will do all stuff that is necessary to parse pom and create
MavenProject object before start your mojo. Because you need to access
dependencies project, you also need to use the
@requiresDependencyResolution.
Hope this helps.
On 2/17/07, David Jackman [EMAIL PROTECTED] wrote:
At this point, it's a simple mojo that I'm executing via the command
line (trying to figure out how I can get at this information and what
form it comes in since no docs explain this). This mojo will
eventually be attached to the verify phase, and that's what's in the
mojo now. Are the properties not available at that stage? The entire
mojo code is below.
..David..
/**
* Verifies that the dependencies of the project are official.
*
* @goal verify
*
* @phase validate
*/
public class VerifyDependenciesMojo extends AbstractMojo {
/**
* Dependencies to verify.
* Items in the list will be of type
org.apache.maven.model.Dependency .
*
* @parameter default-value=${project.dependencies}
* @required
* @readonly
*/
private List dependencies;
/**
* Project properties.
*
* @parameter default-value=${project.properties}
* @required
* @readonly
*/
private Properties properties;
/**
* @see AbstractMojo#execute()
*/
public void execute() throws MojoExecutionException,
MojoFailureException
{
getLog().debug(Properties: + properties);
}
}
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Fri 2/16/2007 8:38 PM
To: Maven Users List
Subject: Re: Mojo accessing project properties
What's the rest of your mojo look like?
Are you using @execute phase=something?
Jason.
On 16 Feb 07, at 4:43 PM 16 Feb 07, David Jackman wrote:
I'm trying to write a mojo that accesses the properties section of
the project pom. I declared a member variable like this
/**
* Project properties.
*
* @parameter default-value=${project.properties}
* @required
* @readonly
*/
private Properties properties;
When my mojo runs, it gets a Properties object okay, but it's always
empty, even if I have declared properties in the project POM.
Am I doing something wrong? How do I access the project properties
(not plugin configuration properties)?
..David..
-
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]
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Get the scm settings from plugin
Thanks, it works!
Does that work for the other objects in the model?
For example if I also want to get the license information can I use
${project.license} to get a License object from model?
Is that functionality documented anywhere?
David Jackman wrote:
It seems project.properties will always be empty (I've been working on
that issue in the Mojo accessing project properties thread in this
forum).
However, what you want isn't in the properties anyway. What you want is
the project.scm value. Declare your plugin field like this:
/**
* Source control information.
* @parameter expression=${project.scm}
* @required
* @readonly
*/
private org.apache.maven.model.Scm scm;
You'll need to add maven-model as a dependency to your plugin as well:
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-model/artifactId
version2.0.4/version
/dependency
That should be enough to get the scm information in your plugin.
..David..
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 9:01 AM
To: users@maven.apache.org
Subject: Get the scm settings from plugin
I would like to be able to access the scm settings (connection, tag,
etc) in the pom.xml from within a plugin. Is this possible? It seems
like there should be an easy way to get access to all of the pom
configuration from within a plugin, but I haven't found it yet. I tried
looking in project.properties, but it was empty. Is project.properties
used for anything?
Thanks!
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Finding where the jar came from...
I think mvn site will give you the dependenecy report. -D On 2/22/07, Bryan Noll [EMAIL PROTECTED] wrote: Can anyone tell me the quick-n-dirty way to figure out which dependency is responsible for a jar that is being transitively downloaded/included in the project? For instance, I see the servlet-api jar showing up in my assembly, but don't need it. I've already excluded it once from the spring dependency like so: dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.2/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency I just need to find out if another one of my dependencies depends on the servlet-api. Could it be the case that the assembly plugin doesn't grock that I said to exclude when I specified the spring dependency? TIA... Bryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Finding where the jar came from...
On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus: Can anyone tell me the quick-n-dirty way to figure out which dependency is responsible for a jar that is being transitively downloaded/included in the project? For instance, I see the servlet-api jar showing up in my assembly, but don't need it. I've already excluded it once from the spring dependency like so: dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.2/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency I just need to find out if another one of my dependencies depends on the servlet-api. Could it be the case that the assembly plugin doesn't grock that I said to exclude when I specified the spring dependency? You can run $ mvn -o project-info-reports:dependencies to generate the dependency report in target/site/dependencies.html HTH, -Al -- :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: Alan D. Salewski Software Developer Health Market Science, Inc. :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug in Plexus code -- Maven 2.0.5 not using latest version?
In researching why project.properties was coming up empty for my plugin, I found that the problem was in Plexus code (plexus-container-default-1.0-alpha-9.jar to be exact). Looking up that project, it seems the latest release is 1.0-alpha-17, but if I try to have Maven use that instead, Maven dies very quickly with a NoClassDefFoundError: org/codehaus/plexus/component/repository/exception/ComponentLifecycleExc eption. I did find the source code to 1.0-alpha-9 and verified that a simple fix to the PropertiesConverter class takes care of the problem. How should I file bugs so this can get fixed in Plexus and also so the Maven 2 project will get updated to the latest version of Plexus (or a patch of alpha-9 with the fix)? ..David..
RE: Hibernate3:hbm2doc
Hello Jim Actually I thought I added support for graphviz but doesn't look like it. I'll be adding the support for that for the next version of the plugin. Right now the plugin is in the process of being voted to be released so I won't be doing any changes until the vote process finishes. Regards Johann Reyes -Original Message- From: Crossley, Jim [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 21, 2007 10:31 AM To: Maven Users List Subject: Hibernate3:hbm2doc Hi. I'm looking to take advantage of hibernate-tools' abililty to generate a graph of my entity relationships. After looking at MOJO-544 and MOJO-530, I thought it might be as easy as applying the attached patch to the source and setting the dotExecutable property, but that didn't work. I notice the hibernate-tools dep version is 3.2-beta9a -- is that newer than beta9? Should the graphviz stuff be in there? Any other ideas how to generate an ER diagram of my EJB3 entities and include it in my site docs? Thanks, Jim - 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]
Re: Mojo accessing project properties
Hello, David
Adding @requiresProject does nothing.
What about try inject the project object instead project.properties?
/**
* @parameter default-value=${project}
* @required
* @readonly
*/
private MavenProject project;
I know that it is not a neat solution, but probably will works fine for you.
Interestingly, I'm getting the dependencies just fine without having
@requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Not sure about it, but maybe it is working because dependencies were already
processed when your mojo is activated.
Kind Regards,
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
easiest way to do testing, that WORKS?
Dear Maven users, I've just spent a frustrating afternoon trying to get TestNG to call the test method of my test class, but without success! Would some kind person please paste into a reply some xml snippets (TestNG or JUnit) that actually work. Thanks and regards, Rob West Mids, UK - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Get the scm settings from plugin
It's not documented anywhere that I know of. I've been sitting on the
source code with this project.properties problem and figured out how
most things come out. I should create a wiki page for it--a mapping of
pom elements to their respective Maven-model types.
..David..
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:04 AM
To: Maven Users List
Subject: Re: Get the scm settings from plugin
Thanks, it works!
Does that work for the other objects in the model?
For example if I also want to get the license information can I use
${project.license} to get a License object from model?
Is that functionality documented anywhere?
David Jackman wrote:
It seems project.properties will always be empty (I've been working on
that issue in the Mojo accessing project properties thread in this
forum).
However, what you want isn't in the properties anyway. What you want
is the project.scm value. Declare your plugin field like this:
/**
* Source control information.
* @parameter expression=${project.scm}
* @required
* @readonly
*/
private org.apache.maven.model.Scm scm;
You'll need to add maven-model as a dependency to your plugin as well:
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-model/artifactId
version2.0.4/version
/dependency
That should be enough to get the scm information in your plugin.
..David..
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 9:01 AM
To: users@maven.apache.org
Subject: Get the scm settings from plugin
I would like to be able to access the scm settings (connection, tag,
etc) in the pom.xml from within a plugin. Is this possible? It seems
like there should be an easy way to get access to all of the pom
configuration from within a plugin, but I haven't found it yet. I
tried looking in project.properties, but it was empty. Is
project.properties used for anything?
Thanks!
-
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]
-
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]
Re: Bug in Plexus code -- Maven 2.0.5 not using latest version?
On 22 Feb 07, at 1:16 PM 22 Feb 07, David Jackman wrote: In researching why project.properties was coming up empty for my plugin, I found that the problem was in Plexus code (plexus-container-default-1.0-alpha-9.jar to be exact). Looking up that project, it seems the latest release is 1.0-alpha-17, but if I try to have Maven use that instead, Maven dies very quickly with a NoClassDefFoundError: org/codehaus/plexus/component/repository/exception/ ComponentLifecycleExc eption. I did find the source code to 1.0-alpha-9 and verified that a simple fix to the PropertiesConverter class takes care of the problem. How should I file bugs so this can get fixed in Plexus and also so the Maven 2 project will get updated to the latest version of Plexus (or a patch of alpha-9 with the fix)? Create an issue in PLX with your fix, and link it to the issue in Maven. Create the issue in Maven if necessary. Ping me when you've done that and I will schedule it for 2.0.6. Jason. ..David.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 - POM inheritance issue with Developers Contributors sections?
The output of 'mvn help:effective-pom shows that developer info from the parent POM is not being merged into its child POMs. I will create a JIRA issue so it can be addressed. Thanks. Brad On Thu, 2007-02-22 at 11:56 -0600, Eric Redmond wrote: Try running mvn help:effective-pom... if they aren't merged, then either the code or doc needs updated. Thanks; Eric On 2/22/07, Brad Szabo [EMAIL PROTECTED] wrote: Hey everyone. I have a quick question. Isn't the developers and contributors info supposed to be merged, not overridden from parent to child POMs? My project has a chief architect/developer over all of the sub-projects and I am trying to list him once in the parent POM, and then add developers working on specific sub-projects in the child POMs accordingly. His information is not being merged into the effective POM of the child projects. According to the Project Inheritance section of http://maven.apache.org/guides/introduction/introduction-to-the-pom.html this info should be merged. Has anyone else run into this? I searched JIRA and could not find an issue about this. Thanks, Brad P.S. I am using Maven 2.0.5 - 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]
tools.jar path
Why is this
http://maven.apache.org/general.html#tools-jar-dependency
suggested? Why it is not
systemPath${java.home}/lib/tools.jar/systemPath
If developing with Eclipse then under Help About Eclipse SDK
Configuration Details my Eclipse says
java.home=C:\Program Files\Java\jre1.5.0_11
I have JAVA_HOME environment system user variable set to C:\Program
Files\Java\jdk1.5.0_011 which has no effect on the Eclipse's java.home
variable.
Now, when a project with a (transitive) dependency to tools.jar in way
suggested in the FAQ exists, there is no way for maven embedder to
resolve the tools.jar.
The only solution is to start the Eclipse with the
-Djava.home=C:\Program Files\Java\jdk1.5.0_11\jre.
I guess all developers have JDK installed and not only JRE. Am I missing
something?
Regards,
Borut
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: tools.jar path
Borut Bolčina wrote: I guess all developers have JDK installed and not only JRE. Am I missing something? I *think* OS X has no separate tools.jar. Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Finding where the jar came from...
Thanks for the feedback. I'm trying to use the project-info-reports plugin, and am getting the following: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' does not exist or no valid version could be found ...which seems odd to me, because I can see it right here: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/ Any ideas? Alan D. Salewski wrote: On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus: Can anyone tell me the quick-n-dirty way to figure out which dependency is responsible for a jar that is being transitively downloaded/included in the project? For instance, I see the servlet-api jar showing up in my assembly, but don't need it. I've already excluded it once from the spring dependency like so: dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.2/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency I just need to find out if another one of my dependencies depends on the servlet-api. Could it be the case that the assembly plugin doesn't grock that I said to exclude when I specified the spring dependency? You can run $ mvn -o project-info-reports:dependencies to generate the dependency report in target/site/dependencies.html HTH, -Al
Re: Finding where the jar came from...
Nevermind... I did it with a '-U' arg tacked on, and it worked... Thanks again for the help. Bryan Noll wrote: Thanks for the feedback. I'm trying to use the project-info-reports plugin, and am getting the following: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' does not exist or no valid version could be found ...which seems odd to me, because I can see it right here: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/ Any ideas? Alan D. Salewski wrote: On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus: Can anyone tell me the quick-n-dirty way to figure out which dependency is responsible for a jar that is being transitively downloaded/included in the project? For instance, I see the servlet-api jar showing up in my assembly, but don't need it. I've already excluded it once from the spring dependency like so: dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.0.2/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency I just need to find out if another one of my dependencies depends on the servlet-api. Could it be the case that the assembly plugin doesn't grock that I said to exclude when I specified the spring dependency? You can run $ mvn -o project-info-reports:dependencies to generate the dependency report in target/site/dependencies.html HTH, -Al
Re: tools.jar path
Manos Batsis wrote: Borut Bolčina wrote: I guess all developers have JDK installed and not only JRE. Am I missing something? I *think* OS X has no separate tools.jar. I am aware of that - OS X Java developers are screwed in both cases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mojo accessing project properties
That works great--the perfect solution for right now as I wait until
this fix is available with Maven 2.0.6.
Thanks!
..David..
-Original Message-
From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:38 AM
To: Maven Users List
Subject: Re: Mojo accessing project properties
Hello, David
Adding @requiresProject does nothing.
What about try inject the project object instead project.properties?
/**
* @parameter default-value=${project}
* @required
* @readonly
*/
private MavenProject project;
I know that it is not a neat solution, but probably will works fine for
you.
Interestingly, I'm getting the dependencies just fine without having
@requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Not sure about it, but maybe it is working because dependencies were
already processed when your mojo is activated.
Kind Regards,
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mojo accessing project properties
On 22 Feb 07, at 3:11 PM 22 Feb 07, David Jackman wrote:
That works great--the perfect solution for right now as I wait until
this fix is available with Maven 2.0.6.
Once in JIRA you can watch it and use a snapshot build once it's fixed.
Jason.
Thanks!
..David..
-Original Message-
From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:38 AM
To: Maven Users List
Subject: Re: Mojo accessing project properties
Hello, David
Adding @requiresProject does nothing.
What about try inject the project object instead project.properties?
/**
* @parameter default-value=${project}
* @required
* @readonly
*/
private MavenProject project;
I know that it is not a neat solution, but probably will works fine
for
you.
Interestingly, I'm getting the dependencies just fine without having
@requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Not sure about it, but maybe it is working because dependencies were
already processed when your mojo is activated.
Kind Regards,
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
-
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]
strange hibernatedoclet and war not adding hbm files
I have hibernatedoclet generating several hbm files from my DAO.jar and
adding them to my common-jar module. Seems to be an issue with Xdoclet1
Maven.
No matter, my app.war seems to suck in the 1st hbm file but not the rest
into the webapp/classes/*
What am I missing to get all the hbm files included?
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
hibernatedoclet destdir=${
project.build.outputDirectory}
mergedir=${basedir}/src/main/resources
excludedtags=@version,@author,@todo,@see,@desc
verbose=true
fileset
dir=${basedir}/src/main/java
include name=**/*.java/
/fileset
hibernate version=3.0/
/hibernatedoclet
/tasks
/configuration
/execution
/executions
/plugin
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
RE: Mojo accessing project properties
Well, since this is a jar included in the core directory of Maven 2.0.5,
I can't just reference a snapshot build from the plugin. I would have
to tell all the developers in the company to patch the jar in their
Maven installation. Having the plugin just use project will be easier
than trying to scale an unreleased fix, especially since the plugin
won't be able to detect an unpatched installation since having no
properties is a valid state.
..David..
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 1:15 PM
To: Maven Users List
Subject: Re: Mojo accessing project properties
On 22 Feb 07, at 3:11 PM 22 Feb 07, David Jackman wrote:
That works great--the perfect solution for right now as I wait until
this fix is available with Maven 2.0.6.
Once in JIRA you can watch it and use a snapshot build once it's fixed.
Jason.
Thanks!
..David..
-Original Message-
From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:38 AM
To: Maven Users List
Subject: Re: Mojo accessing project properties
Hello, David
Adding @requiresProject does nothing.
What about try inject the project object instead project.properties?
/**
* @parameter default-value=${project}
* @required
* @readonly
*/
private MavenProject project;
I know that it is not a neat solution, but probably will works fine
for you.
Interestingly, I'm getting the dependencies just fine without having
@requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Not sure about it, but maybe it is working because dependencies were
already processed when your mojo is activated.
Kind Regards,
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] POM Inheritance
I still haven't found a good solution for this and I was hoping to spark some
discussion with a follow up post.
jp4 wrote:
I was wondering if there is any way to achieve multiple pom inheritance
with maven. I have created several pom abstractions (i.e. data access
which includes dependencies for hibernate, spring, etc... webapp which
includes dependencies for struts, etc) for convenience as most of my data
access projects follow the same pattern using hibernate and spring. I
don't want to have to redefine these dependencies in each of my data
access projects.
Now here is where the problem comes in, I have a multi-module projectA
that has a model, data access, webapp projects. In addition, I have a
multi-module projectB that has a model, data access, webapp project. I
would like to have all modules in projectA have the same version so that I
can refer to version for projectA as ${project.version} in my model, data
access, and webapp. The problem that I have is that I want projectA's
data access project to inherit from both the data access pom as well as
the projectA pom. Is there any way to do this? Or is there a different
approach to achieve the desired results?
Thanks,
jp4
--
View this message in context:
http://www.nabble.com/POM-Inheritance-tf3164691s177.html#a9107889
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven scm
I just noticed that scm (for cvs) is adding the -t flag for tracing. Is this new to the 1.0.4-beta-4 scm plugin? Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How can I excluding a generated source from a compile step
I am using the axistools-maven-plug-in to generate my server side classes for a web service. I use the following plugin definition: plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.0/version configuration packageSpace com.terranua.mco.charts.webservice /packageSpace serverSidetrue/serverSide testCasesfalse/testCases allElementsfalse/allElements subPackageByFileNamefalse/subPackageByFileName /configuration executions execution goals goalwsdl2java/goal /goals /execution /executions /plugin It generates the following files for me in .\target\generated-sources\axistools\wsdl2java\com\terranua\mco\charts\webse rvice: deploy.wsdd GraphDataService.java GraphDataServiceLocator.java GraphDataSoapBindingImpl.java GraphDataSoapBindingStub.java GraphData_PortType.java undeploy.wsdd My problem is that I need to exclude GraphDataSoapBindingImpl.java from the compile step because I already have that implemented. Is there anyway to excluded a single file from the generated sources or does anybody know of a way to get the axistools-maven-plugin to avoid generating GraphDataSoapBindingImpl.java in the first place. Thanks for your help, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I excluding a generated source from a compile step
1. use antrun to remove generated file(s) before compile phase On 2/22/07, Matthews, Brian [EMAIL PROTECTED] wrote: I am using the axistools-maven-plug-in to generate my server side classes for a web service. I use the following plugin definition: plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.0/version configuration packageSpace com.terranua.mco.charts.webservice /packageSpace serverSidetrue/serverSide testCasesfalse/testCases allElementsfalse/allElements subPackageByFileNamefalse/subPackageByFileName /configuration executions execution goals goalwsdl2java/goal /goals /execution /executions /plugin It generates the following files for me in . \target\generated-sources\axistools\wsdl2java\com\terranua\mco\charts\webservice: deploy.wsdd GraphDataService.java GraphDataServiceLocator.java GraphDataSoapBindingImpl.java GraphDataSoapBindingStub.java GraphData_PortType.java undeploy.wsdd My problem is that I need to exclude GraphDataSoapBindingImpl.java from the compile step because I already have that implemented. Is there anyway to excluded a single file from the generated sources or does anybody know of a way to get the axistools-maven-plugin to avoid generating GraphDataSoapBindingImpl.java in the first place. Thanks for your help, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How can I excluding a generated source from a compile step
Not as pretty as I hoped but works. Thanks Dan. -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 9:45 PM To: Maven Users List Subject: Re: How can I excluding a generated source from a compile step 1. use antrun to remove generated file(s) before compile phase On 2/22/07, Matthews, Brian [EMAIL PROTECTED] wrote: I am using the axistools-maven-plug-in to generate my server side classes for a web service. I use the following plugin definition: plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.0/version configuration packageSpace com.terranua.mco.charts.webservice /packageSpace serverSidetrue/serverSide testCasesfalse/testCases allElementsfalse/allElements subPackageByFileNamefalse/subPackageByFileName /configuration executions execution goals goalwsdl2java/goal /goals /execution /executions /plugin It generates the following files for me in . \target\generated-sources\axistools\wsdl2java\com\terranua\mco\charts\webser vice: deploy.wsdd GraphDataService.java GraphDataServiceLocator.java GraphDataSoapBindingImpl.java GraphDataSoapBindingStub.java GraphData_PortType.java undeploy.wsdd My problem is that I need to exclude GraphDataSoapBindingImpl.java from the compile step because I already have that implemented. Is there anyway to excluded a single file from the generated sources or does anybody know of a way to get the axistools-maven-plugin to avoid generating GraphDataSoapBindingImpl.java in the first place. Thanks for your help, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum with Postgres (under JBoss) ???
I've just posted this to JIRA ( http://jira.codehaus.org/browse/CONTINUUM-1181). On 2/21/07, Thierry Lach [EMAIL PROTECTED] wrote: I'm trying to get Continuum to store its data in a postgres database while running under JBoss and I'm getting an exception. It seems that someone is trying to change the transaction isolation during a transaction. I'm running postgres 8.1.4-1 on MS Windows (and am using the driver jar postgresql-8.1-408.jdbc3). Any ideas? Excerpt from JBoss logs follows... snip/
[M2] Trouble deploying a file via FTP
I am trying to use deploy:deploy-file to deploy a 3rd party jar to our company repository. I have included the wagon extension in a POM like so (though I don't understand why FTP doesn't just work): build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ftp/artifactId version1.0-beta-2/version /extension /extensions /build Now, when I try to build (specifying the pomfile property), I get the following: [INFO] Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp Component descriptor cannot be found in the component repository: org.apache.maven.wagon.Wagonftp. wagon-ftp is already in my local repository. Anyone have an idea what the problem could be? -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help with assembler issue on release
Hi all,
I'm running into a very strange issue that I can't seem to find a solution
for. I'm using the assembly plugin to create a zip with my jar file, all
transitive dependencies, and a few jsp files that get added to an existing
webapp. I have the following directory structure
src/main/java
src/main/config/classes
src/main/config/static-content
src/main/config/web
When I run the following command in the project, the zip file contains
classes, static-content, and web.
mvn clean package
However, when I prepare are release and perform a release, the release only
contains the classes, not static-content, or the web directory. If I view
the source that has been checked out and perform a recursive diff with my
existing source, only the POM is modified. If I change directories to the
target/checkout and execute the same command, I still only get the classes
directory. Is this some sort of lifecycle problem when I'm not building a
snapshot? Below is my assembly descriptor (bin.xml) and my pom.
Thanks,
Todd
Assembly:
assembly
idwith-configuration/id
formats
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
moduleSets
moduleSet
includes
includecom.purdueefcu.onlinebanking:mortgageware/include
/includes
binaries
outputDirectorymodules/${artifactId}/outputDirectory
includeDependenciestrue/includeDependencies
unpackfalse/unpack
/binaries
/moduleSet
/moduleSets
fileSets
fileSet
directorysrc/main/config/directory
outputDirectoryconfiguration/outputDirectory
includes
include**/**/include
/includes
/fileSet
/fileSets
dependencySets
dependencySet
outputDirectory//outputDirectory
unpackfalse/unpack
scoperuntime/scope
/dependencySet
/dependencySets
/assembly
POM
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdconfig/artifactId
groupIdcom.purdueefcu.standards/groupId
version1.0.0/version
/parent
modelVersion4.0.0/modelVersion
groupIdcom.purdueefcu.onlinebanking/groupId
artifactIdmortgageware/artifactId
packagingjar/packaging
nameOnlineBanking Mortagware Integration/name
version1.0.0-SNAPSHOT/version
descriptionLink to our online account applications/description
developers
developer
nameTodd Nine/name
email[EMAIL PROTECTED]/email
organization
Purdue Employees Federal Credit Union
/organization
/developer
/developers
scm
connectionscm:svn:
http://sourceforge.purdueefcu.com/svn/repos/olb20/mortgages//connection
developerConnectionscm:svn:
http://sourceforge.purdueefcu.com/svn/repos/olb20/mortgages/
/developerConnection
urlhttp://sourceforge.purdueefcu.com/svn/repos/olb20/mortgages/
/url
/scm
organization
namePurdue Employees Federal Credit Untion/name
urlhttp://www.purdueefcu.com/url
/organization
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
idassembly:package/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptors
descriptor
src/assemble/bin.xml
/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
/plugins
/build
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdcom.summit/groupId
artifactIdpathways/artifactId
version2.0.0/version
/exclusions
/dependency
dependency
groupIdcom.fiserv.summit/groupId
artifactIdeMember/artifactId
version2.0.0/version
scopeprovided/scope
/dependency
dependency
groupIddom4j/groupId
artifactIddom4j/artifactId
version1.1/version
scopeprovided/scope
/dependency
dependency
RE: Bug in Plexus code -- Maven 2.0.5 not using latest version?
Okay, these bugs are now filed. The Plexus bug is PLX-327 (http://jira.codehaus.org/browse/PLX-327) and the Maven bug is MNG-2843 (http://jira.codehaus.org/browse/MNG-2843). ..David.. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 12:04 PM To: Maven Users List Subject: Re: Bug in Plexus code -- Maven 2.0.5 not using latest version? On 22 Feb 07, at 1:16 PM 22 Feb 07, David Jackman wrote: In researching why project.properties was coming up empty for my plugin, I found that the problem was in Plexus code (plexus-container-default-1.0-alpha-9.jar to be exact). Looking up that project, it seems the latest release is 1.0-alpha-17, but if I try to have Maven use that instead, Maven dies very quickly with a NoClassDefFoundError: org/codehaus/plexus/component/repository/exception/ ComponentLifecycleExc eption. I did find the source code to 1.0-alpha-9 and verified that a simple fix to the PropertiesConverter class takes care of the problem. How should I file bugs so this can get fixed in Plexus and also so the Maven 2 project will get updated to the latest version of Plexus (or a patch of alpha-9 with the fix)? Create an issue in PLX with your fix, and link it to the issue in Maven. Create the issue in Maven if necessary. Ping me when you've done that and I will schedule it for 2.0.6. Jason. ..David.. - 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]
Maven 2 compile and IBM javac
I am getting the following error with maven 2 configured to use ibm
1.4. When I switch back to the sun jdk I get no error. Any ideas how
I can get this to give me more info?
Here is the relevant section of my pom:
in properties
ibm-jdk-pathc:/was6/java/bin/javac/ibm-jdk-path
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
verbosetrue/verbose
forktrue/fork
executable${ibm-jdk-path}/executable
compilerVersion1.4/compilerVersion
/configuration
/plugin
the ibm java info
java version 1.4.2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build
cn142-20050609 (JIT enabled: jitc))
[exec] [INFO]
[exec] [ERROR] BUILD FAILURE
[exec] [INFO]
[exec] [INFO] Compilation failure
[exec] Failure executing javac, but could not parse the error:
[exec] [INFO]
[exec] [INFO] Trace
[exec] org.apache.maven.BuildFailureException: Compilation failure
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
[exec] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
[exec] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
[exec] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[exec] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:585)
[exec] at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
[exec] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
[exec] at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
[exec] at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[exec] Caused by:
org.apache.maven.plugin.CompilationFailureException: Compilation
failure
[exec] at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
[exec] at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
[exec] at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
[exec] ... 16 more
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven 2 site plugin and attributes parameter
I'm attempting to inject attributes into the site plugin like so in my pom:
configuration
attributes
foobar/foo
/attributes
moduleExcludes
foobar/foo
/moduleExcludes
templatesite.vm/template
/configuration
/plugin
Supposedly I'm allowed to do this according to the online documentation, and
according to the annotation on the attributes field of the
AbstractSiteRender class.
However, when running 'mvn -X site', the attributes do not show up:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-site-plugin:2.0-beta-5:site' --
[DEBUG] (f) generateReports = true
[DEBUG] (f) generatedSiteDirectory =
/Users/esm/workspace/pluto11trunk/pluto-site/target/generated-site
[DEBUG] (f) inputEncoding = ISO-8859-1
[DEBUG] (f) localRepository = [local] - file:///Users/esm/.m2/repository
[DEBUG] (f) outputDirectory =
/Users/esm/workspace/pluto11trunk/pluto-site/target/site
[DEBUG] (f) outputEncoding = ISO-8859-1
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) reactorProjects =
[EMAIL PROTECTED]
[DEBUG] (f) reports =
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
[DEBUG] (f) repositories = [[apache.snapshots] -
http://people.apache.org/repo/m2-snapshot-repository, [central] -
http://repo1.maven.org/maven2]
[DEBUG] (f) siteDirectory =
/Users/esm/workspace/pluto11trunk/pluto-site/src/site
[DEBUG] (f) template = site.vm
[DEBUG] (f) templateDirectory =
/Users/esm/workspace/pluto11trunk/pluto-site/src/site
[DEBUG] (f) xdocDirectory =
/Users/esm/workspace/pluto11trunk/pluto-site/xdocs
[DEBUG] -- end configuration --
I've added debugging to the AbstractSiteRenderingMojo, and indeed the
attributes Map is null, despite it being configured in the POM.
I've discovered that if I change
/**
* @parameter expression=${attributes}
*/
protected Map attributes;
to (take away expression=${attributes}):
/**
* @parameter
*/
protected Map attributes;
and re-install the site plugin, my configuration/attributes element is
used.
Any ideas?
Thanks,
Elliot
--
View this message in context:
http://www.nabble.com/maven-2-site-plugin-and-attributes-parameter-tf3276722s177.html#a9112643
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m1 or m2] aggregated changes was Re: [m2] changes and modules
Hi, I'm a Maven 1.x user and am looking for an aggregated changes report that shows changes for all modules (in reverse chronological order) The multichanges plugin report doesn't do this, as I had hoped. I did a quick Google and searched through my local archive of this list and found the below message. Two questions: 1) Is there an existing way to do this in either m1 or m2? 2) Does m2 use the same format of changes.xml file as m1? If the answer to #1 is no and #2 is yes, I'll probably try writing an XSL to do it. The XSL could theoretically be used in both an m1 and an m2 plugin. Thanks, Sean Denis Cabasson wrote: Damien Viel wrote: Hi all, Is it possible to aggregate in the same report, all changes report from modules ? Thanks Damien Not in the current version of the maven-changes plugin. How would you want to see things aggregated? If you have a clear idea of how to aggregate things, you can fill in a JIRA request about this... Denis.
Re: [m2] strange hibernatedoclet and war not adding hbm files
Are you using Maven2?
If yes, it is better if you run XDoclet using maven-antrun-plugin.
This link (http://www.nabble.com/-M2--Struts-and-XDoclet-t1775233.html)
gives the reason.
Also, below is the relevant part of my pom.xml that I use to generate my
web.xml (using webdoclet).
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idxdoclet-processing/id
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
taskdef name=webdoclet
classname=xdoclet.modules.web.WebDocletTask
classpath refid=maven.compile.classpath/
/taskdef
webdoclet destDir=${basedir}/src/main/webapp/WEB-INF
fileset dir=${basedir}/src/main/java
includes=**/*.java/
deploymentdescriptor
destDir=${basedir}/src/main/webapp/WEB-INF /
/webdoclet
/tasks
/configuration
/execution
/executions
/plugin
...
/plugins
/build
...
dependencies
...
dependency
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet/artifactId
version1.2.3/version
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxjavadoc/artifactId
version1.1/version
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-web-module/artifactId
version1.2.3/version
/dependency
/dependencies
HTH.
Mick Knutson-4 wrote:
I have hibernatedoclet generating several hbm files from my DAO.jar and
adding them to my common-jar module. Seems to be an issue with Xdoclet1
Maven.
No matter, my app.war seems to suck in the 1st hbm file but not the rest
into the webapp/classes/*
What am I missing to get all the hbm files included?
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
hibernatedoclet destdir=${
project.build.outputDirectory}
mergedir=${basedir}/src/main/resources
excludedtags=@version,@author,@todo,@see,@desc
verbose=true
fileset
dir=${basedir}/src/main/java
include name=**/*.java/
/fileset
hibernate version=3.0/
/hibernatedoclet
/tasks
/configuration
/execution
/executions
/plugin
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
--
View this message in context:
http://www.nabble.com/strange-hibernatedoclet-and-war-not-adding-hbm-files-tf3275025s177.html#a9114252
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: easiest way to do testing, that WORKS?
My open source project uses TestNG. Check out the pom in svn: http://svn.sourceforge.net/viewvc/vigilog/trunk/ Direct link: http://svn.sourceforge.net/viewvc/vigilog/trunk/pom.xml?view=markup regards, Wim 2007/2/22, Rob Dickens [EMAIL PROTECTED]: Dear Maven users, I've just spent a frustrating afternoon trying to get TestNG to call the test method of my test class, but without success! Would some kind person please paste into a reply some xml snippets (TestNG or JUnit) that actually work. Thanks and regards, Rob West Mids, UK - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vigilog - an open source log file viewer: http://vigilog.sourceforge.net Blog: http://www.jroller.com/page/Fester
Passing parameter to mojo
Hello,
I am trying to pass parameter to Mojo. I have done everything mentioned in
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
When I compile the project, it throws
[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[11,9] in
file:/C:/Documents and Settings/ksuthan/maven/testmaven/20_2/maven-g
reeting-plugin/src/main/java/org/ksuthan/plugins/GreetingMojo.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror (Parser.java
:638)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse (Parser.java
:747)
at com.thoughtworks.qdox.parser.impl.Parser.parse (Parser.java:619)
at com.thoughtworks.qdox.JavaDocBuilder.addSource (
JavaDocBuilder.java:300)
at com.thoughtworks.qdox.JavaDocBuilder.addSource (
JavaDocBuilder.java:316)
at com.thoughtworks.qdox.JavaDocBuilder.addSource (
JavaDocBuilder.java:312)
at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile (
JavaDocBuilder.java:369)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk (
DirectoryScanner.java:43)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk (
DirectoryScanner.java:34)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk (
DirectoryScanner.java:34)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk (
DirectoryScanner.java:34)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk (
DirectoryScanner.java:34)
at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan (
DirectoryScanner.java:52)
at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree (
JavaDocBuilder.java:366)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(
JavaMojoDescriptorExtractor.java:520)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(
DefaultMojoScanner.java:84)
at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute (
AbstractGeneratorMojo.java:135)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo (
DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (
DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments (
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (
DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:256)
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)
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Tue Feb 20 18:14:13 GMT+05:30 2007
[INFO] Final Memory: 5M/9M
[INFO]
Can anyone tell me what is wrong with this? Please
package org.ksuthan.plugins;
import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;
/**
* Says Hi to the user.
* @goal sayhi
* @parameter expression=Hello
*/
private String greeting;
public class GreetingMojo extends AbstractMojo
{
public void execute() throws MojoExecutionException
{
getLog().info(Hello, world.);
}
}
Thanks a lot,
Kiruba
