Re: Maven SQL plugin
Folks, Can I specify wildcards like c:\SQLscripts\create\*.sql for the srcFile attribute within srcFiles? We have our db scripts in separate folders like create, upgrade, constraints, triggers etc. As the name says create folders has sql files that have db script to create tables, upgrade has scripts to alter the tables incase we add/remove any columns etc, constraints folder has sql scripts to add foreign key, indexes etc. Sql files within a particular folder can be executed in any order, it does not matter. However, the folders must be picked up in a predefined order, eg: create, upgrade, constraints triggers etc. In this case, I cannot use the fileset as the ordering mechanism is alphabetical. srcFiles seems a good choice however I cannot specify wildcards :( Any help? Thanks, Chris. On Fri, Oct 15, 2010 at 3:48 AM, John Singleton john.te...@gmail.comwrote: http://jira.codehaus.org/browse/MSQL-53 addresses exactly this issue... On Thu, Oct 14, 2010 at 5:12 PM, John Singleton john.te...@gmail.com wrote: Hi Chris, It has been my experience of ~2.5 years that the order is maintained with a srcFile list, though I see nothing in the plugin docs that specifically mentions this, nor have I had the time (or inclination) to read the source... We have a relatively small number of sql files, 4 in one place, 2 in another, so it is not too bad for us to list them all by name. FWIW, we are using version 1.4 of the plugin. Cheers, John On Thu, Oct 14, 2010 at 10:27 AM, Chris Odney chris.od...@gmail.com wrote: Hi John, I never noticed the option of srcFiles as against fileset My understanding is the list of files specified using srcFiles are executed in the order they are specified whereas it is not so in the case of fileset(this is when orderFile attribute is not specified). Am I wrong? Thanks for the reply, Chris. On Thu, Oct 14, 2010 at 7:33 PM, John Singleton john.te...@gmail.com wrote: Hi Chris, #2 is probably the best to ensure repeatability in the order you want. It also prevents inadvertent re-ordering if a new sql file is introduced into the sql directory. In our project, we use srcFiles rather than fileset: srcFiles srcFile[file1]/srcFile srcFile[file2}/srcFile ... /srcFiles HTH, John Singleton On Thu, Oct 14, 2010 at 9:25 AM, Chris Odney chris.od...@gmail.com wrote: Hi, I am facing some problem in ordering the sql execution. We have one sql script file for each table under one directory. Ex: There is user.sql and role.sql in the directory c:\SqlScripts. We are using the sql maven plugin to execute these sql files. The role table has a Foriegn key to the user table and the execution is failing because the plugin is trying to execute the role.sql before user.sql. I cannot use the orderfile attribute as we specify the fileset as c:\SqlScripts\*.sql. How do I overcome this problem? I see 2 solutions: 1) Merge all scripts into one file in the creation order, the script to create role comes after the script to create user. 2)Remove the * wildcard and specify each file in the filelist attribute in the order of execution. 3)Number the name of the files according to the execution order ex: 1_user.sql, 2_role.sql and use the 'ascending' orderfile attribute(not sure if this would work though, as the ordering may not be applied) Any more elegant solutions? Thank you, Chris.
Re: Now seriously: how can I manage dependencies of own projects with maven
On 18 October 2010 23:15, Zac Thompson z...@zac.ca wrote: On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I just set up a big fat aggrigator for each of the test everything together projects that I want to run CI over. I use svn:externals to check everything out and then two maven builders, first to update the aggregator and all child modules to link them together and the second to run verify. That way I never pollute the local repo... and these types of build run less frequently (hourly), so the slower build is less of an issue. Thanks for this bit, Stephen; I've been considering doing exactly this for a little while, so it's good to know you've already proven it can work well in practice. I think nightly is good enough in my case. I haven't tried using externals with Hudson yet, so I'm curious: does your hourly build always run whether there have been changes or not, or are you getting Hudson to check for updates first? I set it as downstream of each module's job so that if the svn:externals build correctly, then we trigger a build of the latest integration uber-build - 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
Assembly Plugin
Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded.
Re: Assembly Plugin
If it is a dependency of Project A and Project B it belongs to its own module and be treated as a dependency. It is the easiest way, really. Another option would be to use the dependency plugin unpack goal with an includes of the needed file. [1] [1] http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Tue, Oct 19, 2010 at 9:55 AM, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly Plugin
Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded.
Re: clean then package error
yes, I do this from m2eclipse, not command line. and I have set eclipse running in jdk in the setting.ini of eclipse. my setting: -vm D:\Java\jdk1.6.0_21\bin\javaw.exe I think it's what you say,right? -- From: Anders Hammar and...@hammar.net Sent: Tuesday, October 19, 2010 12:34 PM To: Maven Users List users@maven.apache.org Subject: Re: clean then package error You're doing tis from Eclipse/m2eclipe, right? Not command line? Is you're Eclipseset up to use a JDK? http://tech.karolzielinski.com/m2eclipse-eclipse-is-running-in-a-jre-but-a-jdk-is-required /Anders 2010/10/19 冯仁君 frj1...@126.com yes,I know. but I have set the JAVA_HOME pointing to the directory of JDK. and when I run package without clean before, it works well. if I run clean, and then package, it's error! -- From: MK Tan mktan...@gmail.com Sent: Monday, October 18, 2010 11:34 PM To: Maven Users List users@maven.apache.org Subject: Re: clean then package error I should spell check before I sending this mail. Maven need jdk and not jre. And if possible please include environment variable called JAVA_HOME which point to your jdk installation directory 2010/10/18 MK Tan mktan...@gmail.com Haven require jdk but you are refer to jre On Oct 18, 2010 8:46 PM, 冯仁君 frj1...@126.com wrote: I'm new in using maven. when I try to package a helloworld maven program after I clean in the Eclipse IDE, it comes to an error. it says : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project module: Compilation failure Unable to locate the Javac Compiler in: D:\Java\jre6\..\lib\tools.jar Please ensure you are using JDK 1.4 or above and not a JRE (the com.sun.tools.javac.Main class is required). In most cases you can change the location of your Java installation by setting the JAVA_HOME environment variable. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :module I'm sure I have installed the jdk1.6, and my environment variable is also correct. I don't it's the problem of maven, but I don't know what to do. what can I do? - 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: Assembly Plugin
Hi, Thanks for the very quick response. I've one project that include a configuration file, the same configuration file with same values need to be used in other projects (more than one), i didn't want to keep the same file on multiple projects and maintain each of them. i can change the structure of the project to maven structure but my issue with it is that in assembly that i create i want all files in src/main/config to be save to conf directory, but what the assembly plugin does instead is creating directory structure like this conf/src/main/config/files (i actually need conf/files) this xml file is being used by the other projects by sending the xml path as a VM parameter... i hope i made my self clear... thanks On Tue, Oct 19, 2010 at 10:48 AM, Anders Hammar and...@hammar.net wrote: Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. -- Oded.
Re: clean then package error
Does it work from command line? If so, move this to the m2eclipse users list and ask for help there. /Anders 2010/10/19 冯仁君 frj1...@126.com yes, I do this from m2eclipse, not command line. and I have set eclipse running in jdk in the setting.ini of eclipse. my setting: -vm D:\Java\jdk1.6.0_21\bin\javaw.exe I think it's what you say,right? -- From: Anders Hammar and...@hammar.net Sent: Tuesday, October 19, 2010 12:34 PM To: Maven Users List users@maven.apache.org Subject: Re: clean then package error You're doing tis from Eclipse/m2eclipe, right? Not command line? Is you're Eclipseset up to use a JDK? http://tech.karolzielinski.com/m2eclipse-eclipse-is-running-in-a-jre-but-a-jdk-is-required /Anders 2010/10/19 冯仁君 frj1...@126.com yes,I know. but I have set the JAVA_HOME pointing to the directory of JDK. and when I run package without clean before, it works well. if I run clean, and then package, it's error! -- From: MK Tan mktan...@gmail.com Sent: Monday, October 18, 2010 11:34 PM To: Maven Users List users@maven.apache.org Subject: Re: clean then package error I should spell check before I sending this mail. Maven need jdk and not jre. And if possible please include environment variable called JAVA_HOME which point to your jdk installation directory 2010/10/18 MK Tan mktan...@gmail.com Haven require jdk but you are refer to jre On Oct 18, 2010 8:46 PM, 冯仁君 frj1...@126.com wrote: I'm new in using maven. when I try to package a helloworld maven program after I clean in the Eclipse IDE, it comes to an error. it says : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project module: Compilation failure Unable to locate the Javac Compiler in: D:\Java\jre6\..\lib\tools.jar Please ensure you are using JDK 1.4 or above and not a JRE (the com.sun.tools.javac.Main class is required). In most cases you can change the location of your Java installation by setting the JAVA_HOME environment variable. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :module I'm sure I have installed the jdk1.6, and my environment variable is also correct. I don't it's the problem of maven, but I don't know what to do. what can I do? - 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: Assembly Plugin
OK, move the config file to a separate project then. The use the dependency plugin as someone else suggested, and unpack. Have a look at the assembly plugin. You can control which folder stuff is added to in the archive. (define outputDirectory) /Anders On Tue, Oct 19, 2010 at 12:26, Maimon Oded oded.mai...@gmail.com wrote: Hi, Thanks for the very quick response. I've one project that include a configuration file, the same configuration file with same values need to be used in other projects (more than one), i didn't want to keep the same file on multiple projects and maintain each of them. i can change the structure of the project to maven structure but my issue with it is that in assembly that i create i want all files in src/main/config to be save to conf directory, but what the assembly plugin does instead is creating directory structure like this conf/src/main/config/files (i actually need conf/files) this xml file is being used by the other projects by sending the xml path as a VM parameter... i hope i made my self clear... thanks On Tue, Oct 19, 2010 at 10:48 AM, Anders Hammar and...@hammar.net wrote: Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. -- Oded.
Re: Now seriously: how can I manage dependencies of own projects with maven
If you are using 'downstream', how do you avoid the need to publish to at least a common local repo? I've been facing the following variation on this: I do not want to publish snapshots to nexus, since they mess up people who download stale ones into their development process. I do want to split a hudson build into multiple jobs with dependencies. Short of an extra repo in nexus that is used only for intra-hudson snapshots, I haven't thought of anything. Have you? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Now seriously: how can I manage dependencies of own projects with maven
because downstream is the trigger, the build checks everything out and uses an uber-aggregator build so that all the artifacts will be in the reactor which is how mvn verify can work (no need for clean because I do a clean checkout for every build) On 19 October 2010 12:25, Benson Margulies bimargul...@gmail.com wrote: If you are using 'downstream', how do you avoid the need to publish to at least a common local repo? I've been facing the following variation on this: I do not want to publish snapshots to nexus, since they mess up people who download stale ones into their development process. I do want to split a hudson build into multiple jobs with dependencies. Short of an extra repo in nexus that is used only for intra-hudson snapshots, I haven't thought of anything. Have you? - 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: Now seriously: how can I manage dependencies of own projects with maven
On Tue, Oct 19, 2010 at 7:28 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: because downstream is the trigger, the build checks everything out and uses an uber-aggregator build so that all the artifacts will be in the reactor which is how mvn verify can work (no need for clean because I do a clean checkout for every build) I'm confused between the implications of 'uberaggregated' and 'downstream'. You've combined all the pieces into one giant build that is downstream of something else, right? OK, I see. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly Plugin
Hi, thanks, i was able to use it as a dependency, it was easy, but the problem with the directory structure remains.. when my file is src/main/config/myxml.xml and i set the output directory to be conf the result is conf/src/main/config/myxml.xml while i want it to just be conf/myxml.xml i guess that i'm doing something wrong here.. thanks. On Tue, Oct 19, 2010 at 1:23 PM, Anders Hammar and...@hammar.net wrote: OK, move the config file to a separate project then. The use the dependency plugin as someone else suggested, and unpack. Have a look at the assembly plugin. You can control which folder stuff is added to in the archive. (define outputDirectory) /Anders On Tue, Oct 19, 2010 at 12:26, Maimon Oded oded.mai...@gmail.com wrote: Hi, Thanks for the very quick response. I've one project that include a configuration file, the same configuration file with same values need to be used in other projects (more than one), i didn't want to keep the same file on multiple projects and maintain each of them. i can change the structure of the project to maven structure but my issue with it is that in assembly that i create i want all files in src/main/config to be save to conf directory, but what the assembly plugin does instead is creating directory structure like this conf/src/main/config/files (i actually need conf/files) this xml file is being used by the other projects by sending the xml path as a VM parameter... i hope i made my self clear... thanks On Tue, Oct 19, 2010 at 10:48 AM, Anders Hammar and...@hammar.net wrote: Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. -- Oded. -- Oded.
Re: Now seriously: how can I manage dependencies of own projects with maven
On 19 October 2010 12:42, Benson Margulies bimargul...@gmail.com wrote: On Tue, Oct 19, 2010 at 7:28 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: because downstream is the trigger, the build checks everything out and uses an uber-aggregator build so that all the artifacts will be in the reactor which is how mvn verify can work (no need for clean because I do a clean checkout for every build) I'm confused between the implications of 'uberaggregated' and 'downstream'. You've combined all the pieces into one giant build that is downstream of something else, right? OK, I see. it's downstream of the trunks of each of it's components... the trunk projects build svn as is and are triggered by svn trigger this is the latest of everything project and that builds only if the constituent trunk projects are building, and wht it is building is not the code in svn but the code in svn after re-linking to the reactor hmmm I think I might have a new feature for versions-m-p (versions:use-reactor) -Stephen - 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: Now seriously: how can I manage dependencies of own projects with maven
Attached is a sample of how I configure the builders (using update-properties as my inter-module deps are via properties for this uber-integration-project) the principle remains the same On 19 October 2010 12:50, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 19 October 2010 12:42, Benson Margulies bimargul...@gmail.com wrote: On Tue, Oct 19, 2010 at 7:28 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: because downstream is the trigger, the build checks everything out and uses an uber-aggregator build so that all the artifacts will be in the reactor which is how mvn verify can work (no need for clean because I do a clean checkout for every build) I'm confused between the implications of 'uberaggregated' and 'downstream'. You've combined all the pieces into one giant build that is downstream of something else, right? OK, I see. it's downstream of the trunks of each of it's components... the trunk projects build svn as is and are triggered by svn trigger this is the latest of everything project and that builds only if the constituent trunk projects are building, and wht it is building is not the code in svn but the code in svn after re-linking to the reactor hmmm I think I might have a new feature for versions-m-p (versions:use-reactor) -Stephen - 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: Assembly Plugin
Yes, it works on my machine. :-) It's very hard to spot the issue if you don't provide more info. /Anders On Tue, Oct 19, 2010 at 13:49, Maimon Oded oded.mai...@gmail.com wrote: Hi, thanks, i was able to use it as a dependency, it was easy, but the problem with the directory structure remains.. when my file is src/main/config/myxml.xml and i set the output directory to be conf the result is conf/src/main/config/myxml.xml while i want it to just be conf/myxml.xml i guess that i'm doing something wrong here.. thanks. On Tue, Oct 19, 2010 at 1:23 PM, Anders Hammar and...@hammar.net wrote: OK, move the config file to a separate project then. The use the dependency plugin as someone else suggested, and unpack. Have a look at the assembly plugin. You can control which folder stuff is added to in the archive. (define outputDirectory) /Anders On Tue, Oct 19, 2010 at 12:26, Maimon Oded oded.mai...@gmail.com wrote: Hi, Thanks for the very quick response. I've one project that include a configuration file, the same configuration file with same values need to be used in other projects (more than one), i didn't want to keep the same file on multiple projects and maintain each of them. i can change the structure of the project to maven structure but my issue with it is that in assembly that i create i want all files in src/main/config to be save to conf directory, but what the assembly plugin does instead is creating directory structure like this conf/src/main/config/files (i actually need conf/files) this xml file is being used by the other projects by sending the xml path as a VM parameter... i hope i made my self clear... thanks On Tue, Oct 19, 2010 at 10:48 AM, Anders Hammar and...@hammar.net wrote: Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. -- Oded. -- Oded.
RE: Assembly Plugin
works on my machine: configuration descriptors descriptorsrc/assemble/bin.xml/descriptor /descriptors /configuration file structure: pom.xml (located in current folder) src (folder of current folder) assemble (subfolder of src) bin.xml (contents of assemble subfolder) did you check to see if the descriptor tag is relative to the location of the pom.xml you are referencing? is it located in the relative path referenced by descriptor tag? do you have access to the file? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 19 Oct 2010 13:55:25 +0200 Subject: Re: Assembly Plugin From: and...@hammar.net To: users@maven.apache.org Yes, it works on my machine. :-) It's very hard to spot the issue if you don't provide more info. /Anders On Tue, Oct 19, 2010 at 13:49, Maimon Oded oded.mai...@gmail.com wrote: Hi, thanks, i was able to use it as a dependency, it was easy, but the problem with the directory structure remains.. when my file is src/main/config/myxml.xml and i set the output directory to be conf the result is conf/src/main/config/myxml.xml while i want it to just be conf/myxml.xml i guess that i'm doing something wrong here.. thanks. On Tue, Oct 19, 2010 at 1:23 PM, Anders Hammar and...@hammar.net wrote: OK, move the config file to a separate project then. The use the dependency plugin as someone else suggested, and unpack. Have a look at the assembly plugin. You can control which folder stuff is added to in the archive. (define outputDirectory) /Anders On Tue, Oct 19, 2010 at 12:26, Maimon Oded oded.mai...@gmail.com wrote: Hi, Thanks for the very quick response. I've one project that include a configuration file, the same configuration file with same values need to be used in other projects (more than one), i didn't want to keep the same file on multiple projects and maintain each of them. i can change the structure of the project to maven structure but my issue with it is that in assembly that i create i want all files in src/main/config to be save to conf directory, but what the assembly plugin does instead is creating directory structure like this conf/src/main/config/files (i actually need conf/files) this xml file is being used by the other projects by sending the xml path as a VM parameter... i hope i made my self clear... thanks On Tue, Oct 19, 2010 at 10:48 AM, Anders Hammar and...@hammar.net wrote: Your structure is not following the Maven file structure standard. All files should typically be in the appropriate directory below src (like src/main/config, src/main/scripts, etc). I find what you're trying to do strange. We would most likely be able to suggest a good solution if you provided more info on what you're trying to actually achieve. I don't understand why you would like to assemble the content of a project plus a minor part of some other project. What's the purpose? Why isn't the xml file in the project to begin with? /Anders On Tue, Oct 19, 2010 at 09:55, Maimon Oded oded.mai...@gmail.com wrote: Hi, I'm new to maven and I've a basic question that i hope that someone can help me with, my projects structure looks something like this: My project structure is simple: - Project A - src - conf - myxml.xml - scripts - Project B - src I would like to have an assembly for project B that will include only the myxml.xml file from project A + all the files in project B, is it possible? how? thanks, Oded. -- Oded. -- Oded.
Strange behaviour on resource plugin
Hi! I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. One of my maven projects uses the resource plugin to copy some configuration files with some placeholders in them. When running maven from eclipse, the placeholders are nicely replaced with some values from the pom file, but when starting maven from the console, this replacement does not take place. My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0 from the command line, both not eager to do the replacement. To make this behaviour even stranger, i detected this failing replacement after i updated my os from ubuntu 8/04 to 10/04, but i have no idea if that is really connected. I did not touch the maven installations at all, so it is a bit confusing Any idea is highly welcome :-) -- Med vennlig hilsen Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
how is the archetype-catalog.xml file on central updated?
I saw in ARCHETYPE-242 that Juven fixed the archetype catalog on Central back in April. How is that catalog updated? Thanks, Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
project structure with per-project trunks and svn
Hello experts, I'm trying to reconcile the standard maven project structure with the standard svn project structure (with per-project versioning). I'd like to have a subversion structure like this: pom.xml --proj A trunk --pom.xml --src --proj B trunk --pom.xml --src etc. How can I get maven to build everything properly? Should I use svn externals to magically remove the trunk directories so that this layout would conform to standard maven layout? If I did that, how would I handle the situation of wanting to build a particular branch..wouldn't I have to update the externals properties back and forth (cumbersome)? Or should I change all project poms to use parent relative paths of ../../pom.xml to get to the parent pom? But this technique wouldn't work if I wanted to build a particular branch because it would be an extra level deep (i.e. proj-branches-1.0.0-pom.xml). What is best practice here? Thank you. -- View this message in context: http://maven.40175.n5.nabble.com/project-structure-with-per-project-trunks-and-svn-tp3219163p3219163.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: project structure with per-project trunks and svn
If you have trunks underneath subprojects, that tells me they have independent release cycles. If you want them to be versioned separately, your structure is okay. If you want the master project to build and control the subprojects as modules, I would re-organize everything under one trunk. Paul On Tue, Oct 19, 2010 at 9:40 AM, thisguy bobsmith30...@yahoo.com wrote: Hello experts, I'm trying to reconcile the standard maven project structure with the standard svn project structure (with per-project versioning). I'd like to have a subversion structure like this: pom.xml --proj A trunk --pom.xml --src --proj B trunk --pom.xml --src etc. How can I get maven to build everything properly? Should I use svn externals to magically remove the trunk directories so that this layout would conform to standard maven layout? If I did that, how would I handle the situation of wanting to build a particular branch..wouldn't I have to update the externals properties back and forth (cumbersome)? Or should I change all project poms to use parent relative paths of ../../pom.xml to get to the parent pom? But this technique wouldn't work if I wanted to build a particular branch because it would be an extra level deep (i.e. proj-branches-1.0.0-pom.xml). What is best practice here? Thank you. -- View this message in context: http://maven.40175.n5.nabble.com/project-structure-with-per-project-trunks-and-svn-tp3219163p3219163.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how is the archetype-catalog.xml file on central updated?
Hi Justin, he uses a CLI tool not released yet, that actually relies on Index (code lifted to spice and shared from nexus-archetype-plugin): CI deploys of snapshot: https://repository.sonatype.org/content/repositories/snapshots/org/sonatype/spice/nexus-archetype-common/1.1-SNAPSHOT/ Source: https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true So, currently on Central, after reindex, this CLI runs too and generates the catalog from just updated index. Thanks, ~t~ On Tue, Oct 19, 2010 at 4:35 PM, Justin Edelson justinedel...@gmail.comwrote: I saw in ARCHETYPE-242 that Juven fixed the archetype catalog on Central back in April. How is that catalog updated? Thanks, Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: project structure with per-project trunks and svn
If the parent is deployed internally then you don't need to worry about the structure. Alternatively, if you are using a Build Management s Server like AHP or Hudson, tey can alter the layout on-the-fly at checkout/update time. Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time -Original Message- From: thisguy [mailto:bobsmith30...@yahoo.com] Sent: Tuesday, October 19, 2010 10:40 AM To: users@maven.apache.org Subject: project structure with per-project trunks and svn Hello experts, I'm trying to reconcile the standard maven project structure with the standard svn project structure (with per-project versioning). I'd like to have a subversion structure like this: pom.xml --proj A trunk --pom.xml --src --proj B trunk --pom.xml --src etc. How can I get maven to build everything properly? Should I use svn externals to magically remove the trunk directories so that this layout would conform to standard maven layout? If I did that, how would I handle the situation of wanting to build a particular branch..wouldn't I have to update the externals properties back and forth (cumbersome)? Or should I change all project poms to use parent relative paths of ../../pom.xml to get to the parent pom? But this technique wouldn't work if I wanted to build a particular branch because it would be an extra level deep (i.e. proj-branches-1.0.0-pom.xml). What is best practice here? Thank you. -- View this message in context: http://maven.40175.n5.nabble.com/project-structure-with-per-project-trun ks-and-svn-tp3219163p3219163.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 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how is the archetype-catalog.xml file on central updated?
Thanks. If I released an archetype via repository.apache.org today, it should be in the central archetype catalog on Sunday? On 10/19/10 10:54 AM, Tamás Cservenák wrote: Hi Justin, he uses a CLI tool not released yet, that actually relies on Index (code lifted to spice and shared from nexus-archetype-plugin): CI deploys of snapshot: https://repository.sonatype.org/content/repositories/snapshots/org/sonatype/spice/nexus-archetype-common/1.1-SNAPSHOT/ Source: https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true So, currently on Central, after reindex, this CLI runs too and generates the catalog from just updated index. Thanks, ~t~ On Tue, Oct 19, 2010 at 4:35 PM, Justin Edelson justinedel...@gmail.com mailto:justinedel...@gmail.com wrote: I saw in ARCHETYPE-242 that Juven fixed the archetype catalog on Central back in April. How is that catalog updated? Thanks, Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto: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: how is the archetype-catalog.xml file on central updated?
the archetype-catalog.xml is updated every Sunday: https://docs.sonatype.org/display/Repository/Central+Repository+FAQ On Tue, Oct 19, 2010 at 11:00 PM, Justin Edelson justinedel...@gmail.comwrote: Thanks. If I released an archetype via repository.apache.org today, it should be in the central archetype catalog on Sunday? On 10/19/10 10:54 AM, Tamás Cservenák wrote: Hi Justin, he uses a CLI tool not released yet, that actually relies on Index (code lifted to spice and shared from nexus-archetype-plugin): CI deploys of snapshot: https://repository.sonatype.org/content/repositories/snapshots/org/sonatype/spice/nexus-archetype-common/1.1-SNAPSHOT/ Source: https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true So, currently on Central, after reindex, this CLI runs too and generates the catalog from just updated index. Thanks, ~t~ On Tue, Oct 19, 2010 at 4:35 PM, Justin Edelson justinedel...@gmail.com mailto:justinedel...@gmail.com wrote: I saw in ARCHETYPE-242 that Juven fixed the archetype catalog on Central back in April. How is that catalog updated? Thanks, Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto:users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- - juven
New official Central repository in Europe
As you know, Maven Central has become an increasingly important resource for the development community at large. We've put several efforts forward earlier this year to help improve the content As you know, Maven Central has become an increasingly important resource for the development community at large. We've put several efforts forward earlier this year to help improve the content quality and to reduce the time required to get artifacts into the repository. These have matured over time and are now automatically validating artifacts. These processes are documented at [1] and [2] To improve the experience for users in Europe, Sonatype has provisioned a new official repository in the United Kingdom. This is more than a mere mirror of Central, this system is updated in lockstep with the systems here in the US, and is managed and monitored 24x7 by Contegix, the same team watching over the US repositories. The new repository consists of two fully redundant systems running in parallel to provide complete fail-over capacity. In addition to the new repository, we have taken several steps to improve and further secure Central itself: * A new system has replaced Central as the inbound processing engine. On this staging system, we can now vet inbound artifacts for quality and other parameters before publishing them to repo1 and Europe. It also serves as a hot standby for the US repository. * We've worked with Contegix to implement additional layered security around the repository machines themselves. * There is a new Jira project to manage any and all concerns and issues with Central, the Mirrors, Content, etc[3] * We are working to provide a repository in Asia soon. The new repository is live at http://uk.maven.org/maven2/ if you're using a repository manager, just replace references to http://repo1.maven.org/maven2 with the new url. If you're not, you should be[4][5], but until you get a repository manager in place, add the following to your settings.xml: mirrors mirror iduk/id mirrorOfcentral/mirrorOf urlhttp://uk.maven.org/maven2//url /mirror /mirrors Thanks, Brian [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide [2] https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central [3] https://issues.sonatype.org/browse/MVNCENTRAL [4] http://www.sonatype.com/Intro-RepoManagement.pdf [5] http://www.sonatype.com/Repo-StagesOfAdoption.pdf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: project structure with per-project trunks and svn
Things are not always so clear cut. For instance, we are developing the first release of an application which is composed of many projects. They are all versioned separately, so as to be ready when we'll have to start shipping updates as opposed to full releases, not to mention that different customers are likely to require customizations to different sub-projects. Still at this point most things are being developed at the same time and using a global aggregating project is convenient for different reasons. One is being able to use the same setup within our IDE of choice as we use for offline building. With Eclipse, Subversive and m2eclipse projects are automatically setup as externals when they are checked out in the top level project's directory. This only has to be done once; afterwards every developer can just checkout the top level project and materialize its modules and have the whole development environment correctly setup. This approach also makes it very simple to setup automated builds with Hudson. Furthermore, Maven has one advantage over other build systems in allowing aggregation to be a casual relationship among projects. For instance in our setup experienced developers may decide to have a private aggregating project where they only include those modules they are actually working on and rely on Maven to retrieve the rest from our Nexus instance. The only serious drawback is the fact that the Maven release plugin does not currently handle this setup. One piece of advice for the OP: Don't confuse inheritance with aggregation! Use one POM project to aggregate your sub-projects and another one to hold common configuration. The latter may well be a module of the former. Cheers, Nicola Musatti Paul Benedict wrote: If you have trunks underneath subprojects, that tells me they have independent release cycles. If you want them to be versioned separately, your structure is okay. If you want the master project to build and control the subprojects as modules, I would re-organize everything under one trunk. Paul On Tue, Oct 19, 2010 at 9:40 AM, thisguybobsmith30...@yahoo.com wrote: Hello experts, I'm trying to reconcile the standard maven project structure with the standard svn project structure (with per-project versioning). I'd like to have a subversion structure like this: pom.xml --proj A trunk --pom.xml --src --proj B trunk --pom.xml --src etc. How can I get maven to build everything properly? Should I use svn externals to magically remove the trunk directories so that this layout would conform to standard maven layout? If I did that, how would I handle the situation of wanting to build a particular branch..wouldn't I have to update the externals properties back and forth (cumbersome)? Or should I change all project poms to use parent relative paths of ../../pom.xml to get to the parent pom? But this technique wouldn't work if I wanted to build a particular branch because it would be an extra level deep (i.e. proj-branches-1.0.0-pom.xml). What is best practice here? Thank you. -- View this message in context: http://maven.40175.n5.nabble.com/project-structure-with-per-project-trunks-and-svn-tp3219163p3219163.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente il mittente e, tenuto conto delle responsabilita' connesse all'indebito utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso contenute, voglia cancellare l'originale e distruggere le varie copie o stampe. The receiver of this message is required to check if he/she has received it erroneously. If so, the receiver is requested to immediately inform the sender and - in consideration of the responsibilities arising from undue use and/or disclosure of the message and/or the information contained therein - destroy the original message and any copy or printout thereof. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Now seriously: how can I manage dependencies of own projects with maven
Attached is a sample of how I configure the builders (using update-properties as my inter-module deps are via properties for this uber-integration-project) the principle remains the same Either you failed to attach anything, or it got stripped. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
A project uses a resource defined in a module that it does not depends upon
Hi, I have this situation. Project A and B have many modules. Everyone has a configuration in which the root pom defines modules and all the dependency management, all the submodules uses root A pom as parent. Before I used to have a separate parent project as onother module but in the end did not seem really necessary. Module B1 uses some of the modules of A, but not everyone, now, I expect that if B1 depends on A1 and A2, it will not have any relation to A3. But what happens? That B1 see a file in the classpath of A3, to be precise, spring loads a properties file that is in A3/src/main/resources, overriding other properties. In fact, if from A pom I remove the A3 modulo, the properties file is not loaded anymore. I suspect that this happen because A1/2/3 all has A as parent pom. But this behavior really seem strange to me. -- Daniele Dellafiore http://danieledellafiore.net - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A project uses a resource defined in a module that it does not depends upon
But what happens? That B1 see a file in the classpath of A3, to be precise, spring loads a properties file that is in A3/src/main/resources, overriding other properties. How does Spring even see the file in A3? What kind of package are you assembling for B1? How do you run B1? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A project uses a resource defined in a module that it does not depends upon
Without any example project (at least the pom.xml for the different modules), I don't think anybody will be able to help you. Have you checked dependency:tree on B1? 2010/10/19 Daniele Dellafiore ilde...@gmail.com Hi, I have this situation. Project A and B have many modules. Everyone has a configuration in which the root pom defines modules and all the dependency management, all the submodules uses root A pom as parent. Before I used to have a separate parent project as onother module but in the end did not seem really necessary. Module B1 uses some of the modules of A, but not everyone, now, I expect that if B1 depends on A1 and A2, it will not have any relation to A3. But what happens? That B1 see a file in the classpath of A3, to be precise, spring loads a properties file that is in A3/src/main/resources, overriding other properties. In fact, if from A pom I remove the A3 modulo, the properties file is not loaded anymore. I suspect that this happen because A1/2/3 all has A as parent pom. But this behavior really seem strange to me. -- Daniele Dellafiore http://danieledellafiore.net - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Vincent
Re: Strange behaviour on resource plugin
I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. Did you lock down the version of m-r-p in your pom? If not, you really have no control over what version is being used, and it is possible that you have run into some change in functionality or a bug that is causing this behaviour. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange behaviour on resource plugin
Hello, Do you define the version of maven-resources-plugin in your pom ? Are you using profiles? 2010/10/19 Søren Krum soren.k...@uninett.no Hi! I have detected a strange bahaviour of the maven resource plugin, and i am wondering if someone can give me a hint, what is going wrong here. One of my maven projects uses the resource plugin to copy some configuration files with some placeholders in them. When running maven from eclipse, the placeholders are nicely replaced with some values from the pom file, but when starting maven from the console, this replacement does not take place. My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0 from the command line, both not eager to do the replacement. To make this behaviour even stranger, i detected this failing replacement after i updated my os from ubuntu 8/04 to 10/04, but i have no idea if that is really connected. I did not touch the maven installations at all, so it is a bit confusing Any idea is highly welcome :-) -- Med vennlig hilsen Søren D. Krum Systemutvikler/system developer UNINETT FAS + 47 73557859 There are 10 different kind of people in the world, those who understand binary and those who don't - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Vincent
scm connection in parent pom
Hi all,
Does it make sense and will it work to define the scm connection in a
parent pom if all my projects follow the same layout in SVN?
i.e.,
connectionscm:svn:http://mysvnrep.com/svn/projects/${artifactId}/trunk/connection
Also, is there a common way to let each developer decide which
protocol they want to use, e.g., svn+ssh:// instead of http://.
Thanks,
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
How to download a whole project
Hi, I'm new to Maven and I'm trying to add the Drools project to my dependency list in my projects POM. I've added to the POM: repositories repository idrepository.jboss.org/id urlhttp://repository.jboss.org/maven2/url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository /repositories dependencies dependency groupIdorg.drools/groupId artifactIddrools/artifactId version5.1.0.M1/version /dependency /dependencies I know the Jboss Drools Maven2 repository doesn't contain a single jar file at for this dependency. But I thought the drools 5.1.0.M1 POM contains transitive dependencies or something. So that all in the project contained data is referenced. I've also tried: dependency groupIdorg.drools/groupId artifactIddrools/artifactId version5.1.0.M1/version typepom/type /dependency What do I have to do to set the drools project as a reference? Thanks for any help! :) Tina
Re: How to download a whole project
I know the Jboss Drools Maven2 repository doesn't contain a single jar file at for this dependency. But I thought the drools 5.1.0.M1 POM contains transitive dependencies or something. So that all in the project contained ... What do I have to do to set the drools project as a reference? A great question... for the Drools User List. They know Drools better than we do, right? Come back when you have a question about how Maven works... Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to download a whole project
I'm sorry, I thought this is Maven-specific question, because it's about how Maven manages and gets dependencies. Sorry therefore. I know the Jboss Drools Maven2 repository doesn't contain a single jar file at for this dependency. But I thought the drools 5.1.0.M1 POM contains transitive dependencies or something. So that all in the project contained ... What do I have to do to set the drools project as a reference? A great question... for the Drools User List. They know Drools better than we do, right? Come back when you have a question about how Maven works... Wayne - 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: project structure with per-project trunks and svn
On 19/10/2010 11:30 AM, Nicola Musatti wrote: Things are not always so clear cut. For instance, we are developing the first release of an application which is composed of many projects. They are all versioned separately, so as to be ready when we'll have to start shipping updates as opposed to full releases, not to mention that different customers are likely to require customizations to different sub-projects. Still at this point most things are being developed at the same time and using a global aggregating project is convenient for different reasons. One is being able to use the same setup within our IDE of choice as we use for offline building. With Eclipse, Subversive and m2eclipse projects are automatically setup as externals when they are checked out in the top level project's directory. This only has to be done once; afterwards every developer can just checkout the top level project and materialize its modules and have the whole development environment correctly setup. This approach also makes it very simple to setup automated builds with Hudson. Furthermore, Maven has one advantage over other build systems in allowing aggregation to be a casual relationship among projects. For instance in our setup experienced developers may decide to have a private aggregating project where they only include those modules they are actually working on and rely on Maven to retrieve the rest from our Nexus instance. This is almost exactly the way we have our projects setup. Works very well and makes it easy to get releases done. The only serious drawback is the fact that the Maven release plugin does not currently handle this setup. One piece of advice for the OP: Don't confuse inheritance with aggregation! Use one POM project to aggregate your sub-projects and another one to hold common configuration. The latter may well be a module of the former. Exactly. Cheers, Nicola Musatti Paul Benedict wrote: If you have trunks underneath subprojects, that tells me they have independent release cycles. If you want them to be versioned separately, your structure is okay. If you want the master project to build and control the subprojects as modules, I would re-organize everything under one trunk. Paul On Tue, Oct 19, 2010 at 9:40 AM, thisguybobsmith30...@yahoo.com wrote: Hello experts, I'm trying to reconcile the standard maven project structure with the standard svn project structure (with per-project versioning). I'd like to have a subversion structure like this: pom.xml --proj A trunk --pom.xml --src --proj B trunk --pom.xml --src etc. How can I get maven to build everything properly? Should I use svn externals to magically remove the trunk directories so that this layout would conform to standard maven layout? If I did that, how would I handle the situation of wanting to build a particular branch..wouldn't I have to update the externals properties back and forth (cumbersome)? Or should I change all project poms to use parent relative paths of ../../pom.xml to get to the parent pom? But this technique wouldn't work if I wanted to build a particular branch because it would be an extra level deep (i.e. proj-branches-1.0.0-pom.xml). What is best practice here? Thank you. -- View this message in context: http://maven.40175.n5.nabble.com/project-structure-with-per-project-trunks-and-svn-tp3219163p3219163.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente il mittente e, tenuto conto delle responsabilita' connesse all'indebito utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso contenute, voglia cancellare l'originale e distruggere le varie copie o stampe. The receiver of this message is required to check if he/she has received it erroneously. If so, the receiver is requested to immediately inform the sender and - in consideration of the responsibilities arising from undue use and/or disclosure of the message and/or the information contained therein - destroy the original message and any copy or printout thereof. - 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,
Re: maven is a swamp
I think that's the main point. Nobody thinks XML is wonderful to read or write, but it's easily read by any tools, languages and by humans. XML is a standard, like it or not. It's a glue. Glue is good. Glue lets the logic be language neutral and portable. On 10/15/10 6:40 PM, Ron Wheeler rwhee...@artifact-software.com wrote: Who cares what language Maven uses? There are IDEs with editors that eliminate the need to look at XML. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
wagon-induced infinite build loop
I'm struggling with the infinite rebuild loop in Eclipse, which might be caused by an old Wagon bug. The bug is described here https://issues.sonatype.org/browse/MNGECLIPSE-1885 and https://issues.sonatype.org/browse/MNGECLIPSE-2239, and someone indicated that this Wagon bug might be the culprit: http://jira.codehaus.org/browse/WAGON-73. My question is, how can I get the latest version of Wagon on my build? If I delete the Wagon directory in my local Maven repo, and run mvn compile, I always get 1.0-alpha-6 and 1.0-beta-2 brought down. These are old versions of Wagon. I have taken our company parent POM and updated all the plugins listed there to the latest version I could find in the central maven repo. I have added Wagon 1.0-beta-6 to the dependencyManagement section of my POM. I've used Maven 3, both with and without my company parent POM. I still get those old versions. How can I force maven to use a later version of Wagon? How could I find out who/what is bringing Wagon into my build? Thanks for any help you can give!
How to download a whole project
Hi, I'm new to Maven and I'm trying to add the Drools project to my dependency list in my projects POM. I've added to the POM: repositories repository idrepository.jboss.org/id urlhttp://repository.jboss.org/maven2/url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository /repositories dependencies dependency groupIdorg.drools/groupId artifactIddrools/artifactId version5.1.0.M1/version /dependency /dependencies I know the Jboss Drools Maven2 repository doesn't contain a single jar file at for this dependency. But I thought the drools 5.1.0.M1 POM contains transitive dependencies or something. So that all in the project contained data is referenced. I've also tried: dependency groupIdorg.drools/groupId artifactIddrools/artifactId version5.1.0.M1/version typepom/type /dependency What do I have to do to set the drools project as a reference? Thanks for any help! :) Tina
wagon-induced infinite build loop
I'm struggling with the infinite rebuild loop in Eclipse, which might be caused by an old Wagon bug. The bug is described here https://issues.sonatype.org/browse/MNGECLIPSE-1885 and https://issues.sonatype.org/browse/MNGECLIPSE-2239, and someone indicated that this Wagon bug might be the culprit: http://jira.codehaus.org/browse/WAGON-73. My question is, how can I get the latest version of Wagon on my build? If I delete the Wagon directory in my local Maven repo, and run mvn compile, I always get 1.0-alpha-6 and 1.0-beta-2 brought down. These are old versions of Wagon. I have taken our company parent POM and updated all the plugins listed there to the latest version I could find in the central maven repo. I have added Wagon 1.0-beta-6 to the dependencyManagement section of my POM. I've used Maven 3, both with and without my company parent POM. I still get those old versions. How can I force maven to use a later version of Wagon? How could I find out who/what is bringing Wagon into my build? Thanks for any help you can give!
Re: overriding inherited properties: what's the semantics?
Let me add an example of what I observed and couldn't find
any documentation about:
project
groupIdmy-group/groupId
artifactIdmy-parent-pom/artifactId
properties
scm-hostsvn.my.host.org/scm-host
project-scm-pathtrunk/maven/my-parent-project/project-scm-path
properties
scm
connectionscm:svn:svn://${scm-host}/${project-scm-path}/connection
/sm
/project
project
parent
groupIdmy-group/groupId
artifactIdmy-parent-pom/artifactId
/parent
groupIdmy-group/groupId
artifactIdmy-child/artifactId
properties
project-scm-pathtrunk/maven/my-child-project/project-scm-path
properties
/project
Question: what scmconnection should my-child have?
Experiments yield:
scm:svn:svn://svn.my.host.org/trunk/maven/my-child-project/my-child
Note the appended my-child!
Compare this to the value in my-parent-pom:
scm:svn:svn://svn.my.host.org/trunk/maven/my-parent-project
If I copypaste the inherited scm section verbatim into the child
I get the expected result:
scm:svn:svn://svn.my.host.org/trunk/maven/my-child-project
For one, I'm asking if it is possible to obtain that result without duplicating
a declaration that is already inherited.
Second, I'm asking if there is any documentation that would tell
me in advance and without having to experiment, what the effect
of the given declarations is.
Also: if overriding inherited properties is a supported concept,
it would be cool if maven would follow the lead of good OO programming
languages: let the user specify whether a property definition is intended
to create a fresh property vs. override an inherited one (think @Override).
In my example I was additionally confused because a small typo in
one property name caused the introduction of a new (unused) property
where I intended to override an existing one. Good languages can
detect typos and report errors -- be they imperative or declarative.
Stephan
On Monday, October 18, 2010 05:02:57 pm you wrote:
I've observed some unexpected behavior when a declaration in a
parent pom uses a property that is overridden in a child pom.
While waiting for parameterized mixins I'd love to know to what
degree property overriding can actually simulate parameterization.
Is this a FAQ? Were should I search for a definition of the semantics?
Is evaluation order-dependent? If so, how exactly?
best,
Stephan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to download a whole project
2010/10/19 Tina Vießmann lfnik...@gmx.de: What do I have to do to set the drools project as a reference? I'd say, ask the Drools maintainers. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: scm connection in parent pom
On Tue, Oct 19, 2010 at 11:47 AM, Phillip Hellewell ssh...@gmail.com wrote:
Also, is there a common way to let each developer decide which
protocol they want to use, e.g., svn+ssh:// instead of http://.
Of course, the big problem with svn+ssh:// is that you have to have
the username in the URL too. Is there a varaible, e.g., ${username},
that I can shove in there?
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: overriding inherited properties: what's the semantics?
Also: if overriding inherited properties is a supported concept, it would be cool if maven would follow the lead of good OO programming languages: let the user specify whether a property definition is intended to create a fresh property vs. override an inherited one (think @Override). The enforcer plugin could probably help with that. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven SQL plugin
In this case, I cannot use the fileset as the ordering mechanism is alphabetical. srcFiles seems a good choice however I cannot specify wildcards :( Have you considered simply modifying the Maven SQL plugin to add the functionality you require, and then offering your changes back for inclusion in a future release of the plugin? Adding a feature like you're proposing should be relatively simple, I'd assume. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Archetype] directory-name
Hi all, I want to create an artifact based on an existing project. Unfortunately the names for the directories are a little weird (can't change them, it's naming-convention in my company!). I have the following directories: project-name-app -- the POM-project |-- project-name -- EAR-project |-- project-name-model -- JAR-project |-- project-name-services -- JAR-project \-- project-name-web -- WAR-project Now, I would like to have the project-name set as a variable... Only problem here is that I can't figure out how to (correctly) do this. When I run 'archetype:create-from-project' in interactive-mode, I can tell it the artifactId is 'project-name' instead of 'project-name-app', but this will then make a) the directory 'project-name' as the root of my project and b) have invalid references to parent in the modules... Can anybody help me out on how to get this working? Thanks. -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien E roland.asm...@adesso.at www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how is the archetype-catalog.xml file on central updated?
Thanks for clarifying. On Oct 19, 2010, at 11:10 AM, Juven Xu ju...@sonatype.com wrote: the archetype-catalog.xml is updated every Sunday: https://docs.sonatype.org/display/Repository/Central+Repository+FAQ On Tue, Oct 19, 2010 at 11:00 PM, Justin Edelson justinedel...@gmail.comwrote: Thanks. If I released an archetype via repository.apache.org today, it should be in the central archetype catalog on Sunday? On 10/19/10 10:54 AM, Tamás Cservenák wrote: Hi Justin, he uses a CLI tool not released yet, that actually relies on Index (code lifted to spice and shared from nexus-archetype-plugin): CI deploys of snapshot: https://repository.sonatype.org/content/repositories/snapshots/org/sonatype/spice/nexus-archetype-common/1.1-SNAPSHOT/ Source: https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true https://sventon.sonatype.org/repos/spice/list/trunk/nexus-archetype-common/?revision=HEADbypassEmpty=true So, currently on Central, after reindex, this CLI runs too and generates the catalog from just updated index. Thanks, ~t~ On Tue, Oct 19, 2010 at 4:35 PM, Justin Edelson justinedel...@gmail.com mailto:justinedel...@gmail.com wrote: I saw in ARCHETYPE-242 that Juven fixed the archetype catalog on Central back in April. How is that catalog updated? Thanks, Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto:users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- - juven - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Now seriously: how can I manage dependencies of own projects with maven
stripped On 19 October 2010 16:50, Wayne Fay wayne...@gmail.com wrote: Attached is a sample of how I configure the builders (using update-properties as my inter-module deps are via properties for this uber-integration-project) the principle remains the same Either you failed to attach anything, or it got stripped. Wayne - 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
Possible bug in Subversion SCM or release plugin
Hi all, Both of these point to the same place: My working copy URL: svn+ssh://usern...@addev/svnrep/components/core/trunk My SCM URL in the pom: scm:svn:http://addev/svn/components/core/trunk I'm getting this error when release:prepare tries to create a tag: svn: Server sent unexpected return value (405 Method Not Allowed) in response to PROPFIND request for '/svnrep/components/core/trunk' It should be using /svn not /svnrep, because it is talking to the HTTP server. I sniffed the packets and found that for most of the DAV operations it is using /svn as it should, but for this one where it goes to create the tag, it's using /svnrep. It must be grabbing that name from my local URL, but it shouldn't do that. That path only exists with the ssh protocol, not when talking to the web server. Maven shouldn't mix and match parts of the working copy URL with the SCM url. It should pick one or the other. Should I submit a bug for this? On a related note, why not have the release plugin just use the working copy URL if an scm connection is not defined in the pom? That would solve all of the following issues for me: 1. I wouldn't have to define an scm connection in all my poms and make sure no one ever screws it up. 2. I wouldn't have to worry about some devs wanting to use http:// and some want to use svn+ssh://. 3. I would never run into the bug that this email is about. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Archetype] directory-name
See http://maven.apache.org/archetype/maven-archetype-plugin/examples/create-multi-module-project.html (Hint use __artifactId__) On Tue, Oct 19, 2010 at 2:55 PM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, I want to create an artifact based on an existing project. Unfortunately the names for the directories are a little weird (can't change them, it's naming-convention in my company!). I have the following directories: project-name-app -- the POM-project |-- project-name -- EAR-project |-- project-name-model -- JAR-project |-- project-name-services -- JAR-project \-- project-name-web -- WAR-project Now, I would like to have the project-name set as a variable... Only problem here is that I can't figure out how to (correctly) do this. When I run 'archetype:create-from-project' in interactive-mode, I can tell it the artifactId is 'project-name' instead of 'project-name-app', but this will then make a) the directory 'project-name' as the root of my project and b) have invalid references to parent in the modules... Can anybody help me out on how to get this working? Thanks. -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien E roland.asm...@adesso.at www.adesso.at - business. people. technology. - - 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: Possible bug in Subversion SCM or release plugin
I suspect that this is because you are not using remoteTagging=true for your release, so it is trying to create the tag from the working copy. the pom is not really designed to handle more than two valid scm connection urls (1 is the at least read-only url and the other dev connection is at least read-write) when making a release you really should be using the connection specified in the devConnection part of the scm section. for svn, setting remote tagging to true should work around your issue somewhat. -Stephen On 19 October 2010 23:02, Phillip Hellewell ssh...@gmail.com wrote: Hi all, Both of these point to the same place: My working copy URL: svn+ssh://usern...@addev/svnrep/components/core/trunk My SCM URL in the pom: scm:svn:http://addev/svn/components/core/trunk I'm getting this error when release:prepare tries to create a tag: svn: Server sent unexpected return value (405 Method Not Allowed) in response to PROPFIND request for '/svnrep/components/core/trunk' It should be using /svn not /svnrep, because it is talking to the HTTP server. I sniffed the packets and found that for most of the DAV operations it is using /svn as it should, but for this one where it goes to create the tag, it's using /svnrep. It must be grabbing that name from my local URL, but it shouldn't do that. That path only exists with the ssh protocol, not when talking to the web server. Maven shouldn't mix and match parts of the working copy URL with the SCM url. It should pick one or the other. Should I submit a bug for this? On a related note, why not have the release plugin just use the working copy URL if an scm connection is not defined in the pom? That would solve all of the following issues for me: 1. I wouldn't have to define an scm connection in all my poms and make sure no one ever screws it up. 2. I wouldn't have to worry about some devs wanting to use http:// and some want to use svn+ssh://. 3. I would never run into the bug that this email is about. Phillip - 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: [Archetype] directory-name
I already have the artifact and the modules are generated just fine. It's just the root-directory that I am not content with! I noticed that the m2eclipse-plugin does change some archetypes during generation... Anybody have an idea hoe it does that, because that is what I am looking for! Can be reproduced with the myfaces-archetype-jsfcomponents -- normal Maven generates a directory like your artifactId, m2eclipse generates 'artifactId-project'... On 20-10-10 00:04, Larry Shatzer, Jr. wrote: See http://maven.apache.org/archetype/maven-archetype-plugin/examples/create-multi-module-project.html (Hint use __artifactId__) On Tue, Oct 19, 2010 at 2:55 PM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, I want to create an artifact based on an existing project. Unfortunately the names for the directories are a little weird (can't change them, it's naming-convention in my company!). I have the following directories: project-name-app -- the POM-project |-- project-name -- EAR-project |-- project-name-model -- JAR-project |-- project-name-services -- JAR-project \-- project-name-web -- WAR-project Now, I would like to have the project-name set as a variable... Only problem here is that I can't figure out how to (correctly) do this. When I run 'archetype:create-from-project' in interactive-mode, I can tell it the artifactId is 'project-name' instead of 'project-name-app', but this will then make a) the directory 'project-name' as the root of my project and b) have invalid references to parent in the modules... Can anybody help me out on how to get this working? Thanks. -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien E roland.asm...@adesso.at www.adesso.at - business. people. technology. - - 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 -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien E roland.asm...@adesso.at www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Possible bug in Subversion SCM or release plugin
Thanks Stephen. See comments below... On Tue, Oct 19, 2010 at 4:16 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I suspect that this is because you are not using remoteTagging=true for your release, so it is trying to create the tag from the working copy. Ok, but it still shouldn't use the path from the working copy URL with the protocol from the pom scm connection. the pom is not really designed to handle more than two valid scm connection urls (1 is the at least read-only url and the other dev connection is at least read-write) Unfortunately, half our developers are using http:// and the other half are using svn+ssh://, and I don't see that changing. when making a release you really should be using the connection specified in the devConnection part of the scm section. Sounds kinda like an excuse :) How do you handle this scenario in general? I'm sure many companies out there allow more than one way to access SVN. So you have to make a rule that only developers who check out code with a specific protocol can do releases? for svn, setting remote tagging to true should work around your issue somewhat. Yep, sure enough it that did the trick. Thanks for that workaround! But anyway, should I still submit a bug? I don't know if it is the release plugin or SCM plugin at fault though... Also, what about my idea that the release plugin ought to just use the working copy URL when an scm connection is not defined? Seems like that would really simplify things, and I don't see any downsides. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Compile dependencies and goals
Hi We have just been accepted into the Maven Incubator with our Isis project. As part of setting thing up we have been instructed to parent our parent pom with the apache artifact. Having done this I have noticed an odd behaviour. In the past I have been able to clear out the local repository and run mvn clean compile in our project and it would compile all the code. All the dependent modules within our own project were referenced via the class directories as there were no jars to call on from the local repo. (I am using Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100), on Java version 1.6.0_11 running 64bit Linux.) With the new configuration mvn clean compile now fails while trying to find test dependencies, although it still succeeds in finding the source dependencies. Two things here: 1) why does the old setup only run the compile and not also the testCompile goals; and 2) why is Maven able to deal with the dependencies for the source compiled code but not for the test compiled code. There has been a thread about this on our mailing list which I shall refer you to for more information, see http://www.mail-archive.com/isis-...@incubator.apache.org/msg00255.htm. Thanks in anticipation. Robert Matthews The Apache Isis project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
