RE: Checkstyle plugin Maven 2
You set them in the pom.xml file. Should like that
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.1/version
configuration
configLocation
{$basedir}/src/main/config/checkstyle.xml
/configLocation
/configuration
/plugin
/plugins
reporting
Hth,
-Stefan
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 5:24 PM
To: users@maven.apache.org
Subject: Checkstyle plugin Maven 2
Does anyone know how the maven 2 checkstyle.properties are set ?
In maven 1.x they were provided in a file checkstyle.properties
Tx
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Forcing a recompile of Java sources
Hi Pieter,
just put it directly in your maven.xml:
project xmlns:j=jelly:core xmlns:m=jelly:maven
xmlns:ant=jelly:ant xmlns:util=jelly:util
preGoal name=java:compile
attainGoal name=generatesomecode/
ant:path id=gen.src.dir location=${maven.build.src}/
m:addPath id=maven.compile.src.set refid=gen.src.dir/
/preGoal
/project
The Pre-Goal for java:compile will make sure that the goal
generatesomecode will be called before the compile is performed. In a
way it is as decorator for java:compile...
-Stefan
--
http://www.kleineikenscheidt.de/stefan
-Original Message-
From: Pieter Van Gorp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 11:45 PM
To: Stefan Kleineikenscheidt
Cc: [EMAIL PROTECTED]
Subject: Re: Forcing a recompile of Java sources
Hi Stefan,
sounds interesting, we'll try it out!
Still, it's not completely clear to me where I should place the
preGoal tag. Should it be nested in the AndroMDA one? Seeing the
attainGoal tag, I would say not but where does it belong otherwise?
Perhaps it should be nested in the goal that is dedicated to compiling
the generated sources? In that case it would indeed be the equivalent
of our ANT build-gensrc target... on the other hand I wouldn't know
what the body of the Maven rule would be: what would the goal contain
besides the preGoal you mention?
Thanks for your insight,
Pieter.
On Wed, 23 Feb 2005 21:04:37 +0100, Stefan Kleineikenscheidt
[EMAIL PROTECTED] wrote:
Hi Pieter,
i prefer to clearly separate generated sources from the
manually edited
sources. Therefore we generate our sources to
${maven.build.src} and
add this path for java:compile like this:
preGoal name=java:compile
attainGoal name=generatesomecode/
ant:path id=gen.src.dir location=${maven.build.src}/
maven:addPath id=maven.compile.src.set
refid=gen.src.dir/
/preGoal
('generatesomecode' would be replaced by the andromda goal
in your case)
Hope this helps,
-Stefan
--
http://www.kleineikenscheidt.de/stefan
-Original Message-
From: Pieter Van Gorp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:04 PM
To: Maven Users List; Brett Porter
Subject: Re: Forcing a recompile of Java sources
Hi Brett,
thanks for your reply.
I'm not sure what you are using to generate sources
I'm using AndroMDA (http://andromda.sourceforge.net/) to
generate Java
sources from UML models.
but it must be
adding the generated sources to the source path
(maven:addPath /),
Do you mean that we have to extend the sourceDirectory
from the build
tag in project.xml by telling Maven the generated sources
are located
elsewhere? In fact, the sources are already generated in
project.xml's sourceDirectory itself so I thought that the regular
build goal would work for the AndroMDA-generated sources
as well as
for non-generated sources... Where am I wrong?
You'll need to get that tag called first - either by adding the
preGoal yourself, or calling the appropriate goal from
the source
generator.
The goal that is not working as it should is 'build'.
AndroMDA has
already done it's job and the generated sources have been modified
manually (for displaying debug output) so should be
recompiled without
running AndroMDA again. Does this comply with your solution?
Best regards,
Pieter.
On Wed, 23 Feb 2005 21:43:44 +1100, Brett Porter
[EMAIL PROTECTED] wrote:
I'm not sure what you are using to generate sources,
but it must be
adding the generated sources to the source path
(maven:addPath /),
and when that is skipped, it is not attempting to compile
them at all.
You'll need to get that tag called first - either by adding the
preGoal yourself, or calling the appropriate goal from
the source
generator.
- Brett
On Wed, 23 Feb 2005 10:49:21 +0100, Pieter Van Gorp
[EMAIL PROTECTED] wrote:
Hi all,
if I should give any extra info to get this question
answered, please
let me know.
In the meanwhile, I'm driving the on-demand
recompilation of the
selected sources (the generated ones) from ANT again. Is
it perhaps
impossible (or undesirable) to use Maven exclusively (=
only maven.xml
and project.xml but no ANT build.xml) for our project
requirements?
Kind regards,
Pieter Van Gorp
http://motmot.sourceforge.net/
-- Forwarded message --
From: Pieter Van Gorp [EMAIL PROTECTED]
Date: Mon, 21 Feb 2005 21:08:02 +0100
Subject: Forcing a recompile of Java sources
To: users@maven.apache.org
Hi, since recently we've moved the build process of our
MDA tool from
ANT to Maven. I can't find out how we should set up our
build process
RE: Questions about Dependencies
-Original Message- From: Scott Goldstein [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 12, 2005 6:57 AM To: users@maven.apache.org Subject: Questions about Dependencies [...] 2.One thing that I'm slightly uncomfortable about concerning the dependency system, is that the Maven remote repository acts as a middle man, downloading jars from the original site and storing it for maven use. Some of the jars have been renamed. I'm assuming that no other changes have been made, but that requires a little bit of a trust factor. I know Maven has a way to configure a dependency to download from the original site, but it doesn't always work because the originators of the site don't always make the jar downloadable by itself. How do others feel about this? Is there a convenient way around it? To get more control over the dependencies you use, you can manually download all JARs to a remote repository within your local network. Although this is a lot of maintenance work, this gives to full control what JARs beeing used in your Maven projects. -Stefan Thanks. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to share and update maven?
Hi Christopher, this post about 'Multiple Versions of Maven and Maven Plugins' might be also interesting in this respect: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] rgmsgNo=16162 -Stefan -Original Message- From: Helck, Christopher [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 2004 10:01 PM To: [EMAIL PROTECTED] Subject: How to share and update maven? I have a set of projects that will be worked on by multiple developers. How do I make sure everyone is using the same version of maven and its various plugins? What I've done is checked maven into my souce control system and added it to my path. I'm expecting other developers to set their paths accordingly When I upgrade to a more recent plugin I've placed the new plugin into the souce control. Everyone checks out the new plugin and off they go. Is this wise? It seems like a kludge. I'm also wondering how I can upgrade to maven 1.0.1 when it comes out. I'd like to allow projects to upgrade at their own schedule. Is there someway to specify the maven version number in the project.xml or project.properties? Thanks, C. Helck The information contained in this e-mail is confidential. This e-mail is intended only for the stated addressee. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system. EBS Dealing Resources International Limited. Registered address: 55-56 Lincoln's Inn Fields, London WC2A 3LJ, United Kingdom. Registered number 2633663. EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison Avenue, 24th Floor, New York, NY 10022, USA, and One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA. EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku, Tokyo 104-0033, Japan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Poll] Writing documentation with Maven
Hi Carlos, the only thing i can say is: Wiki. :) I've found out that documentation is collaborative work and isn't done in one step. Therefore wiki is a perfect fit: One starts off with writing together some information, others add comment or organize that information. Wiki is the tool to make editing and re-editing really easy. At present, the problem with the wiki approach is that the documentation in Wiki syntax doesn't transform very well into other formats. To fix this, i've started working a Maven plugin in for Atlassians Confluence Wiki: It retrieves Wiki pages as listed in the project's navigation.xml and transforms them into XDocs. After that Maven's PDF plugin and the Xdoc plugin take over. My two cents, -Stefan -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 07, 2004 7:15 PM To: 'Maven Users List' Subject: [Poll] Writing documentation with Maven Hi all, I'd like to start a thread about how do you write your documentation to be integrated with Maven. Maybe I can give away some GMail invites to those participating, it's not much, but as you may know open source doesn't pay the bills, at least not MY bills ;-) 1. What format do you use to write documentation? A. xdoc B. html C. docbook D. latex E. who needs documentation? 2. If you didn't choose A, how do you transform your doc to be integrated in a Maven powered site? A. html2xdoc B. docbook plugin C. sdocbook plugin D. latex plugin E. other, please say what F. I don't transform, only link to my docs G. I write it again 4. What tool do you use to write the docs? A. notepad / vi and similar B. one that is not WYSIWYG (please say what) C. a WYSIWYG editor (please say what) D. an hex editor 3. Would you like to use another format instead of answered in (1) and why? Leave your name here if you'd like a Gmail invite. Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net - 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: navigation.xml documentation
Hi Kris, i usually refer to the exisiting navigation.xml files from existing projects, such as: http://cvs.apache.org/viewcvs.cgi/maven/xdocs/navigation.xml?rev=1.33.4. 13view=markup :-) -Stefan -Original Message- From: Charles Daniels [mailto:[EMAIL PROTECTED] Sent: Friday, September 03, 2004 10:29 PM To: Maven Users List Subject: RE: navigation.xml documentation navigation.xml goes in your xdocs directory. See http://maven.apache.org/reference/plugins/xdoc/faq.html for details on what you can put in it. -Original Message- From: Kris Nuttycombe [mailto:[EMAIL PROTECTED] Sent: Friday, September 03, 2004 4:23 PM To: Maven Users List Subject: navigation.xml documentation Hi, all, Where can I find documentation about how to configure the navigation.xml file? I've found references to such a beast numerous places on the web, and there are some references to it on the Maven wiki but nowhere can I find information about where to actually place the navigation.xml file in the project hierarchy or what the schema of the XML file is! Can someone point me in the right direction? Thanks, Kris -- = Kris Nuttycombe Associate Scientist Geospatial Data Services Group CIRES, National Geophysical Data Center/NOAA (303) 497-6337 [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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dependencies/JAR
Hi Brant, i think i don't fully understand. If you want to bundle your application JAR with its dependencies you can use the uberjar plugin (part of the standard maven distro) or the javaapp plugin (http://maven-plugins.sourceforge.net/maven-javaapp-plugin/index.html). I've found the javaapp plugin working better (although uberjar is certainly more sexy ;). Using the classpath-entry of the manifest-file for this is usually more tricky, as the entry is dependent on the location of the dependencies. So far I've only used it for EJB-JARs in EARs. Another way of doing this is shipping the dependencies in a lib/ dir and providing a start-script. -Stefan -Original Message- From: Brant Gurganus [mailto:[EMAIL PROTECTED] Sent: Sunday, August 22, 2004 3:18 AM To: [EMAIL PROTECTED] Subject: dependencies/JAR How do other projects deal with moving dependencies to the build directory and adding them to the classpath entry of the generated JAR? - 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: Accessing Maven properties from a Jelly Bean ?
Hi Serge,
just a short sample how i accessed simple properties:
c:useBean
var=myBean
versionProperty=${pom.currentVersion}
someOtherProperty=${maven.plugin.property}
class=my.package.BeanClass /
Hope this helps,
-Stefan
-Original Message-
From: Serge Huber [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 14, 2004 7:27 PM
To: Maven Users List
Subject: Accessing Maven properties from a Jelly Bean ?
Hi all,
I'm a beginner, trying to develop my first Maven plugin, and I'm a
little lost :)
I need to develop some functionality through a Jelly Bean, but I also
need to access some Maven properties (especially POM properties) from
the bean. Basically what I need to access in my Jelly Bean is :
- the POM's dependencies
- other project related properties.
I understand that I can pass parameters through to the JellyBean via
XML attributes, but can I pass a list of dependencies or
something like
that ? What is the recommended way of developing this functionality ?
Thanks a lot,
Serge Huber.
-
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]
Eclipse-Plugin: No Junit in .classpath file
Hi all, the Maven Eclipse plugin does not add the JUnit JAR to my .classpath file. Is this the desired behaviour? Or am I overlooking something? I've tried this with rc3 and rc4 and got the same effect. Also, i've played with the properties (esp. maven.eclipse.junit). Any ideas? -Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Eclipse-Plugin: No Junit in .classpath file
Hi Alex, Thanks, that was it. Cheers, -Stefan -Original Message- From: Alex Shneyderman [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 7:14 PM To: 'Maven Users List' Subject: RE: Eclipse-Plugin: No Junit in .classpath file Does your project contain unit tests source declaration in project.xml? -Original Message- From: Stefan Kleineikenscheidt [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 12:59 PM To: [EMAIL PROTECTED] Subject: Eclipse-Plugin: No Junit in .classpath file Hi all, the Maven Eclipse plugin does not add the JUnit JAR to my .classpath file. Is this the desired behaviour? Or am I overlooking something? I've tried this with rc3 and rc4 and got the same effect. Also, i've played with the properties (esp. maven.eclipse.junit). Any ideas? -Stefan - 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: Maven - Confluence integration
Hi Jason, hi Rafal, you brought up some good points. I also think of Confluence as a very good tool to collect information, from which projects can extract the documentation. We've been using confluence in a internal project and our documentation has improved, because it is so much easier to edit the doco... The only thing i've been looking for is a good solution to export pages to nicely formatted HTML pages and PDFs. I've just started using Maven, but it seems logical to me to have a plugin which generates documentation from confluence along with the build process. For configuration i think it would be best to define one or more entry pages, from where all child-pages are processed. This would allow to leave out all the cluttered pages, you usually have. I'm looking forward to check out the Maven Confluence plugin.. :) -Stefan Jason van Zyl wrote: It is clipping along at a rapid pace, if you want to try and build with it we can arrange something. Before the alpha is released I'll probably ask various folks to do some pre-alpha testing. There are about 14 plugins so far that are being used for testing, but the core will do the trick as far as building jars. Just let me know and I'll throw you the password for the bundles created by the CI process. Too busy ATM :-(. But when you are in the pre alpha testing phase, I'm willing to participate. Put me on the list. Rafal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
