Re: When using resources:resources, supply properties from jar
Thanks for the help...it's funny that after some searching...I found the following post and noticed that in our codebase someone had copied and used this same exact code to solve it: stackoverflow.com/questions/1231561/how-to-share-common-properties-among-several-maven-projects/1265428#1265428 -- View this message in context: http://maven.40175.n5.nabble.com/When-using-resources-resources-supply-properties-from-jar-tp5668902p5677051.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
[ANN] maven-changes--plugin 2.7
The Maven team is pleased to announce the release of the Maven Changes Report Plugin, version 2.7 Creates a release history for inclusion into the site and assists in generating an announcement mail. http://maven.apache.org/plugins/maven-changes-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-changes-plugin 2.7 Release Notes - Maven Changes Report Plugin - Version 2.7 Bug * [MCHANGES-262] Using custom issue types mapping (MCHANGES-245) throws a llegalArgumentException * [MCHANGES-261] Mail sender specification pointlessly difficult * [MCHANGES-237] The goal jira-report always results in HTTP 400 error when accessing https://*.jira.com Improvement * [MCHANGES-279] ability to skip for Jira is offlince * [MCHANGES-264] [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata * [MCHANGES-213] Update Velocity 1.7 New Feature * [MCHANGES-275] versionPrefix configurable by expression 'changes.versionPrefix' * [MCHANGES-272] Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions. * [MCHANGES-76] Add an option to hava an aggregated Changes Report Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] maven-changes-plugin 2.7 released
The Maven team is pleased to announce the release of the Maven Changes Report Plugin, version 2.7 Creates a release history for inclusion into the site and assists in generating an announcement mail. http://maven.apache.org/plugins/maven-changes-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-changes-plugin 2.7 Release Notes - Maven Changes Report Plugin - Version 2.7 Bug * [MCHANGES-262] Using custom issue types mapping (MCHANGES-245) throws a llegalArgumentException * [MCHANGES-261] Mail sender specification pointlessly difficult * [MCHANGES-237] The goal jira-report always results in HTTP 400 error when accessing https://*.jira.com Improvement * [MCHANGES-279] ability to skip for Jira is offlince * [MCHANGES-264] [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata * [MCHANGES-213] Update Velocity 1.7 New Feature * [MCHANGES-275] versionPrefix configurable by expression 'changes.versionPrefix' * [MCHANGES-272] Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions. * [MCHANGES-76] Add an option to hava an aggregated Changes Report Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Lifecycle phase in which the url for distributionManagement/snapshotRepository is calculated
Yep but means having your jar locally in your m3 installation. -- Olivier Le 30 avr. 2012 21:03, "Mirko Friedenhagen" a écrit : > Hello Olivier, > > I assume I have to create the properties in afterSessionStart as > afterProjectsRead will be to late again? > > Regards Mirko > > On Sun, Apr 29, 2012 at 21:22, Olivier Lamy wrote: > > Yup you can add properties to project.getProperties() > > But in your case you want to change distributionManagement urls using > > properties interpolation mechanism ? but it's too late using a plugin > > as model has been build. > > > > An option you have maybe it's to use maven3 lifecycle extension > > mechanism: > http://maven.apache.org/examples/maven-3-lifecycle-extensions.html > > > > 2012/4/29 Mirko Friedenhagen : > >> Hm, so this seems to be true only for some elements of the pom but not > >> plugin configurations. The > >> http://mojo.codehaus.org/buildnumber-maven-plugin/ actually adds > >> buildNumber and uses it in e.g. the maven-jar-plugin to add a field > >> Implementation-Build. > >> > >> Regards Mirko > >> > >> > >> On Sun, Apr 29, 2012 at 11:09, Hervé BOUTEMY > wrote: > >>> yes, property evaluations is done in the "model interpolation" step of > the > >>> Maven model build: see [1] for a global view > >>> > >>> no, no plugin can add any property at any phase, sorry > >>> > >>> Regards, > >>> > >>> Hervé > >>> > >>> [1] http://maven.apache.org/ref/3.0.4/maven-model-builder/ > >>> > >>> Le dimanche 29 avril 2012 08:36:10 Anders Hammar a écrit : > I think it is resolved even before the build lifecycle starts. > > /Anders > > On Sat, Apr 28, 2012 at 22:01, Mirko Friedenhagen > > wrote: > > Hello, > > > > I developed a plugin which creates an additional property during the > > validate phase and want to use it as part of the > > snapshotRepository/url. However the property is not resolved but the > > name of the property is inserted. I may access the calculated > property > > and insert it into Could anybody tell me in which phase the urls in > > distributionManagement are resolved? > > > > Regards Mirko > > > > > - > > 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 > >> > > > > > > > > -- > > 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 > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Lifecycle phase in which the url for distributionManagement/snapshotRepository is calculated
Hello Olivier, I assume I have to create the properties in afterSessionStart as afterProjectsRead will be to late again? Regards Mirko On Sun, Apr 29, 2012 at 21:22, Olivier Lamy wrote: > Yup you can add properties to project.getProperties() > But in your case you want to change distributionManagement urls using > properties interpolation mechanism ? but it's too late using a plugin > as model has been build. > > An option you have maybe it's to use maven3 lifecycle extension > mechanism: http://maven.apache.org/examples/maven-3-lifecycle-extensions.html > > 2012/4/29 Mirko Friedenhagen : >> Hm, so this seems to be true only for some elements of the pom but not >> plugin configurations. The >> http://mojo.codehaus.org/buildnumber-maven-plugin/ actually adds >> buildNumber and uses it in e.g. the maven-jar-plugin to add a field >> Implementation-Build. >> >> Regards Mirko >> >> >> On Sun, Apr 29, 2012 at 11:09, Hervé BOUTEMY wrote: >>> yes, property evaluations is done in the "model interpolation" step of the >>> Maven model build: see [1] for a global view >>> >>> no, no plugin can add any property at any phase, sorry >>> >>> Regards, >>> >>> Hervé >>> >>> [1] http://maven.apache.org/ref/3.0.4/maven-model-builder/ >>> >>> Le dimanche 29 avril 2012 08:36:10 Anders Hammar a écrit : I think it is resolved even before the build lifecycle starts. /Anders On Sat, Apr 28, 2012 at 22:01, Mirko Friedenhagen wrote: > Hello, > > I developed a plugin which creates an additional property during the > validate phase and want to use it as part of the > snapshotRepository/url. However the property is not resolved but the > name of the property is inserted. I may access the calculated property > and insert it into Could anybody tell me in which phase the urls in > distributionManagement are resolved? > > Regards Mirko > > - > 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 >> > > > > -- > 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 > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Reference file name for filtering
How can I have maven replace a property with the file name that is being
filtered? I have tried ${project.file} and it just gives the me the full
file path for the pom.xml. I want the property to tell me the file that it
is being filtered.
--
View this message in context:
http://maven.40175.n5.nabble.com/Reference-file-name-for-filtering-tp5676444.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: jvm arguments not making it to application and unit tests
Stephen,
This worked excellent and as advertised. Thanks so much for the suggestion and
help!
Thank you!
- Billy -
On Thursday, April 26, 2012 at 4:08 PM, stephenconnolly [via Maven] wrote:
> You need to see this page:
>
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
>
> You will need to define system properties for each system property you want
> to pass through.
>
> Most likely your properties will look like
>
>
> ${foo}
> ${bar}
>
>
> Ie you are just passing them straight through.
>
> You will probably want to define sensible defaults for the properties in
> the Pom itself so that a developer just checking out can build without
> changing anything... There are some times when it becomes sensible to have
> that set of default properties in a profile that is activated if you have
> not defined a touchstone property, so that once you add -Dfoo=... To the
> cli you need to also add the -Dbar=... As the profile with defaults is no
> longer active... That is the "you may need to use profiles" i was referring
> to, but consider it as a finesse once you have it all working.
>
> HTH
>
> -Stephen
>
> Sent from my iPhone
>
> On Thursday, 26 April 2012, billybacon wrote:
>
> > We are also trying to remove profiles altogether, this is one of the
> > reasons
> > we are trying to using jvm command line arguments. After simplifying things
> > a bit further and removing jenkins out of the picture, this does appear to
> > be a maven topic.
> >
> > If I try the following command with maven 2.2.1, the jvm args are _not
> > picked up by the unit tests and application classes (note: each jvm arg had
> > to be encapsulated by quotes):
> >
> > mvn clean package "-DAWS_ACCESS_KEY_ID=" \
> > "-DAWS_SECRET_KEY=" \
> >
> > "-DJDBC_CONNECTION_STRING=jdbc:postgresql://x:5432/test?user=xxx&password=xxx"
> >
> > \
> > "-DPARAM1=5" \
> > "-DPARAM2=localhost:8080" \
> > "-DPARAM3=false"
> >
> > Running the same command with maven 3 succeeds.
> >
> > The above was tried on my local mac:
> > Apache Maven 2.2.1 (r801777; 2009-08-06 13:16:01-0600)
> > Java version: 1.6.0_31
> > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> > Default locale: en_US, platform encoding: MacRoman
> > OS name: "mac os x" version: "10.7.3" arch: "x86_64" Family: "mac"
> >
> > Running this on the same machine that jenkins is installed on succeeds with
> > maven 2.2.1, just using maven directly, BUT it fails when jenkins attempts
> > to execute the job with the jvm args passed in on the Goals and options
> > field.
> >
> > Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> > Java version: 1.6.0_23
> > Java home: /usr/java/jdk1.6.0_23/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux" version: "2.6.18-164.0.0.0.1.el5xen" arch: "amd64" Family:
> > "unix"
> >
> > Could it be the platform encoding?
> >
> >
> > --
> > View this message in context:
> > http://maven.40175.n5.nabble.com/jvm-arguments-not-making-it-to-application-and-unit-tests-tp5667993p5668007.html
> > Sent from the Maven - Users mailing list archive at Nabble.com
> > (http://Nabble.com).
> >
> > -
> > To unsubscribe, e-mail: [hidden email]
> > (/user/SendEmail.jtp?type=node&node=5668784&i=0)
> > For additional commands, e-mail: [hidden email]
> > (/user/SendEmail.jtp?type=node&node=5668784&i=1)
> >
> >
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/jvm-arguments-not-making-it-to-application-and-unit-tests-tp5667993p5668784.html
>
> To unsubscribe from jvm arguments not making it to application and unit
> tests, click here
> (http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5667993&code=YmlsbHkuYmFjb25AZ21haWwuY29tfDU2Njc5OTN8MTQ4NTc1NDA1Mg==).
> NAML
> (http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml)
>
--
View this message in context:
http://maven.40175.n5.nabble.com/jvm-arguments-not-making-it-to-application-and-unit-tests-tp5667993p5676289.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Does maven-nsis-plugin 2.1 work with maven 2.2.1
> Could anyone please confirm does the maven-nsis-plugin 2.1 work with maven > 2.2.1? Stackoverflow says you need to use nsis-maven-plugin instead: http://stackoverflow.com/questions/6049556/failed-to-parse-plugin-descriptor-for-mavenmaven-nsis-plugin2-1 nsis maven plugin is the Maven 2/3 plugin http://mojo.codehaus.org/nsis-maven-plugin/index.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Does maven-nsis-plugin 2.1 work with maven 2.2.1
Hi, I have a NSIS script developed in NSIS version 2.46. I would want to automate the build process of the installer executable using maven. when I searched I found this maven-nsis-plugin. I included it in my plugin section of POM and the jar gets downloaded and after download it says plugin descriptor not found. Could anyone please confirm does the maven-nsis-plugin 2.1 work with maven 2.2.1? This version of the maven-nsis-plugin 2.1 looks like a Maven 1 plugin whcih could not work with Maven 2..X etc. There has been created a maven-nsis-plugin on codehaus http://mojo.codehaus.org/nsis-maven-plugin/ But it looks this plugin has never been released into neither put into maven central... Kind regards 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
Does maven-nsis-plugin 2.1 work with maven 2.2.1
Hello, I have a NSIS script developed in NSIS version 2.46. I would want to automate the build process of the installer executable using maven. when I searched I found this maven-nsis-plugin. I included it in my plugin section of POM and the jar gets downloaded and after download it says plugin descriptor not found. Could anyone please confirm does the maven-nsis-plugin 2.1 work with maven 2.2.1? Thanks in advance !! -- View this message in context: http://maven.40175.n5.nabble.com/Does-maven-nsis-plugin-2-1-work-with-maven-2-2-1-tp5676129.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: javac: invalid target release: 1.7
>> [ERROR] Failure executing javac, but could not parse the error: >> javac: invalid target release: 1.7 >> Usage: javac >> use -help for a list of possible options This error message comes directly from javac and means "Maven tried to call me with -target 1.7 but I can't do that." This is not a Maven error but merely being reported by Maven. Upgrade to JDK7 on Mac and you should have no such issues. Or change the code so it does not require JDK7 and change the pom.xml configuration. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javac: invalid target release: 1.7
Hi, > Mac OS X version 10.7.3 > java -version > java version "1.6.0_31" > > Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > (because required by project I want to build) > > The project I want to build is: > http://code.google.com/p/cmake-maven-project/source/browse/ > > The error I am getting when running mvn install is: > > > [ERROR] Failure executing javac, but could not parse the error: > javac: invalid target release: 1.7 > Usage: javac > use -help for a list of possible options > > I can't upgrade to java 1.7 (if this is the cause of the error). Yup. A compiler target 1.7 means Java 7 is needed for successful compilation. > Are there > other means to fix this? Install Oracle's recently released Java 7 port for MacOS X on your machine :-) HTH Thorsten
javac: invalid target release: 1.7
Hi, Mac OS X version 10.7.3 java -version java version "1.6.0_31" Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) (because required by project I want to build) The project I want to build is: http://code.google.com/p/cmake-maven-project/source/browse/ The error I am getting when running mvn install is: [ERROR] Failure executing javac, but could not parse the error: javac: invalid target release: 1.7 Usage: javac use -help for a list of possible options I can't upgrade to java 1.7 (if this is the cause of the error). Are there other means to fix this? regards -- Witold Eryk Wolski Bergeller str 21 8049 Zuerich
How to operate a xml, After delete a column from mysql
I have table "RT_DATA_BANK" with columns, ID, BANKNAME and ASSIGNMENT_VALUE. Using "dbunit-maven-plugin", I operate the table values from xml, ID BANKNAME ASSIGNMENT_VALUE 1 AAA 55 2 BBB 66 This time executes. But, I delete column ASSIGNMENT_VALUE from mysql. Now, I operate the xml, This time i getting error as, [INFO] Error executing database operation: MSSQL_CLEAN_INSERT Embedded error: RT_DATA_BANK.ASSIGNMENT_VALUE - (Non-uppercase input column: ASSIGNMENT_VALUE) in ColumnNameToIndexes cache map. Note that the map's column names are NOT case sensitive. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing database operation: MSSQL_CLEAN_INSERT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) 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.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing database operation: MSSQL_CLEAN_INSERT at org.codehaus.mojo.dbunit.OperationMojo.execute(OperationMojo.java:109) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.dbunit.dataset.NoSuchColumnException: RT_DATA_BANK.ASSIGNMENT_VALUE - (Non-uppercase input column: ASSIGNMENT_VALUE) in ColumnNameToIndexes cache map. Note that the map's column names are NOT case sensitive. I can understand the missing of column 'ASSIGNMENT_VALUE' in mysql. Is their any other way to execute the xml like, skip the missing column/execute only matching column or any other suggestions.. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-operate-a-xml-After-delete-a-column-from-mysql-tp5675960.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: Maven - offer anything for runtime?
Whether or not it is what I *was* looking at, it certainly seems apropos :-) On Sun, Apr 29, 2012 at 10:50 PM, Wayne Fay wrote: > H... are you talking about PomStrap? ;-) > > http://pomstrap.jfluid.com/ [site is down for me right now] > http://www.pomstrap.techlab.smk.fr/en/ > http://pomstrap.tigris.org/ > > PomStrap is a hierarchical Class-Loader based on the Maven's artifact > repository model. In a nutshell, it provides a runtime feature to > Maven. > > Wayne > > On 4/29/12, Benson Margulies wrote: >> I can't track down the thing I was referring to. It has a cute project >> name and was embedded maven as a way to manage classpath containers >> and plugin downloads at runtime. I also looked a bit at SISU to see if >> it was applicable to your problem, but the eclipse site is not >> revealing at this time. >> >> On Sat, Apr 28, 2012 at 3:58 PM, Matt Narrell >> wrote: >>> You can also use the maven-enforcer-plugin to identify dependencies >>> that attempt to bring in older versions of transitive dependencies. >>> >>> On Apr 28, 2012, at 10:55 AM, Ron Wheeler >>> wrote: >>> It is not that hard. You just paste the same exclusion into each POM that includes something that brings in a version that you do not want. To reduce the effort, make your POMs that produce artifacts that you deploy depend on your own POMs that only serve to bring in third party tools. In that way the developer does not have to do any exclusions since your library POMs have already setup the third party dependencies correctly. mywar.pom depends on myapache.pom and myspring.pom and myjasper.pom. myapache.pom and myspring.pom and myjasper.pom are sanitized to get rid of transitive dependencies that I will provide at run-time. Makes the job very simple Once you do it once the developers have a much simpler life. Ron On 27/04/2012 5:47 PM, J.V. wrote: > If I have a log4j exclusion in every section, that would > look quite messy. Is there a way to globally do this? > We have dozens of dependencies, just looks like there would be an easier > way. Nearly everything depends on log4j so that is a lot of work to add > to every dependency. Not sure there is an easier way though. > > J.V. > > On 4/27/2012 1:44 PM, Ron Wheeler wrote: >> You can either be god-like or trust that Tomcat will be. >> You only need to do it once. >> It takes a bit of time but, at the end, you know what you are running >> in production and developers don't have to worry about getting a >> MethodNotFound at run-time. >> >> It is not as bad as you think if you have a good IDE with Maven >> support. We use Eclipse STS from Springframework. >> >> It will look through your project POM and tell you where all your >> dependencies are coming from. >> >> You can then write excludes on your dependencies to stop them from >> bringing in transitive dependencies that you do not want. >> >> We made our own poms to bring in all the Apache stuff (commons-xxx, >> log4j, etc.) so we had a single dependency that developers could use in >> their projects to get the "right" version of all the "right" Apache >> libraries. They never had to worry about them again and if we wanted to >> upgrade log4j, we just did it in one place. >> For third party libraries that had transitive dependencies on something >> like log4j, we just added an exclude to their dependency >> specification. >> >> We had a small team with a lot of modules so it really made everyone's >> life easier and I did not have to worry that someone would inject an >> old version into the system. >> >> Ron >> >> >> On 27/04/2012 3:27 PM, J.V. wrote: >>> >>> >>> On 4/27/2012 10:04 AM, Ron Wheeler wrote: On 27/04/2012 11:40 AM, J.V. wrote: > I understand how Maven resolves dependencies (and transitive > dependencies) at compile time, but does it bring anything to the > table at run time? It makes your artifacts that your run-time environment will execute. It is a build tool. > > For example, if I have in my application dependency list two > versions of log4J (let's say version 8 and version 15), will I > deploy both jars/version along with my app on say a tomcat server > inside the war? Fix it so you only have 1. Settle on the "right" versions of third party libraries and use "exclusions" in your dependencies to prevent other libraries from grabbing older versions. >>> => this is a very tedious task. I have to be godlike to know the >>> transitive dependencies and what libraries they use, and inspect my >>> local repository, find out all dups of everything, find out which top >>> level dependency needs it an
[ANN] Apache Maven SCM 1.7 released
Hi, The Apache Maven Team is pleased to announce the release of Apache Maven SCM 1.7. Maven SCM is an abstract in top of various SCM tools (see http://maven.apache.org/scm/scms-overview.html). The 1.7 release introduce support of Jazz SCM tool. Release Notes - Apache Maven SCM - Version 1.7 ** New Feature * [SCM-670] - Support Jazz SCM ** Improvement * [SCM-649] - Enhance SCM changelog model to hold more data about changes * [SCM-664] - Git short revision number (emulate command git rev-parse --short=LENGTH) ** Bug * [SCM-154] - Bazaar tests should not assume bzr is installed * [SCM-478] - SvnScmProviderRepository getParent() with endless loop * [SCM-482] - SvnInfoConsumer not I18N aware * [SCM-584] - Checkout branch with Git uses unfamiliar command sequence which leads to errors during checkout * [SCM-618] - StringIndexOutOfBoundsException when doing checkout from SVN in combination with plexus-utils:2.0.5+ * [SCM-632] - Faulty svn commandline is generated for passwords containing redirection characters * [SCM-637] - parsing of git urls fails on windows * [SCM-641] - NPE when workingDirectory is null * [SCM-656] - Building maven-scm-1.6 requires a native install of git. * [SCM-658] - HgChangeLogCommand doesn't implement method executeChangeLogCommand() * [SCM-660] - Perforce Provider does not pass client specification to p4 for blame command * [SCM-663] - scm:update with GIT sometimes fails to report the affected files * [SCM-667] - mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with "is outside repository" * [SCM-671] - Perforce provider Edit command incorrectly ignores working Directory * [SCM-672] - Perforce checking (submit) incorrectly ignores working directory Have Fun, -- The Apache Maven Team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: mvn tomcat:deploy fails with HTTP response 401
redirecting to maven users ..as this is a maven issue Thanks, Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité 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. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sat, 28 Apr 2012 23:24:36 +0200 > Subject: Re: mvn tomcat:deploy fails with HTTP response 401 > From: hord...@gmail.com > To: us...@tomcat.apache.org > > Awesome! I added the pluginGroup and it worked now. > > Thank you! > > 2012/4/28 Olivier Lamy > > > Have a look here > > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html > > > > there is a section regarding content to add in ~/.m2/settings.xml > > > > or add the plugin declaration in the pom section build>plugins>plugin > > (rather than pluginManagement) > > > > HTH > > -- > > Olivier Lamy > > Talend: http://coders.talend.com > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > 2012/4/28 Henrique Ordine : > > > Thanks again for your help. > > > > > > I added to my POM, but if I use tomcat6:deploy or > > > tomcat6:run, Maven says: > > > > > > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist > > > or no valid version could be found > > > > > > I'm using Maven, 2.2.0 by the way. > > > > > > 2012/4/27 Olivier Lamy > > > > > >> Add > > >> > > >> > > >> apache.snapshots > > >> Apache Snapshots > > >> http://repository.apache.org/content/groups/snapshots-group/ > > >> > > >> > > >>false > > >> > > >> > > >>true > > >> > > >> > > >> > > >> > > >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat > > >> version you want to use). > > >> > > >> I'd like to know the command line you are using ? It must be > > >> tomcat6:deploy or tomcat7:deploy > > >> > > >> 2012/4/27 Henrique Ordine : > > >> > Thanks for your reply. > > >> > > > >> > I made the changes that you suggested but tomcat:deploy still fails > > with > > >> the > > >> > same error. > > >> > > > >> > tomcat:run works, but it was already working before. > > >> > > > >> > My POM file is attached, if you could have a look at it, it would be > > >> great. > > >> > It's a small POM, I've only just started my App. > > >> > > > >> > Thanks in advance, > > >> > > > >> > Op 27 april 2012 12:14 schreef Olivier Lamy het > > >> volgende: > > >> >> > > >> >> Hello, > > >> >> > > >> >> That's something which has been fixed in trunk (I will probably > > >> >> release a 2.0 next week). > > >> >> > > >> >> > > >> >> 2012/4/27 Henrique Ordine : > > >> >> > Hi everybody, > > >> >> > > > >> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the > > >> >> > tomcat:deploy maven plugin, but the Manager application fails with > > a > > >> >> > response code 401. > > >> >> > > > >> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I > > manage > > >> to > > >> >> > access my Tomcat/manager app with the user "hordine", that I > > >> configured > > >> >> > and > > >> >> > deploy > > >> >> > > > >> >> > I've configured my tomcat-users.xml, settings.xml, and POM files, > > like > > >> >> > this: > > >> >> > > > >> >> > I've added this user to my tomcat-users.xml: > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > roles="manager"/> > > >> >> > > > >> >> > > > >> >> > > > >> >> > I've added this server to my settings.xml: > > >> >> > > > >> >> > > > >> >> >hordineLocalTomcat > > >> >> >hordine > > >> >> >hordine > > >> >> > > > >> >> > > > >> >> > > > >> >> > And I've configured my POM like this: > > >> >> > > > >> >> > > > >> >> > > > >> >> > hTask-web > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > org.apache.tomcat.maven > > >> >> > > > >> >> > tomcat-maven-plugin > > >> >> > > > >> >> > 1.1 > > >> >> > > >> >> Sure of that > > >> >> > > >> >> But to test if your issue is fixed in trunk try > > >> >> 2.0-SNAPSHOT > > >> >> > > >> >> see mojo declaration and repositories here: > > >> >> > > http://tomcat.apache.org/
Re: enabling optional dependency
Is there some knob to switch this optinal dependency on or i have to copy this dependency to my pom? No knob: "If a user wants to use functionality related to an optional dependency, they will have to redeclare that optional dependency in their own project."
Re: enabling optional dependency
Am 30.04.2012 10:18, schrieb Radim Kolar: > Spring framework has optional dependency on CGLIB: > > > cglib > cglib-nodep > 2.2 > true > > > Is there some knob to switch this optinal dependency on or i have to > copy this dependency to my pom? In case you want to use the Spring features depending on CGLIB: you have to copy it and drop the true. Best regards Ansgar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
enabling optional dependency
Spring framework has optional dependency on CGLIB: cglib cglib-nodep 2.2 true Is there some knob to switch this optinal dependency on or i have to copy this dependency to my pom? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
