Re: Custom Plugin adding project dependencies to Plugin classpath
> How do I enhance my plugin classpath with the project dependencies? I found > some old posts none of them seem to work. Can you not specify them yourself manually? If the plugin needs them, it needs to declare that somewhere so Maven can provide them at the proper time. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 409 Conflict - snapshots/releases repositories
Hey! Yeah, I'm using artifactory, and I'll post on their list, thanks for the advice. But just for the record, I've found something interesting: If I mark my snapshots repo to handle releases, I don't get the 409. Looks like Maven can then search for the artifacts there without problems. If the artifactory is NOT supposed to handle releases, and on client I say that the repository CAN handle releases, a conflict pops up. I'll see what I get on artifactory list. Thanks! On Fri, May 4, 2012 at 12:50 PM, Olivier Lamy wrote: > Hi, > The best is to ask artifactory (it looks to be the mrm you use) mailing > list. > > 2012/5/4 Vitor Miranda : > > The error: > > > > "ArtifactDescriptorException: Failed to read artifact descriptor for > > javax.faces:jsf-api:jar:1_1_01: ArtifactResolutionException: Could not > > transfer artifact javax.faces:jsf-api:pom:1_1_01 from/to snapshots-repo ( > > http://ip/artifactory/snapshots-repo): Failed to transfer > > > http://ip/artifactory/snapshots-repo/javax/faces/jsf-api/1_1_01/jsf-api-1_1_01.pom > . > > Error code 409, Conflict" > > > > Hi! > > > > Anyone know exactly what happens when you set > > true on the > > repository section? The documentation and my intuition said that, if you > > set one to false, Maven won't even care to search/download the specified > > type of artifact from that repository. If it's true, Maven will look on > > that repository for that type of the artifact . If it doesn't find, just > go > > on and look on other repositories, if any are defined. Fair enough to me, > > but I had this issue which took me hours to solve: > > > > We have four repositories. > > > > - Snapshots > > - Releases (which is empty so far) > > - External > > - Release/Legacy (was the first repo created, will migrate to External > soon) > > > > The first two are what they are meant to, External is a repository for > the > > 3rd party artifacts that we use (no snapshots there) and Legacy also has > > 3rd party artifacts (no snapshots also). Then there's this POM which > > references three other POMs, which then have dependencies. All were > > deployed on the Snapshots repo. Some of the jar dependencies were on > > legacy, others on external. I was getting the infamous 409 - Conflict at > 3 > > or 4 artifacts when adding one of the "super poms" as a dependency - > > doesn't happen when adding a specifc jar dependency. > > > > Solution: set false on the > > snapshots repo configuration. > > > > Why? I don't get this. It's ok to filter releases/snapshots to the > correct > > repositories, but why this error? To show an example: when adding the > > highest parent pom, I get the 409 I pasted above on 4 artifacts. All of > > those are on legacy, and none is a snapshot. So maven tries to get a > > release-type artifact from a snapshot repo only. Obviously there's > nothing > > there (but I didn't specify Maven to not get from it (enabled is true), > so > > it's ok). What I'd expect to happen: can't find the artifact here (which, > > in case, there actually ISN'T any similar artifact there), I'll just move > > to the other repositories. What happens: 409. > > > > At least we found a solution, but I'd appreciate any help on > understanding > > this issue. > > > > Thanks! > > > > -- > > Vitor Branco de Miranda > > BCC - UFSCar - São Carlos/SP > > +55 19 92013531 > > vitorbmira...@gmail.com > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Vitor Branco de Miranda BCC - UFSCar - São Carlos/SP +55 19 92013531 vitorbmira...@gmail.com
Re: 409 Conflict - snapshots/releases repositories
Hi, The best is to ask artifactory (it looks to be the mrm you use) mailing list. 2012/5/4 Vitor Miranda : > The error: > > "ArtifactDescriptorException: Failed to read artifact descriptor for > javax.faces:jsf-api:jar:1_1_01: ArtifactResolutionException: Could not > transfer artifact javax.faces:jsf-api:pom:1_1_01 from/to snapshots-repo ( > http://ip/artifactory/snapshots-repo): Failed to transfer > http://ip/artifactory/snapshots-repo/javax/faces/jsf-api/1_1_01/jsf-api-1_1_01.pom. > Error code 409, Conflict" > > Hi! > > Anyone know exactly what happens when you set > true on the > repository section? The documentation and my intuition said that, if you > set one to false, Maven won't even care to search/download the specified > type of artifact from that repository. If it's true, Maven will look on > that repository for that type of the artifact . If it doesn't find, just go > on and look on other repositories, if any are defined. Fair enough to me, > but I had this issue which took me hours to solve: > > We have four repositories. > > - Snapshots > - Releases (which is empty so far) > - External > - Release/Legacy (was the first repo created, will migrate to External soon) > > The first two are what they are meant to, External is a repository for the > 3rd party artifacts that we use (no snapshots there) and Legacy also has > 3rd party artifacts (no snapshots also). Then there's this POM which > references three other POMs, which then have dependencies. All were > deployed on the Snapshots repo. Some of the jar dependencies were on > legacy, others on external. I was getting the infamous 409 - Conflict at 3 > or 4 artifacts when adding one of the "super poms" as a dependency - > doesn't happen when adding a specifc jar dependency. > > Solution: set false on the > snapshots repo configuration. > > Why? I don't get this. It's ok to filter releases/snapshots to the correct > repositories, but why this error? To show an example: when adding the > highest parent pom, I get the 409 I pasted above on 4 artifacts. All of > those are on legacy, and none is a snapshot. So maven tries to get a > release-type artifact from a snapshot repo only. Obviously there's nothing > there (but I didn't specify Maven to not get from it (enabled is true), so > it's ok). What I'd expect to happen: can't find the artifact here (which, > in case, there actually ISN'T any similar artifact there), I'll just move > to the other repositories. What happens: 409. > > At least we found a solution, but I'd appreciate any help on understanding > this issue. > > Thanks! > > -- > Vitor Branco de Miranda > BCC - UFSCar - São Carlos/SP > +55 19 92013531 > vitorbmira...@gmail.com -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
jsr311-api doesn't include.
Hi all, I am trying to create a restful application to deploy on a websphere. The version of was that I'm using doesn't support the specification jsr311. So, I want to add the jars on the /lib of the project, but when I do a mvn package maven leave out the jar in the war. Do you know that maven doesn't include the jar? The dependency: *javax.ws.rs jsr311-api 1.0* Thanks in advance!
409 Conflict - snapshots/releases repositories
The error: "ArtifactDescriptorException: Failed to read artifact descriptor for javax.faces:jsf-api:jar:1_1_01: ArtifactResolutionException: Could not transfer artifact javax.faces:jsf-api:pom:1_1_01 from/to snapshots-repo ( http://ip/artifactory/snapshots-repo): Failed to transfer http://ip/artifactory/snapshots-repo/javax/faces/jsf-api/1_1_01/jsf-api-1_1_01.pom. Error code 409, Conflict" Hi! Anyone know exactly what happens when you set true on the repository section? The documentation and my intuition said that, if you set one to false, Maven won't even care to search/download the specified type of artifact from that repository. If it's true, Maven will look on that repository for that type of the artifact . If it doesn't find, just go on and look on other repositories, if any are defined. Fair enough to me, but I had this issue which took me hours to solve: We have four repositories. - Snapshots - Releases (which is empty so far) - External - Release/Legacy (was the first repo created, will migrate to External soon) The first two are what they are meant to, External is a repository for the 3rd party artifacts that we use (no snapshots there) and Legacy also has 3rd party artifacts (no snapshots also). Then there's this POM which references three other POMs, which then have dependencies. All were deployed on the Snapshots repo. Some of the jar dependencies were on legacy, others on external. I was getting the infamous 409 - Conflict at 3 or 4 artifacts when adding one of the "super poms" as a dependency - doesn't happen when adding a specifc jar dependency. Solution: set false on the snapshots repo configuration. Why? I don't get this. It's ok to filter releases/snapshots to the correct repositories, but why this error? To show an example: when adding the highest parent pom, I get the 409 I pasted above on 4 artifacts. All of those are on legacy, and none is a snapshot. So maven tries to get a release-type artifact from a snapshot repo only. Obviously there's nothing there (but I didn't specify Maven to not get from it (enabled is true), so it's ok). What I'd expect to happen: can't find the artifact here (which, in case, there actually ISN'T any similar artifact there), I'll just move to the other repositories. What happens: 409. At least we found a solution, but I'd appreciate any help on understanding this issue. Thanks! -- Vitor Branco de Miranda BCC - UFSCar - São Carlos/SP +55 19 92013531 vitorbmira...@gmail.com
Re: help needed: problems with eclipse, m2e and wst
Having dependencies on Eclipse projects can be problematic. 1) If you think that the problems is Eclipse related, you might want to try Springframework's Eclipse STS. It comes with everything that you need to use maven to build Java projects. 2) What Repo server are you using? It is highly recommended to use a repo with maven and deploy your snapshots when they are ready to be used in other projects. 3) Turning off Eclipse's use of other projects to resolve dependencies means that you are sure that your dependencies are being resolved from your local Maven folder on your workstation which you have been put there by a maven build and install. Ron On 04/05/2012 3:25 AM, Jörg Hohwiller wrote: Hi Daniel, thank you for your help and response... You're talking about missing dependencies to libraries, not Maven modules, it that correct? No. I mean internal dependencies to my own artefacts not external libraries. Or in other words dependencies on eclipse projects. Did you try going to Project Properties> Deployment Assembly ? Yes. This is where the "org.eclipse.wst.common.component" file is configured. I can also fix my problem here by clicking "add" and then "projects" and then selecting the missing projects. I am absolutely and 100% sure that the missing projects are dependencies of that WAR-packaging module/project. I also checked by "dependency hierarchy" tab of the m2e POM view as well as with mvn dependency:tree. Is "Maven Dependencies" shown? Yes, it is. However only if the project dependencies are also present, it works. Then IMHO this is a bug of m2e such that these maven dependencies are calculated wrong or exclude the eclipse internal project dependencies and those are calculated wrong by m2e-wtp. If not, click on Add> Java Build Path Entries> Maven Dependencies> Finish Then, to be safe, remove the project from Tomcat in the Servers view, click Publish, and add the project to the Tomcat instance in the Servers view. Unfortunately that's not the case. HTH, Daniel Serodio Best Regards Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Buildnumber Maven plugin 1.1 Released
Hi, The Mojo team is pleased to announce the release of the Buildnumber Maven plugin version 1.1 This mojo is designed to get a unique build number for each time you build your project. http://mojo.codehaus.org/buildnumber-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo buildnumber-maven-plugin 1.1 Release Notes - Mojo Build Number Maven Plugin - Version 1.1 ** Bug * [MBUILDNUM-68] - Goals missing on site index page * [MBUILDNUM-79] - javasvn provider does not work for the new SVN 1.7 workspace format * [MBUILDNUM-92] - Git buildId fails when Maven is invoked from another process (e.g NetBeans or packaging scripts) ** Improvement * [MBUILDNUM-67] - Bind mojos to the initialize phase by default * [MBUILDNUM-69] - Default format for timestamp (create-timestamp mojo) should be documented ** New Feature * [MBUILDNUM-86] - Short Revision Id for Git SCM Have Fun! -- The Mojo team. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How can I trigger a makefile through Maven? is there any plugin for this?
Actually there are existing makefiles that we want to use, instead of converting them again into xml files. So I want to know how I can use my makefiles in Maven. I read up on the *Maven Make Orchestration Plugin*. But there are very less resources on the net about it. Can anyone throw some light on how I can use Maven Make Orchestration Plugin to include makefiles in my Maven build life cycle? -- View this message in context: http://maven.40175.n5.nabble.com/How-can-I-trigger-a-makefile-through-Maven-is-there-any-plugin-for-this-tp5663921p5685213.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: Recompile dependencies
Not sure if I understand your problem correctly as your mixing some Maven terms. But, if the scenario is that you have a Maven project with a few dependencies (not modules). If there changes in the projects that create the artifacts that you have a dependency to, then you need to re-build those projects. Either you need to manually build each and every one of them, or if you aggregate them in a multi-module build this can be done by executing one single build command. I think that having a look at some other multi-module Maven project will give you some ideas of how this works. You could look at some open source project, such as Maven core itself. /Anders On Thu, May 3, 2012 at 2:07 PM, Thiago Costa wrote: > Hi .. I have a question. > I am new to maven. : ( > > I have a project J2ee integration with maven, and I have projects as > dependencies. > When I change my projects children, the main project there are no major > design changes, or do I have to manually recompile the projects children. > > How to compile the main project and make new jar of the project > dependencies? > > Thanks a lot. > > Sorry, my english is poor :) > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Recompile-dependencies-tp5682998.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: excluding a file inside a jar while building a war file
Hi, > hi, actually the jar has structure as: > resources/folder1/file1.xml > resources/folder2/file2.xml > resources/folder2/file3.xml > > Now i include this jar as a dependency for 3 different wars and for each > war in need to include only either file1.xml OR file2.xml OR file3.xml > > Could you please tell how to use the upack/assembly here? > Thanks. The best solution take a look here: http://stackoverflow.com/questions/10372197/excluding-certain-files-from-a-jar-which-is-a-dependency-in-a-war-in-maven3 Kind regards Karl-Heinz Marbaise -- MfG Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: excluding a file inside a jar while building a war file
hi, actually the jar has structure as: resources/folder1/file1.xml resources/folder2/file2.xml resources/folder2/file3.xml Now i include this jar as a dependency for 3 different wars and for each war in need to include only either file1.xml OR file2.xml OR file3.xml Could you please tell how to use the upack/assembly here? Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/excluding-a-file-inside-a-jar-while-building-a-war-file-tp5671137p5685051.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: help needed: problems with eclipse, m2e and wst
Hi Daniel, thank you for your help and response... > You're talking about missing dependencies to libraries, not Maven modules, it > that correct? No. I mean internal dependencies to my own artefacts not external libraries. Or in other words dependencies on eclipse projects. > > Did you try going to Project Properties > Deployment Assembly ? Yes. This is where the "org.eclipse.wst.common.component" file is configured. I can also fix my problem here by clicking "add" and then "projects" and then selecting the missing projects. I am absolutely and 100% sure that the missing projects are dependencies of that WAR-packaging module/project. I also checked by "dependency hierarchy" tab of the m2e POM view as well as with mvn dependency:tree. > Is "Maven Dependencies" shown? Yes, it is. However only if the project dependencies are also present, it works. Then IMHO this is a bug of m2e such that these maven dependencies are calculated wrong or exclude the eclipse internal project dependencies and those are calculated wrong by m2e-wtp. > If not, click on Add > Java Build Path Entries > Maven > Dependencies > Finish > > Then, to be safe, remove the project from Tomcat in the Servers view, click > Publish, and add the project to the Tomcat instance in the Servers view. Unfortunately that's not the case. > > HTH, > Daniel Serodio Best Regards Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
