Re: Get the effective pom to a program
Thanks for the quick reply. But what I want to do is to use the maven help
plugin classes inside my program to generate the effective pom. But since
the variables are set by Mojo parameters ${reactorProjects} and ${project} I
cannot accomplish this. Is there a way to get
these parameters programmatically and pass them to the Mojo?
On Fri, Feb 26, 2010 at 6:37 AM, Wayne Fay wrote:
> > I want to get the effective pom of a given pom file in to a progam that I
> am
> > writing. Is there a way to reuse the code in the maven help plugin to get
> > this done?
>
> 1. Probably should be asking this on Maven Users list.
> 2. This should do it: mvn help:effective-pom | your-program
>
> Wayne
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Re: Patch for http://jira.codehaus.org/browse/SCM-444
moving to maven dev ml. Hi, Sure if any objections from others, I will review and commit this this. (after my one week vacation :-) ). What I'd like to be sure (sorry I haven't read the patch yet) : the default option for the push is true by default (as today). 2010/2/26 Hiram Chirino : > Hi, > > I was hoping someone could review and apply the patch attached to SCM-444. > It adds a 'pushChanges' option to the scm plugin which is checked by > the gitexe provider > to see if it should push it's changes when it commits, branches, tags etc. > > The pushChanges option probably would be applicable to other > distributed scms like mercurial. It should help resolve > http://jira.codehaus.org/browse/SCM-475 too. > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > Open Source SOA > http://fusesource.com/ > -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] Release Maven 2.0.11
Vote has passed with 3 binding votes: Brett, Benjamin and Lukas. I'll start the promotion to central. On 12/02/2010, at 11:55 PM, Brett Porter wrote: > Hi, > > This is a vote to release Maven 2.0.11, as we discussed late last year. It > has been available for testing for several months with a few positive reports > and no issues raised. It passes all of the integration tests for that version. > > It includes 36 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118 > > The staging repo is available here: > https://repository.apache.org/content/repositories/maven-staging-002/ > > The distribution files are here: > http://people.apache.org/builds/maven/2.0.11/ > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[jira] Subscription: Design & Best Practices
Issue Subscription Filter: Design & Best Practices (23 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques http://jira.codehaus.org/browse/MNG-612 MNG-139 server definitions should be reusable - review use of repository IDs http://jira.codehaus.org/browse/MNG-139 MNG-2125[doc] when and how to define plugins in a pom http://jira.codehaus.org/browse/MNG-2125 MNG-474 performance improvement for forked lifecycles http://jira.codehaus.org/browse/MNG-474 MNG-1563how to write integration tests http://jira.codehaus.org/browse/MNG-1563 MNG-1381best practices: testing strategies http://jira.codehaus.org/browse/MNG-1381 MNG-2584Rebuild on pom change http://jira.codehaus.org/browse/MNG-2584 MNG-2381improved control over the repositories in the POM http://jira.codehaus.org/browse/MNG-2381 MNG-1950Ability to introduce new lifecycles phases http://jira.codehaus.org/browse/MNG-1950 MNG-1468best practices: version management in multi project builds http://jira.codehaus.org/browse/MNG-1468 MNG-416 best practices: multiple profile deployments http://jira.codehaus.org/browse/MNG-416 MNG-367 best practices: multi-user installation http://jira.codehaus.org/browse/MNG-367 MNG-125 guarded mojo execution http://jira.codehaus.org/browse/MNG-125 MNG-41 best practices: site management http://jira.codehaus.org/browse/MNG-41 MNG-657 possible chicken and egg problem with extensions http://jira.codehaus.org/browse/MNG-657 MNG-1441Starting thinking about a proper distributed repository mechanism a la CPAN http://jira.codehaus.org/browse/MNG-1441 MNG-868 Use uniform format for and other tags http://jira.codehaus.org/browse/MNG-868 MNG-1423best practices: setting up multi-module build http://jira.codehaus.org/browse/MNG-1423 MNG-1463best practices: plugin inheritance for a multi project build http://jira.codehaus.org/browse/MNG-1463 MNG-1425best practices: the location of configuration files vs resources http://jira.codehaus.org/browse/MNG-1425 MNG-1569Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare http://jira.codehaus.org/browse/MNG-1569 MNG-1867deprecate system scope, analyse other use cases http://jira.codehaus.org/browse/MNG-1867 You may edit this subscription at: http://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341&filterId=11471 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Get the effective pom to a program
> I want to get the effective pom of a given pom file in to a progam that I am > writing. Is there a way to reuse the code in the maven help plugin to get > this done? 1. Probably should be asking this on Maven Users list. 2. This should do it: mvn help:effective-pom | your-program Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: IT failures of Maven Compiler Plugin
Milos Kleint wrote: is there something I set up on the grid to have myself notified of failures? IIRC, you can just sign up for an account on Hudson and then configure your mail address. Besides, I just updated the job to send mails to notificati...@maven.apache.org as well. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: IT failures of Maven Compiler Plugin
this should fix it, passed for me locally.. http://fisheye.codehaus.org/changelog/plexus/?cs=8655 I suppose the grid gets back to normal once new plexus-compiler snapshot gets uploaded. does the compiler-plugin hudson job need manual poking? milos On Thu, Feb 25, 2010 at 9:29 PM, Milos Kleint wrote: > is there something I set up on the grid to have myself notified of > failures? > > "Failed to send e-mail to mkleint because no e-mail address is known, and > no default e-mail domain is configured Sending e-mails to: > ol...@apache.org pg...@apache.org bentm...@apache.org Finished: FAILURE " > > thanks > > Milos > > On Thu, Feb 25, 2010 at 9:17 PM, Milos Kleint wrote: > >> yes, looking into it.. >> >> Milos >> >> >> On Thu, Feb 25, 2010 at 12:00 PM, Benjamin Bentmann < >> benjamin.bentm...@udo.edu> wrote: >> >>> Hi Milos, >>> >>> it seems r911840 broke the Maven Compiler Plugin on JRE 1.5- [0], can you >>> please have a closer look? Thanks. >>> >>> >>> Benjamin >>> >>> >>> [0] https://grid.sonatype.org/ci/job/maven-plugins-ITs/changes >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >> >
Re: IT failures of Maven Compiler Plugin
is there something I set up on the grid to have myself notified of failures? "Failed to send e-mail to mkleint because no e-mail address is known, and no default e-mail domain is configured Sending e-mails to: ol...@apache.org pg...@apache.org bentm...@apache.org Finished: FAILURE " thanks Milos On Thu, Feb 25, 2010 at 9:17 PM, Milos Kleint wrote: > yes, looking into it.. > > Milos > > > On Thu, Feb 25, 2010 at 12:00 PM, Benjamin Bentmann < > benjamin.bentm...@udo.edu> wrote: > >> Hi Milos, >> >> it seems r911840 broke the Maven Compiler Plugin on JRE 1.5- [0], can you >> please have a closer look? Thanks. >> >> >> Benjamin >> >> >> [0] https://grid.sonatype.org/ci/job/maven-plugins-ITs/changes >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
Re: IT failures of Maven Compiler Plugin
yes, looking into it.. Milos On Thu, Feb 25, 2010 at 12:00 PM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote: > Hi Milos, > > it seems r911840 broke the Maven Compiler Plugin on JRE 1.5- [0], can you > please have a closer look? Thanks. > > > Benjamin > > > [0] https://grid.sonatype.org/ci/job/maven-plugins-ITs/changes > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[ANN] Maven Eclipse Plugin 2.8 Released
The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.8. This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. Please see the plugin's site for details: http://maven.apache.org/plugins/maven-eclipse-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: org.apache.maven.plugins maven-eclipse-plugin 2.8 To use the updated plugin from command line, add the flag -U the next time you invoke "mvn eclipse:eclipse" in order to have Maven check for the update and download it. Release Notes - Maven 2.x Eclipse Plugin - Version 2.8 ** Bug * [MECLIPSE-368] - Dependency configuration in DependencyManagement with exclusions is ignored * [MECLIPSE-492] - Maven Eclipse Plugin does not take dependencyManagement excludes into account when building eclipse CP configuration. * [MECLIPSE-558] - Ignoring listed AspectJ dependencies * [MECLIPSE-568] - Some compile dependencies are not added to .classpath since 2.6 * [MECLIPSE-569] - eclipse:eclipse does not add all libraries to .classpath * [MECLIPSE-584] - No eclipse classpath entries generated for aspectj dependencies * [MECLIPSE-603] - Exclusions are not applied on transitive dependencies * [MECLIPSE-631] - [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml * [MECLIPSE-633] - [Maven 3] j2ee-simple integration test fails * [MECLIPSE-637] - mvn eclipse:to-maven deploy to nexus fails if nexus security is active ** New Feature * [MECLIPSE-156] - Plugin should support setting file encoding * [MECLIPSE-178] - symbolic links need to able to be specified in the pom ** Task * [MECLIPSE-594] - set AJDT version parameter to none by default * [MECLIPSE-632] - Add markers in the generated project files that can identify them as being created by the maven-eclipse-plugin Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Eclipse Plugin 2.8
Hi, The vote has passed with the following result: +1 (binding): Benjamin Bentmann, Jason van Zyl, Arnaud Héritier, Barrie Treloar I will promote the artifacts to the central repository and continue with the release. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
IT failures of Maven Compiler Plugin
Hi Milos, it seems r911840 broke the Maven Compiler Plugin on JRE 1.5- [0], can you please have a closer look? Thanks. Benjamin [0] https://grid.sonatype.org/ci/job/maven-plugins-ITs/changes - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: annotations support in compiler mojo
Hello Mark, what are the required feaures you are after? From the glimpse at the apt plugin, I got the impression that it has quite a lot of configuration, some I didn't completely understand.. here's what already implemented in code -proc parameter to turn aannotation processing off, or enable it exclusively without compilation. default is process+compile. -s with reasonable path for generated source fles - target/generated/sources/annotations (or test-annotation when executed from test-compile mojo) -processor parameter with optional list of processor classes All these switches are only applied to javac when the source/compiler level is 1.6+. It can already be tested with the latest snapshot of maven-compiler-plugin in apache snapshot repository. What is missing? 1. -processorpath handling. Not sure how many projects have different processor path from compile path, but probably useful to have. I'm not sure how to represent it in terms of mojo parameters. Any hints, precedents welcome.. 2. -implicit - i'm entirely clueless what this is supposed to do.. 3. -Akey=value parameters for annotation processors. could be left for configuration via the generic compileArguments parameter I guess.. 4. currently we put just java source root on the -sourcepath. At least in netbeans codebase we have cases where the sourcepath is supposed to contain resources accessed by the annotation processors. Bundle properties files get checked for presence of keys at compile time etc. I've experimented with adding either target/classes or src/main/resources of source path, but neither worked now due to a bug in javac - jglick filed it under http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6929404 (might take a few days to appear). There is an ugly workaround, to define the resources in src/main/java. I expect we add the relevant portion to the compiler plugin only after at least one jdk release includes the fix. Anything else that could be described as dealbreaker for anyone? Milos On Wed, Feb 10, 2010 at 5:53 PM, Mark Hobson wrote: > Late reply on this one, but I'm certainly interested in seeing apt > support added to maven-compiler-plugin. > > There is already a separate plugin for apt over at Mojo, > apt-maven-plugin [1]. I worked on this a while back to get it into > shape and am currently using it in production. I'd be happy to see > this superseded by the compiler plugin if it incorporates all of the > existing functionality. > > Cheers, > > Mark > > [1] http://mojo.codehaus.org/apt-maven-plugin/ > > On 10 February 2010 15:21, nicolas de loof > wrote: > > Would such a dedicated plugin only apply annotation processing or replace > > compiler plugin ? This may implies duplicate configuration for compiler + > > annotation-processing plugins. Also consider slower build process as > javac > > will need to parse source code 2 times. > > > > (late) +1 for annotations support in maven-compiler-plugin > > Nicolas > > > > 2010/2/10 Brian Fox > > > >> Does it make sense to create a plugin specifically for annotation > >> processing? > >> > >> On Sat, Jan 30, 2010 at 3:06 AM, Milos Kleint > wrote: > >> > can I read silence as lazy consensus to add annotation processing to > the > >> > compiler plugin? > >> > > >> > Milos > >> > > >> > On Mon, Jan 25, 2010 at 2:48 PM, Milos Kleint > wrote: > >> > > >> >> Hello, > >> >> > >> >> I'd like to start a discussion about how annotations are supported in > >> maven > >> >> builds. I'm currently trying to use some NetBeans Platform based > >> annotations > >> >> in maven projects and I'm encountering some problems. > >> >> > >> >> 1. http://jira.codehaus.org/browse/MCOMPILER-98 - -sourcepath needs > to > >> be > >> >> always set to have the annotations processed. fixed in latest plexus > >> >> compiler sources.. > >> >> 2. some annotation processors require resources to be present on the > >> >> sourcepath eg. one that generates java beans from schema or another > one > >> that > >> >> checks for property bundle key presence. I'm not sure how to make > this > >> >> generally available to the processor. resources themselves (in > >> >> src/main/resources) are not to be referenced I guess (as they could > be > >> on > >> >> wrong or not filtered). So the only other option is to > >> include > >> >> the target/classes folder somehow with the correctly processed > >> resources. > >> >> Any other idea? > >> >> 3. Some annotation processors generate xml files or META-INF/services > >> >> content, some generate java files. the default output location for > the > >> >> processor is target/classes, which is fine for xml files, but it's > >> >> inconvenient to generate java files there as they end up in the jar > file > >> >> then. I've tried to configure the compiler to use > >> >> target/generated-sources/annotations as the output folder for sources > >> (via > >> >> -s switch). Unfortunately there are problems associated with > that > >> >> approach. > >> >>a. the folder needs to
Re: annotations support in compiler mojo
Well, the javac executable is caapable of doing both jobs (compile and process annotations) simultaneously. And with reasonable defaults we can make the annotation processing work out of the box for majority of people. Having a special plugin for it, with comfiguration etc would make it more complicated to setup and maintain. Milos On Wed, Feb 10, 2010 at 3:52 PM, Brian Fox wrote: > Does it make sense to create a plugin specifically for annotation > processing? > > On Sat, Jan 30, 2010 at 3:06 AM, Milos Kleint wrote: > > can I read silence as lazy consensus to add annotation processing to the > > compiler plugin? > > > > Milos > > > > On Mon, Jan 25, 2010 at 2:48 PM, Milos Kleint wrote: > > > >> Hello, > >> > >> I'd like to start a discussion about how annotations are supported in > maven > >> builds. I'm currently trying to use some NetBeans Platform based > annotations > >> in maven projects and I'm encountering some problems. > >> > >> 1. http://jira.codehaus.org/browse/MCOMPILER-98 - -sourcepath needs to > be > >> always set to have the annotations processed. fixed in latest plexus > >> compiler sources.. > >> 2. some annotation processors require resources to be present on the > >> sourcepath eg. one that generates java beans from schema or another one > that > >> checks for property bundle key presence. I'm not sure how to make this > >> generally available to the processor. resources themselves (in > >> src/main/resources) are not to be referenced I guess (as they could be > on > >> wrong or not filtered). So the only other option is to > include > >> the target/classes folder somehow with the correctly processed > resources. > >> Any other idea? > >> 3. Some annotation processors generate xml files or META-INF/services > >> content, some generate java files. the default output location for the > >> processor is target/classes, which is fine for xml files, but it's > >> inconvenient to generate java files there as they end up in the jar file > >> then. I've tried to configure the compiler to use > >> target/generated-sources/annotations as the output folder for sources > (via > >> -s switch). Unfortunately there are problems associated with that > >> approach. > >>a. the folder needs to exist up front or the compiler chokes on it. > >> Doable with some ant-run scripting, but ugly. > >>b. what to do with the resources there that need to be copied to the > >> target/classes folder? Doable with resources:copy-resources but again > ugly. > >> 4. reporting from the annotations processors is broken - > >> http://jira.codehaus.org/browse/MCOMPILER-66 > >> > >> > >> Issue http://jira.codehaus.org/browse/MCOMPILER-75 seems to be > dedicated > >> to annotation support. Is anyone actively working on it? I'm > volunteering to > >> add some of the required switches as prameters for the compiler mojo, > but > >> I'm unsure how to proceed. Is it ok just to add the required stuff as > mojo > >> params, even if it will be unused by some of the other compilers? and > even > >> by the non 1.6 javac compilers? or have some new ways fo configuring the > >> mojo (as pointed out in http://jira.codehaus.org/browse/MCOMPILER-14)? > >> > >> Thanks for any comments. > >> > >> Milos > >> > >> PS: I can provide a sample project with the above mentioned annotations > >> being used if there is interest. > >> > >> > >> > >> > >> > >> > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Get the effective pom to a program
I want to get the effective pom of a given pom file in to a progam that I am writing. Is there a way to reuse the code in the maven help plugin to get this done? Thanks, Pubudu
