Scope question
Hello, I wondering if it is possible to change the scope of a dependency depending on the position in the tree of dependencies ? Here is a small example: An artifact A with a dependence on a z artifact defined with compile scope. If I use artifact A in a project B, I would like the dependency scope of z becomes runtime, in order to prevent the user to explicitly call classes from artifact z . Do you think it is possible to have this kind of behaviour ? Thanks in advance, Guillaume
Re: Scope question
Hi Guillaume, Guillaume CHAUVET wrote: Hello, I wondering if it is possible to change the scope of a dependency depending on the position in the tree of dependencies ? Here is a small example: An artifact A with a dependence on a z artifact defined with compile scope. If I use artifact A in a project B, I would like the dependency scope of z becomes runtime, in order to prevent the user to explicitly call classes from artifact z . Do you think it is possible to have this kind of behaviour ? Use a dependencyManagement section to define version and scope of runtime for z. If you share the section in a parent for A and B, then you can simply redeclare the scope in A to compile. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scope question
Should be possible to change through the dependencyManagement section. /Anders On Tue, Nov 5, 2013 at 10:47 AM, Guillaume CHAUVET guillaume.chau...@qualiformed.com wrote: Hello, I wondering if it is possible to change the scope of a dependency depending on the position in the tree of dependencies ? Here is a small example: An artifact A with a dependence on a z artifact defined with compile scope. If I use artifact A in a project B, I would like the dependency scope of z becomes runtime, in order to prevent the user to explicitly call classes from artifact z . Do you think it is possible to have this kind of behaviour ? Thanks in advance, Guillaume
Re: System-wide, read-only repository
When you decide on a solution, a write up of what you did would be helpful for the archives and anyone in the future that has the same needs as you. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to install the impl module for a api dependency in maven
I have a multi-module maven project structured in something like this: parent | |-presentation |+services ||-services-api ||-services-impl |+data-access ||-data-access-api ||-data-access-impl |-+connector ||-connector-api ||-connector-implA ||-connector-implB |-... The presentation module is packaged in a war and it depends only on the api modules. When i run the install goal the only dependencies that the war installs are the api modules. To choose wich impl modules to install in the presentation module i'm using profiles that add the dependency to the impl modules at build time depending on the profiles selected. From what i've been reading i don't think that this is correct usage for the maven profiles. What is the best way to tell maven to add the chosen impl to the presentation module? I would like to keep the dependency to only the api module but with the usage of profiles, if the profile is active, the dependency is there and no compilation errors will happen when i reference a class of the impl module... thanks -- Cumprimentos, João Pedro
RE: Scope question
Thank you for your quick answers, Use the dependencyManagement section seems a little bit cumbersome to implement, because it implies to define a parent POM for all libraries to which I would apply this retention classes mechanism. It's somewhat speculative on my part, but It could be very convenient to provide a new scope (or an option like optional) that allows Maven to change the scope of z dependency to runtime when the artifact A is included as dependency of project B. I think it would be an interesting feature. What do you think about this idea ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scope question
Introducing a new scope is not possible without breaking backwards compatibility. Thus, unlikely to happen in the near future. Your option right now is to use depMgmt. /Anders On Tue, Nov 5, 2013 at 12:15 PM, Guillaume CHAUVET guillaume.chau...@qualiformed.com wrote: Thank you for your quick answers, Use the dependencyManagement section seems a little bit cumbersome to implement, because it implies to define a parent POM for all libraries to which I would apply this retention classes mechanism. It's somewhat speculative on my part, but It could be very convenient to provide a new scope (or an option like optional) that allows Maven to change the scope of z dependency to runtime when the artifact A is included as dependency of project B. I think it would be an interesting feature. What do you think about this idea ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to install the impl module for a api dependency in maven
I don't fully understand what you want to accomplish, but, as you point out, profiles is not the right path. It almost never is. :-) What I think you want to do is to have compile scope dependencies to your api artifacts from the impl projects. And then in the war project (presentation module) you declare deps to the artifacts you need (you have a dependency to), which should include impl artifacts as they are needed. In your war project I would assume that you have some kind of compile time dependency to your impl code, and if so you need to declare that. If you don't have a compile time dependency, then you have a runtime dependency and then specify that (scope 'runtime'). If you want different flavors of your webapp, then you create one war project per flavor. /Anders On Tue, Nov 5, 2013 at 11:50 AM, João Pedro pedro.j...@gmail.com wrote: I have a multi-module maven project structured in something like this: parent | |-presentation |+services ||-services-api ||-services-impl |+data-access ||-data-access-api ||-data-access-impl |-+connector ||-connector-api ||-connector-implA ||-connector-implB |-... The presentation module is packaged in a war and it depends only on the api modules. When i run the install goal the only dependencies that the war installs are the api modules. To choose wich impl modules to install in the presentation module i'm using profiles that add the dependency to the impl modules at build time depending on the profiles selected. From what i've been reading i don't think that this is correct usage for the maven profiles. What is the best way to tell maven to add the chosen impl to the presentation module? I would like to keep the dependency to only the api module but with the usage of profiles, if the profile is active, the dependency is there and no compilation errors will happen when i reference a class of the impl module... thanks -- Cumprimentos, João Pedro
RE: Scope question
Hi Guillaume, Guillaume CHAUVET wrote: Thank you for your quick answers, Use the dependencyManagement section seems a little bit cumbersome to implement, because it implies to define a parent POM for all libraries to which I would apply this retention classes mechanism. No it does not. You may as well define the depMgmt locally. You don't have to share it. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to install the impl module for a api dependency in maven
Thanks, i think that i can use the compiler scopes to resolve the dependencies. But in order to have one war per flavor i have to move all my resources, like jsp's, out of my war and into a child war project rigth? and create more than one top level war with the dependencies to the diferente impl modules. was this what you meant by one project per flavour? On Tue, Nov 5, 2013 at 12:00 PM, Anders Hammar and...@hammar.net wrote: I don't fully understand what you want to accomplish, but, as you point out, profiles is not the right path. It almost never is. :-) What I think you want to do is to have compile scope dependencies to your api artifacts from the impl projects. And then in the war project (presentation module) you declare deps to the artifacts you need (you have a dependency to), which should include impl artifacts as they are needed. In your war project I would assume that you have some kind of compile time dependency to your impl code, and if so you need to declare that. If you don't have a compile time dependency, then you have a runtime dependency and then specify that (scope 'runtime'). If you want different flavors of your webapp, then you create one war project per flavor. /Anders On Tue, Nov 5, 2013 at 11:50 AM, João Pedro pedro.j...@gmail.com wrote: I have a multi-module maven project structured in something like this: parent | |-presentation |+services ||-services-api ||-services-impl |+data-access ||-data-access-api ||-data-access-impl |-+connector ||-connector-api ||-connector-implA ||-connector-implB |-... The presentation module is packaged in a war and it depends only on the api modules. When i run the install goal the only dependencies that the war installs are the api modules. To choose wich impl modules to install in the presentation module i'm using profiles that add the dependency to the impl modules at build time depending on the profiles selected. From what i've been reading i don't think that this is correct usage for the maven profiles. What is the best way to tell maven to add the chosen impl to the presentation module? I would like to keep the dependency to only the api module but with the usage of profiles, if the profile is active, the dependency is there and no compilation errors will happen when i reference a class of the impl module... thanks -- Cumprimentos, João Pedro -- Cumprimentos, João Pedro
Re: How to install the impl module for a api dependency in maven
Thanks, i think that i can use the compiler scopes to resolve the dependencies. Compile scope dependency is the default dependency scope. It is what you probably already use. But in order to have one war per flavor i have to move all my resources, like jsp's, out of my war and into a child war project rigth? and create more than one top level war with the dependencies to the diferente impl modules. was this what you meant by one project per flavour? You could use war overlays. Create the war projects as sibling modules. /Anders On Tue, Nov 5, 2013 at 12:00 PM, Anders Hammar and...@hammar.net wrote: I don't fully understand what you want to accomplish, but, as you point out, profiles is not the right path. It almost never is. :-) What I think you want to do is to have compile scope dependencies to your api artifacts from the impl projects. And then in the war project (presentation module) you declare deps to the artifacts you need (you have a dependency to), which should include impl artifacts as they are needed. In your war project I would assume that you have some kind of compile time dependency to your impl code, and if so you need to declare that. If you don't have a compile time dependency, then you have a runtime dependency and then specify that (scope 'runtime'). If you want different flavors of your webapp, then you create one war project per flavor. /Anders On Tue, Nov 5, 2013 at 11:50 AM, João Pedro pedro.j...@gmail.com wrote: I have a multi-module maven project structured in something like this: parent | |-presentation |+services ||-services-api ||-services-impl |+data-access ||-data-access-api ||-data-access-impl |-+connector ||-connector-api ||-connector-implA ||-connector-implB |-... The presentation module is packaged in a war and it depends only on the api modules. When i run the install goal the only dependencies that the war installs are the api modules. To choose wich impl modules to install in the presentation module i'm using profiles that add the dependency to the impl modules at build time depending on the profiles selected. From what i've been reading i don't think that this is correct usage for the maven profiles. What is the best way to tell maven to add the chosen impl to the presentation module? I would like to keep the dependency to only the api module but with the usage of profiles, if the profile is active, the dependency is there and no compilation errors will happen when i reference a class of the impl module... thanks -- Cumprimentos, João Pedro -- Cumprimentos, João Pedro
Re: Database generation in separate module
Hi List, I haven't received an answer from the list, but I've found a solution myself. In the context of sharing knowledge, here is how I've solved my problem: (again this image for clarification) pom.xml | |-module1 ||-pom.xml | |-module2 ||-pom.xml | |-database ||-pom.xml ||-src/../liquibase.xml The database module now also builds a zip assembly from the generated H2 database in the target directory (phase: package). This assembly is installed into the local Maven repository. In the other modules I've added (scope: test) dependencies to this zip artifact. I use the maven-dependency-plugin to unpack the zip dependency into its target directory (phase: generate-resources). Now I can use the H2 database as a dependency, which was generated in another module. The only thing I don't really like about it, is that the generated database, which is currently still small, is deployed in my Maven repo. But on the other side, it does allow the other modules to always use it, even without (re-)building the database module in each run. Yay for Maven ;-) Melvyn On Thu, Oct 31, 2013 at 7:48 PM, Melvyn de Kort mel...@mdekort.nl wrote: Hi all, I have a project which consists of several modules: pom.xml | --- module1 | src/... | pom.xml | --- module2 | src/... | pom.xml | --- database src/.../liquibase.xml pom.xml My Liquibase changelogs are all in the database module under the src/main/resources directory. The database module executes the liquibase:update during the process-resources stage, this works great. During a normal run It uses a H2 database which it creates in the target directory of its own module (database/target/dbfile). The packaging of this module is simply pom, and I plan on configuring an assembly which creates a ZIP file containing everything needed for setting up and updating a database. Now my problem is that when I want to test one of my other modules against a database, I want to use a H2 database which was created by Liquibase. How can I get the Liquibase generated H2 database from the target folder of the database module into the target directory of module 1 or/and 2? Or are there any other mechanisms I could use? I prefer not to generate the H2 database in something else than the target directories when I don't have to. I want the Maven projects to be self-contained and not rely on some other directory or the users settings.xml. Thank you in advance. Melvyn
How to obtain a ModelResolver in a MOJO
Hi all mates, I am writing a plugin which needs to calcuate the effective POM of a given GAV coordinate - IIUC I need an instance of org.apache.maven.model.resolution.ModelResolver, but didn't find a way to obatin a concrete service reference... Do you have any hint? Any suggestin will be much more than appreciated! Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi
Some help needed with maven-enforcer-plugin
Hi All! I am struggling with the enforcer-plugin's requireSameVersions rule. Introducing the bannedDependencies rule was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludecommons-logging/exclude /excludes /bannedDependencies /rules failtrue/fail /configuration /execution execution idenforce-same-versions/id goals goalenforce/goal /goals configuration rules requireSameVersions dependencies dependencyorg.slf4j:*/dependency /dependencies /requireSameVersions /rules failtrue/fail /configuration /execution /executions configuration ignoreCachetrue/ignoreCache /configuration /plugin As a matter of fact we have org.slf4j:slf4j-api:1.7.5 as well as org.slf4j:com.springsource.slf4j.api:1.6.1 in our dependency tree. But still the build is SUCCESSFUL. Did I get anything wrong here? Some misconfiguration. I would expect that the rule as configured would enforce all org.slf4j-group dependencies to have the same version. Thanks for your help! Markward
Re: Some help needed with maven-enforcer-plugin
I looked up the ticket that introduced the feature: http://jira.codehaus.org/browse/MENFORCER-147 It doesn't look like it enforces dependency versions; it enforces that Maven plugin versions in build match reporting. Paul On Tue, Nov 5, 2013 at 10:07 AM, Markward Schubert markward.schub...@gmail.com wrote: Hi All! I am struggling with the enforcer-plugin's requireSameVersions rule. Introducing the bannedDependencies rule was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludecommons-logging/exclude /excludes /bannedDependencies /rules failtrue/fail /configuration /execution execution idenforce-same-versions/id goals goalenforce/goal /goals configuration rules requireSameVersions dependencies dependencyorg.slf4j:*/dependency /dependencies /requireSameVersions /rules failtrue/fail /configuration /execution /executions configuration ignoreCachetrue/ignoreCache /configuration /plugin As a matter of fact we have org.slf4j:slf4j-api:1.7.5 as well as org.slf4j:com.springsource.slf4j.api:1.6.1 in our dependency tree. But still the build is SUCCESSFUL. Did I get anything wrong here? Some misconfiguration. I would expect that the rule as configured would enforce all org.slf4j-group dependencies to have the same version. Thanks for your help! Markward -- Cheers, Paul
Re: import plugin configurations
Hi, +1 about the obvious need to also import the plugins configuration, as well as the dependencies configuration. I'm interested by your solution. Is it open source, still in use, maintained, Maven 2 and/or 3 compliant? Given the answers you got, here are some additional arguments about the difference between a corporate POM and a third-party BOM, both being needed in some cases. From a customer project point of view, since there can be only one parent POM, such an import solution is required for reusing the provider project's configuration (ie the third-party BOM: dependencyManagement, pluginManagement, properties; including profiles; maybe also the repositories and pluginRepositories, and optionally the dependencies, plugins and reporting) but in the mean time also using custom corporate configuration (ie the corporate POM: organization, licenses, distributionManagement, ...). The following figure is missing the multi-enterprise aspect with parent/import relationships from outside the company: http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html#fig-multi-module Regards, Marcos Mendez wrote So just to give a heads-up on what I've done. I needed the ability to be able to import more than just dependency management (DM) from a pom. USE CASE: Import properties and plugin configurations from a central location Once your company starts using maven and creating all sorts of projects, this ability becomes necessary. Managing common changes in properties, plugin versions and configurations across multiple big projects (diff repos) becomes tedious. SOLUTION: Custom build extension I created a build extension that merges interesting (to me) items from an external pom into the maven projects accessible to the extension. Sort of like having an external parent pom, though not as powerful as there are only a couple of things that work; mainly what I was interested in - plugins and their configurations. LIMITATIONS: Manual property resolution. Not everything can be merged to affect the current build. For example I have to resolve external properties during my merging process. They don't seem to resolve properly even when I add them to the project's properties. Changes are merged into the project's build plugins. Adding them to plugin management has no effect, probably because the projects have already been read. Works for me though. I think this should probably be a feature for future versions of maven. Importing should not just be restricted to DM. -- View this message in context: http://maven.40175.n5.nabble.com/import-plugin-configurations-tp5741927p5774388.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Some help needed with maven-enforcer-plugin
Thanks Paul, ahh, I think I really misunderstood the docs. The dependencies tag refers to dependencies of plugins, instead of depenencies of the project. Thanks! 2013/11/5 Paul Benedict pbened...@apache.org I looked up the ticket that introduced the feature: http://jira.codehaus.org/browse/MENFORCER-147 It doesn't look like it enforces dependency versions; it enforces that Maven plugin versions in build match reporting. Paul On Tue, Nov 5, 2013 at 10:07 AM, Markward Schubert markward.schub...@gmail.com wrote: Hi All! I am struggling with the enforcer-plugin's requireSameVersions rule. Introducing the bannedDependencies rule was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludecommons-logging/exclude /excludes /bannedDependencies /rules failtrue/fail /configuration /execution execution idenforce-same-versions/id goals goalenforce/goal /goals configuration rules requireSameVersions dependencies dependencyorg.slf4j:*/dependency /dependencies /requireSameVersions /rules failtrue/fail /configuration /execution /executions configuration ignoreCachetrue/ignoreCache /configuration /plugin As a matter of fact we have org.slf4j:slf4j-api:1.7.5 as well as org.slf4j:com.springsource.slf4j.api:1.6.1 in our dependency tree. But still the build is SUCCESSFUL. Did I get anything wrong here? Some misconfiguration. I would expect that the rule as configured would enforce all org.slf4j-group dependencies to have the same version. Thanks for your help! Markward -- Cheers, Paul
Re: Some help needed with maven-enforcer-plugin
This is indeed the expected configuration, so you might have hit a bug. Robert Op Tue, 05 Nov 2013 17:07:12 +0100 schreef Markward Schubert markward.schub...@gmail.com: Hi All! I am struggling with the enforcer-plugin's requireSameVersions rule. Introducing the bannedDependencies rule was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludecommons-logging/exclude /excludes /bannedDependencies /rules failtrue/fail /configuration /execution execution idenforce-same-versions/id goals goalenforce/goal /goals configuration rules requireSameVersions dependencies dependencyorg.slf4j:*/dependency /dependencies /requireSameVersions /rules failtrue/fail /configuration /execution /executions configuration ignoreCachetrue/ignoreCache /configuration /plugin As a matter of fact we have org.slf4j:slf4j-api:1.7.5 as well as org.slf4j:com.springsource.slf4j.api:1.6.1 in our dependency tree. But still the build is SUCCESSFUL. Did I get anything wrong here? Some misconfiguration. I would expect that the rule as configured would enforce all org.slf4j-group dependencies to have the same version. Thanks for your help! Markward - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Scope question
Hi, I will dig in the dependency manager. Best regards, Guillaume - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
best way to attach source for debugging maven plugin
I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release plugin, Windows, Subversion
Folks, I'm starting to work with Maven's release plugin and I've run into a problem. OS: Windows 7 64 bit Home Premium SCM:TortoiseSVN 1.7.10 Maven: 3.1.1 SCM Plugin: 1.8.1 The error I get on mvn release:prepare is: [ERROR] svn: E720005: Error resolving case of 'C:\Users\mdeggers\My Documents\NetBeansProjects\ProjectConfig\pom.xml' This is apparently because the release plugin stores backslashes, but subversion expects forward slashes. I've found a bug report for this, but it's still open. Is there any workaround for this issue? BTW - the release works flawlessly on Linux (Fedora 19, 64 bit). Thanks, /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin, Windows, Subversion
Hi, If you run Maven with debug logging (add -X to the arguments) you will see how the maven-release-plugin executes the svn executable. It will look something like cmd.exe /X /C svn.exe . You should see the same result when you copy the cmdline between the quotes and executes it directly. That way you can verify that it is not a problem of the maven-release-plugin, but from the SVN Client or the way your project is checked out under Windows. Robert Op Tue, 05 Nov 2013 22:52:35 +0100 schreef Mark Eggers its_toas...@yahoo.com: Folks, I'm starting to work with Maven's release plugin and I've run into a problem. OS: Windows 7 64 bit Home Premium SCM:TortoiseSVN 1.7.10 Maven: 3.1.1 SCM Plugin: 1.8.1 The error I get on mvn release:prepare is: [ERROR] svn: E720005: Error resolving case of 'C:\Users\mdeggers\My Documents\NetBeansProjects\ProjectConfig\pom.xml' This is apparently because the release plugin stores backslashes, but subversion expects forward slashes. I've found a bug report for this, but it's still open. Is there any workaround for this issue? BTW - the release works flawlessly on Linux (Fedora 19, 64 bit). Thanks, /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: best way to attach source for debugging maven plugin
Use mvnDebug cli instead of mvn -- Olivier On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote: I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: best way to attach source for debugging maven plugin
On 11/05/2013 04:22 PM, Olivier Lamy wrote: Use mvnDebug cli instead of mvn -- Olivier On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote: I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, I am using the mvnDebug cli. That does seems to bring in the Maven (core and plugin source) but it does not bring in the source for the Codehaus Plexus stuff called by the plugin, which I also need to see for this debugging. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: best way to attach source for debugging maven plugin
Bringing in the source should be a function of your editor. What are you using? It works fine for me in IntelliJ - Russ On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote: On 11/05/2013 04:22 PM, Olivier Lamy wrote: Use mvnDebug cli instead of mvn -- Olivier On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote: I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, I am using the mvnDebug cli. That does seems to bring in the Maven (core and plugin source) but it does not bring in the source for the Codehaus Plexus stuff called by the plugin, which I also need to see for this debugging. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Author, Getting Started with Apache Maven http://www.packtpub.com/getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!
Re: best way to attach source for debugging maven plugin
I'm using Eclipse (with m2eclipse). Basic problem there is that plugins are not normally dependencies of a maven project, therefore do not show up anywhere where I can apply the Maven-get source function. I suppose I could make them dependencies but that seems wrong. On 11/05/2013 05:51 PM, Russell Gold wrote: Bringing in the source should be a function of your editor. What are you using? It works fine for me in IntelliJ - Russ On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote: On 11/05/2013 04:22 PM, Olivier Lamy wrote: Use mvnDebug cli instead of mvn -- Olivier On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote: I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, I am using the mvnDebug cli. That does seems to bring in the Maven (core and plugin source) but it does not bring in the source for the Codehaus Plexus stuff called by the plugin, which I also need to see for this debugging. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Author, Getting Started with Apache Maven http://www.packtpub.com/getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: best way to attach source for debugging maven plugin
Hi, I think you are just gonna have to retrieve the code manually inside your ide. Cheers Le 6 nov. 2013 03:34, Steve Cohen sco...@javactivity.org a écrit : I'm using Eclipse (with m2eclipse). Basic problem there is that plugins are not normally dependencies of a maven project, therefore do not show up anywhere where I can apply the Maven-get source function. I suppose I could make them dependencies but that seems wrong. On 11/05/2013 05:51 PM, Russell Gold wrote: Bringing in the source should be a function of your editor. What are you using? It works fine for me in IntelliJ - Russ On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote: On 11/05/2013 04:22 PM, Olivier Lamy wrote: Use mvnDebug cli instead of mvn -- Olivier On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote: I have a need to debug the maven-assembly-plugin which is not functioning correctly. I have found the instructions for setting up a debugging environment for maven itself within eclipse. What is the best way to get the source for this plugin so that it can be used by the debugging process. I know I can download it from svn, and attach in Eclipse, but is there a maven command to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, I am using the mvnDebug cli. That does seems to bring in the Maven (core and plugin source) but it does not bring in the source for the Codehaus Plexus stuff called by the plugin, which I also need to see for this debugging. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Author, Getting Started with Apache Maven http://www.packtpub.com/ getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater. com/misfile/! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
