[ANN] Maven Dashboard Plugin 1.6 released
We are pleased to announce the Maven Dashboard Plugin 1.6 release! http://maven.apache.org/reference/plugins/dashboard/ Generate a dashboard containing global statistics about other maven reports Changes in this version include: New Features: o Added Maven Change Log aggregators. Issue: MPDASHBOARD-16. o Added Maven Tasks List aggregators. Issue: MPDASHBOARD-16. Fixed bugs: o Added Findbugs aggregators which were supposed to have been committed in the previous version but which somehow were not... Issue: MPDASHBOARD-16. To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.6 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.6.jar Have fun! -The Maven Dashboard Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Dashboard Plugin 1.5 released
The maven team is pleased to announce the Maven Dashboard Plugin 1.5 release! http://maven.apache.org/reference/plugins/dashboard/ Generate a dashboard containing global statistics about other maven reports Changes in this version include: New Features: o Added dashboard report example to the Dashboard plugin web site. o Added new fbfilesaggregator that computes FindBugs total number of files with violations. Issue: MPDASHBOARD-13. Thanks to Nascif Abousalh-Neto. o Added new fbviolationsaggregator that computes FindBugs total number of violations. Issue: MPDASHBOARD-13. Thanks to Nascif Abousalh-Neto. o Added percentage bar graphs to the report. Issue: MPDASHBOARD-3. Thanks to Nascif Abousalh-Neto. o Added new jcoveragelocaggregator that computes JCoverage total lines of code. Issue: MPDASHBOARD-12. Thanks to Thomas Recloux. o Added new jcoveragelipcaggregator that computes JCoverage lines percentage. Issue: MPDASHBOARD-11. Thanks to Thomas Recloux. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.5 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.5.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Checkstyle Plugin 2.5 released
The maven team is pleased to announce the Maven Checkstyle Plugin 2.5 release! http://maven.apache.org/reference/plugins/checkstyle/ Changes in this version include: New Features: o Added new maven.checkstyle.suppressions.fileproperty. o Added generation of a Checkstyle RSS feed. Fixed bugs: o Fix : Build failed if target directory and License file didn't exist. Issue: MPCHECKSTYLE-21. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-checkstyle-plugin -Dversion=2.5 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-checkstyle-plugin-2.5.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Clover Plugin 1.6 released
The maven team is pleased to announce the Maven Clover Plugin 1.6 release! http://maven.apache.org/reference/plugins/clover/ Changes in this version include: New Features: o Added ability for users to specify their own Clover license file by overriding the new maven.clover.license.path property. o Added new clover:test-single goal to execute a single test case and to view the test coverage result directly using the Clover Swing viewer. This is useful if you wish to quickly see the action that a single unit test has on the code it tests. Issue: MPCLOVER-9. Fixed bugs: o The default compiler was not reset after the execution of the clover:report goal. Issue: MPCLOVER-23. o Now using maven:get and maven:set. Issue: MPCLOVER-19. o When executing clover:on and clover:off, modify the maven.build.dest property value in the Root context of all plugins so that the value change is available in all Maven plugins. o Prevented the clover:on goal from failing when there are no unit tests sources available. Changes: o Made the following goals public by documenting them: clover:report, clover:on, clover:off, clover:test, clover:test-single. o The clover:report goal does not call the tests anymore. It only generates Clover reports. o Updated to Clover Ant 1.3_01. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.6 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-clover-plugin-1.6.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Dashboard Plugin 1.4 released
The maven team is pleased to announce the Maven Dashboard Plugin 1.4 release! http://maven.apache.org/reference/plugins/dashboard/ Generate a dashboard containing global statistics about other maven reports Changes in this version include: New Features: o Added new Checkstyle File aggregator and PMD aggregators (count of violations and count of files with violations). Issue: MPDASHBOARD-7. Thanks to Paul Spencer. Fixed bugs: o Fixed documentation regarding the maven.dashboard.rungoalsproperty. Issue: MPDASHBOARD-8. Thanks to Carlos Sanchez. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.4 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.4.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Announcement Plugin 1.3 released
The maven team is pleased to announce the Maven Announcement Plugin 1.3 release! http://maven.apache.org/reference/plugins/announcement/ The Announcement plugin generates release announcements. It uses the information found in both the POM and in the changes.xml file to generate the announcement text. Changes in this version include: New Features: o Added check to verify that the POM has a versionelement for the announcement to be generated. Issue: MPANNOUNCEMENT-14. Thanks to Felipe Leme. o Added new optional maven.announcement.encodingproperty that defines which charset encoding to use to generate the text announcement (defaults to UTF-8). Issue: MPANNOUNCEMENT-13. Thanks to Felipe Leme. o Added new announcement:mailgoal to automatically send the generated announcement by email. Issue: MPANNOUNCEMENT-9. Thanks to Felipe Leme. o Added new optional maven.announcement.stylesheet.pathproperty that defines what stylesheet to use to generate the text announcement. Issue: MPANNOUNCEMENT-11. Thanks to Felipe Leme. Fixed bugs: o Fixed error message when current version is not available at xdocs/changes.xml. Issue: MPANNOUNCEMENT-12. Thanks to Felipe Leme. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-announcement-plugin -Dversion=1.3 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-announcement-plugin-1.3.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Announcement Plugin 1.3-SNAPSHOT released
The maven team is pleased to announce the Maven Announcement Plugin 1.3-SNAPSHOT release! http://maven.apache.org/reference/plugins/announcement/ The Announcement plugin generates release announcements. It uses the information found in both the POM and in the changes.xml file to generate the announcement text. Changes in this version include: New Features: o Added new announcement:mail goal to automatically send the generated announcement by email. Issue: MPANNOUNCEMENT-9. Thanks to Felipe Leme. o Added new optional maven.announcement.stylesheet.pathproperty that defines what stylesheet to use to generate the text announcement. Issue: MPANNOUNCEMENT-11. Thanks to Felipe Leme. Fixed bugs: o Fixed error message when current version is not available at xdocs/changes.xml. Issue: MPANNOUNCEMENT-12. Thanks to Felipe Leme. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-announcement-plugin -Dversion=1.3-SNAPSHOT For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-announcement-plugin-1.3-SNAPSHOT.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of J2EE related plugins
dIon, [snip] > > What's the plan? > ear processing is in the ear plugin. > war processing is in the war plugin. > ejb processing is in the ejb plugin. > jar processing is in the java plugin. > appserver processing is in the appserver plugin. What do you call appserver processing? For example, I'd like to develop a jboss plugin that creates a valid jboss deployment configuration (i.e. what you'll find in jbosshome/server/). I had planned to create a jboss plugin for that. Then, if I want to add a goal to start/stop jboss, where does it go: in the appserver plugin or in this jbossplugin? I think containers are pretty different in their configuration, deployment features, etc and that it may warrants a separate plugin for each container. However, there are pros and cons for both strategies (one plugin vs N plugins). Ideas? Thanks -Vincent > > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > > > - > 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: Why no multiple locations of sources? ( was Re: inter-project dependencies for the Eclipse plugin )
En réponse à Raphaël Piéroni <[EMAIL PROTECTED]>: > Hello maven devs and users, > > i dunno why splitting a source tree but as said before maven at the > moment as multiple trees : one for tests, one for java, one for > aspects. > > but i'll see a new one that can be added : aspect-test because some > aspects are for production execution and some others for tests. > > in such a case : > src/aspectj > src/java > src/test > src/aspectjtest > > when using : > java:compile : use src/java > aspectj : use src/java+src/aspectj > test : use src/test after java:compile or aspectj > test:aspect : use all for compile as we can have aspects that modify he > "production" code in the aspectjtest directory (eg tracing issues) > > do that make sense ? Absolutely. Definition of src directories is done qt the plugin level. For example, the Cactus plugin defines a src/test-cactus directory. The PatternTestig Maven plugin (http://patterntesting.sf.net) defines a src/test- aspect directory. -Vincent > > R > > = > > | Raphaël Piéroni | > | 33+ 223 351 354 | > | mailto:[EMAIL PROTECTED]| > | http://www.dexem.com | > | mailing:[EMAIL PROTECTED] | > > > ___ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! > Yahoo! Mail : http://fr.mail.yahoo.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: How to use Cactus to test EJB?
Quoting Willie Vu <[EMAIL PROTECTED]>: > Vincent, > > I dig up some threads where you said EJB will be a focus for Cactus 1.6. > Is > there any initial work someone is working on? Not much. There has been the start of an EJB redirector in the past but it has n't been integrated. > > For the time being, can you suggest some ideas to implement a > workaround > solution for EJB unit test in Cactus/Maven? The workaround is to patch the Cactus/Maven plugin by adding support for EAR. More specifically this means adding: - cactification of an EAR (the script already has cactification of a WAR). - modify the container-specific scripts to support deploying an EAR (for JBoss it is almost transparent as WAR and EAR are deployed in the same directory). It shouldn't be too hard to do. I can certainly provide guidance if you're interested in participating! Thanks -Vincent > > -- > Willie Vu > > > > > -Original Message- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 31, 2003 1:35 > > To: 'Maven Users List' > > Subject: RE: How to use Cactus to test EJB? > > > > > > Unit testing EJB is not yet supported by the Cactus plugin for Maven. > > > > Thanks > > -Vincent > > > > > -Original Message- > > > From: Willie Vu [mailto:[EMAIL PROTECTED] > > > Sent: 31 March 2003 04:24 > > > To: 'Maven Users List' > > > Subject: How to use Cactus to test EJB? > > > > > > Is there any documentation on how to use Maven Cactus plugin to > test > > EJB? > > > > > > -- > > > Willie Vu > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pmd plugin, maven b8-9
Hi Fabian, It also fails for me (even after adding the missing dependencies). I've just sent a few bug reports to the maven-plugins WRT the issues. I hope someone listens to it at the other end... My feeling is that the PMD plugin should be included in Maven CVS so it has a higher chance of staying up to date with Maven. -Vincent Quoting Fabian Ritzmann <[EMAIL PROTECTED]>: > Hi, > > I had originally posted this to the maven-plugins mailing list but that > list seems to be dead. Sorry if you get this twice: > > I tried to run the pmd plugin 0.5 with PMD 1.04 and a three week old > version of Maven from CVS and failed miserably. I ran into all sorts of > class loading issues. I managed to work around some of them by stating > dependencies in the plugin project.xml, copying libraries to my local > maven repository, and adding explicit classpath entries to the > plugin.jelly. But it still doesn't run and I'm sure I wasn't supposed > to > make all these hacks. :-) > > Has anybody managed to run the plugin with a recent Maven and PMD 1.04 > and is there anything I need to be aware of? I read the archived > messages on the maven users list on similar topics, but it seems that > too much has changed in the meantime. > > Fabian > > > > - > 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: Problem with Cactus and jboss-3.0.4_tomcat-4.1.12
oops.. I forgot to ask if you are using a Maven built from CVS HEAD or a release version. My previous email was about the CVS HEAD version of the Cactus plugin. -Vincent Quoting Willie Vu <[EMAIL PROTECTED]>: > I am trying to use cactus plugin with jboss-3.0.4_tomcat-4.1.12 to test > EJBs. I > keep running into the following error: > > [java] 17:47:42,245 ERROR [URLDeploymentScanner] Failed to deploy: > [EMAIL PROTECTED] > url=fil > e:/E:/java/jboss-3.0.4_tomcat-4.1.12/server/default/deploy/tomcat41- service.xml, > deployedLastModified=0 } > [java] org.jboss.deployment.DeploymentException: instantiating > org.jboss.web.catalina.EmbeddedCatalinaService41 failed: > java.lang.NoClassDefFoundE > rror: org/apache/catalina/Context; - nested throwable: > (RuntimeErrorException: > instantiating org.jboss.web.catalina.EmbeddedCatalinaService41 failed: > java.lang.NoClassDefFoundError: org/apache/catalina/Context > [java] Cause: java.lang.NoClassDefFoundError: > org/apache/catalina/Context) > [java] at > org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:155) > [java] at > org.jboss.system.ServiceController.install(ServiceController.java:225) > [java] at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown > Source) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.jav > a:25) > [java] at java.lang.reflect.Method.invoke(Method.java:324) > [java] at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher > .java:284) > > > Any idea? > > > -- > Willie Vu > > > - > 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: Problem with Cactus and jboss-3.0.4_tomcat-4.1.12
Hi Willie, ATM, the Cactus plugin works with the JBoss/Jetty combo. It has not been tested with JBoss/Tomcat and thus it is not supported. That said, I would be glad to add this support. In your specific case, it means it is missing the tomcat jars in the classpath. FYI, the way we start jboss is with the following: (full script is located here: http://cvs.apache.org/viewcvs/jakarta- cactus/integration/ant/src/scripts/j2ee13/). Thanks -Vincent Quoting Willie Vu <[EMAIL PROTECTED]>: > I am trying to use cactus plugin with jboss-3.0.4_tomcat-4.1.12 to test > EJBs. I > keep running into the following error: > > [java] 17:47:42,245 ERROR [URLDeploymentScanner] Failed to deploy: > [EMAIL PROTECTED] > url=fil > e:/E:/java/jboss-3.0.4_tomcat-4.1.12/server/default/deploy/tomcat41- service.xml, > deployedLastModified=0 } > [java] org.jboss.deployment.DeploymentException: instantiating > org.jboss.web.catalina.EmbeddedCatalinaService41 failed: > java.lang.NoClassDefFoundE > rror: org/apache/catalina/Context; - nested throwable: > (RuntimeErrorException: > instantiating org.jboss.web.catalina.EmbeddedCatalinaService41 failed: > java.lang.NoClassDefFoundError: org/apache/catalina/Context > [java] Cause: java.lang.NoClassDefFoundError: > org/apache/catalina/Context) > [java] at > org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:155) > [java] at > org.jboss.system.ServiceController.install(ServiceController.java:225) > [java] at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown > Source) > [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.jav > a:25) > [java] at java.lang.reflect.Method.invoke(Method.java:324) > [java] at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher > .java:284) > > > Any idea? > > > -- > Willie Vu > > > - > 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: Sharing goals between maven.xml files w/o a plugin
Hi James, See my proposal of this morning for sharing maven.xml. That would allow you to share common custom goals. -Vincent Quoting James CE Johnson <[EMAIL PROTECTED]>: > Heya, > > I've got a project with a half-dozen sub-projects. Several of those > (not > all) need to share some common custom goals. I don't really want to > create > a plugin because the goals are specific to this one project. Is there > another way to make shared goals available? > > Thanks, > J > > > - > 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: Container start/stop + packaging (was RE: WebLogic Server plugin)
Hi Michal, Quoting "michal.maczka" <[EMAIL PROTECTED]>: > > > > -Original Message- > > From: Aslak Hellesøy [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 25, 2003 10:46 PM > > To: Maven Users List > > Subject: RE: Container start/stop + packaging (was RE: WebLogic > Server > > plugin) [snip] > > As I understand the purpose of at Jakarta Commons, components developed > under this initiative > should be highly reusable across many projects. > This set of API which we are discussing id rather not that > "frequently needed". > > Maybe Maven itself can open an umbrella for development of such > subprojects? > I don't think it belongs to Maven. In the same way as I wouldn't put it under the Eclipse project umbrella. It is something more generic that can be used by Maven plugins, by Eclipse plugins, etc. Putting it under a given tool's umbrella is dangerous as it may incite tying it to that tool thus making it not reusable by other projects. We've had this example with Ant and the Zip task for example. I would rather have seen the zip code as a commons project and then write a wrapper for Ant than the other way around. > I don't know what are the objectives for Maven project. > But I would like to see what we call Maven now, more thinner and > equipped > only with > set of real core plugins. Other plugins should be easily > downloadable/deployable > only on user demand. sure. This is the direction. > > I think if such separation would happen why not to create subproject > directly under Maven? I don't view this project as a Maven plugin, nor being Maven related. It is as much Centipede-related, Ant-related as it is Maven-related... That said, I do agree that there will be a Maven plugin that *wraps* around this API to make it easily usable by Maven users. > > I see possibly a lot of categories of projects: > > 0) Everything related to repository access > 1) Appserver Control API > 2) Version Control API (unified access to CVS, SVN, VSS ) etc > 3) Issue Tracking System API (pure Java API for accessing JIRA, Scarab > etc) > 4) Continuous integration build system > 5) Maven IDE > 6) etc.. I agree with all of these but only for plugins. I believe we should be *very* careful not to implement business logic in the plugin itself. In other word, the plugin should wrap existing frameworks. For example, the checkstyle plugin wraps the checkstyle framework and that is good. Same with all the others. This provides reusability. Things that could be separated from Maven (and this is the plan as defined by Jason) are for example: - SCM code - API for downloading/uploading to a remote repository What do yout think? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
