RE: build fails
Radiya, > -Original Message- > From: radiya sojitrawala > Sent: woensdag 25 juni 2008 18:07 > To: Maven Users List > Subject: Re: build fails > > Hi Ringo, > > I do not see any repository settings in my project.xml. What > should I be looking for? > Am I missing something? I think most of us were assuming that you were running Maven 2.x. Have a look first to the Properties Reference page in the Maven 1.x documentation. http://maven.apache.org/maven-1.x/reference/properties.html The Connection Properties and the Proxy Properties are the sections you should definitely read. BTW, any specific reason why you can't switch to Maven 2.x? It is a better option in the long run... Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running generate-resources with eclipse:eclipse
Hello, I want to run some custom antrun action after execution of eclipse:eclipse goal. Currently I've managed this calling eclipse:eclipse and antrun activating some profile like: mvn -P eclipse generate-resources But this is not standard way to generate eclipse project files. User would most time want to simple do: mvn eclipse:eclipse Is there any way to attache custom antrun plugin to eclipse:eclipse goal? Thanks. -- View this message in context: http://www.nabble.com/Running-generate-resources-with-eclipse%3Aeclipse-tp18126844p18126844.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Releasing native-maven-plugin alpha 3 ?
Dear native-maven-plugin's users, if you would like me to make a new release, please test the snapshot and vote for this task: http://jira.codehaus.org/browse/MOJO-1157 Thanks -D -- Forwarded message -- From: Dan Tran (JIRA) <[EMAIL PROTECTED]> Date: Wed, Jun 25, 2008 at 9:45 PM Subject: [jira] Created: (MOJO-1157) Releasing native-maven-plugin alpha 3 To: [EMAIL PROTECTED] Releasing native-maven-plugin alpha 3 -- Key: MOJO-1157 URL: http://jira.codehaus.org/browse/MOJO-1157 Project: Mojo Issue Type: Task Components: native Reporter: Dan Tran To native-maven-plugin's users, If you would like to see this plugin released, please test, and add you vote for this task -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
blocking dependencies based on scope
Hi all, I am tasked with configuring our team's internal repository. As a team we are allowed to use any 3rd party dependencies for build-related activity, so for e.g. we may use JUnit/TestNG/EasyMock etc for the build. However, we are restricted in what we can and can't use for compile/runtime dependencies. Typically any 3rd party dependency like this needs to be okayed via a strict process (primarily due to licensing concerns). So, I've configured two different repos: 1. A proxy to Maven Central 2. An internal repo that has a tightly controlled set of 3rd party dependencies. So my question is: how do I configure Maven to use the proxy for all test-scope dependencies but only the second repo for compile/runtime dependencies? Thanks, Ishaaq
Re: Exclude module conditionally
You are right that profiles are only additive. I'd configure a profile named "development" or something like that, activate it by default, include and create the test ears in it, then configure another profile named "release", "versioned" or "distro" that doesn't specify the test ears but includes the final one. You need to have the profile configurations in several poms with matching profile names. More about activebydefault profile at http://maven.apache.org/guides/introduction/introduction-to-profiles.html Kalle On Wed, Jun 25, 2008 at 9:25 AM, Chris Lieb <[EMAIL PROTECTED]> wrote: > Hope y'all don't mind if I give this a bump. > > > Chris Lieb wrote: > >> I have a multi-module web project with the following structure: >> >> swear (pom) >> |- fish-tissue (pom) >> | |- ft-webapp (war) >> | |- ft-ear (ear) >> |- swear-core (pom) >> | |- sc-model (jar) >> | |- sc-webapp (war) >> | |- sc-ear (ear) >> |- swear-ear (ear) >> >> sc-ear is an EAR for testing just the swear-core module and ft-ear is an >> EAR for testing the fish-tissue module. swear-ear is the EAR that will house >> the final deployment unit for the entire application. >> >> Currently, both the swear-core and fish-tissue modules have a pom.xml that >> builds all sub-projects, including the test EARs, along with a >> pom-no-ear.xml that builds all sub-projects except for the EAR, and is used >> when constructing the final swear-ear deployment unit. I achieve this by >> placing the following modules section into the POM for swear: >> >> swear-core/pom-no-ear.xml >> fish-tissue/pom-no-ear.xml >> >> >> This does not seem right to me since the pom.xml and the pom-no-ear.xml >> are otherwise identical, with the exception of the one module (the EAR >> module) that is conditionally included. This would mean that, depending on >> when you pulled a POM artifact from the repository, you would get different >> POMs. >> >> I think that this could be remedied by using activation elements to >> control the included modules, but activation only seems to be additive, not >> subtractive. This is an issue since, by default, we want the testing EARs >> to be generated, with the no-EAR mode to be only used for generating a final >> deployment unit. >> >> Does anyone know how to achieve this? >> >> Thanks, >> Chris Lieb >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Assembly to include another assembly
Hi All, I have generated a assembly using the assembly plugin. This creates a zip file at a location in the repository. I have another project, that creates another assembly, that requires the first one. Is there any way to include the first assembly into the new one? In case anybody knows, please let me know how to do that. Thanks, Vijay -- View this message in context: http://www.nabble.com/Assembly-to-include-another-assembly-tp18122932p18122932.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reusable, in-line assemblies/user-level descriptorrefs
Thank you Julien! You ROCK! This is exactly what I was looking for. I think I'll spend some more time reading that book. You have been a great help. -mark Julien Simon wrote: > > Hi, > > If you want to re-use an assembly descriptor, the best solution is to > create > an artifact containing the assembly descriptor. Then you have to specify > this artifact as a plugin dependency for maven-assembly-plugin . After > that, > you should be able to specify directly your assembly descriptor contained > in > the artifact. If you want more details with code examples, you should read > "the maven definitive guide" from page 303 to 306. It's available at > http://www.sonatype.com/book/ , and there's a good example about how to > make reusable assembly descriptors. > > Regards, > > Julien Simon. > > -- View this message in context: http://www.nabble.com/Reusable%2C-in-line-assemblies-user-level-descriptorrefs-tp18114887p18120324.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: try -source 1.5 to enable annotations
Try adding the compiler plugin? org.apache.maven.plugins maven-compiler-plugin 1.5 1.5 -Original Message- From: get_it_done [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 2:50 PM To: users@maven.apache.org Subject: try -source 1.5 to enable annotations Hi folks, My Env: Spring 2.5 JDK 1.5 Ecllipse 3.3 Junit 4.4 Maven 2.0 I have maven plugin integrated in eclipse IDE. When I try to run Maven Test to test all the test cases, it throws up . Compilation failure ... annotations are not supported in -source 1.3 (try -source 1.5 to enable annotations) @Autowired any suggestions? -- View this message in context: http://www.nabble.com/try--source-1.5-to-enable-annotations-tp18119281p1 8119281.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
try -source 1.5 to enable annotations
Hi folks, My Env: Spring 2.5 JDK 1.5 Ecllipse 3.3 Junit 4.4 Maven 2.0 I have maven plugin integrated in eclipse IDE. When I try to run Maven Test to test all the test cases, it throws up . Compilation failure ... annotations are not supported in -source 1.3 (try -source 1.5 to enable annotations) @Autowired any suggestions? -- View this message in context: http://www.nabble.com/try--source-1.5-to-enable-annotations-tp18119281p18119281.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where to put DLLs required by gwt-dev.jar ??
gwt-dev.jar searches the dlls in the directory it is located. I don't know if this is the standard way or specific to gwt, I didn't manage to set java.library.path to work with this. My solution is to create a ZIP with the required native libs and deploy it as gwt-dev:version with classifier windows-libs : http://repo1.maven.org/maven2/com/google/gwt/gwt-dev/1.5-RC1/ The gwt-maven-plugin unpack the ZIP in the localrepository, so that the gwt hosted browser can run from a simple a maven-based classpath. Hope this helps, Nicolas. 2008/6/25 Mikel Cármenes Cavia <[EMAIL PROTECTED]>: > Hello Nicholas, > > Would you mind elaborating a little more on how you went about getting your > DLL's to work? > > I'm guessing that the answer you found was in my message thread about > incorporating DLL's, shockingly though, I still have not managed to figure > this one out myself! > > I have two DLL's and I currently have not discovered a way to put them > inside my jar, in the very location where the Java code looks via JNA. > > Thanks in advance mate! > > Mikel > > On Tue, Jun 24, 2008 at 07:22, nicolas de loof <[EMAIL PROTECTED]> wrote: > > > I've found an answer in recent list archive about incorporating DLLs in > > maven project. > > > > For info I'll package all the DLLs in a zip, use dependency:unpack, and > set > > my java.library.path > > > > 2008/6/24 nicolas de loof <[EMAIL PROTECTED]>: > > > > > I've setup my project with a dependency to gwt-dev-windows.jar, that is > > > downloaded in my local repository. > > > > > > To run the hosted mode I need two DLLs to be present in the same folder > > (in > > > my local repository) > > > > > > How can I set my dependencies/repository to get those DLLs downloaded > and > > > installed by maven ? > > > > > > Nico. > > > > > >
Re: Where to put DLLs required by gwt-dev.jar ??
Hello Nicholas, Would you mind elaborating a little more on how you went about getting your DLL's to work? I'm guessing that the answer you found was in my message thread about incorporating DLL's, shockingly though, I still have not managed to figure this one out myself! I have two DLL's and I currently have not discovered a way to put them inside my jar, in the very location where the Java code looks via JNA. Thanks in advance mate! Mikel On Tue, Jun 24, 2008 at 07:22, nicolas de loof <[EMAIL PROTECTED]> wrote: > I've found an answer in recent list archive about incorporating DLLs in > maven project. > > For info I'll package all the DLLs in a zip, use dependency:unpack, and set > my java.library.path > > 2008/6/24 nicolas de loof <[EMAIL PROTECTED]>: > > > I've setup my project with a dependency to gwt-dev-windows.jar, that is > > downloaded in my local repository. > > > > To run the hosted mode I need two DLLs to be present in the same folder > (in > > my local repository) > > > > How can I set my dependencies/repository to get those DLLs downloaded and > > installed by maven ? > > > > Nico. > > >
Location of tests for an API with 2 different implementations
Hello, I have the following question: I have a multi module project that is composed of three modules: one that specify an API (with interfaces and factories), and the two others are two different implementations of the API. The problem is relative to the tests. Because the tests are independent of the implementation but need at least one implementation to run, and because I want to run them against each of the implementation, in order to prevent code duplication, my intent is to put the test sources in the API module. Of course, when building the API module, it will set the skip parameter of the surefire plugin to true. Now, my question is does the surefire plugin will run the tests when I will build the implementations because there will be no tests in the tests folder of each implementation module ? Thanks Jeff MAURY -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
Re: Snippet with file
try or (not sure about your project structure, I don't know what the three dots mean...) HTH, -Lukas [EMAIL PROTECTED] wrote: the MU_32_sommaire.fr.xml is locate into ...\projet\src\site\xdoc If I do that I obtain : Caused by: java.io.FileNotFoundException: C:\Program Files\NetBeans 6.1\MU_32_sommaire.fr.xml (Le fichier spécifié est introuvable) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at java.net.URL.openStream(URL.java:1007) at org.apache.maven.doxia.macro.snippet.SnippetReader.readLines(SnippetReader.java:118) at org.apache.maven.doxia.macro.snippet.SnippetReader.readSnippet(SnippetReader.java:59) at org.apache.maven.doxia.macro.snippet.SnippetMacro.getSnippet(SnippetMacro.java:150) at org.apache.maven.doxia.macro.snippet.SnippetMacro.execute(SnippetMacro.java:110) ... 26 more Have you got any idea ? I don't want to put the absolute path to the file as every one into the team has different path
RE: build fails
Sorry - I only have experience with Maven 2. Pete -Original Message- From: radiya sojitrawala [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 12:28 PM To: Maven Users List Subject: Re: build fails hi Peter, I am using Maven 1.1. I dotn see a settings.xml -R On Wed, Jun 25, 2008 at 9:16 AM, Hayes, Peter <[EMAIL PROTECTED]> wrote: > If you are behind a firewall, make sure to configure the proxy settings > : > > http://maven.apache.org/guides/mini/guide-proxies.html > > If that's not the problem, please post the full output. > > Pete > > -Original Message- > From: radiya sojitrawala [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 7:57 PM > To: users@maven.apache.org > Subject: build fails > > Hi, > > > > I ma new to Maven. My build fails due to the following: > > > > > > >> The build cannot continue because of the following unsatisfied > dependencies: > > - org.codehaus.plexus:plexus-utils:1.0.5:jar > > - com.jcraft:jsch:0.1.27:jar > > - org.apache.velocity:velocity:1.5:jar > > - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar > > - net.java.dev.stax-utils:stax-utils:20060502:jar > > > > Any pointers? > > Thanks > > Radiya > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build fails
hi Peter, I am using Maven 1.1. I dotn see a settings.xml -R On Wed, Jun 25, 2008 at 9:16 AM, Hayes, Peter <[EMAIL PROTECTED]> wrote: > If you are behind a firewall, make sure to configure the proxy settings > : > > http://maven.apache.org/guides/mini/guide-proxies.html > > If that's not the problem, please post the full output. > > Pete > > -Original Message- > From: radiya sojitrawala [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 7:57 PM > To: users@maven.apache.org > Subject: build fails > > Hi, > > > > I ma new to Maven. My build fails due to the following: > > > > > > >> The build cannot continue because of the following unsatisfied > dependencies: > > - org.codehaus.plexus:plexus-utils:1.0.5:jar > > - com.jcraft:jsch:0.1.27:jar > > - org.apache.velocity:velocity:1.5:jar > > - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar > > - net.java.dev.stax-utils:stax-utils:20060502:jar > > > > Any pointers? > > Thanks > > Radiya > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: build fails
hi Peter, I am using Maven 1.1. I dotn see a settings.xml -R On Wed, Jun 25, 2008 at 9:16 AM, Hayes, Peter <[EMAIL PROTECTED]> wrote: > If you are behind a firewall, make sure to configure the proxy settings > : > > http://maven.apache.org/guides/mini/guide-proxies.html > > If that's not the problem, please post the full output. > > Pete > > -Original Message- > From: radiya sojitrawala [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 7:57 PM > To: users@maven.apache.org > Subject: build fails > > Hi, > > > > I ma new to Maven. My build fails due to the following: > > > > > > >> The build cannot continue because of the following unsatisfied > dependencies: > > - org.codehaus.plexus:plexus-utils:1.0.5:jar > > - com.jcraft:jsch:0.1.27:jar > > - org.apache.velocity:velocity:1.5:jar > > - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar > > - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar > > - net.java.dev.stax-utils:stax-utils:20060502:jar > > > > Any pointers? > > Thanks > > Radiya > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Exclude module conditionally
Hope y'all don't mind if I give this a bump. Chris Lieb wrote: I have a multi-module web project with the following structure: swear (pom) |- fish-tissue (pom) | |- ft-webapp (war) | |- ft-ear (ear) |- swear-core (pom) | |- sc-model (jar) | |- sc-webapp (war) | |- sc-ear (ear) |- swear-ear (ear) sc-ear is an EAR for testing just the swear-core module and ft-ear is an EAR for testing the fish-tissue module. swear-ear is the EAR that will house the final deployment unit for the entire application. Currently, both the swear-core and fish-tissue modules have a pom.xml that builds all sub-projects, including the test EARs, along with a pom-no-ear.xml that builds all sub-projects except for the EAR, and is used when constructing the final swear-ear deployment unit. I achieve this by placing the following modules section into the POM for swear: swear-core/pom-no-ear.xml fish-tissue/pom-no-ear.xml This does not seem right to me since the pom.xml and the pom-no-ear.xml are otherwise identical, with the exception of the one module (the EAR module) that is conditionally included. This would mean that, depending on when you pulled a POM artifact from the repository, you would get different POMs. I think that this could be remedied by using activation elements to control the included modules, but activation only seems to be additive, not subtractive. This is an issue since, by default, we want the testing EARs to be generated, with the no-EAR mode to be only used for generating a final deployment unit. Does anyone know how to achieve this? Thanks, Chris Lieb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: build fails
If you are behind a firewall, make sure to configure the proxy settings : http://maven.apache.org/guides/mini/guide-proxies.html If that's not the problem, please post the full output. Pete -Original Message- From: radiya sojitrawala [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2008 7:57 PM To: users@maven.apache.org Subject: build fails Hi, I ma new to Maven. My build fails due to the following: >> The build cannot continue because of the following unsatisfied dependencies: - org.codehaus.plexus:plexus-utils:1.0.5:jar - com.jcraft:jsch:0.1.27:jar - org.apache.velocity:velocity:1.5:jar - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar - net.java.dev.stax-utils:stax-utils:20060502:jar Any pointers? Thanks Radiya - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build fails
Hi Ringo, I do not see any repository settings in my project.xml. What should I be looking for? Am I missing something? thanks Radiya 2008/6/25 De Smet Ringo <[EMAIL PROTECTED]>: > Radiya, > > > -Original Message- > > From: radiya sojitrawala [mailto:[EMAIL PROTECTED] > > Sent: woensdag 25 juni 2008 1:57 > > To: users@maven.apache.org > > Subject: build fails > > > > I ma new to Maven. My build fails due to the following: > > Can you post your Maven repository settings from your pom.xml? > > Ringo > * > > Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie > bevatten die vertrouwelijk is en/of beschermd door intellectuele > eigendomsrechten. Dit bericht is uitsluitend bestemd voor de > geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht > (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder > elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien > u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te > verwittigen en dit bericht te verwijderen. > > This e-mail and any attachment thereto may contain information which is > confidential and/or protected by intellectual property rights and are > intended for the sole use of the addressees. Any use of the information > contained herein (including but not limited to total or partial reproduction > or distribution in any form) by other persons than the addressees is > prohibited. If you have received this e-mail in error, please notify the > sender and delete its contents. > > Ce courriel et les annexes éventuelles peuvent contenir des informations > confidentielles et/ou protégées par des droits de propriété intellectuelle. > Ce message est adressé exclusivement à son (ses) destinataire(s). Toute > utilisation du contenu de ce message (y compris la reproduction ou diffusion > partielle ou complète sous toute forme) par une autre personne que le(s) > destinataire(s) est formellement interdite. Si vous avez reçu ce message par > erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. > > * > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Snippet with file
the MU_32_sommaire.fr.xml is locate into ...\projet\src\site\xdoc If I do that I obtain : Caused by: java.io.FileNotFoundException: C:\Program Files\NetBeans 6.1\MU_32_sommaire.fr.xml (Le fichier spécifié est introuvable) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:106) at java.io.FileInputStream.(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at java.net.URL.openStream(URL.java:1007) at org.apache.maven.doxia.macro.snippet.SnippetReader.readLines(SnippetReader.java:118) at org.apache.maven.doxia.macro.snippet.SnippetReader.readSnippet(SnippetReader.java:59) at org.apache.maven.doxia.macro.snippet.SnippetMacro.getSnippet(SnippetMacro.java:150) at org.apache.maven.doxia.macro.snippet.SnippetMacro.execute(SnippetMacro.java:110) ... 26 more Have you got any idea ? I don't want to put the absolute path to the file as every one into the team has different path
Re: Reusable, in-line assemblies/user-level descriptorrefs
Hi, If you want to re-use an assembly descriptor, the best solution is to create an artifact containing the assembly descriptor. Then you have to specify this artifact as a plugin dependency for maven-assembly-plugin . After that, you should be able to specify directly your assembly descriptor contained in the artifact. If you want more details with code examples, you should read "the maven definitive guide" from page 303 to 306. It's available at http://www.sonatype.com/book/ , and there's a good example about how to make reusable assembly descriptors. Regards, Julien Simon.
Reusable, in-line assemblies/user-level descriptorrefs
Is it possible to place an assembly in the pom.xml file rather than a separate xml file? My purpose is that I have a large number of similar projects that use the same assembly descriptor. It is different than all of the built-in descriptors, and I would like NOT to have to copy the assembly.xml file into each project explicitly, but to inherit the assembly through normal pom.xml inheritance. If this is not possible, does anyone have a suggestion as to how to go about this in another way? My problem manifests itself when I build in an environment that does not have ALL of the necessary source code locally. I would like to be able to place an assembly in a versioned Maven project, and refer to it from other projects that depend upon it. Currently, the assembly.xml file cannot be found because I have to explicitly define the path to it, and this path does not exist unless the source to the project in which it resides is checked-out of CM. Thanks for the help. -mark -- View this message in context: http://www.nabble.com/Reusable%2C-in-line-assemblies-user-level-descriptorrefs-tp18114887p18114887.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
weird error message
Component descriptor role: 'org.apache.maven.wagon.CommandExecutor', implementation: 'org.apache.maven.wagon.providers.ssh.external.ScpExternalCommandExecutor', role hint: 'scpexe' has a hint, but there are other implementations that don't Thank you for your help, Ittay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CVS, maven2 release plugin, best practice
Hi all, I have been playing with maven2 release plugin and wanted to get insight from the community. The following link was very useful in getting a setup going: http://jlorenzen.blogspot.com/2007/09/how-to-create-release-using-maven2.html. However there is still a gray area into how branching/merging would fit in the picture. In my model I use release:branch plugin to create a branch whenever a release is ready for staging/production. I do: mvn release:branch -DupdateBranchVersions=true when prompted I provide 1.0 version for the branch and 2.0-SNAPSHOT for next working version. The branch is getting created in CVS and pom files are updated appropriately. Now let's say I need to apply a bugfix to my branch. 1. I checkout branch in a separate workspace. I apply fixes check them in to the branch. I create a tag say: 1_0_branch_fix1. At this point should I update the pom files in the branch to something like 1.0.fix1 ? Afaik there is no automated process for this in maven2. 2. Now I released 1_0_branch_fix1 with release:perform plugin using -Dtag and -DconnectionUrl option (no need for release.properties) 3. Merge back fix in the trunk. This process is not done through maven. Let me know how you guys tackle this problem, I guess the only missing piece in my process is the update of the pom files in the branch when doing a bugfix release. Today I have to update this manually. Regards, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Regarding Reports.
I am generating javaodc, checkstyle, pld junit reprts using maven plugins. when i open the report htmls on the server where i generate them, i do not see the place holders for the images. also i see some warning that : XRef link not found/disabled, the decorations will not be resolved Also when i open the index.html page in the target/site/ folder, and try to click any hyper link on the page, i see a blank page Also the index.html has no stling they way any maven page has, no images. but when i donwload the folder site folder on my local box, everything works perfect. the wbe page CSS, the cross links from the home page to the other pasges. the reports need to be wirking right on the server, as when one opens the target/site/index.html he shold see everything that is available, he shold not be forced to downlaod it to the local box to see all reprts. wht m i missing in my POM? -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want"
Re: Advanced exclude pattern for Skinny Wars
Hi Chris I was doing the same thing these days here at IBM on a migration
project from WAS 4.7 to WAS 6.1. So I've applied maven to organize the
projects that are no "so good" hehehee...
I've already added some of the configurations you've added for the
maven-eclipse-plugin (m2eclipse specific goal) but the JRE System Library I
was not using like yours... I was using in this way:
org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType
and in your previous message where you've added your complete pom you've
used in this way:
org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
v6.1 JRE
However, when I run the eclipse:m2eclipse to generate the RAD files
(.project, .classpath, .settings and etc..) I got this on my .classpath and
I think it's no ok:
I think the problem is only the end of the value... Is it "WebSphere v6.1
JRE" (with a space between WebSphere and v6.1) or "WebSpherev6.1 JRE" (with
no space) ???
Other questions... Where on the RAD installation did you get the dependency
to deploy on your private repository??? I have and Artifactory server in
place and I'd like to do that as well... The dependency I'm asking is this
one:
com.ibm.websphere.appserver
runtime
6.1
pom
provided
I'm looking forward your feedback...
Thaks in advance.
ChrisGWarp wrote:
>
> "Baeriswyl Kuno - Extern (IT-BA-MV)" <[EMAIL PROTECTED]> wrote on
> 30/05/2008 00:37:53:
>
>> Hello,
>>
>> in der Maven documentation is an article about a workaround for creating
>
>> skinny wars. http://maven.apache.org/plugins/maven-war-
>> plugin/examples/skinny-wars.html
>>
>> In this approach, all libs in WEB-INF/lib are exluded by applying
>> following pattern configuration: WEB-INF/lib/*.
>> jar
>>
>> Is it possible to exclude only certain libraries? Respectively, can I
>> configure the war plugin in way that I it keeps the web specific
>> dependencies, e.g. Struts libraries, in the web application and shares
>> only the utility libraries in the EAR classloader?
>
> I've managed to do just that! :-)
>
> The tools, resources are the utility ones and the ejb one is added as
> well.
>
> I had issues previously when adding in the dependencies - gave wierd
> errors about things not being able to be found. The final one was the ejb
> jar. It needed the type of ejb being set specifically as it otherwise
> defaults to jar.
>
> This is my complete pom for the war file:
>
>
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd"; xmlns:xsi=
> "http://www.w3.org/2001/XMLSchema-instance";>
>
> 4.0.0
>
>
> au.com.aami
> aami-parent
> 1-SNAPSHOT
>
>
> au.com.aami.dialler
> DiallerWeb
> war
> 1.0-SNAPSHOT
> DiallerWeb Project
> DiallerWeb Project
> http://centre.ourspace.int.corp.sun/it/sd/webapplications/
>
>
>
> junit
> junit
> ${junit.version}
> test
>
>
>
> au.com.aami
> AAMITools
> 1.0-SNAPSHOT
>
>
>
> au.com.aami.dialler
> DiallerResources
> 1.0-SNAPSHOT
>
>
>
> au.com.aami.dialler
> DiallerEJB
> 1.0-SNAPSHOT
> ejb
>
>
>
> com.ibm.websphere.appserver
> runtime
> 6.1
> pom
> provided
>
>
>
>
>
> 3.8.1
>
>
>
>
>
> maven-war-plugin
>
>
> WEB-INF/lib/*.jar warSourceExcludes>
>
>
> true
>
>
>
>
>
>
>
> maven-eclipse-plugin
>
> 1.5
>
>
>
> org.eclipse.wst.validation.validationbuilder
>
> org.eclipse.wst.common.project.facet.core.builder
>
>
>
>
> org.eclipse.wst.common.project.facet.core.nature
>
> org.eclipse.wst.common.modulecore.ModuleCoreNature
>
>
>
>
> org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
>
> v6.1 JRE
>
> org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61
>
>
> org.eclipse.jst.j2ee.internal.web.container
>
> org.eclipse.jst.j2ee.internal.
Re: Suggestion for artifact parametrization
This is a good topic, that IMO is not simple with maven 2. I'm also looking for a simple or elegant solution. Rémy
RE: Avoiding a parent project from being installed into the repository
Hello, The subprojects do not inherit from the parent pom. However, it seems that you and other guys are rights about my 'issue'. Since the installation is done only in a local repository, that's not so important; final/corporate repository will only holds concrete artifacts. That was false problem - and may be misunderstanding of some concepts... Thank you and other people for your answers. Vincent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven 2.0.9 unable to download artificats
Hello, > -Original Message- > From: shady kazan [mailto:[EMAIL PROTECTED] > Sent: woensdag 25 juni 2008 14:55 > To: [EMAIL PROTECTED] > Cc: users@maven.apache.org > Subject: RE: maven 2.0.9 unable to download artificats > > but i had no previous installation, i made a fresh clean > install of maven. > i guess thi rules out the erroneous settings.xml file possibility Just for completeness, in which folder did you put the settings.xml? Maven2 requires this file in /.m2, while Maven1 had this in /.maven Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven 2.0.9 unable to download artificats
but i had no previous installation, i made a fresh clean install of maven. i guess thi rules out the erroneous settings.xml file possibility regards
RE: Incrementing a pom version in a multi-module project (without doing by hand)
Ian, This looks like a usecase for release:prepare, this will create a new SCM tag and manage your version numbers in the pom.xml files. thanks, -Guillaume From: Ian Rowlands [mailto:[EMAIL PROTECTED] Sent: Tue 24/06/2008 7:34 PM To: users@maven.apache.org Subject: Incrementing a pom version in a multi-module project (without doing by hand) Just wondering what the best way to change the version of POMs in a multi-module Maven 2 project from one number to another? I know you can use the release:branch plugin to do it if you require a branch, but sometimes I don't want to branch - I just want to increase the version! I need to be able to choose the version as well. Which plugin can do this, and how do I use it? Thanks, Ian Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected (administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Re: maven assembly bug MASSEMBLY-74
Thanks, I have opened a JIRA issue at http://jira.codehaus.org/browse/MASSEMBLY-332 . I didn't mention the http://jira.codehaus.org/browse/MASSEMBLY-74 bug in the issue description, because for me the problem appears only for a assembly with a war format. Regards, Julien Simon.
RE: maven 2.0.9 unable to download artificats
Just a lucky guess: maybe you had a customized settings.xml in your old maven installation that you didn't copy inside the new 2.0.9 conf directory? Something like the proxy parameters would be an obvious reason for the artefact retrieving to fail. Cheers. -Message d'origine- De : shady kazan [mailto:[EMAIL PROTECTED] Envoyé : mercredi 25 juin 2008 13:46 À : users@maven.apache.org Objet : maven 2.0.9 unable to download artificats I just installed maven2.0.9 on my Windows XP. I verified the installation and all seems to work fine except that it crashes trying to download needed artifacts.I'm behind a proxy server, my corporate proxy which is an NTLM proxy. I know there used to be an issue with maven behind NTLM proxies with versions prior to 2.0.9 and that they have been resolved in 2.0.9.Anyway, here's what i'm getting when i try. i have adjusted the proxy setings in the settings.xml file as appropriate but still no effect C:\Dev\> mvn -e package + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - wrox:pixweb:war:0.0.1 [INFO]task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/1/maven-plugins-1.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/1/maven-plugins-1.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-plugins Version: 1 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-plugins:pom:1 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.apache.maven.plugins:mav en-resources-plugin': Cannot find parent: org.apache.maven.plugins:maven-plugins for project: null:maven-resources-plugi n:maven-plugin:2.2 for project null:maven-resources-plugin:maven-plugin:2.2 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1 033) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java: 997) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.apache.maven.plugins: maven-resources-plugin': Cannot find parent: org.apache.maven.plugins:maven-plugins for project: null:maven-resources-pl ugin:maven-plugin:2.2 for project null:maven-resources-plugin:maven-plugin:2.2 at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:281) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) ... 18 more Caused by: org.apache.maven.project.ProjectBuildingException: Cann
How to set the JDK target used into MANIFEST.MF Build-Jdk
Hi all,
currently I am trying to set properly the JDK target used when jarring my
modules. What I have tried is:
org.apache.maven.plugins
maven-jar-plugin
false
test
${maven.compiler.compilerVersion}
${maven.compiler.target}
..
The problem seems to be that ${maven.compiler.compilerVersion} has not been
initialised yet neither the ${maven.compiler.target} expression, when it
should be set into the entry. When I open the MANIFEST.MF I see
that Build-Jdk is set to "test null".
I have read a JIRA related to this issue:
[jira] Created: (MPJAR-49) Incorrect jdk version in "Build JDK" in manifest
when maven.compile.executable is set
but it seems I can not fix it.
Could you advise me.
Thank you
Dobri
Re: Re: javadoc plugin [Virus checked]
On Wed, Jun 25, 2008 at 12:54 PM, <[EMAIL PROTECTED]> wrote: > Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - It seems, that Javadoc is exiting with a return code of 1. Maybe there is an interesting error message before the lines you have pasted that helps to track down the problem. You may also try to run javadoc manually (without Maven) to get a hint why it is failing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven 2.0.9 unable to download artificats
I just installed maven2.0.9 on my Windows XP. I verified the installation and all seems to work fine except that it crashes trying to download needed artifacts.I'm behind a proxy server, my corporate proxy which is an NTLM proxy. I know there used to be an issue with maven behind NTLM proxies with versions prior to 2.0.9 and that they have been resolved in 2.0.9.Anyway, here's what i'm getting when i try. i have adjusted the proxy setings in the settings.xml file as appropriate but still no effect C:\Dev\> mvn -e package + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - wrox:pixweb:war:0.0.1 [INFO]task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/1/maven-plugins-1.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/1/maven-plugins-1.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-plugins Version: 1 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-plugins:pom:1 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.apache.maven.plugins:mav en-resources-plugin': Cannot find parent: org.apache.maven.plugins:maven-plugins for project: null:maven-resources-plugi n:maven-plugin:2.2 for project null:maven-resources-plugin:maven-plugin:2.2 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1 033) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java: 997) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.apache.maven.plugins: maven-resources-plugin': Cannot find parent: org.apache.maven.plugins:maven-plugins for project: null:maven-resources-pl ugin:maven-plugin:2.2 for project null:maven-resources-plugin:maven-plugin:2.2 at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:281) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) ... 18 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.maven.plugins:maven-plugins for project: null:maven-resources-plugin:maven-plugin:2.2 for project null:maven-resources-plugin:maven-plugin:2.2 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821) at org.apache.maven.project.DefaultMave
Re: Maven & WebSphere 6.1
On Tue, 10 Jun 2008, Jo Support wrote: Hello folks, I'm following the instructions from http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating in order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have the following jars under /lib : This plugin might come in handy for you: http://mojo.codehaus.org/was6-maven-plugin/ -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antwort: Re: javadoc plugin [Virus checked]
When I take the comments out, it runs fine: maven-javadoc-plugin 2.0 java -Xms512m -Xmx512m sun.tools.javadoc.Main otherwise I get (finally after lots of warnings) :/Dokumente und Einstellungen/DE16297/workspace/CPM-opm/src/main/java/net/atos/wlp/cpm/domain/opm/PlasticFactory.java:75: warning - @linkPlastic is an unknown tag. D:/Dokumente und Einstellungen/DE16297/workspace/CPM-opm/src/main/java/net/atos/wlp/cpm/domain/opm/PlasticValueFactory.java:62: warning - @linkPlasticValue is an unknown tag. D:/Dokumente und Einstellungen/DE16297/workspace/CPM-opm/src/main/java/net/atos/wlp/cpm/domain/opm/ValueSetFactory.java:65: warning - @linkValueSet is an unknown tag. at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) ... 18 more Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - javadoc: warning - Multiple sources of package comments found for package "net.atos.wlp.cpm.command" D:/Dokumente und Einstellungen/DE16297/workspace/CPM-opm/src/main/java/net/atos/wlp/cpm/masscommand/MassCommandAssignmentFactory.java:174: warning - Tag @author cannot be used in method documentation. It can only be used in the following types of documentation: overview, package, class/interface.: at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:845) at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:104) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) ... 22 more [INFO] [INFO] Total time: 1 minute 32 seconds [INFO] Finished at: Wed Jun 25 12:50:16 CEST 2008 [INFO] Final Memory: 25M/254M Does it help ??? mit freundlichen Grüßen/best regards Wolfgang Schrecker "Der Inhalt eines Begriffs nimmt ab, wenn sein Umfang zunimmt; wird dieser allumfassend, so muß der Inhalt ganz verloren gehen." from G. Frege: Die Grundlagen der Arithmetik S. 40 -- -- Atos Worldline Processing GmbH Hahnstrasse 25 60528 Frankfurt/Main Germany Phone: +49 69/6657-1176 mailto:[EMAIL PROTECTED] http://www.atosworldline.com Geschäftsführer: Erik Munk Koefoed Aufsichtsratsvorsitzender: Didier Dhennin Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 "Heinrich Nirschl" "Maven Users List" 24.06.2008 13:45Kopie Thema Bitte antworten Re: javadoc plugin [Virus checked] an "Maven Users List" <[EMAIL PROTECTED] he.org> On Tue, Jun 24, 2008 at 9:30 AM, <[EMAIL PROTECTED]> wrote: > > does anybody know why the following happens: > > in a project we just recently converted to MAVEN with about 460 classes to > compile, > the MAVEN task for generating the javadoc does NOT complete. Can you give some more details (e.g. an error message)? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Atos Worldline Processing GmbH Hahnstraße 25 60528 Frankfurt/Main Germany Phone: +49 69/6657-1176 Fax : mailto: [EMAIL PROTECTED] http://www.atosworldline.com Geschäftsführer: Erik Munk Koefoed Aufsichtsratsvorsitzender: Didier Dhennin Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * * This e-mail is d
RE: Please help with assembly plugin dependency problems! :-(
Kent, > -Original Message- > From: Kent Närling > Sent: woensdag 25 juni 2008 11:22 > To: Maven Users List > Subject: Re: Please help with assembly plugin dependency problems! :-( > > Thanks a lot, this fixed it! :-) You're welcome! As to the 'why': Maven Embedder is based on the Maven 2.1 codebase, which is still a work in progress. It's a fact of life that bugs can creep in in code that is being changed. I continue to use an external Maven installation at least until Maven 2.1 and the Embedder gets official. Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[testing] maven + selenium + jetty = broken output on console
Hello everybody, I configured maven to run my selenium tests in a jetty-container managed by maven. Since then a successfully build does not generate a report at the end of the lifecycle. I found out, that is has to do with the startup and shutdown of the jetty-container defined in my pom. Logging on the console ends like this for successfully running "mvn install" instead of writing the standard report to the console: 2008-06-25 11:20:12.049:/toys-view:INFO: Closing Spring root WebApplicationContext 2008-06-25 11:20:12.065::INFO: Shutdown hook complete My questions are: Did you make similar experiences? How would you deal with this problem? Thanks for any hints, Stefan For better traceability I enclose my configuration of the build-section in my pom: toys-view org.mortbay.jetty maven-jetty-plugin 10 STOPJETTY start-jetty pre-integration-test run 0 true stop-jetty post-integration-test stop org.codehaus.mojo selenium-maven-plugin pre-integration-test start-server true true org.apache.maven.plugins maven-surefire-plugin true integration-test test false
Re: Please help with assembly plugin dependency problems! :-(
Thanks a lot, this fixed it! :-) 2008/6/25 De Smet Ringo <[EMAIL PROTECTED]>: > Kent, > > > -Original Message- > > From: Kent Närling > > Sent: woensdag 25 juni 2008 10:53 > > To: Maven Users List > > Subject: Re: Please help with assembly plugin dependency problems! :-( > > > > Update to this one, this seems to happen if I execute the > > build from within the M2 plugin in eclipse only. > > > > If I run it on the command line it works fine!?! > > > > Anyone know why the plugin makes this behave differently? > > On the command line it also tries to download the failing POM > > and fails too, but it seems to ignore it then! > > (but not from within Eclipse) > > I also encountered problems once where a build using the m2eclipse plugin > failed, while it worked on the command line. What I did was to disable the > Maven Embedder in m2eclipse and select a normal Maven2 installation to use. > Check the Eclipse Preferences (Window -> Preferences -> Maven -> > Installations). > > Ringo > * > > Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie > bevatten die vertrouwelijk is en/of beschermd door intellectuele > eigendomsrechten. Dit bericht is uitsluitend bestemd voor de > geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht > (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder > elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien > u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te > verwittigen en dit bericht te verwijderen. > > This e-mail and any attachment thereto may contain information which is > confidential and/or protected by intellectual property rights and are > intended for the sole use of the addressees. Any use of the information > contained herein (including but not limited to total or partial reproduction > or distribution in any form) by other persons than the addressees is > prohibited. If you have received this e-mail in error, please notify the > sender and delete its contents. > > Ce courriel et les annexes éventuelles peuvent contenir des informations > confidentielles et/ou protégées par des droits de propriété intellectuelle. > Ce message est adressé exclusivement à son (ses) destinataire(s). Toute > utilisation du contenu de ce message (y compris la reproduction ou diffusion > partielle ou complète sous toute forme) par une autre personne que le(s) > destinataire(s) est formellement interdite. Si vous avez reçu ce message par > erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. > > * > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
RE: Please help with assembly plugin dependency problems! :-(
Kent, > -Original Message- > From: Kent Närling > Sent: woensdag 25 juni 2008 10:53 > To: Maven Users List > Subject: Re: Please help with assembly plugin dependency problems! :-( > > Update to this one, this seems to happen if I execute the > build from within the M2 plugin in eclipse only. > > If I run it on the command line it works fine!?! > > Anyone know why the plugin makes this behave differently? > On the command line it also tries to download the failing POM > and fails too, but it seems to ignore it then! > (but not from within Eclipse) I also encountered problems once where a build using the m2eclipse plugin failed, while it worked on the command line. What I did was to disable the Maven Embedder in m2eclipse and select a normal Maven2 installation to use. Check the Eclipse Preferences (Window -> Preferences -> Maven -> Installations). Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help with assembly plugin dependency problems! :-(
Update to this one, this seems to happen if I execute the build from within the M2 plugin in eclipse only. If I run it on the command line it works fine!?! Anyone know why the plugin makes this behave differently? On the command line it also tries to download the failing POM and fails too, but it seems to ignore it then! (but not from within Eclipse) 2008/6/25 Kent Närling <[EMAIL PROTECTED]>: > Hi, > > I still cannot get the assembly plugin to work properly in many situations. > > There are a lot of situations where a plugin/depenedency depends on > something else where it works nicely for building and running since it only > requires the jar. > But then the assembly plugin tries to get the POM which fails! (since the > known repositories doesn't have it) > > Yet another fresh example: > Error retrieving POM of module-dependency: > com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2; Reason: POM > 'com.sun.xml.fastinfoset:FastInfoset' not found in repository: Unable to > download the artifact from any repository > > And this seems quite common... ? > Can anyone explain why this is and enlighten me how to fix it? > > I am pulling out my hair trying to get this working ... :-( > > //Kent > -- Kent Närling System Architect SEAMLESS Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden Phone: +46 8 5648 7800, fax: +46 8 5648 7823 Mobile: +46 70 836 9925 Mail: [EMAIL PROTECTED] www.seamless.se
Please help with assembly plugin dependency problems! :-(
Hi, I still cannot get the assembly plugin to work properly in many situations. There are a lot of situations where a plugin/depenedency depends on something else where it works nicely for building and running since it only requires the jar. But then the assembly plugin tries to get the POM which fails! (since the known repositories doesn't have it) Yet another fresh example: Error retrieving POM of module-dependency: com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2; Reason: POM 'com.sun.xml.fastinfoset:FastInfoset' not found in repository: Unable to download the artifact from any repository And this seems quite common... ? Can anyone explain why this is and enlighten me how to fix it? I am pulling out my hair trying to get this working ... :-( //Kent
RE: Passing compile dependencies to Ant-based mojo?
No answers so far... Should I rather direct this to the developer list?
Ringo
> -Original Message-
> From: De Smet Ringo
> Sent: vrijdag 20 juni 2008 15:14
> To: users@maven.apache.org
> Subject: Passing compile dependencies to Ant-based mojo?
>
> Hello,
>
> I am busy converting our complete build process from Maven 1
> to Maven 2.
> One of my tasks is to migrate our custom Maven 1 build plugin
> to the Maven 2 format. In this latter plugin, I wrote an
> Ant-based mojo that invokes the Weblogic WLI wlwbuild task.
> However, I failed to correctly configure the classpath to
> this task up to now. Here are the contents of the
> wlibuild.build.xml Ant file:
>
>
>
> Hello, wli
>
>
>path="${weblogicHome}/workshop/wlw-ide.jar" />
>
>
>
>
>
>
>
>
>
>classname="workshop.core.WlwBuildTask">
>
>path="${weblogicHome}/workshop/wlw-ide.jar" />
>
>
>
>serverclasspath="${weblogicHome}/server/lib/wli.jar;${weblogic
> Home}/serv
> er/lib/xbean.jar;${weblogicHome}/server/lib/weblogic.jar;"
> maxmemory="512m" logDir="${targetDirectory}">
>
>
>
>outputfilename="${targetEarName}" noear="${noEar}" />
>value="${weblogicHome}/workshop">
>
>
>
>
>
> While the mojo is defined in the maven2.plugin project, in
> the our custom build plugin, I want to pass the classpath to
> the dependencies of the project in which this mojo is
> invoked. E.g. if I invoke this mojo in project
> srv.service.common, then I want the compile-time dependencies
> of srv.service.common being passed as the classpath setting
> of the wlwBuild Ant task. What do I have to write in place of
> the XML comment above?
>
> Let me clarify that I have been searching the user and
> developer for a number of hours, read through a lot of posts,
> but still couldn't get it to work!
>
> Ringo De Smet
*
Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie
bevatten die vertrouwelijk is en/of beschermd door intellectuele
eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n).
Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of
gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen
dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft
ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te
verwijderen.
This e-mail and any attachment thereto may contain information which is
confidential and/or protected by intellectual property rights and are intended
for the sole use of the addressees. Any use of the information contained herein
(including but not limited to total or partial reproduction or distribution in
any form) by other persons than the addressees is prohibited. If you have
received this e-mail in error, please notify the sender and delete its contents.
Ce courriel et les annexes éventuelles peuvent contenir des informations
confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce
message est adressé exclusivement à son (ses) destinataire(s). Toute
utilisation du contenu de ce message (y compris la reproduction ou diffusion
partielle ou complète sous toute forme) par une autre personne que le(s)
destinataire(s) est formellement interdite. Si vous avez reçu ce message par
erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu.
*
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: build fails
Radiya, > -Original Message- > From: radiya sojitrawala [mailto:[EMAIL PROTECTED] > Sent: woensdag 25 juni 2008 1:57 > To: users@maven.apache.org > Subject: build fails > > I ma new to Maven. My build fails due to the following: Can you post your Maven repository settings from your pom.xml? Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build fails
Hi, I ma new to Maven. My build fails due to the following: >> The build cannot continue because of the following unsatisfied dependencies: - org.codehaus.plexus:plexus-utils:1.0.5:jar - com.jcraft:jsch:0.1.27:jar - org.apache.velocity:velocity:1.5:jar - org.apache.maven.wagon:wagon-provider-api:1.0-beta-2:jar - org.apache.maven.wagon:wagon-http:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ftp:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh-common:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh:1.0-beta-2:jar - org.apache.maven.wagon:wagon-ssh-external:1.0-beta-2:jar - org.apache.maven.wagon:wagon-file:1.0-beta-2:jar - net.java.dev.stax-utils:stax-utils:20060502:jar Any pointers? Thanks Radiya
