Re: Dashboard plugin
to do what ? you want a snapshot report or the full report with historical graph ? canerK wrote: Is it possible to generate the dashboard plugin report in just one pass?What i want to achieve is:generating the report by executing only mvn site dashboard:dashboard site:deploy command -- View this message in context: http://old.nabble.com/Dashboard-plugin-tp26692812p26693841.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dashboard plugin
It's not possible to generate dashboard report in one pass. The problem is that you must generate all others reports to aggregate them. so you must do it in 2 passes : - mvn site - mvn dashboard:dashboard site:deploy it's the only way to do it canerK wrote: Hi, Thanks for the reply. We have a multi-module maven project and we want an aggregated report containing information about all submodules.The name of the report we want is :Global DashBoard Report and we dont need the historical graph attribute now. dvicente wrote: to do what ? you want a snapshot report or the full report with historical graph ? canerK wrote: Is it possible to generate the dashboard plugin report in just one pass?What i want to achieve is:generating the report by executing only mvn site dashboard:dashboard site:deploy command -- View this message in context: http://old.nabble.com/Dashboard-plugin-tp26692812p26695400.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: commons-loging issue
Hi Mick, it's a known issue since Maven 2.0.9. See the FAQ page to resolve this problem : http://mojo.codehaus.org/dashboard-maven-plugin/faq.html Best Regards David Vicente mickknutson wrote: I have found several issues like: http://jira.codehaus.org/browse/MOJO-1118 But I am NOT able to find a working solution. The basic fact is that as soon as I add the artifactIdmaven-dashboard-plugin/artifactId and try to run dashboard:dashboard, I get this error: *These will use the artifact files already in the core ClassRealm instead, to allow them to be included in PluginDescriptor.getArtifacts(). [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. [INFO] [DEBUG] Trace java.lang.ExceptionInInitializerError at org.codehaus.mojo.dashboard.report.plugin.hibernate.HibernateServiceImpl.initialize(HibernateServiceImpl.java:116) * Help would be appreciated to get the dashboard working --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- -- View this message in context: http://www.nabble.com/commons-loging-issue-tp23491161p23497027.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JDepend Reporting Plugin in a Multi-Module Project
Hi, the problem with JDepend plugin is : All design quality metrics are computed into a single project, not with other modules which could use this first project. So the Afferent and Efferent Couplings metrics are distorted with this problem. The dashboard plugin cannot resolve this lack. Brad Harper wrote: Does anyone have experience running the JDepend reporting plugin in a multi-module project? We've been able to successfully run the subject plugin [via site:site] in individual projects with packaging types of jar and war, but when performing mvn jdepend:generate in the top-level project [which contains no source of its own], the plugin fails with ... [INFO] [jdepend:generate] Directory does not exist: c:\workspace\dev\target\classes ... Ultimately, the goal is to run 'site:site' for the top-level project [which would run JDepend and other reporting plugins], followed by 'dashboard:dashboard'. BTW, there isn't any configuration info http://mojo.codehaus.org/jdepend-maven-plugin/. Thanks. Brad - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/JDepend-Reporting-Plugin-in-a-Multi-Module-Project-tp20980649p21011352.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven dashboard plugin problem
Hi, can you do a mvn dashboard:persist -e -Xmaven.log and send the log as attachment ? it's possible that the hibernate version (3.2.2) used in the dashboard is not compatible with Oracle XE pdurbha wrote: Hi, I am trying to use the maven-dashboard-plugin to store and display build metrics on the dashboard application from an Oracle XE database..but the metrics are not getting stored in the OracleXE database.. Isn't the maven-dashboard-pulgin compatible with the Oracle XE database? The architecture in the link below doesn't specify the kind of database.. http://mojo.codehaus.org/dashboard-maven-plugin/ Please advise. Thanks -- View this message in context: http://www.nabble.com/maven-dashboard-plugin-problem-tp20909443p20910353.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Reporting - DashBoard-Maven-Plugin
Hi all, as described in dashboard documentation : http://mojo.codehaus.org/dashboard-maven-plugin/ you must add this in your pom.xml or settings.xml to use properly the dashboard plugin: pluginRepositories pluginRepository idCodehaus Snapshots/id url http://snapshots.repository.codehaus.org//url /pluginRepository /pluginRepositories But even if this configuration is well done, Maven doesn't recognize the mvn dashboard-report:dashboard command. and to work fine, you must run mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command instead of mvn dashboard-report:dashboard. See : http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html or http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html or http://jira.codehaus.org/browse/MOJO-899 In the project's beginning, i decided to modify the goal prefix to dashboard-report instead of the default's one by adding in the pom.xml of the dashboard plugin : ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build I think it's The Maven resolution problem of dashboard-report. Maven does not resolve properly the plugin prefix. it's for that : mvn dashboard-report:dashboard doesn't work correctly. For the next release , i will post a vote to users@maven.apache.org and [EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the default's one which works fine. After that, you will have to modify the goal prefix in your command line or Continuum goals to use the dashboard report : from dashboard-report:dashboard to dashboard:dashboard or from dashboard-report:persist to dashboard:persist Best Regards David Vicente SrinivasN wrote: I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Reporting - DashBoard-Maven-Plugin
Hi all, as described in dashboard documentation : http://mojo.codehaus.org/dashboard-maven-plugin/ you must add this in your pom.xml or settings.xml to use properly the dashboard plugin: pluginRepositories pluginRepository idCodehaus Snapshots/id url http://snapshots.repository.codehaus.org//url /pluginRepository /pluginRepositories But even if this configuration is well done, Maven doesn't recognize the mvn dashboard-report:dashboard command. and to work fine, you must run mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command instead of mvn dashboard-report:dashboard. See : http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html or http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html or http://jira.codehaus.org/browse/MOJO-899 In the project's beginning, i decided to modify the goal prefix to dashboard-report instead of the default's one by adding in the pom.xml of the dashboard plugin : ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build I think it's The Maven resolution problem of dashboard-report. Maven does not resolve properly the plugin prefix. it's for that : mvn dashboard-report:dashboard doesn't work correctly. For the next release , i will post a vote to users@maven.apache.org and [EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the default's one which works fine. After that, you will have to modify the goal prefix in your command line or Continuum goals to use the dashboard report : from dashboard-report:dashboard to dashboard:dashboard or from dashboard-report:persist to dashboard:persist Best Regards David Vicente SrinivasN wrote: I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin configuration
Hi, It's just a lack in the doc. as you can see in the default configuration file : https://svn.codehaus.org/mojo/trunk/sandbox/dashboard-maven-plugin/src/main/resources/config/default-dashboard-config.xml the dashboard supports the Findbugs plugin Best regards David Vicente Lee Meador-3 wrote: At this page http://mojo.codehaus.org/dashboard-maven-plugin/standard_config.html there is listed the standard dashboard configuration xml file. Is this up to date? I notice nothing in there about FindBugs. Where would one get a current one? (If that isn't it) Thanks. -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- View this message in context: http://www.nabble.com/Dashboard-plugin-configuration-tp15293488s177p15299733.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] when is the dashboard going to be out of snapshot?
Hi all, i'm the project leader of dashboard plugin. To release the dashboard, i must release the 2.0 JDepend plugin which is in snapshot version ( and i'm not the project leader of this plugin), i must correct 2 issues ( one with 1.9 cobertura problem and the new one with 2.4 surefire NPE). When all these will be ok, i will release. But as i already said to EN, i can't work on it at my job because i'm full and my personal computer has been robbed during my house's burglary. I 'm in progress to buy a new personal computer. I hope you understand the delay before having a release. Best regards David Vicente EN wrote: I had to file http://jira.codehaus.org/browse/MOJO-1023 also. I don't know if it will block 1.0 release, but it certainly blocks us from using surefire + dashboard :-( Erez. On Jan 30, 2008 2:20 AM, Mick Knutson [EMAIL PROTECTED] wrote: I voted for them... :-) On Jan 29, 2008 4:12 PM, Kalle Korhonen [EMAIL PROTECTED] wrote: The issue blocking the release of the dashboard plugin is the dependency to unreleased JDepend 2.0. What you can do - short of becoming a mojo developer yourself - is to vote for it to be fixed. The respective issues are: http://jira.codehaus.org/browse/MOJO-828 and http://jira.codehaus.org/browse/MOJO-829. I'm surprised there's so few votes so far even though many people seem to be using the dashboard. Kalle On 1/29/08, Erez Nahir [EMAIL PROTECTED] wrote: I'll second Mick, It is one of those good things that gives you the whole project's health picture up front without the need to digg into components and reports. Currently, there is an issue with latest surefire 2.4/testng 5.7preventing us from moving to surefire 2.4, but other then that (that I'm sure will be fixed soon ;-) way to go!! Erez. On Jan 29, 2008 9:14 PM, Mick Knutson [EMAIL PROTECTED] wrote: To the Dashboard developer: I love this plugin. It has really helped me push code quality onto my developers as I can display a great overview for management. The PM does not want to dig through each and every module to understand the current status and trend of our code. Thanks! On Jan 29, 2008 10:46 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Jan 29, 2008 11:35 AM, Mick Knutson [EMAIL PROTECTED] wrote: I am using the dashboard plugin but I can't use the release plugin because the dashboard is still snapshot. This one? http://mojo.codehaus.org/dashboard-maven-plugin/ It's a Codehaus plugin, so the right place to ask is on the Mojo Development list. Rather than just asking when it's going to be done, though, the developers might like to hear that you have successfully used it for X or Y -- i.e., give them some confidence that it's ready to be released. Checking JIRA might also give an idea of what's left to be done (whether there are any blocking issues) but I don't see a project for it on http://jira.codehaus.org/browse . You always have the option of doing an internal release to your organization's private repository, though it can be tedious to track down all the dependencies. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- -- View this message in context: http://www.nabble.com/-m2--when-is-the-dashboard-going-to-be-out-of-snapshot--tp15166209s177p15177225.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site.xml for dashboard reports?
Hi, as you can see under JIRA : http://jira.codehaus.org/browse/MOJO-700 MOJO-700 http://jira.codehaus.org/browse/MOJO-872 MOJO-872 it's not an excuse but all report plugins have the same behaviour. If you run mvn site, all works fine. But if you run any report plugin after mvn site, the skin and site.xml configuration are lost and replaced by the default one. the best would be that AbstractMavenReport does the job and thus all reports will inherit the same behavior. Best regards David Mick Knutson-4 wrote: I am running dashboard plugin for a multi-module project and find that all the reports do not seem to use my src/site/site.xml file for the reports. -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- -- View this message in context: http://www.nabble.com/-m2--site.xml-for-dashboard-reports--tp15024315s177p15036665.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] correct goal sequence for multimodule site generation
HI, The second 'site' run is apparently needed for the dashboard plugin : it's wrong. the site goal must be done completly before doing the dashboard, not twice. in your case : mvn clean install site mvn dashboard-report:dashboard mvn site:deploy or with historic graph mvn clean install site mvn dashboard-report:persist dashboard-report:dashboard mvn site:deploy that'all Best regards David jblack wrote: I have found conflicting guidance on which goals should be run to get a correct multimodule maven build to correctly produce all module site. Note that we use the cobertura and dashboard report plugins. Currently we do: mvn clean install site mvn site mvn site:deploy (The second 'site' run is apparently needed for the dashboard plugin) So is the 'install' goal even needed? Does anyone have better guidance on this? Using maven 2.0.7. -- View this message in context: http://www.nabble.com/-M2--correct-goal-sequence-for-multimodule-site-generation-tp14955602s177p14973599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard summary missing PMD and Cobertura sections
Hi Lee,
For Cobertura, your plugin configuration is commented, why ?
So far, only Cobertura 2.0 version is supported , so I advise you to
configure Cobertura as :
...
build
plugins
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0/version
executions
execution
goals
goalclean/goal
/goals
/execution
/executions
/plugin
/plugins
/build
...
reporting
plugins
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0/version
/plugin
/plugins
/reporting
and it must work.
For pmd and cpd, the problem is the aggregatetrue/aggregate parameter.
As described in the doc :
http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#aggregate
if you set the aggregate parameter to true, the pmd and cpd xml files are
only at the root project target directory.
But it isn't compatible with dashboard report, because the dashboard scan
each module to retreive xml files.
So delete this aggregatetrue/aggregate line, without this, each
module will have its own pmd and cpd xml files and the dashboard will be
able to aggregate values.
I hope it will help you
Lee Meador-3 wrote:
David,
I have sent the files you suggested by seperate email. If you have a
whitelist protecting your email from spam it might not get through to you.
Let me know.
Sorry to inflict this on the maven users list.
-- Lee
On Jan 4, 2008 1:44 PM, dvicente [EMAIL PROTECTED] wrote:
Could you post your pom.xml to see the reporting configuration ?
you can do a mvn -e -x dashboard-report:dashboardmaven.log and post
the
maven.log as attachment ?
Lee Meador-3 wrote:
1) The issue about the relocated XML files not being found was added
here
http://jira.codehaus.org/browse/MOJO-987
2) I noticed the issue already reported about the Cobertura columns not
appearing due to mixed Cobertura version. I suppose they are only
missing
in
the parent project's dashboard report.
3) Any ideas on why my PMD and CPD reports are not included on the
dashboard?
Thanks.
On Jan 4, 2008 2:16 AM, dvicente [EMAIL PROTECTED] wrote:
Hi,
i'm the dashboard's project leader.
It's true that the dashboard used the default location of output
directory
for each plugin.
I must resolve this problem.
Create an issue under http://jira.codehaus.org/browse/MOJO JIRA
David
Lee Meador-3 wrote:
How does the dashboard report plugin know whether to include the
various
summarized reports? My PMD and/or CPD report isn't showing up at all
in
the
dashboard and the Cobertura columns show nothing next to the JDepend
column
in that dashboard section.
I'm thinking it must look for certain xml files to be in certain
places.
For
example, when I was putting the FindBugs xml in a custom location
with:
mlOutputDirectory
${project.build.directory}/findbugs-reports
/xmlOutputDirectory
the dashboard didn't know about the findbugs report. (That setup
fact
might
be needed in the docs BTW.)
I am not specifying a location for the missing reports' xml files.
Its
just
the default.
Any ideas?
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14612401.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14623584.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14673934.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard summary missing PMD and Cobertura sections
Hi,
i'm the dashboard's project leader.
It's true that the dashboard used the default location of output directory
for each plugin.
I must resolve this problem.
Create an issue under http://jira.codehaus.org/browse/MOJO JIRA
David
Lee Meador-3 wrote:
How does the dashboard report plugin know whether to include the various
summarized reports? My PMD and/or CPD report isn't showing up at all in
the
dashboard and the Cobertura columns show nothing next to the JDepend
column
in that dashboard section.
I'm thinking it must look for certain xml files to be in certain places.
For
example, when I was putting the FindBugs xml in a custom location with:
mlOutputDirectory
${project.build.directory}/findbugs-reports
/xmlOutputDirectory
the dashboard didn't know about the findbugs report. (That setup fact
might
be needed in the docs BTW.)
I am not specifying a location for the missing reports' xml files. Its
just
the default.
Any ideas?
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14612401.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard summary missing PMD and Cobertura sections
Could you post your pom.xml to see the reporting configuration ?
you can do a mvn -e -x dashboard-report:dashboardmaven.log and post the
maven.log as attachment ?
Lee Meador-3 wrote:
1) The issue about the relocated XML files not being found was added here
http://jira.codehaus.org/browse/MOJO-987
2) I noticed the issue already reported about the Cobertura columns not
appearing due to mixed Cobertura version. I suppose they are only missing
in
the parent project's dashboard report.
3) Any ideas on why my PMD and CPD reports are not included on the
dashboard?
Thanks.
On Jan 4, 2008 2:16 AM, dvicente [EMAIL PROTECTED] wrote:
Hi,
i'm the dashboard's project leader.
It's true that the dashboard used the default location of output
directory
for each plugin.
I must resolve this problem.
Create an issue under http://jira.codehaus.org/browse/MOJO JIRA
David
Lee Meador-3 wrote:
How does the dashboard report plugin know whether to include the
various
summarized reports? My PMD and/or CPD report isn't showing up at all in
the
dashboard and the Cobertura columns show nothing next to the JDepend
column
in that dashboard section.
I'm thinking it must look for certain xml files to be in certain
places.
For
example, when I was putting the FindBugs xml in a custom location with:
mlOutputDirectory
${project.build.directory}/findbugs-reports
/xmlOutputDirectory
the dashboard didn't know about the findbugs report. (That setup fact
might
be needed in the docs BTW.)
I am not specifying a location for the missing reports' xml files. Its
just
the default.
Any ideas?
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14612401.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
--
View this message in context:
http://www.nabble.com/Dashboard-summary-missing-PMD-and-Cobertura-sections-tp14604267s177p14623584.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: dashboard - code coverage not not included with cobertura 2.2
Hi, the probelm is : Cobertura maven plugin in 2.2 version uses the 1.9 Cobertura runtime. The dashboard plugin uses the 1.7 Cobertura runtime. see the JIRA issue : http://jira.codehaus.org/browse/MOJO-910 http://jira.codehaus.org/browse/MOJO-910 I'm making tests to use 1.9 cobertura runtime instead of 1.7 version but with compatibilty with 2.0 and 2.1 cobertura maven plugin which uses 1.7 and 1.8 cobertura runtime. Best regards David EN wrote: Forgot to mention that the coverage reports available on a component level reports. On Dec 15, 2007 10:06 PM, Erez Nahir [EMAIL PROTECTED] wrote: Hi, After moving to cobertura 2.2, coverage report no longer presented in our dashboard. It used to work with cobertura 2.1. Has anyone else experienced this issue? Thanks, Erez. -- View this message in context: http://www.nabble.com/dashboard---code-coverage-not-not-included-with-cobertura-2.2-tp14354623s177p14359864.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dashboard - code coverage not not included with cobertura 2.2
Hi, the better is to rollback to 2.1 because, due time constraint with my job and the robbery of my personal computer, i can do a new snapshot release before the next month. Best regards David EN wrote: Thanks for prompt reply David, Any estimation when a fix will be available (or should I rollback to v2.1for now?). Thanks, Erez. On Dec 16, 2007 11:14 AM, dvicente [EMAIL PROTECTED] wrote: Hi, the probelm is : Cobertura maven plugin in 2.2 version uses the 1.9 Cobertura runtime. The dashboard plugin uses the 1.7 Cobertura runtime. see the JIRA issue : http://jira.codehaus.org/browse/MOJO-910 http://jira.codehaus.org/browse/MOJO-910 I'm making tests to use 1.9 cobertura runtime instead of 1.7 version but with compatibilty with 2.0 and 2.1 cobertura maven plugin which uses 1.7and 1.8 cobertura runtime. Best regards David EN wrote: Forgot to mention that the coverage reports available on a component level reports. On Dec 15, 2007 10:06 PM, Erez Nahir [EMAIL PROTECTED] wrote: Hi, After moving to cobertura 2.2, coverage report no longer presented in our dashboard. It used to work with cobertura 2.1. Has anyone else experienced this issue? Thanks, Erez. -- View this message in context: http://www.nabble.com/dashboard---code-coverage-not-not-included-with-cobertura-2.2-tp14354623s177p14359864.html Sent from the Maven - Users mailing list archive at Nabble.comhttp://nabble.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/dashboard---code-coverage-not-not-included-with-cobertura-2.2-tp14354623s177p14360650.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2][c1.1] How to run dashboard in Continuum?
This bug should have been corrected since Continuum 1.0.3. Have you used the build fresh checkbox ? i think it's used to force Continuum to execute the goal even if there is no SCM change between 2 goals ? Mick Knutson-4 wrote: Can I please get a little help on this? I have been looking for 2 days... On Dec 10, 2007 12:44 PM, Mick Knutson [EMAIL PROTECTED] wrote: I have setup the 3 phases I needed on my project group: Goals Arguments Build File Schedule Profile From Build Fresh Default Description Type clean site:site -P documentation -e pom.xml Site Schedulehttp://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6 site documentation GROUP false true Run clean site:site -P documentation -e maven2 [image: Build]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=truefromProjectPage=trueprojectId=81buildDefinitionId=24description=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 [image: Edit]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-egoals=dashboard-report%3AdashboardprojectId=81buildDefinitionId=24description=Run+dashboard-report%3Adashboard+-P+documentation+-egroupBuildDefinition=trueprojectGroupId=11buildDefinitionType=maven2scheduleId=6defaultBuildDefinition=trueprofileId=11buildFile=pom.xml [image: Delete]http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=trueprojectId=81buildDefinitionId=24confirmed=falsedescription=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 dashboard-report:dashboard -P documentation -e pom.xml Site Schedulehttp://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6 site documentation GROUP false false Run dashboard-report:dashboard -P documentation -e maven2 [image: Build]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=truefromProjectPage=trueprojectId=81buildDefinitionId=25description=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 [image: Edit]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-egoals=dashboard-report%3AdashboardprojectId=81buildDefinitionId=25description=Run+dashboard-report%3Adashboard+-P+documentation+-egroupBuildDefinition=trueprojectGroupId=11buildDefinitionType=maven2scheduleId=6defaultBuildDefinition=trueprofileId=11buildFile=pom.xml [image: Delete]http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=trueprojectId=81buildDefinitionId=25confirmed=falsedescription=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 site:site-deploy -P documentation -e pom.xml Site Schedulehttp://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6 site documentation GROUP false false Run clean site:site-deploy -P documentation -e maven2 [image: Build]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=truefromProjectPage=trueprojectId=81buildDefinitionId=26description=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 [image: Edit]http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-egoals=dashboard-report%3AdashboardprojectId=81buildDefinitionId=26description=Run+dashboard-report%3Adashboard+-P+documentation+-egroupBuildDefinition=trueprojectGroupId=11buildDefinitionType=maven2scheduleId=6defaultBuildDefinition=trueprofileId=11buildFile=pom.xml [image: Delete]http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition.action?goals=dashboard-report%3Adashboardarguments=-P+documentation+-egroupBuildDefinition=truescheduleId=6buildDefinitionType=maven2defaultBuildDefinition=trueprojectId=81buildDefinitionId=26confirmed=falsedescription=Run+dashboard-report%3Adashboard+-P+documentation+-eprojectGroupId=11buildFile=pom.xmlprofileId=11 But when I click to run the project, it only does the default. How can I have continuum run all three? -- Thanks, Mick Knutson http://www.baselogic.com
Re: Error when running dashboard-maven-plugin
Hi, could you change the Continuum goal as -e -X dashboard-report:persist and send the whole log as attachment. moreover, could you detail your config as : - maven version - JDK version - used database and version - Continuum version Best regards David Deneux, Christophe wrote: Hi all, I have the following error when running dashboard-maven-plugin:persist on my project into Continuum. That's works fine on the command line. Can someone help me ? The plugin version used is: 1.0-20070907.172709-15 [INFO] [ERROR] FATAL ERROR [INFO] [INFO]instance not of expected entity type: org.codehaus.mojo.dashboard.report.plugin.beans.JDependReportBean is not a: org.codehaus.mojo.dashboard.report.plugin.beans.AbstractReportBean [INFO] Trace org.hibernate.HibernateException: instance not of expected entity type: org.codehaus.mojo.dashboard.report.plugin.beans.JDependReportBean is not a: org.codehaus.mojo.dashboard.report.plugin.beans.AbstractReportBean at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3568) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1347) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:180) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:487) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:84) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:507) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:499) at org.hibernate.engine.CascadingAction$1.cascade(CascadingAction.java:218) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.engine.Cascade.cascade(Cascade.java:97) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.cascadeOnUpdate(DefaultSaveOrUpdateEventListener.java:332) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:304) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:217) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:93) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:507) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:499) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:495) at org.codehaus.mojo.dashboard.report.plugin.hibernate.HibernateServiceImpl.saveOrUpdate(HibernateServiceImpl.java:235) at org.codehaus.mojo.dashboard.report.plugin.DashBoardDBMojo.execute(DashBoardDBMojo.java:80) ___ Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 95 55 92 / www.capgemini.com http://www.capgemini.com/ Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE Join the Collaborative Business Experience ___ Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness. 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. -- View this message in context: http://www.nabble.com/Error-when-running-dashboard-maven-plugin-tf4954733s177.html#a14188804 Sent from the Maven - Users mailing list archive at
Re: dashboard and site plugin
Hi, could you post a http://jira.codehaus.org/browse/MOJO JIRA issue for this problem with a sample project as attachment ? Best regards David emerson cargnin wrote: Erez I presume you don't have any sub-project with a . on the name : ) emerson On 05/12/2007, Erez Nahir [EMAIL PROTECTED] wrote: So am I. Like every other 1.0-SNAPSHOT, there are things to improve, but still, greate work. Erez. P.S. it works for us on a multi module project with no issues. On Dec 5, 2007 7:16 PM, Mick Knutson [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/dashboard-maven-plugin/index.html I love the plugin and it works great On Dec 5, 2007 6:00 AM, emerson cargnin [EMAIL PROTECTED] wrote: Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/dashboard-and-site-plugin-tf4949858s177.html#a14191216 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin/aggregate report and site plugin.
HI, i'm the dashboard project leader. Your experience is very valuable. To improve the usage documentation, you can post a JIRA issue with your experience and share your problem and your solution to solve it ? No? Thxs David emerson cargnin wrote: Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dashboard-plugin-aggregate-report-and-site-plugin.-tf4949325s177.html#a14171947 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Aggregated maven reports
HI, to do that, you must specify a distributionManagement in your pom and do a mvn site:deploy to aggregate the whole site and to have the correct navigation link see the doc : http://maven.apache.org/plugins/maven-site-plugin/usage.html site usage and it's correct, the whole navigation hierarchy in Dashboard works fine only if you do a site deploy Best regards David Vicente Vishal Pahwa wrote: Hi We are already using this plugin what it does is creating the consolidated report from all the plugins like checkstyle plugin, emma plugin also but this report will agaian be separate separate for all the modules in their target directory but what the requirement is we need report only at one place from which we could navigate to any other module as well as their reports. This is definitely achievable coz I have seen in one of the project guys are doing the same they display the site on tomcat but donno how they have achieved the same. Regards Vishal. -Original Message- From: Erez Nahir [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 3:25 PM To: Maven Users List Subject: Re: Aggregated maven reports Hi Vishal, Have a look at http://mojo.codehaus.org/dashboard-maven-plugin/. Erez. Vishal Pahwa wrote: Hi We are using maven2.0.6 for our multi module project. For reports we ae using various plugins like javadoc plugin, Emma plugin, pmd plugin, depend plugin and so on. But the problem we are facing is we got the reports in each of the module individually but we have defined plugins only at the root level but still the reports are being created individually but obviously the best case would be if we couldget the consolidated report at the root level like list of all the modules and just by clicking any of the module if we could get the report for the same. So could anyone please tell me how can I achieve this. Is their any specific configuration required at the time of deployin this report on Tomcat or there is some configuration required with the plugins itself. Regards Vishal. - 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] -- View this message in context: http://www.nabble.com/Aggregated-maven-reports-tf4796528s177.html#a13731087 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] dashboard error....
Hi,
could you attach your pom.xml and the log of maven execution as :
mvn -e -X
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:persistmaven.log
best regards
David Vicente
Mick Knutson-4 wrote:
Well, I added the plugin prefix to my pom.xml, then ran the full command
and
this is what I get:
C:\opt\baselogic\yoursosmvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:persist
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] yoursos
[INFO] Utilities Common (Module Group)
[INFO] Common-Exception
[INFO] Common-Jar
[INFO] YourSOS EJB3
[INFO] YourSOS - war
[INFO] YourSOS EAR
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Required goal not found:
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:persist
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Sun Nov 04 14:10:08 PST 2007
[INFO] Final Memory: 2M/5M
[INFO]
On 11/3/07, dvicente [EMAIL PROTECTED] wrote:
Hi all,
as described in dashboard documentation :
http://mojo.codehaus.org/dashboard-maven-plugin/
you must add this in your pom.xml or settings.xml to use properly the
dashboard plugin:
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
url http://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories
But even if this configuration is well done, Maven doesn't recognize the
mvn dashboard-report:dashboard command.
and to work fine, you must run mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command
instead of mvn dashboard-report:dashboard or mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:persist command
instead of mvn dashboard-report:persist.
See :
http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html
or
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html
or
http://jira.codehaus.org/browse/MOJO-899
In the project's beginning, i decided to modify the goal prefix to
dashboard-report instead of the default's one by adding in the
pom.xmlof
the dashboard plugin :
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
I think it's The Maven resolution problem of dashboard-report.
Maven does not resolve properly the plugin prefix.
it's for that : mvn dashboard-report:dashboard or mvn
dashboard-report:persistdoesn't work correctly.
For the next release , i will post a vote to users@maven.apache.org
and
[EMAIL PROTECTED] mailing lists to delete this goalPrefix and let
the
default's one which works fine.
Mick Knutson-4 wrote:
Ok, I got something different.
I put this in my plugin section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddashboard-maven-plugin/artifactId
version1.0-SNAPSHOT/version
!--jar file that has the jdbc driver --
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.1.5/version
/dependency
/dependencies
configuration
dialect${hibernate.dialect}/dialect
driverClass${jdbc.driverClass}/driverClass
connectionUrl${dashboard.connectionUrl
}/connectionUrl
usernametro/username
passwordtro/password
/configuration
/plugin
I put this into my report plugin section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddashboard-maven-plugin/artifactId
/plugin
But I get this error when running mvn dashboard:persist -e -X
[INFO] Searching repository for plugin with prefix: 'dashboard'.
[DEBUG] Loading plugin prefixes from group: triemax
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Loading plugin prefixes from group: org.codehaus.mojo
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] build-helper-maven-plugin
Re: [m2] dashboard error....
Hi all,
as described in dashboard documentation :
http://mojo.codehaus.org/dashboard-maven-plugin/
you must add this in your pom.xml or settings.xml to use properly the
dashboard plugin:
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
url http://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories
But even if this configuration is well done, Maven doesn't recognize the
mvn dashboard-report:dashboard command.
and to work fine, you must run mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command
instead of mvn dashboard-report:dashboard or mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:persist command
instead of mvn dashboard-report:persist.
See :
http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html
or
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html
or
http://jira.codehaus.org/browse/MOJO-899
In the project's beginning, i decided to modify the goal prefix to
dashboard-report instead of the default's one by adding in the pom.xml of
the dashboard plugin :
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
I think it's The Maven resolution problem of dashboard-report.
Maven does not resolve properly the plugin prefix.
it's for that : mvn dashboard-report:dashboard or mvn
dashboard-report:persistdoesn't work correctly.
For the next release , i will post a vote to users@maven.apache.org and
[EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the
default's one which works fine.
Mick Knutson-4 wrote:
Ok, I got something different.
I put this in my plugin section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddashboard-maven-plugin/artifactId
version1.0-SNAPSHOT/version
!--jar file that has the jdbc driver --
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.1.5/version
/dependency
/dependencies
configuration
dialect${hibernate.dialect}/dialect
driverClass${jdbc.driverClass}/driverClass
connectionUrl${dashboard.connectionUrl
}/connectionUrl
usernametro/username
passwordtro/password
/configuration
/plugin
I put this into my report plugin section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddashboard-maven-plugin/artifactId
/plugin
But I get this error when running mvn dashboard:persist -e -X
[INFO] Searching repository for plugin with prefix: 'dashboard'.
[DEBUG] Loading plugin prefixes from group: triemax
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Loading plugin prefixes from group: org.codehaus.mojo
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] build-helper-maven-plugin: resolved to version 1.0 from repository
central
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project:
null:build-helper-maven-plugin:maven-plugin:1.0 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8
for
project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the
repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for
project:
org.apache.maven.plugins:maven-plugins:pom:8 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::3 for project:
org.apache.maven:maven-parent:pom:5 from the repository.
[DEBUG] Skipping disabled repository Backup
[DEBUG] Skipping disabled repository central
[DEBUG] dashboard-maven-plugin: using locally installed snapshot
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2 for
project:
org.codehaus.mojo:dashboard-maven-plugin:maven-plugin:1.0-SNAPSHOTfrom
the r
epository.
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::11 for project:
null:mojo-sandbox:pom:2 from the repository.
[DEBUG] dashboard-maven-plugin: using locally installed snapshot
[DEBUG] Skipping disabled repository Codehaus Snapshots
[DEBUG] maven-eclipse-plugin: resolved to version 2.3 from repository
central
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::7
for
project: org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.3
from
t
he repository.
[DEBUG] Retrieving parent-POM:
Re: [m2] Has anyone configured the dashboard plugin to use Derby Database for persistence?
Hi i do that all the time when i have developed the dashboard plugin : you must add this in your pom.xml : build plugins ... plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0-SNAPSHOT/version configuration dialectorg.hibernate.dialect.DerbyDialect/dialect driverClassorg.apache.derby.jdbc.ClientDriver/driverClass connectionUrljdbc:derby:c:/temp/mydashboardDB;create=true/connectionUrl usernamedashboard/username passworddashboard/password /configuration dependencies dependency groupIdorg.apache.derby/groupId artifactIdderbyclient/artifactId version10.2.1.6/version /dependency /dependencies /plugin ... /plugins /build .. reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0-SNAPSHOT/version /plugin /plugins /reporting and all works fine Mick Knutson-4 wrote: Has anyone configured the dashboard plugin to use Derby Database for persistence? I find that it might be easier to get an embedded DB instead of another Oracle DB setup so I can track the dashboard plugin -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com --- -- View this message in context: http://www.nabble.com/-m2--Has-anyone-configured-the-dashboard-plugin-to-use-Derby-Database-for-persistence--tf4732953s177.html#a13562216 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multimodule code coverage report
i think the problem is : when you add this in the pom.xml of a plugin:
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
Maven does not resolve correctly the plugin prefix.
it's for that : mvn dashboard-report:dashboard doesn't work correctly.
i mustl remove this goalPrefix but before i must post a vote
Dan Tran wrote:
umm, i actually have codehaus snaphot repo thru my maven-proxy, and i do
see
the plugin get downloaded. Perhaps, I need to specify mojo full name.
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
HI,
as described in
http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
you must add this in your pom.xml :
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories
or modify the settings.xml (in ${M2_HOME}\conf
to add the codehaus snapshot repository as :
profiles
profile
activation
activeByDefaulttrue/activeByDefault
/activation
repositories
repository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
snapshots
enabledtrue/enabled
/snapshots
releases
enabledfalse/enabled
/releases
/repository
/repositories
/profile
/profiles
keep me informed
Best regards
David
Dan Tran wrote:
is there any special instruction interm of configuration that allow me
to
run
dashboard-report:dashboard on command line.
maven throws mojo not found when I run this
my appology if i miss this configuration already in the site doc.
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
The problem is : when you add this in the pom.xml of a plugin:
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
this section is not used by the site plugin to generate the correct
plugin-info.html
what is your problem ?
Dan Tran wrote:
interesting since this site doc does not show this mojo, also
when I run it, maven errors out with mojo not found
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
yes mvn dashboard-report:dashboard is valid.
it is perhaps not a judicious choice but it's a choice i've made.
Dan Tran wrote:
from the site
are you sure 'mvn dashboard-report:dashboard ' is valid?
mvn dashboard:dashboard
perhaps?
On 9/26/07, dvicente [EMAIL PROTECTED] wrote:
you can find the dashboard at :
http://mojo.codehaus.org/dashboard-maven-plugin/
http://mojo.codehaus.org/dashboard-maven-plugin/
Bruce Alspaugh-2 wrote:
I'm having some trouble using the 2.0 version of the Cobertura
plugin
for a multiple module build. I configured the reporting
section
of
my
top level POM to generate a Cobertura report as part of my
website.
What it does is to generate reports for each of the modules
below
it,
but I don't get any report at all at the top level. How do I
configure
the plugin to generate an aggregated report the way I can with
the
javadoc plugin? I don't see it mentioned in the plugin
documentation.
Is there another plugin that would generate an aggregated code
coverage
report? Is the Emma plugin ready for primetime?
Bruce
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12916179
Sent from the Maven - Users
Re: Make a Codehaus plugin works on a local configuration
i think the problem is : when you add this in the pom.xml of a plugin: ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build Maven does not resolve correctly the plugin prefix. it's for that : mvn dashboard-report:dashboard doesn't work correctly. i mustl remove this goalPrefix but before i must post a vote Jimbog wrote: Hi Romain, I have finally got this to work, you have to call the dashboard plugin using mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard As suggested by David Vicente here:- http://jira.codehaus.org/browse/MOJO-899 Then in your local repository you have to install the plugin under libs-snaphot and plugins-snapshot, as maven seems to not download the plugin snapshot from the plugins-snapshot directory in the local repository, which seems odd. Anyway this set up seems to work fine locally. Id use ANT if I were you :o) Cheers James RomainTaz wrote: Hi James, Sorry, but I didn't find any solution to solve this problem :( Thus, this plugin has been disabled on my configuration. Note that we still do not use Artifactory. So I can't tell you if this tool can solve this problem... If you have any idea... Regards. Romain -- View this message in context: http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html#a12999702 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multimodule code coverage report
you can do a mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard
As I suggested here:-
http://jira.codehaus.org/browse/MOJO-899
http://jira.codehaus.org/browse/MOJO-899
Dan Tran wrote:
umm, i actually have codehaus snaphot repo thru my maven-proxy, and i do
see
the plugin get downloaded. Perhaps, I need to specify mojo full name.
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
HI,
as described in
http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
you must add this in your pom.xml :
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories
or modify the settings.xml (in ${M2_HOME}\conf
to add the codehaus snapshot repository as :
profiles
profile
activation
activeByDefaulttrue/activeByDefault
/activation
repositories
repository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
snapshots
enabledtrue/enabled
/snapshots
releases
enabledfalse/enabled
/releases
/repository
/repositories
/profile
/profiles
keep me informed
Best regards
David
Dan Tran wrote:
is there any special instruction interm of configuration that allow me
to
run
dashboard-report:dashboard on command line.
maven throws mojo not found when I run this
my appology if i miss this configuration already in the site doc.
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
The problem is : when you add this in the pom.xml of a plugin:
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
this section is not used by the site plugin to generate the correct
plugin-info.html
what is your problem ?
Dan Tran wrote:
interesting since this site doc does not show this mojo, also
when I run it, maven errors out with mojo not found
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
yes mvn dashboard-report:dashboard is valid.
it is perhaps not a judicious choice but it's a choice i've made.
Dan Tran wrote:
from the site
are you sure 'mvn dashboard-report:dashboard ' is valid?
mvn dashboard:dashboard
perhaps?
On 9/26/07, dvicente [EMAIL PROTECTED] wrote:
you can find the dashboard at :
http://mojo.codehaus.org/dashboard-maven-plugin/
http://mojo.codehaus.org/dashboard-maven-plugin/
Bruce Alspaugh-2 wrote:
I'm having some trouble using the 2.0 version of the Cobertura
plugin
for a multiple module build. I configured the reporting
section
of
my
top level POM to generate a Cobertura report as part of my
website.
What it does is to generate reports for each of the modules
below
it,
but I don't get any report at all at the top level. How do I
configure
the plugin to generate an aggregated report the way I can with
the
javadoc plugin? I don't see it mentioned in the plugin
documentation.
Is there another plugin that would generate an aggregated code
coverage
report? Is the Emma plugin ready for primetime?
Bruce
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12916179
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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: Multimodule code coverage report
yes mvn dashboard-report:dashboard is valid. it is perhaps not a judicious choice but it's a choice i've made. Dan Tran wrote: from the site are you sure 'mvn dashboard-report:dashboard ' is valid? mvn dashboard:dashboard perhaps? On 9/26/07, dvicente [EMAIL PROTECTED] wrote: you can find the dashboard at : http://mojo.codehaus.org/dashboard-maven-plugin/ http://mojo.codehaus.org/dashboard-maven-plugin/ Bruce Alspaugh-2 wrote: I'm having some trouble using the 2.0 version of the Cobertura plugin for a multiple module build. I configured the reporting section of my top level POM to generate a Cobertura report as part of my website. What it does is to generate reports for each of the modules below it, but I don't get any report at all at the top level. How do I configure the plugin to generate an aggregated report the way I can with the javadoc plugin? I don't see it mentioned in the plugin documentation. Is there another plugin that would generate an aggregated code coverage report? Is the Emma plugin ready for primetime? Bruce - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12916179 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multimodule code coverage report
The problem is : when you add this in the pom.xml of a plugin: ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build this section is not used by the site plugin to generate the correct plugin-info.html what is your problem ? Dan Tran wrote: interesting since this site doc does not show this mojo, also when I run it, maven errors out with mojo not found -D On 9/27/07, dvicente [EMAIL PROTECTED] wrote: yes mvn dashboard-report:dashboard is valid. it is perhaps not a judicious choice but it's a choice i've made. Dan Tran wrote: from the site are you sure 'mvn dashboard-report:dashboard ' is valid? mvn dashboard:dashboard perhaps? On 9/26/07, dvicente [EMAIL PROTECTED] wrote: you can find the dashboard at : http://mojo.codehaus.org/dashboard-maven-plugin/ http://mojo.codehaus.org/dashboard-maven-plugin/ Bruce Alspaugh-2 wrote: I'm having some trouble using the 2.0 version of the Cobertura plugin for a multiple module build. I configured the reporting section of my top level POM to generate a Cobertura report as part of my website. What it does is to generate reports for each of the modules below it, but I don't get any report at all at the top level. How do I configure the plugin to generate an aggregated report the way I can with the javadoc plugin? I don't see it mentioned in the plugin documentation. Is there another plugin that would generate an aggregated code coverage report? Is the Emma plugin ready for primetime? Bruce - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12916179 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12922369 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multimodule code coverage report
HI,
as described in http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
you must add this in your pom.xml :
pluginRepositories
pluginRepository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories
or modify the settings.xml (in ${M2_HOME}\conf
to add the codehaus snapshot repository as :
profiles
profile
activation
activeByDefaulttrue/activeByDefault
/activation
repositories
repository
idCodehaus Snapshots/id
urlhttp://snapshots.repository.codehaus.org//url
snapshots
enabledtrue/enabled
/snapshots
releases
enabledfalse/enabled
/releases
/repository
/repositories
/profile
/profiles
keep me informed
Best regards
David
Dan Tran wrote:
is there any special instruction interm of configuration that allow me to
run
dashboard-report:dashboard on command line.
maven throws mojo not found when I run this
my appology if i miss this configuration already in the site doc.
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
The problem is : when you add this in the pom.xml of a plugin:
...
build
plugins
plugin
artifactIdmaven-plugin-plugin/artifactId
configuration
goalPrefixdashboard-report/goalPrefix
/configuration
/plugin
...
/plugins
...
/build
this section is not used by the site plugin to generate the correct
plugin-info.html
what is your problem ?
Dan Tran wrote:
interesting since this site doc does not show this mojo, also
when I run it, maven errors out with mojo not found
-D
On 9/27/07, dvicente [EMAIL PROTECTED] wrote:
yes mvn dashboard-report:dashboard is valid.
it is perhaps not a judicious choice but it's a choice i've made.
Dan Tran wrote:
from the site
are you sure 'mvn dashboard-report:dashboard ' is valid?
mvn dashboard:dashboard
perhaps?
On 9/26/07, dvicente [EMAIL PROTECTED] wrote:
you can find the dashboard at :
http://mojo.codehaus.org/dashboard-maven-plugin/
http://mojo.codehaus.org/dashboard-maven-plugin/
Bruce Alspaugh-2 wrote:
I'm having some trouble using the 2.0 version of the Cobertura
plugin
for a multiple module build. I configured the reporting section
of
my
top level POM to generate a Cobertura report as part of my
website.
What it does is to generate reports for each of the modules below
it,
but I don't get any report at all at the top level. How do I
configure
the plugin to generate an aggregated report the way I can with
the
javadoc plugin? I don't see it mentioned in the plugin
documentation.
Is there another plugin that would generate an aggregated code
coverage
report? Is the Emma plugin ready for primetime?
Bruce
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12916179
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12922369
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
Re: Multimodule code coverage report
you can find the dashboard at : http://mojo.codehaus.org/dashboard-maven-plugin/ http://mojo.codehaus.org/dashboard-maven-plugin/ Bruce Alspaugh-2 wrote: I'm having some trouble using the 2.0 version of the Cobertura plugin for a multiple module build. I configured the reporting section of my top level POM to generate a Cobertura report as part of my website. What it does is to generate reports for each of the modules below it, but I don't get any report at all at the top level. How do I configure the plugin to generate an aggregated report the way I can with the javadoc plugin? I don't see it mentioned in the plugin documentation. Is there another plugin that would generate an aggregated code coverage report? Is the Emma plugin ready for primetime? Bruce - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html#a12902383 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 dashboard-plugin clover historic report data missing
Hi, yes it's true, i have the same bug. Could you create an issue on JIRA : http://jira.codehaus.org/browse/MOJO I will correct it this week-end and try to make a new snapshot release the next week. Keep me informed Best regards David Jimbog wrote: Great, thanks, let me know if you need anymore information. dvicente wrote: no error in the log file. I will do new tests with clover and i keep you informed. Best regards David Jimbog wrote: dvicente wrote: Hi, I'm the dashboard project leader. No, i haven't seen this error before. it must be a bug of dashboard plugin but could you do a mvn -e -X dashboard-report:dashboard and redirect the output to a log file and upload it as an attachment ? Jimbog wrote: Hi, I have an M2 multi project, with the dashboard plug-in amalgamating all of our clover, maven, checkstyle, pmd and cpd reports. The plug-in also persists all the data for these reports. However, when I generate the historic html, the clover chart contains no data, despite the data being persisted in the database. All the other charts display data, and the clover reports are shown in the dash board report page. Is this a bug in the dashboard plugin? Has anyone else seen this ? Thanks James http://www.nabble.com/file/p12523267/historicClover.zip historicClover.zip -- View this message in context: http://www.nabble.com/Maven-2-dashboard-plugin-clover-historic-report-data-missing-tf4392197s177.html#a12553829 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 dashboard-plugin clover historic report data missing
Ok i've released the new version of dashboard as 1.0-SNAPSHOT keep me informed Best regards David Vicente Jimbog wrote: Issue for this is http://jira.codehaus.org/browse/MOJO-907 Thanks James dvicente wrote: Hi, yes it's true, i have the same bug. Could you create an issue on JIRA : http://jira.codehaus.org/browse/MOJO I will correct it this week-end and try to make a new snapshot release the next week. Keep me informed Best regards David Jimbog wrote: Great, thanks, let me know if you need anymore information. dvicente wrote: no error in the log file. I will do new tests with clover and i keep you informed. Best regards David Jimbog wrote: dvicente wrote: Hi, I'm the dashboard project leader. No, i haven't seen this error before. it must be a bug of dashboard plugin but could you do a mvn -e -X dashboard-report:dashboard and redirect the output to a log file and upload it as an attachment ? Jimbog wrote: Hi, I have an M2 multi project, with the dashboard plug-in amalgamating all of our clover, maven, checkstyle, pmd and cpd reports. The plug-in also persists all the data for these reports. However, when I generate the historic html, the clover chart contains no data, despite the data being persisted in the database. All the other charts display data, and the clover reports are shown in the dash board report page. Is this a bug in the dashboard plugin? Has anyone else seen this ? Thanks James http://www.nabble.com/file/p12523267/historicClover.zip historicClover.zip -- View this message in context: http://www.nabble.com/Maven-2-dashboard-plugin-clover-historic-report-data-missing-tf4392197s177.html#a12561386 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] strange, show-stopping PMD error
Hi,
I'm the dashboard project leader.
No, i haven't seen this error before.
could you do a mvn -e -X site and redirect the output to a log file and
upload it as an attachment ?
so, could you also uncomment the dashboard plugin but still left the PMD
plugin commented out, and do a mvn -e -X site and redirect the output to a
log file and upload it as an attachment ?
Thanks
Best regards
David Vicente
Mick Knutson-4 wrote:
To add more details, I removed the dashboard plugin as well as the pmd
plugin, and it works fine, but then I don't get PMD and I really need it!
So I also uncommented PMD but still left the dashboard plugin commented
out,
and went back to the same error Provider
oracle.xml.jaxp.JXDocumentBuilderFactory could not be instantiated:
java.lang.NullPointerException with the first module that did not have
java
code.
On 9/7/07, Mick Knutson [EMAIL PROTECTED] wrote:
I have a strange and intermittent error. It appears [mostly], when I am
running site on a module goup that does not have any java code in it.
Now oracle.xml.jaxp.JXDocumentBuilderFactory is the jaxp lib's from OC4j
in my project, but I have no idea how that is getting referenced as I am
running the SUN JDK, not the Oracle JDK.
I have done 2 things:
1. Add site plugin to every pom (30 of them) and only turn site
generation onto the ones that need it. The issue with that is the
dashboard
plugin then does not include Checkstyle or PMD in the report even though
locally the reports are generated. (see PMD error #1)
2. commented out just the custom ruleset and there was no change.
3. I commented out the PMD plugin (removed the work from #1), and then I
started getting these dashboard errors with the modules that had no java
source in them. (seeDashboard Error below).
Here is my reporting plugin:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
version2.2/version
configuration
linkXreftrue/linkXref
sourceEncodingutf-8/sourceEncoding
minimumTokens100/minimumTokens
targetJdk1.5/targetJdk
rulesets
ruleset${project.root
}tools/build-tools/src/main/resources/pmd-rules.xml/ruleset
/rulesets
excludes
exclude**/* Bean.java/exclude
exclude**/generated-sources/*.java/exclude
/excludes
/configuration
/plugin
Here is the error I get (PMD error #1):
[DEBUG] **
[DEBUG] Starting Jakarta Velocity v1.4
[DEBUG] RuntimeInstance initializing.
[DEBUG] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[DEBUG] Trying to use logger class
org.apache.maven.jxr.log.VelocityLogger
[DEBUG] Using logger class org.apache.maven.jxr.log.VelocityLogger
[DEBUG] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[DEBUG] Resource Loader Instantiated:
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
[DEBUG] ClasspathResourceLoader : initialization starting.
[DEBUG] ClasspathResourceLoader : initialization complete.
[DEBUG] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[DEBUG] Default ResourceManager initialization complete.
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[DEBUG] Created: 20 parsers.
[DEBUG] Velocimacro : initialization starting.
[DEBUG] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[DEBUG] Velocimacro : allowInlineToOverride = false : VMs defined inline
may NOT replace previous VM definitions
[DEBUG] Velocimacro : allowInlineLocal = false : VMs defined inline will
be global in scope if allowed.
[DEBUG] Velocimacro : messages on : VM system will output logging
messages
[DEBUG] Velocimacro : autoload off : VM system will not automatically
reload global library macros
[DEBUG] Velocimacro : initialization complete.
[DEBUG] Velocity successfully started.
[DEBUG] ResourceManager : found templates/index.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
[DEBUG] ResourceManager : found templates/overview-frame.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
[DEBUG] ResourceManager : found templates/allclasses-frame.vm with loader
Re: [m2] strange, show-stopping PMD error
Mick Knutson-4 wrote:
How do I redirect the output to a log file?
On 9/7/07, dvicente [EMAIL PROTECTED] wrote:
like this: mvn -e -X sitemaven.log
Hi,
I'm the dashboard project leader.
No, i haven't seen this error before.
could you do a mvn -e -X site and redirect the output to a log file and
upload it as an attachment ?
so, could you also uncomment the dashboard plugin but still left the PMD
plugin commented out, and do a mvn -e -X site and redirect the output to
a
log file and upload it as an attachment ?
Thanks
Best regards
David Vicente
Mick Knutson-4 wrote:
To add more details, I removed the dashboard plugin as well as the pmd
plugin, and it works fine, but then I don't get PMD and I really need
it!
So I also uncommented PMD but still left the dashboard plugin commented
out,
and went back to the same error Provider
oracle.xml.jaxp.JXDocumentBuilderFactory could not be instantiated:
java.lang.NullPointerException with the first module that did not have
java
code.
On 9/7/07, Mick Knutson [EMAIL PROTECTED] wrote:
I have a strange and intermittent error. It appears [mostly], when I
am
running site on a module goup that does not have any java code in it.
Now oracle.xml.jaxp.JXDocumentBuilderFactory is the jaxp lib's from
OC4j
in my project, but I have no idea how that is getting referenced as I
am
running the SUN JDK, not the Oracle JDK.
I have done 2 things:
1. Add site plugin to every pom (30 of them) and only turn site
generation onto the ones that need it. The issue with that is the
dashboard
plugin then does not include Checkstyle or PMD in the report even
though
locally the reports are generated. (see PMD error #1)
2. commented out just the custom ruleset and there was no change.
3. I commented out the PMD plugin (removed the work from #1), and then
I
started getting these dashboard errors with the modules that had no
java
source in them. (seeDashboard Error below).
Here is my reporting plugin:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
version2.2/version
configuration
linkXreftrue/linkXref
sourceEncodingutf-8/sourceEncoding
minimumTokens100/minimumTokens
targetJdk1.5/targetJdk
rulesets
ruleset${project.root
}tools/build-tools/src/main/resources/pmd-rules.xml/ruleset
/rulesets
excludes
exclude**/* Bean.java/exclude
exclude**/generated-sources/*.java/exclude
/excludes
/configuration
/plugin
Here is the error I get (PMD error #1):
[DEBUG] **
[DEBUG] Starting Jakarta Velocity v1.4
[DEBUG] RuntimeInstance initializing.
[DEBUG] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[DEBUG] Trying to use logger class
org.apache.maven.jxr.log.VelocityLogger
[DEBUG] Using logger class org.apache.maven.jxr.log.VelocityLogger
[DEBUG] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[DEBUG] Resource Loader Instantiated:
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
[DEBUG] ClasspathResourceLoader : initialization starting.
[DEBUG] ClasspathResourceLoader : initialization complete.
[DEBUG] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[DEBUG] Default ResourceManager initialization complete.
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[DEBUG] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[DEBUG] Created: 20 parsers.
[DEBUG] Velocimacro : initialization starting.
[DEBUG] Velocimacro : allowInline = true : VMs can be defined inline
in
templates
[DEBUG] Velocimacro : allowInlineToOverride = false : VMs defined
inline
may NOT replace previous VM definitions
[DEBUG] Velocimacro : allowInlineLocal = false : VMs defined inline
will
be global in scope if allowed.
[DEBUG] Velocimacro : messages on : VM system will output logging
messages
[DEBUG] Velocimacro : autoload off : VM system will not automatically
reload global library macros
[DEBUG] Velocimacro : initialization complete.
[DEBUG] Velocity successfully started.
[DEBUG] ResourceManager : found templates/index.vm with loader
Re: Maven 2 dashboard-plugin clover historic report data missing
Hi, I'm the dashboard project leader. No, i haven't seen this error before. it must be a bug of dashboard plugin but could you do a mvn -e -X dashboard-report:dashboard and redirect the output to a log file and upload it as an attachment ? Jimbog wrote: Hi, I have an M2 multi project, with the dashboard plug-in amalgamating all of our clover, maven, checkstyle, pmd and cpd reports. The plug-in also persists all the data for these reports. However, when I generate the historic html, the clover chart contains no data, despite the data being persisted in the database. All the other charts display data, and the clover reports are shown in the dash board report page. Is this a bug in the dashboard plugin? Has anyone else seen this ? Thanks James -- View this message in context: http://www.nabble.com/Maven-2-dashboard-plugin-clover-historic-report-data-missing-tf4392197s177.html#a12522938 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 dashboard-plugin clover historic report data missing
no error in the log file. I will do new tests with clover and i keep you informed. Best regards David Jimbog wrote: dvicente wrote: Hi, I'm the dashboard project leader. No, i haven't seen this error before. it must be a bug of dashboard plugin but could you do a mvn -e -X dashboard-report:dashboard and redirect the output to a log file and upload it as an attachment ? Jimbog wrote: Hi, I have an M2 multi project, with the dashboard plug-in amalgamating all of our clover, maven, checkstyle, pmd and cpd reports. The plug-in also persists all the data for these reports. However, when I generate the historic html, the clover chart contains no data, despite the data being persisted in the database. All the other charts display data, and the clover reports are shown in the dash board report page. Is this a bug in the dashboard plugin? Has anyone else seen this ? Thanks James http://www.nabble.com/file/p12523267/historicClover.zip historicClover.zip -- View this message in context: http://www.nabble.com/Maven-2-dashboard-plugin-clover-historic-report-data-missing-tf4392197s177.html#a12523793 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the best way to consolidate the site from a multi-project project
yes you add this section in your root pom : loganalyzer.site Maven Project Website file:///C:\temp\site Maven nw knows where to deploy the site. after that, mvn site site:deploy and your site is fully operational see the doc : http://maven.apache.org/plugins/maven-site-plugin/usage.html http://maven.apache.org/plugins/maven-site-plugin/usage.html ChuckC wrote: I have my site generating for a multi-project project, but the top level pom report does not properly link into the sub-level pom reports. Ideally, I would like the site to be in a single destination. Is there a way to get the sites to link together as a single site. This is very similar to the earlier post about getting it to generate sites for a multi-projects project. -- View this message in context: http://www.nabble.com/What-is-the-best-way-to-consolidate-the-site-from-a-multi-project-project-tf4239560s177.html#a12088208 Sent from the Maven - Users mailing list archive at Nabble.com.
RE: [continuum-1.1-beta-1] pb with Synergy SCM
no i haven't seen your earlier post but it seems the same problem with Synergy. Thanks you for your answer Randall Fidler wrote: Hi David, Not sure if you saw the earlier post by myself and another person but the same situation happened with Perforce SCM; upgraded to the latest beta and nothing works since. It seems like it just doesn't execute the actual scm commands properly in this latest version. Regards, Randall -Original Message- From: david vicente [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:42 AM To: continuum-users@maven.apache.org Subject: [continuum-1.1-beta-1] pb with Synergy SCM Hi all, I used Continuum 1.0.3 with Synergy (with maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works fine. I have just continuum-1.1-beta-1 and nothing works since. it does not manage to extract the sources. In Continuum.log, I have that : 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default - Enqueuing 'VignetteOffre' (Build definition id=2). 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of VignetteOffre 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Updating working dir 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action check-working-directory 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action checkout-project 339638 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum- 1.1\working-directory\1'. 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - A working project already exists [Query expression must be specified.]. 354857 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results 354935 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Error updating from SCM, not building and my build result traces : Exception: Cannot checkout sources. Exception while executing SCM command. Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must be specified.' STDOUT = Project reference requires name and version optionally followed by instance: 'Query expression must be specified.' STDERR = Warning: Unable to identify project. I try to set level log to DEBUG but nothing more could you help me ? David Vicente -- View this message in context: http://www.nabble.com/-continuum-1.1-beta-1--pb-with-Synergy-SCM-tf4235149.html#a12052245 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: [continuum-1.1-beta-1] pb with Synergy SCM
I think that the problem is in SynergyCheckOutCommand class and
getWorkingProject method of SynergyUtil class.
The correct command must be :
ccm sync -r -p %displayname owner='MTP001' and status='working' and
type='project' and has_predecessor('VignetteOffre~01_00_00:project:1')
i think that the problem is Continuum executes a checkout Command instead of
update command because in my case the local Synergy project already exists.
Emmanuel Venisse wrote:
It isn't a problem with the command execution process because all other
commands (mvn, ant, svn, cvs...) works fine.
Maybe it's a change in maven-scm done between maven-scm 1.0-beta-4 and 1.0
final
David, can you explain this message?
Exception:
Cannot checkout sources.
Exception while executing SCM command.
Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must be
specified.'
STDOUT = Project reference requires name and version optionally followed
by
instance: 'Query expression must be specified.'
STDERR = Warning: Unable to identify project.
What would be the correct command to run?
dvicente a écrit :
Windows 2000 Advanced Server ;-((
Emmanuel Venisse wrote:
Randall, David,
What is your OS?
dvicente a écrit :
no i haven't seen your earlier post but it seems the same problem with
Synergy.
Thanks you for your answer
Randall Fidler wrote:
Hi David,
Not sure if you saw the earlier post by myself and another
person but the same situation happened with Perforce SCM; upgraded to
the latest beta and nothing works since. It seems like it just
doesn't
execute the actual scm commands properly in this latest version.
Regards,
Randall
-Original Message-
From: david vicente [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 08, 2007 1:42 AM
To: continuum-users@maven.apache.org
Subject: [continuum-1.1-beta-1] pb with Synergy SCM
Hi all,
I used Continuum 1.0.3 with Synergy (with maven-SCM-api-1.0-beta-4.jar
and
maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works
fine.
I have just continuum-1.1-beta-1 and nothing works since.
it does not manage to extract the sources.
In Continuum.log, I have that :
339122 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing
'VignetteOffre'
(Build definition id=2).
339169 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Initializing build
339169 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Starting build of VignetteOffre
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Updating working dir
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action check-working-directory
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action checkout-project
339638 [pool-1-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Checking out
project:
'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum-
1.1\working-directory\1'.
348091 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - A working project
already
exists [Query expression must be specified.].
354857 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Merging SCM results
354935 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Error
updating from SCM, not building
and my build result traces :
Exception:
Cannot checkout sources.
Exception while executing SCM command.
Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must
be
specified.'
STDOUT = Project reference requires name and version optionally
followed
by
instance: 'Query expression must be specified.'
STDERR = Warning: Unable to identify project.
I try to set level log to DEBUG but nothing more
could you help me ?
David Vicente
--
View this message in context:
http://www.nabble.com/-continuum-1.1-beta-1--pb-with-Synergy-SCM-tf4235149.html#a12053113
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: [continuum-1.1-beta-1] pb with Synergy SCM
i do the 2 types of Continuum integration.
- add a local pom.xml to Continuum and let Continuum to check-out the
project
- check-out the project before and add this specific pom.xml to Continuum
i have the same result.
And when Continuum works, it's not me which decide what is the scm command
to launch
Emmanuel Venisse wrote:
Why do you project already exists?
Maybe you can patch the checkout command to run an update if the project
already exists
dvicente a écrit :
I think that the problem is in SynergyCheckOutCommand class and
getWorkingProject method of SynergyUtil class.
The correct command must be :
ccm sync -r -p %displayname owner='MTP001' and status='working' and
type='project' and has_predecessor('VignetteOffre~01_00_00:project:1')
i think that the problem is Continuum executes a checkout Command instead
of
update command because in my case the local Synergy project already
exists.
Emmanuel Venisse wrote:
It isn't a problem with the command execution process because all other
commands (mvn, ant, svn, cvs...) works fine.
Maybe it's a change in maven-scm done between maven-scm 1.0-beta-4 and
1.0
final
David, can you explain this message?
Exception:
Cannot checkout sources.
Exception while executing SCM command.
Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must be
specified.'
STDOUT = Project reference requires name and version optionally followed
by
instance: 'Query expression must be specified.'
STDERR = Warning: Unable to identify project.
What would be the correct command to run?
dvicente a écrit :
Windows 2000 Advanced Server ;-((
Emmanuel Venisse wrote:
Randall, David,
What is your OS?
dvicente a écrit :
no i haven't seen your earlier post but it seems the same problem
with
Synergy.
Thanks you for your answer
Randall Fidler wrote:
Hi David,
Not sure if you saw the earlier post by myself and another
person but the same situation happened with Perforce SCM; upgraded
to
the latest beta and nothing works since. It seems like it just
doesn't
execute the actual scm commands properly in this latest version.
Regards,
Randall
-Original Message-
From: david vicente [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 08, 2007 1:42 AM
To: continuum-users@maven.apache.org
Subject: [continuum-1.1-beta-1] pb with Synergy SCM
Hi all,
I used Continuum 1.0.3 with Synergy (with
maven-SCM-api-1.0-beta-4.jar
and
maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works
fine.
I have just continuum-1.1-beta-1 and nothing works since.
it does not manage to extract the sources.
In Continuum.log, I have that :
339122 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing
'VignetteOffre'
(Build definition id=2).
339169 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Initializing build
339169 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Starting build of VignetteOffre
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Updating working dir
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Performing action check-working-directory
339435 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Performing action checkout-project
339638 [pool-1-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Checking out
project:
'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum-
1.1\working-directory\1'.
348091 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - A working project
already
exists [Query expression must be specified.].
354857 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Merging SCM results
354935 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default
-
Error
updating from SCM, not building
and my build result traces :
Exception:
Cannot checkout sources.
Exception while executing SCM command.
Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must
be
specified.'
STDOUT = Project reference requires name and version optionally
followed
by
instance: 'Query expression must be specified.'
STDERR = Warning: Unable to identify project.
I try to set level log to DEBUG but nothing more
could you help me ?
David Vicente
--
View this message in context:
http://www.nabble.com/-continuum-1.1-beta-1--pb-with-Synergy-SCM-tf4235149.html#a12053368
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: [continuum-1.1-beta-1] pb with Synergy SCM
Windows 2000 Advanced Server ;-(( Emmanuel Venisse wrote: Randall, David, What is your OS? dvicente a écrit : no i haven't seen your earlier post but it seems the same problem with Synergy. Thanks you for your answer Randall Fidler wrote: Hi David, Not sure if you saw the earlier post by myself and another person but the same situation happened with Perforce SCM; upgraded to the latest beta and nothing works since. It seems like it just doesn't execute the actual scm commands properly in this latest version. Regards, Randall -Original Message- From: david vicente [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 1:42 AM To: [EMAIL PROTECTED] Subject: [continuum-1.1-beta-1] pb with Synergy SCM Hi all, I used Continuum 1.0.3 with Synergy (with maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works fine. I have just continuum-1.1-beta-1 and nothing works since. it does not manage to extract the sources. In Continuum.log, I have that : 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default - Enqueuing 'VignetteOffre' (Build definition id=2). 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of VignetteOffre 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Updating working dir 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action check-working-directory 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action checkout-project 339638 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum- 1.1\working-directory\1'. 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - A working project already exists [Query expression must be specified.]. 354857 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results 354935 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Error updating from SCM, not building and my build result traces : Exception: Cannot checkout sources. Exception while executing SCM command. Commandeline = cmd.exe /X /C 'ccm sync -r -p Query expression must be specified.' STDOUT = Project reference requires name and version optionally followed by instance: 'Query expression must be specified.' STDERR = Warning: Unable to identify project. I try to set level log to DEBUG but nothing more could you help me ? David Vicente -- View this message in context: http://www.nabble.com/-continuum-1.1-beta-1--pb-with-Synergy-SCM-tf4235149.html#a12052553 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: site:site versus site:stage
Hi,
the mvn site:site creates the site for each module in
${module}/target/site directory
all created links in each site don't work because they reflect the future
deployed site architecture, not the current directories architecture.
the mvn site:stage command creates the site in a local directory to test
it in local as if it has deployed.
To work fine, you must create and deploy the site with
distributionManagement section in your root pom as :
distributionManagement
site
idmysite/id
nameMaven ProjectWebsite/name
urlfile:///c:\temp/url
/site
/distributionManagement
and the mvn site:site site:deploy command
Adam Fisk-3 wrote:
I'm having issues using site:site with a multi-module project. site:stage
works fine, but for some reason site:site doesn't like my modules, instead
just listing them in bold.
Shouldn't they do the same thing? Any idea how I get site:site to just
link
the darn modules? I'm using maven 2.0.7.
Thanks!
-Adam
--
View this message in context:
http://www.nabble.com/site%3Asite-versus-site%3Astage-tf4154748s177.html#a11827772
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I get the Dashboard plugin integrated to my website?
Hi, could you gie us your pom ? which maven's version do you use ? which dashboard plugin's version ? Ian Rowlands wrote: I've added it into the pom file, I can see the report output being generated, but when I open the project-reports.html file it doesn't have a link in there. Is there anything else I have to do? I am running the build in a number of phases, as recommended: mvn site mvn dashboard:dashboard mvn site:deploy Regards, Ian Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected ( administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-do-I-get-the-Dashboard-plugin-integrated-to-my-website--tf4156303s177.html#a11826621 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I get the Dashboard plugin integrated to my website?
Hi, i've made a mistake when i'v writted the doc. the right command is : mvn dashboard-report:dashboard Ian Rowlands wrote: I've added it into the pom file, I can see the report output being generated, but when I open the project-reports.html file it doesn't have a link in there. Is there anything else I have to do? I am running the build in a number of phases, as recommended: mvn site mvn dashboard:dashboard mvn site:deploy Regards, Ian Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected ( administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-do-I-get-the-Dashboard-plugin-integrated-to-my-website--tf4156303s177.html#a11836469 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build Failed For 521889
it was just a problem of classpath's length.
i made a shared directory with my repository as root disk and it's ok.
thanks
Joakim Erdfelt-2 wrote:
Wow. that's ugly!
The lack of STDOUT or STDERR output on this error is troubling.
Can you delete your $HOME/.m2/repository/jpox/jpox-enhancer/* files and
try again?
If it still fails, I'd like for you to run mvn --debug clean install
and see if there is anymore STDOUT or STDERR output.
- Joakim Erdfelt
dvicente wrote:
i try to build Archiva and it fails during Building Archiva Standard
Reports because :
[INFO] [jpox:enhance {execution: default}]
[DEBUG] Classes Dir is :
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes
[DEBUG] Executing command line:
[DEBUG] java -cp
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes;C:\PIC\maven-repo-sonate\org\apache\maven\maven-profile\2.0.5\maven-profile-2.0.5.jar;C:\PIC\maven-repo-sonate\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-classworlds\1.2-alpha-7\plexus-classworlds-1.2-alpha-7.jar;C:\PIC\projects\Archiva\archiva-repository-layer\target\classes;C:\PIC\maven-repo-sonate\javax\jdo\jdo2-api\2.0\jdo2-api-2.0.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-project\2.0.5\maven-project-2.0.5.jar;C:\PIC\maven-repo-sonate\log4j\log4j\1.2.8\log4j-1.2.8.jar;C:\PIC\maven-repo-sonate\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-component-api\1.0-alpha-19\plexus-component-api-1.0-alpha-19.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\cache\plexus-cache-ehcache\1.0-alpha-2-SNAPSHOT\plexus-cache-ehcache-1.0-alpha-2-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\javax\resource\connector\1.0\connector-1.0.jar;C:\PIC\maven-repo-sonate\org\slf4j\slf4j-log4j12\1.2\slf4j-log4j12-1.2.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-model\2.0.5\maven-model-2.0.5.jar;C:\PIC\maven-repo-sonate\org\apache\lucene\lucene-core\2.0.0\lucene-core-2.0.0.jar;C:\PIC\projects\Archiva\archiva-discoverer\target\classes;C:\PIC\maven-repo-sonate\org\apache\maven\maven-artifact\2.0.5\maven-artifact-2.0.5.jar;C:\PIC\projects\Archiva\archiva-common\target\archiva-common-1.0-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\org\apache\maven\wagon\wagon-provider-api\1.0-beta-2\wagon-provider-api-1.0-beta-2.jar;C:\PIC\maven-repo-sonate\geronimo-spec\geronimo-spec-jta\1.0.1B-rc2\geronimo-spec-jta-1.0.1B-rc2.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-settings\2.0.5\maven-settings-2.0.5.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-digest\1.0\plexus-digest-1.0.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-utils\1.4\plexus-utils-1.4.jar;C:\PIC\maven-repo-sonate\commons-lang\commons-lang\2.2\commons-lang-2.2.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-container-default\1.0-alpha-20\plexus-container-default-1.0-alpha-20.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-repository-metadata\2.0.5\maven-repository-metadata-2.0.5.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-jdo2\1.0-alpha-8\plexus-jdo2-1.0-alpha-8.jar;C:\PIC\maven-repo-sonate\org\slf4j\slf4j-api\1.2\slf4j-api-1.2.jar;C:\PIC\projects\Archiva\archiva-indexer\target\classes;C:\PIC\maven-repo-sonate\commons-collections\commons-collections\3.2\commons-collections-3.2.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\cache\plexus-cache-api\1.0-alpha-2-SNAPSHOT\plexus-cache-api-1.0-alpha-2-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\net\sf\ehcache\ehcache\1.2.4\ehcache-1.2.4.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-artifact-manager\2.0.5\maven-artifact-manager-2.0.5.jar;C:\PIC\maven-repo-sonate\commons-io\commons-io\1.2\commons-io-1.2.jar;C:\PIC\maven-repo-sonate\jpox\jpox\1.1.7\jpox-1.1.7.jar;C:\PIC\maven-repo-sonate\geronimo-spec\geronimo-spec-jta\1.0.1B-rc2\geronimo-spec-jta-1.0.1B-rc2.jar;C:\PIC\maven-repo-sonate\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar;C:\PIC\maven-repo-sonate\org\apache\bcel\bcel\5.2\bcel-5.2.jar;C:\PIC\maven-repo-sonate\javax\resource\connector\1.0\connector-1.0.jar;C:\PIC\maven-repo-sonate\javax\jdo\jdo2-api\2.0\jdo2-api-2.0.jar;C:\PIC\maven-repo-sonate\jakarta-regexp\jakarta-regexp\1.4\jakarta-regexp-1.4.jar;C:\PIC\maven-repo-sonate\jpox\jpox-enhancer\1.1.7\jpox-enhancer-1.1.7.jar;C:\PIC\maven-repo-sonate\ant\ant\1.6\ant-1.6.jar;C:\PIC\maven-repo-sonate\log4j\log4j\1.2.8\log4j-1.2.8.jar;C:\PIC\maven-repo-sonate\jpox\jpox\1.1.7\jpox-1.1.7.jar;C:\PIC\maven-2.0.5\core\plexus-container-default-1.0-alpha-9.jar;C:\PIC\maven-2.0.5\core\plexus-utils-1.1.jar;C:\PIC\maven-2.0.5\lib\maven-artifact-2.0.5.jar;C:\PIC\maven-2.0.5\lib\maven-plugin-api-2.0.5.jar
-Dlog4j.configuration=jar:file:/C:/PIC/maven-repo-sonate/org/codehaus/mojo/jpox-maven-plugin/1.1.7-SNAPSHOT/jpox-maven-plugin-1.1.7-SNAPSHOT.jar!/log4j.configuration
org.jpox.enhancer.JPOXEnhancer -v
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes\org\apache\maven\archiva\reporting\model\package.jdo
Re: Build Failed For 521889
i try to build Archiva and it fails during Building Archiva Standard
Reports because :
[INFO] [jpox:enhance {execution: default}]
[DEBUG] Classes Dir is :
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes
[DEBUG] Executing command line:
[DEBUG] java -cp
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes;C:\PIC\maven-repo-sonate\org\apache\maven\maven-profile\2.0.5\maven-profile-2.0.5.jar;C:\PIC\maven-repo-sonate\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-classworlds\1.2-alpha-7\plexus-classworlds-1.2-alpha-7.jar;C:\PIC\projects\Archiva\archiva-repository-layer\target\classes;C:\PIC\maven-repo-sonate\javax\jdo\jdo2-api\2.0\jdo2-api-2.0.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-project\2.0.5\maven-project-2.0.5.jar;C:\PIC\maven-repo-sonate\log4j\log4j\1.2.8\log4j-1.2.8.jar;C:\PIC\maven-repo-sonate\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-component-api\1.0-alpha-19\plexus-component-api-1.0-alpha-19.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\cache\plexus-cache-ehcache\1.0-alpha-2-SNAPSHOT\plexus-cache-ehcache-1.0-alpha-2-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\javax\resource\connector\1.0\connector-1.0.jar;C:\PIC\maven-repo-sonate\org\slf4j\slf4j-log4j12\1.2\slf4j-log4j12-1.2.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-model\2.0.5\maven-model-2.0.5.jar;C:\PIC\maven-repo-sonate\org\apache\lucene\lucene-core\2.0.0\lucene-core-2.0.0.jar;C:\PIC\projects\Archiva\archiva-discoverer\target\classes;C:\PIC\maven-repo-sonate\org\apache\maven\maven-artifact\2.0.5\maven-artifact-2.0.5.jar;C:\PIC\projects\Archiva\archiva-common\target\archiva-common-1.0-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\org\apache\maven\wagon\wagon-provider-api\1.0-beta-2\wagon-provider-api-1.0-beta-2.jar;C:\PIC\maven-repo-sonate\geronimo-spec\geronimo-spec-jta\1.0.1B-rc2\geronimo-spec-jta-1.0.1B-rc2.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-settings\2.0.5\maven-settings-2.0.5.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-digest\1.0\plexus-digest-1.0.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-utils\1.4\plexus-utils-1.4.jar;C:\PIC\maven-repo-sonate\commons-lang\commons-lang\2.2\commons-lang-2.2.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-container-default\1.0-alpha-20\plexus-container-default-1.0-alpha-20.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-repository-metadata\2.0.5\maven-repository-metadata-2.0.5.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\plexus-jdo2\1.0-alpha-8\plexus-jdo2-1.0-alpha-8.jar;C:\PIC\maven-repo-sonate\org\slf4j\slf4j-api\1.2\slf4j-api-1.2.jar;C:\PIC\projects\Archiva\archiva-indexer\target\classes;C:\PIC\maven-repo-sonate\commons-collections\commons-collections\3.2\commons-collections-3.2.jar;C:\PIC\maven-repo-sonate\org\codehaus\plexus\cache\plexus-cache-api\1.0-alpha-2-SNAPSHOT\plexus-cache-api-1.0-alpha-2-SNAPSHOT.jar;C:\PIC\maven-repo-sonate\net\sf\ehcache\ehcache\1.2.4\ehcache-1.2.4.jar;C:\PIC\maven-repo-sonate\org\apache\maven\maven-artifact-manager\2.0.5\maven-artifact-manager-2.0.5.jar;C:\PIC\maven-repo-sonate\commons-io\commons-io\1.2\commons-io-1.2.jar;C:\PIC\maven-repo-sonate\jpox\jpox\1.1.7\jpox-1.1.7.jar;C:\PIC\maven-repo-sonate\geronimo-spec\geronimo-spec-jta\1.0.1B-rc2\geronimo-spec-jta-1.0.1B-rc2.jar;C:\PIC\maven-repo-sonate\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar;C:\PIC\maven-repo-sonate\org\apache\bcel\bcel\5.2\bcel-5.2.jar;C:\PIC\maven-repo-sonate\javax\resource\connector\1.0\connector-1.0.jar;C:\PIC\maven-repo-sonate\javax\jdo\jdo2-api\2.0\jdo2-api-2.0.jar;C:\PIC\maven-repo-sonate\jakarta-regexp\jakarta-regexp\1.4\jakarta-regexp-1.4.jar;C:\PIC\maven-repo-sonate\jpox\jpox-enhancer\1.1.7\jpox-enhancer-1.1.7.jar;C:\PIC\maven-repo-sonate\ant\ant\1.6\ant-1.6.jar;C:\PIC\maven-repo-sonate\log4j\log4j\1.2.8\log4j-1.2.8.jar;C:\PIC\maven-repo-sonate\jpox\jpox\1.1.7\jpox-1.1.7.jar;C:\PIC\maven-2.0.5\core\plexus-container-default-1.0-alpha-9.jar;C:\PIC\maven-2.0.5\core\plexus-utils-1.1.jar;C:\PIC\maven-2.0.5\lib\maven-artifact-2.0.5.jar;C:\PIC\maven-2.0.5\lib\maven-plugin-api-2.0.5.jar
-Dlog4j.configuration=jar:file:/C:/PIC/maven-repo-sonate/org/codehaus/mojo/jpox-maven-plugin/1.1.7-SNAPSHOT/jpox-maven-plugin-1.1.7-SNAPSHOT.jar!/log4j.configuration
org.jpox.enhancer.JPOXEnhancer -v
C:\PIC\projects\Archiva\archiva-reports-standard\target\classes\org\apache\maven\archiva\reporting\model\package.jdo
[DEBUG] Exit code: 1
[DEBUG]
[DEBUG] Standard output from the JPox enhancer tool:
[DEBUG]
[INFO]
[DEBUG]
[ERROR]
[ERROR] Standard error from the JPox enhancer tool:
[ERROR]
[ERROR] La chaŒne de caractŠres suivante est trop longueÿ:
-cp
Re: [m2] Dashboard
you could read this issue : http://jira.codehaus.org/browse/MSITE-189 which coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 and i have release a snapshot version of my dashboard plugin : http://mojo.codehaus.org/dashboard-maven-plugin/ a newer version will be released soon as 1.0.1-SNASHOT David Vicente Rik Bosman wrote: Hi Laksman, Below the answer I recieved some months ago: *Hi Rik, We implemented this in the dashboard for maven1. However this does not exist for m2 yet. There are some thought on this on **http://docs.codehaus.org/display/MAVEN/Maven+Dashboard*http://docs.codehaus.org/display/MAVEN/Maven+Dashboard * (I've put a diagram of how I would view an architecture for this). I don't think much work has been done on this and most of the m2 dev team has focused on stabilizing/firming up the m2 core and core plugins. -Vincent * 2006/9/22, Lakshman Srilakshmanan [EMAIL PROTECTED] : Hi All, Is there a maven-dashboard-plugin as in maven 1.x for maven 2 ? Thanks Lakshman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--Dashboard-tf2315975s177.html#a8519299 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Quality Dashboard
yes , you could read this issue : http://jira.codehaus.org/browse/MSITE-189 to coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 and i have release a snapshot version of my dashboard plugin : http://mojo.codehaus.org/dashboard-maven-plugin/ a newer version will be released soon as 1.0.1-SNASHOT vmassol wrote: Well... :-) I have been wanting to write this dashboard stuff for a long time now but I've never found the time to do it... I've now joined the XWiki project and I think it would make a nice foundation for a quality/health dashboard. OTOH I still don't know when I'll have time to work on it. Don't hold your breath... That said, others on the list have already started working on a dashboard plugin and there's even been a submission for it I think. You may want to look at that. Thanks -Vincent -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: samedi 2 décembre 2006 02:08 To: Maven Users List Subject: Re: Quality Dashboard I went to a conference in Montreal today and from what Vincent said, it's going to be based on XWiki. I'll let him talk more about it by himself :) On 9/7/06, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, reading through http://idisk.maven.org/jvanzyl/Public/presos/Feynman.pdf, there is talk of Vincent's Dashboard. Is this a plugin that is going to be released soon? I think many users would like a quality dashboard that can generate graphs of your metrics (PMD, unit test pass rate, code coverage, ...) over time. regards, Wim ___ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Quality-Dashboard-tf2231524s177.html#a8502371 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Dashboard report available?
you could read this issue : http://jira.codehaus.org/browse/MSITE-189 which coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 and i have release a snapshot version of my dashboard plugin : http://mojo.codehaus.org/dashboard-maven-plugin/ a newer version will be released soon as 1.0.1-SNASHOT David Vicente Wayne Fay wrote: Yes. Go back to m1.0.2. ;-) In all seriousness, no one has created a similar dashboard (yet) for M2, at least I haven't seen it yet myself. Wayne On 1/2/07, Mick Knutson [EMAIL PROTECTED] wrote: I would like to create a multi project dashboard report like the one in m1.0.2 Is this possible? -- Thanks DJ MICK http://www.djmick.com http://www.myspace.com/mickknutson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--Dashboard-report-available--tf2909139s177.html#a8502372 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M1] QALab 0.9.1 and Maven plugin released
could you join this effort = http://jira.codehaus.org/browse/MSITE-189 ? Thanks David Benoitx wrote: Paul Could you show us your POM that generates the XML for Cobertura? We're working on the M2 plugin for QALab... Thanks Benoit Benoitx wrote: Paul Can you post this on the QALab Users list. We will look into it but could you confirm which JDK you are using? It is the first time we see that one... Regards Benoit Paul Balm wrote: Benoitx wrote: ObjectLab is pleased to announce the release of version 0.9.1 (slowly getting closer to v 1.0) of QALab and its Maven 1.x plugin. I'm trying to use this plug-in under Maven 1.1-beta2, to agregate stats from Cobertura and PMD, I'm getting parser errors on the XML output of pmd-raw-report.xml and cobertura.xml respectively. Because it happens on both these files, I think it's my maven set-up (the XML parser that I use e.g.), and that the PMD and Cobertura reports are fine. I can also see those when I generate maven site -- they are ok. I have the dependencies that QALab specificies in my project.xml (on http://qalab.sourceforge.net/maven/dependencies.html), but of course additionally a bunch of other stuff that my project needs, so I'm worried this might screw things up. Anyway, below this message I pasted the output with errors. I think it goes wrong 12 lines into the output that I'm showing (on the PMD XML(, and the same error two lines below that on the Cobertura XML. I also append a list of the libraries that I'm using (the dependencies from my project.xml). Any suggestions more than welcome, 'cause I'm stuck! Thanks! Paul maven cobertura pmd [...ok...] maven -e maven-qalab-plugin:report [...] maven-qalab-plugin:report: [echo] QALab Report. Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:merge: [echo] QALab Merge!... [echo] No Checkstyle file to process (/home/pbalm/dev/isoc/simbad/target/checkstyle/checkstyle-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/pmd-raw-report.xml... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] No FindBugs file to process (/home/pbalm/dev/isoc/simbad/target/findbugs-raw-report.xml). [echo] No Simian file to process (/home/pbalm/dev/isoc/simbad/target/simian-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Line... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Branch... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:charts: [echo] QALab CHARTS! [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] Cobertura Chart [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] QALab SUMMARY XDOC for CHARTS! ... BUILD FAILED org.apache.commons.jelly.JellyTagException: file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:35:-1: jsl:stylesheet file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:89:-1: x:sort You must define an attribute called 'list' for this tag. at org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:704) at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:668) at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:644) at org.apache.commons.jelly.tags.core.IncludeTag.doTag(IncludeTag.java:101) [...more...] == Dependencies: (declared in this order) !-- As required by QALab: -- artifactIdant/artifactId version1.6.4/version artifactIdjcommon/artifactId version0.9.6/version artifactIdjfreechart/artifactId version0.9.21/version groupIdnet.objectlab/groupId artifactIdqalab/artifactId version0.9.1/version artifactIdxalan/artifactId version2.7.0/version artifactIdxerces/artifactId version2.4.0/version artifactIdxercesImpl/artifactId version2.6.2/version !-- Private libraries -- (private code here) !--
Re: [M1] QALab 0.9.1 and Maven plugin released
Hi, I think that the idea is to choose a dashboard plugin (qalab for example) for maven 2 and all other developers help to improve it instead of to develop many plugins. If Qalab is the most advanced plugin, it can be choosen as dashboard reference for Maven 2. Benoitx wrote: Dear David, We really need to have 188 fixed... http://jira.codehaus.org/browse/MSITE-188 It is the last hurdle for QALab. I will keep an eye on 189 too but we cannot become too specific to Maven 2, QALab works accross ant, Maven 1 and now (in beta soon) Maven 2. I find QALab complementary to the dashboard as we keep track of similar stats over time rather than snapshot. We've been using it for a few years and only released it open source in June 05. As I said, we will keep an eye but I prefer to be frank and say that it will be difficult to dedicate a lot of time to it due to massive amount of work (real work and open source: QALab, JTreeMap, ObjectLabKit etc all on sourceforge by the way...). Sorry, Benoit dvicente wrote: could you join this effort = http://jira.codehaus.org/browse/MSITE-189 ? Thanks David Benoitx wrote: Paul Could you show us your POM that generates the XML for Cobertura? We're working on the M2 plugin for QALab... Thanks Benoit Benoitx wrote: Paul Can you post this on the QALab Users list. We will look into it but could you confirm which JDK you are using? It is the first time we see that one... Regards Benoit Paul Balm wrote: Benoitx wrote: ObjectLab is pleased to announce the release of version 0.9.1 (slowly getting closer to v 1.0) of QALab and its Maven 1.x plugin. I'm trying to use this plug-in under Maven 1.1-beta2, to agregate stats from Cobertura and PMD, I'm getting parser errors on the XML output of pmd-raw-report.xml and cobertura.xml respectively. Because it happens on both these files, I think it's my maven set-up (the XML parser that I use e.g.), and that the PMD and Cobertura reports are fine. I can also see those when I generate maven site -- they are ok. I have the dependencies that QALab specificies in my project.xml (on http://qalab.sourceforge.net/maven/dependencies.html), but of course additionally a bunch of other stuff that my project needs, so I'm worried this might screw things up. Anyway, below this message I pasted the output with errors. I think it goes wrong 12 lines into the output that I'm showing (on the PMD XML(, and the same error two lines below that on the Cobertura XML. I also append a list of the libraries that I'm using (the dependencies from my project.xml). Any suggestions more than welcome, 'cause I'm stuck! Thanks! Paul maven cobertura pmd [...ok...] maven -e maven-qalab-plugin:report [...] maven-qalab-plugin:report: [echo] QALab Report. Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:merge: [echo] QALab Merge!... [echo] No Checkstyle file to process (/home/pbalm/dev/isoc/simbad/target/checkstyle/checkstyle-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/pmd-raw-report.xml... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] No FindBugs file to process (/home/pbalm/dev/isoc/simbad/target/findbugs-raw-report.xml). [echo] No Simian file to process (/home/pbalm/dev/isoc/simbad/target/simian-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Line... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Branch... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:charts: [echo] QALab CHARTS! [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] Cobertura Chart [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] QALab SUMMARY XDOC for CHARTS! ... BUILD FAILED org.apache.commons.jelly.JellyTagException: file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:35:-1: jsl:stylesheet file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:89:-1: x:sort You must define an attribute called 'list' for this tag. at org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.java:127
Re: [M1] QALab 0.9.1 and Maven plugin released
at this time, my only solution is to generate in 2 phases mvn clean site = to generate the site with all links mvn dashboard-report:dashboard = to generate again the dashboard with good and last values of other reports Benoitx wrote: Dear David, We really need to have 188 fixed... http://jira.codehaus.org/browse/MSITE-188 It is the last hurdle for QALab. I will keep an eye on 189 too but we cannot become too specific to Maven 2, QALab works accross ant, Maven 1 and now (in beta soon) Maven 2. I find QALab complementary to the dashboard as we keep track of similar stats over time rather than snapshot. We've been using it for a few years and only released it open source in June 05. As I said, we will keep an eye but I prefer to be frank and say that it will be difficult to dedicate a lot of time to it due to massive amount of work (real work and open source: QALab, JTreeMap, ObjectLabKit etc all on sourceforge by the way...). Sorry, Benoit dvicente wrote: could you join this effort = http://jira.codehaus.org/browse/MSITE-189 ? Thanks David Benoitx wrote: Paul Could you show us your POM that generates the XML for Cobertura? We're working on the M2 plugin for QALab... Thanks Benoit Benoitx wrote: Paul Can you post this on the QALab Users list. We will look into it but could you confirm which JDK you are using? It is the first time we see that one... Regards Benoit Paul Balm wrote: Benoitx wrote: ObjectLab is pleased to announce the release of version 0.9.1 (slowly getting closer to v 1.0) of QALab and its Maven 1.x plugin. I'm trying to use this plug-in under Maven 1.1-beta2, to agregate stats from Cobertura and PMD, I'm getting parser errors on the XML output of pmd-raw-report.xml and cobertura.xml respectively. Because it happens on both these files, I think it's my maven set-up (the XML parser that I use e.g.), and that the PMD and Cobertura reports are fine. I can also see those when I generate maven site -- they are ok. I have the dependencies that QALab specificies in my project.xml (on http://qalab.sourceforge.net/maven/dependencies.html), but of course additionally a bunch of other stuff that my project needs, so I'm worried this might screw things up. Anyway, below this message I pasted the output with errors. I think it goes wrong 12 lines into the output that I'm showing (on the PMD XML(, and the same error two lines below that on the Cobertura XML. I also append a list of the libraries that I'm using (the dependencies from my project.xml). Any suggestions more than welcome, 'cause I'm stuck! Thanks! Paul maven cobertura pmd [...ok...] maven -e maven-qalab-plugin:report [...] maven-qalab-plugin:report: [echo] QALab Report. Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:merge: [echo] QALab Merge!... [echo] No Checkstyle file to process (/home/pbalm/dev/isoc/simbad/target/checkstyle/checkstyle-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/pmd-raw-report.xml... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] No FindBugs file to process (/home/pbalm/dev/isoc/simbad/target/findbugs-raw-report.xml). [echo] No Simian file to process (/home/pbalm/dev/isoc/simbad/target/simian-raw-report.xml). [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Line... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 [echo] QALab Merge! /home/pbalm/dev/isoc/simbad/target/docs/cobertura/coverage.xml Branch... [mergestat] org.xml.sax.SAXNotSupportedException: Feature: http://xml.org/sax/features/external-general-entities State: false [mergestat] Files: 0 Statistics:0 Tag library requested that is not present: 'qalab' in plugin: 'maven-qalab-plugin-0.9.0' maven-qalab-plugin:charts: [echo] QALab CHARTS! [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] Cobertura Chart [buildchart] java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser [echo] QALab SUMMARY XDOC for CHARTS! ... BUILD FAILED org.apache.commons.jelly.JellyTagException: file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:35:-1: jsl:stylesheet file:/home/pbalm/.maven/cache/maven-qalab-plugin-0.9.0/plugin-resources/qalab-chart-xdoc.jsl:89:-1: x:sort You must define an attribute called 'list' for this tag. at org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.java:127) at org.apache.commons.jelly.impl.TagScript.run
Re: Aggregate plugin that runs after each module's reports
Yes, me too. i try to develop the same plugin and i have the problem. If i put my report at the end of plugins list in reporting section, it works for 1 project but doesn't work for projects with module. see my last posts : http://www.nabble.com/-m2--Dashboard-report-plugin-tf2338270.html#a6506403 or http://www.nabble.com/-m2--lifecycle-design-tf2350045.html the only one solution is to declare plugin in reporting section: with this you have the item menu in the generated site and re-generated your dashboard after site generation as : mvn compile site dashboard-report:report if your plugin is dashboard-report with goal report as i do it's the the same problem as Clover plugin as described in JIRA: http://jira.codehaus.org/browse/MNG-2184 J.J.B. Rentrop wrote: It's good to hear that there is someone who is also working on it. I'm in favour of focusing the work and have this available for everyone. Your solution works for projects that have packaging=jar but not for projects that consists of multiple modules (packaging=pom). It can affect the sequence of the plugins that are ran for each site but it can't make the plugin execute after the site phase for each module has been executed. Best regards, Julien - Original Message - From: Gisbert Amm [EMAIL PROTECTED] Date: Thursday, October 19, 2006 12:17 pm Subject: Re: Aggregate plugin that runs after each module's reports To: Maven Users List users@maven.apache.org I'm currently writing almost the same plugin, formerly (in the Maven 1 world) known as Dashboard Plugin. Isn't that funny (I think it isn't)? Would it probably not be better to focus such efforts within the Maven project itself rather than having each company writing it's own Dashboard plugin for Maven 2? Your question: I simply wrote the plugin section for this plugin behind all others in the POM and that seems to work. Of course, one has to check if the required XML lies there as expected. ATM, I'm simply leaving the respective table cells in the generated report empty if that should happen. -Gisbert J.J.B. Rentrop wrote: Hi all, I'm looking for ways to enable an aggregate report for multi module projects for tools like checkstyle, cobertura, findbugs, surefire etc. One approach I'm trying is to first generate all reports and xml data files for each module and afterwards loop through each module, read their xml output file and create an aggregation report based on that data. The problem I face is that my aggregation MavenReport executes before the reports of each modules has been executed. When I run mvn site it will create an empty aggregate report, because it's unable to gather the data from each module. If I run it a second time it will work because then the data files of each module are available. Is there a way to make my aggregation MavenReport execute after the reports of all modules have been generated? I have tried some annotations but it didn't work. - 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] -- View this message in context: http://www.nabble.com/Aggregate-plugin-that-runs-after-each-module%27s-reports-tf2472384.html#a6894274 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire-Plugin: how to get aggregated XML?
i only know Maven 2 but in maven 2 surefire generates this xml. see in directory /myProject/target/surefire-reports, you must have TEST-.yyy.xml Gisbert Amm-3 wrote: A week passed since I've posted this question and I got no reply so far. Can anyone say something about it, please? -Gisbert Gisbert Amm wrote: Hi, in Maven1 the Junit Plugin wrote the test data aggregated into a file named TESTS-TestSuites.xml. How can I achieve this with the Maven2 Surefire plugin? -Gisbert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--Surefire-Plugin%3A-how-to-get-aggregated-XML--tf2430953.html#a6894432 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire-Plugin: how to get aggregated XML?
ok, i haven't understood. But why do you want this aggregated xml file ? Gisbert Amm-3 wrote: That's not what I meant. The TEST-.yyy.xml files are there, indeed, but no file with *aggregated* test results. Of course I can go through the single files and collect errors and failures from there (that's what I actually do ATM). But the Surefire plugin could do that much more efficent during it's execution and write it to a neat XML file afterwards as it was in Maven 1. -Gisbert dvicente wrote: i only know Maven 2 but in maven 2 surefire generates this xml. see in directory /myProject/target/surefire-reports, you must have TEST-.yyy.xml Gisbert Amm-3 wrote: A week passed since I've posted this question and I got no reply so far. Can anyone say something about it, please? -Gisbert Gisbert Amm wrote: Hi, in Maven1 the Junit Plugin wrote the test data aggregated into a file named TESTS-TestSuites.xml. How can I achieve this with the Maven2 Surefire plugin? -Gisbert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gisbert Amm Softwareentwickler Infrastruktur WEB.DE GmbH Brauerstraße 48 · D-76135 Karlsruhe Tel. +49-721-91374-4224 · Fax +49-721-91374-2740 [EMAIL PROTECTED] · http://www.web.de/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--Surefire-Plugin%3A-how-to-get-aggregated-XML--tf2430953.html#a6896130 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Dashboard report plugin
I have created a Dashboard report plugin for Maven2. My problem is : How to configure my plugin to generate the dashboard report only after all reports have been generated. In my DashBoardReportMojo which extends AbstractMavenReport, i put this mojo metadata as class-level annotation : @phase post-site but my report has been generated during the site phase instead of at the end of all reports generation. Can you help me ? Thanks a lot -- View this message in context: http://www.nabble.com/-m2--Dashboard-report-plugin-tf2338270.html#a6506403 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] assembly filters
yes i do that
in my assembly file , i have :
files
file
sourcerelease/bin/loganalyzer.bat/source
outputDirectorybin/outputDirectory
filteredtrue/filtered
/file
/files
but in my zipfile, the loganalyzer.bat is not filtered.
I missed something ?
How to obtain the complete list of pom properties which i can use ?
in my command file, i use ${project.version}
--
View this message in context:
http://www.nabble.com/-M2--assembly-filters-t1797081.html#a4931441
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] assembly filters
i find the reason
i must use ${pom.version} instead of ${project.version}
thanks for your help
--
View this message in context:
http://www.nabble.com/-M2--assembly-filters-t1797081.html#a4933025
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M2] assembly filters
For my project, i have a command file to launch my app (.bat for windows and
.sh for unix)
During assembly goal, i want to use my maven project properties ( as version
value) to filter those 2 files.
example : in my command file i have
set LOGANALYZER_HOME=%ProgramFiles%\logAnalyzer-{project.version}
and my zip , i want to have
set LOGANALYZER_HOME=%ProgramFiles%\logAnalyzer-0.1
How to do that ?
--
View this message in context:
http://www.nabble.com/-M2--assembly-filters-t1797081.html#a4897216
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
