Re: Resolving Source code dependency among modules?
that kinda defeats the 1 module/1 artifact convention of maven, each project is supposed to be self-contained and the dependency mechanism is the mechanism by which the needed components are referenced. so continuum isn't going to be able to do that if you have the individual components broken out like that, they are not self-contained then. A top lvl build is the best you can hope for in that case. I would consider getting that generated code broken out into its own module and released as its own artifact, then you would be in good shape. jesse On 8/8/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Yes Jesse.. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 8:07 PM To: continuum-users@maven.apache.org Subject: Re: Resolving Source code dependency among modules? so you have a process where you are generating source code from one module for another module? p p/a/ p/b/ so you have A actually generating files into the directories for B? On 8/7/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Hi Jesse, My problem is not w.r.t resolving compile time dependencies (class file dependencies). But it is actually problem of generating source code in a different module. Since Continuum allocates a number for each module in its working directory, I cannot generate the source code of module B from module A. Am using clean package install as my build definition. Regards, Kapil -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 4:34 AM To: continuum-users@maven.apache.org Subject: Re: Resolving Source code dependency among modules? sounds like you need to be having each of the subprojects installing into the local repository so they can be referenced from the other subprojects.. ie, the maven process that is running on each of the subprojects is running as some user, and the local repository for that user is not getting the other subprojects installed into it and are therefore not able to gain access to those generated classes.. I had thought that the install was one of the default build definitions, how are you configured for build definitions right now? jesse On 8/7/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Hi, I have a multi-module (Spring based) project and there is a case where module A is generating source code of module B and module B generates source code of module C. The reason behind this is that I have separated interfaces of my application in module A and using a perl script to generate remote implementations (which internally call local implementation) in module B. Module B again uses perl scripts to generate iiop stubs in module C and Soap adapters in module D. All modules are in parallel i.e. under same parent directory. Am able to compile and package everything if I use a parent pom to build all these modules and specify scm tag there only instead of in each child pom. But in that case I can't build modules individually as there is no SCM tag specified in child modules. Even on specifying scm tag in each module, I can't generate source code of module B from Module A as they are in parallel directories. Is there any way I can refer to module B from module A? Is there any other way to tackle this kind of situation? Thanks, Kapil CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone +91.172.229.9450 or return e-mail message [EMAIL PROTECTED] BLOCKED::mailto:[EMAIL PROTECTED] and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. -- jesse mcconnell [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED]
Re: How to delete build history on continuum
and can i delete this in the database ??? -- View this message in context: http://www.nabble.com/How-to-delete-build-history-on-continuum-tf1378895.html#a5726852 Sent from the Continuum - Users forum at Nabble.com.
RE: Resolving Source code dependency among modules?
Riffing off of Jesse's comments... Since the lifecycle of a project is generate-sources ... compile ... compile-tests ... install the whole notion is really to have generation of code for a module done within the lifecycle build of that module. One way you might be able to approach your a-b-c generation approach (knowing nothing about the details of your code, mind you) would be this. Assuming A has code that can be used to generate sources for B, Compile A, and install. Define A as a compile-only dependency of B (right now there's no such thing exactly, but you can use provided scope to wing-it) Bind the generation capabilities of A to the generate-sources phase of project B (possibly using the ant-run plug-in), to generate B's code within the B lifecycle. Then compile the resulting code in B's compile phase, install, etc. Define B as a compile-only dependency of C Bind the generation capabilities of B to the generate-sources phase of project C, to generate C's code within the C lifecycle. Then compile the resulting code in C's compile phase, install, etc. Rinse and repeat. Regards, Christian. christian gruber + agile coach and architect Israfil Consulting Services Corporation email [EMAIL PROTECTED] + bus +1 (905) 640-1119 cell: +1 (416) 998-6023 + cell: +1 (410) 900-0796 -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 9:15 AM To: continuum-users@maven.apache.org Subject: Re: Resolving Source code dependency among modules? that kinda defeats the 1 module/1 artifact convention of maven, each project is supposed to be self-contained and the dependency mechanism is the mechanism by which the needed components are referenced. so continuum isn't going to be able to do that if you have the individual components broken out like that, they are not self-contained then. A top lvl build is the best you can hope for in that case. I would consider getting that generated code broken out into its own module and released as its own artifact, then you would be in good shape. jesse On 8/8/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Yes Jesse.. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 8:07 PM To: continuum-users@maven.apache.org Subject: Re: Resolving Source code dependency among modules? so you have a process where you are generating source code from one module for another module? p p/a/ p/b/ so you have A actually generating files into the directories for B? On 8/7/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Hi Jesse, My problem is not w.r.t resolving compile time dependencies (class file dependencies). But it is actually problem of generating source code in a different module. Since Continuum allocates a number for each module in its working directory, I cannot generate the source code of module B from module A. Am using clean package install as my build definition. Regards, Kapil -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 4:34 AM To: continuum-users@maven.apache.org Subject: Re: Resolving Source code dependency among modules? sounds like you need to be having each of the subprojects installing into the local repository so they can be referenced from the other subprojects.. ie, the maven process that is running on each of the subprojects is running as some user, and the local repository for that user is not getting the other subprojects installed into it and are therefore not able to gain access to those generated classes.. I had thought that the install was one of the default build definitions, how are you configured for build definitions right now? jesse On 8/7/06, Kapil Gupta(CT) [EMAIL PROTECTED] wrote: Hi, I have a multi-module (Spring based) project and there is a case where module A is generating source code of module B and module B generates source code of module C. The reason behind this is that I have separated interfaces of my application in module A and using a perl script to generate remote implementations (which internally call local implementation) in module B. Module B again uses perl scripts to generate iiop stubs in module C and Soap adapters in module D. All modules are in parallel i.e. under same parent directory. Am able to compile and package everything if I use a parent pom to build all these modules and specify scm tag there only instead of in each child pom. But in that case I can't build modules individually as there is no SCM tag specified in child modules. Even on specifying scm tag in each module, I can't generate source code of module B from Module A as they are in parallel directories. Is there any way I can refer to module B from module A? Is there any other way to tackle this kind of situation?
Re: Blame mechanism with SVN
Emmanuel, I am unsure what language is used by my SVN installation. I looked at the SVN documentation at http://svnbook.red-bean.com/nightly/en/svn-book.html, and there is nothing specific to 'languages'. The SVN book mentions that SVN can work with different locales and print all messages in an appropriate language; if that is the info you are looking for, the SVN client on the CI server is printing out english messages only. Also, although English is not the native tounge of most of us here at our office, all of us converse in English for official purposes. So I would be very surprised if the language is set to anything other than English. :) So can you please let me know how to figure out the language used by my SVN installation? Also, should I be looking for some specific (error) messages in the Contiuum logs? Thanks, Binil On 8/8/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: What is the language used by your svn? I guess it isn't english, right? Emmanuel Binil Thomas a écrit : Hi all, I am using Continuum 1.0.3, Maven 2.0.4 and SVN. Is there anything special I need to do to get the blame mechanism working? I have seen previous posts here, and someone did reply that it is fixed in 1.0.3, but I still am not getting it to work. I am attaching a sample failure email I got. It currently shows the files that are changed, but does not show who changed them. Kindly help me configure the failure email to show the id which changed a file. Thanks, Binil Online report : Build statistics: State: Failed Previous State: Failed Started at: Mon, 7 Aug 2006 15:52:38 +0530 Finished at: Mon, 7 Aug 2006 15:52:59 +0530 Total time: 21s Build Trigger: Forced Exit code: 1 Building machine hostname: MY-BUILD-MACHINE Operating system : Windows 2000(Service Pack 4) Java version : 1.5.0_06(Sun Microsystems Inc.) Changes src\main\java\my\package\MyClass.java Output: [INFO] Scanning for projects... [INFO] [INFO] Building myproject [INFO]task-segment: [clean, install, deploy] [INFO] [INFO] [clean:clean] [INFO] Deleting directory D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target [INFO] Deleting directory D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target\classes [INFO] Deleting directory D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target\test-classes [INFO] [cobertura:clean {execution: clean}] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 68 source files to D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 19 source files to D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: D:\softwares\continuum- 1.0.3\apps\continuum\working-directory\20\target\surefire-reports --- T E S T S --- [..snipped..] Results : Tests run: 61, Failures: 0, Errors: 3, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Mon Aug 07 15:52:59 IST 2006 [INFO] Final Memory: 7M/20M [INFO]
mvn site: NoClassDefFoundError on MacOS X Intel
When running mvn site, I get the following error on a MacOSX Intel box: [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.0.1:cim' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' org/apache/maven/reporting/AbstractMavenReport The full -e trace is listed below. It seems like a classloader issue, as the underlying cause is: Caused by: java.lang.NoClassDefFoundError: org/apache/maven/reporting/AbstractMavenReport The machine is Mac OS X (Intel), 10.4.7, Java 1.5.0_06. I get no errors running the same command on 1.5.0_06 on a Windows XP box. Any ideas? Thanks in advance, Adam Winer FULL STACK TRACE: org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.0.1:cim' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:689) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:512) 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: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.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.0.1:cim' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:533) at org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:462) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:678) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-project-info-reports-plugin:2.0.1:cim', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:524) ... 20 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.apache.maven.report.projectinfo.CimReport' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) ... 22 more Caused by: java.lang.NoClassDefFoundError: org/apache/maven/reporting/AbstractMavenReport at
Re: Continuum on Tomcat?
It will be possible in 1.1 because it will be a webapp. Emmanuel Thomas Van de Velde a écrit : Hi, Is it possible to run Continuum on Tomcat? Right now Continuum does not support HTTPS, which obviously is a no-go in an enterprise deployment over the Internet. Luntbuild e.g. gives me the flexibility to deploy on any app server that I'd like. I use mod_jk with Luntbuild. Can I do the same with Continuum? Thomas
RE: Conflicting Dependency Version Dilemna
Hi Craig, Craig McClanahan wrote on Wednesday, August 09, 2006 6:58 AM: A project[1] that I'm a participant in is a recent convert to Maven2 as a build environment. So far, there's a lot to like. But ... I think I've run into a limitation of the current design related to resolving conflicts in dependency versions. I'm looking for advice on what I can do other than wait for FINR (fixed in next rev) as the Better Builds book implies will be necessary :-). The starting point for my scenario is I wanted to explore whether Commons Logging 1.1 could successfully replace version 1.0.4 in a Shale-created webapp. To see all the gory details, you're probably best off downloading the sources and trying the build yourself. But the bottom line is that the only way I can convince a particular webapp build to use the new version of Commons Logging is to put the explicit dependence on 1.1 directly in the POM for that webapp. This is *not* what I want -- I'd much prefer to inherit the Commons Logging version dependency from the top-level shale POM ( org.apache.shale:shale-parent), or even from the intermediate layer I have as a basis for all the example webapps (org.apache.shale:shale-apps-parent). If you have a depednencyManagement section in your top-level POM and add the dep to your webapp without the version, it will work. Alas, this doesn't work. Any dependency such as MyFaces that declares a dependency on Commons Logging 1.0.4 seems to win, because it is closer on the nearness algorithm described in Section 3.6 of the Better Builds book. Point is, that you *have to* desclare the dep in the webapp, since the algorithm for the nearest version would take another version from one of your dependencies. It would seem to me that the simplest way to deal with this is that inherited dependencies (from a parent POM) should be considered as being at the same level of the dependency graph, just as if they had been explicitly declared. That would always allow a project to establish priority for shared dependencies itself, without having their builds destabilized because inheritance and dependence are both being treated as one step down the graph. Am I missing something? Is there some way to accomplish what I want (with M2 2.0.4) in the mean time, without explicitly declaring this dependency in the leaf node artifact POMs? Vote for it: http://jira.codehaus.org/browse/MNG-1577 - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicting Dependency Version Dilemna
On 8/8/06, Jörg Schaible [EMAIL PROTECTED] wrote: Hi Craig, Hello Jörg Craig McClanahan wrote on Wednesday, August 09, 2006 6:58 AM: A project[1] that I'm a participant in is a recent convert to Maven2 as a build environment. So far, there's a lot to like. But ... I think I've run into a limitation of the current design related to resolving conflicts in dependency versions. I'm looking for advice on what I can do other than wait for FINR (fixed in next rev) as the Better Builds book implies will be necessary :-). The starting point for my scenario is I wanted to explore whether Commons Logging 1.1 could successfully replace version 1.0.4 in a Shale-created webapp. To see all the gory details, you're probably best off downloading the sources and trying the build yourself. But the bottom line is that the only way I can convince a particular webapp build to use the new version of Commons Logging is to put the explicit dependence on 1.1 directly in the POM for that webapp. This is *not* what I want -- I'd much prefer to inherit the Commons Logging version dependency from the top-level shale POM ( org.apache.shale:shale-parent), or even from the intermediate layer I have as a basis for all the example webapps (org.apache.shale:shale-apps-parent). If you have a depednencyManagement section in your top-level POM and add the dep to your webapp without the version, it will work. Agreed ... but the requirement to explicitly do this in every single webapp is not what I want. The whole point of my apps inheriting a parent POM is to get rid of this sort of administrivia. Alas, this doesn't work. Any dependency such as MyFaces that declares a dependency on Commons Logging 1.0.4 seems to win, because it is closer on the nearness algorithm described in Section 3.6 of the Better Builds book. Point is, that you *have to* desclare the dep in the webapp, since the algorithm for the nearest version would take another version from one of your dependencies. Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so? It would seem to me that the simplest way to deal with this is that inherited dependencies (from a parent POM) should be considered as being at the same level of the dependency graph, just as if they had been explicitly declared. That would always allow a project to establish priority for shared dependencies itself, without having their builds destabilized because inheritance and dependence are both being treated as one step down the graph. Am I missing something? Is there some way to accomplish what I want (with M2 2.0.4) in the mean time, without explicitly declaring this dependency in the leaf node artifact POMs? Vote for it: http://jira.codehaus.org/browse/MNG-1577 Done. - Jörg Craig
Re: Conflicting Dependency Version Dilemna
On 8/8/06, Craig McClanahan [EMAIL PROTECTED] wrote: Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so? I should have been more clear. It is not that transitive dependencies are bad ... it's that I believe inherited dependencies (including version dependencies described by dependencyManagement sections should *always* override transitive dependencies on the same artifact. Alternatively, it would be reasonable to allow an override of whatever the default behavior is for advanced cases ... but requiring me to define version overrides in leaf nodes, simply because my inheritance hierarchy is deeper than my dependence hierarchy, encourages bad build architecture design behavior -- and isn't part of the point of Maven to eliminate that kind of idiocy? :-) Craig
RE: Conflicting Dependency Version Dilemna
Hi Craig, Craig McClanahan wrote on Wednesday, August 09, 2006 8:46 AM: On 8/8/06, Craig McClanahan [EMAIL PROTECTED] wrote: Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so? I should have been more clear. It is not that transitive dependencies are bad ... it's that I believe inherited dependencies (including version dependencies described by dependencyManagement sections should *always* override transitive dependencies on the same artifact. This is also my PoV, struggling with the same problems. While the current algorithm works for simple jars, it fails badly for all modules gathering the transitive dependencies: - webapps - ears - all jars with the classpath in the manifest (esp. true for EJBs) Building an ear with two EJBs I have to add a dep for any of the EJBs as well as for the EAR. Otherwise the manifest of the two EJBs might reference the same artifact in different versions and the EAR will contain a third one - leaving me with a complete broken EAR (not to mension that M2 will screw up the classspaths in the manifests for snapshot deps anyway using a multi-module build - at least this one is fixed in 2.0.5: MEJB-18). Alternatively, it would be reasonable to allow an override of whatever the default behavior is for advanced cases ... but requiring me to define version overrides in leaf nodes, simply because my inheritance hierarchy is deeper than my dependence hierarchy, encourages bad build architecture design behavior -- and isn't part of the point of Maven to eliminate that kind of idiocy? :-) I wished MNG-1577 would not have been postponed from version to version ... feel the same about the idiocy part ... - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum on Tomcat?
Thanks Emmanuel. I think that's a great thing as that will not force infrastructure decisions on the user. Thomas On 8/9/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: It will be possible in 1.1 because it will be a webapp. Emmanuel Thomas Van de Velde a écrit : Hi, Is it possible to run Continuum on Tomcat? Right now Continuum does not support HTTPS, which obviously is a no-go in an enterprise deployment over the Internet. Luntbuild e.g. gives me the flexibility to deploy on any app server that I'd like. I use mod_jk with Luntbuild. Can I do the same with Continuum? Thomas
RE: Automating install:install-file
I would disagree that this is somehow harder than what you're talking about. You are correct, it is at least equally hard. However I have made some progress though with the deploy plugin. It seems there is some duplication of effort between deploy:deploy-file and install:install-file. Also the former is more robust and has a richer configuration, so it was good advice to use it. The docos for wagon are pitifully bad (possibly because of a bug in the site generation), but I managed to piece it together. The short story is: if you use urlfile://path-to-my-local-repo/url in the configuration for deploy-file it works pretty much the same as install-file. This is fine by me, and I can switch to ftp or scp if I ever need to (and can find some decent documentation). One last question: how do I switch off the default behaviour of mvn deploy? I want to only run the deploy:deploy-file goal in the deploy phase, and not try to deploy my empty pom with no artifacts (which I am using to configure the deploy-file). Is there a packagingnone/packaging or something in the distributionManagement section of the pom I can use? And aren't you going to want an internal repo at some point anyway? Maybe, but that doesn't mean it's going to be easy to get control of ftp or shared filesystem permissions. I only wanted to be able to test the deployment before going through the pain of setting up an internal repo. Although I'm sure the install plugin could be modified to not have the read-only params Actually it already has been modified, but not yet published (see earlier post). Presumably the deploy plugin never had this restriction. -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a5721358 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xdoclet- mvn2 dilemma when generating sources
hi all, i m currently using xdoclet for generating sources for my EJBs.. problem is, my project is a Multi-Project. its structure is as follows MyProject | EJB1 | EJB2 i m generating sources for both EJB1 project and EJB2 project issue is that one of the beans in EJB2 has to have a reference to one of the beans of EJB1. for example, in EJB1 i have a bean named 'Contact', and in EJB2 one of the ejbs has a reference to my 'Contact' bean when generating sources in EJB2, XDoclete raises the following error [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: Unexpected error No such EJB defined: Contact [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant tasks at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:559) 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: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.MojoExecutionException: Error executing ant tasks at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( AbstractAntMojo.java:77) at org.codehaus.mojo.xdoclet.XDocletMojo.execute(XDocletMojo.java:102) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) ... 16 more Caused by: Unexpected error at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:118) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( AbstractAntMojo.java:71) ... 19 more Caused by: XDoclet failed. at xdoclet.DocletTask.start(DocletTask.java:471) at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:105) ... 23 more Caused by: xdoclet.XDocletException: No such EJB defined: Contact at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.findEjb( EnvEjbRefTagsHandler.java:392) at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.doGenerate( EnvEjbRefTagsHandler.java:312) at xdoclet.modules.ejb.env.EnvTagsHandler.forTagsInternal( EnvTagsHandler.java:531) at xdoclet.modules.ejb.env.EnvTagsHandler.forTags(EnvTagsHandler.java :451) at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.forAllEjbRefs( EnvEjbRefTagsHandler.java:79) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:641) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:540) at xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java :965) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java :932) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:472) at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:348) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:742) at xdoclet.tagshandler.MergeTagsHandler.generateUsingMergedFile( MergeTagsHandler.java:297) at xdoclet.tagshandler.MergeTagsHandler.merge(MergeTagsHandler.java:120) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
Re: xdoclet- mvn2 dilemma when generating sources / solved
hi all, sorry, myfault.. shouldnt have bothered the list but done some research on my own instead. Found a JIRA, solution is to use @ejb:ejb-external-ref sorry for bothering regards marco On 8/9/06, Marco Mistroni [EMAIL PROTECTED] wrote: hi all, i m currently using xdoclet for generating sources for my EJBs.. problem is, my project is a Multi-Project. its structure is as follows MyProject | EJB1 | EJB2 i m generating sources for both EJB1 project and EJB2 project issue is that one of the beans in EJB2 has to have a reference to one of the beans of EJB1. for example, in EJB1 i have a bean named 'Contact', and in EJB2 one of the ejbs has a reference to my 'Contact' bean when generating sources in EJB2, XDoclete raises the following error [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: Unexpected error No such EJB defined: Contact [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException : Error executing ant tasks at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:559) 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: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.MojoExecutionException : Error executing ant tasks at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( AbstractAntMojo.java:77) at org.codehaus.mojo.xdoclet.XDocletMojo.execute(XDocletMojo.java:102) at org.apache.maven.plugin.DefaultPluginManager.executeMojo ( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) ... 16 more Caused by: Unexpected error at xjavadoc.ant.XJavadocTask.execute (XJavadocTask.java:118) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java :275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( AbstractAntMojo.java:71) ... 19 more Caused by: XDoclet failed. at xdoclet.DocletTask.start(DocletTask.java:471) at xjavadoc.ant.XJavadocTask.execute (XJavadocTask.java:105) ... 23 more Caused by: xdoclet.XDocletException: No such EJB defined: Contact at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.findEjb( EnvEjbRefTagsHandler.java:392) at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.doGenerate ( EnvEjbRefTagsHandler.java:312) at xdoclet.modules.ejb.env.EnvTagsHandler.forTagsInternal( EnvTagsHandler.java:531) at xdoclet.modules.ejb.env.EnvTagsHandler.forTags(EnvTagsHandler.java :451) at xdoclet.modules.ejb.env.EnvEjbRefTagsHandler.forAllEjbRefs ( EnvEjbRefTagsHandler.java:79) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:585) at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:641) at xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java :540) at xdoclet.template.TemplateEngine.invokeBlockMethod ( TemplateEngine.java:965) at xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java :932) at xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:472) at xdoclet.template.TemplateEngine.generate (TemplateEngine.java:348) at xdoclet.XDocletTagSupport.generate(XDocletTagSupport.java:742) at xdoclet.tagshandler.MergeTagsHandler.generateUsingMergedFile(
RE: cargo deploy jboss datasource-ds.xml file?
Hi James, You should post to the cargo lists. You'll probably get more answers there. If you post there please be sure to tell us if you're really talking about an oracle-ds.xml file or some jboss ds file. Thanks -Vincent -Original Message- From: James Richards [mailto:[EMAIL PROTECTED] Sent: mercredi 9 août 2006 00:46 To: users@maven.apache.org Subject: cargo deploy jboss datasource-ds.xml file? Hello all, I'm using the Cargo plugin to deploy to a JBoss 4.x instance: plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId configuration container containerIdjboss4x/containerId !-- JBOSS log -- output${project.build.directory}/jboss4x.log/output !-- CARGO log -- log${project.build.directory}/cargo.log/log zipUrlInstaller urlhttp://umn.dl.sourceforge.net/sourceforge/jboss/jboss- 4.0.4.GA.zip/url installDir${installDir}/installDir /zipUrlInstaller /container /configura I have an oracle-ds.xml file which I would like to be deployed so that the datasources are configured prior to my web application starting. I tried installing the file directly into the ${installDir}/server/default/deploy directory as well as the ${installDir}/server\default\deploy\jbossweb- tomcat55.sar directories but neither seem to pick up the file. The problem is that cargo is deploying to the target directory. Is there any way to tell cargo to include oracle-ds.xml to the ${build.output.directory}\jboss4x\deploy directory so that it will deploy the datasources? Thanks again for your time, James ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cargo-plugin 0.3-SNAPSHOT problem?
Hi Michael, Please post to the cargo lists. When you post there please be sure to post your effective pom (mvn help:effective-pom). Also you shouldn't have both start and deploy goals as start does static deployment. Check the online docs. Let's continue this discussion on the cargo list. Thanks -Vincent -Original Message- From: Michael Mekaail [mailto:[EMAIL PROTECTED] Sent: mercredi 9 août 2006 04:49 To: users@maven.apache.org Subject: Cargo-plugin 0.3-SNAPSHOT problem? Hey, I'm trying to get the Cargo plugin working with Maven 2. My first problem was that the ping was timing out after 2000 (20 sec) which was too short. But this problem is fixed by using Cargo version 0.3-SNAPSHOTand using the tag pingTimeout24/pingTimeout. However my problem now is that when I do intregration-test I have the goals in this order: cargo:start cargo:deploy cargo:start Again??!?! Here is the code that I have in my POM plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId version0.3-SNAPSHOT/version configuration waitfalse/wait container containerIdtomcat5x/containerId zipUrlInstaller urlhttp://www.apache.org/dist/jakarta/tomcat-5/v5.0.30/bin/jakarta- tomcat-5.0.30.zip/url installDir${installDir}/installDir /zipUrlInstaller timeout12/timeout outputoutput.log/output logcargo-log.log/log /container configuration home${project.build.directory}/tomcat5x/container/home properties cargo.servlet.port9087/cargo.servlet.port /properties /configuration /configuration executions execution idstart-container/id phasepre-integration-test/phase goals goalstart/goal goaldeploy/goal /goals configuration deployer deployables deployable groupIdcom.company.project/groupId artifactIdproject/artifactId typewar/type location../project/target/project-1.0.war/location pingURLhttp://localhost:9087/project-1.0/pingURL pingTimeout24/pingTimeout /deployable /deployables /deployer /configuration /execution execution idstop-container/id phasepost-integration-test/phase goals goalstop/goal /goals /execution /executions /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PMD report plugin fails the build
How can I configure the PMD plugin not to fail the build when generating the report? I tried passing the parameter failOnViolation with value false but it's ignored. And I dont want to configure this plugin in the build section, it should be called only when is site is generated. The classes that fail this report were automatically generated. Thx, Ciprian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD report plugin fails the build
Add the pmd plugin to your reporting section instead of your build section, and it shouldn't breal the build anymore (but still generate the report). Denis. Ciprian Duma wrote: How can I configure the PMD plugin not to fail the build when generating the report? I tried passing the parameter failOnViolation with value false but it's ignored. And I dont want to configure this plugin in the build section, it should be called only when is site is generated. The classes that fail this report were automatically generated. Thx, Ciprian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
invocation of external commands
Hi All, I just wonder if there is any plugins for me to execute some external commands, at least some java applications, during my compilation process? Currently I am using the Ant Run plugin and do those things using ant tasks to execute those commands, is it the only way or there are some other plugins serving such purpose? Thanks a lot. Best regards Adrian Shum This email is confidential. If you are not the intended recipient, please delete it from your system and notify the sender immediately. Any unauthorized use, disclosure, dissemination or copying of this email is prohibited. Tai Fook Securities Group, its group companies and their content providers (Parties) shall not be responsible for the accuracy or completeness of this email or its attachment, if any, which could contain virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late. The Parites do not accept liability for any damage caused by this email.
Need help regarding the Changelog plugin.
Hi all I am trying to get changelog for my project and the mvn site command generates empty changelog output. Following is the scm section of my pom.xml scm connectionscm:perforce:PRIVACYHIDDEN@fish:1678://EJB/ejb-dev/MavenCo deline/connection /scm and the plugin section I have plugin groupIdorg.codehaus.mojo/groupId artifactIdchangelog-maven-plugin/artifactId reportSets reportSet idPerofrce report/id configuration typerange/type range30/range /configuration reports reportchangelog/report reportfile-activity/report reportdev-activity/report /reports /reportSet /reportSets /plugin I get following error when I generate site using maven site command. [ERROR] There are test failures. [INFO] [site:site] [WARNING] Error loading report org.apache.maven.changelog.ChangeLogReport - Abst ractMethodError: canGenerateReport() [WARNING] Error loading report org.apache.maven.changelog.FileActivityReport - A bstractMethodError: canGenerateReport() [WARNING] Error loading report org.apache.maven.changes.ChangesMojo - AbstractMe thodError: canGenerateReport() [WARNING] Error loading report org.apache.maven.jira.JiraMojo - AbstractMethodEr ror: canGenerateReport() Is it something related to setting maven.changelog.factory to org.apache.maven.perforcelib.PerforceChangeLogFactory. But where do you set this value if this is what i need. Any help would be really really appreciated. Thanks a lot Abhijit
Customize site Project Reports menu labels
Hi! I need to customize the labels of the Project Reports menu entries in the Maven2 site. How can I do? Thanks, Lorenzo -- View this message in context: http://www.nabble.com/Customize-site-Project-Reports-menu-labels-tf2077958.html#a5723454 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD report plugin fails the build
It's in the reports section. But I think the plugin calls first pdm-check and I can't tell it not to fail (or it ignores the option). On 8/9/06, Denis Cabasson [EMAIL PROTECTED] wrote: Add the pmd plugin to your reporting section instead of your build section, and it shouldn't breal the build anymore (but still generate the report). Denis. Ciprian Duma wrote: How can I configure the PMD plugin not to fail the build when generating the report? I tried passing the parameter failOnViolation with value false but it's ignored. And I dont want to configure this plugin in the build section, it should be called only when is site is generated. The classes that fail this report were automatically generated. Thx, Ciprian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 Sent from the Maven - Users forum 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: PMD report plugin fails the build
Have you run with -U to get the latest version of the plugin? This used to happen to me, but stopped recently after running mvn site -U -Stephen On 8/9/06, Ciprian Duma [EMAIL PROTECTED] wrote: It's in the reports section. But I think the plugin calls first pdm-check and I can't tell it not to fail (or it ignores the option). On 8/9/06, Denis Cabasson [EMAIL PROTECTED] wrote: Add the pmd plugin to your reporting section instead of your build section, and it shouldn't breal the build anymore (but still generate the report). Denis. Ciprian Duma wrote: How can I configure the PMD plugin not to fail the build when generating the report? I tried passing the parameter failOnViolation with value false but it's ignored. And I dont want to configure this plugin in the build section, it should be called only when is site is generated. The classes that fail this report were automatically generated. Thx, Ciprian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 Sent from the Maven - Users forum 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : invocation of external commands
Have a look : http://mojo.codehaus.org/exec-maven-plugin/ -Message d'origine- De : Adrian Shum [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 août 2006 12:32 À : users@maven.apache.org Objet : invocation of external commands Hi All, I just wonder if there is any plugins for me to execute some external commands, at least some java applications, during my compilation process? Currently I am using the Ant Run plugin and do those things using ant tasks to execute those commands, is it the only way or there are some other plugins serving such purpose? Thanks a lot. Best regards Adrian Shum This email is confidential. If you are not the intended recipient, please delete it from your system and notify the sender immediately. Any unauthorized use, disclosure, dissemination or copying of this email is prohibited. Tai Fook Securities Group, its group companies and their content providers (Parties) shall not be responsible for the accuracy or completeness of this email or its attachment, if any, which could contain virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late. The Parites do not accept liability for any damage caused by this email. This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customize site Project Reports menu labels
It is not possible yet. See: http://jira.codehaus.org/browse/MPIR-35 Cheers, Vincent 2006/8/9, lore [EMAIL PROTECTED]: Hi! I need to customize the labels of the Project Reports menu entries in the Maven2 site. How can I do? Thanks, Lorenzo -- View this message in context: http://www.nabble.com/Customize-site-Project-Reports-menu-labels-tf2077958.html#a5723454 Sent from the Maven - Users forum 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]
Flat directory structure and Eclipse
Hi, The flat directory is recommended for J2EE projects: myProject / pom.xml | |-- EAR / pom.xml | |-- EJB / pom.xml | |-- WEB / pom.xml This structure is not entirely flat because of the root myProject / pom.xml. It is not clear to me how this structure fits into Eclipse workspace. Do you have the myProject / pom.xml in the root folder of Eclipse workspace and each EAR/EJB/WEB as eclipse projects? It seems to me that this shold work better with Eclipse: EclipseWorkspace | |-- myProject.EAR / pom.xml | |-- myProject.EJB / pom.xml | |-- myProject.WEB / pom.xml | |-- myProject.main / pom.xml (this is the parent POM) Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Flat directory structure and Eclipse
Hi Jan, running the maven eclipse plugin, you won't get any project file for the top level (myProject / pom.xml). Also, I recomment using a workspace location different from where you keep your source code (using eclipse's import existing project feature) HTHAB, Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:05:26: Hi, The flat directory is recommended for J2EE projects: myProject / pom.xml | |-- EAR / pom.xml | |-- EJB / pom.xml | |-- WEB / pom.xml This structure is not entirely flat because of the root myProject / pom.xml. It is not clear to me how this structure fits into Eclipse workspace. Do you have the myProject / pom.xml in the root folder of Eclipse workspace and each EAR/EJB/WEB as eclipse projects? It seems to me that this shold work better with Eclipse: EclipseWorkspace | |-- myProject.EAR / pom.xml | |-- myProject.EJB / pom.xml | |-- myProject.WEB / pom.xml | |-- myProject.main / pom.xml (this is the parent POM) Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Flat directory structure and Eclipse
Thanks Stefan, I don't use the eclipse plugin, but it makes no difference. So, if I understand you well, you have the structure recomended by Maven doc outside of Eclipse workspace and use Eclipse links to each fo the EAR/EJB/WAR subfolders? Are there any troubles with this setup? Jan Hi Jan, running the maven eclipse plugin, you won't get any project file for the top level (myProject / pom.xml). Also, I recomment using a workspace location different from where you keep your source code (using eclipse's import existing project feature) HTHAB, Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:05:26: Hi, The flat directory is recommended for J2EE projects: myProject / pom.xml | |-- EAR / pom.xml | |-- EJB / pom.xml | |-- WEB / pom.xml This structure is not entirely flat because of the root myProject / pom.xml. It is not clear to me how this structure fits into Eclipse workspace. Do you have the myProject / pom.xml in the root folder of Eclipse workspace and each EAR/EJB/WEB as eclipse projects? It seems to me that this shold work better with Eclipse: EclipseWorkspace | |-- myProject.EAR / pom.xml | |-- myProject.EJB / pom.xml | |-- myProject.WEB / pom.xml | |-- myProject.main / pom.xml (this is the parent POM) Thanks, Jan - 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 1.1-beta3 maven-artifact-plugin 1.8
Hi, I just upgraded from maven 1.0.2 to 1.1-beta3, and got the maven-artifact-plugin 1.8 along with it. But Now I can't deploy any artifacts because scp refuses my host key, while scpexe just doesn't do anything at all, but doesn't complain... So, I've reverted back to 1.0.2 for now, but are there any plans for fixing these problems? (I'm running maven on JDK 1.5.0_07, on Fedora core 5). Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Flat directory structure and Eclipse
The eclipse plugin is included by default try running mvn eclipse:eclipse. It will generate the project/classpath files for you automatically. You can of course set up the projects manually, but it's a lot of work. I typically use the follwing setup: c:\projects c:\projects\myproject\ c:\projects\myproject\EAR c:\projects\myproject\WAR c:\projects\myproject\EJB c:\projects\myproject_workspace The advantage of this is that you don't mess up your project folder with workspace settings. HTH Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:24:38: Thanks Stefan, I don't use the eclipse plugin, but it makes no difference. So, if I understand you well, you have the structure recomended by Maven doc outside of Eclipse workspace and use Eclipse links to each fo the EAR/EJB/WAR subfolders? Are there any troubles with this setup? Jan Hi Jan, running the maven eclipse plugin, you won't get any project file for the top level (myProject / pom.xml). Also, I recomment using a workspace location different from where you keep your source code (using eclipse's import existing project feature) HTHAB, Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:05:26: Hi, The flat directory is recommended for J2EE projects: myProject / pom.xml | |-- EAR / pom.xml | |-- EJB / pom.xml | |-- WEB / pom.xml This structure is not entirely flat because of the root myProject / pom.xml. It is not clear to me how this structure fits into Eclipse workspace. Do you have the myProject / pom.xml in the root folder of Eclipse workspace and each EAR/EJB/WEB as eclipse projects? It seems to me that this shold work better with Eclipse: EclipseWorkspace | |-- myProject.EAR / pom.xml | |-- myProject.EJB / pom.xml | |-- myProject.WEB / pom.xml | |-- myProject.main / pom.xml (this is the parent POM) Thanks, Jan - 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: Maven 1.1-beta3 maven-artifact-plugin 1.8
Hi Steve, Yes, this is an issue I encountered as well. I have found that the 6/30 1.1-beta3-SNAPSHOT does not have this problem, but every release since then does. See 20060630/ here: http://people.apache.org/~aheritier/maven/1.X/snapshots/ We are researching the problem to find a fix. In the meantime, I suggest the 6/30 snapshot if you would like to use 1.1. It is very solid and the current one we use for our production work (we've used nearly every one of those snapshots all along as they were published). -Original Message- From: Steve Molloy [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 7:24 AM To: users@maven.apache.org Subject: Maven 1.1-beta3 maven-artifact-plugin 1.8 Hi, I just upgraded from maven 1.0.2 to 1.1-beta3, and got the maven-artifact-plugin 1.8 along with it. But Now I can't deploy any artifacts because scp refuses my host key, while scpexe just doesn't do anything at all, but doesn't complain... So, I've reverted back to 1.0.2 for now, but are there any plans for fixing these problems? (I'm running maven on JDK 1.5.0_07, on Fedora core 5). Thanks, Steve - 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: Re: Flat directory structure and Eclipse
Thanks Stefan for your time. Stefan Magnus Landrø [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] The eclipse plugin is included by default try running mvn eclipse:eclipse. It will generate the project/classpath files for you automatically. You can of course set up the projects manually, but it's a lot of work. I typically use the follwing setup: c:\projects c:\projects\myproject\ c:\projects\myproject\EAR c:\projects\myproject\WAR c:\projects\myproject\EJB c:\projects\myproject_workspace The advantage of this is that you don't mess up your project folder with workspace settings. HTH Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:24:38: Thanks Stefan, I don't use the eclipse plugin, but it makes no difference. So, if I understand you well, you have the structure recomended by Maven doc outside of Eclipse workspace and use Eclipse links to each fo the EAR/EJB/WAR subfolders? Are there any troubles with this setup? Jan Hi Jan, running the maven eclipse plugin, you won't get any project file for the top level (myProject / pom.xml). Also, I recomment using a workspace location different from where you keep your source code (using eclipse's import existing project feature) HTHAB, Stefan news [EMAIL PROTECTED] skrev 09.08.2006 14:05:26: Hi, The flat directory is recommended for J2EE projects: myProject / pom.xml | |-- EAR / pom.xml | |-- EJB / pom.xml | |-- WEB / pom.xml This structure is not entirely flat because of the root myProject / pom.xml. It is not clear to me how this structure fits into Eclipse workspace. Do you have the myProject / pom.xml in the root folder of Eclipse workspace and each EAR/EJB/WEB as eclipse projects? It seems to me that this shold work better with Eclipse: EclipseWorkspace | |-- myProject.EAR / pom.xml | |-- myProject.EJB / pom.xml | |-- myProject.WEB / pom.xml | |-- myProject.main / pom.xml (this is the parent POM) Thanks, Jan - 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: Maven 1.1-beta3 maven-artifact-plugin 1.8
Thanks, I guess I'll stick with 1.0.2 until the next release, hoping this issue will be fixed. Is there any ETA set for the next 1.1 release yet? Steve On Wed, 2006-09-08 at 08:23 -0500, Jeff Jensen wrote: Hi Steve, Yes, this is an issue I encountered as well. I have found that the 6/30 1.1-beta3-SNAPSHOT does not have this problem, but every release since then does. See 20060630/ here: http://people.apache.org/~aheritier/maven/1.X/snapshots/ We are researching the problem to find a fix. In the meantime, I suggest the 6/30 snapshot if you would like to use 1.1. It is very solid and the current one we use for our production work (we've used nearly every one of those snapshots all along as they were published). -Original Message- From: Steve Molloy [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 7:24 AM To: users@maven.apache.org Subject: Maven 1.1-beta3 maven-artifact-plugin 1.8 Hi, I just upgraded from maven 1.0.2 to 1.1-beta3, and got the maven-artifact-plugin 1.8 along with it. But Now I can't deploy any artifacts because scp refuses my host key, while scpexe just doesn't do anything at all, but doesn't complain... So, I've reverted back to 1.0.2 for now, but are there any plans for fixing these problems? (I'm running maven on JDK 1.5.0_07, on Fedora core 5). Thanks, Steve - 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: Maven 1.1-beta3 maven-artifact-plugin 1.8
Steve, Even if you don't use this snapshot, can you test it to tell us if this one works also for you. We are searching what we changed since this snapshot and the official beta 3 to fix it in the RC1. We are trying to produce the RC1 at the end of the month. If the returns about it are good, we'll release the final 1.1 in september (probably in mid-september). It's why we need to have as many feedback as possible about this beta 3 to have less Release Candidates. Cheers Arnaud On 8/9/06, Steve Molloy [EMAIL PROTECTED] wrote: Thanks, I guess I'll stick with 1.0.2 until the next release, hoping this issue will be fixed. Is there any ETA set for the next 1.1 release yet? Steve On Wed, 2006-09-08 at 08:23 -0500, Jeff Jensen wrote: Hi Steve, Yes, this is an issue I encountered as well. I have found that the 6/30 1.1-beta3-SNAPSHOT does not have this problem, but every release since then does. See 20060630/ here: http://people.apache.org/~aheritier/maven/1.X/snapshots/ We are researching the problem to find a fix. In the meantime, I suggest the 6/30 snapshot if you would like to use 1.1. It is very solid and the current one we use for our production work (we've used nearly every one of those snapshots all along as they were published). -Original Message- From: Steve Molloy [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 7:24 AM To: users@maven.apache.org Subject: Maven 1.1-beta3 maven-artifact-plugin 1.8 Hi, I just upgraded from maven 1.0.2 to 1.1-beta3, and got the maven-artifact-plugin 1.8 along with it. But Now I can't deploy any artifacts because scp refuses my host key, while scpexe just doesn't do anything at all, but doesn't complain... So, I've reverted back to 1.0.2 for now, but are there any plans for fixing these problems? (I'm running maven on JDK 1.5.0_07, on Fedora core 5). Thanks, Steve - 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: Automating install:install-file
One last question: how do I switch off the default behaviour of mvn deploy? I want to only run the deploy:deploy-file goal in the deploy phase, and not try to deploy my empty pom with no artifacts (which I am using to configure the deploy-file). Hmmm. It sounds to me like you're using the deploy:deploy-file goal incorrectly. You don't need a pom (empty or otherwise) to run this goal. Perhaps that's some of the confusion. If it helps, here's the bat file I use (incidentally, this file is in version control, although the jar files it references aren't): set LIBDIR=c:/home/devel/java/lib set REPOINFO=-Durl=scp://repo-server/repo-release -DrepositoryId=repo-release call mvn deploy:deploy-file %REPOINFO% -DgroupId=com.sybase -DartifactId=jconnect -Dversion=5.5.EBF11656 -Dpackaging=jar -DgeneratePom=true -Dfile=%LIBDIR%/jConnect5.5.EBF11656.jar call mvn deploy:deploy-file %REPOINFO% -DgroupId=javax.media -DartifactId=jai-core -Dversion=1.1.2 -Dpackaging=jar -DgeneratePom=true -Dfile=%LIBDIR%/jai-1.1.2 This is run in an directory containing only this file - no pom, no nothing. If you don't want to do with the repository, you could write this same script with the install:install-file goal: set LIBDIR=c:/home/devel/java/lib set REPOINFO=-Durl=scp://repo-server/repo-release -DrepositoryId=repo-release call mvn install:install-file -DgroupId=com.sybase -DartifactId=jconnect -Dversion=5.5.EBF11656 -Dpackaging=jar -DgeneratePom=true -Dfile=%LIBDIR%/jConnect5.5.EBF11656.jar call mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core -Dversion=1.1.2 -Dpackaging=jar -DgeneratePom=true -Dfile=%LIBDIR%/jai-1.1.2/jai_core.jar -Original Message- From: Dave Syer [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 3:53 AM To: users@maven.apache.org Subject: RE: Automating install:install-file I would disagree that this is somehow harder than what you're talking about. You are correct, it is at least equally hard. However I have made some progress though with the deploy plugin. It seems there is some duplication of effort between deploy:deploy-file and install:install-file. Also the former is more robust and has a richer configuration, so it was good advice to use it. The docos for wagon are pitifully bad (possibly because of a bug in the site generation), but I managed to piece it together. The short story is: if you use urlfile://path-to-my-local-repo/url in the configuration for deploy-file it works pretty much the same as install-file. This is fine by me, and I can switch to ftp or scp if I ever need to (and can find some decent documentation). One last question: how do I switch off the default behaviour of mvn deploy? I want to only run the deploy:deploy-file goal in the deploy phase, and not try to deploy my empty pom with no artifacts (which I am using to configure the deploy-file). Is there a packagingnone/packaging or something in the distributionManagement section of the pom I can use? And aren't you going to want an internal repo at some point anyway? Maybe, but that doesn't mean it's going to be easy to get control of ftp or shared filesystem permissions. I only wanted to be able to test the deployment before going through the pain of setting up an internal repo. Although I'm sure the install plugin could be modified to not have the read-only params Actually it already has been modified, but not yet published (see earlier post). Presumably the deploy plugin never had this restriction. -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a 5721358 Sent from the Maven - Users forum 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: Maven 1.1-beta3 maven-artifact-plugin 1.8
Sure, just tried it, but the build failed with a ClassNotFoundException for AbstractSshWagon... One thing weird is that the tar and the md5 don't have the same dates (July 18th vs August 1st...). It was in 20060630 right? (used http://people.apache.org/~aheritier/maven/1.X/snapshots/20060630/maven-1.1-beta-3-SNAPSHOT.tar.bz2 ). Steve Stacktrace: BUILD FAILED File.. file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly Element... artifact:artifact-deploy Line.. 103 Column 9 org/apache/maven/wagon/providers/ssh/AbstractSshWagon org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [jar:deploy] -- file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly:103:9: artifact:artifact-deploy org/apache/maven/wagon/providers/ssh/AbstractSshWagon at org.apache.maven.werkz.Goal.fire(Goal.java:663) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:535) at org.apache.maven.cli.App.main(App.java:1318) 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:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: file:/home/smolloy/.maven/cache/maven-artifact-plugin-1.8/plugin.jelly:103:9: artifact:artifact-deploy org/apache/maven/wagon/providers/ssh/AbstractSshWagon at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:193) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78) at org.apache.maven.jelly.tags.werkz.MavenGoalTag $MavenGoalAction.performAction(MavenGoalTag.java:109) at org.apache.maven.werkz.Goal.fire(Goal.java:656) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:694) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:535) at org.apache.maven.cli.App.main(App.java:1318) 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:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.NoClassDefFoundError: org/apache/maven/wagon/providers/ssh/AbstractSshWagon at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:316) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:155) 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:585) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180) ... 19 more Root cause java.lang.NoClassDefFoundError: org/apache/maven/wagon/providers/ssh/AbstractSshWagon at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:316) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Problem with changelog report
Hi! I'm trying to generate the changelog report but I've some problems. First I tryed to use the plugin in the last released version: groupIdorg.codehaus.mojo/groupId artifactIdchangelog-maven-plugin/artifactId but there were problems in the urls pointing to the files in the Subversion repository. Many of our repositories have repeated words in their url (ex.: http://svn_url/.../prod_name/prod_name/...) and those repetition went lost (ex.: http://svn_url/.../prod_name/...). Then I've modified the pom to use the snapshot of the plugin refactored: groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId version2.0-SNAPSHOT/version and now the timestamps are wrong and look like this: 0020-05-27 00:00:00 Thanks a lot in advance! Lorenzo P.S.: Sorry for my English -- View this message in context: http://www.nabble.com/Problem-with-changelog-report-tf2079095.html#a5726723 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SOLVED] RE: [M2] Intercept the workings of EJB Plugins (was RE: [m2] ant run plugin )
-Original Message- From: Pilgrim, Peter ==== [install] The EJB plugin now executes agains and installs the EJB-JAR into the M2 repository. Job done. I will document this craziness on my blog http://jroller.com/page/peter_pilgrim asap because this was too damn crazy. Job done! http://jroller.com/page/peter_pilgrim?entry=battling_with_maven_2_integr ating ==== -- Peter Pilgrim UBS Investment Bank, PTS Portal / IT FIRC OPS LDN, 100 Liverpool Street, London EC2M 2RH, United Kingdom :: Java EE / E-Commerce / Enterprise Integration / Development :: Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT][ANN] JAVAWUG BOF XXI / 5th Sept 2006 @ 18:30 / SkillsMatter
Hi All I would like announce the twentieth first birds-of-a-feather (BOF 21) of the Java Web Users Group. The event will take place on Tuesday 5th September 2006, starting from 18:30 at Skills Matter Limited 1 Sekforde Street LONDON EC1R 0BE Map: mapPhone: 020 7107 2620 Fax: 020 7107 2621 Email: [EMAIL PROTECTED] Web: http://skillsmatter.com/javawug The feature speakers: Max Antoni, Java Web Freelancer Software Developer How to write object oriented AJAX applications. Max Antoni is working at UBS as a freelancer. He is working on the front-end Java web development of an portal enterprise application. (Actually Max and I work together for the same project at 100 Liverpool Street. Max is actually heading back to Germany at the end of September, so I am grateful that he accepted my invitation to talk to usw) In the last couple of years Max have collected some best practices and he has lot of experience about how object orientation works in languages derived from ECMA Script, like todays Javascript implementations. He started working with browser based applications in 2004 and soon came across the idea of writing his own Java based application server, suiting the needs of applications. This idea brought EvaServer to life (See http://www.maxantoni.de website is in German) and now he is working towards to release a version 1.0 by the end of this year. During the two 1/2 years of developing Max gained valuable insight about browser internals and how best to represent client states on the server side [similar but counterpoint to DWR], which will also be part of the discussion/presentation. Afterwards members can retire to the nearby the ``Crown'' pub/restaurant for more in depth discussion dinner, food and drink ... If you would like to attend, please REGISTER so that you can be added to the SECURITY DETAIL ( http://skillsmatter.com/javawug ). Join the http://groups.google.com/group/javawug JAVAWUG at Google Groups and ``Send an Email to the list you are attending'' http://jroller.com/page/javawug The venue has graciously been organised by Wendy Devolder of Skillsmatter. We all appreciate this generous gift. Thank you for your time. -- Peter Pilgrim Your Organiser / Founder ( JAVAWUG http://developers.sun.com/jugs/display/europe/gbr/london ) ( ( ( ( ( ( )\( ( )\)\))( ' ( )\ ) )_)( )\ )_)( ((_)()\ ))\(()/( ((_)\ _ )\((_)((_)\ _ )\_(())\_)()_ ((_)/(_))_ _ | (_)_\(_) \ / /(_)_\(_) \((_)/ / | | (_)) __| | || |/ _ \ \ V / / _ \ \ \/\/ /| |_| | | (_ | \__//_/ \_\ \_/ /_/ \_\ \_/\_/ \___/ \___| = Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compiler plugin: trying to set compileSourceRoots
Hi, I am trying to specify multiple source locations for the compiler-plugin (goal: test-compile). How do I accomplish that? I have tried to set the compileSourceRoots in the configuration of the compiler plugin: configuration compileSourceRootssrc/test/main;src/test2/main/compileSourceRoots /configuration But I always get an error: Cannot override read-only parameter: compileSourceRoots Is there a different way by which I can set the property project.testCompileSourceRoots separately? Thanks, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Automating install:install-file
It sounds to me like you're using the deploy:deploy-file goal incorrectly. I'm trying to use it differently, not incorrectly. I don't want to write a DOS .bat script to do this because it won't work on a UN*X system. The idea is that I should be able to run mvn deploy from my project root (or the parent project if there are multiple dependencies), and have the jar deployed. I'd be happy with mvn install and have the jar installed locally, but that was an even less productive avenue. Although, actually now I am more keen to get a proper pom in my repo, so deploy looks like the way to go because I can add a pom with the pomFile parameter. This is all very frustrating, I must say. I have spent close to three days now trying to build an existing project that was already building fine with ant. I still believe there is some mileage in it, bbut I'm running out of patience. -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a5726808 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Conflicting Dependency Version Dilemna
Any comment from the maven devs? This problem seems to be affecting more and more people. Ruel Loehr JBoss QA -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 1:57 AM To: Maven Users List Subject: RE: Conflicting Dependency Version Dilemna Hi Craig, Craig McClanahan wrote on Wednesday, August 09, 2006 8:46 AM: On 8/8/06, Craig McClanahan [EMAIL PROTECTED] wrote: Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so? I should have been more clear. It is not that transitive dependencies are bad ... it's that I believe inherited dependencies (including version dependencies described by dependencyManagement sections should *always* override transitive dependencies on the same artifact. This is also my PoV, struggling with the same problems. While the current algorithm works for simple jars, it fails badly for all modules gathering the transitive dependencies: - webapps - ears - all jars with the classpath in the manifest (esp. true for EJBs) Building an ear with two EJBs I have to add a dep for any of the EJBs as well as for the EAR. Otherwise the manifest of the two EJBs might reference the same artifact in different versions and the EAR will contain a third one - leaving me with a complete broken EAR (not to mension that M2 will screw up the classspaths in the manifests for snapshot deps anyway using a multi-module build - at least this one is fixed in 2.0.5: MEJB-18). Alternatively, it would be reasonable to allow an override of whatever the default behavior is for advanced cases ... but requiring me to define version overrides in leaf nodes, simply because my inheritance hierarchy is deeper than my dependence hierarchy, encourages bad build architecture design behavior -- and isn't part of the point of Maven to eliminate that kind of idiocy? :-) I wished MNG-1577 would not have been postponed from version to version ... feel the same about the idiocy part ... - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.10.8/414 - Release Date: 8/9/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.10.8/414 - Release Date: 8/9/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Proximity Demo Site
Hi all, Proximity demo site started to work on address: http://proximity.abstracthorizon.org:12000/px-webapp This site will show the current edge development In case site is down, I beg for your patience, it will mean that the site is updating. NOTE: To prevent using this site as repository, an AccessManager on repo level is PREVENTING JAR download, all other kind of files is downloadable. This has no blocking effect in functionality. Thanx and Have fun! ~t~
Re: Compiler plugin: trying to set compileSourceRoots
Alexander Hars wrote: Hi, I am trying to specify multiple source locations for the compiler-plugin (goal: test-compile). How do I accomplish that? I have tried to set the compileSourceRoots in the configuration of the compiler plugin: configuration compileSourceRootssrc/test/main;src/test2/main/compileSourceRoots /configuration But I always get an error: Cannot override read-only parameter: compileSourceRoots Is there a different way by which I can set the property project.testCompileSourceRoots separately? Thanks, Alexander - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] You can't do that in the compiler plugin. You have to do you own custom maven plugin if you want to add sources to the compile phase. Sample mojo (kudos to emmanuel Venisse): public class AddSourcesDirectoryMojo extends AbstractMojo { /** * @parameter */ private List sources; /** * @parameter expression=${project} * * @required */ private MavenProject project; public void execute() throws MojoExecutionException { if ( project != null sources != null ) { for ( Iterator i = sources.iterator(); i.hasNext(); ) { String sourceDirectory = (String) i.next(); project.addCompileSourceRoot( sourceDirectory ); } } } } Denis. -- View this message in context: http://www.nabble.com/Compiler-plugin%3A-trying-to-set-compileSourceRoots-tf2079114.html#a5727585 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: castor doclet plugin
mmistroni wrote: hi all, with maven1 i have been usign castordoclet (as part of xdoclet) to generate castor mapping files for my classes... it looks like it is not in m2 xdoclet plugin.. am i wrong or is there a different solution for generating castor mapping files? thanks in advance and regards marco There is a castor plugin in the mojo project: http://mojo.codehaus.org/castor-maven-plugin/ You should have a look at it. Denis. -- View this message in context: http://www.nabble.com/castor-doclet-plugin-tf2079368.html#a5727738 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Proximity Demo Site
Thank you for continuing to make and improve such a fine product! We are happy with the quality of work, clarity of docs, and ease of installation and use. Quoting Tamás Cservenák [EMAIL PROTECTED]: Hi all, Proximity demo site started to work on address: http://proximity.abstracthorizon.org:12000/px-webapp This site will show the current edge development In case site is down, I beg for your patience, it will mean that the site is updating. NOTE: To prevent using this site as repository, an AccessManager on repo level is PREVENTING JAR download, all other kind of files is downloadable. This has no blocking effect in functionality. Thanx and Have fun! ~t~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build happening twice
Hi All I have multimodule project with maven everthing seems to be working fine,but one thing I will create ear from my project, then i created a profile which is activated by a property like, so when that property(deployto.wlserver)is set to true it will deploy the created ear into weblogic server. so when i ran mvn -e clean deploy it goes thru the deploy lifecycle twice.. i see the reason its coz my profile was activated at deploy phase and i'm running the goal deploy which is found in weblogic-maven-plugin Is there a way to make it work only once the deploy goal, i tried with weblogic:deploy at goal section but it was throwing error as [INFO] 'weblogic:deploy' was specified in an execution, but not found in the plugin profile idDEPLOY-TO-WEBLOGIC/id activation property namedeployto.wlserver/name valuetrue/value /property /activation build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdweblogic-maven-plugin/artifactId version2.8.0-SNAPSHOT/version executions execution idDeploy-To-Weblogic/id goals goaldeploy/goal /goals phasedeploy/phase configuration adminServerProtocol${wl.admin.protocol}/adminServerProtocol adminServerHostName${wl.admin.host}/adminServerHostName adminServerPort${wl.admin.port}/adminServerPort userId${wl.admin.userid}/userId password${wl.admin.passwd}/password targetNames${apps.target.servers}/targetNames !-- name${deploying.apps.name}/name objectPath${apps.loc.inserver}/objectPath staging${copy.fileto.targets}/staging -- upload${upload.artifactto.adminServer}/upload remote${running.from.adminServer}/remote verbose${turn.on.verbose}/verbose debug${turn.on.debug}/debug /configuration /execution /executions /plugin /plugins /build /profile Please help Thanks, Raghurajan Gurunathan - This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
RE: Compiler plugin: trying to set compileSourceRoots
| -Original Message- | From: Denis Cabasson [mailto:[EMAIL PROTECTED] | Sent: Wednesday, August 09, 2006 11:07 AM | To: users@maven.apache.org | Subject: Re: Compiler plugin: trying to set compileSourceRoots | | Alexander Hars wrote: | | Hi, | | I am trying to specify multiple source locations for the | compiler-plugin | (goal: test-compile). How do I accomplish that? | | I have tried to set the compileSourceRoots in the | configuration of the | compiler plugin: | configuration | | compileSourceRootssrc/test/main;src/test2/main/compileSourceRoots | /configuration | | But I always get an error: |Cannot override read-only parameter: compileSourceRoots | | Is there a different way by which I can set the property |project.testCompileSourceRoots | separately? | | Thanks, | | Alexander | | | You can't do that in the compiler plugin. | You have to do you own custom maven plugin if you want to add | sources to the | compile phase. | | Sample mojo (kudos to emmanuel Venisse): | public class AddSourcesDirectoryMojo | extends AbstractMojo | { | /** | * @parameter | */ | private List sources; | | /** | * @parameter expression=${project} | * | * @required | */ | private MavenProject project; | | public void execute() | throws MojoExecutionException | { | if ( project != null sources != null ) | { | for ( Iterator i = sources.iterator(); i.hasNext(); ) | { | String sourceDirectory = (String) i.next(); | project.addCompileSourceRoot( sourceDirectory ); | } | } | } | } | | Denis. | -- Or you can use the build-helper plugin - http://mojo.codehaus.org/build-helper-maven-plugin/howto.html -Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compiler plugin: trying to set compileSourceRoots
Ian Springer wrote: | -Original Message- | From: Denis Cabasson [mailto:[EMAIL PROTECTED] | Sent: Wednesday, August 09, 2006 11:07 AM | To: users@maven.apache.org | Subject: Re: Compiler plugin: trying to set compileSourceRoots | | Alexander Hars wrote: | | Hi, | | I am trying to specify multiple source locations for the | compiler-plugin | (goal: test-compile). How do I accomplish that? | | I have tried to set the compileSourceRoots in the | configuration of the | compiler plugin: | configuration | | compileSourceRootssrc/test/main;src/test2/main/compileSourceRoots | /configuration | | But I always get an error: |Cannot override read-only parameter: compileSourceRoots | | Is there a different way by which I can set the property |project.testCompileSourceRoots | separately? | | Thanks, | | Alexander | | | You can't do that in the compiler plugin. | You have to do you own custom maven plugin if you want to add | sources to the | compile phase. | | Sample mojo (kudos to emmanuel Venisse): | public class AddSourcesDirectoryMojo | extends AbstractMojo | { | /** | * @parameter | */ | private List sources; | | /** | * @parameter expression=${project} | * | * @required | */ | private MavenProject project; | | public void execute() | throws MojoExecutionException | { | if ( project != null sources != null ) | { | for ( Iterator i = sources.iterator(); i.hasNext(); ) | { | String sourceDirectory = (String) i.next(); | project.addCompileSourceRoot( sourceDirectory ); | } | } | } | } | | Denis. | -- Or you can use the build-helper plugin - http://mojo.codehaus.org/build-helper-maven-plugin/howto.html -Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I didn't know of a plugin doing this! Seems nice enough and should do exactly the job. Of course, an existing plugin is always prefered to a home made one. Denis. -- View this message in context: http://www.nabble.com/Compiler-plugin%3A-trying-to-set-compileSourceRoots-tf2079114.html#a5728267 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Packaging all modules as Jar
I'm trying to package all of the compiled code of several modules into 1 jar but I can't seem to figure out the assembly plugin. I tried including this in my parent pom: build .. plugin artifactIdmaven-assembly-plugin/artifactId version2.0-beta-1/version /plugin /build And executing this command line that I found on the maven site somewhere: mvn assembly:assembly -DprojectModulesOnly=true -DdescriptorId=bin However it tells me I need a descriptorId, which I specified. Plus bin isn't really what I want, I just want a jar file of my code only, not any config files or dependent jars. As a side note, is there any task to run to update all maven plugins? When working with this and my failed attempt at aggregating javadocs for my project (looks like I am sticking with ant for that part) I had to specify a version so maven could download the latest plugin. I guess somehow it was using a 1.0 plugin even though I thought the latest plugins would be in the distribution I downloaded.
Re: castor doclet plugin
Hello Denis, thx for the reply. that is doing the other way around.. from xml to bean.. i'll have anyway a look regards marco On 8/9/06, Denis Cabasson [EMAIL PROTECTED] wrote: mmistroni wrote: hi all, with maven1 i have been usign castordoclet (as part of xdoclet) to generate castor mapping files for my classes... it looks like it is not in m2 xdoclet plugin.. am i wrong or is there a different solution for generating castor mapping files? thanks in advance and regards marco There is a castor plugin in the mojo project: http://mojo.codehaus.org/castor-maven-plugin/ You should have a look at it. Denis. -- View this message in context: http://www.nabble.com/castor-doclet-plugin-tf2079368.html#a5727738 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Missing name and url in artifacts from central
I guess I can't be the first person to moan about this, but there are a *lot* of artifacts in the central repo that have no name or url information in their pom (nevermind description, or license). Examples include some big names - this is from my dependencies report: Unnamed - fop:fop:jar:0.20.5 Unnamed - ant:ant:jar:1.6.5 Unnamed - tapestry:tapestry:jar:4.0.1 ... the list goes on (37 in my project). Am I just getting them from the wrong repository? I don't think so, but let me know if anyone has any success getting better poms for some of these projects. Is there some way for me to provide the missing information locally without interfering with the way the repo works? I thought maybe if I put the name, url etc. explicitly in my dependency elements it might work, but it doesn't. -- View this message in context: http://www.nabble.com/Missing-name-and-url-in-artifacts-from-central-tf2079674.html#a5728717 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Conflicting Dependency Version Dilemna
We have come up with a pattern that we feel works pretty well to work around this. We split our modules into standard jars and j2ee type archives. The standard jars declare their own deps as normal. The j2ee jars all share a parent which overrides all dependency versions so all the wars/ears are guaranteed to have the same manifest.mf and ear lib/*.jar contents. When we release, standard jars are released one at a time. The j2ee jars are all released at the same time (using one big recursive release). This way we update the parent with the latest versions of all the standard jars and then all the j2ee jars will pick it up. Craig, the other thing to remember is that version ranges are key here also. Your transitive dependency should not be specifying 1.0.4, it should say [1.0,) so that versions are not pushed to its dependents (i.e. your project) like you are seeing. Unfortunately M2 has several bugs wrt version ranges but this is important to solidify for the 2.1 release IMO. The other thing needed is to document a development process for building J2EE artifacts. M2 works pretty well for OSS people writing jars and fat wars but is a pain to deal with for application (EAR) authors trying to package more than one j2ee module. Jörg Schaible [EMAIL PROTECTED] wrote on 08/09/2006 01:56:58 AM: Hi Craig, Craig McClanahan wrote on Wednesday, August 09, 2006 8:46 AM: On 8/8/06, Craig McClanahan [EMAIL PROTECTED] wrote: Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so? I should have been more clear. It is not that transitive dependencies are bad ... it's that I believe inherited dependencies (including version dependencies described by dependencyManagement sections should *always* override transitive dependencies on the same artifact. This is also my PoV, struggling with the same problems. While the current algorithm works for simple jars, it fails badly for all modules gathering the transitive dependencies: - webapps - ears - all jars with the classpath in the manifest (esp. true for EJBs) Building an ear with two EJBs I have to add a dep for any of the EJBs as well as for the EAR. Otherwise the manifest of the two EJBs might reference the same artifact in different versions and the EAR will contain a third one - leaving me with a complete broken EAR (not to mension that M2 will screw up the classspaths in the manifests for snapshot deps anyway using a multi-module build - at least this one is fixed in 2.0.5: MEJB-18). Alternatively, it would be reasonable to allow an override of whatever the default behavior is for advanced cases ... but requiring me to define version overrides in leaf nodes, simply because my inheritance hierarchy is deeper than my dependence hierarchy, encourages bad build architecture design behavior -- and isn't part of the point of Maven to eliminate that kind of idiocy? :-) I wished MNG-1577 would not have been postponed from version to version ... feel the same about the idiocy part ... - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release Plugin and Parent POM Issues
We have a master POM file that contains common version information, common plug-in settings, and common repository settings. There are also two different profiles in this master POM. One profile is used for development builds. The other profile is used for release builds. All of our build POMs reference this master POM as their parent. Problems: 1. When I run mvn help:active-profiles or mvn release:prepare or mvn release:perform on one of our child POMs, it does not seem to correctly display the correct profile in the master POM. This causes my release not to build correctly because it chooses the wrong profile in the master POM for the build. 2. When I perform a release build. I first run a release on the master POM file. Then I have to manual edit each of my child POM with the correct version number of the parent POM before I do the release and after I complete the release. Is there any way to either request a feature for the release plugin or manually edit the release plugin myself so that the release plugin will prompt for the release version and next development version of the parent POM and have the release plugin write those versions into the child POM file automatically?
Does continuum supports UCM Clease case?
Thanks, Raghurajan Gurunathan - This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Re: Missing name and url in artifacts from central
The best method would be to contact the various projects and request that they update their poms in their own code repository. If you file these as JIRA MEV issues and someone updates the poms, the changes will be lost in the next version released by the project -- ie someone applies a fix to fop 0.20.5 but then fop releases 0.20.6 which of course is missing url and name. Best to fix these problems at the source. Wayne On 8/9/06, Dave Syer [EMAIL PROTECTED] wrote: I guess I can't be the first person to moan about this, but there are a *lot* of artifacts in the central repo that have no name or url information in their pom (nevermind description, or license). Examples include some big names - this is from my dependencies report: Unnamed - fop:fop:jar:0.20.5 Unnamed - ant:ant:jar:1.6.5 Unnamed - tapestry:tapestry:jar:4.0.1 ... the list goes on (37 in my project). Am I just getting them from the wrong repository? I don't think so, but let me know if anyone has any success getting better poms for some of these projects. Is there some way for me to provide the missing information locally without interfering with the way the repo works? I thought maybe if I put the name, url etc. explicitly in my dependency elements it might work, but it doesn't. -- View this message in context: http://www.nabble.com/Missing-name-and-url-in-artifacts-from-central-tf2079674.html#a5728717 Sent from the Maven - Users forum 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: Converting AppFuse to a Maven 2 Project
I started working on the Maven 2 conversion last night. I'm currently using Carlos's nested recommendation. Here's a screenshot of the current structure: http://raibledesigns.com/repository/images/appfuse2-structure.png Using this structure, I get errors stating that the data and web parent projects should have a packaging type of pom. However, I want these projects to create their own JAR artifacts. Should these be moved into common projects instead of having them in the root of data and web? Thanks, Matt -- View this message in context: http://www.nabble.com/Converting-AppFuse-to-a-Maven-2-Project-tf1964609.html#a5729055 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Conflicting Dependency Version Dilemna
Hi Mike, Mike Perham wrote on Wednesday, August 09, 2006 6:21 PM: We have come up with a pattern that we feel works pretty well to work around this. We split our modules into standard jars and j2ee type archives. The standard jars declare their own deps as normal. The j2ee jars all share a parent which overrides all dependency versions so all the wars/ears are guaranteed to have the same manifest.mf and ear lib/*.jar contents. When we release, standard jars are released one at a time. The j2ee jars are all released at the same time (using one big recursive release). This way we update the parent with the latest versions of all the standard jars and then all the j2ee jars will pick it up. Unfortunately this pattern does only help if you build a single EAR. For multiple EARs (we have so) and a lot of EJBs (not exclusivly referenced), you cannot define the dependencies in a common parent, since then you woud end up with all depednencies of all EJBs in every EAR. So you use a dependencyManagement (we do) and you're left with the already described problem - you cannot force transitive dependencies toi the version defined in the management. [snip] - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Automating install:install-file
I'm trying to use it differently, not incorrectly. The deploy:deploy-file goal is clearly documented as being run from the command line. No mention is made of using it within a POM. See http://maven.apache.org/plugins/maven-deploy-plugin/usage.html. Unfortunately, there's no usage page for the install plugin, but I suspect it would be similar. The idea is that I should be able to run mvn deploy from my project root (or the parent project if there are multiple dependencies), and have the jar deployed. This is different than what I'd understood your original question to be. I thought you wanted to run mvn deploy and have your third-party jars deployed, each with their own POM, but not deploy the POM of the current project. This isn't what the deploy phase is for. From http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl e.html, copies the final package to the remote repository for sharing with other developers and projects meaning the package (artifact) of a project, not these 3rd party jars (which are artifacts of other projects). If you're trying to deploy the artifact of a project, then mvn deploy is the way to go, but this obviously requires a repository to deploy to. I don't want to write a DOS .bat script to do this because it won't work on a UN*X system. So then write a shell script :) Although, actually now I am more keen to get a proper pom in my repo, so deploy looks like the way to go because I can add a pom with the pomFile parameter. You can specify a pom with either install:install-file or deploy:deploy-file. Check their mojo documentation. The difference is that with install:install-file, generatePom defaults to false whereas with deploy:deploy-file, it defaults to true. -Original Message- From: Dave Syer [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 10:26 AM To: users@maven.apache.org Subject: RE: Automating install:install-file It sounds to me like you're using the deploy:deploy-file goal incorrectly. I'm trying to use it differently, not incorrectly. I don't want to write a DOS .bat script to do this because it won't work on a UN*X system. The idea is that I should be able to run mvn deploy from my project root (or the parent project if there are multiple dependencies), and have the jar deployed. I'd be happy with mvn install and have the jar installed locally, but that was an even less productive avenue. Although, actually now I am more keen to get a proper pom in my repo, so deploy looks like the way to go because I can add a pom with the pomFile parameter. This is all very frustrating, I must say. I have spent close to three days now trying to build an existing project that was already building fine with ant. I still believe there is some mileage in it, bbut I'm running out of patience. -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a 5726808 Sent from the Maven - Users forum 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 : setting log4j log level for tests
Try to add it in src/test/resources -Message d'origine- De : Christofer Jennings [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 août 2006 19:00 À : Maven Users List Objet : setting log4j log level for tests newbee Q: I'm using maven2 and am having trouble figuring out how log4j settings work. Is there an example pom showing how to set up log4j for tests? I have a log4j.properties in src/main/java and another src/test/java. My pom is based on the web-app archetype but I added the java test directories. Sorry if this is old news, but I'm also having trouble finding clear documentation for what I want. ??? ,chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Automating install:install-file
From ... copies the final package to the remote repository for sharing with other developers and projects meaning the package (artifact) of a project That's fine. I would *love* to be able to make the artifact of a project an existing jar file. Instead I have to struggle with tricking maven into thinking that it has built a jar file when it hasn't. All I want is these 3rd party jars in a repo somewhere with a proper pom... You can specify a pom with either install:install-file or deploy:deploy-file. Check their mojo documentation. The difference is that with install:install-file, generatePom defaults to false whereas with deploy:deploy-file, it defaults to true. ...which means, not the pom that is autogenerated by deploy-file or install-file - deploy-file allows me to specify a concrete pom. I don't feel like I'm getting any further forward here. Maven is not the only game in town, and there will always be jar files that other people produce. It just isn't very easy to use them in a controlled environment, within the maven framework. OK I can write scripts, but the point is that I want maven to do my build, and not to have to rely on other tools (that might not be available according to the platform). -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a5730267 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: module dependencies?
Sascha Sadat-Guscheh wrote: hi all.. i'm not sure if this is the correct mailinglist for asking this questions, but i'm pretty desperate so i'll give it a try. This question is best suited for the users list. i'm using the maven-idea-plugin in the version 2.0-beta-1. my config looks like this: The first thing to do would be to update to version 2.0, which was released a couple of months ago. Try that and if the problem is still there get back to us on the users list. plugin artifactIdmaven-idea-plugin/artifactId version2.0-beta-1/version configuration jdkName1.5/jdkName downloadJavadocstrue/downloadJavadocs downloadSourcestrue/downloadSources dependenciesAsLibrariesfalse/dependenciesAsLibraries /configuration /plugin we have a project with about 30 submodules. when i run the maven idea:idea it generates the project files but i doesn't set the module dependencies .. it always uses the built .jar files as dependency (library dep.) so if i go to my idea settings/project, choose a module and look at the dependencies tab none of the checkboxes are checked. it is really annoying, because for each change in a module i have to run a mvn install to make this change visible in other modules. the goal mvn eclipse:eclipse works fine btw any ideas/suggestions? kind regards, sascha -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting AppFuse to a Maven 2 Project
yes, you need to move them to common On 8/9/06, mraible [EMAIL PROTECTED] wrote: I started working on the Maven 2 conversion last night. I'm currently using Carlos's nested recommendation. Here's a screenshot of the current structure: http://raibledesigns.com/repository/images/appfuse2-structure.png Using this structure, I get errors stating that the data and web parent projects should have a packaging type of pom. However, I want these projects to create their own JAR artifacts. Should these be moved into common projects instead of having them in the root of data and web? Thanks, Matt -- View this message in context: http://www.nabble.com/Converting-AppFuse-to-a-Maven-2-Project-tf1964609.html#a5729055 Sent from the Maven - Users forum 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: Conflicting Dependency Version Dilemna
Not exactly. We have a single parent POM per ear and don't share war/ejbs between ears, yes. But you can still do what you want with a dependencyManagement section in the parent to centralize the version numbers and just have each ear POM pull in its required ejbs. Or am I missing something? mike Jörg Schaible [EMAIL PROTECTED] wrote on 08/09/2006 11:46:10 AM: Unfortunately this pattern does only help if you build a single EAR. For multiple EARs (we have so) and a lot of EJBs (not exclusivly referenced), you cannot define the dependencies in a common parent, since then you woud end up with all depednencies of all EJBs in every EAR. So you use a dependencyManagement (we do) and you're left with the already described problem - you cannot force transitive dependencies toi the version defined in the management.
Re: Problem with changelog report
lore wrote: Hi! I'm trying to generate the changelog report but I've some problems. First I tryed to use the plugin in the last released version: groupIdorg.codehaus.mojo/groupId artifactIdchangelog-maven-plugin/artifactId but there were problems in the urls pointing to the files in the Subversion repository. Many of our repositories have repeated words in their url (ex.: http://svn_url/.../prod_name/prod_name/...) and those repetition went lost (ex.: http://svn_url/.../prod_name/...). Then I've modified the pom to use the snapshot of the plugin refactored: groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId version2.0-SNAPSHOT/version and now the timestamps are wrong and look like this: 0020-05-27 00:00:00 Do the timestamps make any sense at all to you? I'm trying to find out if it's a formating issue or an SCM issue. Was the file with the above timestamp changed on the 27 of May in, well some year? Thanks a lot in advance! Lorenzo P.S.: Sorry for my English -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicting Dependency Version Dilemna
On 8/9/06, Mike Perham [EMAIL PROTECTED] wrote: Not exactly. We have a single parent POM per ear and don't share war/ejbs between ears, yes. But you can still do what you want with a dependencyManagement section in the parent to centralize the version numbers and just have each ear POM pull in its required ejbs. Or am I missing something? Defining dependencyManagement in the parent does not seem to cover all the cases for me. A simplified scenario goes like this: * Parent POM declares a version for artifact A * Child POM declares (or inherits) a dependency on artifact B * Dependency B declares a dependency on artifact A with an explicit, but different, version number. It seems that the two dependencies on artifact A are at the same level (in the terms of the book's section on this) and therefore the behavior is undefined. Indeed, it seems to work for most of the dependencies with version conflicts, but not all of them ... and it is completely unclear to me at this point why the cases are different. mike Craig Jörg Schaible [EMAIL PROTECTED] wrote on 08/09/2006 11:46:10 AM: Unfortunately this pattern does only help if you build a single EAR. For multiple EARs (we have so) and a lot of EJBs (not exclusivly referenced), you cannot define the dependencies in a common parent, since then you woud end up with all depednencies of all EJBs in every EAR. So you use a dependencyManagement (we do) and you're left with the already described problem - you cannot force transitive dependencies toi the version defined in the management.
Retrieving root directory in maven 2
Hi there, How can I retrieve the root directory in maven 2 from the pom? ${basedir} was the closest I found, but then I get the path from where maven is running, so this seems to be the module path. I would guess its a simple ${..} I can use.. BTW: Where can I find an overview over all the references I can use from a pom? Thanks in advance, Rohnny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Retrieving root directory in maven 2
${project.parent} parent project ${project.parent.basedir} for the parent basedir For all expressions, checks appendix A from Better builds with maven ebook. Cheers, Vincent 2006/8/9, Rohnny Moland [EMAIL PROTECTED]: Hi there, How can I retrieve the root directory in maven 2 from the pom? ${basedir} was the closest I found, but then I get the path from where maven is running, so this seems to be the module path. I would guess its a simple ${..} I can use.. BTW: Where can I find an overview over all the references I can use from a pom? Thanks in advance, Rohnny - 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: Automating install:install-file
I would *love* to be able to make the artifact of a project an existing jar file. But you have to understand that this isn't what the jar or pom packaging types do. Instead I have to struggle with tricking maven into thinking that it has built a jar file when it hasn't. You just have you use deploy:deploy-file as documented. No trickery involved. ...which means, not the pom that is autogenerated by deploy-file or install-file - deploy-file allows me to specify a concrete pom. install:install-file has a pomFile property just like deploy:deploy-file OK I can write scripts, but the point is that I want maven to do my build As far as I can tell, nothing in this thread is related to build. Deploying a 3rdparty jar should be a one-time operation. The only reason you'd need to redeploy is when a new version of the 3rdparty jar was released or you lost your repository and didn't have backups. Look - I don't want to beat a dead horse here, but I really don't think you should give up just because of this issue. As I said above, at least in my world, deploying a 3rdparty jar is a one-time operation. You're obviously free to do whatever you want, but this seems like way to minor a point to block your efforts. -Original Message- From: Dave Syer [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 1:26 PM To: users@maven.apache.org Subject: RE: Automating install:install-file From ... copies the final package to the remote repository for sharing with other developers and projects meaning the package (artifact) of a project That's fine. I would *love* to be able to make the artifact of a project an existing jar file. Instead I have to struggle with tricking maven into thinking that it has built a jar file when it hasn't. All I want is these 3rd party jars in a repo somewhere with a proper pom... You can specify a pom with either install:install-file or deploy:deploy-file. Check their mojo documentation. The difference is that with install:install-file, generatePom defaults to false whereas with deploy:deploy-file, it defaults to true. ...which means, not the pom that is autogenerated by deploy-file or install-file - deploy-file allows me to specify a concrete pom. I don't feel like I'm getting any further forward here. Maven is not the only game in town, and there will always be jar files that other people produce. It just isn't very easy to use them in a controlled environment, within the maven framework. OK I can write scripts, but the point is that I want maven to do my build, and not to have to rely on other tools (that might not be available according to the platform). -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a 5730267 Sent from the Maven - Users forum 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]
Native artifacts (.dll, .so etc)
Can maven handle native artifacts? I have a java project with an associated JNI DLL that I would like to have in the maven repository for generating assemblies. The real problem with native libraries is how to handle system dependencies. I have three versions on my JNI library, one each for windows, linux and macosx. Has anyone come up with a solution for these issues? Thanks Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Optional Goals Dependencies
I am trying to figure out a way to define optional goals and/or dependencies. Is there a way to do this? I am looking for something similar to the ability in ant to only do a certain task if a certain property is set. __ Douglas W. Ferguson EPSIIA - Another Fiserv Connection Development Office Phone: 512-329-0081 ext. 3309 Dial Toll Free: 800-415-5946 Mobile Phone: 512-293-7279 Fax: 512-329-0086 [EMAIL PROTECTED] www.epsiia.com http://www.epsiia.com/ __
RE: Optional Goals Dependencies
Then you probably want to become familiar with the wonderful world of profiles. http://maven.apache.org/guides/introduction/introduction-to-profiles.htm l Chris -Original Message- From: Douglas Ferguson [mailto:[EMAIL PROTECTED] Sent: Wednesday, 09 August, 2006 17:25 To: 'Maven Users List' Subject: Optional Goals Dependencies I am trying to figure out a way to define optional goals and/or dependencies. Is there a way to do this? I am looking for something similar to the ability in ant to only do a certain task if a certain property is set. __ Douglas W. Ferguson EPSIIA - Another Fiserv Connection Development Office Phone: 512-329-0081 ext. 3309 Dial Toll Free: 800-415-5946 Mobile Phone: 512-293-7279 Fax: 512-329-0086 [EMAIL PROTECTED] www.epsiia.com http://www.epsiia.com/ __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running a script/bat file - Post Build
Hi, I would like to execute a script or a bat file after the build. Does continuum has any way to execute this ?What is the best way ? regards --Prashanth __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: invocation of external commands
Have a look at http://mojo.codehaus.org/exec-maven-plugin/ Frederik -Original Message- From: Adrian Shum [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 3:32 AM To: users@maven.apache.org Subject: invocation of external commands Hi All, I just wonder if there is any plugins for me to execute some external commands, at least some java applications, during my compilation process? Currently I am using the Ant Run plugin and do those things using ant tasks to execute those commands, is it the only way or there are some other plugins serving such purpose? Thanks a lot. Best regards Adrian Shum This email is confidential. If you are not the intended recipient, please delete it from your system and notify the sender immediately. Any unauthorized use, disclosure, dissemination or copying of this email is prohibited. Tai Fook Securities Group, its group companies and their content providers (Parties) shall not be responsible for the accuracy or completeness of this email or its attachment, if any, which could contain virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late. The Parites do not accept liability for any damage caused by this email. _ Scanned on 09 Aug 2006 10:33:07 Scanned by Erado - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Native artifacts (.dll, .so etc)
It can, there is a native-maven-plugin on codehaus. It should work for most simple JNI projects. The various OS's though, I'm not sure. You specify the OS in the pom, and you'd need the various platform dependencies available as well as a cross-compiler for each if you wanted to do this build on one machine. How do you do it now? I imagine if you built it on the various systems, you could make a profile that would activate per-OS, and fill in the OS-specific stuff for the pom. On 8/9/06, Chris Audley [EMAIL PROTECTED] wrote: Can maven handle native artifacts? I have a java project with an associated JNI DLL that I would like to have in the maven repository for generating assemblies. The real problem with native libraries is how to handle system dependencies. I have three versions on my JNI library, one each for windows, linux and macosx. Has anyone come up with a solution for these issues? Thanks Chris - 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]
-javaagent in integartion tests
I am having trouble using instrumentation API with Surefire. The project pom can be found here - [1]. Essentially, no matter whether I start mvn with -javaagent in MAVEN_OPTS, or use fork with argLine, I am getting an exception (see below). When I start unit tests with a main method of a regular Java class, it works. Any insights? See error details below. Thanks Andrus [1] https://svn.apache.org/repos/asf/incubator/cayenne/sandbox/itest- unit1/pom.xml ERROR 1. With childDelegation=false (the agent is loaded but ClassLoader blows during the test: [INFO] Surefire report directory: /Users/andrus/work/jpa-itests/itest- unit1/target/surefire-reports *** CayenneAgent starting... --- T E S T S --- Running org.apache.cayenne.jpa.itest.entity.EntityClassTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.061 sec FAILURE! testFieldBasedPersistence (org.apache.cayenne.jpa.itest.entity.EntityClassTest) Time elapsed: 0.016 sec ERROR! java.lang.NoClassDefFoundError: javax/persistence/spi/ PersistenceProvider at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass (SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java: 268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java: 319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass (SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java: 268) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass (IsolatedClassLoader.java:100) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java: 319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.cayenne.jpa.itest.Unit1TestHelper.init (Unit1TestHelper.java:44) at org.apache.cayenne.jpa.itest.Unit1TestHelper.clinit (Unit1TestHelper.java:32) at org.apache.cayenne.jpa.itest.entity.EntityClassTest.testFieldBasedPersis tence(EntityClassTest.java:33) ERROR 2: Without child delegation (agent loaded, but no instrumentation is available to the tests): *** CayenneAgent starting... --- T E S T S --- Running org.apache.cayenne.jpa.itest.entity.EntityClassTest cayenne WARN [main 08-09 21:59:12] InstrumentingUnit: *** No instrumentation instance present. Check the -javaagent: option Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.554 sec FAILURE! testFieldBasedPersistence (org.apache.cayenne.jpa.itest.entity.EntityClassTest) Time elapsed: 0.512 sec ERROR! java.lang.IllegalArgumentException: entity must be Persistent at org.apache.cayenne.jpa.cspi.CjpaEntityManager.checkEntityType (CjpaEntityManager.java:116) at org.apache.cayenne.jpa.cspi.CjpaEntityManager.persistInternal (CjpaEntityManager.java:48) at org.apache.cayenne.jpa.JpaEntityManager.persist (JpaEntityManager.java:95) at org.apache.cayenne.jpa.itest.entity.EntityClassTest.testFieldBasedPersis tence(EntityClassTest.java:36) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicting Dependency Version Dilemna
Again, this is because dependency B is not using version ranges but rather forcing a specific version on its downstream dependents. If A requires a different version, it has to declare that dependency in order to override the transitive dependency version from B. There's nothing Maven can do when the POM data is incorrect. You need to exclude it or override it. [EMAIL PROTECTED] wrote on 08/09/2006 01:29:22 PM: Defining dependencyManagement in the parent does not seem to cover all the cases for me. A simplified scenario goes like this: * Parent POM declares a version for artifact A * Child POM declares (or inherits) a dependency on artifact B * Dependency B declares a dependency on artifact A with an explicit, but different, version number. It seems that the two dependencies on artifact A are at the same level (in the terms of the book's section on this) and therefore the behavior is undefined. Indeed, it seems to work for most of the dependencies with version conflicts, but not all of them ... and it is completely unclear to me at this point why the cases are different.
Re: Conflicting Dependency Version Dilemna
On 8/9/06, Mike Perham [EMAIL PROTECTED] wrote: Again, this is because dependency B is not using version ranges but rather forcing a specific version on its downstream dependents. Ah, but dependency B is a third party library ... and the entire transitive dependency tree for Shale (which is pretty small compared to lots of multi-project environments) has at least 100 such dependencies. Seems to me like evangelizing all those folks to set up proper version ranges in their POMs belongs to the Maven team, not to me whose just an (indirect) Joe User for all those packages :-). If A requires a different version, it has to declare that dependency in order to override the transitive dependency version from B. There's nothing Maven can do when the POM data is incorrect. You need to exclude it or override it. Yes, there is something Maven could do -- it could reflect the reality that most POMs don't actually do this, and provide developers a workaround that protects them from instabilities caused by the current rules. It could define the version conflict resolution rules such that dependencyManagement version declarations in *my* POMs (defined as the one for this project or the explictly declared parent tree) always win over version declarations that come from explicit or transitive dependencies. That way, I can declare in a single parent POM all my version dependency information for *all* my leaf node projects (webapps in my case, but the same principle applies to any environment where you are creating lots of individual artifacts that share a common set of dependencies) without having to tediously edit all of the leaf POMs individually. Craig
Re: Conflicting Dependency Version Dilemna
On 8/9/06, Mike Perham [EMAIL PROTECTED] wrote: Again, this is because dependency B is not using version ranges but rather forcing a specific version on its downstream dependents. Thinking about this a little further, there is a QE viewpoint that leads me to believe that declaring a specific version on a dependency is actually the right thing to do. Let's consider a concrete case: the Shale core library (org.apache.shale:shale-core) artifact depends on, among other things, Commons BeanUtils. In the POM for this module, I want to inherit from the parent POM (org.apache.shale:shale-parent) a dependence on a particular version of this library, so that I can update the dependencies of a bunch of other artifacts all at once when I've satisfied myself that it works. Currently, in the parent POM, the version (declared in a dependencyManagement section) of BeanUtils that is requested is, specifically, 1.7.0. This is essentially an assertion that I have tested my library against this specific version, and am satisfied that it works. If I understand your recommendation correctly, you would like me to declare my dependency on version [1.7.0,) instead (meaning version 1.7.0 or any later version). From a QE perspective, that is an untestable assertion -- there is no way to know that some future version of BeanUtils might introduce some incompatible change that makes *my* library no longer work. That is not acceptable to me as the supplier of a library, because it is *me* who is going to suffer the you *said* it would work bug reports. If an end user of my library wants to override my setting, they can (although making them do it in every leaf node is definitely a violation of the don't repeat yourself mantra that M2 seems to really like :-). But I want *my* POMs to advertise what *I* have tested, and not rely on all of my dependencies not to break me with future versions. I wouldn't even want to trust my own modules enough to use ranges like that :-). Craig
Re: Maven and Selenium?
The 2.x site has been published. Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 72 43 74 / www.capgemini.com Fax: + 33 4 93 21 02 95 Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice Join the Collaborative Business Experience Wim Deblauwe a écrit : I have no experience with other web test frameworks, but it looks nice looking at the quick start. The link to the 2.x site does not work currently, better fix this. regards, Wim 2006/8/2, Christophe DENEUX [EMAIL PROTECTED]: Hi Daniel, Some advantages of using jWebUnit to test a web application are: - easier test case writing, - faster test case running, - No graphic server is needed with the engine htmlunit, so the integration into a continuous integration system is easier (no browser is needed), - Soon, you will use an engine for Selenium to run your tests directly in your browser. jWebUnit home: http://jwebunit.sourceforge.net Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 72 43 74 / www.capgemini.com Fax: + 33 4 93 21 02 95 Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice Join the Collaborative Business Experience Daniel Serodio a écrit : Christophe DENEUX wrote: Hi , A snapshot repository is available at: http://maven.openqa.org/ Have you try jWebUnit (http://jwebunit.sourceforge.net/index.html) instead of Selenium for your functional tests? With jWebUnit, you can run your tests with different engines as htmlunit or Selenium (the Selenium engine is available trough SVN). You will use the htmlunit engine to execute your tests in a background mode (continuous integration) and the selenium engine in a visual mode. It's been a while since I looked at jWebUnit, and I'm currently using Selenium; what is the advantage of using jWebUnit as you describe instead of using Selenium directly? Do you have an URL with more info on the subject? TIA, Daniel Serodio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]