Re: -Dmaven.test.skip=true && jar:test-jar
just use "-DskipTests" as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias "-Dmaven.skip.test.exec=true" as well as the bigger skip that you are using "-Dmaven.skip.test=true" -Stephen On 3 September 2010 02:28, Andrew Hughes wrote: > Hi Guys, > > When -Dmaven.test.skip=true the jar:test-jar goals are skipped. Other > modules who have a dependency on the jar:test-jar artifact then fail > (unresolved dependency). > > Is this a sensible default for the plugin and any idea's how I can override > this? > > Thanks heaps (again) :) > --Andrew >
Re: -Dmaven.test.skip=true && jar:test-jar
On Fri, Sep 3, 2010 at 10:58 AM, Andrew Hughes wrote: > Hi Guys, > > When -Dmaven.test.skip=true the jar:test-jar goals are skipped. Other > modules who have a dependency on the jar:test-jar artifact then fail > (unresolved dependency). > > Is this a sensible default for the plugin and any idea's how I can override > this? > > Thanks heaps (again) :) > --Andrew > I've noticed this too. But when thinking about it, I *really* do want my tests to be working. So its important to fix them. One case where this is a problem is in integration tests and someone plays with the data in databases. Whole tests start failing. And then someone wants to cut a release ... So we work around this issue by doing -Dmaven.test.failure.ignore=true which still runs the tests, so the test-jar gets built, but ignores all failures. Dont do it often, but its in the toolbox for when you do. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
-Dmaven.test.skip=true && jar:test-jar
Hi Guys, When -Dmaven.test.skip=true the jar:test-jar goals are skipped. Other modules who have a dependency on the jar:test-jar artifact then fail (unresolved dependency). Is this a sensible default for the plugin and any idea's how I can override this? Thanks heaps (again) :) --Andrew
Re: Dependency:sources skipping files
File a jira, that might be an easy fix. On Wed, Sep 1, 2010 at 3:37 PM, C. Benson Manica wrote: > I see, that explains it, although I'm a little sad that -U doesn't force it > to download the sources again. > > On Tue, Aug 31, 2010 at 4:15 PM, Brian Fox wrote: > >> They don't exist and the dependency plugin has remembered this fact. >> It stores marker files in /target/dependency so if you run it many >> times it won't try to get the missing ones over and over. This goal >> dates to the days when the connection to central was unreliable and I >> was tired of having eclipse:eclipse -DdownloadSources=true fail in the >> middle. >> >> On Mon, Aug 30, 2010 at 11:01 AM, C. Benson Manica >> wrote: >> > I run mvn -U dependency:sources, and all my source jars are on an >> > Artifactory build server, but all the sources are "skipped" and nothing >> gets >> > downloaded. What causes Maven to "skip" downloading sources? >> > >> > -- >> > C. Benson Manica >> > cbman...@gmail.com >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > C. Benson Manica > cbman...@gmail.com > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Welcome Kristian Rosenvold to the Maven PMC
This is a little delayed, but still deserved. A few weeks ago, Kristian joined us on the Maven PMC. He's been driving a lot of interesting work in Maven 3 to support parallel builds. If you haven't tried that out yet, please do and send some feedback. Welcome Kristian! --Brian Fox Maven PMC Chair - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven 3.0-beta-3 Released
The Maven team is pleased to announce the release of Apache Maven 3.0-beta-3. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html This new beta version features a reworked repository system (Aether) and a new IoC container (based on Guice). We are already aware of a few regressions since 3.0-beta-2 due to these new components so we kindly ask users of the new beta to check our issue tracker for duplicate issues before filling new ones. The list of issues filled against the new 3.0-beta-3 can be seen via http://jira.codehaus.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+MNG+AND+affectedVersion+%3D+%223.0-beta-3%22&runQuery=true&clear=true Nevertheless, we highly appreciate feedback from our users on this new release to help us track down any other potential issues. If you encounter unexpected problems while using Maven 3.0-beta-3, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 & 3 - Version 3.0-beta-3 ** Bug * [MNG-2686] - POM dependency scope auto-downgrades from provided to test * [MNG-4690] - Transitive dependency lost when included another dependency * [MNG-4745] - [regression] Maven does not check for plugin updates, even if forced via -U * [MNG-4755] - Version ranges cannot be resolved against mirror if a local artifact is present * [MNG-4761] - Plugin-level dependency scope causes some plugin classpaths to be incorrect * [MNG-4765] - Failing to determine java version for profile * [MNG-4767] - Regression in parsing command-line arguments including variables * [MNG-4768] - Depending on declaration order, nearest matching version does not win when version range is involved in conflict * [MNG-4769] - Regression: flag for central cannot be overriden * [MNG-4771] - [regression] Plugin prefix resolution ignores enabled flags on repository * [MNG-4772] - [regression] Plugin version resolution ignores enabled flags on repository * [MNG-4773] - Stack trace printed from MavenProject.getParent * [MNG-4775] - Outdated NOTICE.txt * [MNG-4776] - NPE during build from parent but not from child * [MNG-4779] - NullPointerException thrown during dependency resolution when dependency with range occurs more than once in the dirty tree * [MNG-4781] - Can't deploy to Nexus staging repository ** Improvement * [MNG-4749] - Move from Plexus to Guice as IoC container * [MNG-4782] - Automatically dump stack trace in case of internal Maven error ** New Feature * [MNG-4756] - Aether integration Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
On Thu, Sep 2, 2010 at 5:58 PM, Pulkit Singhal wrote: > If someone on the list doesn't mind, and can guide me ... I would like > to put up an example w/o any of my mis-deeds ofcourse on the site that > hosts this one: > http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html > > How can I do that? Contribute to the Assembly plugin documentation? In brief, check out the source code from http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/ and look under src/site to find the source files. There are some resources here http://maven.apache.org/developers/index.html (probably more geared towards source code patches though.) Come join us on the dev list if you need help building it and generating the site. :) -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
If someone on the list doesn't mind, and can guide me ... I would like to put up an example w/o any of my mis-deeds ofcourse on the site that hosts this one: http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html How can I do that? On Thu, Sep 2, 2010 at 5:17 PM, Pulkit Singhal wrote: > Well commands you say ... hmm ... just doing: mvn clean install > and since that assembly:single goal should tie me into the maven > lifecycle, I suppose I felt this command was good enough? > > In addition, in the .m2 repo I see exactly: > ./m2/repository/parent/artifact-generating-child/artifact-xx.ABC > ./m2/repository/parent/artifact-generating-child/artifact-xx.pom > ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.jar > ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.pom > ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx-from-assembler.DEF > > Yes, there's no pom for artifact-xx.DEF > > I'll try and figure this out on my own, the main questions around > structure have been answered for me. .. I'm sure at this point it will > take my effort and not any additional info from the users to get it > done > > Thanks for the head start and good advice :) > > On Thu, Sep 2, 2010 at 5:04 PM, Wendy Smoak wrote: >> On Thu, Sep 2, 2010 at 4:59 PM, Pulkit Singhal >> wrote: >>> >>> ../artifact-generating-child/target >> ... >>> >>> ../assembly-based-artifact-generating-child/target >> >> Bad idea. Maven modules are intended to stand alone, not go wandering >> around the filesystem picking up stuff. >> >> Figure out why it can't get the artifacts from the repository like >> it's supposed to. My guess is that you are not using an assembly >> plugin goal that "attaches" the artifacts to the build, so they are >> not getting installed/deployed. >> >> You said you're using assembly:single. What commands are you >> executing and exactly do you see in your local repo after that? >> >> -- >> 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
Re: exclude META-INF/maven dirs
The question could be why ?? The solution is : ... org.apache.maven.plugins maven-jar-plugin 2.3.1 false ... ... See : http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#archive http://maven.apache.org/shared/maven-archiver/index.html cheers Arnaud On Sep 2, 2010, at 11:48 PM, woods5242-photogra...@yahoo.com wrote: > Hi, > New to maven. > > I have a basic project setup which is packaging a jar using the > maven-compiler-plugin. > > My resulting JAR is getting a /META-INF/maven directory with a bunch of stuff > in > it. How do I remove this or ensure that mvn package does not generate it? > > thanks > > > - > 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
exclude META-INF/maven dirs
Hi, New to maven. I have a basic project setup which is packaging a jar using the maven-compiler-plugin. My resulting JAR is getting a /META-INF/maven directory with a bunch of stuff in it. How do I remove this or ensure that mvn package does not generate it? thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly with modules of specific classifier
I don't about bug or not but I have this nagging feeling that if you
limited yourself to:
foo:bar-rpt:jar
it would work?
On Tue, Jun 22, 2010 at 12:48 AM, Adrian Shum wrote:
> Dear all,
>
> Assume I have a multi-module project "foo:bar",
> with several sub-modules, one of them is "foo:bar-rpt".
> I made an assembly descriptor in foo:bar-rpt to
> generate a jar with dependencies, with classifier
> "uber", and the generation is hooked at the package
> phase.
>
> I try to create a assembly descriptor in foo:bar,
> which will gather related modules and put in a
> directory. Here is what it looks like:
>
> allModules
>
> dir
>
>
>
>
> foo:bar-ear
> foo:bar-rpt:jar:uber
>
>
> modules/${artifactId}
>
> foo-${module.artifactId}-${module.version}${dashC
> lassifier?}.${module.extension}
> false
> false
>
>
>
>
>
>
> However, it failed to include bar-rpt-VERSION-uber.jar.
> Without defining classifier (i.e. foo:bar-rpt)
> it works fine, but that's not what I want.
>
> Did I misused moduleSet? or is it a bug?
>
> I am using maven 2.2.1, JDK 1.5.0-12
>
> Thanks a lot :)
>
> Alien
>
>
>
> This email is confidential. If you are not the intended recipient, please
> delete it from your system and notify the sender immediately. Any
> unauthorized use, disclosure, dissemination or copying of this email is
> prohibited. Taifook Securities Group, its group companies and their content
> providers ("Parties") shall not be responsible for the accuracy or
> completeness of this email or its attachment, if any, which could contain
> virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late.
> The Parties do not accept liability for any damage caused by this email.
>
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
Well commands you say ... hmm ... just doing: mvn clean install and since that assembly:single goal should tie me into the maven lifecycle, I suppose I felt this command was good enough? In addition, in the .m2 repo I see exactly: ./m2/repository/parent/artifact-generating-child/artifact-xx.ABC ./m2/repository/parent/artifact-generating-child/artifact-xx.pom ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.jar ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx.pom ./m2/repository/parent/assembly-based-artifact-generating-child/artifact-xx-from-assembler.DEF Yes, there's no pom for artifact-xx.DEF I'll try and figure this out on my own, the main questions around structure have been answered for me. .. I'm sure at this point it will take my effort and not any additional info from the users to get it done Thanks for the head start and good advice :) On Thu, Sep 2, 2010 at 5:04 PM, Wendy Smoak wrote: > On Thu, Sep 2, 2010 at 4:59 PM, Pulkit Singhal > wrote: >> >> ../artifact-generating-child/target > ... >> >> ../assembly-based-artifact-generating-child/target > > Bad idea. Maven modules are intended to stand alone, not go wandering > around the filesystem picking up stuff. > > Figure out why it can't get the artifacts from the repository like > it's supposed to. My guess is that you are not using an assembly > plugin goal that "attaches" the artifacts to the build, so they are > not getting installed/deployed. > > You said you're using assembly:single. What commands are you > executing and exactly do you see in your local repo after that? > > -- > 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
Re: Assembling multi-module artifacts
On Thu, Sep 2, 2010 at 4:59 PM, Pulkit Singhal wrote: > > ../artifact-generating-child/target ... > > ../assembly-based-artifact-generating-child/target Bad idea. Maven modules are intended to stand alone, not go wandering around the filesystem picking up stuff. Figure out why it can't get the artifacts from the repository like it's supposed to. My guess is that you are not using an assembly plugin goal that "attaches" the artifacts to the build, so they are not getting installed/deployed. You said you're using assembly:single. What commands are you executing and exactly do you see in your local repo after that? -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
Yup using fileSets tag rather than dependencySets worked. I simply don't know why given the following structure: parent-pom.xml |_artifact-generating-child-pom.xml |_assembly-based-artifact-generating-child-pom.xml |_assembly-based-parent-product-packaging-delegate-pom.xml The artifact-generating-child-pom.xml and assembly-based-artifact-generating-child-pom.xml publish to my local .m2 repo but the assembly-based-parent-product-packaging-delegate-pom.xml chooses not to pull fro mthere but instead go otu to the web and fail if it can't find anything in real maven repos. Did you folks out there get dependencySets to work or did you also resort to using fileSets when working with assembly-based-parent-product-packaging-delegate-pom.xml 's assembly-descriptor? parent:artifact-generating-child:abc parent:assembly-based-artifact-generating-child:def VERSUS ../artifact-generating-child/target / *.abc ../assembly-based-artifact-generating-child/target / *.def On Thu, Sep 2, 2010 at 4:41 PM, Pulkit Singhal wrote: > The sub-module is using the following goal for the assembler: > > package > > single > > > But I think perhaps my artifact is being installed locally > (/.m2/repository) and then for some strange reason the > fake-assembly-put-my-product-together project decides that it should > look at real repositories when looking for dependencySets and not my > local .m2 repo, I wonder why that could be. Perhaps I should switch > over to using fileSets tag? > > - Pulkit > > On Thu, Sep 2, 2010 at 4:36 PM, Wendy Smoak wrote: >> On Thu, Sep 2, 2010 at 4:26 PM, Pulkit Singhal >> wrote: >>> Thank You Anders & Wendy, that was a very educational link. >>> >>> But by moving the product assembler from the parent to a child >>> project, I've now run into a problem because i also have some of the >>> children of the parent pom building some packages using assemblers ... >>> their assembled stuff is not published in the repository (i wonder >>> why) ... and the fake-assembly-put-my-product-together project can't >>> download it from the repo so it chokes :( >> >> What assembly plugin goal are you using? You probably need to use one >> that 'attach'es those assemblies to the project so they get >> installed/deployed. >> >> -- >> 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
Re: Assembling multi-module artifacts
On 02/09/2010 4:26 PM, Pulkit Singhal wrote: Thank You Anders& Wendy, that was a very educational link. But by moving the product assembler from the parent to a child project, I've now run into a problem because i also have some of the children of the parent pom building some packages using assemblers ... their assembled stuff is not published in the repository (i wonder why) ... and the fake-assembly-put-my-product-together project can't download it from the repo so it chokes :( Any ideas? You might want to provide some more specifics about which POMs work and which ones do not. You have an error in your POM or assembly or parent. Hard to know where without more details. Remember: It works for everyone else. Given that fact, what do you need to tell us to find out what is not done correctly? Ron - Pulkit On Thu, Sep 2, 2010 at 3:06 PM, Anders Hammar wrote: Best-practice. Here's one reason: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries /Anders On Thu, Sep 2, 2010 at 20:54, Pulkit Singhalwrote: Do you mean structuring it like so: parent-maven-project |__childA-maven-project |__childB-maven-project |__childC-maven-project |__fake-assembly-project Is that the best-practice or the practical-practice? I ask because it feels a bit odd to have a parent for modules and then not use it for something like assembling the structure for the final releasable product based on the artifacts from its children. On Thu, Sep 2, 2010 at 2:43 PM, Wendy Smoak wrote: On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal wrote: In a multi-module project, I am attempting to provide the parent pom with an assembly descriptor which will pick up the artifacts from some of its children modules This works best if you put the assembly in its own module, not in the parent. -- 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 - 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: Assembling multi-module artifacts
The sub-module is using the following goal for the assembler: package single But I think perhaps my artifact is being installed locally (/.m2/repository) and then for some strange reason the fake-assembly-put-my-product-together project decides that it should look at real repositories when looking for dependencySets and not my local .m2 repo, I wonder why that could be. Perhaps I should switch over to using fileSets tag? - Pulkit On Thu, Sep 2, 2010 at 4:36 PM, Wendy Smoak wrote: > On Thu, Sep 2, 2010 at 4:26 PM, Pulkit Singhal > wrote: >> Thank You Anders & Wendy, that was a very educational link. >> >> But by moving the product assembler from the parent to a child >> project, I've now run into a problem because i also have some of the >> children of the parent pom building some packages using assemblers ... >> their assembled stuff is not published in the repository (i wonder >> why) ... and the fake-assembly-put-my-product-together project can't >> download it from the repo so it chokes :( > > What assembly plugin goal are you using? You probably need to use one > that 'attach'es those assemblies to the project so they get > installed/deployed. > > -- > 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
Re: Assembling multi-module artifacts
On Thu, Sep 2, 2010 at 4:26 PM, Pulkit Singhal wrote: > Thank You Anders & Wendy, that was a very educational link. > > But by moving the product assembler from the parent to a child > project, I've now run into a problem because i also have some of the > children of the parent pom building some packages using assemblers ... > their assembled stuff is not published in the repository (i wonder > why) ... and the fake-assembly-put-my-product-together project can't > download it from the repo so it chokes :( What assembly plugin goal are you using? You probably need to use one that 'attach'es those assemblies to the project so they get installed/deployed. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
Thank You Anders & Wendy, that was a very educational link. But by moving the product assembler from the parent to a child project, I've now run into a problem because i also have some of the children of the parent pom building some packages using assemblers ... their assembled stuff is not published in the repository (i wonder why) ... and the fake-assembly-put-my-product-together project can't download it from the repo so it chokes :( Any ideas? - Pulkit On Thu, Sep 2, 2010 at 3:06 PM, Anders Hammar wrote: > Best-practice. > Here's one reason: > http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries > > /Anders > > On Thu, Sep 2, 2010 at 20:54, Pulkit Singhal wrote: > >> Do you mean structuring it like so: >> >> parent-maven-project >> |__childA-maven-project >> |__childB-maven-project >> |__childC-maven-project >> |__fake-assembly-project >> >> Is that the best-practice or the practical-practice? >> >> I ask because it feels a bit odd to have a parent for modules and then >> not use it for something like assembling the structure for the final >> releasable product based on the artifacts from its children. >> >> On Thu, Sep 2, 2010 at 2:43 PM, Wendy Smoak wrote: >> > On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal >> wrote: >> >> In a multi-module project, I am attempting to provide the parent pom >> >> with an assembly descriptor which will pick up the artifacts from some >> >> of its children modules >> > >> > This works best if you put the assembly in its own module, not in the >> parent. >> > >> > -- >> > 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 >> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enforce Maven client to use credentials for read artifacts from repository
On 2010-08-31 22:18, Brian Fox wrote: > The http clients usually don't send the credentials until the server > requests them with a 403, then it will send them and good clients will > recall this and "pre-emptively" send the credentials for future > requests to that server. Maven doesn't pre-emptively send them by > default, but it is possible to set a flag to make this happen if you > really want to. We tried to force preemptive authentication with configuration taken from [1], but with no luck. Maven didn't sent credentials to configured server [2]. [1] - http://maven.apache.org/guides/mini/guide-http-settings.html [2] - https://jira.codehaus.org/browse/MNG-4792 Marcin > > 2010/8/30 Anders Hammar : >> I would check the logs on the repo manager. And possibly crank up the >> logging level. Nexus tells you the user that tries to access. I would assume >> Artifactory does similar. >> >> /Anders >> >> 2010/8/29 Marcin Zajączkowski >> >>> On 2010-08-29 14:06, Anders Hammar wrote: Sure, just match the id of the repo with the id of the server credentails >>> in settings.xml. >>> I tried: >>> >>> >>> >>> repo-id >>> user >>> password >>> (...) >>> >>> >>> >>> >>>true >>> >>> repo-id >>> repo-id >>> ... >>> (...) >>> >>> >>> In log I only see (it's a SNAPSHOT artifact): >>> (...) >>> [INFO] snapshot my-group-id:my-artifact-id:1.2.0-SNAPSHOT checking for >>> updates from repo-id >>> Downloading: >>> http://url/.../1.2.0-SNAPSHOT/my-artifact-id-1.2.0-SNAPSHOT.pom >>> [INFO] Unable to find resource >>> 'my-group-id:my-artifact-id:1.2.0-SNAPSHOT' in repository repo-id (url) >>> >>> Is there any easier way (than sniffing) to get know if maven uses >>> credentials to try to get artifact? >>> >>> >>> Marcin >>> >>> >>> 2010/8/28 Marcin Zajączkowski > Hi, > > > I need to set up a repository whose artifacts would be accessible (being > able to get using Maven client) only for authorized people (with account > like for deploy). I have an Artifactory server with a few publicly > available repositories and I added there a new one only for selected > people. It's not available for anonymous users, but I have one problem - > Maven client tries to connect as anonymous user and claims there are no > such artifact (server returns 404 Not Found). > > Is it possible to force Maven client to always connect to given > repository with user/password (defined in settings.xml) to *get* >>> artifacts? > > Regards > Marcin > > > - > 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: Assembling multi-module artifacts
On Thu, Sep 2, 2010 at 2:54 PM, Pulkit Singhal wrote: > Do you mean structuring it like so: > > parent-maven-project > |__childA-maven-project > |__childB-maven-project > |__childC-maven-project > |__fake-assembly-project > > Is that the best-practice or the practical-practice? > > I ask because it feels a bit odd to have a parent for modules and then > not use it for something like assembling the structure for the final > releasable product based on the artifacts from its children. Search the archives and JIRA for more info, but in brief there's a problem because the parent has to build first so it's available for the children, yet the assembly needs to build last because it needs the artifacts from the children. Your life will be much easier if you make the assembly a module of its own. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembling multi-module artifacts
Best-practice. Here's one reason: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries /Anders On Thu, Sep 2, 2010 at 20:54, Pulkit Singhal wrote: > Do you mean structuring it like so: > > parent-maven-project > |__childA-maven-project > |__childB-maven-project > |__childC-maven-project > |__fake-assembly-project > > Is that the best-practice or the practical-practice? > > I ask because it feels a bit odd to have a parent for modules and then > not use it for something like assembling the structure for the final > releasable product based on the artifacts from its children. > > On Thu, Sep 2, 2010 at 2:43 PM, Wendy Smoak wrote: > > On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal > wrote: > >> In a multi-module project, I am attempting to provide the parent pom > >> with an assembly descriptor which will pick up the artifacts from some > >> of its children modules > > > > This works best if you put the assembly in its own module, not in the > parent. > > > > -- > > 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 > >
Re: Assembling multi-module artifacts
Do you mean structuring it like so: parent-maven-project |__childA-maven-project |__childB-maven-project |__childC-maven-project |__fake-assembly-project Is that the best-practice or the practical-practice? I ask because it feels a bit odd to have a parent for modules and then not use it for something like assembling the structure for the final releasable product based on the artifacts from its children. On Thu, Sep 2, 2010 at 2:43 PM, Wendy Smoak wrote: > On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal > wrote: >> In a multi-module project, I am attempting to provide the parent pom >> with an assembly descriptor which will pick up the artifacts from some >> of its children modules > > This works best if you put the assembly in its own module, not in the parent. > > -- > 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
Re: Assembling multi-module artifacts
On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal wrote: > In a multi-module project, I am attempting to provide the parent pom > with an assembly descriptor which will pick up the artifacts from some > of its children modules This works best if you put the assembly in its own module, not in the parent. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin (version 2.1) question
I can say definitively that transitive was not intended for Copy/Unpack. I wrote these goals with a very specific use case and that was to be able to cherry-pick artifacts from this list. The xxx-dependencies goals where intended to support transitivity. On Wed, Sep 1, 2010 at 10:49 AM, EJ Ciramella wrote: > > > Actually, it very specifically says nothing about dependencies under > the copy goal. It merely says "artifacts." There is a difference... > > > This is why maven is so polarizing - either you love it or hate it. > > "specifically saying nothing" - it should be explicit... > > Thanks again all for the clarifications - I appreciate it! > > > CONFIDENTIALITY NOTICE: This e-mail and the information transmitted within > including any attachments is only for the recipient(s) to which it is > intended 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 send the > e-mail back by replying to the sender and permanently delete the entire > message and its attachments from all computers and network systems involved > in its receipt. > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembling multi-module artifacts
Hello, In a multi-module project, I am attempting to provide the parent pom with an assembly descriptor which will pick up the artifacts from some of its children modules and throw them in a folder. I'm doing this by closely following the instructions given here: http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html But one of the children happens to have an assembly descriptor of its own and the artifact resulting from that child module's assembly descriptor is not included in the artifacts that the parent is collecting. Is this a bug or is there some special configuration required? Thanks, - Pulkit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using distributet NetBeans from HP
why not try remote debugging from a different machine using a different OS? On 2 September 2010 14:53, Stadelmann Josef < josef.stadelm...@axa-winterthur.ch> wrote: > > > _ > Von: Stadelmann Josef > Gesendet: Donnerstag, 2. September 2010 15:15 > An: 'Maven Users List'; 'Distributed NetBeans for OpenVMS'; > 'nbus...@netbeans.org' > Betreff: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using > distributet NetBeans from HP > > > I have a very nice catch 22 situation > > Porting maven-2.2.1 to OpenVMS using NetBeans 5.5.1 and distributet > NetBeans from HP; > > I build it first in VISTA SP1, using a DOS Windows running as > administrator. The build works perfect. > > But building maven-2.2.1 using NetBeans 5.5. 1 with distributet NetBeans > from HP is a mess. > I get the following errors, (not running as administrator) > > clean-bootstrap: > Deleting directory C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap > initTaskDefs: > isMavenHomeSet: > Using Maven home at: C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1 > initLocalRepo: > Using the local repository at: C:\Users\C770817\.m2\repository > init: > maven.home = C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1 > maven.assembly = > C:\asf\maven\maven-2\tags\maven-2.2.1\apache-maven\target\apache-maven-2 > .2.1-bin.zip > read-poms: > Copying 1 file to C:\asf\maven\maven-2\tags\maven-2.2.1 > Deleting: C:\asf\maven\maven-2\tags\maven-2.2.1\dependencies.xml > pull: > generate-sources: > Created dir: C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target > Created dir: > C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target\generated-sources > Generating sources for maven-model/src/main/mdo/maven.mdo > C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:147: The following error > occurred while executing this line: > C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:141: The following error > occurred while executing this line: > C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:123: > java.lang.SecurityException > BUILD FAILED (total time: 1 minute 5 seconds) > > Why a security exception, how can I avoid it? > Then starting NetBeans 5.5.1 using RUN AS ADMINISTRATOR to hopefully > prevent the security exception > Is a no go too and results results in a crash and leaves two processes > on the system during startup of NB > > Java.lang.NoClassDefFoundError: > org/netbenas/modules/project/ui/OpenProjectList >At > org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.searchFS(Unkn > own Source) >At > org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.MOUNTfs(Unkno > wn Source) >At > org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.GETfILEOBJECT > S(Unknown Source) >At > org.OPENIDE.FILESYSTEM.urlmAPPER.FINDfILEoBJECT(urlmAPPER.Java:196)) > . > > Why does Modello demand privileges to generate code using this target > during a maven-2.2.1 boot-strat-build > > > > > > > > > > > 123 failonerror="true"> > > > > > > > > > > > > > > > > > > 141 mode="java"/> > mode="xpp3-reader"/> > mode="xpp3-writer"/> > > > > 147 > > > file="maven-plugin-parameter-documenter/src/main/mdo/paramdoc.mdo"/> > > > file="maven-repository-metadata/src/main/mdo/metadata.mdo"/> > > > > > I am open for any kind of hints, and I can't use maven 3 because we have > projects which are not yet mavenized for version3 of maven. > > Also, I wan't to debug maven-2.2.1 to see if and how proxy > authentication works using the BASIC authentication scheme > on HP OpenVMS with JDK 5.0 e all. > > And yes; > using a higher version of NetBeans leaves renders my netbeans project > files in a way that I can't open it thereafter in NetBeans 5.5.1 > > Beautifull dependencies :-) > > Josef - with catch 22's > >
WG: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using distributet NetBeans from HP
_ Von: Stadelmann Josef Gesendet: Donnerstag, 2. September 2010 15:15 An: 'Maven Users List'; 'Distributed NetBeans for OpenVMS'; 'nbus...@netbeans.org' Betreff: catch 22s building Maven-2.2.1 with NetBeans 5.5.1 using distributet NetBeans from HP I have a very nice catch 22 situation Porting maven-2.2.1 to OpenVMS using NetBeans 5.5.1 and distributet NetBeans from HP; I build it first in VISTA SP1, using a DOS Windows running as administrator. The build works perfect. But building maven-2.2.1 using NetBeans 5.5. 1 with distributet NetBeans from HP is a mess. I get the following errors, (not running as administrator) clean-bootstrap: Deleting directory C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap initTaskDefs: isMavenHomeSet: Using Maven home at: C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1 initLocalRepo: Using the local repository at: C:\Users\C770817\.m2\repository init: maven.home = C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1 maven.assembly = C:\asf\maven\maven-2\tags\maven-2.2.1\apache-maven\target\apache-maven-2 .2.1-bin.zip read-poms: Copying 1 file to C:\asf\maven\maven-2\tags\maven-2.2.1 Deleting: C:\asf\maven\maven-2\tags\maven-2.2.1\dependencies.xml pull: generate-sources: Created dir: C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target Created dir: C:\asf\maven\maven-2\tags\maven-2.2.1\bootstrap\target\generated-sources Generating sources for maven-model/src/main/mdo/maven.mdo C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:147: The following error occurred while executing this line: C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:141: The following error occurred while executing this line: C:\asf\maven\maven-2\tags\maven-2.2.1\build.xml:123: java.lang.SecurityException BUILD FAILED (total time: 1 minute 5 seconds) Why a security exception, how can I avoid it? Then starting NetBeans 5.5.1 using RUN AS ADMINISTRATOR to hopefully prevent the security exception Is a no go too and results results in a crash and leaves two processes on the system during startup of NB Java.lang.NoClassDefFoundError: org/netbenas/modules/project/ui/OpenProjectList At org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.searchFS(Unkn own Source) At org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.MOUNTfs(Unkno wn Source) At org.netbeans.modules.distributed.remotefs.MyURLMapperProxy.GETfILEOBJECT S(Unknown Source) At org.OPENIDE.FILESYSTEM.urlmAPPER.FINDfILEoBJECT(urlmAPPER.Java:196)) . Why does Modello demand privileges to generate code using this target during a maven-2.2.1 boot-strat-build 123 141 147 I am open for any kind of hints, and I can't use maven 3 because we have projects which are not yet mavenized for version3 of maven. Also, I wan't to debug maven-2.2.1 to see if and how proxy authentication works using the BASIC authentication scheme on HP OpenVMS with JDK 5.0 e all. And yes; using a higher version of NetBeans leaves renders my netbeans project files in a way that I can't open it thereafter in NetBeans 5.5.1 Beautifull dependencies :-) Josef - with catch 22's
Re: Where to find the "jboss-ejb3x.jar" fro mthe central maven-repo?
You should use one of the repos at JBoss's new Nexus instance instead. Have a look here https://repository.jboss.org/nexus/ and also read info on the JBoss wiki. /Anders On Thu, Sep 2, 2010 at 13:00, Erlend Hamnaberg wrote: > Have you looked in http://repository.jboss.org? > > On Thu, Sep 2, 2010 at 9:02 AM, thomas2004ch > wrote: > > > > > I need the jboss-ejb3x.jar in my project and want to put it into my > pom.xml > > as . But I couldn't find this jboss-ejb3x.jar any where from > > the central maven-repo. > > > > Maybe someone knows? > > > > Regards > > > > Thomas > > -- > > View this message in context: > > > http://maven.40175.n5.nabble.com/Where-to-find-the-jboss-ejb3x-jar-fro-mthe-central-maven-repo-tp2800224p2800224.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: mvn package
I dont believe antlr has compile goal in any of the V2 plugins try one of the
antlr-plugins such as maven-castor-plugin
In the event you do'nt have internet access and want to demo offline try
download ANTLR from svn checkout http://svn.codehaus.org/mojo/trunk mojo
cd mojo
--determine which folder you will need e.g. solaris / weblogic / was6 ..I use
castor alot so i cd castor-maven-plugin
cd castor-maven-plugin
mvn compile
mvn package
--install to local repository
mvn install:install-file -DgroupId=org.codehaus.mojo
-DartifactId=castor-maven-plugin
-Dversion=2.1-SNAPSHOT -Dfile=pom.xml -Dpackaging=pom
--make SURE the maven-plugin's plugin.xml is located in
./META-INF/maven/plugin.xml then install
mvn install:install-file -DgroupId=org.codehaus.mojo
-DartifactId=castor-maven-plugin
-Dversion=2.1-SNAPSHOT -Dfile=pom.xml -Dpackaging=maven-plugin
--you *can* mvn deploy:deploy-file or simply copy the file up such as what is
seen here
cp ./target/castor-maven-plugin-2.1-SNAPSHOT.jar
.${user.home}/.m2/repository/org/codehaus/mojo/target/castor-maven-plugin-2.1-SNAPSHOT.jar
--to test grep for all goals in *Mojo.java
grep -S -l "@goal" *Mojo.java
--i've determined there is a help goal so i will call the help goal of
castor-maven-plugin with
mvn -e -X org.codehaus.mojo:castor-maven-plugin:2.1-SNAPSHOT:help
i've experienced this same problem with struts-plugins and have used this
methodology successfully
Ciao
Martin
__
Verzicht und Vertraulichkeitanmerkung
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Date: Thu, 2 Sep 2010 11:45:34 +0200
> Subject: Re: mvn package
> From: antonio.petre...@gmail.com
> To: users@maven.apache.org; dri...@visetics.com
>
> 2010/9/2 Daniel Rindt :
> > Am Donnerstag, den 02.09.2010, 11:17 +0200 schrieb Antonio Petrelli:
> >> It seems that in your pom you specify explicitly the need of Maven
> >> 2.0.9. What do you see when you run mvn -version?
> > It was as you mentioned. I updated maven2 by hand to 2.2.1, but now i
> > got next errors during the packaging task.
> > ...
> > [WARNING] POM for 'antlr:antlr:pom:2.7.6:compile' is invalid.
> > ...
> > error: error
> > reading /home/drindt/.m2/repository/antlr/antlr/2.7.6/antlr-2.7.6.jar;
> > error in opening zip file
>
> AFAICT, it seems that you have a problem with accessing your local
> repository, maybe they cannot be accessed or they are corrupt.
> This is strange. Did you try with a normal Maven distribution?
>
> Antonio
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
Stack trace output maven
Hi, My test execution in maven takes around 1 hr as I have 100+ Testcases. Surefire plugin generates reports only after all tests are run. What I want is to have the report right after first testcase, and then so on after each testcase, is there any way I can do this in maven? Please let me know thnkx sridharl
Re: Where to find the "jboss-ejb3x.jar" fro mthe central maven-repo?
Have you looked in http://repository.jboss.org? On Thu, Sep 2, 2010 at 9:02 AM, thomas2004ch wrote: > > I need the jboss-ejb3x.jar in my project and want to put it into my pom.xml > as . But I couldn't find this jboss-ejb3x.jar any where from > the central maven-repo. > > Maybe someone knows? > > Regards > > Thomas > -- > View this message in context: > http://maven.40175.n5.nabble.com/Where-to-find-the-jboss-ejb3x-jar-fro-mthe-central-maven-repo-tp2800224p2800224.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: Release of the site plugin?
Hi, I'm currently waiting the end of beta-3 core release process. 2010/9/1 Steve Jerman : > ... thanks for the answer. I tried with the snapshot and it works... any idea > when the release of the new beta will happen > > Steve > > On Sep 1, 2010, at 9:31 AM, Steve Jerman wrote: > >> Hi, >> >> I have tried out Maven-3 Beta-3, and the site plugin is failing due to a API >> change from beta-2 to beta-3. Does anyone know if/when a release of the site >> plugin will be made to match the Beta-3 API? >> >> Steve >> >> [INFO] >> >> [INFO] Reactor Summary: >> [INFO] >> [INFO] XMP-IM Modules FAILURE [0.866s] >> [INFO] Artifacts Parent .. SKIPPED >> [INFO] xmp-im-foundation-module artifacts SKIPPED >> [INFO] xmp-im-location-module artifacts .. SKIPPED >> [INFO] xmp-im-party-module artifacts . SKIPPED >> [INFO] xmp-im-physical-resource-module artifacts . SKIPPED >> [INFO] xmp-im-connectivity-module artifacts .. SKIPPED >> [INFO] xmp-im-logical-resource-module artifacts .. SKIPPED >> [INFO] xmp-im-res-mgr-module artifacts ... SKIPPED >> [INFO] ca-im-module artifacts SKIPPED >> [INFO] xmp-im-discovery-module artifacts . SKIPPED >> [INFO] xmp-im-events-alarms artifacts SKIPPED >> [INFO] xmp-im-file-system-module artifacts ... SKIPPED >> [INFO] xmp-im-job-module artifacts ... SKIPPED >> [INFO] xmp-im-link-aggregation-module artifacts .. SKIPPED >> [INFO] xmp-im-software artifacts . SKIPPED >> [INFO] xmp-im-process artifacts .. SKIPPED >> [INFO] xmp-im-sensor-module artifacts SKIPPED >> [INFO] xmp-im-switch-module artifacts SKIPPED >> [INFO] xmp-im-vlan-module artifacts .. SKIPPED >> [INFO] xmp-im-test ... SKIPPED >> [INFO] Update site creation parent POM ... SKIPPED >> [INFO] Common Models Feature . SKIPPED >> [INFO] Common Modules Update Site SKIPPED >> [INFO] >> >> [INFO] BUILD FAILURE >> [INFO] >> >> [INFO] Total time: 9.501s >> [INFO] Finished at: Wed Sep 01 07:35:53 PDT 2010 >> [INFO] Final Memory: 28M/554M >> [INFO] >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site (default-site) on >> project aggregate: Execution default-site of goal >> org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site failed: An API >> incompatibility was encountered while executing >> org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site: >> java.lang.NoSuchMethodError: >> org.apache.maven.plugin.MavenPluginManager.getPluginDescriptor(Lorg/apache/maven/model/Plugin;Lorg/apache/maven/artifact/repository/RepositoryRequest;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; >> - >> realm = plugin>org.apache.maven.plugins:maven-site-plugin:3.0-beta-1 >> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy >> urls[0] = >> file:/Users/steve/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0-beta-1/maven-site-plugin-3.0-beta-1.jar >> urls[1] = >> file:/Users/steve/.m2/repository/com/cisco/build/doxia-macros/0.0.3/doxia-macros-0.0.3.jar >> urls[2] = >> file:/Users/steve/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar >> urls[3] = >> file:/Users/steve/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar >> urls[4] = >> file:/Users/steve/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar >> urls[5] = >> file:/Users/steve/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar >> urls[6] = >> file:/Users/steve/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar >> urls[7] = >> file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.1.3/doxia-sink-api-1.1.3.jar >> urls[8] = >> file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.1.3/doxia-logging-api-1.1.3.jar >> urls[9] = >> file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.3/doxia-core-1.1.3.jar >> urls[10] = >> file:/Users/steve/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar >> urls[11] = >> file:/Users/steve/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar >> urls[12] = >> file:/Users/st
Re: mvn package
Am Donnerstag, den 02.09.2010, 11:45 +0200 schrieb Antonio Petrelli: > > AFAICT, it seems that you have a problem with accessing your local > repository, maybe they cannot be accessed or they are corrupt. > This is strange. Did you try with a normal Maven distribution? Yes, the problem was maybe the version maven2-2.0.8, had problems with repositories defined in the pom.xml. I cleaned up the repositories in pom.xml and define just jboss repo. After deletion of ~/.m2 and rerun mvn package it runs properly. Thanks for your support Antonio. Daniel signature.asc Description: This is a digitally signed message part
Re: mvn package
2010/9/2 Daniel Rindt : > Am Donnerstag, den 02.09.2010, 11:17 +0200 schrieb Antonio Petrelli: >> It seems that in your pom you specify explicitly the need of Maven >> 2.0.9. What do you see when you run mvn -version? > It was as you mentioned. I updated maven2 by hand to 2.2.1, but now i > got next errors during the packaging task. > ... > [WARNING] POM for 'antlr:antlr:pom:2.7.6:compile' is invalid. > ... > error: error > reading /home/drindt/.m2/repository/antlr/antlr/2.7.6/antlr-2.7.6.jar; > error in opening zip file AFAICT, it seems that you have a problem with accessing your local repository, maybe they cannot be accessed or they are corrupt. This is strange. Did you try with a normal Maven distribution? Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn package
Am Donnerstag, den 02.09.2010, 11:17 +0200 schrieb Antonio Petrelli:
> It seems that in your pom you specify explicitly the need of Maven
> 2.0.9. What do you see when you run mvn -version?
It was as you mentioned. I updated maven2 by hand to 2.2.1, but now i
got next errors during the packaging task.
=== 8< ===
[dri...@localhost xxx]$ mvn -e package
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building xxx Webapp
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 2 resources
[WARNING] POM for 'antlr:antlr:pom:2.7.6:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for
'commons-collections:commons-collections:pom:3.1:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'dom4j:dom4j:pom:1.6.1:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'commons-logging:commons-logging:pom:1.1.1:compile' is
invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'ognl:ognl:pom:2.7.3:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for
'commons-fileupload:commons-fileupload:pom:1.2.1:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'commons-io:commons-io:pom:1.3.2:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for 'mysql:mysql-connector-java:pom:5.1.13:compile' is
invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 1 source file
to /home/drindt/Programmierung/xxx/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
error: error
reading /home/drindt/.m2/repository/antlr/antlr/2.7.6/antlr-2.7.6.jar;
error in opening zip file
error: error
reading
/home/drindt/.m2/repository/commons-collections/commons-collections/3.1/commons-collections-3.1.jar;
error in opening zip file
error: error
reading /home/drindt/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar;
error in opening zip file
error: error
reading
/home/drindt/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar;
error in opening zip file
error: error
reading /home/drindt/.m2/repository/ognl/ognl/2.7.3/ognl-2.7.3.jar;
error in opening zip file
error: error
reading
/home/drindt/.m2/repository/commons-fileupload/commons-fileupload/1.2.1/commons-fileupload-1.2.1.jar;
error in opening zip file
error: error
reading
/home/drindt/.m2/repository/commons-io/commons-io/1.3.2/commons-io-1.3.2.jar;
error in opening zip file
error: error
reading
/home/drindt/.m2/repository/mysql/mysql-connector-java/5.1.13/mysql-connector-java-5.1.13.jar;
error in opening zip file
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.
Re: mvn package
2010/9/2 Daniel Rindt : > [INFO] Error resolving version for > 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven > version 2.0.9 It seems that in your pom you specify explicitly the need of Maven 2.0.9. What do you see when you run mvn -version? Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release of the site plugin?
... thanks for the answer. I tried with the snapshot and it works... any idea when the release of the new beta will happen Steve On Sep 1, 2010, at 9:31 AM, Steve Jerman wrote: > Hi, > > I have tried out Maven-3 Beta-3, and the site plugin is failing due to a API > change from beta-2 to beta-3. Does anyone know if/when a release of the site > plugin will be made to match the Beta-3 API? > > Steve > > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] XMP-IM Modules FAILURE [0.866s] > [INFO] Artifacts Parent .. SKIPPED > [INFO] xmp-im-foundation-module artifacts SKIPPED > [INFO] xmp-im-location-module artifacts .. SKIPPED > [INFO] xmp-im-party-module artifacts . SKIPPED > [INFO] xmp-im-physical-resource-module artifacts . SKIPPED > [INFO] xmp-im-connectivity-module artifacts .. SKIPPED > [INFO] xmp-im-logical-resource-module artifacts .. SKIPPED > [INFO] xmp-im-res-mgr-module artifacts ... SKIPPED > [INFO] ca-im-module artifacts SKIPPED > [INFO] xmp-im-discovery-module artifacts . SKIPPED > [INFO] xmp-im-events-alarms artifacts SKIPPED > [INFO] xmp-im-file-system-module artifacts ... SKIPPED > [INFO] xmp-im-job-module artifacts ... SKIPPED > [INFO] xmp-im-link-aggregation-module artifacts .. SKIPPED > [INFO] xmp-im-software artifacts . SKIPPED > [INFO] xmp-im-process artifacts .. SKIPPED > [INFO] xmp-im-sensor-module artifacts SKIPPED > [INFO] xmp-im-switch-module artifacts SKIPPED > [INFO] xmp-im-vlan-module artifacts .. SKIPPED > [INFO] xmp-im-test ... SKIPPED > [INFO] Update site creation parent POM ... SKIPPED > [INFO] Common Models Feature . SKIPPED > [INFO] Common Modules Update Site SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 9.501s > [INFO] Finished at: Wed Sep 01 07:35:53 PDT 2010 > [INFO] Final Memory: 28M/554M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site (default-site) on > project aggregate: Execution default-site of goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site failed: An API > incompatibility was encountered while executing > org.apache.maven.plugins:maven-site-plugin:3.0-beta-1:site: > java.lang.NoSuchMethodError: > org.apache.maven.plugin.MavenPluginManager.getPluginDescriptor(Lorg/apache/maven/model/Plugin;Lorg/apache/maven/artifact/repository/RepositoryRequest;)Lorg/apache/maven/plugin/descriptor/PluginDescriptor; > - > realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.0-beta-1 > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > urls[0] = > file:/Users/steve/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0-beta-1/maven-site-plugin-3.0-beta-1.jar > urls[1] = > file:/Users/steve/.m2/repository/com/cisco/build/doxia-macros/0.0.3/doxia-macros-0.0.3.jar > urls[2] = > file:/Users/steve/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar > urls[3] = > file:/Users/steve/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar > urls[4] = > file:/Users/steve/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar > urls[5] = > file:/Users/steve/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar > urls[6] = > file:/Users/steve/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar > urls[7] = > file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.1.3/doxia-sink-api-1.1.3.jar > urls[8] = > file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.1.3/doxia-logging-api-1.1.3.jar > urls[9] = > file:/Users/steve/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.3/doxia-core-1.1.3.jar > urls[10] = > file:/Users/steve/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar > urls[11] = > file:/Users/steve/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar > urls[12] = > file:/Users/steve/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar > urls[13] = > file:/Users/steve/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3
Where to find the "jboss-ejb3x.jar" fro mthe central maven-repo?
I need the jboss-ejb3x.jar in my project and want to put it into my pom.xml as . But I couldn't find this jboss-ejb3x.jar any where from the central maven-repo. Maybe someone knows? Regards Thomas -- View this message in context: http://maven.40175.n5.nabble.com/Where-to-find-the-jboss-ejb3x-jar-fro-mthe-central-maven-repo-tp2800224p2800224.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
mvn package
Hello, i couldn't package my project anymore. I am using the provided Maven2 packages of my linux distribution. So can't understand why the version mismatch is here. The ~/.m2 directory i have temporary moved, but that seems not the problem. Please take a look here: === 8< === $ mvn package /usr [INFO] Scanning for projects... [INFO] [INFO] Building Webapp [INFO]task-segment: [package] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error resolving version for 'org.apache.maven.plugins:maven-compiler-plugin': Plugin requires Maven version 2.0.9 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Thu Sep 02 10:41:34 CEST 2010 [INFO] Final Memory: 2M/4M [INFO] [dri...@localhost ]$ rpm -qa|grep maven maven-surefire-2.3-7.7.fc12.noarch maven2-plugin-compiler-2.0.8-3.fc12.noarch maven-scm-1.2-5.fc13.noarch maven-shared-invoker-2.0.7-4.fc13.noarch maven-shared-test-tools-1.0-4.fc13.noarch maven-shared-plugin-testing-tools-1.0-4.fc13.noarch maven-wagon-1.0-0.2.b2.7.fc12.noarch maven-shared-verifier-1.2-4.fc13.noarch maven2-2.0.8-3.fc12.noarch maven-jxr-2.1-6.fc12.noarch maven-enforcer-rule-api-1.0-0.1.a2.1.5.fc12.noarch maven-shared-common-artifact-filters-1.0-4.fc13.noarch maven-doxia-1.0-0.8.a10.4.fc13.noarch maven-shared-io-1.1-4.fc13.noarch maven2-plugin-eclipse-2.0.8-3.fc12.noarch maven2-common-poms-1.0-12.fc13.noarch maven-scm-test-1.2-5.fc13.noarch maven-shared-8-4.fc13.noarch maven-shared-monitor-1.0-4.fc13.noarch maven-shared-repository-builder-1.0-4.fc13.noarch maven-shared-jar-1.1-4.fc13.noarch maven-shared-model-converter-2.3-4.fc13.noarch maven-shared-file-management-1.2-4.fc13.noarch === >8 === maybe the package "maven2-plugin-compiler" is not providing the capabilities for the "maven-compiler-plugin". How can i fix that? Thanks in advance Daniel signature.asc Description: This is a digitally signed message part
Re: Why my OpenQA repository is not used..?
If these are dependencies of a plugin, you may need to list a
as well. Otherwise it's not quite clear from what you've
included.
Regardless, I'd recommend upgrading to the newer versions of Selenium (and if
you're using it, the Selenium Maven Plugin). They're backwards compatible, and
already present on central.
- Brett
On 02/09/2010, at 5:06 PM, Stephane-3 wrote:
>
> Hello,
>
> I get an unresolved dependency with Selenium.
>
> Maven is looking for it in the wrong repository I think..
>
> [INFO] [resources:resources {execution: default-resources}]
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> /home/stephane/dev/java/project/thalasoft-webtest/src/main/resources
> Downloading:
> http://repo1.maven.org/maven2/org/openqa/selenium/server/selenium-server/1.0-beta-1/selenium-server-1.0-beta-1.pom
> [INFO] Unable to find resource
> 'org.openqa.selenium.server:selenium-server:pom:1.0-beta-1' in repository
> central (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/org/openqa/selenium/client-drivers/selenium-java-client-driver/1.0-beta-1/selenium-java-client-driver-1.0-beta-1.pom
> [INFO] Unable to find resource
> 'org.openqa.selenium.client-drivers:selenium-java-client-driver:pom:1.0-beta-1'
> in repository central (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/org/openqa/selenium/client-drivers/selenium-java-client-driver/1.0-beta-1/selenium-java-client-driver-1.0-beta-1.jar
> Downloading:
> http://repo1.maven.org/maven2/org/openqa/selenium/server/selenium-server/1.0-beta-1/selenium-server-1.0-beta-1.jar
> [INFO] Unable to find resource
> 'org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1'
> in repository central (http://repo1.maven.org/maven2)
> [INFO] Unable to find resource
> 'org.openqa.selenium.server:selenium-server:jar:1.0-beta-1' in repository
> central (http://repo1.maven.org/maven2)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1)
> org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.openqa.selenium.client-drivers
> -DartifactId=selenium-java-client-driver -Dversion=1.0-beta-1
> -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.openqa.selenium.client-drivers
> -DartifactId=selenium-java-client-driver -Dversion=1.0-beta-1
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
> 2)
> org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1
>
> 2) org.openqa.selenium.server:selenium-server:jar:1.0-beta-1
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.openqa.selenium.server
> -DartifactId=selenium-server -Dversion=1.0-beta-1 -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.openqa.selenium.server
> -DartifactId=selenium-server -Dversion=1.0-beta-1 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
> 2) org.openqa.selenium.server:selenium-server:jar:1.0-beta-1
>
> --
> 2 required artifacts are missing.
>
> for artifact:
> com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Thu Sep 02 08:49:28 CEST 2010
> [INFO] Final Memory: 6M/15M
> [INFO]
>
>
>
> I wonder what to do..
>
> I have the following content in the file .m2/.settings.xml
>
>
> http://maven.apache.org/SETTINGS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd";>
>
>org.grails
>org.mortbay.jetty
>
>
>
>
>true
>
>
>
>
Why my OpenQA repository is not used..?
Hello,
I get an unresolved dependency with Selenium.
Maven is looking for it in the wrong repository I think..
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/home/stephane/dev/java/project/thalasoft-webtest/src/main/resources
Downloading:
http://repo1.maven.org/maven2/org/openqa/selenium/server/selenium-server/1.0-beta-1/selenium-server-1.0-beta-1.pom
[INFO] Unable to find resource
'org.openqa.selenium.server:selenium-server:pom:1.0-beta-1' in repository
central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/openqa/selenium/client-drivers/selenium-java-client-driver/1.0-beta-1/selenium-java-client-driver-1.0-beta-1.pom
[INFO] Unable to find resource
'org.openqa.selenium.client-drivers:selenium-java-client-driver:pom:1.0-beta-1'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/openqa/selenium/client-drivers/selenium-java-client-driver/1.0-beta-1/selenium-java-client-driver-1.0-beta-1.jar
Downloading:
http://repo1.maven.org/maven2/org/openqa/selenium/server/selenium-server/1.0-beta-1/selenium-server-1.0-beta-1.jar
[INFO] Unable to find resource
'org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1'
in repository central (http://repo1.maven.org/maven2)
[INFO] Unable to find resource
'org.openqa.selenium.server:selenium-server:jar:1.0-beta-1' in repository
central (http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.openqa.selenium.client-drivers
-DartifactId=selenium-java-client-driver -Dversion=1.0-beta-1
-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.openqa.selenium.client-drivers
-DartifactId=selenium-java-client-driver -Dversion=1.0-beta-1
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
2)
org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:1.0-beta-1
2) org.openqa.selenium.server:selenium-server:jar:1.0-beta-1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.openqa.selenium.server
-DartifactId=selenium-server -Dversion=1.0-beta-1 -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.openqa.selenium.server
-DartifactId=selenium-server -Dversion=1.0-beta-1 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
2) org.openqa.selenium.server:selenium-server:jar:1.0-beta-1
--
2 required artifacts are missing.
for artifact:
com.thalasoft.webtest:thalasoft-webtest:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Sep 02 08:49:28 CEST 2010
[INFO] Final Memory: 6M/15M
[INFO]
I wonder what to do..
I have the following content in the file .m2/.settings.xml
http://maven.apache.org/SETTINGS/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
org.grails
org.mortbay.jetty
true
OpenQA
OpenQA repository
true
false
http://nexus.openqa.org/content/repositories/releases/
maven2
Maven2 repository
true
false
http://repo2.maven.org/maven2/
ibiblio
ibiblio repository
true
false
http://www.ibiblio.org/maven/
maven
