Re: maven-surefire-plugin forkMode question
Do you know of any example of using the 'exec plugin from the test phase in the POM '? Currently the workaround I have found is to use the GMaven plugin that deletes the DB. However I don't have known control over when this runs...it just happens to work at the moment. BTW, do non-lifecyle bound plugins run in order they are specified in the pom? -Dave On Thu, Sep 3, 2009 at 11:40 PM, Brett Porter br...@apache.org wrote: On 04/09/2009, at 3:35 PM, David Hoffer wrote: During the setup for the test, actually I do this in the @BeforeClass because its expensive, we make some calls into legacy code that creates db connections. I need to delete the access db after the test but can't because the db connections still exist. So ideally I need some (tearDown) process to come along after each test and do a cleanup. Doing this in the AfterClass would be fine but I can't get it to work...it seems to be the same process as the tests. It is. I think your best alternative is to delete the database using the exec plugin from the test phase in the POM (which will run after the surefire tests have concluded). It also means you don't need to fork multiple JVMs for your tests if you don't want to. - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-surefire-plugin forkMode question
On 04/09/2009, at 4:04 PM, David Hoffer wrote: Do you know of any example of using the 'exec plugin from the test phase in the POM '? Currently the workaround I have found is to use the GMaven plugin that deletes the DB. However I don't have known control over when this runs...it just happens to work at the moment. That's an equivalent solution. Adding phasetest/phase inside that execution is the right place. BTW, do non-lifecyle bound plugins run in order they are specified in the pom? All plugins are lifecycle bound if they are run via the POM. - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: report encoding problem (doxia)
Hi! Mhh.. the code is not accessible, sorry... But my eclipse uses UTF-8, the compiler is configured to use UTF-8... Is there any other way, to check when the String is converted wrong ?! (I think you're right, its before doxia) If there is no other solution, i think the string should be defined in a prop-file... thanks, 2009/9/3 Hervé BOUTEMY herve.bout...@free.fr: Hi, If you're writing your report, ie java code using Doxia API, you're writing Strings, without any encoding notion. Are you sure the content isn't broken before you send it to Doxia? Is your code accessible somewhere? Regards, Hervé Le jeudi 03 septembre 2009, javadevd...@googlemail.com a écrit : Hello! I'm writing my own maven-report plugin, which should create some output. This output is made with doxia, how it's explained in the tutorials. The problems are the german umlauts. I use it directly in the code (as String) to put via doxia into the html-page.(report) But the report don't shows the umlauts correctly. My problem is, that i don't know, where the encoding for doxia can be changed. (because doxia is initialized within the AbstractMavenReport) I'm a little bit confused, because there are a lot of descriptions in the net, that the default encoding is UTF-8 , so that there should be no problem with german umlauts. I have also tried to use the project.reporting.outputEncoding property in the pom, but nothing changes. Are there any experiences with that problem? thanks,,, Dave - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
dependency / version problem
Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) I hope there is any solution for that problem... Thanks if you are a this point! :-) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: M2 site-plugin: Roadmap for 2.2
You really mean 2.2 or 2.1? The roadmap is here: http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel and 2.1 will include doxia 1.1.2. Timeline there is none. You might also have a look at the related Doxia release plan: http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan HTH, -Lukas Bruno Marti wrote: Which is the roadmap/timeline for release 2.2? And will Doxia 1.1.2 be included? http://jira.codehaus.org/browse/MSITE-419 http://jira.codehaus.org/browse/MSITE-419 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
Hi, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 09:38: Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) Maybe you should reconsider your complete approach and start using Maven for the version management instead of managing the versions by exchanging repositories on your own. In this case Maven cannot help you and you already face the problem. See, we use M2 now since years and we're now - compared to your numbering scheme - at V10. However, I don't have to clear my local repo to switch between different code lines. Basically start using a parent POM that is global for your project i.e. every POM of your project will inherit either directly or indirectly from that one. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. That's it. This global POM will define that for your complete project all the used versions everytime. There's no possibility anymore to get suddenly something else and this is completely independent from the stuff in your local repo. I hope there is any solution for that problem... The location of the local repo is defined in the settings.xml. You can use a separate settings.xml, its name and location can be defined from the command line. Thanks if you are a this point! :-) No, I won't get there, because we take a different approach. You should really reconsider yours. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: report encoding problem (doxia)
2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com Hi! Mhh.. the code is not accessible, sorry... But my eclipse uses UTF-8, the compiler is configured to use UTF-8... Is there any other way, to check when the String is converted wrong ?! (I think you're right, its before doxia) If there is no other solution, i think the string should be defined in a prop-file... keeping strings in a properties file is a good practice as it allows for i18n later... just be careful because most people forget that properties files are effectively US-ASCII encoded (OK, so it's actually an 8 bit encoding... but most people get it wrong) and so you have to escape *all* unicode characters above code point 127 as \u -Stephen thanks, 2009/9/3 Hervé BOUTEMY herve.bout...@free.fr: Hi, If you're writing your report, ie java code using Doxia API, you're writing Strings, without any encoding notion. Are you sure the content isn't broken before you send it to Doxia? Is your code accessible somewhere? Regards, Hervé Le jeudi 03 septembre 2009, javadevd...@googlemail.com a écrit : Hello! I'm writing my own maven-report plugin, which should create some output. This output is made with doxia, how it's explained in the tutorials. The problems are the german umlauts. I use it directly in the code (as String) to put via doxia into the html-page.(report) But the report don't shows the umlauts correctly. My problem is, that i don't know, where the encoding for doxia can be changed. (because doxia is initialized within the AbstractMavenReport) I'm a little bit confused, because there are a lot of descriptions in the net, that the default encoding is UTF-8 , so that there should be no problem with german umlauts. I have also tried to use the project.reporting.outputEncoding property in the pom, but nothing changes. Are there any experiences with that problem? thanks,,, Dave - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
Hi! Thanks for the complete answer. I think i described it a bit inconclusive. But the approach you described will also not solve the problem: because: the dependency i described can be transitive! (I dont know every dependency - for example - of spring, so it's impossible for me to check every version-range of every dependency of spring ...) So.. if I have one parent pom for all the different versions of the project, there is still the problem, that some version range in any dependency (like in the sample of my picture) - not defined by myself (a transitive from any third party) - influence all versions!! (because the newest version is used, and the newest version is first searched in the local repo - for all project versions) To define different local repos for every project Version is possible, but then there are some problems with automatic build (after storing changed code) in M2Eclipse, because you cant give maven-parameters with it. I hope it's a bit clearer... thanks 2009/9/4 Jörg Schaible joerg.schai...@gmx.de Hi, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 09:38: Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) Maybe you should reconsider your complete approach and start using Maven for the version management instead of managing the versions by exchanging repositories on your own. In this case Maven cannot help you and you already face the problem. See, we use M2 now since years and we're now - compared to your numbering scheme - at V10. However, I don't have to clear my local repo to switch between different code lines. Basically start using a parent POM that is global for your project i.e. every POM of your project will inherit either directly or indirectly from that one. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. That's it. This global POM will define that for your complete project all the used versions everytime. There's no possibility anymore to get suddenly something else and this is completely independent from the stuff in your local repo. I hope there is any solution for that problem... The location of the local repo is defined in the settings.xml. You can use a separate settings.xml, its name and location can be defined from the command line. Thanks if you are a this point! :-) No, I won't get there, because we take a different approach. You should really reconsider yours. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
1. you refer to a non-existant picture 2. Jorg's solution is the way to go. -Stephen 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com Hi! Thanks for the complete answer. I think i described it a bit inconclusive. But the approach you described will also not solve the problem: because: the dependency i described can be transitive! (I dont know every dependency - for example - of spring, so it's impossible for me to check every version-range of every dependency of spring ...) So.. if I have one parent pom for all the different versions of the project, there is still the problem, that some version range in any dependency (like in the sample of my picture) - not defined by myself (a transitive from any third party) - influence all versions!! (because the newest version is used, and the newest version is first searched in the local repo - for all project versions) To define different local repos for every project Version is possible, but then there are some problems with automatic build (after storing changed code) in M2Eclipse, because you cant give maven-parameters with it. I hope it's a bit clearer... thanks 2009/9/4 Jörg Schaible joerg.schai...@gmx.de Hi, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 09:38: Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) Maybe you should reconsider your complete approach and start using Maven for the version management instead of managing the versions by exchanging repositories on your own. In this case Maven cannot help you and you already face the problem. See, we use M2 now since years and we're now - compared to your numbering scheme - at V10. However, I don't have to clear my local repo to switch between different code lines. Basically start using a parent POM that is global for your project i.e. every POM of your project will inherit either directly or indirectly from that one. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. That's it. This global POM will define that for your complete project all the used versions everytime. There's no possibility anymore to get suddenly something else and this is completely independent from the stuff in your local repo. I hope there is any solution for that problem... The location of the local repo is defined in the settings.xml. You can use a separate settings.xml, its name and location can be defined from the command line. Thanks if you are a this point! :-) No, I won't get there, because we take a different approach. You should really reconsider yours. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:
Apache Continuum 1.3.4 (Beta) Released!
The Apache Continuum team is pleased to announce the release of Apache Continuum 1.3.4 (Beta). Apache Continuum is an enterprise-ready continuous integration server with features such as automated builds, release management, role-based security, and integration with popular build tools and source control management systems. The latest release can be downloaded from: http://continuum.apache.org/download.html For a complete list of changes, please see the release notes: http://continuum.apache.org/docs/1.3.4/release-notes.html If you have any questions, please consult: - the web site: http://continuum.apache.org - the continuum-user mailing list: http://continuum.apache.org/mail-lists.html Enjoy! ~The Apache Continuum Team
Re: dependency / version problem
there is no picture? I added it to the first mail.. and i can see it as an attachment... I try it again with that mail... I already use Maven for complete Version Management. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. And here is the problem. This is not possible because the problem I described is a transitive dependency, I don't know! (Because its in any dependency of another dependency...) So defining fix versions of the first-direct dependency is ok (DEP_A). But if there are dependencies in DEP_A (DEP_A-DEP_B) and DEP_B has some dependeny with open version-ranges (DEP_Copen)... then I cant influence this. And there is suddenly a new version of the dependency (DEP_Copen) used by all versions of my project (V3,V4 etc.).. and then there can be unpredictable bugs... (in an older tested version of my project) I think the picture is very important to understand this use case, so I add it again... thanks... Dave 2009/9/4 Stephen Connolly stephen.alan.conno...@gmail.com 1. you refer to a non-existant picture 2. Jorg's solution is the way to go. -Stephen 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com Hi! Thanks for the complete answer. I think i described it a bit inconclusive. But the approach you described will also not solve the problem: because: the dependency i described can be transitive! (I dont know every dependency - for example - of spring, so it's impossible for me to check every version-range of every dependency of spring ...) So.. if I have one parent pom for all the different versions of the project, there is still the problem, that some version range in any dependency (like in the sample of my picture) - not defined by myself (a transitive from any third party) - influence all versions!! (because the newest version is used, and the newest version is first searched in the local repo - for all project versions) To define different local repos for every project Version is possible, but then there are some problems with automatic build (after storing changed code) in M2Eclipse, because you cant give maven-parameters with it. I hope it's a bit clearer... thanks 2009/9/4 Jörg Schaible joerg.schai...@gmx.de Hi, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 09:38: Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) Maybe you should reconsider your complete approach and start using Maven for the version management instead of managing the versions by exchanging repositories on your own. In this case Maven cannot help you and you already face the problem. See, we use M2 now since years and we're now - compared to your numbering scheme - at V10.
Re: dependency / version problem
2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com there is no picture? I added it to the first mail.. and i can see it as an attachment... I try it again with that mail... I already use Maven for complete Version Management. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. And here is the problem. This is not possible because the problem I described is a transitive dependency, I don't know! (Because its in any dependency of another dependency...) So defining fix versions of the first-direct dependency is ok (DEP_A). But if there are dependencies in DEP_A (DEP_A-DEP_B) and DEP_B has some dependeny with open version-ranges (DEP_Copen)... then I cant influence this. And there is suddenly a new version of the dependency (DEP_Copen) used by all versions of my project (V3,V4 etc.).. and then there can be unpredictable bugs... (in an older tested version of my project) I think the picture is very important to understand this use case, so I add it again... thanks... Dave 2009/9/4 Stephen Connolly stephen.alan.conno...@gmail.com 1. you refer to a non-existant picture 2. Jorg's solution is the way to go. -Stephen 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com Hi! Thanks for the complete answer. I think i described it a bit inconclusive. But the approach you described will also not solve the problem: because: the dependency i described can be transitive! (I dont know every dependency - for example - of spring, so it's impossible for me to check every version-range of every dependency of spring ...) So.. if I have one parent pom for all the different versions of the project, there is still the problem, that some version range in any dependency (like in the sample of my picture) - not defined by myself (a transitive from any third party) - influence all versions!! (because the newest version is used, and the newest version is first searched in the local repo - for all project versions) To define different local repos for every project Version is possible, but then there are some problems with automatic build (after storing changed code) in M2Eclipse, because you cant give maven-parameters with it. I hope it's a bit clearer... thanks 2009/9/4 Jörg Schaible joerg.schai...@gmx.de Hi, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 09:38: Hi all! My problem is not easy to describe :-) But i try it... I have add a picture to this mail, where the situation is painted.. The Situation: There are two versions of my project. - Version 3: This version is in production and has been frozen. (the repository for V3 is offline, that no changes from dependencies can make trouble...) - Version 4: This is the actual developed Version. It usees another remote Repository because some dependencies changed. Using eclipse M2 plugin for developing. The Problem: All dependencies (from V3 and V4) are at the same time in the local repository. And there is one special dependency (can also be transitive) with no fixed version. (red circle in painting) In V4 there was created a new Version for that dependency (from a third party! But i didn't recocnize, because maven fetch it automaticly!!) Now, there is also a new Version of that dependeny in the local repository. Suddenly there should be a bug fixing in V3! (So the frozen version should be used to change something...) But, the changed dependency, described above, is in the local repository and is also be used from V3, what is wrong, because the frozen state used another version! (Another version can have some differences, where the build doesn't break, but some different behaoviours can be in the software... so there are unpredictable bugs!) Some possible solutions, and why they aren't real solutions: 1) clean the local repository before bug fixing V3: To fetch all dependencies from remote Repository V3 needs some time. And the developer must be able to switch beetween V3 and V4 very fast. To clean and reload the local repository is to time-intensive, and if some changes are made in V4, and after that again in V3, the clean should be made again and again 2) change dependencies version-range to one version only: I have to look for all dependencies, transitive dependencies etc. where some version ranges can be defined. This is to much to look for! So... If anythink is not described properly, please ask :-) Maybe you should reconsider your complete approach and start using Maven for the version management instead of managing the versions by exchanging repositories on your own. In this case Maven cannot help you and you already face the problem. See, we use M2
running a single execution goal from command line
My build has a couple of groovy scripts that run before and after
integration tests, setting things up and tearing them down.
plugin
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-plugin/artifactId
version1.0/version
executions
execution
idset-up/id
phasepre-integration-test/phase
goals
goalexecute/goal
/goals
configuration
source${pom.basedir}/src/script/setUp.groovy/source
/configuration
/execution
execution
idtear-down/id
phasepost-integration-test/phase
goals
goalexecute/goal
/goals
configuration
source${pom.basedir}/src/script/tearDown.groovy/source
/configuration
/execution
/executions
/plugin
I want to be able to run just the tear-down execution from the command line
by specifying the execution id. Is this possible? I know that an id of
default-cli is run by default but I can't find any information on specifying
a different id.
Thanks
Jeff
Re: dependency / version problem
Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 10:53: there is no picture? I added it to the first mail.. and i can see it as an attachment... I try it again with that mail... Maybe you did not realize yet, that versions defined in a depMgmt section do always take precedence - even for transitive deps! I already use Maven for complete Version Management. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. And here is the problem. This is not possible because the problem I described is a transitive dependency, I don't know! (Because its in any dependency of another dependency...) So defining fix versions of the first-direct dependency is ok (DEP_A). But if there are dependencies in DEP_A (DEP_A-DEP_B) and DEP_B has some dependeny with open version-ranges (DEP_Copen)... then I cant influence this. And there is suddenly a new version of the dependency (DEP_Copen) used by all versions of my project (V3,V4 etc.).. and then there can be unpredictable bugs... (in an older tested version of my project) I think the picture is very important to understand this use case, so I add it again... That's the whole point, the problem you describe in your use case does not exist in this way. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
But all you described implies, that I know about this dependency. But I dont know the dependency, it can happen in any transitive dependency. Because attachements are not shown, i loaded the image to http://goliatmesh.go.funpic.de/mavenDependencyProblem.jpg Perhaps there is really something I didn't figure out, but I had a problem, similar to this already :-( thanks... 2009/9/4 Jörg Schaible joerg.schai...@gmx.de Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 10:53: there is no picture? I added it to the first mail.. and i can see it as an attachment... I try it again with that mail... Maybe you did not realize yet, that versions defined in a depMgmt section do always take precedence - even for transitive deps! I already use Maven for complete Version Management. Use in this global POM a dependencyMgmt section and define there all your deps with fix versions. And here is the problem. This is not possible because the problem I described is a transitive dependency, I don't know! (Because its in any dependency of another dependency...) So defining fix versions of the first-direct dependency is ok (DEP_A). But if there are dependencies in DEP_A (DEP_A-DEP_B) and DEP_B has some dependeny with open version-ranges (DEP_Copen)... then I cant influence this. And there is suddenly a new version of the dependency (DEP_Copen) used by all versions of my project (V3,V4 etc.).. and then there can be unpredictable bugs... (in an older tested version of my project) I think the picture is very important to understand this use case, so I add it again... That's the whole point, the problem you describe in your use case does not exist in this way. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: M2 site-plugin: Roadmap for 2.2
Oops, sorry meant 2.1. Hope it coming soon ltheussl wrote: You really mean 2.2 or 2.1? The roadmap is here: http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel and 2.1 will include doxia 1.1.2. Timeline there is none. You might also have a look at the related Doxia release plan: http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan HTH, -Lukas Bruno Marti wrote: Which is the roadmap/timeline for release 2.2? And will Doxia 1.1.2 be included? http://jira.codehaus.org/browse/MSITE-419 http://jira.codehaus.org/browse/MSITE-419 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/M2-site-plugin%3A-Roadmap-for-2.2-tp25270282p25291423.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: dependency / version problem
Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 11:25: But all you described implies, that I know about this dependency. But I dont know the dependency, it can happen in any transitive dependency. If you use fix versions for your dependencies in the depMgmt section, it is no longer possible to introduce new/other transitive dependencies, because this implies that at least one of the fix versions must have been changed. Because attachements are not shown, i loaded the image to http://goliatmesh.go.funpic.de/mavenDependencyProblem.jpg Perhaps there is really something I didn't figure out, but I had a problem, similar to this already :-( If your global project POM declares a group:b:1.1.4 in the depMgmt section, nothing else will be used - never. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
sorry, that i'm so annoying ;-) because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. U say, that this use case will neber happen? So Maven ignores version Range from DEP_B:2.3 to DEP_C ? If this is right, than thanks for all the comments ;-) And the my use case is really impossible... dave
Re: dependency / version problem
2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com: sorry, that i'm so annoying ;-) because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. As long as your project depends on A:1.0, B:2.3 and C:1.0 will be transitive dependencies. If C comes in a new version 1.1, your project will still get C:1.0 as a transitive dependency. If B wants to use C:1.1, B will come in a new version, say 2.4 that depends on C:1.1. The only way for your project to be affected by the release of C:1.1 is that A has a new release that depends on B:2.4, and your project is updated to depend on this new version of A. Do you understand the picture? -ketil - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
DepB should not use a range, or else you should lock down depC in your parent pom to a fixed version. if your dependency: dep A has a fixed dependency on depB, then depB cannot change, so you can sigure out all your current dependencies (dependency:tree is your friend) All you do is before you release, you add a depMgnt section locking down the versions to the versions currently displayed using dependency:tree. Now everything is locked down and no new transitive deps can be added 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com sorry, that i'm so annoying ;-) because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. U say, that this use case will neber happen? So Maven ignores version Range from DEP_B:2.3 to DEP_C ? If this is right, than thanks for all the comments ;-) And the my use case is really impossible... dave
Re: dependency / version problem
Some help is available: http://mojo.codehaus.org/versions-maven-plugin/resolve-ranges-mojo.html Just prior to doing a release, you will do the following: mvn versions:resolve-ranges This will turn all the ranges into the current version (it does not handle transitive... but if you file a JIRA, we can see about adding support in a later release) That will at least help somewhat. Then you use dependency:tree to find any extra transitives, and add those into your dependencyMgnt section... -Stephen 2009/9/4 Ketil Aasarød ketil.aasa...@gmail.com 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com: sorry, that i'm so annoying ;-) because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. As long as your project depends on A:1.0, B:2.3 and C:1.0 will be transitive dependencies. If C comes in a new version 1.1, your project will still get C:1.0 as a transitive dependency. If B wants to use C:1.1, B will come in a new version, say 2.4 that depends on C:1.1. The only way for your project to be affected by the release of C:1.1 is that A has a new release that depends on B:2.4, and your project is updated to depend on this new version of A. Do you understand the picture? -ketil - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
Sorry for overlooking the version range for dep C in my earlier post. Stephen is right. You should lock down the version of C from your pom using dependencyManagement. -ketil 2009/9/4 Stephen Connolly stephen.alan.conno...@gmail.com: Some help is available: http://mojo.codehaus.org/versions-maven-plugin/resolve-ranges-mojo.html Just prior to doing a release, you will do the following: mvn versions:resolve-ranges This will turn all the ranges into the current version (it does not handle transitive... but if you file a JIRA, we can see about adding support in a later release) That will at least help somewhat. Then you use dependency:tree to find any extra transitives, and add those into your dependencyMgnt section... -Stephen 2009/9/4 Ketil Aasarød ketil.aasa...@gmail.com 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com: sorry, that i'm so annoying ;-) because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. As long as your project depends on A:1.0, B:2.3 and C:1.0 will be transitive dependencies. If C comes in a new version 1.1, your project will still get C:1.0 as a transitive dependency. If B wants to use C:1.1, B will come in a new version, say 2.4 that depends on C:1.1. The only way for your project to be affected by the release of C:1.1 is that A has a new release that depends on B:2.4, and your project is updated to depend on this new version of A. Do you understand the picture? -ketil - 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 to site:deploy to multiple urls?
I have tried your suggestion but it didn't work.Maybe i have done something wrong? My pom.xml. profile idprofile1/id distributionManagement site idid1/id namename1/name urlurl1/url /site /distributionManagement build plugins plugin artifactIdmaven-deploy-plugin/artifactId executions execution idsend-to-second-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration altDeploymentRepository idid2/id namename2/name urlurl2/url /altDeploymentRepository altDeploymentRepository idid3/id namename3/name urlurl3/url /altDeploymentRepository /configuration /execution /executions /plugin i execute mvn site site:deploy -P profile1 end it deploys the site to only url1(defined in distributionManagement)What am i doing wrong? Stephen Connolly-2 wrote: multiple executions of deploy:deploy bound to the deploy phase. plugin artifactIdmaven-deploy-plugin/artifactId executions execution idsend-to-second-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration *altDeploymentRepository*/*altDeploymentRepository* /configuration /execution execution idsend-to-third-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration *altDeploymentRepository*/*altDeploymentRepository* /configuration /execution /executions /plugin 2009/9/3 Caner Kaplıca caner.kapl...@yapikredi.com.tr Hi, I want to deploy(site:deploy) a site to two different places(url).I couldnt manage it with muliple profiles.Every profile has its own distributionManagement,but maven uses only one of them and deploys the site to that url.Also maven doesnt allow to use multiple url tags in site element or multiple site in distributionManagement.How can i achieve this?Any idea is appreciated.. Thanks in advance, -- View this message in context: http://www.nabble.com/How-to-site%3Adeploy-to-multiple-urls--tp25271071p25292662.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: How to site:deploy to multiple urls?
I want to execute only one command.eg. mvn site site:deploy -P profile1,profile2.The configurations for the site plugin are in profile1 and an alternative url is in profile2.Is there a way to achieve that? Anders Hammar wrote: Why didn't it work with profiles? Did you specify the profile (id) on the command line? I don't understand why that wouldn't work; Maven should use the url defined in the profile being used. However, you need to run the deploy twice; once with each profile: mvn site:deploy -Pprofile1 mvn site:deploy -Pprofile2 /Anders On Thu, Sep 3, 2009 at 09:18, canerK canerkapl...@gmail.com wrote: Hi, I want to deploy(site:deploy) a site to two different places(url).I couldnt manage it with muliple profiles.Every profile has its own distributionManagement,but maven uses only one of them and deploys the site to that url.Also maven doesnt allow to use multiple url tags in site element or multiple site in distributionManagement.How can i achieve this?Any idea is appreciated.. Thanks in advance, -- View this message in context: http://www.nabble.com/How-to-site%3Adeploy-to-multiple-urls--tp25270953p25270953.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 -- View this message in context: http://www.nabble.com/How-to-site%3Adeploy-to-multiple-urls--tp25270953p25292713.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: How to site:deploy to multiple urls?
ahh site:deploy then you are S.O.o.L. by my reading file a JIRA against m-s-p I thought you were after deploy:deploy -Stephen 2009/9/4 canerK canerkapl...@gmail.com I have tried your suggestion but it didn't work.Maybe i have done something wrong? My pom.xml. profile idprofile1/id distributionManagement site idid1/id namename1/name urlurl1/url /site /distributionManagement build plugins plugin artifactIdmaven-deploy-plugin/artifactId executions execution idsend-to-second-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration altDeploymentRepository idid2/id namename2/name urlurl2/url /altDeploymentRepository altDeploymentRepository idid3/id namename3/name urlurl3/url /altDeploymentRepository /configuration /execution /executions /plugin i execute mvn site site:deploy -P profile1 end it deploys the site to only url1(defined in distributionManagement)What am i doing wrong? Stephen Connolly-2 wrote: multiple executions of deploy:deploy bound to the deploy phase. plugin artifactIdmaven-deploy-plugin/artifactId executions execution idsend-to-second-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration *altDeploymentRepository*/*altDeploymentRepository* /configuration /execution execution idsend-to-third-repo/id phasedeploy/phase goals goaldeploy/goal /goals configuration *altDeploymentRepository*/*altDeploymentRepository* /configuration /execution /executions /plugin 2009/9/3 Caner Kaplıca caner.kapl...@yapikredi.com.tr Hi, I want to deploy(site:deploy) a site to two different places(url).I couldnt manage it with muliple profiles.Every profile has its own distributionManagement,but maven uses only one of them and deploys the site to that url.Also maven doesnt allow to use multiple url tags in site element or multiple site in distributionManagement.How can i achieve this?Any idea is appreciated.. Thanks in advance, -- View this message in context: http://www.nabble.com/How-to-site%3Adeploy-to-multiple-urls--tp25271071p25292662.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: confirm unsubscribe from users@maven.apache.org
On Friday 04 September 2009, users-h...@maven.apache.org wrote: Hi! This is the ezmlm program. I'm managing the users@maven.apache.org mailing list. I'm working for my owner, who can be reached at users-ow...@maven.apache.org. To confirm that you would like david.goodeno...@btconnect.com removed from the users mailing list, please send a short reply to this address: users-uc.1252064798.apgbojikebpmopegchol-david.goodenough=btconnect@mav en.apache.org Usually, this happens when you just hit the reply button. If this does not work, simply copy the address and paste it into the To: field of a new message. or click here: mailto:users-uc.1252064798.apgbojikebpmopegchol-david.goodenough=btconnect @maven.apache.org I haven't checked whether your address is currently on the mailing list. To see what address you used to subscribe, look at the messages you are receiving from the mailing list. Each message has your address hidden inside its return path; for example, m...@xdd.ff.com receives messages with return path: users-return-number-mary=xdd.ff@maven.apache.org. Some mail programs are broken and cannot handle long addresses. If you cannot reply to this request, instead send a message to users-requ...@maven.apache.org and put the entire address listed above into the Subject: line. --- Administrative commands for the users list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: users-subscr...@maven.apache.org To remove your address from the list, send a message to: users-unsubscr...@maven.apache.org Send mail to the following for info and FAQ for this list: users-i...@maven.apache.org users-...@maven.apache.org Similar addresses exist for the digest list: users-digest-subscr...@maven.apache.org users-digest-unsubscr...@maven.apache.org To get messages 123 through 145 (a maximum of 100 per request), mail: users-get.123_...@maven.apache.org To get an index with subject and author for messages 123-456 , mail: users-index.123_...@maven.apache.org They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send a short message to: users-thread.12...@maven.apache.org The messages should contain one line or word of text to avoid being treated as s...@m, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example j...@host.domain, just add a hyphen and your address (with '=' instead of '@') after the command word: users-subscribe-john=host.dom...@maven.apache.org To stop subscription for this address, mail: users-unsubscribe-john=host.dom...@maven.apache.org In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at users-ow...@maven.apache.org. Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: david.goodeno...@btconnect.com Received: (qmail 22650 invoked by uid 99); 4 Sep 2009 11:46:37 - Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 11:46:37 + X-ASF-Spam-Status: No, hits=-0.8 required=10.0 tests=ASF_LIST_OPS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [77.75.108.10] (HELO mail.ukfsn.org) (77.75.108.10) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2009 11:46:27 + Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 30E6BDF081 for users-unsubscr...@maven.apache.org; Fri, 4 Sep 2009 12:46:09 +0100 (BST) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id mKNX0xQi0DFg for users-unsubscr...@maven.apache.org; Fri, 4 Sep 2009 12:46:06 +0100 (BST) Received: from stargate.dga.co.uk (unknown [84.45.236.142]) by mail.ukfsn.org (Postfix) with ESMTP id 10DC5DF080 for users-unsubscr...@maven.apache.org; Fri, 4 Sep 2009 12:46:09 +0100 (BST) From: David Goodenough david.goodeno...@btconnect.com To: users-unsubscr...@maven.apache.org Subject: unsubscribe Date: Fri, 4 Sep 2009 12:46:00 +0100 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: 200909041246.03056.david.goodeno...@btconnect.com X-Virus-Checked: Checked by ClamAV
[ANNOUNCEMENT] - Taglist Maven Plugin 2.4 released
The Taglist Maven Plugin team is pleased to announce the taglist-maven-plugin-2.4 release! Produce a tag list report. Changes in this version include: New features: o either support ignoring of casing for tags or implement tag-classes (clusters) Issue: MTAGLIST-15. Fixed Bugs: o XML report created with wrong encoding Issue: MTAGLIST-40. o Code links are all to xref-test Issue: MTAGLIST-32. Changes: o Possibility to exclude unit tests Issue: MTAGLIST-41. For a manual installation, you can download the taglist-maven-plugin-2.4 here: http://mojo.codehaus.org/taglist-maven-plugin Have fun! -Taglist Maven Plugin team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependency / version problem
Hi Dave, javadevd...@googlemail.com wrote at Freitag, 4. September 2009 12:10: sorry, that i'm so annoying ;-) Hehehe .. because this implies that at least one of the fix versions must have been changed. Thats not right (I think). Example: My dependency: DEP_A:1.0 Dependency of DEP_A = DEP_B:2.3 Dependency of DEP_B:2.3 = DEP_C:[1.0,) My dependency is fixed, and nothing changed. Some day, there is a new Version of DEP_C, so DEP_B:2.3 use this new version, because the dependency allows newer versions. U say, that this use case will neber happen? So Maven ignores version Range from DEP_B:2.3 to DEP_C ? No, because DEP_C has not been fixed in fist place. If this is right, than thanks for all the comments ;-) And the my use case is really impossible... Rule of thumb: All dependencies that end up somewhere in a war, ear or assembly should have been locked down in the project's global POM. As Stephen already suggested, use dependency:tree to get the current versions in use. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-surefire-plugin forkMode question
Do you know of a way, using gmaven, to drop a folder containing files and/or subfolders? Currently I consider my solution to be a hack because its bad enough that the logic of what to cleanup is not in the test case source file, but when I have to manually specify each and every file to delete it's a hack. This will never stay in sync over time. If I could put all my temp test files/folders in a folder called 'tmp' and then just drop 'tmp' using gmaven that's less of a hack. You are right on the lifecyle, I forgot that I had set a phase...I'll change it to 'test'. I always get confused on this issue...do plugins ALWAYS run AFTER the phase they are attached to? -Dave On Fri, Sep 4, 2009 at 12:14 AM, Brett Porter br...@apache.org wrote: On 04/09/2009, at 4:04 PM, David Hoffer wrote: Do you know of any example of using the 'exec plugin from the test phase in the POM '? Currently the workaround I have found is to use the GMaven plugin that deletes the DB. However I don't have known control over when this runs...it just happens to work at the moment. That's an equivalent solution. Adding phasetest/phase inside that execution is the right place. BTW, do non-lifecyle bound plugins run in order they are specified in the pom? All plugins are lifecycle bound if they are run via the POM. - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-surefire-plugin forkMode question
On 04/09/2009, at 11:33 PM, David Hoffer wrote: Do you know of a way, using gmaven, to drop a folder containing files and/or subfolders? Currently I consider my solution to be a hack because its bad enough that the logic of what to cleanup is not in the test case source file, but when I have to manually specify each and every file to delete it's a hack. This will never stay in sync over time. If I could put all my temp test files/folders in a folder called 'tmp' and then just drop 'tmp' using gmaven that's less of a hack. I think you'd be better off configuring an instance of the clean plugin instead of gmaven if all you want to do is delete a directory. It can take an arbitrary set of files / directories to clean. You are right on the lifecyle, I forgot that I had set a phase...I'll change it to 'test'. I always get confused on this issue...do plugins ALWAYS run AFTER the phase they are attached to? No, they run in that phase, but are added after any already specified (so after anything built in). - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-compiler-plugin does not exist or no valid version could be found
Thanks Mick
That was the correct answer
--
Peter Pilgrim | E-Channel Services Technical Lead, Products Markets
Lloyds TSB Bank plc, Corporate Markets, 10 Gresham Street, London, EC2V
7AE, UK
' +44 (0)207 158 6135 | ( +44 (0)1234 567 8901
+ peter.pilg...@lloydstsb.co.uk
: www.lloydstsbcorporatemarkets.com
-Original Message-
From: mknut...@baselogic.com [mailto:mknut...@baselogic.com] On Behalf
Of
Mick Knutson
Sent: 03 September 2009 13:24
To: Maven Users List
Subject: Re: maven-compiler-plugin does not exist or no valid version
could be found
The skin error is from the site.xml as it needs the specific skin you
plan
to use:
project name=FedEx Ground ${project.version}
bannerRight
srchttp://baselogic.com/images/blinc-maven.png/src
hrefhttp://baselogic.com/href
/bannerRight
poweredBy
logo name=BLiNC href=http://baselogic.com/;
img=http://baselogic.com/images/pb-blinc-maven.png/
/poweredBy
publishDate format=dd MMM /
*skin
groupIdorg.apache.tapestry/groupId
artifactIdmaven-skin/artifactId
version1.1/version
/skin*
body
---
Thank You...
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Thu, Sep 3, 2009 at 8:19 AM, Pilgrim, Peter
peter.pilg...@lloydsbanking.com wrote:
Partially solved the problem
I building an internal repository behind the firewall and therefore
the
artefacts in the POM must be explicitly versioned. I had to add an
explicit version into the POM build and report sections.
Now I have a different error, where the maven-site-plugin attempts
to
find the skin.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] SiteToolException: ArtifactNotFoundException: The skin does
not
exist: Unable to determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file
there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
org.apache.maven.skins:maven-default-skin:jar:RELEASE
How do I specify the skins in the POM file?
How do INTERNAL REPOSITORY MAINTAINERS solve this problem of the
version
being the latest release of X?
--
Peter Pilgrim | E-Channel Services Technical Lead, Products
Markets
Lloyds TSB Bank plc, Corporate Markets, 10 Gresham Street, London,
EC2V
7AE, UK
' +44 (0)207 158 6135 | ( +44 (0)1234 567 8901
+ peter.pilg...@lloydstsb.co.uk
: www.lloydstsbcorporatemarkets.com
-Original Message-
From: Pilgrim, Peter [mailto:peter.pilg...@lloydsbanking.com]
Sent: 03 September 2009 13:06
To: Maven Users List
Subject: maven-compiler-plugin does not exist or no valid version
could be
found
Hi All
I am attempting to fix a Hudson build failure with Maven.
Now on my workstation I can type mvn site:stage and the whole
project.
However, when I use PuTTY in order to remote into Hudson UNIX
server
and
manually invoke the same command, I get a failure.
[INFO]
[INFO] Building BOS Summit DealPublisher MASTER project
[INFO]task-segment: [site:stage]
[INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin'
does
not exist or no valid version could be found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-compiler-plugin' does not exist or
no
valid version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(D
efaultLifecycleExecutor.java:1651)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReportExecutions(
Re: Overriding the property value in child pom.xml
The problem is that this version isn't being passed to the forked
execution of Maven that is actually performing the release. There is a
way to do that, I'll have to look it up, but generally you would be
better off with your source representing what you intend to release,
and only have the command line overrides for one-offs in development.
Otherwise your tag represents something other than what you released.
A big problem in my book...
Here's how you pass options to the forked build during perform:
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments
On Thu, Sep 3, 2009 at 1:39 PM, arulanandarulanan...@gmail.com wrote:
I am overriding from the command prompt using -Dtest.version=5
Jim Sellers wrote:
How are you overriding it? With
-Dtest.version=5
?
I'm assuming that you don't have that value in your settings.xml file.
Are you getting the correct dependency when you run:
mvn help:effective-pom -Dtest.version=5
Jim
On Wed, Sep 2, 2009 at 2:45 PM, Arul Anand S P
arulanan...@gmail.comwrote:
hi all,
I am having a property named test.version in parent pom.xml
properties
test.version8/test.version
/properties
and I have a the below entry in child pom.xml
dependencies
dependency
groupIdcom.test.data/groupId
artifactIdUtilLibrary/artifactId
version${test.version}/version
/dependency
/dependencies
While executing the release:prepare from the command prompt I am
over-riding
the value of the property test.version to 5
But the child pom.xml still takes the value 8 instead of 5 and is trying
to
download the file UtilLibrary-8.jar instead of UtilLibrary-5.jar
Please help in resolving this
--
View this message in context:
http://www.nabble.com/Overriding-the-property-value-in-child-pom.xml-tp25271120p25280841.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
Cyclic reference error when building my plugin
I am working on a project where a number of different groups are writing Mule
applications that are being managed by Maven. So we have created a large
parent POM with all of the Mule dependencies that each project POM is
supposed to inherit from. So far so good.
I am writing a new Maven plugin that automates part of the deployment to
production process. Each Mule project is supposed to use this plugin, so I
have put it as a dependency in the large parent POM. This also works, and
the projects can use the plugin.
The problem I have run into is that now that I have put the plugin
dependency in the parent POM, I can not longer build my plugin. The plugin
POM also refers to the parent POM, and I end up with a cyclic reference:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.travelport.esb.esb-p.maven-plugins:maven-store-plugin'}'
and
'Vertex{label='com.travelport.esb.esb-p.maven-plugins:maven-store-plugin'}'
introduces to cycle in the graph
com.travelport.esb.esb-p.maven-plugins:maven-store-plugin --
com.travelport.esb.esb-p.maven-plugins:maven-store-plugin
I have checked the documentation and online posts, and cannot find a way to
remove the plugin dependency in my plugin POM. The docs seem to imply that
this can be done, but I cannot see how.
Does anyone know of a way to do this, or do I just need to remove the plugin
dependency from the parent POM, and have each project add it to their own?
Thanks
Chris Pabst
--
View this message in context:
http://www.nabble.com/Cyclic-reference-error-when-building-my-plugin-tp25298551p25298551.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: Need a separate jar from war in assembly
This is still a problem. Still not working. Clues anyone? On Mon, Aug 31, 2009 at 10:50 AM, Jim Collingsjlistn...@gmail.com wrote: BTW, I've tried this by using a dependancySet in the descriptor. This didn't work out. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Overriding the property value in child pom.xml
Actually I am doing the same way by calling
mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:clean
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
-Dtest.version=5
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform
-DdryRun=true -Dtest.version=5
But it doesnot work
BRIAN FOX-5 wrote:
The problem is that this version isn't being passed to the forked
execution of Maven that is actually performing the release. There is a
way to do that, I'll have to look it up, but generally you would be
better off with your source representing what you intend to release,
and only have the command line overrides for one-offs in development.
Otherwise your tag represents something other than what you released.
A big problem in my book...
Here's how you pass options to the forked build during perform:
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments
On Thu, Sep 3, 2009 at 1:39 PM, arulanandarulanan...@gmail.com wrote:
I am overriding from the command prompt using -Dtest.version=5
Jim Sellers wrote:
How are you overriding it? With
-Dtest.version=5
?
I'm assuming that you don't have that value in your settings.xml file.
Are you getting the correct dependency when you run:
mvn help:effective-pom -Dtest.version=5
Jim
On Wed, Sep 2, 2009 at 2:45 PM, Arul Anand S P
arulanan...@gmail.comwrote:
hi all,
I am having a property named test.version in parent pom.xml
properties
test.version8/test.version
/properties
and I have a the below entry in child pom.xml
dependencies
dependency
groupIdcom.test.data/groupId
artifactIdUtilLibrary/artifactId
version${test.version}/version
/dependency
/dependencies
While executing the release:prepare from the command prompt I am
over-riding
the value of the property test.version to 5
But the child pom.xml still takes the value 8 instead of 5 and is
trying
to
download the file UtilLibrary-8.jar instead of UtilLibrary-5.jar
Please help in resolving this
--
View this message in context:
http://www.nabble.com/Overriding-the-property-value-in-child-pom.xml-tp25271120p25280841.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
--
View this message in context:
http://www.nabble.com/Overriding-the-property-value-in-child-pom.xml-tp25271120p25299605.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: Overriding the property value in child pom.xml
Actually I am doing the same way by calling
mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:clean
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
-Dtest.version=5
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform
-DdryRun=true -Dtest.version=5
But it doesnot work
Below is how my actual pom.xml look like
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdtest/artifactId
groupIdcom.test/groupId
version2.1-SNAPSHOT/version
relativePath../pom.xml/relativePath
/parent
modelVersion4.0.0/modelVersion
groupIdcom.test.data/groupId
artifactIdDataManager/artifactId
nameData Manager/name
version2.1-SNAPSHOT/version
description /
scm
urlhttp://hostname/test/trunk/DataManager/url
connectionscm:svn:https://hostname/test/trunk/DataManager/connection
developerConnectionscm:svn:https://hostname/test/trunk/DataManager/developerConnection
/scm
dependencies
dependency
groupIdcom.test.data/groupId
artifactIdUtilLib/artifactId
version${test.version}/version
/dependency
/dependencies
/project
Parent pom.xml is given below
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.test/groupId
artifactIdtest/artifactId
packagingpom/packaging
nameTest/name
version2.1-SNAPSHOT/version
properties
test.version1.0-SNAPSHOT/test.version
/properties
modules
moduleDataManager/module
/modules
scm
urlhttp://hostname/test/trunk/url
connectionscm:svn:https://hostname/test/trunk/connection
developerConnectionscm:svn:https://hostname/test/trunk/developerConnection
/scm
/project
BRIAN FOX-5 wrote:
The problem is that this version isn't being passed to the forked
execution of Maven that is actually performing the release. There is a
way to do that, I'll have to look it up, but generally you would be
better off with your source representing what you intend to release,
and only have the command line overrides for one-offs in development.
Otherwise your tag represents something other than what you released.
A big problem in my book...
Here's how you pass options to the forked build during perform:
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments
On Thu, Sep 3, 2009 at 1:39 PM, arulanandarulanan...@gmail.com wrote:
I am overriding from the command prompt using -Dtest.version=5
Jim Sellers wrote:
How are you overriding it? With
-Dtest.version=5
?
I'm assuming that you don't have that value in your settings.xml file.
Are you getting the correct dependency when you run:
mvn help:effective-pom -Dtest.version=5
Jim
On Wed, Sep 2, 2009 at 2:45 PM, Arul Anand S P
arulanan...@gmail.comwrote:
hi all,
I am having a property named test.version in parent pom.xml
properties
test.version8/test.version
/properties
and I have a the below entry in child pom.xml
dependencies
dependency
groupIdcom.test.data/groupId
artifactIdUtilLibrary/artifactId
version${test.version}/version
/dependency
/dependencies
While executing the release:prepare from the command prompt I am
over-riding
the value of the property test.version to 5
But the child pom.xml still takes the value 8 instead of 5 and is
trying
to
download the file UtilLibrary-8.jar instead of UtilLibrary-5.jar
Please help in resolving this
--
View this message in context:
http://www.nabble.com/Overriding-the-property-value-in-child-pom.xml-tp25271120p25280841.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
--
View this message in context:
http://www.nabble.com/Overriding-the-property-value-in-child-pom.xml-tp25271120p25299898.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: Need a separate jar from war in assembly
So, the recommended way is to have something like this, correct? xx-weblogic (all code for web-application) xx-webapp (the actual war, containing src/main/webapp, src/main/resources, but no src/main. Code is really included though .jar files in lib). I've created a xx-weblogic module. That part was easy. Problem is that there is no lib dir. Maven doesn't copy libs to the source tree in accordance with the idea that they should not be in the version control system. So the question remains... how do I get the jar from the repository and into the assembly? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Getting a jar from a repo directly to an assembly?
Is there any way to do this? The jar in question is not part of my build but is part of my assembly as it needs to be installed into the web container by the installation script. I've had one suggestion so far that I should create a separate module for getting the jar but I'll need more details. The jar is never downloaded and after all why would it be? There isn't any code in the module in question. It just makes an empty jar file. It has a pom and a manifest and that's it. Clues? Pontifications? Explanations? Remonstrations? or dare I posit... Combinations? ;-) Jim C. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
JUG Switzerland: Next Generation Development Infrastructure: Maven, M2Eclipse, Nexus Hudson
For those interested I'll be talking about Maven, M2Eclipse, Nexus and Hudson at the JUG Switzerland on Thursday, September 17th: http://www.jugs.ch/html/events/2009/maven_3.0.html?by=JUGS%20mailing#Formular Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3.0 @ JavaZone
Norway has always been a big supporter of Maven (I'm sorry about Maven 1.x) and so it's the first place that I'm going to give a talk on Maven 3.0. If you're going to JavaZone you might want to check it out: http://javazone.no/incogito09/events/JavaZone%202009/sessions/Maven%20Reloaded Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting a jar from a repo directly to an assembly?
On Fri, Sep 4, 2009 at 12:02 PM, Jim Collingsjlistn...@gmail.com wrote: Is there any way to do this? The jar in question is not part of my build but is part of my assembly as it needs to be installed into the web container by the installation script. I've had one suggestion so far that I should create a separate module for getting the jar but I'll need more details. The jar is never downloaded and after all why would it be? There isn't any code in the module in question. It just makes an empty jar file. It has a pom and a manifest and that's it. Add this jar as a dependency of the separate module that builds your assembly. The packaging of this module would be 'pom'. Maven should resolve the dependencies and download it for you, and you can include it in your assembly. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-surefire-plugin forkMode question
Using the clean plugin does seem much better but I could not find any docs on how to drop a folder only files in a folder. -Dave On Fri, Sep 4, 2009 at 7:44 AM, Brett Porter br...@apache.org wrote: On 04/09/2009, at 11:33 PM, David Hoffer wrote: Do you know of a way, using gmaven, to drop a folder containing files and/or subfolders? Currently I consider my solution to be a hack because its bad enough that the logic of what to cleanup is not in the test case source file, but when I have to manually specify each and every file to delete it's a hack. This will never stay in sync over time. If I could put all my temp test files/folders in a folder called 'tmp' and then just drop 'tmp' using gmaven that's less of a hack. I think you'd be better off configuring an instance of the clean plugin instead of gmaven if all you want to do is delete a directory. It can take an arbitrary set of files / directories to clean. You are right on the lifecyle, I forgot that I had set a phase...I'll change it to 'test'. I always get confused on this issue...do plugins ALWAYS run AFTER the phase they are attached to? No, they run in that phase, but are added after any already specified (so after anything built in). - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Questions about dependencies and artifact publication
Hi, I am a newbie to Maven and I have questions about dependencies and artifact publication. Let's imagine I work for www.mycompany.com. Let's imagine I develop two projects A and B. B has a dependency on A. Let's imagine I want to publish the jars for project A and project B in www.mycompany.com/myprojects. i) Is is correct to define the coordinates of Project A as following? groupIdcom.mycompany/groupId artifactIdProjectA/artifactId version1.2/version or should it be groupIdcom.mycompany.myprojects/groupId artifactIdProjectA/artifactId version1.2/version ? By default, the ProjectA-1.2.jar artifact will be created in \ProjectA\target. ii) Should I copy this jar under: www.mycompany.com/myprojects/ or www.mycompany.com/myprojects/ProjectA-1.2/ or www.mycompany.com/myprojects/ProjectA/1.2/ ? iii) How should I declare the dependency in my project B? Should I do it like this? dependencies dependency groupIdcom.mycompany/groupId artifactIdProjectA/artifactId version1.2/version /dependency /dependencies or like this? dependencies dependency groupIdmyprojects.com.mycompany/groupId artifactIdProjectA/artifactId version1.2/version /dependency /dependencies iv) Do I need to include the following in Project B's pom.xml? repositories repository idmy-repository/id urlhttp://www.mycompany.com/url /repository /repositories or eventually this repositories repository idmy-repository/id urlhttp://www.mycompany.com/myprojects/url /repository /repositories ? What are the best practices? Thanks, UseTheFork -- View this message in context: http://www.nabble.com/Questions-about-dependencies-and-artifact-publication-tp25300769p25300769.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: report encoding problem (doxia)
But my eclipse uses UTF-8, the compiler is configured to use UTF-8... you mean you configured maven-compiler-plugin encoding parameter in your pom.xml? AFAIK, it works. There must be a simple info missing, but without seeing anything from your sources and pom.xml, it's hard to find :) Hervé Le vendredi 04 septembre 2009, Stephen Connolly a écrit : 2009/9/4 javadevd...@googlemail.com javadevd...@googlemail.com Hi! Mhh.. the code is not accessible, sorry... But my eclipse uses UTF-8, the compiler is configured to use UTF-8... Is there any other way, to check when the String is converted wrong ?! (I think you're right, its before doxia) If there is no other solution, i think the string should be defined in a prop-file... keeping strings in a properties file is a good practice as it allows for i18n later... just be careful because most people forget that properties files are effectively US-ASCII encoded (OK, so it's actually an 8 bit encoding... but most people get it wrong) and so you have to escape *all* unicode characters above code point 127 as \u -Stephen thanks, 2009/9/3 Hervé BOUTEMY herve.bout...@free.fr: Hi, If you're writing your report, ie java code using Doxia API, you're writing Strings, without any encoding notion. Are you sure the content isn't broken before you send it to Doxia? Is your code accessible somewhere? Regards, Hervé Le jeudi 03 septembre 2009, javadevd...@googlemail.com a écrit : Hello! I'm writing my own maven-report plugin, which should create some output. This output is made with doxia, how it's explained in the tutorials. The problems are the german umlauts. I use it directly in the code (as String) to put via doxia into the html-page.(report) But the report don't shows the umlauts correctly. My problem is, that i don't know, where the encoding for doxia can be changed. (because doxia is initialized within the AbstractMavenReport) I'm a little bit confused, because there are a lot of descriptions in the net, that the default encoding is UTF-8 , so that there should be no problem with german umlauts. I have also tried to use the project.reporting.outputEncoding property in the pom, but nothing changes. Are there any experiences with that problem? thanks,,, Dave - 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 - 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: Getting a jar from a repo directly to an assembly?
If you have a multi-module build, I'd consider Wendy's suggestion a best practice. However if you just happen to have a single module and want to avoid creating another one (and a parent for them) you can use dependency plugin's copy goal to pull the jar in and put it somewhere (like target/lib), then use assembly's fileset to include it into the assembly. Kalle On Fri, Sep 4, 2009 at 12:08 PM, Wendy Smoakwsm...@gmail.com wrote: On Fri, Sep 4, 2009 at 12:02 PM, Jim Collingsjlistn...@gmail.com wrote: Is there any way to do this? The jar in question is not part of my build but is part of my assembly as it needs to be installed into the web container by the installation script. I've had one suggestion so far that I should create a separate module for getting the jar but I'll need more details. The jar is never downloaded and after all why would it be? There isn't any code in the module in question. It just makes an empty jar file. It has a pom and a manifest and that's it. Add this jar as a dependency of the separate module that builds your assembly. The packaging of this module would be 'pom'. Maven should resolve the dependencies and download it for you, and you can include it in your assembly. -- Wendy - 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
