Re: How to use the latest version from dependencies (not from all repository)
I don't like to use version ranges and I agree that it is evil. This is just example that it is possible. I just want to use the latest version from full dependency tree. This is absolutely reproducable. Do you agree with that? Now I set version of A in D each time some middle artifact is changed. I have a great library tree and when some middle library starts to depend on new version of A I set also this version in D. Absolutely always in D I set the latest version from full dependency tree. Do you have the experience where this wasn't the case for your library trees? So, I want this to be done automatically.. If I need to know version of A that will be used, I can always do it by dependency:list or dependency:tree. What is the problem with that workflow? -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4673465.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use the latest version from dependencies (not from all repository)
I am absolutely agree with your opinion that unreproducability of build is a bad feature, but ... 1. Maven has a built-in mechanism of dependency version range (http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges). Using this you can set that the build will always include the last version of some artifact. That makes it absolutely unreproducable. So unreproducability doesn't contradict with the concepts of Maven and what I ask could be possible in it too. 2. What I want is absolutely reproducable. Maybe you didn't understand me. I want an artifact D to include last version of artifact A, but not among all versions of A but among versions that are present in D's full dependency tree. As dependency tree is not changed in time we get a reproducable build. At each moment of time (if artifacts from dependency tree are not changed) final D's build will include the same version of A. Moreover, what I want, I suppose, is much more reproducable and logical behaviour because using standard behaviour you depend very strongly on the order in which dependencies are declared. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4672834.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use the latest version from dependencies (not from all repository)
I don't need to make maven use A version that is inherited from C exactly. I want Maven to define the latest version automatically, without explicit definition. And I don't want to release new version of B only to fix it's A version. A:1.0 is suitable for B, so there's no need to change it. In real life I have a lot of artifacts. Some of them are stable and I don't want to update all them once new version of some middle artifact is changed. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4649537.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
How to use the latest version from dependencies (not from all repository)
Suppose I have the following artifacts. I will omit groups for simplicity. A:1.0 A:2.0 A:3.0 B:1.0 depends on A:1.0 C:1.0 depends on A:2.0 D:1.0 depends on B:1.0, C:1.0 I want D to use the latest version of A that is inherited from it's dependencies (not from repository). In this case it is 2.0. How can I make this with Maven 2 or Maven 3? -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-the-latest-version-from-dependencies-not-from-all-repository-tp4642240p4642240.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
Developing maven plugin.Can I use 'expression' and 'default-value' in my config objects.
I can create configuration parameter for my plugin and annotate it with /** * The greeting to display. * * @parameter expression="${sayhi.greeting}" default-value="Hello World!" */ private String greeting; This is said here http://maven.apache.org/guides/plugin/guide-java-plugin-development.html But I have my objects as config parameters. Can I use 'expression' and 'default-value' for its fields? -- View this message in context: http://old.nabble.com/Developing-maven-plugin.Can-I-use-%27expression%27-and-%27default-value%27-in-my-config-objects.-tp27769924p27769924.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: Developing maven plugin. How can I manage artifacts?
I tried to use glassfish-plugin but it has very simple goals whereas I need to implement a huge and complex workflow. Wendy Smoak-3 wrote: > > On Mon, Mar 1, 2010 at 6:02 AM, boraldo wrote: >> >> Please tell about all known ways. I will choose then. > > You already said that existing plugins don't satisfy your > requirements. Which ones are those, and why? > > With that info, perhaps someone here can point out an alternative. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://old.nabble.com/Developing-maven-plugin.-How-can-I-manage-artifacts--tp27734652p27743235.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: Developing maven plugin. How can I manage artifacts?
Please tell about all known ways. I will choose then. nicolas de loof-2 wrote: > > Do you want to use current project artifact or a project dependency ? > > 2010/2/28 boraldo > >> >> I want to develop plugin that will do something with jar files in a local >> repository. >> Example: deploy application ear file to server. Please, don't propose to >> use >> existing plugins for this. They don't satisfy my requirements. I want to >> develop my plugin. >> How can I do it? >> >> -- >> View this message in context: >> http://old.nabble.com/Developing-maven-plugin.-How-can-I-manage-artifacts--tp27734652p27734652.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > -- View this message in context: http://old.nabble.com/Developing-maven-plugin.-How-can-I-manage-artifacts--tp27734652p27742143.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
Developing maven plugin. How can I manage artifacts?
I want to develop plugin that will do something with jar files in a local repository. Example: deploy application ear file to server. Please, don't propose to use existing plugins for this. They don't satisfy my requirements. I want to develop my plugin. How can I do it? -- View this message in context: http://old.nabble.com/Developing-maven-plugin.-How-can-I-manage-artifacts--tp27734652p27734652.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: ear-plugin and profiles: poor cooperation?
I have the same problem and I'd like to explain it. I want to have an ability to add some web-modules to my ear in some profile. And I don't want to redefine other modules, only my module. If I only add dependency on my module in profile, it's context root will be equal to war name, but I want to set it manually. snicoll wrote: > > A configuration item that is a list can't be merged in a profile. See the > "modules" element as a configuration item, like the JavaEE version you > want > to use. If you override the value in the profile, you can't expect it to > merge the elements that are set in the main build (this is a global > behavior > of Maven btw). > > Why don't you add a dependency section in your profile instead? Why > quartz.jar should be added to the application context? Maybe you need to > use > http://maven.apache.org/plugins/maven-ear-plugin/generate-application-xml-mojo.html#includeLibInApplicationXmlinstead. > > Regards, > Stéphane > > On Tue, Dec 22, 2009 at 4:12 PM, Rebholz Paul > wrote: > >> > Hi all! >> > >> > We have a project producing an ear artifact. The contents of the ear >> > file are configured with the maven-ear-plugin. In profiles we want to >> > be able to flexibly add more artifacts to the ear file as shown in the >> > example below. Our tests so far revealed a different behaviour than >> > expected. When adding a jar file with the jarModule element, all other >> > entries corresponding to jarModules disappear in the application.xml >> > and even some other jar files disappear completely from the ear. >> > Moreover, when adding a second profile adding jars, the first is >> > eclipsed. Is this a bug in the maven-ear-plugin implementation? >> > >> > Regards, Paul >> > >> > >> > >> > my_test >> > >> > >> > my_switch >> > true >> > >> > >> > >> > >> > >> > maven-ear-plugin >> > >> > >> > >> > quartz >> > quartz >> > >> > true >> > >> > >> > >> > >> > >> > >> > >> > >> > quartz >> > quartz >> > jar >> > 1.5.2 >> > >> > >> > >> >> This message is for the named person's use only. It may contain >> confidential, proprietary or legally privileged information. If you >> receive >> this message in error, please notify the sender urgently and then >> immediately delete the message and any copies of it from your system. >> Please >> also immediately destroy any hardcopies of the message. >> The sender's company reserves the right to monitor all e-mail >> communications through their networks. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > Large Systems Suck: This rule is 100% transitive. If you build one, you > suck" -- S.Yegge > > -- View this message in context: http://old.nabble.com/ear-plugin-and-profiles%3A-poor-cooperation--tp26889824p27452223.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can I execute plugin X, then plugin Y, then plugin X again ?
>> you need to put the executions in different phases if they need a defined order I don't want that phases to execute. For example clean will clean, compile wil compile. If there any phases besides initialize that do nothing ? Stephen Connolly-2 wrote: > > not the bug you think it is > > you need to put the executions in different phases if they need a > defined order > > the bug is allowing you to list the same plugin twice in the one > plugins section > > Sent from my [rhymes with tryPod] ;-) > > On 10 Nov 2009, at 17:51, Paul Benedict wrote: > >> This is probably a bug since the order of plugins should be respected. >> >> Have you checked the ticket list of 2.2.2 or 3.0-alpha-3 to see if it >> is already fixed? >> >> And are you running 2.2.1? >> >> Paul >> >> On Tue, Nov 10, 2009 at 11:48 AM, boraldo wrote: >>> >>> Suppose I have to execute some actions after some phase. >>> These actions are made plugins X and Y. >>> 1st action - executed by plugin X >>> 2nd action - executed by plugin Y >>> 3rd action - executed by plugin X >>> >>> I wrote the following pom: >>> >>> >>> >>> >>>plugin-x >>> >>> >>>step-1-x >>>initialize >>> >>>goal-x-1 >>> >>> >>> >>> >>> >>>plugin-y >>> >>> >>>step-2-y >>>initialize >>> >>>goal-y-1 >>> >>> >>> >>> >>> >>>plugin-x >>> >>> >>>step-3-x >>>initialize >>> >>>goal-x-2 >>> >>> >>> >>> >>> >>> >>> >>> I executed: >>> mvn initialize >>> >>> But the sequence of executions was wrong: >>> 1. step-1-x >>> 2. step-3-x >>> 3. step-2-y >>> >>> This means that each plugin executes all its executions, then the >>> next >>> plugin starts to work. >>> Can I corrupt such scenario ? >>> -- >>> View this message in context: >>> http://old.nabble.com/How-can-I-execute-plugin-X%2C-then-plugin-Y%2C-then-plugin-X-again---tp26287350p26287350.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 >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://old.nabble.com/How-can-I-execute-plugin-X%2C-then-plugin-Y%2C-then-plugin-X-again---tp26287350p26298018.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
How can I execute plugin X, then plugin Y, then plugin X again ?
Suppose I have to execute some actions after some phase. These actions are made plugins X and Y. 1st action - executed by plugin X 2nd action - executed by plugin Y 3rd action - executed by plugin X I wrote the following pom: plugin-x step-1-x initialize goal-x-1 plugin-y step-2-y initialize goal-y-1 plugin-x step-3-x initialize goal-x-2 I executed: mvn initialize But the sequence of executions was wrong: 1. step-1-x 2. step-3-x 3. step-2-y This means that each plugin executes all its executions, then the next plugin starts to work. Can I corrupt such scenario ? -- View this message in context: http://old.nabble.com/How-can-I-execute-plugin-X%2C-then-plugin-Y%2C-then-plugin-X-again---tp26287350p26287350.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
How to send email with enclosed files ?
Please tell me which plugin is able to do it ? -- View this message in context: http://www.nabble.com/How-to-send-email-with-enclosed-files---tp26074704p26074704.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can deploy artefacts without rebuilding project ?
deploy:deploy-file deploys single file. I need to deploy all modules. MALICE wrote: > > This means that you have a non-standard packaging... I guess... > > Try deploy:deploy-file. Not the prefered solution (imo), but it should > work. > Oh, check the parameters it needs though! > > > On Monday 12 October 2009 14:45, boraldo wrote: >> deploy:deploy implies to >> The packaging for this project did not assign a file to the build >> artifact >> >> MALICE wrote: >> > If the artifact still exists, try deploy:deploy. >> > >> > On Monday 12 October 2009 12:54, boraldo wrote: >> >> I want to build in 2 steps. >> >> 1. install >> >> 2. deploy >> >> >> >> But if I execute mvn deploy, it executes install phase again. >> >> If I execute mvn deploy:mvn deploy, error occurs: >> >> >> >> The packaging for this project did not assign a file to the build >> >> artifact >> >> >> >> How can I fix it ? >> > >> > -- >> > Roland Asmann >> > >> > CFC Informationssysteme Entwicklungsgesellschaft m.b.H >> > Bäckerstrasse 1/2/7 >> > A-1010 Wien >> > FN 266155f, Handelsgericht Wien >> > >> > Tel.: +43/1/513 88 77 - 27 >> > Fax.: +43/1/513 88 62 >> > Email: roland.asm...@cfc.at >> > Web: www.cfc.at >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org > > -- > Roland Asmann > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > Bäckerstrasse 1/2/7 > A-1010 Wien > FN 266155f, Handelsgericht Wien > > Tel.: +43/1/513 88 77 - 27 > Fax.: +43/1/513 88 62 > Email: roland.asm...@cfc.at > Web: www.cfc.at > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/How-can-deploy-artefacts-without-rebuilding-project---tp25853779p25867904.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can deploy artefacts without rebuilding project ?
deploy:deploy implies to The packaging for this project did not assign a file to the build artifact MALICE wrote: > > If the artifact still exists, try deploy:deploy. > > > On Monday 12 October 2009 12:54, boraldo wrote: >> I want to build in 2 steps. >> 1. install >> 2. deploy >> >> But if I execute mvn deploy, it executes install phase again. >> If I execute mvn deploy:mvn deploy, error occurs: >> >> The packaging for this project did not assign a file to the build >> artifact >> >> How can I fix it ? > > -- > Roland Asmann > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > Bäckerstrasse 1/2/7 > A-1010 Wien > FN 266155f, Handelsgericht Wien > > Tel.: +43/1/513 88 77 - 27 > Fax.: +43/1/513 88 62 > Email: roland.asm...@cfc.at > Web: www.cfc.at > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/How-can-deploy-artefacts-without-rebuilding-project---tp25853779p25855211.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
How can deploy artefacts without rebuilding project ?
I want to build in 2 steps. 1. install 2. deploy But if I execute mvn deploy, it executes install phase again. If I execute mvn deploy:mvn deploy, error occurs: The packaging for this project did not assign a file to the build artifact How can I fix it ? -- View this message in context: http://www.nabble.com/How-can-deploy-artefacts-without-rebuilding-project---tp25853779p25853779.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