Re: A required plugin was not found: Plugin could not be found
The cobertura plugin is not finished yet. I recommend you pop over to http://jira.codehaus.org/browse/MCOBERTURA-2 and http://jira.codehaus.org/browse/MCOBERTURA-5 and vote on those issues Kind regards, Dave Sag Boris Lenzinger <[EMAIL PROTECTED]> wrote on 15-03-2006 11:03:35: > Hi, > > I'm newbie in Maven and I'm exploring this great tool. I'm using it for > a personnal project but I encounter a problem that I cannot fix. I've > searched on the ML and googled with no result on this problem. > > I'm using Maven 2.0.2. > > I want to generate code coverage reports on the project (and some other > like jdepend, changes, etc). I saw cobertura-maven-plugin and wanted to > use it. > In the central repository, it seems to be working with Maven1 only. I > get a NullPointerException that is raised which is caracteristic of > trying to use a plugin of Maven1 with Maven2 no ? I saw some mails about > this in the ML saying plugins were not up-to-date. > > I've searched for a repository that could have the plugins I'm > interested in for Maven2. I found one here > (http://snapshots.maven.codehaus.org/maven2). > > I then added to settings.xml a profile where I added the repository. At > last I've set the profile as always active. > Here is the declaration: > > > additional-repository > > > > codehaus > Code Haus snapshots. > http://snapshots.maven.codehaus.org/maven2 > default > > > > > > > additional-repository > > > Declaration in the pom file: > > org.codehaus.mojo > cobertura-maven-plugin > 2.0-20060130.214008-3 > > > Then I execute the command mvn site. > > Maven starts to download the pom file related to the plugin and then say > that it cannot find the plugin. > Here is the exact message: > +-+-+-+-+-+-+-+-+-+ START OF MESSAGE +-+-+-+-+-+-+-+-+-+ > > [INFO] Building Common Classes > [INFO] task-segment: [site] > [INFO] > > Downloading: > http://snapshots.maven.codehaus. > org/maven2/org/codehaus/mojo/cobertura-maven-plugin/2.0- > SNAPSHOT/cobertura-maven-plugin-2.0-20060130.214008-3.pom > 3K downloaded > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] A required plugin was not found: Plugin could not be found - > check that the goal name is correct: Unable to download the artifact > from any repository > > > org.codehaus.mojo:cobertura-maven-plugin:maven-plugin:2.0-20060130.214008-3 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > > org.codehaus.mojo:cobertura-maven-plugin:maven-plugin:2.0-20060130.214008-3 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > +-+-+-+-+-+-+-+-+-+ END OF MESSAGE +-+-+-+-+-+-+-+-+-+ > > I've tried tons of things but with no success. I've search in the > mailing list but found nothing (well for the problem else I found some > interesting references to plugin or some fixes for other problems I > could have). > > In the FAQ there is a section that answers to this but it is not > applying to me since I'm not behind a proxy and it was working fine > until I want those plugins from a special repository. > > So I ask for help since I cannot find a solution. > > Any help would be greatly appreciated. > > thanks in advance > > Boris > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: [M2] Jcoverage plugin?
There are a few serious bugs with cobertura and maven 2. i've been plugging away with it for a while now and if you build maven from source it does work but only for single project builds. multi-project builds all report zero coverage. see http://jira.codehaus.org/browse/MCOBERTURA-2 and http://jira.codehaus.org/browse/MCOBERTURA-5 for examples. i urge you to vote on these issues in Jira. cobertura not working properly is pretty much my final showstopper for getting maven 2 approved for use here at work. Kind regards, Dave Sag "Siegmann Daniel, NY" <[EMAIL PROTECTED]> wrote on 13-03-2006 23:16:13: > Will it be moved out of the sandbox when 2.0.3 is released, do you think? > > Anyway, thanks for the info. > > ~Daniel > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 13, 2006 1:39 PM > > To: Maven Users List > > Subject: Re: [M2] Jcoverage plugin? > > > > > > The Cobertura plug-in for Maven2 depends on features > > introduced in Maven 2.0.3. Until 2.0.3 is released, I > > personally wouldn't use it (the Cobertura plug-in) in Production code. > > > > > > Ian > > > > > There is, cobertura, I don't know if it is ok though. I had > > to build it from cvs. But that was a while ago... > > > > On 3/13/06, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote: > > > > > > Is there a jcoverage plugin for Maven 2, or any plans to > > create one? I > > did > > > not see one on Mojo. If not, is there an equivalent tool I can use? > > > > > > -- > > > Daniel Siegmann > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: custom src directory layout - how to get it to not checkstyle/javadoc the tests too.
"Wayne Fay" <[EMAIL PROTECTED]> wrote on 10-03-2006 18:00:22: > Easiest answer is to move to Subversion. There are tools to facilitate > this so you can save your history out of CVS. > easier said than done here I am afraid. certainly that's what I have done for all of my personal and freelance projects, but in here at the EPO we face considerable technological inertia. getting permission to begin to migrate projects from ant builds to maven 2 was a huge effort here. if i was the supreme executive dark lord of development i'd have replaced our lotus notes based bug tracker with jira, cvs with svn and cruise-control with continuum too. they are battles i'll not win here as such wide-ranging changes affect many hundreds of developers across many departments and I am a but a mere contractor. Hell it took some doing just to get an english language keyboard instead of the standard swiss-german one they issue you with here. Even now I can't properly enter single or double quotes and have to copy and paste should I need one. In fact when I aksed the help-desk people about it they just laughed and told me the single quote key has been remapped as so many of our staff have characters like 'é' or 'ü' in their names. (and they wonder why i prefer to work on my mac!) as an old boss of mine used to say "politiics is the art of the possible." cheers dave > Then restructure your project. > > Wayne > > > On 3/10/06, Thorsten Heit <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi, > > > > > the directory structure we have is > > > > > > pom.xml > > > src/ > > > - org/ > > > > Maven uses src/java/... per default. Have you tried that? > > > > > > Regards > > > > Thorsten > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.2.1 (MingW32) > > > > iD8DBQFEEXUbQvObkgCcDe0RAurvAJ9R6yQpsS7OKSBa+mnJkkwvNkTVTQCfWdx9 > > PKyRi1m9fa9lNLqFYjMP1uU= > > =Jkxh > > -END PGP SIGNATURE- > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > >
Re: custom src directory layout - how to get it to not checkstyle/javadoc the tests too.
Thorsten Heit <[EMAIL PROTECTED]> wrote on 10-03-2006 13:46:19: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > > the directory structure we have is > > > > pom.xml > > src/ > > - org/ > > Maven uses src/java/... per default. Have you tried that? > unfortunately I do not have permission to change the folder heirarchy for our projects. This is mostly because: 1) we have hundreds of projects 2) we have hundreds of developers 3) we use CVS not SVN internally and CVS don't do folder heirarchy changes while preserving version histories. I am able to move the tests into the m2 preferred folder heirarchy however as we have SFA tests in any of our projects. I wonder if I would be better off with a heirarchy more like pom.xml src/ - org/... test/ - java/ -- org/... that would certainly keep the tests apart from the main source, but I'd really rather at least start the process of moving to the m2 preferred arrangement. thoughts? dave
Re: Maven documentation (was Re: how to include all dependencies in your jar)
I heard about a very interesting way to attack this problem a couple of years ago in the Cocoon project. At one of the big cocoon user/dveleoper conferences (it could even have been at an apachecon) a small room of people with varying degrees of familiarity with the source code worked collaborativly for a stretch of about 6 hours to clean up the top 100 issues facing cocoon, including tons of documentation. The proceedure was very simple but needs some tools. Ingredients: - 1 projector to display the list of issues for all to see - some developers with commit rights - 5 x that many other people willing to collaborate - everyone needs an apple mac and SubEthaEdit (collaborative text editor) and iChat. method - small teams (max 6 including the key-dev ala the dinner party principle) rally about a developer with commit rights - the key-dev as i shall call her - and choose an issue to address. - key-dev opens master copy of code in SEE and other developers connect to that via bonjour. - everyone makes changes / be they code, javadocs, useage docs or whatever. - using ichat's status indicators to show others if you are still working or done with your specific changes. - when all done key-dev saves / builds / tests etc - fix any new issues that have emerged from this cycle - when done key-dev commits to SVN and the team is free to disband and form a new team, or just keep on going with another issue. I use the term swarm development to describe this approach and after hearing about it from an apache mate we tried it within my old workplace where many of the developers used macs. it was quite astounding how quickly issues, especially documentation issues were nailed. My suggestion is to coordinate a maven users / developers conference somwhere where the weather is nice (I hear the April sun in Cuba is nice) and we all collaboratively fix as many of the outstanding documentation issues as we can. iChat and SEE work over the wider internet too but there's nothing quite like having a bunch of people in a single room attacking a set of problems at once. the vibe is intense. Kind regards, Dave Sag "Brett Porter" <[EMAIL PROTECTED]> wrote on 07-03-2006 04:14:18: > I tihnk you both make pretty good points on this, even where you might > agree to disagree. Unfortunately I don't have time to reply to this > entire thread, but I couldn't resist this point: > > On 3/7/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > > > > > > And fourthly, the developers are often *not* the best people to write > > > the documentation. For someone who knows all the details of an > > > implementation it's quite hard to step back and write good introductory > > > tutorials. > > > > On a roll here - although I'd replace "often" with "definitely". What > > would be truly beneficial would be to have someone IN CHARGE (as much as > > certain people are "IN CHARGE" of certain parts of the code) of > > providing USER documentation for each release. A developer? Sure. But > > NOT a core developer that "just knows". > > All you are talking about here is a contributing user. There is > nothing stopping any user making that transition, and it would be > welcomed - in fact, the minute we find one we'll hold on and never let > go. It's rare for people to only contribute to documentation, and the > couple who have volunteered to do so in the past have either ended up > preferring to code or getting burned out on it very quickly. > > By the way, in our projects, its rare for anyone to be in charge for > anything code or documentation. The whole project is responsible for > everything, and people do what they have to for their work or itches > as time allows. As a project, we try and direct people with the > capacity to the right areas. > > Now, we do know there are missing pieces of documentation, and are > correcting that over time. It's also my personal vendatta to write > docs for new functionality at least going forward, and even if they > are brief so that people can expand on them easily. > > The key point of this all was that it is impossible for developers to > know exactly where the holes are now. Rants about documentation are > not going to change anything - *we already know* it needs work, and > always will need work, as you've both said. > > But there are many ways you can contribute: > * file a bug for specific documentation problems. Even if you don't > know the answer, say what you couldn't find or couldn't understand. > * pick up a bug and research that single topic and write a doc for it. > * put together outlines for other people to flesh out. > > As for the wiki, we consider that a workspace. Please use it if you > can, and suggest ways to integrate it into the site if you find uesful > things there. Patches are best - APT is no harder to write than wiki > markup. > > Thanks for your concern! > > - Brett > > - > To unsubscribe, e-mail: [EMA
custom src directory layout - how to get it to not checkstyle/javadoc the tests too.
Hi All, I am beginning now to migrate many of our projects to maven 2, but I am not permitted to move the location of the stuff in the src directory as CVS is unable to retain the history in this case and we have no plans to move to something more useful such as subversion. the directory structure we have is pom.xml src/ - org/ -- epo/ -- etc - site/ -- apt/ --- index.apt -- fml/ --- faq.fml -- site.xml -test/ -- java/ --- org/ epo/ - etc i tried setting my to src/ but the compiler then tries to build everything in the test directory as well. so i tell maven2 to exclude src/test and src/site from the main compile goal **/test/** **/site/** into my parent pom's compiler config, and that works fine, but now cobertura is not instrumenting any of my classes (or indeed even being invoked as far as i can tell) running mvn site however pretends to generate a cobertura report but it just ends up being blank - this is a showstopper for me. cobertura generates the following error: net.sourceforge.cobertura.reporting.ComplexityCalculator - cannot find source file during CNN computation ... so clearly cobertura is not finding the source files. (i have added a comment to this effect to http://jira.codehaus.org/browse/MCOBERTURA-2) the following problems are annoying but i have live with them for now: also the javadocs are being generated for the test classes. there is no config for the javadoc tool according to the documentation. i tried adding an excludes config as per the compiler plugin but, while it threw no error, neither did it actually have any effect. checkstyle's excludes config param uses a different syntax to the compiler's excludes syntax and the format is not documented. is it a comma separated list of paths? either way i tried adding **/test/** but that made no difference at all. pmd reports fail as they are looking for the src in src/main/java and ignoring the sourceDirectory (but PMD is being a pain anyway so i am not so concerned with this at the moment) it seems to me that the tag could do with having some in-build excludes and includes sub-tags Kind regards, Dave Sag
Re: [m2] multi-project problems
Interesting - for me it's the cobertura report that is breaking my overall site build. i'll have to experiment offline for a few days tho as I am about to be away. seems strange to have a different general philosophy for reports as for build. indeed i find it odd that the reporting is so clearly separate from the overall build lifecycle. almost like it was an afterthought. for me the reports are the most important part of a build. Kind regards, Dave Sag [EMAIL PROTECTED] wrote on 01-03-2006 17:12:36: > Here is a section from my parent pom.xml that causes all the reports to run > on the parent and alll the children. The parent has no source and so > checkstyle complains but it doesn't kill the site build and continues on. > The generated site does end up with some links in the left sidebar that go > nowhere though. I just live with it. > > One thing (or two) to note is that the changelog report requires a valid > section in the pom. I also have a > section in each of the poms (parent and child) to tell the site:deploy > target where to put the generated stuff on my site server. That may be > because of the way I have done things and not really be required. You get to > fiddling around with the maven setup and when it works good enough it gets > frozen without any backtracking to do it a better way. > > > > > org.codehaus.mojo > jxr-maven-plugin > > > org.apache.maven.plugins > maven-javadoc-plugin > > 1.4 > > > > org.apache.maven.plugins > maven-project-info-reports-plugin > > > org.codehaus.mojo > surefire-report-maven-plugin > > > org.apache.maven.plugins > maven-checkstyle-plugin > > ../AA-IFS-checkstyle-rules.xml > > ../license.txt > > > > org.codehaus.mojo > changelog-maven-plugin > > > > > On 3/1/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > > > There might be a reportManagement section, there is a dependencyManagement > > section. Take a look at the project descriptor under "where is it" on the > > maven page. > > > > > > > > From: David Sag [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 01, 2006 10:40 AM > > To: Maven Users List > > Subject: RE: [m2] multi-project problems > > > > > > > > Hi Brian, > > > > Your suggestion worked well, while it's not quite what I was after (I > > wanted to leave the build details out of the sub-project altogether) but > > hey, we can't always get what we want. > > > > But there is no equivalent for the reporting section of the pom. how do I > > define a standard suite of reports in a parent pom? or failing that at > > least define how the report plugins are configured in the parent. > > > > any tips? > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 15:28:25: > > > > > if you put something in the plugins section of the parent, it will > > > run with the parent. To do what you want, you should put the config > > > in the parent's pluginManagement section. Then in each child you > > > just need to put the plugin group and id in the build/plugin section > > > but the configuration will be inherited. > > > > > > > > > > > > From: David Sag [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, March 01, 2006 8:49 AM > > > To: Maven Users List > > > Subject: RE: [m2] multi-project problems > > > > > > > > > > > > aha. okay i had my parent pom called generic-pom.xml as I was only > > > interesed in building some of our 'generic' projects for now. > > > > > > just to get a first-stab working i have renamed it to pom.xml and > > > moved my local folder heirarchy about a bit and voila - it seems to > > > work when i run mvn test > > > > > > but when i run mvn install from the parent it complains that there > > > are no source directories to process for checkstyle - that's
Re: [m2] Multiple Goals In Pom
After setting up your pom you'd just call [mvn clean deploy] and it will do everything in the build lifecycle to that point. see http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Kind regards, Dave Sag "Adam Leggett" <[EMAIL PROTECTED]> wrote on 01-03-2006 17:03:44: > Hi all, > > May be a simple answer to this, but how in my pom do I define multiple > goals to be executed. > > I can achieve the desired result by typing at cmd prompt mvn > [plugin1:goal1] [plugin2:goal2] ... [pluginn:goaln] > > But I would like to be able to simply type mvn and have these goals > execute. > > Specifically I wish to run clean, install then jboss:deploy. Can this > been done via the pom? > > In ANT I would define a 'master' target to aggregate the others. What is > the maven approach to this? > > TIA > > Adam > > Adam Leggett <[EMAIL PROTECTED]> > Senior Consultant > UPCO > Direct Line: 0113 20 10 631 > Fax: 0113 20 10 666 > > > > > > === > The contents of this email are intended for the named addresses and may > contain confidential and/or privileged material. If received in error, > please contact UPCO head office on +44(0)113 201 0600 and then delete > the entire mail from your system. Unauthorised review, distribution, > disclosure or other use of information could constitute a breach of > confidence. Your co-operation in this matter is greatly appreciated. > > Every effort has been taken to ensure that this email and any > attachments are virus-free. However, UPCO does not make any warranty > to this effect, and is not liable for any damage done by an infected > email message or attachment. UPCO recommends that all emails and > attachments are checked before opening. > > All views or opinions expressed in this electronic message and its > attachements are those of the sender and do not necessarily reflect > the views and opinions of The Ultimate People Company Ltd. > === > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: [m2] multi-project problems
Yep I looked there but no-dice. I'll have to give up on this now as I am offline until mid-next week. thanks for your help and perhaps (fingers xxed) someone who's actually done what I am trying to do (use a master pom.xml to define all common build/dependency/reporting/profile/developer details, thus making the poms for each subproject very very simple and generate a common and consistent suite of build-artifacts and reports) will post to this list with some definitive answers. thanks for your help however. I am documenting all of this as I go as I need to write up impact assesments later this month and assess at that point if we migrate to m2 or stick with ant. so far it's much simpler to just import an ant script with the appropriate reporting targets from a common location than it is to set up pom-inheritance. but that's probably because I still don't really know what I am doing with m2. (and that's partially because every time i want to try something new i need to research it and often end up having to write my own documentation, wheras Ant is very well understood by everyone here and there is a vast existing base [spaghetti mostly] of ant scripts.) if i can get what i want to work working i am happy to contribute documentation to the maven project. but i am still not sure i have my head in the right place to qualify myself for that task. Kind regards, Dave Sag "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 16:56:41: > There might be a reportManagement section, there is a > dependencyManagement section. Take a look at the project descriptor > under "where is it" on the maven page. > > > > From: David Sag [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 10:40 AM > To: Maven Users List > Subject: RE: [m2] multi-project problems > > > > Hi Brian, > > Your suggestion worked well, while it's not quite what I was after > (I wanted to leave the build details out of the sub-project > altogether) but hey, we can't always get what we want. > > But there is no equivalent for the reporting section of the pom. how > do I define a standard suite of reports in a parent pom? or failing > that at least define how the report plugins are configured in the parent. > > any tips? > > Kind regards, > Dave Sag > > > > > > > "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 15:28:25: > > > if you put something in the plugins section of the parent, it will > > run with the parent. To do what you want, you should put the config > > in the parent's pluginManagement section. Then in each child you > > just need to put the plugin group and id in the build/plugin section > > but the configuration will be inherited. > > > > > > > > From: David Sag [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 01, 2006 8:49 AM > > To: Maven Users List > > Subject: RE: [m2] multi-project problems > > > > > > > > aha. okay i had my parent pom called generic-pom.xml as I was only > > interesed in building some of our 'generic' projects for now. > > > > just to get a first-stab working i have renamed it to pom.xml and > > moved my local folder heirarchy about a bit and voila - it seems to > > work when i run mvn test > > > > but when i run mvn install from the parent it complains that there > > are no source directories to process for checkstyle - that's right > > the only thing in the parent is the pom.xml file. > > > > is that a bug in checkstyle, or a design feature that build plugins > > in a parent pom actually expect something to be in the parent > > project folder other than the pom. > > > > in general I am going to want to put all common build, test and > > reporting config in an otherwise void parent project and extend as > > needed in sub-projects is that not the right idea? maybe i have > > misunderstood it. > > > > on this point, say i have set up checktyle in the master pom but for > > some reason checktyle crashes while processing a sub-project (it > > happens if there are way too many checktyle errors for examplek that > > it can run out of memory.) is there a way of subtractively extending > > the parent, ie to tell one specific sub-project not to generate a > > checkstyle report, or would i have to remove it from the master and > > add it in to all sub-projects by hand until the offending project > > has been fixed? > > > > Kind regards, > > Dave Sag > > > >
RE: [m2] multi-project problems
Hi Brian, Your suggestion worked well, while it's not quite what I was after (I wanted to leave the build details out of the sub-project altogether) but hey, we can't always get what we want. But there is no equivalent for the reporting section of the pom. how do I define a standard suite of reports in a parent pom? or failing that at least define how the report plugins are configured in the parent. any tips? Kind regards, Dave Sag "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 15:28:25: > if you put something in the plugins section of the parent, it will > run with the parent. To do what you want, you should put the config > in the parent's pluginManagement section. Then in each child you > just need to put the plugin group and id in the build/plugin section > but the configuration will be inherited. > > ____ > > From: David Sag [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 8:49 AM > To: Maven Users List > Subject: RE: [m2] multi-project problems > > > > aha. okay i had my parent pom called generic-pom.xml as I was only > interesed in building some of our 'generic' projects for now. > > just to get a first-stab working i have renamed it to pom.xml and > moved my local folder heirarchy about a bit and voila - it seems to > work when i run mvn test > > but when i run mvn install from the parent it complains that there > are no source directories to process for checkstyle - that's right > the only thing in the parent is the pom.xml file. > > is that a bug in checkstyle, or a design feature that build plugins > in a parent pom actually expect something to be in the parent > project folder other than the pom. > > in general I am going to want to put all common build, test and > reporting config in an otherwise void parent project and extend as > needed in sub-projects is that not the right idea? maybe i have > misunderstood it. > > on this point, say i have set up checktyle in the master pom but for > some reason checktyle crashes while processing a sub-project (it > happens if there are way too many checktyle errors for examplek that > it can run out of memory.) is there a way of subtractively extending > the parent, ie to tell one specific sub-project not to generate a > checkstyle report, or would i have to remove it from the master and > add it in to all sub-projects by hand until the offending project > has been fixed? > > Kind regards, > Dave Sag > > > > > > > "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 14:33:40: > > > It will try to find the parent at ../pom.xml and then look in the > > local repository. If you never built the parent before and you don't > > have the pom one folder up, then it won't work. The safest thing is > > to keep your parent pom immediately above your children: > > > > Parent pom.xml > > module a > > module b > > sub modules parent pom.xml > > sub a > > sub b > > > > etc > > > > -Original Message- > > From: Piéroni Raphaël [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 01, 2006 8:14 AM > > To: Maven Users List > > Subject: Re: [m2] multi-project problems > > > > Hi Dave, > > > > Have you tryed to call mvn install from the parent directory ? > > > > You can also reference the parent by adding a in the > > parent definition in the child pom. (never used it myself) > > > > May that helps. > > > > Raphaël > > > > 2006/3/1, David Sag <[EMAIL PROTECTED]>: > > > > > > > > > Dear people, > > > > > > I am having my first proper stab at doing a milti-project build, but > > > naturally have hit some immediate problems. > > > > > > Firstly I have scoured the maven site and google but can't find any > > > sound documentation on how the multi-project builds are meant to work. > > > I did find this page > > > http://maven.apache.org/guides/mini/guide-multi-module.html but it's a > > > little low on detail. > > > > > > But from the bits and pieces I could patch together from this mailing > > > list I have done the following. > > > > > > I have created a master pom.xml file that specifies > > > > > > packaging: pom > > > version: 2.3-SNAPSHOT (i just made this up for now - yes snapshots are > > > working) > > > url: a url for the group of projects &g
Re: xDoc i18n base language HTML placed in wrong directory
Lance Bader
wisely said:
"Automatic
redirection based on browser locale is a good idea for a consumer
site but our multi-lingual users are aggravated if they have to change
the
browser's locale in order to view a particular language. A multi-lingual
front page allowing quick choices to a particular version is much
preferred."
as an expat aussie living in europe
i couldn't agree more. try buying anything from the apple store in
the netherlands as an english speaker - it's insanity. i am happy for sites
to pick up the country from the browser (or ip number) but they should
always allow the user to select their preferred language.
that's my 2cents (ie my euro 0.01421512)
worth
Kind regards,
Dave Sag
"Lance Bader" <[EMAIL PROTECTED]>
wrote on 01-03-2006 15:58:42:
> No, I double checked my prototype web site. If a directory does
not contain
> any xdoc source files (like images or styles in my structure), it
is copied
> to the base directory but not the language directories. Maybe
this is a
> defect?
>
> Better yet, use the value specified as the base language, ${
> maven.xdoc.locale.default}, if specified explicitly rather than left
> unspecified, in the root of docs.
>
> Automatic redirection based on browser locale is a good idea for a
consumer
> site but our multi-lingual users are aggravated if they have to change
the
> browser's locale in order to view a particular language. A multi-lingual
> front page allowing quick choices to a particular version is much
> preferred.
>
> Lance
>
> On 2/27/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> >
> > I think that user resources (images, ..) are copied in each language
> > directory and in the top directory.
> > We put the default language in the root of the documentation
because we
> > didn't know what to add in the root of the docs without it ?
> > A default home page with links for all documentations ? It's
not very nice
> > for a project homepage.
> > What I prefered was to have a redirection page which move the
user to the
> > default language subdirectory.
> > But how to do that ? It's not really standard to use the meta
tag
> > "refresh".
> >
> > Arnaud
> >
> > On 2/27/06, Lance Bader <[EMAIL PROTECTED]> wrote:
> > >
> > > I'm willing to believe I'm wrong, but if the base langague
is xx,
> > > shouldn't
> > > the generated HTML be placed in ${maven.docs.dest}/xx?
> > >
> > > Consider this scenario.
> > >
> > > - Assume that there are number of files that are copied,
not generated
> > > from
> > > XML source, including images, style sheets, Javadoc, and
code templates.
> > >
> > > - The base language source files contain relative URLs to
these files.
> > >
> > > - The team who translates the base language source files
are only
> > changing
> > > the text between the tags. They are not changing relative
URLs. Even
> > if
> > > they understand URLs, they don't know which relative URLs
must be
> > > modified.
> > >
> > > - For each supported language yy, the generated HTML is
placed in ${
> > > maven.docs.dest}/yy. If the base language xx is placed
in ${
> > > maven.docs.dest}
> > > instead of ${maven.docs.dest}/xx, all of the relative URLs
that
> > reference
> > > files that are not generated by the xDoc plugin must be
different for
> > the
> > > base language and the other languages.
> > >
> > > Of course, for me, it is much more pleasing to see all the
supported
> > > languages, including the base language, appear in parallel
directory
> > trees
> > > where the name of the root is the ISO language code. However,
if my
> > sense
> > > of aesthetics and symmetry is blinding me a better solution,
I will just
> > > have to ignore my senses.
> > >
> > > Lance
> > >
> > >
> >
> >
RE: [m2] multi-project problems
Hi Brian, thanks for that tip - i'll give it a try now. where are you getting this knowledge from? hard-won experience or is there a docuement somewhere I could read? Kind regards, Dave Sag "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 15:28:25: > if you put something in the plugins section of the parent, it will > run with the parent. To do what you want, you should put the config > in the parent's pluginManagement section. Then in each child you > just need to put the plugin group and id in the build/plugin section > but the configuration will be inherited. > > ________ > > From: David Sag [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 8:49 AM > To: Maven Users List > Subject: RE: [m2] multi-project problems > > > > aha. okay i had my parent pom called generic-pom.xml as I was only > interesed in building some of our 'generic' projects for now. > > just to get a first-stab working i have renamed it to pom.xml and > moved my local folder heirarchy about a bit and voila - it seems to > work when i run mvn test > > but when i run mvn install from the parent it complains that there > are no source directories to process for checkstyle - that's right > the only thing in the parent is the pom.xml file. > > is that a bug in checkstyle, or a design feature that build plugins > in a parent pom actually expect something to be in the parent > project folder other than the pom. > > in general I am going to want to put all common build, test and > reporting config in an otherwise void parent project and extend as > needed in sub-projects is that not the right idea? maybe i have > misunderstood it. > > on this point, say i have set up checktyle in the master pom but for > some reason checktyle crashes while processing a sub-project (it > happens if there are way too many checktyle errors for examplek that > it can run out of memory.) is there a way of subtractively extending > the parent, ie to tell one specific sub-project not to generate a > checkstyle report, or would i have to remove it from the master and > add it in to all sub-projects by hand until the offending project > has been fixed? > > Kind regards, > Dave Sag > > > > > > > "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 14:33:40: > > > It will try to find the parent at ../pom.xml and then look in the > > local repository. If you never built the parent before and you don't > > have the pom one folder up, then it won't work. The safest thing is > > to keep your parent pom immediately above your children: > > > > Parent pom.xml > > module a > > module b > > sub modules parent pom.xml > > sub a > > sub b > > > > etc > > > > -Original Message- > > From: Piéroni Raphaël [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 01, 2006 8:14 AM > > To: Maven Users List > > Subject: Re: [m2] multi-project problems > > > > Hi Dave, > > > > Have you tryed to call mvn install from the parent directory ? > > > > You can also reference the parent by adding a in the > > parent definition in the child pom. (never used it myself) > > > > May that helps. > > > > Raphaël > > > > 2006/3/1, David Sag <[EMAIL PROTECTED]>: > > > > > > > > > Dear people, > > > > > > I am having my first proper stab at doing a milti-project build, but > > > naturally have hit some immediate problems. > > > > > > Firstly I have scoured the maven site and google but can't find any > > > sound documentation on how the multi-project builds are meant to work. > > > I did find this page > > > http://maven.apache.org/guides/mini/guide-multi-module.html but it's a > > > little low on detail. > > > > > > But from the bits and pieces I could patch together from this mailing > > > list I have done the following. > > > > > > I have created a master pom.xml file that specifies > > > > > > packaging: pom > > > version: 2.3-SNAPSHOT (i just made this up for now - yes snapshots are > > > working) > > > url: a url for the group of projects > > > description: a description for the group of projects > > > modules: i just listed one module for now > > > issueManagement: same for all projects so i put it here > > > ciManagement: same for all projects so i pu
RE: [m2] multi-project problems
aha. okay i had my parent pom called generic-pom.xml as I was only interesed in building some of our 'generic' projects for now. just to get a first-stab working i have renamed it to pom.xml and moved my local folder heirarchy about a bit and voila - it seems to work when i run mvn test but when i run mvn install from the parent it complains that there are no source directories to process for checkstyle - that's right the only thing in the parent is the pom.xml file. is that a bug in checkstyle, or a design feature that build plugins in a parent pom actually expect something to be in the parent project folder other than the pom. in general I am going to want to put all common build, test and reporting config in an otherwise void parent project and extend as needed in sub-projects is that not the right idea? maybe i have misunderstood it. on this point, say i have set up checktyle in the master pom but for some reason checktyle crashes while processing a sub-project (it happens if there are way too many checktyle errors for examplek that it can run out of memory.) is there a way of subtractively extending the parent, ie to tell one specific sub-project not to generate a checkstyle report, or would i have to remove it from the master and add it in to all sub-projects by hand until the offending project has been fixed? Kind regards, Dave Sag "Brian E. Fox" <[EMAIL PROTECTED]> wrote on 01-03-2006 14:33:40: > It will try to find the parent at ../pom.xml and then look in the > local repository. If you never built the parent before and you don't > have the pom one folder up, then it won't work. The safest thing is > to keep your parent pom immediately above your children: > > Parent pom.xml > module a > module b > sub modules parent pom.xml > sub a > sub b > > etc > > -Original Message- > From: Piéroni Raphaël [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 8:14 AM > To: Maven Users List > Subject: Re: [m2] multi-project problems > > Hi Dave, > > Have you tryed to call mvn install from the parent directory ? > > You can also reference the parent by adding a in the > parent definition in the child pom. (never used it myself) > > May that helps. > > Raphaël > > 2006/3/1, David Sag <[EMAIL PROTECTED]>: > > > > > > Dear people, > > > > I am having my first proper stab at doing a milti-project build, but > > naturally have hit some immediate problems. > > > > Firstly I have scoured the maven site and google but can't find any > > sound documentation on how the multi-project builds are meant to work. > > I did find this page > > http://maven.apache.org/guides/mini/guide-multi-module.html but it's a > > little low on detail. > > > > But from the bits and pieces I could patch together from this mailing > > list I have done the following. > > > > I have created a master pom.xml file that specifies > > > > packaging: pom > > version: 2.3-SNAPSHOT (i just made this up for now - yes snapshots are > > working) > > url: a url for the group of projects > > description: a description for the group of projects > > modules: i just listed one module for now > > issueManagement: same for all projects so i put it here > > ciManagement: same for all projects so i put that here too > > organization: EPO > > developers: mostly the same for all projects with a few exceptions. > > should I put all of the developers who are common to all projects here > > and then add specific decelopers to the sub-poms on a > > project by project basis? > > ditto for contributors > > build: the build plugins are the same for all projects > > profiles: once again same for all projects, excpet for the > > distributionManagement which varies from one project to the next. > > if i list the main profile definition here can i just override a > > profile > > defn with the same id in a sub-pom to add the > > distributionManagement data? > > dependencies: junit and some of the commons libs are common to all > > projects > > assume i declare them here and then declare any additional ones i > > need in > > a sub-pom. > > reporting: the same for all projects so I put that here. > > > > in my sub-project's pom i have pulled out everything that's already in > > the parent. I am not sure what to put in the 'parent' tag though, but > > tried setting a parent with the same groupId and artifactId and > > version as my parent pom file. > >
Re: [m2] multi-project problems
Okay that's going to be useful to know as I know in the mid-term i do not have the freedom to change the project heiracrchies. do you (and any other interested reader) have any pointers on docs relating to the config of the parent tag in a sub-project? Kind regards, Dave Sag "Piéroni Raphaël" <[EMAIL PROTECTED]> wrote on 01-03-2006 14:14:29: > Hi Dave, > > Have you tryed to call mvn install from the parent directory ? > > You can also reference the parent by adding a in the parent > definition in the child pom. (never used it myself) > > May that helps. > > Raphaël > > 2006/3/1, David Sag <[EMAIL PROTECTED]>: > > > > > > Dear people, > > > > I am having my first proper stab at doing a milti-project build, but > > naturally have hit some immediate problems. > > > > Firstly I have scoured the maven site and google but can't find any sound > > documentation on how the multi-project builds are meant to work. I did > > find this page > > http://maven.apache.org/guides/mini/guide-multi-module.html but it's a > > little low on detail. > > > > But from the bits and pieces I could patch together from this mailing list > > I have > > done the following. > > > > I have created a master pom.xml file that specifies > > > > packaging: pom > > version: 2.3-SNAPSHOT (i just made this up for now - yes snapshots are > > working) > > url: a url for the group of projects > > description: a description for the group of projects > > modules: i just listed one module for now > > issueManagement: same for all projects so i put it here > > ciManagement: same for all projects so i put that here too > > organization: EPO > > developers: mostly the same for all projects with a few exceptions. > > should I put all of the developers who are common to all projects here > > and then add specific decelopers to the sub-poms on a > > project by project basis? > > ditto for contributors > > build: the build plugins are the same for all projects > > profiles: once again same for all projects, excpet for the > > distributionManagement which varies from one project to the next. > > if i list the main profile definition here can i just override a > > profile > > defn with the same id in a sub-pom to add the distributionManagement > > data? > > dependencies: junit and some of the commons libs are common to all > > projects > > assume i declare them here and then declare any additional ones i need > > in > > a sub-pom. > > reporting: the same for all projects so I put that here. > > > > in my sub-project's pom i have pulled out everything that's already in the > > parent. I am not sure what to put in the 'parent' tag though, but tried > > setting a parent with the same groupId and artifactId and version as my > > parent pom file. > > > > when i try to build now however, the first thing maven does is complain it > > can't > > download the parent project from any of the repositories and then it gives > > up. > > > > naturally the parent is not in any repository as it has never ever been > > built before. > > > > so I tried just commenting out the reference to parent in the sub-project > > and then, > > using the parent pom, mvn clean works fine but compiling fails as it is > > not > > picking up any of the parent dependencies. > > > > i checked in the maven plugin's project to see how you do it there and i > > note that the > > version listed as the ant plugin's pom's parent is 2.0 but the parent pom > > itself has a version 2.0.1 > > > > Could someone please exaplain how this is all meant to work? > > > > cheers > > > > dave > > > > > > Kind regards, > > Dave Sag > > > > > > > > > >
[m2] multi-project problems
Dear people, I am having my first proper stab at doing a milti-project build, but naturally have hit some immediate problems. Firstly I have scoured the maven site and google but can't find any sound documentation on how the multi-project builds are meant to work. I did find this page http://maven.apache.org/guides/mini/guide-multi-module.html but it's a little low on detail. But from the bits and pieces I could patch together from this mailing list I have done the following. I have created a master pom.xml file that specifies packaging: pom version: 2.3-SNAPSHOT (i just made this up for now - yes snapshots are working) url: a url for the group of projects description: a description for the group of projects modules: i just listed one module for now issueManagement: same for all projects so i put it here ciManagement: same for all projects so i put that here too organization: EPO developers: mostly the same for all projects with a few exceptions. should I put all of the developers who are common to all projects here and then add specific decelopers to the sub-poms on a project by project basis? ditto for contributors build: the build plugins are the same for all projects profiles: once again same for all projects, excpet for the distributionManagement which varies from one project to the next. if i list the main profile definition here can i just override a profile defn with the same id in a sub-pom to add the distributionManagement data? dependencies: junit and some of the commons libs are common to all projects assume i declare them here and then declare any additional ones i need in a sub-pom. reporting: the same for all projects so I put that here. in my sub-project's pom i have pulled out everything that's already in the parent. I am not sure what to put in the 'parent' tag though, but tried setting a parent with the same groupId and artifactId and version as my parent pom file. when i try to build now however, the first thing maven does is complain it can't download the parent project from any of the repositories and then it gives up. naturally the parent is not in any repository as it has never ever been built before. so I tried just commenting out the reference to parent in the sub-project and then, using the parent pom, mvn clean works fine but compiling fails as it is not picking up any of the parent dependencies. i checked in the maven plugin's project to see how you do it there and i note that the version listed as the ant plugin's pom's parent is 2.0 but the parent pom itself has a version 2.0.1 Could someone please exaplain how this is all meant to work? cheers dave Kind regards, Dave Sag
RE : default skin - where do i get it?
yes that's what I thought and indeed
already had that site configured in my normal repositories config. but
as that didn't work i tried adding it as a plugin too - but that didn't
work either. specifying site beta-4 fixed the problem for now however.
making my own skin is a good plan and
we'll eventually do this - but for now i have to worry each morning that
what worked the day before will break tomorrow and have precious little
time to piss about making skins.
i am giving another presentation internally
here next thursday and for all i know there'll be a new maven 2.0.3 out
with a fixed cobertura. my problem is that i need the snapshots to
demo cobertura, but that makes my whole build rather fragile. is
there some way of locking down what i currently have that works and not
allowing any more recent snapshots until after my presentation; short of
building my own repository and forcing my dns lookup to fail on ibiblio
and other external repositories?
Kind regards,
Dave Sag
"Olivier Lamy" <[EMAIL PROTECTED]>
wrote on 24-02-2006 15:09:38:
> AFAIK, skin are resolved as artifacts but not as plugin [1] see method
> getSkinArtifactFile
>
> But to not depends on this create your own skin ;-) (very nice feature)
>
> - Olivier
>
> [1]
> http://svn.apache.org/viewcvs.cgi/maven/plugins/trunk/maven-site-plugin/
> src/main/java/org/apache/maven/plugins/site/SiteMojo.java?rev=370214&vie
> w=markup
> -Message d'origine-
> De : David Sag [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 24 février 2006 14:51
> À : Maven Users List
> Objet : Re: default skin - where do i get it?
>
>
>
> Hi Brett
>
> I added that to the pluginRepositories section of my settings.xml
(it
> was already in the repositories section) and while i can see it trying
> to look for stuff in there, i still get the same problem.
>
> fixing the site plugin to 2.0-beta-4 fixed my problem for now though
>
> Kind regards,
> Dave Sag
>
>
>
>
>
>
> "Brett Porter" <[EMAIL PROTECTED]> wrote on 24-02-2006
13:38:16:
>
> > You'll need to use this repository until the site skins and site
> plugin are
> > released:
> >
> >
> > http://cvs.apache.org/maven-snapshot-repository/
> >
> >
> > Or, you can lock your site plugin to version 2.0-beta-4 (the
current
> > release).
> >
> > - Brett
> >
> > On 2/24/06, David Sag <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Hi,
> > >
> > > I had to rebuild maven from the source files in svn as the
cobertura
> > > plugin is now demanding version 2.0.3 to run.
> > >
> > > but now the site plugin is complaining that it can't find
the skin
> > > org.apache.maven.skins:maven-default-skin:jar:RELEASE
> > >
> > > so where do I find that - please don't say I have to build
it from
> source
> > > as I am at work now where I can't access your svn repo.
> > >
> > > the mvn output says to try downloading it from the project
website -
> but
> > > does not mention where that site is.
> > >
> > > Kind regards,
> > > Dave Sag
> > >
> > >
> > >
> > >
> > >
>
>
>
> This e-mail, any attachments and the information contained therein
> ("this message") are confidential and intended solely for
the use of
> the addressee(s). If you have received this message in error please
> send it back to the sender and delete it. Unauthorized publication,
> use, dissemination or disclosure of this message, either in whole
or
> in part is strictly prohibited.
> --
> Ce message électronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci après "le message"
),
> sont confidentiels et destinés exclusivement à l'usage de la
> personne à laquelle ils sont adressés. Si vous avez reçu ce message
> par erreur, merci de le renvoyer à son émetteur et de le détruire.
> Toutes diffusion, publication, totale ou partielle ou divulgation
> sous quelque forme que se soit non expressément autorisées de ce
> message, sont interdites.
> -
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: default skin - where do i get it?
Hi Brett I added that to the pluginRepositories section of my settings.xml (it was already in the repositories section) and while i can see it trying to look for stuff in there, i still get the same problem. fixing the site plugin to 2.0-beta-4 fixed my problem for now though Kind regards, Dave Sag "Brett Porter" <[EMAIL PROTECTED]> wrote on 24-02-2006 13:38:16: > You'll need to use this repository until the site skins and site plugin are > released: > > > http://cvs.apache.org/maven-snapshot-repository/ > > > Or, you can lock your site plugin to version 2.0-beta-4 (the current > release). > > - Brett > > On 2/24/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > I had to rebuild maven from the source files in svn as the cobertura > > plugin is now demanding version 2.0.3 to run. > > > > but now the site plugin is complaining that it can't find the skin > > org.apache.maven.skins:maven-default-skin:jar:RELEASE > > > > so where do I find that - please don't say I have to build it from source > > as I am at work now where I can't access your svn repo. > > > > the mvn output says to try downloading it from the project website - but > > does not mention where that site is. > > > > Kind regards, > > Dave Sag > > > > > > > > > >
default skin - where do i get it?
Hi, I had to rebuild maven from the source files in svn as the cobertura plugin is now demanding version 2.0.3 to run. but now the site plugin is complaining that it can't find the skin org.apache.maven.skins:maven-default-skin:jar:RELEASE so where do I find that - please don't say I have to build it from source as I am at work now where I can't access your svn repo. the mvn output says to try downloading it from the project website - but does not mention where that site is. Kind regards, Dave Sag
jpox enhancing
I want to use JPOX there is a maven-jpox-plugin in repo1.maven.org/maven2/maven-plugins/ but when i add a reference to it in my pom.xml i get a FATAL ERROR "null" doing a mvn clean. is anyone out there using JPOX and Maven 2? Downloading: http://snapshots.maven.codehaus.org/maven2/maven-plugins/maven-jpox-plugin/1.0.0/maven-jpox-plugin-1.0.0.pom [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://repo1.maven.org/maven2/maven-plugins/maven-jpox-plugin/1.0.0/maven-jpox-plugin-1.0.0.pom 164b downloaded Downloading: http://snapshots.maven.codehaus.org/maven2/maven-plugins/maven-jpox-plugin/1.0.0/maven-jpox-plugin-1.0.0.jar [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://repo1.maven.org/maven2/maven-plugins/maven-jpox-plugin/1.0.0/maven-jpox-plugin-1.0.0.jar 4K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:982) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:254) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) 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) Kind regards, Dave Sag
Re: tests are running 3 times when i generate my site
Hi Brett, I am well looking forward to that release. Once 2.0.3 is out and Cobertura is out I hope I can turn off snapshots for a while as official policy here won't allow their use (understandably). Kind regards, Dave Sag "Brett Porter" <[EMAIL PROTECTED]> wrote on 22-02-2006 23:10:03: > On 2/22/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > unfortunately cobertura is not working again as it now demands > maven 2.0.3to run and breaks my builds. > > > Sorry, that was the only way to resolve the issue. > > i was at home last night so had access to svn, checked out the latest maven2 > > from the trunk and built it and cobertura ran runs ok now when i go mvn site > > I am now again getting the "the skin does not exist" error i had the other > > day (but fixed by setting up the snapshot stuff in my setting.xml). > > > I think the skins are stable. I will release them. > > when i have something that works reliably, and still keeps working reliably > > the following day, i'll happily put together a canonical example > pom.xmlfor you. so far that's a pipe dream for me however. using > maven 2 is a bit > > like arm wrestling the blob. > > > > Sorry, but this is sometimes an unavoidable result of using nightly builds. > There's a reason why they haven't been released yet :) > > It seems like cobertura is pretty close now. I'll try and get it released > after the Maven 2.0.3 release is finalised. > > - Brett
Re: tests are running 3 times when i generate my site
unfortunately cobertura is not working again as it now demands maven 2.0.3 to run and breaks my builds. i was at home last night so had access to svn, checked out the latest maven2 from the trunk and built it and cobertura ran runs ok now when i go mvn site I am now again getting the "the skin does not exist" error i had the other day (but fixed by setting up the snapshot stuff in my setting.xml). this is rather frustrating i must say. when i have something that works reliably, and still keeps working reliably the following day, i'll happily put together a canonical example pom.xml for you. so far that's a pipe dream for me however. using maven 2 is a bit like arm wrestling the blob. Kind regards, Dave Sag "Brett Porter" <[EMAIL PROTECTED]> wrote on 21-02-2006 17:15:09: > I previously sent a link to the repository manager. I use: > > > > > org.codehaus.mojo > cobertura-maven-plugin > > > org.codehaus.mojo > changelog-maven-plugin > > > org.codehaus.mojo > taglist-maven-plugin > > > org.codehaus.mojo > jxr-maven-plugin > > > org.codehaus.mojo > surefire-report-maven-plugin > > > maven-javadoc-plugin > > > maven-pmd-plugin > > > > > On 2/22/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > Since we're on the subject of cobertura, could I ask one of you guys > > to perhaps post your pom to the list? I had trouble getting cobertura > > to run, must be doing something wrong. ;-) > > > > Especially interested in David's because I'm already running PMD & > > Findbugs reports... Once I get cobertura working, then I'm happy to > > assist as best I can in looking into why its running tests 3 times > > etc. ;-) > > > > Wayne > > > > > > On 2/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > I'm now seeing the tests run twice under cobertura (once > silently, which is > > > a bit sneaky :) This is standalone, so that could be the reason for the > > > corruption you get if it conflicts with the other run. > > > > > > As for cobertura and surefire report running tests again as part of the > > > site, even after install - yes, that always happens. It's a > known issue that > > > requires some optimizations in the Maven lifecycle. > > > > > > Plugins really don't interact directly. Everything is driven via the > > > lifecycle bindings, with the project object holding any information that > > > might change. > > > > > > - Brett > > > > > > On 2/22/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > For some reason as of today the unit tests in one of my projects are now > > > > running 3 times when i do mvn install site. > > > > > > > > I declare the surefire plugin in my build as per normal and in my > > > > reporting as per normal so am not sure why this could be. > > > > > > > > I also generate pmd, cobertura, findbugs and qalab reports - > all that has > > > > changed is i now have cobertura working. could the cobertura reporting > > > > plugin be running the tests again separately to surefire? > > > > > > > > When the surefire report runs (this only runs once) i am now getting a > > > > 'failure to parse file at [[snipped]]/surefire-reports/TEST- > > > > org.epoFopTransformerTest.xml and sure enough when i look > at that file > > > > it ends unexpectedly at
tests are running 3 times when i generate my site
For some reason as of today the unit tests in one of my projects are now running 3 times when i do mvn install site. I declare the surefire plugin in my build as per normal and in my reporting as per normal so am not sure why this could be. I also generate pmd, cobertura, findbugs and qalab reports - all that has changed is i now have cobertura working. could the cobertura reporting plugin be running the tests again separately to surefire? When the surefire report runs (this only runs once) i am now getting a 'failure to parse file at [[snipped]]/surefire-reports/TEST-org.epoFopTransformerTest.xml and sure enough when i look at that file it ends unexpectedly at but if i mvn clean then mvn install, the tests run once and the xml file is okay. if i then as a separate task run mvn site the tests still appear to run 3 times but the xml file remains uncorrupted. so my questions. 1) why does surefire run the tests more than once. surely the report should just take the results of the run from the build phase. 2) why does it make a difference if i run mvn clean install site vs mvn clean; mvn install; mvn site as three separate commands 3) is the interaction between the various common plugins documented anywhere? for example cobertura is smart enough to tell surefire to run the tests against the instrumented classes behind the scenes, but this is not documented anywhere that I have seen. what other side effects might it have? Kind regards, Dave Sag
RE: cobertura plugin
You are so right. Removing the extra
configuration solved all of my cobertura problems.
Kind regards,
Dave Sag
"Mike Perham" <[EMAIL PROTECTED]>
wrote on 20-02-2006 15:44:17:
> David, you are way overcomplicating the cobertura setup. Remove
your
> executions and the surefire config. There's no need - all this
is
> handled internally when the plugin executes with 'cobertura:cobertura'.
>
> _
>
> From: David Sag [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 20, 2006 7:20 AM
> To: Maven Users List
> Subject: Re: cobertura plugin
>
>
>
> Interesting
>
> the main difference between the way you do it and the way I am doing
is
> that I specify the goal and execution phase in my build declarations
> thusly:
>
>
> org.codehaus.mojo
> cobertura-maven-plugin
> 2.0-SNAPSHOT
>
>
> instrument-classes
> process-classes
>
> instrument
>
>
>
>
>
> could this be causing my problem? i doubt it.
>
> Also I explicitly tell surefire where the instrumented classes are:
>
>
>
> maven-surefire-plugin
> 2.0
>
>
> ${project.build.directory}/classes-instrumented
> esDirectory>
>
>
>
> otherwise we are doing pretty much the same thing.
>
> I can't see in your pom.xml how your tests know to run the instrumented
> classes, nor is it obvious in what phase you are instrumenting your
> classes. what sort of coverage reports are you getting?
>
> Kind regards,
> Dave Sag
>
>
>
>
>
>
> "javed mandary" <[EMAIL PROTECTED]> wrote on 20-02-2006
13:57:41:
>
> > Am running maven site with cobertura report generation:
> >
> >
> >
> > [.]
> >
> >
> >
> > src/main/resources
> >
> >
*.xls
> >
**/*.xml
> >
*.properties
> >
> >
> >
> >
> >
> >
org.codehaus.mojo
> >
> surefire-report-maven-plugin
> >
2.0-beta-1
> >
> >
true
> >
> >
> >
> >
org.codehaus.mojo
> >
> cobertura-maven-plugin
> >
2.0-SNAPSHOT
> >
> >
> >
> >
> >
> >
> >
org.codehaus.mojo
> >
> surefire-report-maven-plugin
> >
2.0-beta-1
> >
> >
> >
org.codehaus.mojo
> >
cobertura-maven-plugin
> >
2.0-SNAPSHOT
> >
> >
> >
> >
> >
> >
> > asm
> > asm
> > 1.5.3
> >
> >
> > org.springframework
> > spring-mock
> > 1.2.6
> > test
> >
> >
> >
jta
> >
javax.transaction
> >
> >
> >
jdbc-stdext
> >
javax.sql
> >
> >
> >
jsf-api
> >
javax.faces
> >
> >
> >
> >
> > org.springframework
> > spring-remoting
> > 1.2.6
> >
> >
> > org.springframework
> > spring-core
> > 1.2.6
> >
> >
> > axis
> > axis
> > 1.2.1
> >
> >
> >
activation
> >
javax.activation
> >
> >
> >
mail
> >
javax.mail
> >
> >
> >
> >
> > axis
> > axis-jaxrpc
> > 1.2.1
> >
Re: cobertura plugin
Interesting
the main difference between the way
you do it and the way I am doing is that I specify the goal and execution
phase in my build declarations thusly:
org.codehaus.mojo
cobertura-maven-plugin
2.0-SNAPSHOT
instrument-classes
process-classes
instrument
could this be causing my problem? i
doubt it.
Also I explicitly tell surefire where
the instrumented classes are:
maven-surefire-plugin
2.0
${project.build.directory}/classes-instrumented
otherwise we are doing pretty much
the same thing.
I can't see in your pom.xml how your
tests know to run the instrumented classes, nor is it obvious in what phase
you are instrumenting your classes. what sort of coverage reports
are you getting?
Kind regards,
Dave Sag
"javed mandary" <[EMAIL PROTECTED]>
wrote on 20-02-2006 13:57:41:
> Am running maven site with cobertura report generation:
>
>
>
> [.]
>
>
>
> src/main/resources
>
> *.xls
> **/*.xml
> *.properties
>
>
>
>
>
>
org.codehaus.mojo
>
surefire-report-maven-plugin
>
2.0-beta-1
>
>
true
>
>
>
>
org.codehaus.mojo
>
cobertura-maven-plugin
>
2.0-SNAPSHOT
>
>
>
>
>
>
> org.codehaus.mojo
> surefire-report-maven-plugin
> 2.0-beta-1
>
>
>
org.codehaus.mojo
>
cobertura-maven-plugin
>
2.0-SNAPSHOT
>
>
>
>
>
>
> asm
> asm
> 1.5.3
>
>
> org.springframework
> spring-mock
> 1.2.6
> test
>
>
>
jta
>
javax.transaction
>
>
>
jdbc-stdext
>
javax.sql
>
>
>
jsf-api
>
javax.faces
>
>
>
>
> org.springframework
> spring-remoting
> 1.2.6
>
>
> org.springframework
> spring-core
> 1.2.6
>
>
> axis
> axis
> 1.2.1
>
>
>
activation
>
javax.activation
>
>
>
mail
>
javax.mail
>
>
>
>
> axis
> axis-jaxrpc
> 1.2.1
>
>
> axis
> axis-saaj
> 1.2.1
>
>
>
>
>
> On 2/20/06, David Sag <[EMAIL PROTECTED]> wrote:
> >
> >
> > I guess we are having different problems. In a reply to
my Jira issue
> > Carlos Sanchez points out that my problem lies in the fact that
cobertura is
> > trying to instrument the classes twice. I am not sure why
this is
> > happening, nor am i sure why this is even a problem, but clearly
you are not
> > getting this problem.
> >
> > could you show me your pom.xml so i can look for any obvious
differences
> > between what you are doing and what I am doing.
> >
> > Kind regards,
> > Dave Sag
> >
> >
> >
> >
> >
> >
> > "Brett Porter" <[EMAIL PROTECTED]> wrote
on 20-02-2006 09:05:19:
> >
> > > this problem was fixed in SVN (asm is no longer propogated
to tests
> > > themselves)
> > >
> > > On 2/20/06, javed mandary <[EMAIL PROTECTED]> wrote:
> > > > Hi David,
> > > > I solved
the problem with the Cobertura plugin running
> > > > hibernate junit tests by adding the following dependency
in my POM:
> > > >
> > > >
Re: cobertura plugin
I guess we are having different problems. In a reply to my Jira issue Carlos Sanchez points out that my problem lies in the fact that cobertura is trying to instrument the classes twice. I am not sure why this is happening, nor am i sure why this is even a problem, but clearly you are not getting this problem. could you show me your pom.xml so i can look for any obvious differences between what you are doing and what I am doing. Kind regards, Dave Sag "Brett Porter" <[EMAIL PROTECTED]> wrote on 20-02-2006 09:05:19: > this problem was fixed in SVN (asm is no longer propogated to tests > themselves) > > On 2/20/06, javed mandary <[EMAIL PROTECTED]> wrote: > > Hi David, > > I solved the problem with the Cobertura plugin running > > hibernate junit tests by adding the following dependency in my POM: > > > > > > asm > > asm > > 1.5.3 > > > > > > > > It seems that Cobertura is looking for asm-2.1 in its POM while hibernate > > requires asm-1.5.3. > > > > By setting the dependency asm-1.5.3 , this is placed in classpath and > > everything works fine , cobertura site report is generated successfully. > > > > regards, > > Javed > > > > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > Maven 2 is what I am on about. see the jira issue, but i am getting the > > > same problem as you describe. perhaps you'd like to vote on > that issue and > > > add your comments there. > > > > > > Kind regards, > > > Dave Sag > > > > > > > > > > > > > > > > > > > > > "javed mandary" <[EMAIL PROTECTED]> wrote on 17-02-2006 14:14:17: > > > > > > > ok , what about the cobertura plugin for maven 2 ? In maven site I am > > > > getting a problem after cobertura runs the junit tests and tryto create > > > a > > > > report it crashes and fails the build. > > > > > > > > Has anyone got similar problems and any solutions to that? > > > > > > > > this is what i am using: > > > > > > > > org.codehaus.mojo > > > > cobertura-maven-plugin > > > > 2.0-SNAPSHOT > > > > > > > > > > > > > > > > clean > > > > > > > > > > > > > > > > > > > > > > > > regards, > > > > Javed > > > > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Hi Brett > > > > > > > > > > I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and > > > > > included an example project that displays the bug. > > > > > > > > > > if you could put your repo manager code somewhere in a zip file I can > > > try > > > > > it out here and see if I get the same problems. > > > > > > > > > > Kind regards, > > > > > Dave Sag > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:33:08: > > > > > > > > > > > Hi David, > > > > > > > > > > > > There might be a release coming up, but we haven't worked on your > > > issue > > > > > and > > > > > > there are still some other issues outstanding that should be fixed > > > > > first. > > > > > > > > > > > > If you could confirm that cobertura fails for you on the repository > > > > > manager > > > > > > app (if SVN is a problem I can upload it somewhere), that would > > > isolate > > > > > it > > > > > > to you environment over your particular project. > > > > > > > > > > > > Thanks, > > > > > > Brett > > > > > > > > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > Sorry br
Re: cobertura plugin
Maven 2 is what I am on about. see the jira issue, but i am getting the same problem as you describe. perhaps you'd like to vote on that issue and add your comments there. Kind regards, Dave Sag "javed mandary" <[EMAIL PROTECTED]> wrote on 17-02-2006 14:14:17: > ok , what about the cobertura plugin for maven 2 ? In maven site I am > getting a problem after cobertura runs the junit tests and try to create a > report it crashes and fails the build. > > Has anyone got similar problems and any solutions to that? > > this is what i am using: > > org.codehaus.mojo > cobertura-maven-plugin > 2.0-SNAPSHOT > > > > clean > > > > > > regards, > Javed > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Hi Brett > > > > I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and > > included an example project that displays the bug. > > > > if you could put your repo manager code somewhere in a zip file I can try > > it out here and see if I get the same problems. > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:33:08: > > > > > Hi David, > > > > > > There might be a release coming up, but we haven't worked on your issue > > and > > > there are still some other issues outstanding that should be fixed > > first. > > > > > > If you could confirm that cobertura fails for you on the repository > > manager > > > app (if SVN is a problem I can upload it somewhere), that would isolate > > it > > > to you environment over your particular project. > > > > > > Thanks, > > > Brett > > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Sorry brett the last i heard from you was that you were working on the > > > > problem and there would be a release late this week. > > > > > > > > So I have been working on other things and waiting paitiently. > > > > > > > > But if you are now telling me I need to file a jira issue then that's > > what > > > > i'll do. > > > > > > > > I'll have to put together a minimal project and reproduce the problem > > in > > > > some code that is not the EPOs tho. This probably won't happen today. > > > > > > > > Kind regards, > > > > Dave Sag > > > > > > > > > > > > > > > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:20:42: > > > > > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > Sorry are you talking about maven 1 or 2 plugin? > > > > > > > > > > > > > > > They are talking about Maven 1.0 > > > > > > > > > > I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since > > > > > > updating to maven 2.0.2 the reporting part of cobertura hasn't > > worked. > > > > > > > > > > > > > > > I can't reproduce it. If it never gets filed in JIRA, it'll never > > get > > > > > fixed... can you please do that at > > http://jira.codehaus.org/browse/MOJO? > > > > > > > > > > Did you try the repository manager example I showed you last time > > that > > > > is > > > > > working for me? > > > > > > > > > > - Brett > > > > > >
Re: cobertura plugin
Hi Brett I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and included an example project that displays the bug. if you could put your repo manager code somewhere in a zip file I can try it out here and see if I get the same problems. Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:33:08: > Hi David, > > There might be a release coming up, but we haven't worked on your issue and > there are still some other issues outstanding that should be fixed first. > > If you could confirm that cobertura fails for you on the repository manager > app (if SVN is a problem I can upload it somewhere), that would isolate it > to you environment over your particular project. > > Thanks, > Brett > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Sorry brett the last i heard from you was that you were working on the > > problem and there would be a release late this week. > > > > So I have been working on other things and waiting paitiently. > > > > But if you are now telling me I need to file a jira issue then that's what > > i'll do. > > > > I'll have to put together a minimal project and reproduce the problem in > > some code that is not the EPOs tho. This probably won't happen today. > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:20:42: > > > > > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Sorry are you talking about maven 1 or 2 plugin? > > > > > > > > > They are talking about Maven 1.0 > > > > > > I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since > > > > updating to maven 2.0.2 the reporting part of cobertura hasn't worked. > > > > > > > > > I can't reproduce it. If it never gets filed in JIRA, it'll never get > > > fixed... can you please do that at http://jira.codehaus.org/browse/MOJO? > > > > > > Did you try the repository manager example I showed you last time that > > is > > > working for me? > > > > > > - Brett > >
Re: cobertura plugin
Sorry brett the last i heard from you was that you were working on the problem and there would be a release late this week. So I have been working on other things and waiting paitiently. But if you are now telling me I need to file a jira issue then that's what i'll do. I'll have to put together a minimal project and reproduce the problem in some code that is not the EPOs tho. This probably won't happen today. Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 17-02-2006 13:20:42: > On 2/17/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Sorry are you talking about maven 1 or 2 plugin? > > > They are talking about Maven 1.0 > > I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since > > updating to maven 2.0.2 the reporting part of cobertura hasn't worked. > > > I can't reproduce it. If it never gets filed in JIRA, it'll never get > fixed... can you please do that at http://jira.codehaus.org/browse/MOJO? > > Did you try the repository manager example I showed you last time that is > working for me? > > - Brett
Re: cobertura plugin
Sorry are you talking about maven 1 or 2 plugin? I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since updating to maven 2.0.2 the reporting part of cobertura hasn't worked. Kind regards, Dave Sag Nicolas De Loof <[EMAIL PROTECTED]> wrote on 17-02-2006 11:12:27: > > 1.2-SNAPSHOT works fine for me. > > Thanks ! > > Nicolas De Loof a écrit : > > I'm using maven-cobertura-plugin from [EMAIL PROTECTED] > > As this site uses CVS, this seems you've in mind another cobertura > > plugin. Where to find it ? > > > > Mike Perham a écrit : > > > >> The plugin code in SVN already uses 1.7. It's never been released so > >> you must be using an old version you compiled. Update svn and recompile > >> it. > >> > >> -Original Message- > >> From: Nicolas De Loof [mailto:[EMAIL PROTECTED] Sent: > >> Thursday, February 16, 2006 8:36 AM > >> To: Maven Users List > >> Subject: cobertura plugin > >> > >> > >> Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ? > >> > >> I'm using AspectJ and JiBX that both operate on bytecode and are not > >> compatible with cobertura 1.6 instrumentation (plugin fails) > >> > >> Upgrading dependency to 1.7 solves this problem > >> > >> I've created > >> http://sourceforge.net/tracker/index.php?func=detail&aid=1432911&group_i > >> d=61626&atid=497853 > >> for this. > >> > >> Nico. > >> > >> This message contains information that may be privileged or confidential > >> and is the property of the Capgemini Group. It is intended only for the > >> person to whom it is addressed. If you are not the intended recipient, > >> you are not authorized to read, print, retain, copy, disseminate, > >> distribute, or use this message or any part thereof. If you receive this > >> message in error, please notify the sender immediately and delete all > >> copies of this message. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > > > > This message contains information that may be privileged or > confidential and is the property of the Capgemini Group. It is > intended only for the person to whom it is addressed. If you are not > the intended recipient, you are not authorized to read, print, > retain, copy, disseminate, distribute, or use this message or any > part thereof. If you receive this message in error, please notify > the sender immediately and delete all copies of this message. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: cobertura plugin
Please - that would be nice. Kind regards, Dave Sag Arnaud HERITIER <[EMAIL PROTECTED]> wrote on 16-02-2006 16:24:10: > Isn't it possible to release it ? > > Arnaud > > On 2/16/06, Mike Perham <[EMAIL PROTECTED]> wrote: > > The plugin code in SVN already uses 1.7. It's never been released so > > you must be using an old version you compiled. Update svn and recompile > > it. > > > > -Original Message- > > From: Nicolas De Loof [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 16, 2006 8:36 AM > > To: Maven Users List > > Subject: cobertura plugin > > > > > > Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ? > > > > I'm using AspectJ and JiBX that both operate on bytecode and are not > > compatible with cobertura 1.6 instrumentation (plugin fails) > > > > Upgrading dependency to 1.7 solves this problem > > > > I've created > > http://sourceforge.net/tracker/index.php?func=detail&aid=1432911&group_i > > d=61626&atid=497853 > > for this. > > > > Nico. > > > > This message contains information that may be privileged or confidential > > and is the property of the Capgemini Group. It is intended only for the > > person to whom it is addressed. If you are not the intended recipient, > > you are not authorized to read, print, retain, copy, disseminate, > > distribute, or use this message or any part thereof. If you receive this > > message in error, please notify the sender immediately and delete all > > copies of this message. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m202] site:site exepction
I get a similar error with one of my projects. javadoc just seems to fall over due to the huge amount of javadoc errors (not my code, legacy stuff) - so for now i am just omitting the javadoc report until i get a chance to clean up that code. it looks like you are getting similar probs despite far fewer javadoc errors. spooky. Kind regards, Dave Sag "Mick Knutson" <[EMAIL PROTECTED]> wrote on 10-02-2006 20:11:28: > I just upgraded to 2.0.2 and got the latests surefire report plugin from svn > and I get this when running site:site: > > === > > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error during report > generation > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoals(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeStandaloneGoal(DefaultLifecycleExecutor.java:485) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoal(DefaultLifecycleExecutor.java:455) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl. > invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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 during > report generation > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389) > at > org.apache.maven.plugin.DefaultPluginManager. > executeMojo(DefaultPluginManager.java:415) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoals(DefaultLifecycleExecutor.java:531) > ... 16 more > Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - > javadoc: Error reading file: C:/opt/furlm2/core/trunk/../ppw-project-settin > gs/packagelists/ppw-bean-I/package-list > javadoc: Error reading file: > C:/opt/furlm2/core/trunk/../ppw-project-settings/packagelists/ppw- > bean-II/package-list > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:323: > warning - @return tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:467: > warning - @return tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/storage/StoreEntry.java:23: > warning - @version tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/daos/CategoryDAO.java:55: > warning - @return tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/daos/CategoryDAO.java:80: > warning - @return tag has no arguments. > C: > /opt/furlm2/core/trunk/src/main/java/com/visionstudio/web/common/Database. > java:206: > warning - @return tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemsBean.java:78: > warning - @return tag has no arguments. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:59: > warning - @param argument "count" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:82: > warning - @param argument "userIds" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:82: > warning - @param argument "categories" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:82: > warning - @param argument "exludeUrl" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:103: > warning - @param argument "maxItem" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:167: > warning - @param argument "forUserId" is not a parameter name. > C:/opt/furlm2/core/trunk/src/main/java/com/furl/beans/ItemUtilBean.java:323: > warning - @param argument "maxItems" is
Re: [m2] Surefire-Plugin ignores argLine
Hi Jim, to get this to work I have set up an environment variable MAVEN_OPTS=-ea in my .profile (I am on MacOSX - do whatever you need to do to set up env variables on your platform) it's less than ideal but for now I have been told this is the only way. Kind regards, Dave Sag "Jim Babka" <[EMAIL PROTECTED]> wrote on 06-02-2006 18:54:03: > I am trying to run tests with assertions enabled, but the surefire > plugin is apparently ignoring the argLine parameter. If I specify the > following, assertions are not turned on: > > ... > > ... > > > org.apache.maven.plugins > maven-surefire-plugin > > **/*TestSuite* > false > once > -ea > > > ... > > > ... > > By the way, I did try this with -enableassertions as well (which is what > is shown in the surefire example doc), and it made no difference. > > As a further example, this produces no error at all, even though it > clearly should, so this argLine parameter is really being ignored: > > > org.apache.maven.plugins > maven-surefire-plugin > > **/*TestSuite* > false > once > -xxx > > > > What is the right way to get surefire to run tests with assertions on? > > Jim Babka > Senior Software Engineer > Main: (512) 334 3200 > Direct: (512) 334 3237 > Email: [EMAIL PROTECTED] > > Webify Solutions > Enabling the On Demand Enterprise(tm) > www.webifysolutions.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: AW: Integrating Junit Testreport into the maven site
Hi Karsten,
As well as declaring it in the build
section of your pom you also need to add it to the reporting.
In your reporting section of your pom.xml
add the following:
org.codehouse.mojo
surefire-report-maven-plugin
and that will generate the surefire
report for your maven2 generated site.
Kind regards,
Dave Sag
"Pleines, Karsten (I B 3)" <[EMAIL PROTECTED]>
wrote on 06-02-2006 07:52:12:
> Hi,
> Thank you for the answer. I think you missunderstood my question or
> I forulated them erroneous.
> Now I have the Junit reports inside the "target\surefire-reports"
as
> Text and XML Files but I don't know how to include them into the
> maven generated website? I want to deploy the site for a better
> controle of my project.
> Can you help me to solve this problem?
>
> Tank you for your help
> Karsten
>
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 3. Februar 2006 15:07
> An: Maven Users List
> Betreff: Re: Integrating Junit Testreport into the maven site
>
>
> Pleines, Karsten (I B 3) wrote:
>
> >Hi,
> >I've started to generate a maven site and it succeeds. The problem
is,
> >I don't know how to integrate the Junit report into the site.
Can
> >somebody help me?
> >
> >Thank you
> >Karsten
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> if you get a numberformatexception build version 2.0-beta-2 from the
> sources in subversion codehaus
>
>
> all config settings are the defaults
> except true
because if you
> do not set this to true, you well never see failed tests in the site
> report because you wont have a site (junit failure makes site generation
stop)
>
>
> ...
>
>
>
>
> org.codehaus.mojo
> surefire-report-maven-plugin
>
>
> ${basedir}
>
>
> ${project.build.outputDirectory}
>
>
>
>
>
>
>
> ${localRepository}
>
>
>
> ${plugin.artifacts}
>
>
> true
>
> brief
>
>
> ${project.build.directory}/surefire-reports
>
>
> ${maven.test.skip}
>
>
>
> ${test}
>
>
> ${project.build.testOutputDirectory}
>
>
> true
>
> true
>
>
>
>
>
>
> --
>
>
> met vriendelijke groeten
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: [m202] Cobertura plugin
Brett Porter <[EMAIL PROTECTED]> wrote on 04-02-2006 03:29:43: > It's the first one in the section on the link you gave. Unless > I'm clearly mistaken :) > well it is now, so maybe i just missed it the last time i looked. if so i apologise. > The cobertura plugin will be worked on to completion in the next two weeks. > We're working through the issues at the mojo project. fantastic news. do you have a link to a JIRA issue i could track? > - Brett > > On 2/4/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > As far as I can tell the latest snapshot version (2.0) still does not work > > properly. it will instrument okay but when generating the a site with > > cobertura as a report it generates 0 byte class files and the surefire tests > > break. > > > > brett porter claims it does work and offered up > > https://svn.apache.org/repos/asf/maven/repository-manager/trunk as an > > example of it in use, but a quick look over > > https://svn.apache.org/repos/asf/maven/repository-manager/trunk/pom.xmlshows > that there is no mention of cobertura there, so brett is clearly > > mistaken. > > > > I am still hopefull that this could be fixed so have commented out the > > cobertura stuff for now and am persevering with maven 2. > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Konstantin Polyzois <[EMAIL PROTECTED]> wrote on 03-02-2006 08:03:52: > > > > > I checked it out ant built it myself did not find a working release of > > it. > > > > > > /Konstantin > > > > > > 2006/2/1, Arnaud Bailly <[EMAIL PROTECTED]>: > > > > Hello, > > > > What is the status of the cobertura plugin for m2 ? I had problems > > > > trying to include it in the pom through central and there > > > > was some discussion on the list some days ago, but I didn't find > > > > how to get the latest and greatest version. > > > > > > > > Thanks, > > > > > > > > -- > > > > Arnaud Bailly, Dr. - Ingénieur de Recherche > > > > NORSYS > > > > 1, rue de la Cense des Raines > > > > ZAC du Moulin > > > > 59710 ENNEVELIN > > > > Tel : (33) 3 28 76 56 76 > > > > Mob : (33) 6 17 12 19 78 > > > > Fax : (33) 3 28 76 57 00 > > > > Web : http://www.norsys.fr > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: Using cobertura with Maven 2
The only solution i know right now is not to include cobertura repoorts and hope whoever is working on the plugin fixes whatever it is they did to break it between maven 2.0 and 2.0.2 I had a big presentation on maven today and was luckily able to skirt around the cobertura issue with some quick sleight of hand. so i have bought myself a week i think. Kind regards, Dave Sag Rik Bosman <[EMAIL PROTECTED]> wrote on 03-02-2006 16:33:39: > David, > > I do run into (the same you had I think ) > net.sourceforge.cobertura.instrument.Main - Unable to instrument file. > Do you know a solution? > > I'm using mvn 2.02. > > regards, > > Rik > > > 2006/2/3, David Sag <[EMAIL PROTECTED]>: > > > > > > Hi Rik, > > > > So you have actually been able to get the 2.0-SNAPSHOT to work? I'd love > > to see how. I have been trying all week to get the cobertura reports to work > > but since iupping to maven 2.0.2 have not been successful due to the > > problem of it generating 0 byte instrumented class files during the > > reporting phase that overwrite the originally instrumented class files. > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Rik Bosman <[EMAIL PROTECTED]> wrote on 03-02-2006 10:29:45: > > > > > Jared, > > > > > > I had the same problem and solved it with the following actions: > > > > > > - Add the version to both the plugins: 2.0-SNAPSHOT > > > - Add the sandbox repository to the pom, see below. > > > > > > Hope this helps, > > > > > > Kindly revert for clarifications, > > > > > > Rik > > > > > > > > > > > > Maven Snapshots > > > http://snapshots.maven.codehaus.org/maven2/ > > > > > > true > > > > > > > > > false > > > > > > > > > > > > > > > > > > Maven Snapshots > > > http://snapshots.maven.codehaus.org/maven2/ > > > > > > true > > > > > > > > > false > > > > > > > > > > > > > > > > > > > > > 2006/2/3, javed mandary <[EMAIL PROTECTED]>: > > > > > > > > Hi Guys, > > > > i'd like to know some information about the cobertura > > plugin > > > > in > > > > general: > > > > > > > > 1. On which repo is the cobertura-maven-plugin hosted ? > > > > 2. How to configure it in your POM ? > > > > > > > > I tried the following 2 configurations in my POM: > > > > ---EXTRACT OF MY POM > > > > -- > > > > > > > > > > > > > > > > > > > > org.codehaus.mojo > > > > cobertura-maven-plugin > > > > > > > > > > > > > > > > clean > > > > > > > > > > > > > > > > > > > > > > > > > > > > ... > > > > > > > > > > > > > > > > org.codehaus.mojo > > > > cobertura-maven-plugin > > > > > > > > > > > > > > > > > > > > > > > > - > > > END- > > > > > > > > I get the following error: > > > > > > > > --- > > > > [ERROR] BUILD ERROR > > > > [INFO] > > > > > > - > > > > --- > > > > [INFO] The plugin 'org.codehaus.mojo:cobertura-maven-plugin' does not > > > > exist > > > > or n > > > > o valid version could be found > > > > [INFO] > > > > > > - > > > > --- > > > > [INFO] For more information, run Maven with the -e switch > > > > [INFO] > > > > > > - > > > > --- > > > > [INFO] Total time: 1 second > > > > [INFO] Finished at: Fri Feb 03 11:34:19 GST 2006 > > > > [INFO] Final Memory: 2M/4M > > > > [INFO] -- > > > > --- > > > > > > > > Is there any other configurations that is required ? I am using Maven > > > > 2.0.2. > > > > > > > > kind regards, > > > > Javed > > > > > > > > > >
Re: [m2.0.2] the skin does not exist: unable to determine the release version.
Hi Arik your suggestion, in combination with emanuelle's suggestion fixed the problem (for today at least). I only enabled snapshots as part of a general attempt to get cobertura working. since that is pretty mucha lost cause for now, tell me, if i disable snapshots, will the presence of the tags in my site.xml break anything? Kind regards, Dave Sag Arik Kfir <[EMAIL PROTECTED]> wrote on 03-02-2006 14:31:15: > Hi David, > > You should remember that although Maven itself was released, some of > the plugins (e.g. the site plugin) have not been released yet. You are > currently using either a SNAPSHOT, or one of the BETA releases - all > of which are subject to change as they are still being written and > implemented. > > As for your problem - if the above solution does not work, try adding > this (in addition to what Emmanuel specified above) to your site.xml > file: > > > org.apache.maven.skins > maven-stylus-skin > 1.0-SNAPSHOT > > > Best regards (and good luck :P) > Arik. > > > On 2/3/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > You use the snapshot version of site plugin, right? > > > > Add this in your pom : > > > > > > > > false > > > > apache.snapshots > > Apache Development Repository > > http://cvs.apache.org/maven-snapshot-repository > > > > > > > > Emmanuel > > > > David Sag a écrit : > > > > > > Today I got a new error when building the site for my project. > > > > > > the skin does not exist: unable to determine the release version. > > > > > > WTF? I've never seen this error before. > > > > > > Is it just me, or does the new found brittle nature of builds scare > > > anyone else? It's truly scary to go home leaving a project that builds > > > fine, and come in in the morning to discover that now it doesn't. > > > > > > Kind regards, > > > Dave Sag > > > > > > > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Regards, > _ > Arik Kfir [EMAIL PROTECTED]
[m2.0.2] the skin does not exist: unable to determine the release version.
Today I got a new error when building the site for my project. the skin does not exist: unable to determine the release version. WTF? I've never seen this error before. Is it just me, or does the new found brittle nature of builds scare anyone else? It's truly scary to go home leaving a project that builds fine, and come in in the morning to discover that now it doesn't. Kind regards, Dave Sag
Re: Using cobertura with Maven 2
Hi Rik, So you have actually been able to get the 2.0-SNAPSHOT to work? I'd love to see how. I have been trying all week to get the cobertura reports to work but since iupping to maven 2.0.2 have not been successful due to the problem of it generating 0 byte instrumented class files during the reporting phase that overwrite the originally instrumented class files. Kind regards, Dave Sag Rik Bosman <[EMAIL PROTECTED]> wrote on 03-02-2006 10:29:45: > Jared, > > I had the same problem and solved it with the following actions: > > - Add the version to both the plugins: 2.0-SNAPSHOT > - Add the sandbox repository to the pom, see below. > > Hope this helps, > > Kindly revert for clarifications, > > Rik > > > > Maven Snapshots > http://snapshots.maven.codehaus.org/maven2/ > > true > > > false > > > > > > Maven Snapshots > http://snapshots.maven.codehaus.org/maven2/ > > true > > > false > > > > > > > 2006/2/3, javed mandary <[EMAIL PROTECTED]>: > > > > Hi Guys, > > i'd like to know some information about the cobertura plugin > > in > > general: > > > > 1. On which repo is the cobertura-maven-plugin hosted ? > > 2. How to configure it in your POM ? > > > > I tried the following 2 configurations in my POM: > > ---EXTRACT OF MY POM > > -- > > > > > > > > > > org.codehaus.mojo > > cobertura-maven-plugin > > > > > > > > clean > > > > > > > > > > > > > > ... > > > > > > > > org.codehaus.mojo > > cobertura-maven-plugin > > > > > > > > > > > > - > END- > > > > I get the following error: > > > > --- > > [ERROR] BUILD ERROR > > [INFO] > > - > > --- > > [INFO] The plugin 'org.codehaus.mojo:cobertura-maven-plugin' does not > > exist > > or n > > o valid version could be found > > [INFO] > > - > > --- > > [INFO] For more information, run Maven with the -e switch > > [INFO] > > - > > --- > > [INFO] Total time: 1 second > > [INFO] Finished at: Fri Feb 03 11:34:19 GST 2006 > > [INFO] Final Memory: 2M/4M > > [INFO] -- > > --- > > > > Is there any other configurations that is required ? I am using Maven > > 2.0.2. > > > > kind regards, > > Javed > > > >
Re: Using cobertura with Maven 2
you will need to enable snapshots to get the cobertura plugin as it has not actually ever been released. then try org.codehaus.mojo cobertura-maven-plugin 2.0-SNAPSHOT process-classes instrument the 2.0 snapshot breaks in reporting however as it tries to instrument the classes again and this time it generates 0 byte class files. Kind regards, Dave Sag javed mandary <[EMAIL PROTECTED]> 03-02-2006 08:31 Please respond to "Maven Users List" To Maven Users List cc Subject Using cobertura with Maven 2 Hi Guys, i'd like to know some information about the cobertura plugin in general: 1. On which repo is the cobertura-maven-plugin hosted ? 2. How to configure it in your POM ? I tried the following 2 configurations in my POM: ---EXTRACT OF MY POM -- org.codehaus.mojo cobertura-maven-plugin clean ... org.codehaus.mojo cobertura-maven-plugin -END- I get the following error: --- [ERROR] BUILD ERROR [INFO] - --- [INFO] The plugin 'org.codehaus.mojo:cobertura-maven-plugin' does not exist or n o valid version could be found [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: 1 second [INFO] Finished at: Fri Feb 03 11:34:19 GST 2006 [INFO] Final Memory: 2M/4M [INFO] -- --- Is there any other configurations that is required ? I am using Maven 2.0.2. kind regards, Javed
Re: [m202] Cobertura plugin
As far as I can tell the latest snapshot version (2.0) still does not work properly. it will instrument okay but when generating the a site with cobertura as a report it generates 0 byte class files and the surefire tests break. brett porter claims it does work and offered up https://svn.apache.org/repos/asf/maven/repository-manager/trunk as an example of it in use, but a quick look over https://svn.apache.org/repos/asf/maven/repository-manager/trunk/pom.xml shows that there is no mention of cobertura there, so brett is clearly mistaken. I am still hopefull that this could be fixed so have commented out the cobertura stuff for now and am persevering with maven 2. Kind regards, Dave Sag Konstantin Polyzois <[EMAIL PROTECTED]> wrote on 03-02-2006 08:03:52: > I checked it out ant built it myself did not find a working release of it. > > /Konstantin > > 2006/2/1, Arnaud Bailly <[EMAIL PROTECTED]>: > > Hello, > > What is the status of the cobertura plugin for m2 ? I had problems > > trying to include it in the pom through central and there > > was some discussion on the list some days ago, but I didn't find > > how to get the latest and greatest version. > > > > Thanks, > > > > -- > > Arnaud Bailly, Dr. - Ingénieur de Recherche > > NORSYS > > 1, rue de la Cense des Raines > > ZAC du Moulin > > 59710 ENNEVELIN > > Tel : (33) 3 28 76 56 76 > > Mob : (33) 6 17 12 19 78 > > Fax : (33) 3 28 76 57 00 > > Web : http://www.norsys.fr > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: I can't get cobertura to work with maven 2.0.2
Thanks Carolos but if you'd followed
this thread you'd see that Brett has released the latest build as a snapshot,
and that's the version I am useing - 2.0-SNAPSHOT.
If you know of an even more recent version
please let me know. I have until friday to get this to work or it's
back to using ant for me.
Kind regards,
Dave Sag
[EMAIL PROTECTED] wrote on 31-01-2006 18:35:26:
> You need latest cobertura built from sources
>
>
> On 1/31/06, David Sag <[EMAIL PROTECTED]> wrote:
> >
> > Okay I have changed my build so that the checkstyle etc all happen
> on the verify phase, and have updated to use the latest snapshot
> version of cobertura plugin.
> >
> > [mvn install] works fine - all is as expected.
> >
> > but [mvn site] continues to break as follows:
> >
> > (disco-davesag) [15:59:16] ~/checkouts/EPO/cassius_service_Sis$
mvn site
> > [INFO] Scanning for projects...
> > [INFO]
>
> > [INFO] Building Search Information Service (redux)
> > [INFO] task-segment: [site]
> > [INFO]
>
> > [INFO] Preparing cobertura:cobertura
> > [INFO] [resources:resources]
> > [INFO] [compiler:compile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [cobertura:instrument {execution: instrument-classes}]
> > [INFO] Cobertura 1.7 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
file
> > Cobertura: Loaded information on 4 classes.
> > Instrumenting 6 classes to
> /Users/davesag/checkouts/EPO/cassius_service_Sis/target/generated-
> classes/cobertura
> > Cobertura: Saved information on 4 classes.
> > Instrument time: 244ms
> >
> > [INFO] Instrumentation was successful.
> > [INFO] [cobertura:instrument]
> > [INFO] Cobertura 1.7 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
file
> > Cobertura: Loaded information on 4 classes.
> > Instrumenting 6 classes to
> /Users/davesag/checkouts/EPO/cassius_service_Sis/target/generated-
> classes/cobertura
> > [cobertura] WARN [main] net.sourceforge.cobertura.instrument.Main
> - Unable to instrument file
> /Users/davesag/checkouts/EPO/cassius_service_Sis/target/generated-
> classes/cobertura/org/epo/cassius/csp/DossierTranslationService.class
> > java.lang.ArrayIndexOutOfBoundsException: 8
> > at org.objectweb.asm.ClassReader.readUnsignedShort(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentationToSingleClass(Main.java:286)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentation(Main.java:364)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentation(Main.java:382)
> > at net.sourceforge.cobertura.instrument.Main.
> parseArguments(Main.java:440)
> > at net.sourceforge.cobertura.instrument.Main.main(Main.java:462)
> > [cobertura] WARN [main] net.sourceforge.cobertura.instrument.Main
> - Unable to instrument file
> /Users/davesag/checkouts/EPO/cassius_service_Sis/target/generated-
> classes/cobertura/org/epo/cassius/csp/SearchInformationService.class
> > java.lang.ArrayIndexOutOfBoundsException: 8
> > at org.objectweb.asm.ClassReader.readUnsignedShort(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentationToSingleClass(Main.java:286)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentation(Main.java:364)
> > at net.sourceforge.cobertura.instrument.Main.
> addInstrumentation(Main.java:382)
> > at net.sourceforge.cobertura.instrument.Main.
> parseArguments(Main.java:440)
> > at net.sourceforge.cobertura.instrument.Main.main(Main.java:462)
> > [cobertura] WARN [main] net.sourceforge.cobertura.instrument.Main
> - Unable to instrument file
> /Users/davesag/checkouts/EPO/cassius_service_Sis/target/generated-
> classes/cobertura/org/epo/cassius/csp/SearchInformationServiceDelegate.class
> > java.lang.ArrayIndexOutOfBoundsException: 8
> > at org.objectweb.asm.ClassReader.readUnsignedShort(Unknown
Source)
> > at org.objectweb.asm.ClassReader.(Unknown
Source)
> > at org.objectw
Re: I can't get cobertura to work with maven 2.0.2
Brett Porter <[EMAIL PROTECTED]> wrote on 31-01-2006 18:46:42: > On 2/1/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > > > Okay I have changed my build so that the checkstyle etc all happen on the > > verify phase, and have updated to use the latest snapshot version of > > cobertura plugin. > > > > [mvn install] works fine - all is as expected. > > > > but [mvn site] continues to break as follows: > > > Do you have zero-length classes, or is this something else? I recall seeing > AIOOBE as a bug back in jcoverage some time back, but I'm not sure this is > the same. > yes that's exactly what is happening. the second (redundent) instrumentation generates 0 length classes. I am not sure what AIOOBE means. > I stress that this all used to work fine with maven 2.0 and the old > > cobertura plugin. I suspected a bug in the surefire reporting rather than > > in cobertura, and so removed any references to surefire from my reporting > > but i get pretty much the exact same result. > > > The cobertura plugin was changed around mid-Dec to better use the facilities > provided by Maven 2.0.1 for defining the lifecycle. > shame it broke eh. > Does anyone out there have a working example of maven 2.0.2 using cobertura > > to instrument classes and generate a report? If so please would you care to > > share your wisdom? Or would you recommend rolling back to maven 2.0 until > > these issues are fixed? > > > > We use it for: > https://svn.apache.org/repos/asf/maven/repository-manager/trunk > I see no reference at all to cobertura in https://svn.apache.org/repos/asf/maven/repository-manager/trunk/pom.xml dave
I can't get cobertura to work with maven 2.0.2
] [ERROR] BUILD ERROR [INFO] [INFO] There are some test failure. I stress that this all used to work fine with maven 2.0 and the old cobertura plugin. I suspected a bug in the surefire reporting rather than in cobertura, and so removed any references to surefire from my reporting but i get pretty much the exact same result. Does anyone out there have a working example of maven 2.0.2 using cobertura to instrument classes and generate a report? If so please would you care to share your wisdom? Or would you recommend rolling back to maven 2.0 until these issues are fixed? Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 31-01-2006 11:16:29: > On 1/31/06, David Sag <[EMAIL PROTECTED]> wrote: > > the version jason sent me was 2.0-SNAPSHOT > > Yep, still a snapshot: > http://maven.apache.org/guides/development/guide-testing- > development-plugins.html > > > so site *does* invoke compile and test then. for after all imho what use > > is the site without the surefire reports? > > Actually, I generally don't run the surefire reports, preferring to > fail the build if the tests don't pass and not generate the site. The > surefire report plugin needs some work, such as the effeciency you > mention. > > > Either way I probably need to bind checkstyle, pmd, findbugs etc to a > > phase other than compile then, perhaps verify. Hmm will ponder this. > > The reports, or the checks? The reports should be part of the site > generation and not bound to any phases. The checks definitely belong > in verify if they don't require any extra steps such as compilation. > > HTH, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Forcing the order of plugins bound to the same phase (was Re: M2.02 - mvn site now triggers a compile!)
Brett Porter <[EMAIL PROTECTED]> wrote on 31-01-2006 11:16:29: > On 1/31/06, David Sag <[EMAIL PROTECTED]> wrote: > > Either way I probably need to bind checkstyle, pmd, findbugs etc to a > > phase other than compile then, perhaps verify. Hmm will ponder this. > > The reports, or the checks? The reports should be part of the site > generation and not bound to any phases. The checks definitely belong > in verify if they don't require any extra steps such as compilation. > the checks. i run the checkstyle, pmd and findbugs checks and then in the verify stage pipe those checks into the qalab plugin to generate historical dev stats. ideally i'd run these as part of verify and then once they had run pipe them trhough qalab, but i have never been able to work out how to specify the order that plugins run when bound to the same phase. any clues how to do that? dave
Re: M2.02 - mvn site now triggers a compile!
Brett Porter <[EMAIL PROTECTED]> wrote on 31-01-2006 10:44:57: > On 1/31/06, David Sag <[EMAIL PROTECTED]> wrote: > > > I'll deploy a snapshot, so you can follow the instructions on the maven > > > website to use it. > > > > > > > Okay that would be great. Will you announce it to this list when you do > > please? I'll focus on something else until that point. > > Yep, already done. > ah thanks. i guess i am stupid but i can't see it in http://maven.apache.org/plugins/ is there somewhere more specific in the maven website i should look? I looked in http://www.ibiblio.org/maven2/maven-plugins/maven-cobertura-plugin/ but the latest version there is 1.1.1 dated 5 dec 2005. and there is no sign of it in http://www.ibiblio.org/maven2/org/apache/maven/plugins/ the version jason sent me was 2.0-SNAPSHOT > > > I'm not sure on this one. Would need to boil it down to something simple > > and > > > reproducible to look at it I think. > > > > > > > shall i raise a Jira issue? Unfortunately I can't supply the pom.xml and > > code I am using as it's internal to the EPO. > > Yes, I meant if you could reproduce it with something similar to your > build, without the variables. > i'll try out the new cobertural plugin first. > Do you know what versions of plugins you are using? A safe bet is to > remove ~/.m2/repository/org/apache/maven/plugins to ensure you are on > the last releases. > ok > > > I suspect one of the other plugins is doing this (eg surefire-report?) > > > > > > > hmm. there's nothing non-standard about the way I generate my surefire > > report so this is a bit of a mystery. > > But surefire-report does invoke compile and test to generate the > report - it has always done so. I thought you meant something was > happening in addition to that? > so site *does* invoke compile and test then. for after all imho what use is the site without the surefire reports? Why does it need to do this though? Surely if the tests have already been run and some sort of xml report has already been generated then the site report could simply transform that xml into a site with no need to recompile and run the tests. Either way I probably need to bind checkstyle, pmd, findbugs etc to a phase other than compile then, perhaps verify. Hmm will ponder this. cheers dave
Re: M2.02 - mvn site now triggers a compile!
Brett Porter <[EMAIL PROTECTED]> wrote on 30-01-2006 22:22:47: > On 1/30/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > so my questions: > > 1) could someone with a working (with maven 2.0.2) cobertura plugin please > > send it to me with the correct pom.xml - jason z only sent me the compiled > > plugin without any pom.xml so it is entirely possible this is a big part > > of my problem. > > > I'll deploy a snapshot, so you can follow the instructions on the maven > website to use it. > Okay that would be great. Will you announce it to this list when you do please? I'll focus on something else until that point. > 2) why would [mvn install site] fail, but separate [mvn install] followed by > > [mvn site] work okay? (once i have removed cobertura from the reporting) > > > I'm not sure on this one. Would need to boil it down to something simple and > reproducible to look at it I think. > shall i raise a Jira issue? Unfortunately I can't supply the pom.xml and code I am using as it's internal to the EPO. > 3) if the site phase is not supposed to trigger the compile and other phases > > then why would it be doing so, with or without the presence of thecobertura > > plugin? > > > I suspect one of the other plugins is doing this (eg surefire-report?) > hmm. there's nothing non-standard about the way I generate my surefire report so this is a bit of a mystery. > All this used to work fine using maven 2.0, and i was supposed to demo this > > last friday so you can imagine my frustration. > > > Sure, sorry about that. > > Any idea when the fixed cobertura plugin will be released properly? It's > > really not very acceptable to update the core maven project and then expect > > that we'll know to go build some plugins from source because they have been > > broken by the upgrade. I would prefer to see more comprehensive testing > > followed by simultanious release of a new core with new plugins and some > > mention in the release notes of any gotchas. As it is I am fighting an > > uphill battle to be able to recommend use of maven 2 for production systems > > as I have not been able to demonstrate that it is in fact stable for even > > pilot-project use. > > > Ok, you have to understand - the cobertura plugin has not ever been > released. Please don't generalise the situation. Simultaneous releases > should never be required as updates shouldn't break old released plugins > using documented and finalised APIs. > so you are telling me I have stumbled upon a very isolated case of the new release breaking a a plugin. Okay I can accept that. For now I will just have to make do without my lovely cobertura reports. Please let us know when you do deploy a snapshot of the working cobertura plugin however, as it really is a critical part of my project. dave
Re: M2.02 - mvn site now triggers a compile!
Hmm okay then something very strange is happening as when I type mvn site it attempts to compile my code again, then instrument the classes for cobertura again (only now generates 0 byte length classes doing so) and then dies running the unit tests via surefire. i don't have the source code for the fixed plugin, jason z just sent me the jar and i installed it manually into my repository. I just copied the pom.xml from the old cobertura polugin so that's possibly the cause of my problems. I have now update my pom.xml to use cobertura 1.7 but i get the exact same problem as before - mvn install works fine but mvn site reinstruments the classes and leaves them as 0 byte class files, causing surefire to die. Now here's where it gets weird too... If I comment out the cobertura lines from the reporting section of my project's pom.xml and, from a clean start type mvn install site the build and install part happens fine but I get the same errors with surefire trying to run against 0 byte length instrumented class files during the site phase. BUT: if i clean it all out and then first type mvn install and let that build okay, then as a separate task type mvn site with no cobertura data in the reporting section, then the site builds fine sans the cobertura reports. so mvn install site - fails. mvn install then mvn site - works. but only without any reference to conbertura in the reporting part of my project's pom.xml so now as an experiment I have removed any references to cobertura at all from the pom and lo and behold running mvn install site works perfectly. however looking at my consol I can see that when the site phase starts maven reports 'preparing sureffire report' then it indeed does attempt to recompile (but there have been no code changes obviously), then runs checkstyle and pmd and findbugs again, then compiles the tests (nothing to compile obviosuly), then runs the tests again, then site:site runs and the javadocs are generated and various reports and it's done. so something in my reporting is casuing maven to attempt to recompile with al of the subsequent activity attached to the compile phase, but the presence of the cobertura plugin really screws it up. so my questions: 1) could someone with a working (with maven 2.0.2) cobertura plugin please send it to me with the correct pom.xml - jason z only sent me the compiled plugin without any pom.xml so it is entirely possible this is a big part of my problem. 2) why would [mvn install site] fail, but separate [mvn install] followed by [mvn site] work okay? (once i have removed cobertura from the reporting) 3) if the site phase is not supposed to trigger the compile and other phases then why would it be doing so, with or without the presence of the cobertura plugin? All this used to work fine using maven 2.0, and i was supposed to demo this last friday so you can imagine my frustration. Any idea when the fixed cobertura plugin will be released properly? It's really not very acceptable to update the core maven project and then expect that we'll know to go build some plugins from source because they have been broken by the upgrade. I would prefer to see more comprehensive testing followed by simultanious release of a new core with new plugins and some mention in the release notes of any gotchas. As it is I am fighting an uphill battle to be able to recommend use of maven 2 for production systems as I have not been able to demonstrate that it is in fact stable for even pilot-project use. Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 27-01-2006 21:50:36: > On 1/28/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > 1) why does mvn site now trigger the other phases of the lifecycle. is > > this supposed to happen? > > > no. > > 2) anyone else using cobertura having this problem? > > > nope. > > 3) do i need to update my core cobertura libs too or is version 1.6 still > > okay for use with the 2.0 version of the plugin? > > > > > The POM from the plugin I'm using has 1.7. How do you mean "my cobertura > libs"? The plugin source should have specified the version. > > - Brett
Re: SV: Worst documentation in the whole apache projects
well i would agree in principle but the maven2 plugin matrix you list is hopelessly out of date, and always has been. my current irritation is that i have no idea what the latest versions of most plugins are and what their compatability status with maven 2.0.2 is. I foolishly upgraded to 2.0.2 and now can't get my projects to build properly anymore. Kind regards, Dave Sag Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote on 19-01-2006 17:19:20: > I have posted a wish in JIRA on some kind of standard for plugin > documentation à la http://cargo.codehaus.org/Maven2+plugin. Under > "Documentation". Vote for it if you agree! > > Regards, > > /B-E > > > -Ursprungligt meddelande- > Från: Tim OBrien [mailto:[EMAIL PROTECTED] > Skickat: den 19 januari 2006 17:05 > Till: Maven Users List > Ämne: Re: Worst documentation in the whole apache projects > > I've have to totally agree. 200% The documentation is a total joke, it's > hard to read and the > maintainers don't seem to care to create a consolidated reference. > > And, the book by Vincent Massol and Tim O'Brien is just a total rag. I mean > really, full of typos > and everything. C'mon, if Maven were so EASY, why wold we need to read > anything to know how to > use it. > > How do they expect us to start a multi-project build when the help > documentation is TOTALLY BLANK! > And, the fact that Maven forces you to use the ibiblio > repositorypuh-lease. > > You are right though, really I'd have to recommend gmake from now on. Maven > is for the birds. I > mean, seriously, what are we paying these people for!?! > > :-) > > Tim O'Brien > [EMAIL PROTECTED] > > > > --- "Nanamura, Roberto" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Is there any way to improve all the documentation for the Maven. > > > > I will not use Maven anymore since there are a bunch of thing missing > > from the documentation (and a lot of things do not work like the J2EE > > archetype which is nowhere to be find and I am not the only one to > > complain about it). > > > > It is good for a simple project (then again, why should I need maven for > > a simple Hello World project?). But if you add a J2EE layer or other > > components, it simpy does not have document (for example no document for > > the topic: "Guide to creating a multi-module build"). Then how should I > > create a multi-project maven? What is this artifactId and groupID? What > > the hell it keeps on going to the repo1.maven.org repository for my > > sub-projects? What are the examples? No samples? > > > > The reference is a joke. How can a reference be so laconious? It is a > > reference so every tag in the XML must have a good description (even the > > description in the generated xml is better than the reference!). > > > > I do not recommend Maven to anyone starting a serious project for lack > > of documentation and erroneous documentation. > > > > I spent the whole day try to make it work for a simple J2EE project, > > then I had to google it several times for each error (it should be in > > the document web-site). > > Whereas I would take one hour to create the directories, my build and > > deployment ant targets. > > > > Thanks but I'd rather do not use it, > > > > Roberto > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
M2.02 - mvn site now triggers a compile!
Hi People, I've recently upped to maven 2.0.2 from 2.0 and have hit some problems with cobertura. jason z sent me a fresh new cobertura plugin and if i go mvn install it instruments okay and the unit tests all run fine. but when i go to generate my site (mvn site) maven now does a full compile cycle again, runs all the checkstyle/findbugs/ etc stuff, re-instruments the code but this time the instrumented classes are 0bytes and i get a host of errors as a result. my questions are: 1) why does mvn site now trigger the other phases of the lifecycle. is this supposed to happen? 2) anyone else using cobertura having this problem? 3) do i need to update my core cobertura libs too or is version 1.6 still okay for use with the 2.0 version of the plugin? Kind regards, Dave Sag
Re: [M2.0.2] cobertura-maven-plugin not working with 2.0.2
ahah just saw this mail. could someone please send me the latest plugin as a zip file? I have trouble getting svn working from in here. Kind regards, Dave Sag Konstantin Polyzois <[EMAIL PROTECTED]> wrote on 23-01-2006 20:27:05: > ok now it works again nice > 2006/1/23, Brett Porter <[EMAIL PROTECTED]>: > > fixed in SVN of the cobertura plugin. > > > > On 1/23/06, Weichsel, Ingo <[EMAIL PROTECTED]> wrote: > > > > > > Hello, > > > > > > I like the cobertura-maven-plugin a lot, which I builded from the > > > mojo-sandbox. This plugin did work fine with the maven-2.0.1 > release, but is > > > not working with maven-2.0.2 any more. Does any of you know a > workaround or > > > will there be an updated version soon? > > > > > > Regards, > > > Ingo > > > > > > Stacktrace: > > > > > > [INFO] [cobertura:instrument] > > > [INFO] > > > > > > > [ERROR] FATAL ERROR > > > [INFO] > > > > > > > [INFO] org/apache/maven/wagon/util/FileUtils > > > [INFO] > > > > > > > [INFO] Trace > > > java.lang.NoClassDefFoundError: org/apache/maven/wagon/util/FileUtils > > > at > > > org.codehaus.mojo.cobertura.tasks.AbstractTask. > getLog4jConfigFile(AbstractTa > > > sk.java:107) > > > at > > > org.codehaus.mojo.cobertura.tasks.AbstractTask. > executeJava(AbstractTask.java > > > :128) > > > at > > > org.codehaus.mojo.cobertura.tasks.InstrumentTask. > execute(InstrumentTask.java > > > :122) > > > at > > > org.codehaus.mojo.cobertura.CoberturaInstrumentMojo. > execute(CoberturaInstrum > > > entMojo.java:101) > > > at > > > org.apache.maven.plugin.DefaultPluginManager. > executeMojo(DefaultPluginManage > > > r.java:415) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoals(DefaultLife > > > cycleExecutor.java:531) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoalWithLifecycle > > > (DefaultLifecycleExecutor.java:472) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > forkProjectLifecycle(Def > > > aultLifecycleExecutor.java:859) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > forkLifecycle(DefaultLif > > > ecycleExecutor.java:731) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoals(DefaultLife > > > cycleExecutor.java:522) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoalWithLifecycle > > > (DefaultLifecycleExecutor.java:472) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoal(DefaultLifec > > > ycleExecutor.java:451) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeGoalAndHandleFail > > > ures(DefaultLifecycleExecutor.java:303) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > executeTaskSegments(Defa > > > ultLifecycleExecutor.java:270) > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor. > execute(DefaultLifecycle > > > Executor.java:139) > > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > at > > > sun.reflect.NativeMethodAccessorImpl. > invoke(NativeMethodAccessorImpl.java:39 > > > ) > > > at > > > sun.reflect.DelegatingMethodAccessorImpl. > invoke(DelegatingMethodAccessorImpl > > > .java:25) > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > 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) > > > [INFO] > > > - > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
cobertura plugin breaks with maven 2.02 - wors fine with 2.0
I have just updated my maven 2 to 2.0.2 and now the instrumentation of my classes fails when using the cobertura plugin. I get NoClassDefFoundError: org/apache/maven/wagon/util/FileUtils any clues as to what changed between 2.0 and 2.0.2 that would lead to this error? most frustrating Kind regards, Dave Sag
Re: [m2] Migrating mockobject calls to Maven2
We use EasyMock and all that needs is to put the folllowwing in the pom. there are no generated files like with what you describe however. it makes great little mockobjects though using the cglib. easymock easymock 1.2_Java1.3 test easymock easymockclassextension 1.1 test Kind regards, Dave Sag "Dennis Ho" <[EMAIL PROTECTED]> wrote on 28-12-2005 07:08:42: > Hi, > > I am in the process of migrating some existing maven tasks to > use maven 2. We use mockobjects in our code for testing purposes, and I > would like to know if anyone has experience using maven2 with > mockobjects can give me some pointer as to how the pom should look like. > > When we did it with maven 1.x we have to use ant like the > following: > > > classname="de.abstrakt.tools.codegeneration.file.MockCreatorFile" > fork="yes" failonerror="true" > classpathref="mockcreator.classpath"> > > > > > > > > > > > > Is there a more natural way to do it in Maven 2? I can't find anything > from the web so any advice is welcome. > > Thanks in advance for your help! > > Regards, > > Dennis Ho.
Re: SV: LOTS of dependencies just not found
I think that is actually an excellent solution - i am going through similar pain right now - our build of maven2 does what we want on a few test projects of increasing complexity, but we've written a bunch of patches (submitted via jira) and plugins to get where we are and it's still not exactly a no brainer for someone to move to maven 2. a big part of that is the overall veracity of the ibiblio libs themselves. some tool needs to be written that checks every upload to ibiblio and rejects that upload if the dependencies cannot be downloaded. Kind regards, Dave Sag Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote on 27-12-2005 17:13:48: > Wrote an issue to maven-repository-plugin-JIRA. > I don't think you should be allowed to publish to repository if dependencies > of the stuff you're publishing does not exist. > > Regards, > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
reverse dependency management
We have many interdependent projects here. When someone releases a project upon which many other projects depend we need some way of knowing automatically which projects will also need to be retested. is there a m2 plugin that manages reverse dependency lookups? For simplicity I am really mostly concerned with changes to our internal projects here. Kind regards, Dave Sag
Re: Is it possible to make pom.xml simpler?
+1 to that. Kind regards, Dave Sag Matt Raible <[EMAIL PROTECTED]> wrote on 15-12-2005 02:06:04: > After seeing what the Spring Developers have done to simplify Spring > context files, I can't help but think the same thing is possible for > Maven 2's pom.xml. Is it possible to add namespaces and make > something like the following possible? > > Before: > > > springframework > spring > 1.2.6 > > > After: > > > > Or just allow attributes to make things a bit cleaner? > > > version="1.2.6"/> > > Allowing 1 line instead of 5-6 lines per dependency would allow me to > cut my dependencies listing from 140 lines of XML to 37 lines. When > the Spring guys allows a couple of elements as attributes ( and > ) - it made writing Spring context files *much* easier. > > Here's an example of my simplified version: > > > > scope="test"/> > > version="2.0"/> > > version="1.0.4"/> > > version="1.0" scope="runtime"> > > > > > > version="1.0" scope="runtime"/> > > version="3.0.5"> > > > > > > version="1.0.1B-rc4"/> > > scope="test"/> > > scope="test"/> > > scope="test"/> > > scope="test"> > > > > > > > version="8.1-404.jdbc3"/> > > version="2.4" scope="provided"/> > > version="1.1.2" scope="runtime"/> > > version="1.1.2" scope="runtime"/> > > version="2.2.1" scope="runtime"/> > > artifactId="springmodules-validator" version="0.1" scope="runtime"/> > > version="1.2.6"/> > > version="1.2.6" scope="test"> > > > > > > > > Of course, Ivy's syntax is even simpler, so maybe that'll provide some > motivation. ;-) > > > > > > > Matt > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Surefires test order
JUnit tests never run in a specific
order and you are stongly advised never to depend upon their execution
order.
if it worked for you at all that is
just a lucky fluke
Kind regards,
Dave Sag
Jochen Wiedmann <[EMAIL PROTECTED]>
wrote on 13-12-2005 16:21:44:
> Hi,
>
> I have a test suite that depends on a certain order of tests. More
> precisely, a unit test, which looks like
>
> public class MyTest extends TestCase {
> public void testFoo(){ ... }
> public void testBar(){ ... }
> }
>
> assumes, that testFoo() is invoked before testBar(). This works fine,
> when running the tests from within Ant, or Eclipse.
>
> My impression is, that Surefire doesn't keep this order. Can anyone
> confirm this? I assume, that reordering the methods is intentional?
> However, if so, two questions arise to me:
>
> - A reordering occurs, both for test classes (which are typically
executed in
> alphabetical orders by other frameworks), and methods. However,
the reorder
> doesn't look choosen randomly: It is reproducable.
>
> But if the desired effect is to stop the user from assuming
a
> certain order, why
> isn't it random?
>
> - Would it be possibly to accept a patch, which restores the typical
> order on the users
> behalf (for example, by setting a property "canonicalOrder")?
The
> test suite isn't
> written by me, and I am almost unable to change it.
>
>
> Thanks,
>
> Jochen
>
>
> --
> Often it does seem a pity that Noah and his party did not miss the
> boat. (Mark Twain)
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: Invalid SCM URL
ah of course - makes sense but here's an interesting q then... we are setting up continuum to build our m2 projects. i'd like continuum to check out the code from CVS, build it, build the site, deploy the site, generate notification emails and generate a snapshot release. all using the same pom.xml file as any developer would. is that 'best practice'or am i missing some key concept? if so then how would i prevent 'any old developer' from running mvn release? Kind regards, Dave Sag Kenney Westerhof <[EMAIL PROTECTED]> wrote on 12-12-2005 14:56:23: > On Mon, 12 Dec 2005, David Sag wrote: > > > No; you can specify the username/password in ~/.m2/settings.xml > in a tag. > I'm not really sure a password is needed for svn/cvs; if you logged in > once on the command line the password is stored in ~/.subversion/ or > ~/.cvspass, but I'm not sure the scm code uses that (yet). > > -- Kenney > > > Does this imply i need to put a username and password into my pom.xml as > > hard coded params? > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Jean-Charles Giardina <[EMAIL PROTECTED]> wrote on 08-12-2005 > > 10:59:29: > > > > > The correct scm URL format is : > > > > > > scm:cvs:pserver:[username[:[EMAIL PROTECTED]:port]: > > > path_to_repository:module_name > > > > > > For your example that mean : > > > > > > scm:cvs:pserver:[EMAIL PROTECTED]:/r:m > > > > > > don't miss the first '/' at repository path > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Invalid SCM URL
Does this imply i need to put a username and password into my pom.xml as hard coded params? Kind regards, Dave Sag Jean-Charles Giardina <[EMAIL PROTECTED]> wrote on 08-12-2005 10:59:29: > The correct scm URL format is : > > scm:cvs:pserver:[username[:[EMAIL PROTECTED]:port]: > path_to_repository:module_name > > For your example that mean : > > scm:cvs:pserver:[EMAIL PROTECTED]:/r:m > > don't miss the first '/' at repository path > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] clover and assertions
I believe you need to also specify the source version for the clover plugin too. it does not default to the same as the compiler plugin setting - same too for javadocs and indeed other plugins. It seems to me that this sort of config is project wide and the pom needs a place to declare such project wide configs. Kind regards, Dave Sag "Mike Perham" <[EMAIL PROTECTED]> wrote on 29-11-2005 20:49:45: > I'm running clover:check with clover plugin 2.0a1 and finding that it is > choking on my asserts. I have the compiler plugin configured as > follows: > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.4 > 1.4 > > > > Am I missing something else? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
[m2] migrating jellly scripts
I am migrating a plugin to m2 and the original maven 1 plugin makes quite a bit of use of jelly scripts, as well as XSLT transformations. The xslt stuff is easy to migrate, but I have never even looked at jelly before. Is there a simple way in Java to apply jelly scripts, or should i rewrite them to be more like the xslt scripts? Ideally i could use the same jelly scripts as in the m1 plugin. Are there any simple examples of an m2 report generated using a jelly script? Kind regards, Dave Sag
Re: writing a new plugin
You are basically correct - just write a Mojo that mirrors the ant task. you can leave out the getters and setters and throw a slightly different exception but that's about the only difference. Kind regards, Dave Sag Brill Pappin <[EMAIL PROTECTED]> wrote on 27-11-2005 01:25:16: > I'm about to embark on writing a maven 2 plugin for Antenna. > > Antenna has existing Ant tasks defined (in fact its an Ant task lib). > > In Maven 1 it was fairly easy to implement a Maven plugin using ant tasks > because you could simple call them int he plugin... how would that type of > conversion be done for Maven 2? > > So far the best I can see is to create a new Mojo that mirrors the Ant > task(s). > > Is there documentation some place on converting an Ant task to a maven goal?
Re: [M2] How to fire plugin in site generation?
I've just done this actually. Make it a report and override the isExternalReport() method to return true; then you don't need to use the Sink at all. Kind regards, Dave Sag Jose Gonzalez Gomez <[EMAIL PROTECTED]> wrote on 24-11-2005 15:46:55: > Is there any way to fire the execution of a plugin whenever the site > plugin is executed? I would like to add some dinammically generated > content to the site, but I don't want to use the report mechanism, as > this forces me to use the Sink interface to write content, doesn't it? > Or can I turn my plugin into a report, just ignore the Sink and write > the contect directly to some known location? > > TIA, best regards > Jose > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: MNG-1398: How to obtain an updated version of the maven-javadoc-plugin
Yeah I have been meaning to sort that out but it's taken low priority over other things here. Many thanks to those of you who reacted so fast and sent me a working plugin tho - now my demo is looking great. Kind regards, Dave Sag Wim Deblauwe <[EMAIL PROTECTED]> wrote on 24-11-2005 15:14:43: > Tip to get svn to work through a firewall: use https instead of http. It > worked for me. > > regards, > > Wim > > 2005/11/24, David Sag <[EMAIL PROTECTED]>: > > > > > > I would like it too. We have a first presentation tomorrow of the maven 2 > > stuff we have been doing and it is a little embrarrasing to have no javadocs > > available. > > > > I know we *could* build it from SVN but honestly I'd just rather someone > > send me a zipped up plugin I can just drop in manually. We don't use SVN at > > all in here (much as I'd like to) and I am yet to be able to get SVN to work > > thru our firewalls. > > > > So if someone has a newer build of the javadoc plugin could they please > > email or skype me a zip file and i'll drop it into my repository manually. > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Jochen Wiedmann <[EMAIL PROTECTED]> wrote on 09-11-2005 > > 12:41:44: > > > > > > > > Hi, > > > > > > sorry for asking the stupid question: I am one of the users who stumbled > > > > > over > > > > > > MNG-1398: site report generates an 'empty' > > > target/site/apidocs/index.html > > > > > > I see that a fixed version of the plugin will be available in Maven > > > 2.0.1. Very nice. But do I actually have to wait for that version? Or, > > > do I have to rebuild Maven from SVN? > > > > > > Regards, > > > > > > Jochen > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: MNG-1398: How to obtain an updated version of the maven-javadoc-plugin
I would like it too. We have a first presentation tomorrow of the maven 2 stuff we have been doing and it is a little embrarrasing to have no javadocs available. I know we *could* build it from SVN but honestly I'd just rather someone send me a zipped up plugin I can just drop in manually. We don't use SVN at all in here (much as I'd like to) and I am yet to be able to get SVN to work thru our firewalls. So if someone has a newer build of the javadoc plugin could they please email or skype me a zip file and i'll drop it into my repository manually. Kind regards, Dave Sag Jochen Wiedmann <[EMAIL PROTECTED]> wrote on 09-11-2005 12:41:44: > > Hi, > > sorry for asking the stupid question: I am one of the users who stumbled > over > > MNG-1398: site report generates an 'empty' > target/site/apidocs/index.html > > I see that a fixed version of the plugin will be available in Maven > 2.0.1. Very nice. But do I actually have to wait for that version? Or, > do I have to rebuild Maven from SVN? > > Regards, > > Jochen > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] commons-io 1.1 POM invalid
Thanks Paul - I have xposted to that jira too for completeness. Kind regards, Dave Sag Paul Spencer <[EMAIL PROTECTED]> wrote on 23-11-2005 16:29:49: > David, > Below is a link to the Maven Evangelism JIRA project. > http://jira.codehaus.org/browse/MEV > > Paul Spencer > > David Sag wrote: > > Snap! I just filed a jira issue on this about 20 mts ago - could not find > > any special 'evangelism' jira however. I did look for it tho. > > > > http://jira.codehaus.org/browse/MNG-1668 > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Wim Deblauwe <[EMAIL PROTECTED]> wrote on 23-11-2005 15:33:49: > > > > > >>Best is to file in bug in Maven Evangilsm JIRA > >> > >>2005/11/23, Richard Allen <[EMAIL PROTECTED]>: > >> > >>>I'm not sure if this is where this problem should be noted, but the > > > > POM > > > >>>for commons-io 1.1 is invalid because the closing dependencies tag is > >>>mispelled as . > >>> > >>>Richard Allen > >>> > >>>- > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] commons-io 1.1 POM invalid
Snap! I just filed a jira issue on this about 20 mts ago - could not find any special 'evangelism' jira however. I did look for it tho. http://jira.codehaus.org/browse/MNG-1668 Kind regards, Dave Sag Wim Deblauwe <[EMAIL PROTECTED]> wrote on 23-11-2005 15:33:49: > Best is to file in bug in Maven Evangilsm JIRA > > 2005/11/23, Richard Allen <[EMAIL PROTECTED]>: > > > > I'm not sure if this is where this problem should be noted, but the POM > > for commons-io 1.1 is invalid because the closing dependencies tag is > > mispelled as . > > > > Richard Allen > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > >
Re: Newbie: problem creating checkstyle report
Hi Volker, Volker Hartmann <[EMAIL PROTECTED]> wrote on 22-11-2005 14:06:08: > Hi David, > > > I have got checkstyle working fine (sadly still without the option to > > specify a custom config - see http://jira.codehaus.org/browse/MNG-1113). > > I already know that. :-( > > > > > the groupId is org.apache.maven.plugins > > artifactId is maven-checkstyle-plugin > > Which version of maven do you use!? 2.0 > And which version of the plugin? not sure - whatever the lastest in maven's repository is. i don't explicitly specify a version. > I also tried this in the reporting section of the pom > without any success. > > > we (small internal team here where I work) are writing a FindBugs > > plugin now for maven2. I expect we'll be releasing it to the findbugs > > or maven people as soon as we are happy with it. similary for > > Cobertura and maybe even PMD, which is rather broken wrt maven 2. > > (see http://jira.codehaus.org/browse/MNG-1158) > > Sounds great. I'm looking forward for this. :-) > me too cheers dave > Kind regards, > Volker > > > There is an irony here in that the plugins with the most problems are > > all to do with software quality monitoring. The javadoc plugin is > > broken and has been for over a month, pmd plugin is utterly useless, > > checkstyle is only almost working, findbugs was not even attempted, > > same with qalab. Even support for the java1.4 assert statement is > > there as an afterthought. (http://jira.codehaus.org/browse/MNG-1087) > > > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Volker Hartmann <[EMAIL PROTECTED]> wrote on 22-11-2005 08:24:18: > > > > > Hi, > > > > > > I tried to generate a report for my first project. > > > (I used the Maven Quick Start Archetype.) > > > I added the following lines in the pom.xml > > > > > > ... > > > > > > > > > > > > org.apache.maven.plugins > > > maven-project-info-reports-plugin > > > > > > > > > org.apache.maven.plugins > > > maven-checkstyle-plugin > > > > > > > > > > > > > > > (Maybe somone can explain me why the documentation uses this > > > groupId and artifactId is mentioned nowhere else in the documentation > > > but in the example together with an old version!? > > > http://maven.apache.org/plugins/maven-checkstyle-plugin/howto.html ) > > > But I got an error message. I tried several versions (3.4, 4.0 beta 6, > > > ...) with different > > > errors. > > > I also tried > > > > > > checkstyle > > > checkstyle > > > > > > with no success. > > > > > > Another problem is that I can call the goal directly via > > > mvn checkstyle:checkstyle but the configuration set in pom.xml > > > seems to be ignored. > > > > > > BTW: I use Maven 2.0 but I also tried the 2.0.1 from the SVN > > > > > > I appreciate any help and thanks in advance > > > Volker > > > > > > P.S.: I also tried to generate a report for findbugs without > > > any success. > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: maven2 plugin suggestions
On this point - for us mac users it would be neat to finish the release phase by generating all the bits and pieces that allow a java app to look like a real mac app - ie a MyApp.app folder with the content in the right places and a custom icon etc. Kind regards, Dave Sag Paul Rule <[EMAIL PROTECTED]> wrote on 22-11-2005 10:22:18: > I often write stand alone apps, and I've often thought > it would be good to have a plugin to bundle up a build > complete with all the dependent jars, scripts, config > files etc - and to even generate the run.bat & run.sh > scripts. > > Is there anything like this currently (I talking > maven2) - if I wrote it would anyone else find it > useful? > > Also, would anyone find a plugin that generated the > java service wrapper configuration useful? > > > > > Do you Yahoo!? > The New Yahoo! Movies: Check out the Latest Trailers, Premiere > Photos and full Actor Database. > http://au.movies.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Newbie: problem creating checkstyle report
I have got checkstyle working fine (sadly still without the option to specify a custom config - see http://jira.codehaus.org/browse/MNG-1113). the groupId is org.apache.maven.plugins artifactId is maven-checkstyle-plugin we (small internal team here where I work) are writing a FindBugs plugin now for maven2. I expect we'll be releasing it to the findbugs or maven people as soon as we are happy with it. similary for Cobertura and maybe even PMD, which is rather broken wrt maven 2. (see http://jira.codehaus.org/browse/MNG-1158) There is an irony here in that the plugins with the most problems are all to do with software quality monitoring. The javadoc plugin is broken and has been for over a month, pmd plugin is utterly useless, checkstyle is only almost working, findbugs was not even attempted, same with qalab. Even support for the java1.4 assert statement is there as an afterthought. (http://jira.codehaus.org/browse/MNG-1087) Kind regards, Dave Sag Volker Hartmann <[EMAIL PROTECTED]> wrote on 22-11-2005 08:24:18: > Hi, > > I tried to generate a report for my first project. > (I used the Maven Quick Start Archetype.) > I added the following lines in the pom.xml > > ... > > > > org.apache.maven.plugins > maven-project-info-reports-plugin > > > org.apache.maven.plugins > maven-checkstyle-plugin > > > > > (Maybe somone can explain me why the documentation uses this > groupId and artifactId is mentioned nowhere else in the documentation > but in the example together with an old version!? > http://maven.apache.org/plugins/maven-checkstyle-plugin/howto.html ) > But I got an error message. I tried several versions (3.4, 4.0 beta 6, > ...) with different > errors. > I also tried > > checkstyle > checkstyle > > with no success. > > Another problem is that I can call the goal directly via > mvn checkstyle:checkstyle but the configuration set in pom.xml > seems to be ignored. > > BTW: I use Maven 2.0 but I also tried the 2.0.1 from the SVN > > I appreciate any help and thanks in advance > Volker > > P.S.: I also tried to generate a report for findbugs without > any success. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] mojo report (sink mandatory content ?)
Or, as I have just discovered, (thanks
brett), if your report implements isExternalReport() by returning true
then you need not use the sink at all, but can generate the whole page
/ pages you want directly.
You are right tho - the page will be
named getOutputName() + ".html"
Kind regards,
Dave Sag
"Olivier Lamy" <[EMAIL PROTECTED]>
wrote on 21-11-2005 13:29:42:
> Hi,
> I have a question concerning doxia Sink in report Mojo.
> Is there any mandatory content in Sink ?
> Actually I try the very simple :
> Sink sink = getSink();
> sink.head();
> sink.text("Test Report");
> sink.head_();
> sink.body();
> sink.text("test");
> sink.body_();
> sink.flush();
> sink.close();
>
> As I understand the html page will be getOutputName() . html ?
> Or I have probably forgot content in the sink.
>
> My pom has dependency :
>
> doxia
> doxia-sink-api
> 1.0-alpha-4
>
>
> Thanks for help,
> - Olivier
>
>
>
> This e-mail, any attachments and the information contained therein
> ("this message") are confidential and intended solely for
the use of
> the addressee(s). If you have received this message in error please
> send it back to the sender and delete it. Unauthorized publication,
> use, dissemination or disclosure of this message, either in whole
or
> in part is strictly prohibited.
> **
> Ce message electronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci apres "le message"
),
> sont confidentiels et destines exclusivement a l'usage de la
> personne a laquelle ils sont adresses. Si vous avez recu ce message
> par erreur, merci de le renvoyer a son emetteur et de le detruire.
> Toutes diffusion, publication, totale ou partielle ou divulgation
> sous quelque forme que se soit non expressement autorisees de ce
> message, sont interdites.
> **
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: [m2] where to put test data
Just a short note tho:
There is no system property called java.io.tmp.dir
it's called java.io.tmpdir
Kind regards,
Dave Sag
David Sag <[EMAIL PROTECTED]> wrote on 18-11-2005
11:08:17:
>
> Thanks John those answers were perfectly satisfactory and i have
> updated my code accordingly.
>
> a point to note however - the path to the resource should not start
witha '/'
>
> i have not looked but i wonder what the file path to a file within
a
> jar looks like. under maven the unit tests run before the jar
is
> made. i shall explore this a bit more.
>
> and two - i went with the java.io.tmp.dir idea - seemed to me to be
> the most useful.
>
> Kind regards,
> Dave Sag
>
>
> [image removed]
>
>
>
> John Casey <[EMAIL PROTECTED]> wrote on 17-11-2005 16:52:13:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > David Sag wrote:
> > |
> > | I am writing the unit tests for a simple xml transformer and
want to
> > | know 2 things.
> > |
> > | 1) where is the maven2 approved place to put the test xml and
xslt
> > | files? If I put them in src/test/resources then they
end up in a jar
> > | file, and I am not sure how i refer to their path when i invoke
File xml
> > | = new File("test.xm;");
> > | - so advice wanted please.
> >
> > it may be a little hacky, but what I've used is:
> >
> > ClassLoader loader = getClass().getClassLoader();
> > String resourceName = "/path/to/test.xslt";
> > URL resource = loader.getResource( resourceName );
> >
> > File testFile;
> > if ( resource != null )
> > {
> > ~ testFile = new File( resource.getPath() );
> > }
> > else
> > {
> > ~ throw new SomethingException(..);
> > }
> >
> > // use file.
> >
> > This assumes that the test resources are somewhere in the classpath,
not
> > necessarily in a jar. It works regardless of the ${user.dir}
used, which
> > ~ makes it more resilient to IDE vs. Maven test invocation...
> >
> > |
> > | 2) where is the best place to write test output that I then
clean up?
> > | in this case i want to write out the transformed file
and check that it
> > | contains what I expect. I am wtiting to target/temp -
is that what you
> > | other maven2 users are doing?
> >
> > You could pass in the directory via:
> >
> >
> > ~ ...
> > ~
> > ~
> > ~ maven-surefire-plugin
> >
> > ~
> > ~
> > ~ ${project.build.directory}/temp
> > ~
> > ~
> > ~
> > ~
> >
> >
> > This is usually going to be the same as using target/temp, but
it will
> > track any changes in
within the POM. Of
> > course, that means you'll have to call:
> >
> > System.setProperty( "output", "/path" );
> >
> > when you want to run the test outside of Maven...Another possibility
> > would be to use a location within ${java.io.tmp.dir}...a temporaryfile/dir.
> >
> > HTH,
> >
> > John
> >
> > |
> > | Kind regards,
> > | Dave Sag
> > |
> > |
> > |
> > |
> > |
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v1.2.6 (GNU/Linux)
> >
> > iD8DBQFDfKctK3h2CZwO/4URApFTAJsFhDlZaD5y1eO5UXWIfPkpQkRq+ACcCHcX
> > 5TlKSnWBjnCF7y/8J0f/Z/k=
> > =0ZHf
> > -END PGP SIGNATURE-
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
[m2] which report?
The plugin i am writing has 3 general goals and 2 reports. How do I specify in my pom.xml file which report to run? Kind regards, Dave Sag
Re: [m2] where to put test data
Thanks John those answers were perfectly
satisfactory and i have updated my code accordingly.
a point to note however - the path to
the resource should not start witha '/'
i have not looked but i wonder what
the file path to a file within a jar looks like. under maven the
unit tests run before the jar is made. i shall explore this a bit
more.
and two - i went with the java.io.tmp.dir
idea - seemed to me to be the most useful.
Kind regards,
Dave Sag
John Casey <[EMAIL PROTECTED]> wrote on
17-11-2005 16:52:13:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> David Sag wrote:
> |
> | I am writing the unit tests for a simple xml transformer and want
to
> | know 2 things.
> |
> | 1) where is the maven2 approved place to put the test xml and xslt
> | files? If I put them in src/test/resources then they end up
in a jar
> | file, and I am not sure how i refer to their path when i invoke
File xml
> | = new File("test.xm;");
> | - so advice wanted please.
>
> it may be a little hacky, but what I've used is:
>
> ClassLoader loader = getClass().getClassLoader();
> String resourceName = "/path/to/test.xslt";
> URL resource = loader.getResource( resourceName );
>
> File testFile;
> if ( resource != null )
> {
> ~ testFile = new File( resource.getPath() );
> }
> else
> {
> ~ throw new SomethingException(..);
> }
>
> // use file.
>
> This assumes that the test resources are somewhere in the classpath,
not
> necessarily in a jar. It works regardless of the ${user.dir} used,
which
> ~ makes it more resilient to IDE vs. Maven test invocation...
>
> |
> | 2) where is the best place to write test output that I then clean
up?
> | in this case i want to write out the transformed file and
check that it
> | contains what I expect. I am wtiting to target/temp - is that
what you
> | other maven2 users are doing?
>
> You could pass in the directory via:
>
>
> ~ ...
> ~
> ~
> ~ maven-surefire-plugin
>
> ~
> ~
> ~ ${project.build.directory}/temp
> ~
> ~
> ~
> ~
>
>
> This is usually going to be the same as using target/temp, but it
will
> track any changes in
within the POM. Of
> course, that means you'll have to call:
>
> System.setProperty( "output", "/path" );
>
> when you want to run the test outside of Maven...Another possibility
> would be to use a location within ${java.io.tmp.dir}...a temporary
file/dir.
>
> HTH,
>
> John
>
> |
> | Kind regards,
> | Dave Sag
> |
> |
> |
> |
> |
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFDfKctK3h2CZwO/4URApFTAJsFhDlZaD5y1eO5UXWIfPkpQkRq+ACcCHcX
> 5TlKSnWBjnCF7y/8J0f/Z/k=
> =0ZHf
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
[m2] where to put test data
I am writing the unit tests for a simple
xml transformer and want to know 2 things.
1) where is the maven2 approved place
to put the test xml and xslt files? If I put them in src/test/resources
then they end up in a jar file, and I am not sure how i refer to their
path when i invoke File xml = new File("test.xm;");
- so advice wanted please.
2) where is the best place to write
test output that I then clean up? in this case i want to write out
the transformed file and check that it contains what I expect. I
am wtiting to target/temp - is that what you other maven2 users are
doing?
Kind regards,
Dave Sag
Re: m2 VSS access
My heart goes out to you. We used VSS on a project back in 2000 and it was a truly horrible experience. Do you have the option to change to a more collaborative tool such as subversion, or even CVS? Kind regards, Dave Sag "Maruf Aytekin" <[EMAIL PROTECTED]> wrote on 17-11-2005 09:43:32: > Hello, > > I use VSS as SCM. any ideas how can I access VSS to fetch the source for > a maven2 project?? > > Thanks, > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
[m2] reports - how to use the sink?
Hi people, I have got a basic report compiling that extends the AbstractMavenReport but now it comes to actually implimenting the exectureReport method and I am not really sure what the 'Sink' is or how I would use it. Could someone point me at the docs on this? Kind regards, Dave Sag
[m2] looking for example reports
I need to write a report that applies an XSLT transformation to an xml file to spit out the right HTML. I know I am being lazy here but is there an example of this sort of thing in any of the existing plugins. The last time i did an xslt transformation was using cocoon1. Kind regards, Dave Sag
Re: [m2] Clover plugin
We are about to start using cobertura but as of right now there is no m2 plugin for it that i know of. We were going to write our own. Kind regards, Dave Sag javed mandary <[EMAIL PROTECTED]> 15-11-2005 08:03 Please respond to "Maven Users List" To Maven Users List cc Subject Re: [m2] Clover plugin What dont you guys use cobertura*(code coverage tool) instead of clover , its free compared to clover where you need to have a license . http://cobertura.sourceforge.net/ regards, Javed On 11/15/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > This is what I get from maven calling 'mvn -e site' > > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] > > > [INFO] Building Utils Logging Module > [INFO] task-segment: [site] > [INFO] > > > [INFO] > > > [ERROR] BUILD ERROR > [INFO] > > > [INFO] The plugin 'org.apache.maven.plugins:maven-clover-plugin' does not > exist or no valid version could be found > [INFO] > > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin ' > org.apache.maven.plugins:maven-clover-plugin' does not exist or no valid > version could be found > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin( > DefaultLifecycleExecutor.java:1164) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports( > DefaultLifecycleExecutor.java:642) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports( > DefaultLifecycleExecutor.java:622) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > DefaultLifecycleExecutor.java:501) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > (DefaultLifecycleExecutor.java:469) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( > DefaultLifecycleExecutor.java:448) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > (DefaultLifecycleExecutor.java:301) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments > ( > DefaultLifecycleExecutor.java:268) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java > :39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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.version.PluginVersionNotFoundException: > The plugin 'org.apache.maven.plugins:maven-clover-plugin' does not exist > or > no valid version could be found > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion > (DefaultPluginVersionManager.java:225) > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReportPluginVersion > (DefaultPluginVersionManager.java:94) > at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin( > DefaultPluginManager.java:461) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin( > DefaultLifecycleExecutor.java:1135) > ... 19 more > [INFO] > > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Nov 15 07:57:56 CET 2005 > [INFO] Final Memory: 1M/4M > [INFO] > > > > 2005/11/14, Brett Porter <[EMAIL PROTECTED]>: > > > > Neither of these should be required with the current version, though > > I'm not sure when it was last released. At worst you only need the > > first and it should be added to the clover plugin definition, not a > > general dependency. > > > > The clover DB is also not required as that is the default. > > > > Wim, any more details on why the plugin was "not found"? > > > > - Brett > > > > On 11/15/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote: > > > i forgot that i also added this in my dependency: > > > > > > > > > clover > > > clover > > > 1.3.5 > > > > > > > > > maven > > > maven-clover-plugin > > > 1.8 > >
[m2] using the mboot2 stuff in our own plugins
Hi all, We are writing a FindBugs plugin for maven 2 right now and it is failing when we run it within the maven2 environment, but when run atandalone it works fine. So we are exploring how we'd run it from maven but as a standalone app. Looking at the source for the surefire plugin we've seen that it makes use of objects from the maven-mboot2 plugin (is that actually a plugin?) and in fact mboot2 contains the SurefireBooter. There is a class there called MBoot and a few other classes that look like they'd be very handy for us to use. Are there any issues with depending on mboot2 we should be aware of? Does anyone have any other advice on writing a plugin that needs to run in its own VM? Kind regards, Dave Sag
Re: Users List configuration
I utterly sympathise with Blaise on this. I joined this list because I found the web-archive of the list to be unsearchable and, if i must say like most apache list archives, pretty much useless. So I just put up with the flood and get lotus notes to try to filter it for me (a big ask as notes is crap at filtering, (and most things)). What is this nabble of which you speak Brett? Do you have a URL? Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 12-11-2005 12:55:50: > No, that's not possible - maybe one of the web archives (nabble?) > allows you to subscribe to your own topics for updates? > > - Brett > > On 11/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I have a question concerning this Users List. Maybe it's a stupid > question ;-) , > > but I have to answer it. > > > > Indeed, I have subscribed to this mailing list four days ago, and since that > > moment I receive all the mails sent by every users. > > > > Isn't it possible to receive only the mail in response to my own > subjects, as I > > can go on the Internet site to see the others subjects ? > > > > Thanks in advance. > > _ _ _ _ > > bgOnline > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Documentation -- making better use of the wiki
+1 Kind regards, Dave Sag Alexander Hars <[EMAIL PROTECTED]> wrote on 11-11-2005 10:42:58: > Hi, > > I have been using Maven2 for two weeks and am very impressed by all the > great features. > > However, the learning curve is steep and it is often very difficult to > find certain answers (I often need to > to look at the source code to find them). Whenever I find an answer to a > question, I alone have learned. > Others don't profit. I would be quite willing to submit an answer to > Maven2 for inclusion into the guides. But that takes > quite a bit of time (...going into CVS, downloading the apt file, > modifying it, testing it, submitting it to someone for posting > to the CVS etc.). I did that once, but we can't expect big progress in > the documentation to occur this way. > > The only solution that does not overload the developers (who put in so > much time already anyhow), is to make better use > of the wiki because everybody can contribute and increase our cumulated > knowledge. But just providing the wiki as > it is now (http://wiki.apache.org/maven/Maven2Info) does not work. There > is almost nothing there, almost nobody > goes to it, therefore few people add anything either. > > There are two practical ways in which we could make better use of the wiki: > > a) provide a prominent link from the Maven2 documentation (guides, > miniguides, references, etc.) to a related wiki > page. Anyone who has some insight to add to the documentation can place > it there; anyone who has not found the > answer in the standard documentation can easily check whether there is > more information in the wiki. From time > to time someone can integrate the bulk of good insights from the wiki > back into the documentation. > > b) put most of the documentation into the wiki. In my opinion this is > the ideal case, because it would reduce the > load on the developers for providing the documentation and there would > be a single documentation mechanism. > But it is probably not practical because the Maven Wiki is not based on > the .apt format and integration with the > maven site generation mechanism may be difficult. > > Option a) is very easy to do. We would only need to create associated > wiki pages and insert a link to the wiki > page from the original documentation. I am sure that we could greatly > expand the Maven-related knowledge > this way. > > I certainly would be willing to work on the necessary changes to get > this rolling if you think this is a good idea. > > - Alexander Hars > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: how to create a site in maven 2
On a related topic, We plan on using Continuum to do our regular builds and as part of that I want it to generate the project site on each build. Now, as far as I can see, none of the standard lifecycle phases include site generation. How are other people generating their project sites using maven 2 and continuum? Kind regards, Dave Sag Paul Spencer <[EMAIL PROTECTED]> wrote on 11-11-2005 10:22:12: > 1) cd to the project directory. It will contain the file pom.xml. > > 2) execute the following command to generate the site. > mvn site > > 3) The site will be created in the target directory > target/docs/index.html > Paul Spencer > > > Maruf Aytekin wrote: > > Hello All, > > I am pretty new to maven just trying it for my company. I hve a problem > > with creating site. I know that it'd be something so simple. Apologies > > for taking your time. My problem is following; > > > > I first created a maven project amqxtras with the following command > > C:\TestMaven> mvn archetype:create -DgroupId=com.idds.amqxtras > > -DartifactId=amqxtras > > This created a maven project under amqxtras directory. > > > > When I ran the following to generate site documentation > > C:\TestMaven>mvn archetype:create -DgroupId=com.idds.amqxtras > > -DartifactId=amqxtras -DarchetypeGroupId=org.apache.maven.archetypes > > -DarchetypeArtifactId=maven-archetype-site > > > > I got the following error that amqxtras already exist. What do I do > > wrong? > > > > > > --- > > [ERROR] BUILD ERROR > > [INFO] > > > > - > > --- > > [INFO] amqxtras already exists - please run from a clean directory > > [INFO] > > > > - > > --- > > [INFO] For more information, run Maven with the -e switch > > [INFO] > > > > - > > --- > > [INFO] Total time: 1 second > > [INFO] Finished at: Fri Nov 11 10:52:47 EET 2005 > > [INFO] Final Memory: 3M/7M > > [INFO] > > > > - > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: CheckStyle html report contains no source link
Unfortunately our firewalls here don't let me checkout the source from subversion servers that are not on https, so in this case I would need to go home, use my laptop to check out the source, build it there and then manually copy the jars to my windoze box at work. It would be easier for me, and anyone else where I work, if the update could just be released, as it clearly was fixed weeks ago. Isn't one of the points of using something like continuum that you can release nightly snapshot releases? It does make me wonder about other developers - the main issues i have with m2 are this javadoc bug, the lack of plugins for the standards code-quality tools, lack of support for the assert statement, and the obviously broken PMD and checkstyle plugins. All of this seems to indicate that formal code quality is not a concern for the majority of developers. Kind regards, Dave Sag Rik Bosman <[EMAIL PROTECTED]> wrote on 11-11-2005 09:16:35: > David, > The simplest solution before the release of Maven 2.0.1 is to download the > newest release yourself: > Actually it is quite simple: > - Download SVN (if not already on your machine) > - Checkout the maven source tree. "svn checkout > http://svn.apache.org/repos/asf/maven/components/trunk/ maven-site" > - Find the plugins directory, drill down to maven-javadoc > - Run the mvn commands "mvn compile" and "mvn install". > - The newest plugin is automatically added to your repository. > --rik > > 2005/11/11, David Sag <[EMAIL PROTECTED]>: > > > > > > I'm quite amazed that this long-standing bug with the javadoc plugin > > hasn't been addressed sooner. I know it's been fixed but is there a problem > > with actually releasing the fixed javadoc plugin? It's quite embarrassing > > giving demos of maven 2 and having to constantly explain that "this blank > > page is where the javadocs would be but for a bug." Or is javadoc generation > > a very very low priority for most developers? > > > > Kind regards, > > Dave Sag > > > > > > > > > > > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 11-11-2005 05:12:23: > > > > > The fix will occur when the next javadoc plugin release is made. It > > > isn't currently scheduled. > > > > > > I'm not sure if the checkstyle plugin is correctly linking them - you > > > might need to file a bug. > > > > > > - Brett > > > > > > On 11/11/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > > > Brett, > > > > The plugin is working, the sources were generated. > > > > But still no links in the generated checkstyle report. Any > > suggestions? > > > > Another question: I read about the problem with the empty javadoc " > > > > index.html". > > > > The solution would be in maven 2.0.1. for what date is this release > > planned? > > > > --rik > > > > > > > > 2005/11/10, Brett Porter <[EMAIL PROTECTED]>: > > > > > > > > > > groupId = org.codehaus.mojo > > > > > artifactId = jxr-maven-plugin > > > > > > > > > > it is still in beta. > > > > > > > > > > On 11/10/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > I want to use maven2 to generate some reports (e.g. mvn site) to > > check > > > > > code > > > > > > produced by a company working for us in India. Generating the > > reports > > > > > for > > > > > > pmd and checkstyle goes pretty straightforward, but the html links > > (the > > > > > > mentioned line should be a link) are missing. I saw this feature > > in some > > > > > > examples which I found on the Internet. > > > > > > How could this be done? > > > > > > Currenty I only have a simple pom.xml with only 2 plugins. Do I > > need > > > > > > another plugin to generate the (xref?) sources? Where can > > thisplugin be > > > > > > found? > > > > > > Thanks a lot. > > > > > > Rik > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: CheckStyle html report contains no source link
I'm quite amazed that this long-standing bug with the javadoc plugin hasn't been addressed sooner. I know it's been fixed but is there a problem with actually releasing the fixed javadoc plugin? It's quite embarrassing giving demos of maven 2 and having to constantly explain that "this blank page is where the javadocs would be but for a bug." Or is javadoc generation a very very low priority for most developers? Kind regards, Dave Sag Brett Porter <[EMAIL PROTECTED]> wrote on 11-11-2005 05:12:23: > The fix will occur when the next javadoc plugin release is made. It > isn't currently scheduled. > > I'm not sure if the checkstyle plugin is correctly linking them - you > might need to file a bug. > > - Brett > > On 11/11/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > Brett, > > The plugin is working, the sources were generated. > > But still no links in the generated checkstyle report. Any suggestions? > > Another question: I read about the problem with the empty javadoc " > > index.html". > > The solution would be in maven 2.0.1. for what date is this release planned? > > --rik > > > > 2005/11/10, Brett Porter <[EMAIL PROTECTED]>: > > > > > > groupId = org.codehaus.mojo > > > artifactId = jxr-maven-plugin > > > > > > it is still in beta. > > > > > > On 11/10/05, Rik Bosman <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I want to use maven2 to generate some reports (e.g. mvn site) to check > > > code > > > > produced by a company working for us in India. Generating the reports > > > for > > > > pmd and checkstyle goes pretty straightforward, but the html links (the > > > > mentioned line should be a link) are missing. I saw this feature in some > > > > examples which I found on the Internet. > > > > How could this be done? > > > > Currenty I only have a simple pom.xml with only 2 plugins. Do I need > > > > another plugin to generate the (xref?) sources? Where can thisplugin be > > > > found? > > > > Thanks a lot. > > > > Rik > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
built in project properties
Where can I find a doc on the built
in maven 2 pom properties such as ${project.build.directory}
specifically I need one that is the
project's base directory. ${project.directory} is not it apparently.
Kind regards,
Dave Sag
Re: JCOVERAGE for MAVEN 2
I do not put much stock in that matrix - it's not exactly accurate. Kind regards, Dave Sag stéphane bouchet <[EMAIL PROTECTED]> wrote on 08-11-2005 10:20:38: > Sorry for confusion, according to the maven 2 plugin matrix, > (http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix) the cobertura > plugin is in dev for maven2. > > Stéphane > > > David Sag a écrit : > > There is no maven 2 plugin for cobertura according to the developers. > > > > dave > > > > > > REBOISSON Eric <[EMAIL PROTECTED]> wrote on 08-11-2005 09:46:48: > > > > > >>I tried to use Cobertura but this error appears , why ? How to resolve > > > > it ? > > > >>: > >> > >>D:\Documents and Settings\reboisse\workspace\DataModel>mvn > > > > cobertura:report > > > >>[INFO] Scanning for projects... > >>[INFO] Searching repository for plugin with prefix: 'cobertura'. > >>Downloading: > >>http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.pom > >>150b downloaded > >>Downloading: > >>http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.jar > >>80K downloaded > >>[INFO] > >> > > > > > > > >>[ERROR] FATAL ERROR > >>[INFO] > >> > > > > > > > >>[INFO] null > >>[INFO] > >> > > > > > > > >>[INFO] Trace > >>java.lang.NullPointerException > >> at > >> > > > > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. > > > >>java:292) > >> at > >> > > > > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl > > > >>uginManager.java:198) > >> at > >> > > > > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag > > > >>er.java:163) > >> at > >> > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife > > > >>cycleExecutor.java:1095) > >> at > >> > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul > > > >>tLifecycleExecutor.java:1305) > >> at > >> > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega > > > >>tionNeeds(DefaultLifecycleExecutor.java:376) > >> at > >> > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle > > > >>Executor.java:132) > >> at > > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > > > >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> at > >> > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 > > > >>) > >> at > >> > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl > > > >>.java:25) > >> at java.lang.reflect.Method.invoke(Method.java:585) > >> 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) > >>[INFO] > >> > > > > > > > >>[INFO] Total time: 8 seconds > >>[INFO] Finished at: Tue Nov 08 09:45:42 CET 2005 > >>[INFO] Final Memory: 1M/3M > >>[INFO] > >> > > > > > > > >>D:\Documents and Settings\reboisse\workspace\DataModel> > >> > >>-Message d'origine- > >>De : stéphane bouchet [mailto:[EMAIL PROTECTED] > >>Envoyé : lund
RE: JCOVERAGE for MAVEN 2
There is no maven 2 plugin for cobertura according to the developers. dave REBOISSON Eric <[EMAIL PROTECTED]> wrote on 08-11-2005 09:46:48: > I tried to use Cobertura but this error appears , why ? How to resolve it ? > : > > D:\Documents and Settings\reboisse\workspace\DataModel>mvn cobertura:report > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'cobertura'. > Downloading: > http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.pom > 150b downloaded > Downloading: > http://repo1.maven.org/maven2/cobertura/cobertura/1.4/cobertura-1.4.jar > 80K downloaded > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager. > java:292) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPl > uginManager.java:198) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManag > er.java:163) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLife > cycleExecutor.java:1095) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul > tLifecycleExecutor.java:1305) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega > tionNeeds(DefaultLifecycleExecutor.java:376) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle > Executor.java:132) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 > ) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Tue Nov 08 09:45:42 CET 2005 > [INFO] Final Memory: 1M/3M > [INFO] > > > D:\Documents and Settings\reboisse\workspace\DataModel> > > -Message d'origine- > De : stéphane bouchet [mailto:[EMAIL PROTECTED] > Envoyé : lundi 7 novembre 2005 17:28 > À : Maven Users List > Objet : Re: JCOVERAGE for MAVEN 2 > > > Jcoverage is a commercial tool, prefer cobertura. > > the plugin for maven2 is still in dev. > > http://maven-plugins.sourceforge.net/maven-cobertura-plugin/ > > STéphane > > > REBOISSON Eric a écrit : > > Is there a JCOVERAGE plugins for maven 2 ? > > > > How to install it if it exists ? > > > > Thanks > > > > Eric > > > > __ > > > > Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et > établi à l'intention exclusive de ses destinataires. Toute utilisation de ce > message non conforme à sa destination, toute diffusion ou toute publication, > totale ou partielle, est interdite, sauf autorisation expresse. L'IFP > décline toute responsabilité au titre de ce message. > > > > This message and any attachments (the message) are confidential and > intended solely for the addressees. Any unauthorised use or dissemination is > prohibited. IFP should not be liable for this message. > > > > Visitez notre site Web / Visit our web site : http://www.ifp.fr > > __ > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] config of goals
Further to this, I have posted an issue in JIRA
http://jira.codehaus.org/browse/MNG-1446
Unable to config goals that are not bound to part of the standard
lifecycle
cheers
dave
David Sag <[EMAIL PROTECTED]> wrote on 07-11-2005 08:50:51:
>
> I am having real problems getting my plugin config to work.
>
> Here's my use case:
>
> a developer compiles and as part of her build checkstyle must be run
> and fail a build on any checkstyle errors.
> this is easy and works fine.
>
> but within the same pom.xml file
>
> Continuum needs to build everything and, whether the build fails or
> not, needs to then run the qalab plugin's merge goal with specific
> config telling it to use the results generated by checkstyle.
>
> the QALab plugin has three different goals and only a few of their
> config params are in common with each other. so each goal must have
> its own config.
>
> So right now, for simplicity's sake, I just want the qalab:merge goal to
work.
>
> my build section is as follows:
>
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.4
> 1.4
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> 1.4
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
> xml
> true
>
>
>
> check-main-src
> compile
>
> ${project.build.directory}
> /checkstyle-result.xml
>
>
>checkstyle
>
>
>
>
>
> net.objectlab
> maven-qalab-plugin
>
>
>
> net.objectlab.qalab.parser.
> CheckstyleStatMerge
> ${project.build.directory}
> /checkstyle-result.xml
>
>
>merge
>
>
>
>
>
>
>
> the checkstyle plugin works fine but when I try
>
> %mvn qalab:merge
>
> i get
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] One or more required plugin parameters are invalid/missing
> for 'qalab:merge'
>
> [0] inside the definition for plugin: 'maven-qalab-plugin'specify
> the following:
>
>
> ...
> VALUE
> .
>
> [1] inside the definition for plugin: 'maven-qalab-plugin'specify
> the following:
>
>
> ...
> VALUE
> .
>
> if i move the config from the executions block such that it is like so:
>
>
> net.objectlab
> maven-qalab-plugin
>
> net.objectlab.qalab.parser.CheckstyleStatMerge
> ${project.build.directory}/checkstyle-result.
> xml
>
>
>
> then the params are accepted, but now I can't have different params
> for the different goals, indeed i can't see how i'd go about
> specifying different configs for the different goals in such a case.
> I need goal specific parameter config, not plugin-wide config. or
> should I make these goals into totally different plugins instead?
>
> cheers
>
> dave
>
> Kind regards,
> Dave Sag
>
>
> [image removed]
>
>
[m2] config of goals
I am having real problems getting my
plugin config to work.
Here's my use case:
a developer compiles and as part of
her build checkstyle must be run and fail a build on any checkstyle errors.
this is easy and works fine.
but within the same pom.xml file
Continuum needs to build everything
and, whether the build fails or not, needs to then run the qalab plugin's
merge goal with specific config telling it to use the results generated
by checkstyle.
the QALab plugin has three different
goals and only a few of their config params are in common with each other.
so each goal must have its own config.
So right now, for simplicity's sake,
I just want the qalab:merge goal to work.
my build section is as follows:
org.apache.maven.plugins
maven-compiler-plugin
1.4
1.4
org.apache.maven.plugins
maven-javadoc-plugin
1.4
org.apache.maven.plugins
maven-checkstyle-plugin
xml
true
check-main-src
compile
${project.build.directory}/checkstyle-result.xml
checkstyle
net.objectlab
maven-qalab-plugin
net.objectlab.qalab.parser.CheckstyleStatMerge
${project.build.directory}/checkstyle-result.xml
merge
the checkstyle plugin works fine but
when I try
%mvn qalab:merge
i get
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters
are invalid/missing for 'qalab:merge'
[0] inside the definition for plugin:
'maven-qalab-plugin'specify the following:
...
VALUE
.
[1] inside the definition for plugin:
'maven-qalab-plugin'specify the following:
...
VALUE
.
if i move the config from the executions
block such that it is like so:
net.objectlab
maven-qalab-plugin
net.objectlab.qalab.parser.CheckstyleStatMerge
${project.build.directory}/checkstyle-result.xml
then the params are accepted, but now
I can't have different params for the different goals, indeed i can't see
how i'd go about specifying different configs for the different goals in
such a case. I need goal specific parameter config, not plugin-wide
config. or should I make these goals into totally different plugins
instead?
cheers
dave
Kind regards,
Dave Sag
Re: [m2] does a plugin bound to a phase execute before or after that phase?
by that do you mean that it's random and so sometimes checkstyle might run before the compile and sometimes after? that's a strange architectural decision dave "Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 04-11-2005 13:46:29: > m2 collect all plugins bound in a specific phase and run them one by one > without a specific order. > > David Sag said: > > That's interesting. To try this I bound checkstyle to my compile phase > > and lo - the compile happened and then checkstyle ran. You are saying > > that checkstyle should have run "in the phase"... what does that mean > > exactly? Compilation is a pretty discrete process so I don't see how or > > why checksyle would run while the compile is happening. > > > > In answer to your question, I want my plugin to run once the source files > > have been processed, but before any resources are generated. > > > > dave > > > > > > "Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 04-11-2005 13:20:27: > > > >> it run in the phase. > >> All plugin bound to a phase will be run in this phase without order. > >> > >> why do you want to run it between this two phases? > >> > >> Emmanuel > >> > >> David Sag said: > >> > Hi there, > >> > > >> > I want my plugin to run after the process-sources phase, and before > > the > >> > generate-resources phase. if i bind it to the process-sources phase > > will > >> > it run after that or before it? > >> > > >> > dave > >> > > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] does a plugin bound to a phase execute before or after that phase?
That's interesting. To try this I bound checkstyle to my compile phase and lo - the compile happened and then checkstyle ran. You are saying that checkstyle should have run "in the phase"... what does that mean exactly? Compilation is a pretty discrete process so I don't see how or why checksyle would run while the compile is happening. In answer to your question, I want my plugin to run once the source files have been processed, but before any resources are generated. dave "Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 04-11-2005 13:20:27: > it run in the phase. > All plugin bound to a phase will be run in this phase without order. > > why do you want to run it between this two phases? > > Emmanuel > > David Sag said: > > Hi there, > > > > I want my plugin to run after the process-sources phase, and before the > > generate-resources phase. if i bind it to the process-sources phase will > > it run after that or before it? > > > > dave > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] does a plugin bound to a phase execute before or after that phase?
Just to answer my own question, and to help others who are wondering the same thing, I just tried it and the plugin runs *after* the phase it has been bound to. dave David Sag <[EMAIL PROTECTED]> wrote on 04-11-2005 12:57:08: > Hi there, > > I want my plugin to run after the process-sources phase, and before the > generate-resources phase. if i bind it to the process-sources phase will > it run after that or before it? > > dave
[m2] does a plugin bound to a phase execute before or after that phase?
Hi there, I want my plugin to run after the process-sources phase, and before the generate-resources phase. if i bind it to the process-sources phase will it run after that or before it? dave
Re: [ANN][M1] Findbugs 1.0 Release
Fantastic - any word on a maven 2 version? Kind regards, Dave Sag Eric Pugh <[EMAIL PROTECTED]> wrote on 02/11/2005 03:30:32 PM: > The maven-plugins team is pleased to announce the FindBugs Plug-in 1.0 > release! > > http://maven-plugins.sourceforge.net/maven-findbugs-plugin > > A plugin to automate FindBugs tasks > > Changes in this version include: > > Fixed bugs: > > o Sample findbugs report didn't have xref source to link to. Issue: > 1078970. > o FindBugs does not xref to source of inner classes correctly. Issue: > 1194218. Thanks to John Whaley. > o Use libraries as dependencies instead of bundle them. > > Changes: > > o Switch from naming Maven Findbugs releases after Findbugs versions > to using > a sequence just for Maven Findbugs Plugin. > o Upgrade to findbugs 0.9.3. > > To automatically install the plugin, type the following on a single > line: > > maven plugin:download > -DgroupId=maven-plugins > -DartifactId=maven-findbugs-plugin > -Dversion=1.0 > > For a manual installation, you can download the plugin here: > http://maven-plugins.sourceforge.net/repository/maven-plugins/plugins/ > maven-findbugs-plugin-1.0.jar > > > Have fun! > -The maven-plugins team > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: [M2] checkstyle
che.maven: > maven-model:jar:2.0 > [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for > runtime > ) > [DEBUG] Retrieving parent-POM from the repository for project: > org.apache.maven: > maven-artifact-manager:jar:2.0 > [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected > for runt > ime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for > runtime > ) > [DEBUG] > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (se > lected for runtime) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for > runtime) > [DEBUG] Retrieving parent-POM from the repository for project: > org.apache.maven: > maven-repository-metadata:jar:2.0 > [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 > (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected > for runti > me) > [DEBUG] > org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selec > ted for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected > for runti > me) > [DEBUG] Retrieving parent-POM from the repository for project: > null:maven-profil > e:jar:2.0 > [DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for > runtime > ) > [DEBUG] > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (se > lected for runtime) > [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for > runtime) > [DEBUG] Retrieving parent-POM from the repository for project: > null:maven-report > ing-api:jar:2.0 > [DEBUG] Retrieving parent-POM from the repository for project: > org.apache.maven. > reporting:maven-reporting:pom:2.0 > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0 > (selected for > runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4 (selected for > runtime) > [DEBUG] commons-validator:commons-validator:jar:1.1.4 (selected for > runtime) > > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for > runtime) > [DEBUG] oro:oro:jar:2.0.7 (selected for runtime) > [DEBUG] doxia:doxia-core:jar:1.0-alpha-4 (selected for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4 (selected for > runtime) > [DEBUG] oro:oro:jar:2.0.7 (selected for runtime) > [DEBUG] antlr:antlr:jar:2.7.2 (selected for runtime) > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-checkstyle-plugin:2.0-b > eta-1:checkstyle' --> > [DEBUG] (f) cacheFile = > C:\m2Projects\configuration-module\app-config\target/c > heckstyle-cachefile > [DEBUG] (f) failsOnError = true > [DEBUG] (f) format = sun > [DEBUG] (f) headerFile = > C:\m2Projects\configuration-module\app-config\LICENSE > .txt > [DEBUG] (f) includes = **/*.java > [DEBUG] (f) outputDirectory = > C:\m2Projects\configuration-module\app-config\ta > rget\site > [DEBUG] (f) outputFile = > C:\m2Projects\configuration-module\app-config\target/ > checkstyle-result.txt > [DEBUG] (f) outputFileFormat = plain > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) propertiesFile = > C:\m2Projects\configuration-module\app-config\src > \config\siebel_check.xml > [DEBUG] (f) sourceDirectory = > C:\m2Projects\configuration-module\app-config\sr > c\main\java > [DEBUG] -- end configuration -- > [INFO] [checkstyle:checkstyle] > > _ > > From: David Sag [mailto:[EMAIL PROTECTED] > Sent: Monday, October 24, 2005 3:45 AM > To: Maven Users List > Subject: Re: [M2] checkstyle > > > > Here's an extract from my pom.xml where i apply different checkstyle > rules to my main src and my test code. > > > > > org.apache.maven.plugins > maven-checkstyle-plugin > > > check-main-src > compile > > > checkstyle-src.xml > true > > > checkstyle > > > > check-test-src > test-compile > > > checkstyle-test.xml > true > src/test > > > checkstyle > > > >
[m2] specifying a specific plugin goal in a report.
As part of generating a QALab report i need to run my qalab plugin's merge goal. I have tried adding my qalab plugin to the reporting section of my pom but i can't see how i specify which goal to actually run? i tried adding an ... section but that's not allowed. hints or outright telling me both welcomed. Kind regards, Dave Sag
Re: [m2] writing a Mojo for a plugin that requires Reports to have been run
Done. see http://jira.codehaus.org/browse/MNG-1298
Kind regards,
Dave Sag
Brett Porter <[EMAIL PROTECTED]>
21/10/05 09:51 PM
Please respond to
"Maven Users List"
To
Maven Users List
cc
Subject
Re: [m2] writing a Mojo for a plugin
that requires Reports to have been run
I see. This capability is not really available right
now other than by
correctly ordering them in the POM. Please file a JIRA issue.
-Brett
On 10/19/05, David Sag <[EMAIL PROTECTED]> wrote:
>
>
> Hmm sorry we seem to be t cross-purposes here.
>
> All I want to do is to ensure that the various reports have been run.
I
> don't need to access the liost of registered reports specifically.
unless i
> suppose i wish to check from within my mojo that the other reports
have been
> run. i am probably just failing to understand you properly.
>
> Kind regards,
> Dave Sag
>
>
>
>
>
>
> Brett Porter <[EMAIL PROTECTED]> wrote on 20/10/2005 03:09:30
AM:
>
> > It's not a dummy parameter, it's the parameter that will give
you the
> > reports. Without it, how do you hope to access the list of registered
> > reports at all?
> >
> > - Brett
> >
> > On 10/18/05, David Sag <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > What I need is acccess to the various checkstyle (etc) reports
in an
> xml
> > > format.
> > >
> > > what you describe below doesn't seem appropriate to me.
My parameters
> > > already have various expressions and default values but
i do need to
> ensure
> > > that the checkstyle (etc) plugins have already been run,
before
> myplugin is
> > > run.
> > >
> > > requiresReports is a goal-wide setting, not specific to
a parameter,
> so i
> > > guess what i am assking is
> > >
> > > 1) what is that tag actually for
> > > 2) how to set it to true
> > >
> > > if you are saying that to set that tag to true i need to
create a
> dummy
> > > parameter with @parameter _expression_="${reports}"
set then i really
> feel
> > > that's a very stupid hack.
> > >
> > > why not just let me set @requiresReports in the very top
of my mojo
> where
> > > the @goal, @phase and @requiresDependencyResolution tags
live.
> > >
> > > Kind regards,
> > > Dave Sag
> > >
> > >
> > >
> > >
> > >
> > >
> > > Brett Porter <[EMAIL PROTECTED]> wrote on 18/10/2005
04:58:26 AM:
> > >
> > > > You need to use the reports, so declare:
> > > >
> > > > @parameter _expression_="${reports}"
> > > >
> > > > That will trigger it. But are you sure you relly need
access to the
> > > reports?
> > > > That's generally only for the site plugin.
> > > >
> > > > The aggregator tag causes the mojo not to be run for
subprojects,
> > > instead it
> > > > is run at the root and you have access to ${reactorProjects}
> > > >
> > > > On 10/17/05, David Sag <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I am writing an M2 plugin for QALab. QALab aggregates
the reports
> from
> > > > > other plugins such as checkstyle etc.
> > > > >
> > > > > In my plugin.xml file there is a tag
> > > > > false
and so I guessed that
> setting
> > > > >
> > > > > @requiresReports
> > > > >
> > > > > at the to of my Mojo would change this flat to
true when i
> regenerate
> > > the
> > > > > plugin.xml file. but it does not.
> > > > >
> > > > > also while I am at it, I am curious as to the
role of the
> aggregator
> > > tag
> > > > >
> > > > > Kind regards,
> > > > > Dave Sag
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
>
Re: [M2] checkstyle
Here's an extract from my pom.xml where i apply different checkstyle rules to my main src and my test code. org.apache.maven.plugins maven-checkstyle-plugin check-main-src compile checkstyle-src.xml true checkstyle check-test-src test-compile checkstyle-test.xml true src/test checkstyle however, as this jira issue (and my own experience) makes plain, right now the propertiesFile is ignored so you'll have to put up with the default for a while until they fix this, or apply the patch yourself. http://jira.codehaus.org/browse/MNG-1113 Kind regards, Dave Sag "Mark Kuzmycz" <[EMAIL PROTECTED]> wrote on 22/10/2005 07:24:03 PM: > How do I specify a customized checkstyle format. The source code for the > checkstyle report suggests that it only knows about sun, turbine and > avalon. > > Regards, > Mark. > > ___ > Siebel > IT'S ALL ABOUT THE CUSTOMER > Visit www.siebel.com > > This e-mail message is for the sole use of the intended recipient(s) > and contains confidential and/or privileged information belonging to > Siebel Systems, Inc. or its customers or partners. Any unauthorized > review, use, copying, disclosure or distribution of this message is > strictly prohibited. If you are not an intended recipient of this > message, please contact the sender by reply e-mail and destroy all > soft and hard copies of the message and any attachments. Thank you > for your cooperation.
[m2] clover plug-in fails when it encounters asserts.
I've mentioned this before, and filed an issue in Jira, an the fix has been explained in Jira but somehow it's never made it into the release of v2 I'm just bringing it up again in the hope that someone out these cares enough to perhaps visit the issue and vote for it - and thus it may get the attention of a developer. http://jira.codehaus.org/browse/MNG-1136 a question: how many developers on this list actually use assertions code quality tools like PMD, FindBugs, Emma, Simian, QALab etc Kind regards, Dave Sag
Re: [m2] javadoc plugin
Would you like to add your fix to the
bug report in Jira?
http://jira.codehaus.org/browse/MNG-1249
Kind regards,
Dave Sag
Samuel Le Berrigaud <[EMAIL PROTECTED]> wrote
on 21/10/2005 12:54:02 PM:
> Hi,
>
> there is a bug in the current javadoc plugin regarding the site
> integration. The link to the javadoc leads to blank page.
>
> The javadoc is correctly generated, however the index page of the
> javadoc is overwritten by a blank index page.
>
> I found the bug come from the JavadocReport class of the plugin, this:
>
> public String getOutputName()
> {
> return "apidocs/index";
> }
>
> give the plugin its incorrect behavior.
>
> I corrected this to :
>
> public String getOutputName()
> {
> return "javadoc";
> }
>
> And I add the following document to my src/site/apt directory:
>
> --
> Javadoc
>
> You can find the javadoc at {{{apidocs/index.html}apidocs/index.html}}
> --
>
> This can obviously not be a premanent solution but it works fine for
> me for now.
> I don't know how to integrate this simple APT page into the plugin
> directly, if anyone has any hint for me. I would glad to put some
> effort on this and the contribute creating a JIRA bug and providing
a
> first patch maybe...
>
> Thanks,
>
> --
> Samuel Le Berrigaud
