RE: cactus plugin and overring war:war
Brett Porter [mailto:[EMAIL PROTECTED] wrote: Incidentally, I've just had exactly this error, using the maven-cactus-plugin-3.1 distributed with RC1. I had to add junit to my project with the root classloader, although at this point I'm not sure why as the cactus plugin seems to be doing everything it should. I ran into this issue as well. I think it may be something similar to the issue described in the Ant FAQ (http://ant.apache.org/faq.html#delegating-classloader), but I haven't looked into it too closely to know for sure. -- Sean T. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How do I exclude files from compile
Hi All, Is there any way I can exclude files (of a paticular pattern say *ABC*.java ) from the source directory, while compiling? Thanks Regards, Ranes.
Multiproject site generation
Hello,
I'm trying to use Maven Multiproject plugin in the following way:
- I have a main project (mtv);
- I have en extension dir with two subprojects :
* the torque database classes (mtv-om subproject)
* the castor config classes (mtv-config subproject)
I've properly set the multiproject options, however I met following
problems:
- when including dependencies on the subprojects in the main project,
maven multiproject detects a loop (subprojects declared as
extensions of the main project are dependencies of the main
project), but I fail to see how I could have a correct build
classpath for my mainproject without including them. Right now, I
leave the dependencies to run maven eclipse or maven in the
main project tree, but I comment them when I am doing a maven
multiproject.
- when I had only torque in the extensions, I could happily do a
maven multiproject site:fsdeploy to generate the site and copy
it on the server, but with the new castor subprojct I can't:
the javadoc target is complaining about missing sources and
targetPackage. I fail to see how I could resolve this and I'd
appreciate pointers to a castor subproject if anyone has some.
- the license file is in my main project dir, and the
project.properties of my subprojects refer to it with
${basedir}/../../LICENSE.txt this fails in multiproject goals but
succeeds when running maven in a subproject. How do you conceal the
two?
Any comments are gracefully appreciated.
Regards,
--
Loïc Minier [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I exclude files from compile
Add an exclude with the your patern in the build of your pom see : http://maven.apache.org/reference/project-descriptor.html#sourceModifications Nicolas, R a n e s [EMAIL PROTECTED] 06/11/2003 11:19 Veuillez répondre à Maven Users List Pour : Maven User List [EMAIL PROTECTED] cc : Objet : How do I exclude files from compile Hi All, Is there any way I can exclude files (of a paticular pattern say *ABC*.java ) from the source directory, while compiling? Thanks Regards, Ranes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I exclude files from compile
Hi Nicolas, Thanks for your suggestion. I tried something like this, but it doesn't seems to be working for me :( sourceModifications sourceModification classNameProcessorTest/className excludes exclude**test*.java/exclude exclude**Test*.java/exclude /excludes /sourceModification /sourceModifications Am particularly not sure about the value for className tag. Do I need to set any other parameters too??? Can any one provide a working version. Thanks Regards Ranes. - Original Message - From: [EMAIL PROTECTED] To: Maven Users List [EMAIL PROTECTED] Sent: Thursday, November 06, 2003 4:02 PM Subject: Re: How do I exclude files from compile Add an exclude with the your patern in the build of your pom see : http://maven.apache.org/reference/project-descriptor.html#sourceModification s Nicolas, R a n e s [EMAIL PROTECTED] 06/11/2003 11:19 Veuillez répondre à Maven Users List Pour : Maven User List [EMAIL PROTECTED] cc : Objet : How do I exclude files from compile Hi All, Is there any way I can exclude files (of a paticular pattern say *ABC*.java ) from the source directory, while compiling? Thanks Regards, Ranes. - 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 do I exclude files from compile
* R a n e s [EMAIL PROTECTED] [2003-11-06 07:14]: Hi Nicolas, Thanks for your suggestion. I tried something like this, but it doesn't seems to be working for me :( sourceModifications sourceModification classNameProcessorTest/className excludes exclude**test*.java/exclude exclude**Test*.java/exclude /excludes /sourceModification /sourceModifications Try: **/Test*.java ^ | +- Add a file separator. -- Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war plugin : [maven.caller.call.compile-java] is not defined
Vincent Massol wrote: No. It's because you seem not to have installed the caller plugin... My guess is that you have only taken the war plugin from HEAD without taking it's dependencies. Actually, thinking about it, we should add a dependency in the war plugin on the caller plugin so that it gets automatically downloaded. I installed all plugins from maven and maven-plugin (including caller plugin) from CVS 3 days ago, and i saw no relevant changes in CVS since i downloaded the sources. maven -DsourcesPresent=true war:war leads to this error with any project. Eric war:war goal leads to: BUILD FAILED File.. file:/C:/Documents and Settings/juju/.maven/plugins/maven-caller-plugin-1.0-SNAPSHOT/ Element... ant:fail Line.. 24 Column 91 Property [maven.caller.call.compile-java] is not defined - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: war plugin : [maven.caller.call.compile-java] is not defined
Eric, Have you tried without -DsourcesPresent=true? It was working for me some time ago (I haven't checked recently). Also, are you sure you have removed you plugin cache directory when you updated your maven plugins 3 days ago? Thanks -Vincent -Original Message- From: Eric Berenguier [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 14:26 To: Maven Users List Subject: Re: war plugin : [maven.caller.call.compile-java] is not defined Vincent Massol wrote: No. It's because you seem not to have installed the caller plugin... My guess is that you have only taken the war plugin from HEAD without taking it's dependencies. Actually, thinking about it, we should add a dependency in the war plugin on the caller plugin so that it gets automatically downloaded. I installed all plugins from maven and maven-plugin (including caller plugin) from CVS 3 days ago, and i saw no relevant changes in CVS since i downloaded the sources. maven -DsourcesPresent=true war:war leads to this error with any project. Eric war:war goal leads to: BUILD FAILED File.. file:/C:/Documents and Settings/juju/.maven/plugins/maven-caller-plugin-1.0-SNAPSHOT/ Element... ant:fail Line.. 24 Column 91 Property [maven.caller.call.compile-java] is not defined - 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: Building Maven
I apologize for my tone. If I'm misinformed or uninformed, I beg you to take me to task. I am a new user, going mainly by the available documentation. A clear error in my previous emails is that I said task when I meant target, I'm sure there are others. If user error resulted in the errors I saw (with the exception of the OutOfMemory which was known, well documented, and easily fixed), I'd love to know how I can avoid them. Again, I am quire thankful for the help I have received Mr. Porter. Since my tone grates, I will try to fix that. It does seem unlikely that I'll figure out exactly what I'm doing wrong since I don't even think I used sarcasm. But I'll try. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:52 AM To: Maven Users List Subject: RE: Building Maven On Wed, 2003-11-05 at 23:52, Horn, Cameron wrote: As previously stated, the error was an OutOfMemory error that was resolved as suggested in the build directions, by setting MAVEN_OPTS. I don't blame maven for the error (well, if it needs it often, perhaps it should be the default), but I do blame maven for not handling it correctly. Unless it was an optional bit, in which case I should be told that an optional bit failed, but it's continuing anyways. But you led me to believe that it continued not by design, but by error. Not handling build failures is a serious problem. Full stop. Not providing summaries of warnings and errors is just annoying. CVS is a wonderful system for handling version control. In addition to that primary function, it ensures that you have the correct files, keeps logs on activity, and provides access control. I fail to see what the problem with using it, even for storing JARs. HTTP is brittle (as seen previously) and almost wholly unsuited to this task. Now, if you're talking about the dangers of storing multiple copies of dependencies, or other such mix-ups, that's a different issue. One which is unrelated to the use of a CVS repository. Would you be happier if I refreshed my HTTP server from CVS? I'm still not sure what the ASCII portraits (banners?) mean. Is it bigger and therefore more important? Makes it difficult to search a log when T H I N G S A R E W R I T T E N L I K E T H I S. You have my need exactly right with your commons-logging example. Not only is dependency control beyond the scope of maven, maven actively circumvents it. In my opinion, dependency control is a requirement of a complete build solution. As to building from CVS not being a requirement for most, agreed. However, I see no reason why a project devoted to building software should not have a good, informitive, correct, and trouble-free build. If the authors of the tool can't do it, who the heck can? Here is the last automated build: http://www.mail-archive.com/dev%40maven.apache.org/msg06230.html It runs on a daily basis and has been fine for sometime. So in addition to the developers being able to build it our simple minded automaton can build it. Albeit this is from HEAD but shows there is no difficulty building Maven. Almost always it is user error. Additionally you would do well to heed some common open source courtesy. This is a volunteer effort and you can certainly raise the issues you see without the sarcasm and entirely uninformed comments. Some of the issues you raise certainly need to be addressed and you are certainly lucky Brett is patient enough to deal with you. But the tone used in your messages will in general illicit no responses to your queries. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - 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]
Javadoc offline links
When generating my project javadocs, I'd like to link to other APIs, but I'm in the dreaded 'behind a proxy' situation. So, I'm trying to do the linkoffline thing, but it appears that Maven's default behaviour is to direct the offline links to your offline API, which is not what I want. I want it to read the offline package-list, then use the online link I provide it. So, I'm using something like the following: maven.javadoc.offlineLinks=http://java.sun.com/j2se/1.4.1/docs/api/#../. ./document/apis/java According to http://maven.apache.org/reference/plugins/javadoc/properties.html, this is what I should use, but this leads to Javadoc trying to fetch the package list from http://java.sun.com/j2se/1.4.1/docs/api/package-list, which doesn't work, because of the proxy. If I reverse the order, to maven.javadoc.offlineLinks=../../document/apis/java#http://java.sun.com/ j2se/1.4.1/docs/api/ Then I get links, but to the offline version, which is the behaviour as if there was nothing after the #. So, does anyone know if this is actually supposed to work, and what I am doing wrong, or if it's a future goal, and not implemented yet. If so, I think a bug report might be forthcoming... Cheers, Nick --- Research Engineer Intelligent Systems Lab, BT Exact Tel: (+44)1473 605 894 Email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REQUEST] Add commons-discovery 0.2 to ibiblio
Please add commons-discovery 0.2 to the ibiblio repository. http://jakarta.apache.org/commons/discovery.html Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
repository connection string
Hello, I'm trying to configure the repository in my project.xml but while i'm using cvsnt on Windows 2K my repository connection is like this : scm:cvs:pserver:[EMAIL PROTECTED]:D:\BuildSystem\tools\cvsnt\repository:module1 And Maven count the number of token used and it said : more than 6 token useds = Build Failed I know that i can configure a prefix in CVS which can help me in that situation, but i've just remove this prefix because Eclipse 3.0 M3 said me that it is not a good idea to use prefix for cvs plugin. So my question is : Is it a back door to avoid Maven counting the token or which connection string can i use in that situation ? Thank's for your answer Eric
Javadoc: No source files and no packages have been specified.
I feel kinda stupid, but what am I missing here? Maven output C:\Eclipse3.0\workspace\myprojectmaven javadoc:generate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT Attempting to download maven-SNAPSHOT.jar. BUILD FAILED No source files and no packages have been specified. Total time: 5 seconds Finished at: Thu Nov 06 11:57:22 EST 2003 project.xml- ?xml version=1.0? project . nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress sourceDirectorysrc/main/java/sourceDirectory unitTestSourceDirectorysrc/test/java/unitTestSourceDirectory aspectSourceDirectory/ resources resource directorysrc/main/resources/directory includes include**/*/include /includes /resource /resources unitTest includes include**/*Test.java/include /includes excludes exclude**/RepositoryTest.java/exclude /excludes resources resource directorysrc/test/resources/directory includes include**/*/include /includes /resource /resources /unitTest /build reports reportmaven-jdepend-plugin/report reportmaven-checkstyle-plugin/report reportmaven-javadoc-plugin/report /reports /project -- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Javadoc: No source files and no packages have been specified.
Have you tried a packagecom.foo.bar/package tag under project? The javadoc plugin source uses that as the packagenames element of the Ant javadoc task. Between that and the build.sourceDirectory element, that's all I can see... Are your sourceDirectory tags and similar within the build tags? Nick -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 17:01 To: Maven Users List Subject: Javadoc: No source files and no packages have been specified. I feel kinda stupid, but what am I missing here? Maven output C:\Eclipse3.0\workspace\myprojectmaven javadoc:generate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT Attempting to download maven-SNAPSHOT.jar. BUILD FAILED No source files and no packages have been specified. Total time: 5 seconds Finished at: Thu Nov 06 11:57:22 EST 2003 project.xml- ?xml version=1.0? project . nagEmailAddress[EMAIL PROTECTED]/nagEmailAddress sourceDirectorysrc/main/java/sourceDirectory unitTestSourceDirectorysrc/test/java/unitTestSourceDirectory aspectSourceDirectory/ resources resource directorysrc/main/resources/directory includes include**/*/include /includes /resource /resources unitTest includes include**/*Test.java/include /includes excludes exclude**/RepositoryTest.java/exclude /excludes resources resource directorysrc/test/resources/directory includes include**/*/include /includes /resource /resources /unitTest /build reports reportmaven-jdepend-plugin/report reportmaven-checkstyle-plugin/report reportmaven-javadoc-plugin/report /reports /project -- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu - 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: repository connection string
I'm sorry for that stupid question. I found the response in the documentation : scm|cvs|pserver|[EMAIL PROTECTED]|d:\BuildSystem\tools\cvsnt\repository|module1 I'll try Eric -Message d'origine- De : Eric Taix Envoyé : jeudi 6 novembre 2003 17:56 À : [EMAIL PROTECTED] Objet : repository connection string Hello, I'm trying to configure the repository in my project.xml but while i'm using cvsnt on Windows 2K my repository connection is like this : scm:cvs:pserver:[EMAIL PROTECTED]:D:\BuildSystem\tools\cvsnt\repository:module1 And Maven count the number of token used and it said : more than 6 token useds = Build Failed I know that i can configure a prefix in CVS which can help me in that situation, but i've just remove this prefix because Eclipse 3.0 M3 said me that it is not a good idea to use prefix for cvs plugin. So my question is : Is it a back door to avoid Maven counting the token or which connection string can i use in that situation ? Thank's for your answer Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problems running ant tasks from maven
Googling the maven web site for root ClassLoader turned up one promising page, http://maven.apache.org/reference/developers/developer-guide.html. However, the current page (generated 03 November) doesn't even contain the word ClassLoader. Google's cached page (from 07 October) DOES mention it, at least in the context of developing a plugin. Now I get an INTERNAL ERROR: Reference made to goal 'java:jar-resources' which has no definition. --Daniel Rabe -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 6:45 PM To: 'Maven Users List' Subject: RE: problems running ant tasks from maven You probably need to add a junit dependency to your project. You might need to put it in the root classloader (google the maven website). Anyway, you can integrate your ant script into maven.xml really easily. I'd recommend trying that. Actually, I'd recommend the test plugin above all of these, although I'm assuming this doesn't suite your needs. - Brett -Original Message- From: Daniel Rabe [mailto:[EMAIL PROTECTED] Sent: Thursday, 6 November 2003 12:33 PM To: '[EMAIL PROTECTED]' Subject: problems running ant tasks from maven I have an existing ant task set up to run junit. If I invoke it from the command line with ant test, it works fine. I want to integrate this into maven, so I added the following to maven.xml: goal name=zzz ant target=test / /goal When I run maven zzz it fails (error messages below). Why would it not run from within maven when it runs fine from the command line? Thanks, Daniel Rabe BUILD FAILED File.. file:/C:/KangaHermes/ file:/C:/KangaHermes/ Element... ant Line.. 36 Column 24 Could not create task or type of type: junit. Ant could not find the task or a class this task relies upon. This is common and has a number of causes; the usual solutions are to read the manual pages then download and install needed JAR files, or fix the build file: - You have misspelt 'junit'. Fix: check your spelling. - The task needs an external JAR file to execute and this is not found at the right place in the classpath. Fix: check the documentation for dependencies. Fix: declare the task. - The task is an Ant optional task and optional.jar is absent Fix: look for optional.jar in ANT_HOME/lib, download if needed - The task was not built into optional.jar as dependent libraries were not found at build time. Fix: look in the JAR to verify, then rebuild with the needed libraries, or download a release version from apache.org - The build file was written for a later version of Ant Fix: upgrade to at least the latest release version of Ant - The task is not an Ant core or optional task and needs to be declared using taskdef. Remember that for JAR files to be visible to Ant tasks implemented in ANT_HOME/lib, the files must be in the same directory or on the classpath Please neither file bug reports on this problem, nor email the Ant mailing lists, until all of these causes have been explored, as this is not an Ant bug. Total time: 9 seconds Finished at: Wed Nov 05 18:32:23 MST 2003
Maven Intergration Question
Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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 Intergration Question
In the sense of the property maven.build.dir? See http://maven.apache.org/reference/user-guide.html#Maven%20Setup. This is where compiled classes, generated documentation and jar files will be initially put. Nick -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 17:59 To: Maven Users List Subject: Maven Intergration Question Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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 Intergration Question
Set maven.build.dir Sri P.S. Please start a new thread for new discussions. -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:59 PM To: Maven Users List Subject: Maven Intergration Question Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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 Intergration Question
I am new to this, I don't know how to start a new group,care to show me.. -S -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:02 PM To: Maven Users List Subject: RE: Maven Intergration Question Set maven.build.dir Sri P.S. Please start a new thread for new discussions. -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:59 PM To: Maven Users List Subject: Maven Intergration Question Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Intergration Question
Just the way you sent the first message -- however, instead of replying to an existing message (and changing the subject) just start a new message to the maven users' list. Sri -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 1:05 PM To: Maven Users List Subject: RE: Maven Intergration Question I am new to this, I don't know how to start a new group,care to show me.. -S -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:02 PM To: Maven Users List Subject: RE: Maven Intergration Question Set maven.build.dir Sri P.S. Please start a new thread for new discussions. -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:59 PM To: Maven Users List Subject: Maven Intergration Question Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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] - 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 Intergration Question
That's hardly a good enough reason. In fact, I'd prefer to change it then, so that the bugs get shaken out. In my case, I've moved it into the WEB-INF directory, because I want a nice easily deployed web-app during development, but also to keep as much stuff as possible out of public view. Traditions are all well and good, but they're a pain when you want to do something different, which always comes soon enough... Nick -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 18:07 To: Maven Users List Subject: Re: Maven Intergration Question On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote: Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Why do you really want to do this? Most people don't muck with the target/ default. If it's simply a personal preference I would recommend just sticking with target/ as I'm sure there are some places where target/ has been hard-coded by mistake in some plugins because that has been the standard for so long. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - 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 Intergration Question
Hi
I agree with you, but in over company we are using ant to build the
whole application, we just want to maven to build documentation, Do you
have any bright ideas?
Also I was looking into changing maven.build.dir value, but it's warning
me about bootstrap of Maven from source code, as it expects the jar
created to be in ${basedir}/target/. Can you please give more guidence
on this.
Below is from Maven docs:
CAUTION: Changing default maven.build.dir value in your
${user.home}/build.properties might allow one some control of individual
project directory layouts. However this practice will interfere with the
bootstrap of Maven from source code, as it expects the jar created to be
in ${basedir}/target/
${basedir
Thanks,
S-
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 12:07 PM
To: Maven Users List
Subject: Re: Maven Intergration Question
On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote:
Is there is a way to customize target folder maven looks at. I wanted
to
looked at build folder instead.
Why do you really want to do this? Most people don't muck with the
target/ default. If it's simply a personal preference I would recommend
just sticking with target/ as I'm sure there are some places where
target/ has been hard-coded by mistake in some plugins because that has
been the standard for so long.
Thanks,
-S
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 11:51 AM
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 07:18
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
[snip]
Also, plugin:download'ing the latest cactus plugin as per the cactus
maven
integration page doesn't work as the dependencies on the cactus jars
themselves are incorrect :)
Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now.
-Vincent
-
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]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
-
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 Intergration Question
Thanks, advice greatly appericated -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:09 PM To: Maven Users List Subject: RE: Maven Intergration Question Just the way you sent the first message -- however, instead of replying to an existing message (and changing the subject) just start a new message to the maven users' list. Sri -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 1:05 PM To: Maven Users List Subject: RE: Maven Intergration Question I am new to this, I don't know how to start a new group,care to show me.. -S -Original Message- From: Sri Sankaran [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:02 PM To: Maven Users List Subject: RE: Maven Intergration Question Set maven.build.dir Sri P.S. Please start a new thread for new discussions. -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:59 PM To: Maven Users List Subject: Maven Intergration Question Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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] - 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: war plugin : [maven.caller.call.compile-java] is not defined
Vincent Massol wrote: Eric, Have you tried without -DsourcesPresent=true? It was working for me some time ago (I haven't checked recently). It works perfectly without the -D (it's obvious looking at the source code: the war plugin only calls the caller plugin when 'sourcesPresent' is true) Also, are you sure you have removed you plugin cache directory when you updated your maven plugins 3 days ago? That's always the first i do whenever something goes wrong :-) Thanks -Vincent -Original Message- From: Eric Berenguier [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 14:26 To: Maven Users List Subject: Re: war plugin : [maven.caller.call.compile-java] is not defined Vincent Massol wrote: No. It's because you seem not to have installed the caller plugin... My guess is that you have only taken the war plugin from HEAD without taking it's dependencies. Actually, thinking about it, we should add a dependency in the war plugin on the caller plugin so that it gets automatically downloaded. I installed all plugins from maven and maven-plugin (including caller plugin) from CVS 3 days ago, and i saw no relevant changes in CVS since i downloaded the sources. maven -DsourcesPresent=true war:war leads to this error with any project. Eric war:war goal leads to: BUILD FAILED File.. file:/C:/Documents and Settings/juju/.maven/plugins/maven-caller-plugin-1.0-SNAPSHOT/ Element... ant:fail Line.. 24 Column 91 Property [maven.caller.call.compile-java] is not defined - 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 Intergration Question
Jason brings up a valid point -- however, we have been using
maven.build.dir=${basedir}/build
and haven't had any plug-in blow up, yet -- at least not because of it :)
As Nick points out, this is a good way to find out if target has been hard-coded in
any plug-in!
The docs you are referring to are talking about the case when (and if) you build Maven
itself from source. If you happen to do that simply follow the instructions verbatim
and all will be well.
Sri
-Original Message-
From: Rauf, Saleem [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 1:12 PM
To: Maven Users List; [EMAIL PROTECTED]
Subject: RE: Maven Intergration Question
Hi
I agree with you, but in over company we are using ant to build the
whole application, we just want to maven to build documentation, Do you
have any bright ideas?
Also I was looking into changing maven.build.dir value, but it's warning
me about bootstrap of Maven from source code, as it expects the jar
created to be in ${basedir}/target/. Can you please give more guidence
on this.
Below is from Maven docs:
CAUTION: Changing default maven.build.dir value in your
${user.home}/build.properties might allow one some control of individual
project directory layouts. However this practice will interfere with the
bootstrap of Maven from source code, as it expects the jar created to be
in ${basedir}/target/
${basedir
Thanks,
S-
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 12:07 PM
To: Maven Users List
Subject: Re: Maven Intergration Question
On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote:
Is there is a way to customize target folder maven looks at. I wanted
to
looked at build folder instead.
Why do you really want to do this? Most people don't muck with the
target/ default. If it's simply a personal preference I would recommend
just sticking with target/ as I'm sure there are some places where
target/ has been hard-coded by mistake in some plugins because that has
been the standard for so long.
Thanks,
-S
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 11:51 AM
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 07:18
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
[snip]
Also, plugin:download'ing the latest cactus plugin as per the cactus
maven
integration page doesn't work as the dependencies on the cactus jars
themselves are incorrect :)
Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now.
-Vincent
-
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]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
-
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 Intergration Question
If you are using Ant and Maven independently, it's probably better to
keep their build directories separate, so 'target' for Maven and 'build'
for Ant. That way, neither app should interfere with the other. Of
course, in the long run you should be heading towards building with
Maven... ;-)
As to bootstrapping Maven, unless you're building from CVS, it's not an
issue. If you are building from CVS, leave the settings alone the first
time you build it, then once you have a functioing install, go ahead and
change stuff.
Nick
-Original Message-
From: Rauf, Saleem [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 18:12
To: Maven Users List; [EMAIL PROTECTED]
Subject: RE: Maven Intergration Question
Hi
I agree with you, but in over company we are using ant to build the
whole application, we just want to maven to build
documentation, Do you
have any bright ideas?
Also I was looking into changing maven.build.dir value, but
it's warning
me about bootstrap of Maven from source code, as it expects the jar
created to be in ${basedir}/target/. Can you please give more guidence
on this.
Below is from Maven docs:
CAUTION: Changing default maven.build.dir value in your
${user.home}/build.properties might allow one some control of
individual
project directory layouts. However this practice will
interfere with the
bootstrap of Maven from source code, as it expects the jar
created to be
in ${basedir}/target/
${basedir
Thanks,
S-
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 12:07 PM
To: Maven Users List
Subject: Re: Maven Intergration Question
On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote:
Is there is a way to customize target folder maven looks
at. I wanted
to
looked at build folder instead.
Why do you really want to do this? Most people don't muck with the
target/ default. If it's simply a personal preference I would
recommend
just sticking with target/ as I'm sure there are some places where
target/ has been hard-coded by mistake in some plugins
because that has
been the standard for so long.
Thanks,
-S
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 11:51 AM
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 07:18
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
[snip]
Also, plugin:download'ing the latest cactus plugin as per
the cactus
maven
integration page doesn't work as the dependencies on the
cactus jars
themselves are incorrect :)
Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now.
-Vincent
-
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]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
-
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]
Custom doc folder of of documentation Maven produces
Hi All, and Nick, By directory structure looks like: Root Directory | | | -AppName | | |--src - Where all my source code resides, build.xml which complies all the code. | |--build - where all my class files reside | |--dist - where my war file resides for the application | |--doc - Want this to be produced by Maven All want to see to produce doc folder using maven for application. So what is the best way to go about this, Please feel free to provide examples. Thanks, -S -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 12:10 PM To: [EMAIL PROTECTED] Subject: RE: Maven Intergration Question That's hardly a good enough reason. In fact, I'd prefer to change it then, so that the bugs get shaken out. In my case, I've moved it into the WEB-INF directory, because I want a nice easily deployed web-app during development, but also to keep as much stuff as possible out of public view. Traditions are all well and good, but they're a pain when you want to do something different, which always comes soon enough... Nick -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 18:07 To: Maven Users List Subject: Re: Maven Intergration Question On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote: Is there is a way to customize target folder maven looks at. I wanted to looked at build folder instead. Why do you really want to do this? Most people don't muck with the target/ default. If it's simply a personal preference I would recommend just sticking with target/ as I'm sure there are some places where target/ has been hard-coded by mistake in some plugins because that has been the standard for so long. Thanks, -S -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 11:51 AM To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 06 November 2003 07:18 To: 'Maven Users List' Subject: RE: cactus plugin and overring war:war [snip] Also, plugin:download'ing the latest cactus plugin as per the cactus maven integration page doesn't work as the dependencies on the cactus jars themselves are incorrect :) Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now. -Vincent - 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - 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 Intergration Question
Nick,
Thanks for info. Do you have an example I can follow, I am brand new to
Maven.
Thanks,
-S
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 12:26 PM
To: [EMAIL PROTECTED]
Subject: RE: Maven Intergration Question
If you are using Ant and Maven independently, it's probably better to
keep their build directories separate, so 'target' for Maven and 'build'
for Ant. That way, neither app should interfere with the other. Of
course, in the long run you should be heading towards building with
Maven... ;-)
As to bootstrapping Maven, unless you're building from CVS, it's not an
issue. If you are building from CVS, leave the settings alone the first
time you build it, then once you have a functioing install, go ahead and
change stuff.
Nick
-Original Message-
From: Rauf, Saleem [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 18:12
To: Maven Users List; [EMAIL PROTECTED]
Subject: RE: Maven Intergration Question
Hi
I agree with you, but in over company we are using ant to build the
whole application, we just want to maven to build
documentation, Do you
have any bright ideas?
Also I was looking into changing maven.build.dir value, but
it's warning
me about bootstrap of Maven from source code, as it expects the jar
created to be in ${basedir}/target/. Can you please give more guidence
on this.
Below is from Maven docs:
CAUTION: Changing default maven.build.dir value in your
${user.home}/build.properties might allow one some control of
individual
project directory layouts. However this practice will
interfere with the
bootstrap of Maven from source code, as it expects the jar
created to be
in ${basedir}/target/
${basedir
Thanks,
S-
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 12:07 PM
To: Maven Users List
Subject: Re: Maven Intergration Question
On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote:
Is there is a way to customize target folder maven looks
at. I wanted
to
looked at build folder instead.
Why do you really want to do this? Most people don't muck with the
target/ default. If it's simply a personal preference I would
recommend
just sticking with target/ as I'm sure there are some places where
target/ has been hard-coded by mistake in some plugins
because that has
been the standard for so long.
Thanks,
-S
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 11:51 AM
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 06 November 2003 07:18
To: 'Maven Users List'
Subject: RE: cactus plugin and overring war:war
[snip]
Also, plugin:download'ing the latest cactus plugin as per
the cactus
maven
integration page doesn't work as the dependencies on the
cactus jars
themselves are incorrect :)
Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now.
-Vincent
-
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]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pmd plugin and custom rules
I have a set of custom pmd rules.
It consists of 2 parts.
1) a custom ruleset-foo.xml
2) a jar file containing the implementation of those rules. (AbstractRule
classes).
Using the maven-pmd-plugin, how do I get my custom jar file into it's
classpath?
Using the often talked about hack of
${pom.getPluginContext('maven-pmd-plugin')} and then
manipulating it, doesn't work in this situation, as the MavenJellyContext
does not
apparently contain dependancy classpath information for me to manipulate in
a preGoal
prior to running the pmd:report goal.
I think this might be a bug.
/me wanders off to jira to look ...
/* Joakim Erdfelt */
Project Descriptor Creation Tool
Hi Everybody, On maven website I read about some tool being developed to generate a project descriptor automatically. I was thinking about either getting or developing something like that for my projects but would surely prefer to use something supplied with maven. So I wanted to know what kind of a tool would that be ? Some GUI program that takes entries or some command line based program ? And when is that tool scheduled come ? Thanks Vikas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
target directory and bootstrap
Hi Guys,
What's the significance of the following statement if I'm just installing
maven with the supplied installer and don't build is from the source at my
end and simply use maven for my project.
However this practice will interfere with the bootstrap of Maven from
source code, as it expects the jar created to be in ${basedir}/target/
As stated in some earlier posts, I'm looking to change the directory
structure for my projects.
Thanks
Vikas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Project Descriptor Creation Tool
I wouldn't find it very useful, but a reverse IDE plugin would be. Currently the IDE plugins generate IDE projects from project.xml files. I'm sure in the future the reverse will be possible, so you can create a maven project inside an IDE and leverage all of their nice gui elements :) Apart from mevenide.sf.net, I don't know of anything along these lines at the moment. - Brett -Original Message- From: Vikas Phonsa [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 6:28 AM To: 'Maven Users List' Subject: Project Descriptor Creation Tool Hi Everybody, On maven website I read about some tool being developed to generate a project descriptor automatically. I was thinking about either getting or developing something like that for my projects but would surely prefer to use something supplied with maven. So I wanted to know what kind of a tool would that be ? Some GUI program that takes entries or some command line based program ? And when is that tool scheduled come ? Thanks Vikas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problems running ant tasks from maven
I got you to google because I knew it had moved and I didn't remember where... It just seems they haven't crawled it recently enough :) Its actually at the bottom of the user guide. Regarding the java:jar-resources missing... I'm pretty sure you'll find an anser to that in the mail archive. Cheers, Brett -Original Message- From: Daniel Rabe [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 4:36 AM To: 'Maven Users List' Subject: RE: problems running ant tasks from maven Googling the maven web site for root ClassLoader turned up one promising page, http://maven.apache.org/reference/developers/developer-guide.html. However, the current page (generated 03 November) doesn't even contain the word ClassLoader. Google's cached page (from 07 October) DOES mention it, at least in the context of developing a plugin. Now I get an INTERNAL ERROR: Reference made to goal 'java:jar-resources' which has no definition. --Daniel Rabe -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 6:45 PM To: 'Maven Users List' Subject: RE: problems running ant tasks from maven You probably need to add a junit dependency to your project. You might need to put it in the root classloader (google the maven website). Anyway, you can integrate your ant script into maven.xml really easily. I'd recommend trying that. Actually, I'd recommend the test plugin above all of these, although I'm assuming this doesn't suite your needs. - Brett -Original Message- From: Daniel Rabe [mailto:[EMAIL PROTECTED] Sent: Thursday, 6 November 2003 12:33 PM To: '[EMAIL PROTECTED]' Subject: problems running ant tasks from maven I have an existing ant task set up to run junit. If I invoke it from the command line with ant test, it works fine. I want to integrate this into maven, so I added the following to maven.xml: goal name=zzz ant target=test / /goal When I run maven zzz it fails (error messages below). Why would it not run from within maven when it runs fine from the command line? Thanks, Daniel Rabe BUILD FAILED File.. file:/C:/KangaHermes/ file:/C:/KangaHermes/ Element... ant Line.. 36 Column 24 Could not create task or type of type: junit. Ant could not find the task or a class this task relies upon. This is common and has a number of causes; the usual solutions are to read the manual pages then download and install needed JAR files, or fix the build file: - You have misspelt 'junit'. Fix: check your spelling. - The task needs an external JAR file to execute and this is not found at the right place in the classpath. Fix: check the documentation for dependencies. Fix: declare the task. - The task is an Ant optional task and optional.jar is absent Fix: look for optional.jar in ANT_HOME/lib, download if needed - The task was not built into optional.jar as dependent libraries were not found at build time. Fix: look in the JAR to verify, then rebuild with the needed libraries, or download a release version from apache.org - The build file was written for a later version of Ant Fix: upgrade to at least the latest release version of Ant - The task is not an Ant core or optional task and needs to be declared using taskdef. Remember that for JAR files to be visible to Ant tasks implemented in ANT_HOME/lib, the files must be in the same directory or on the classpath Please neither file bug reports on this problem, nor email the Ant mailing lists, until all of these causes have been explored, as this is not an Ant bug. Total time: 9 seconds Finished at: Wed Nov 05 18:32:23 MST 2003
junit classpaths
junit tests that run outside of maven hare having problem inside... using 1.0-rc1 $ maven test [ results in (when maven.junit.fork=false (default) ) ] java:prepare-filesystem: .. test:test: [junit] dir attribute ignored if running in the same VM [junit] Running com.txu.tmdb.bd.TranslateColumnNameTest [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0.33 sec [junit] [ERROR] TEST com.txu.tmdb.bd.TranslateColumnNameTest FAILED $ maven test [ results in (when maven.junit.fork=true ) java:prepare-filesystem: .. test:test: [junit] Running com.txu.tmdb.bd.TranslateColumnNameTest [junit] java.lang.NoClassDefFoundError: org/w3c/dom/Node [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:115) [junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement.createFormatter(FormatterElement.java:1 83) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.createAndStoreFormatter(JUnitTestRunner. java:562) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:507) [junit] Exception in thread main [junit] [ERROR] TEST com.txu.tmdb.bd.TranslateColumnNameTest FAILED what happened to the original classpath? i think the problem revolves around those unit tests using System.setProperty() to signal the need for a mock jndi datasource lookup... -- dan * Confidentiality Notice: This email message, including any attachments, contains or may contain confidential information intended only for the addressee. If you are not an intended recipient of this message, be advised that any reading, dissemination, forwarding, printing, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply message and delete this email message and any attachments from your system. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building Maven
If user error resulted in the errors I saw (with the exception of the OutOfMemory which was known, well documented, and easily fixed), I'd love to know how I can avoid them. I think I last time asked about your JVM settings, as a problem starting the modern compiler is unusual. I'm thinking maybe your java executable is a JRE (no compiler installed) instead of a JDK. Check %JAVA_HOME%. Again, I am quire thankful for the help I have received Mr. Porter. [Brett looks around for his father] Who? :) Since my tone grates, I will try to fix that. It does seem unlikely that I'll figure out exactly what I'm doing wrong since I don't even think I used sarcasm. But I'll try. I only just received the reply that Jason quoted - seems our mail system is a bit screwy. Perhaps you should re-read it. To me (and this is just how I interpret it - it may not have been your intention), it sounded as though you knew better than everyone else here about how things should work. There's not an open source project in the world that let's that fly. Mostly this was because statements were misinformed, exaggerated or abrupt. Without wanting to descend into any sort of flame war, let me identify the particular comments that triggered that. Not handling build failures is a serious problem. Full stop. I admitted we needed to look at that, but that it wasn't a high priority. As Jason explained, it works for us and the robots that automatically build the stuff with a correctly configured environment. It is not a serious problem, as it builds correctly when used appropriately, and I think overdramatisation of it makes it sound worse. You should be aware that this is not a standard Maven build problem - errors are always end the build process, but a problem for wrapping Maven in something else (in this case ant to bootstrap it). If Maven used on other projects didn't report errors, yes it would be a serious problem. CVS is a wonderful system for handling version control. In addition to that primary function, it ensures that you have the correct files, keeps logs on activity, and provides access control. I fail to see what the problem with using it, even for storing JARs. HTTP is brittle (as seen previously) and almost wholly unsuited to this task. CVS wasn't ever that great at binary files. A HTTP repository stores JARs with the version number in the filename for version control and retains old versions. This is important when it comes to distributing a product so end-users can see the versions of JARs you are using easily. You can use basic auth or whatever network access controls you want to grant permissions on files. You can read your web server access logs. It does everything you said just as well, and in a way more easily distributable to other sources. Think about the converse: is it easier to configure anonymous pserver access or HTTP for an end user? As for HTTP brittleness, there are already alternative deployment protocols for artifacts, and I imagine retrieving them by these protocols is not far away. You have my need exactly right with your commons-logging example. Not only is dependency control beyond the scope of maven, maven actively circumvents it. In my opinion, dependency control is a requirement of a complete build solution. Actively circumvents it? Hardly. No matter what you use, developers could download the JAR in question and put it in WEB-INF/lib and use it. But you could use whatever access control mentioned earlier to do this under maven if you had to . Dependency control in terms of access permissions sounds so crazy to me and not a part of a complete build solution that I think I've misunderstood you. Perhaps we could discuss that more off-list. I really don't see your use case. As to building from CVS not being a requirement for most, agreed. However, I see no reason why a project devoted to building software should not have a good, informitive, correct, and trouble-free build. If the authors of the tool can't do it, who the heck can? Again, the exaggerated and incorrect nature of this statement is probably what grates. Anyway, enough said. Hope this helps. Cheers, Brett
RE: High ASCII in java code not compiling under Maven
switch( chr) {
case 'à': buf.append(agrave); break;
When I try to run my maven build goal, it will not compile
this utility class, and I get a whole bunch of errors to
the effect:
case '?' already defined
If I run javac, no problemo. Compiles just fine. I played
around with system encoding in the project.xml and maven.xml
files (was UTF-8, also tried iso-8859-1), and in my OS
(linux) to no avail.
Any clues?
We had success with the 'maven.compile.fork=true' and
'maven.compile.encoding=iso8859-1' properties defined at the
maven-java-plugin web page.
http://maven.apache.org/reference/plugins/java/properties.html
/* joakim erdfelt */
statCVS Report
Hi All, When use statcvs report I get following error: C:\maven-samplemaven statcvs __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT statcvs:init: statcvs:generate: [echo] fetching cvs logs... [java] StatCvs-XML - CVS statistics generation [java] [java] Parsing CVS log 'C:\maven-sample/target/statcvs.log' [java] Generating report for rauf into C:\maven-sample/target/generated-xdocs/statcvs\ [java] Assuming web repository is ViewCVS [java] Reading output settings [java] Creating suite using net.sf.statcvs.output.XDocRenderer [java] Using transformer org.apache.xalan.transformer.TransformerImpl [java] Rendering authors [java] Rendering commit_log [java] Rendering dir_sizes [java] Rendering index [java] Rendering file_sizes [java] Rendering dir_activity [java] java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:324) [java] at net.sf.statcvs.Main.generateSuite(Main.java:291) [java] at net.sf.statcvs.Main.run(Main.java:176) [java] at net.sf.statcvs.Main.main(Main.java:78) [java] Caused by: java.lang.ArrayIndexOutOfBoundsException: 1 [java] at org.jfree.chart.plot.ContourPlot.contourRenderer(Unknown Source) [java] at org.jfree.chart.plot.ContourPlot.render(Unknown Source) [java] at org.jfree.chart.plot.ContourPlot.draw(Unknown Source) [java] at org.jfree.chart.JFreeChart.draw(Unknown Source) [java] at org.jfree.chart.JFreeChart.createBufferedImage(Unknown Source) [java] at org.jfree.chart.ChartUtilities.writeChartAsPNG(Unknown Source) [java] at org.jfree.chart.ChartUtilities.saveChartAsPNG(Unknown Source) [java] at org.jfree.chart.ChartUtilities.saveChartAsPNG(Unknown Source) [java] at org.jfree.chart.ChartUtilities.saveChartAsPNG(Unknown Source) [java] at net.sf.statcvs.output.xml.chart.AbstractChart.save(AbstractChart.java:119) [java] at net.sf.statcvs.output.xml.chart.AbstractChart.save(AbstractChart.java:115) [java] at net.sf.statcvs.output.xml.chart.AbstractChart.save(AbstractChart.java:111) [java] at net.sf.statcvs.output.XMLRenderer.renderSingle(XMLRenderer.java:176) [java] at net.sf.statcvs.output.XMLRenderer.render(XMLRenderer.java:127) [java] at net.sf.statcvs.output.xml.DocumentSuite.generate(DocumentSuite.java:61) [java] at net.sf.statcvs.output.XDocRenderer.generate(XDocRenderer.java:51) [java] ... 7 more [java] null [java] [ERROR] Java Result: 1 [copy] Copying 9 files to C:\maven-sample\target\docs\statcvs Has anyone ran into this problem? -S - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: simple jelly explanation
This is true, but only if outputDir is a java.lang.String (or an empty
Map, Collection, or Array). Properties in maven are
org.apache.commons.jelly.expression.ConstantExpression, so they are only
empty() if they are undefined.
A jexl workaround to this would be
${empty(myEmptyProperty.toString())}. A possible long-term solution
would be to return true in jexl's ASTEmptyFunction.java if
Object.toString() is an empty string, rather than using an instanceof
test. Unfortunately, this does break with the spec. Alternatively,
ConstantExpression could extend String, although that might be taking it
a bit far :-)
Matt
James Strachan wrote:
On 6 Nov 2003, at 00:43, matt wrote:
You could also use ${empty(outputDir)}, or ${outputDir == null},
which are both identical in meaning to ${empty outputDir}.
Not quite, empty(outputDir) is also true if outputDir ==
Jelly uses the Jexl Expression Language, which is a superset of JSTL
(Java Standard Tag Library). To quote from JSTL in Action,
The empty operator determines whether a collection or string is
empty or null. For instance, ${empty param.firstname} will be true
only if a request parameter named firstname is not present. JSTL
expressions can also compare items directly against the keyword null,
as in ${param.firstname == null}, but this is an advanced use.
Although Jelly is not always in a web context (ie, doesn't have the
param implicit object), the same rules apply. In addition, to quote
from the jexl home page (http://jakarta.apache.org/commons/jexl.html):
Jexl has extended the JSTL in a few ways :
- Support for invocation of any accessible method (see example
above).
- Added a general size() method, which works on String, returning
length, Map, returning # of keys, and List and arrays, returning the
number of elements.
- Optional syntax for the 'empty' function : empty(obj)
- Misc : '+' has been overloaded to be use as a String
concatenation operator
The invocation of any accessible method means that you can call
${object.getProperty()}, and it will be the same as
${object.property}, or ${object.setProperty(someOtherObject)}. You
can also call methods that do not correspond to properties, such as
${someString.endsWith(otherString)}.
Strongly recommend reading up on Jexl and JSTL.
Good answer Matt :)
James
---
http://radio.weblogs.com/0112098/
-
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: junit classpaths
When running inside maven, junit 'inherits' MAVEN's classpath as well. When running outside, it doesn't. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc [EMAIL PROTECTED] wrote on 07/11/2003 08:38:14 AM: junit tests that run outside of maven hare having problem inside... using 1.0-rc1 $ maven test [ results in (when maven.junit.fork=false (default) ) ] java:prepare-filesystem: .. test:test: [junit] dir attribute ignored if running in the same VM [junit] Running com.txu.tmdb.bd.TranslateColumnNameTest [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0.33 sec [junit] [ERROR] TEST com.txu.tmdb.bd.TranslateColumnNameTest FAILED $ maven test [ results in (when maven.junit.fork=true ) java:prepare-filesystem: .. test:test: [junit] Running com.txu.tmdb.bd.TranslateColumnNameTest [junit] java.lang.NoClassDefFoundError: org/w3c/dom/Node [junit] at java.lang.Class.forName0(Native Method) [junit] at java.lang.Class.forName(Class.java:115) [junit] at org.apache.tools.ant.taskdefs.optional.junit.FormatterElement. createFormatter(FormatterElement.java:1 83) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner. createAndStoreFormatter(JUnitTestRunner. java:562) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner. main(JUnitTestRunner.java:507) [junit] Exception in thread main [junit] [ERROR] TEST com.txu.tmdb.bd.TranslateColumnNameTest FAILED what happened to the original classpath? i think the problem revolves around those unit tests using System.setProperty() to signal the need for a mock jndi datasource lookup... -- dan * Confidentiality Notice: This email message, including any attachments, contains or may contain confidential information intended only for the addressee. If you are not an intended recipient of this message, be advised that any reading, dissemination, forwarding, printing, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply message and delete this email message and any attachments from your system. * - 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]
copying the dependencies
Hi all, I'm writing a maven plugin for the JWSDP-1.3. I was using maven
rc-1 with the following tag in a goal:
deploy:copy-deps todir=${jwsdp.build}/WEB-INF/lib/
which worked well. But I decided to build maven from cvs and to start
using artifact and group ID's. Now the above tag does not work anymore.
So my question is, is there a replacement tag I should be using or did
something break between rc1 and what's in CVS as of 9:00 pm est. us?
TIA,
-ScottTavares-
p.s. I plan on contributing my jwsdp plugin once it is done if anyone is
interested in it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: copying the dependencies
I think the deploy plugin was moved, so after bootstrapping you'll need to
check out maven-plugins from CVS and run maven plugin:install on the deploy
plugin.
Alternatively, your plugin could have a dependency on the deploy plugin
dependency
typeplugin/type
artifactIdmaven-deploy-plugin/artifactId
versionWHATEVER_IT_IS_ON_IBIBLIO/version
groupIdmaven/groupId
/dependency
This is probably a good idea.
What will your JWSDP plugin do? I have previously written one for JAXB's xjc
task.
When you contribute it, it will need to go to maven-plugins.sf.net for
licensing reasons, instead of Maven's CVS (at least for now).
- Brett
-Original Message-
From: Scott Tavares [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 November 2003 1:24 PM
To: Maven Users List
Subject: copying the dependencies
Hi all, I'm writing a maven plugin for the JWSDP-1.3. I was
using maven
rc-1 with the following tag in a goal:
deploy:copy-deps todir=${jwsdp.build}/WEB-INF/lib/
which worked well. But I decided to build maven from cvs and to start
using artifact and group ID's. Now the above tag does not
work anymore. So my question is, is there a replacement tag I
should be using or did
something break between rc1 and what's in CVS as of 9:00 pm est. us?
TIA,
-ScottTavares-
p.s. I plan on contributing my jwsdp plugin once it is done
if anyone is
interested in it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Java Doc and Javac Error-- Please help! -- New bee to Maven
Please help, I am getting errors in javadoc, javac: C:\mavensporty2gmaven site:generate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT site: xdoc:register-reports: maven-checkstyle-plugin:register: maven-changelog-plugin:register: maven-developer-activity-plugin:register: maven-file-activity-plugin:register: maven-javadoc-plugin:register: maven-jdepend-plugin:register: maven-junit-report-plugin:register: maven-jxr-plugin:register: statcvs:init: maven-statcvs-plugin:register: maven-simian-plugin:register: site:run-reports: [echo] Generating the Checkstyle... checkstyle:init: checkstyle:license: checkstyle:report: [echo] Using sun_checks.xml for checkstyle ... [echo] Generating the Change Log... maven-changelog-plugin:report: [echo] Generating the changelog report SCM Working Directory: C:\mavensporty2g SCM Command Line[0]: cvs SCM Command Line[1]: -d SCM Command Line[2]: :ext:[EMAIL PROTECTED]:/wamu/app/CVS SCM Command Line[3]: log SCM Command Line[4]: -d 2003-10-072003-11-07 ChangeLog found: 137 entries [echo] Generating the Developer Activity... maven-developer-activity-plugin:report: [echo] Generating the developer activity report [echo] Generating the File Activity... maven-file-activity-plugin:report: [echo] Generating the file activity report [echo] Generating the JavaDocs... xdoc:init: maven-javadoc-plugin:report: [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\ServacctLogger.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\test\ServacctEjbJunitTestCase.java... [javadoc] Constructing Javadoc information... [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:6: package com.azzura.gregari.common.context does not exist [javadoc] import com.azzura.gregari.common.context.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:7: package com.azzura.gregari.common.dao does not exist [javadoc] import com.azzura.gregari.common.dao.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:8: package com.azzura.gregari.model.bo does not exist [javadoc] import com.azzura.gregari.model.bo.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:9: package com.azzura.gregari.model.dao does not exist [javadoc] import com.azzura.gregari.model.dao.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:11: package com.wamu.sporty2g.servacct.ejb does not exist [javadoc] import com.wamu.sporty2g.servacct.ejb.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:14: package javax.ejb does not exist [javadoc] import javax.ejb.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:16: package org.apache.commons.beanutils does not exist [javadoc] import org.apache.commons.beanutils.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:32: cannot resolve symbol [javadoc] symbol : class BOException [javadoc] location: class com.wamu.sporty2g.servacct.bo.AbstractBO [javadoc] throws BOException [javadoc]^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:63: cannot resolve symbol [javadoc] symbol : class BOException [javadoc] location: class com.wamu.sporty2g.servacct.bo.AbstractBO [javadoc] throws BOException [javadoc]^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:92: cannot resolve symbol [javadoc] symbol : class BOException [javadoc] location: class com.wamu.sporty2g.servacct.bo.AbstractBO [javadoc] throws BOException [javadoc]^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:121: cannot resolve symbol [javadoc] symbol : class BOException [javadoc] location: class com.wamu.sporty2g.servacct.bo.AbstractBO [javadoc] throws BOException [javadoc]
RE: Java Doc and Javac Error-- Please help! -- New bee to Maven
You need to specify dependencies for whatever JAR is providing... import com.azzura.gregari.common.context.*; -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 1:51 PM To: Maven Users List; Maven Users List Subject: Java Doc and Javac Error-- Please help! -- New bee to Maven
Re: copying the dependencies
Brett Porter wrote:
I think the deploy plugin was moved, so after bootstrapping you'll need to
check out maven-plugins from CVS and run maven plugin:install on the deploy
plugin.
Alternatively, your plugin could have a dependency on the deploy plugin
dependency
typeplugin/type
artifactIdmaven-deploy-plugin/artifactId
versionWHATEVER_IT_IS_ON_IBIBLIO/version
groupIdmaven/groupId
/dependency
This is probably a good idea.
Thanks! I didn't expect any to respond so quickly.
What will your JWSDP plugin do? I have previously written one for JAXB's xjc
task
Well, this is a good question. I'm not really sure how much utility it
will have but here's my thinking. I currently work as a consultant and
am doing two projects. Each project is using a different app. servers
(Sybase EAServer and JBoss). Rather then installing both servers on my
laptop and have them fight for resources it's easier to code and test
againest the JWSDP and deploy them later. Where Maven comes in is that I
want the plug in to hook into JWSDP to compile and package up into neat
war files all of my JAXRPC web services, deploy it the jwsdp server
(tomcat) then have maven run unit tests againest them. Lastly, once I'm
on-line I want it to deploy the war files to either of the two app. servers.
The other motivating factors are that I wanted to learn Maven as well as
how to effectively use the jwsdp. So there you go, and once again
thanks for the info.
-ScottTavares-
When you contribute it, it will need to go to maven-plugins.sf.net for
licensing reasons, instead of Maven's CVS (at least for now).
- Brett
-Original Message-
From: Scott Tavares [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 November 2003 1:24 PM
To: Maven Users List
Subject: copying the dependencies
Hi all, I'm writing a maven plugin for the JWSDP-1.3. I was
using maven
rc-1 with the following tag in a goal:
deploy:copy-deps todir=${jwsdp.build}/WEB-INF/lib/
which worked well. But I decided to build maven from cvs and to start
using artifact and group ID's. Now the above tag does not
work anymore. So my question is, is there a replacement tag I
should be using or did
something break between rc1 and what's in CVS as of 9:00 pm est. us?
TIA,
-ScottTavares-
p.s. I plan on contributing my jwsdp plugin once it is done
if anyone is
interested in it.
-
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: High ASCII in java code not compiling under Maven
Thanx. That did the trick. jeff Erdfelt, Joakim wrote: We had success with the 'maven.compile.fork=true' and 'maven.compile.encoding=iso8859-1' properties defined at the maven-java-plugin web page. http://maven.apache.org/reference/plugins/java/properties.html /* joakim erdfelt */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Java Doc and Javac Error-- Please help! -- New bee to Maven
Thank you that did the trick for most of errors I had in javadocs, But I still get this error about javax package, I was trying to figure which folder i need to include in dependices: C:\mavensporty2gmaven javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT xdoc:init: maven-javadoc-plugin:report: [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\ServacctLogger.java... [javadoc] Loading source file C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\test\ServacctEjbJunitTestCase.java... [javadoc] Constructing Javadoc information... [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:11: package com.wamu.sporty2g.servacct.ejb does not exist [javadoc] import com.wamu.sporty2g.servacct.ejb.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\bo\AbstractBO.java:14: package javax.ejb does not exist [javadoc] import javax.ejb.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:10: package javax.ejb does not exist [javadoc] import javax.ejb.*; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:23: cannot resolve symbol [javadoc] symbol : class SessionBean [javadoc] location: class com.wamu.sporty2g.servacct.dao.ServacctDAO [javadoc] implements SessionBean [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:26: cannot resolve symbol [javadoc] symbol : class SessionContext [javadoc] location: class com.wamu.sporty2g.servacct.dao.ServacctDAO [javadoc] public SessionContext sessionContext; [javadoc] ^ [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:222: cannot resolve symbol [javadoc] symbol : class SessionContext [javadoc] location: class com.wamu.sporty2g.servacct.dao.ServacctDAO [javadoc] public void setSessionContext( SessionContext sessionContext ) [javadoc] ^ [javadoc] Standard Doclet version 1.4.2 [javadoc] Generating C:\mavensporty2g\target\docs\apidocs\constant-values.html... [javadoc] Copying file D:\Documents and Settings\srauf\.maven\plugins\maven-javadoc-plugin-1.3\plugin-resources\stylesheet.css to file C:\mavensporty2g\target\docs\apidocs\stylesheet.css... [javadoc] Building tree for all the packages and classes... [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:21: warning - @ejb:bean is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:21: warning - @ejb:transaction is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:21: warning - @ejb:home is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:21: warning - @ejb:interface is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:21: warning - @ejb:util is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:43: warning - @ejb:interface-method is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:43: warning - Tag @see: reference not found: com.azzura.gregari.model.dao.DAOResponse [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:64: warning - @ejb:interface-method is an unknown tag. [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:64: warning - Tag @see: reference not found: com.azzura.gregari.model.dao.DAOResponse [javadoc] C:\mavensporty2g\sporty2g\servacct\ejb\src\java\com\wamu\sporty2g\servacct\dao\ServacctDAO.java:85: warning - @ejb:interface-method is an unknown tag. [javadoc]
RE: Java Doc and Javac Error-- Please help! -- New bee to Maven
Where is it sun's website, j2ee.jar, I couldn't find it. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 10:06 PM To: 'Maven Users List' Subject: RE: Java Doc and Javac Error-- Please help! -- New bee to Maven Probably j2ee.jar, which you will have to manually download from Sun and put in your local repository as we are not allowed to distribute it. - Brett -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 2:48 PM To: Maven Users List; Maven Users List Subject: RE: Java Doc and Javac Error-- Please help! -- New bee to Maven Thank you that did the trick for most of errors I had in javadocs, But I still get this error about javax package, I was trying to figure which folder i need to include in dependices: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Java Doc and Javac Error-- Please help! -- New bee to Maven
Download J2EE reference implementation, or pull it from whatever the EJB container is that you are using (you have built this project somewhere before haven't you? It must have gotten them from somewhere...) - Brett -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 3:29 PM To: Maven Users List Subject: RE: Java Doc and Javac Error-- Please help! -- New bee to Maven Where is it sun's website, j2ee.jar, I couldn't find it. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 10:06 PM To: 'Maven Users List' Subject: RE: Java Doc and Javac Error-- Please help! -- New bee to Maven Probably j2ee.jar, which you will have to manually download from Sun and put in your local repository as we are not allowed to distribute it. - Brett -Original Message- From: Rauf, Saleem [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2003 2:48 PM To: Maven Users List; Maven Users List Subject: RE: Java Doc and Javac Error-- Please help! -- New bee to Maven Thank you that did the trick for most of errors I had in javadocs, But I still get this error about javax package, I was trying to figure which folder i need to include in dependices: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I exclude files from compile
Hi Alain, It worked fine. Thanks a million :-) Am still not clear about the className. Any idea what it is for??? Thanks Regards, Ranes. - Original Message - From: Alain Javier Guarnieri del Gesu [EMAIL PROTECTED] To: R a n e s [EMAIL PROTECTED] Cc: Maven Users List [EMAIL PROTECTED] Sent: Thursday, November 06, 2003 2:44 PM Subject: Re: How do I exclude files from compile * R a n e s [EMAIL PROTECTED] [2003-11-06 07:14]: Hi Nicolas, Thanks for your suggestion. I tried something like this, but it doesn't seems to be working for me :( sourceModifications sourceModification classNameProcessorTest/className excludes exclude**test*.java/exclude exclude**Test*.java/exclude /excludes /sourceModification /sourceModifications Try: **/Test*.java ^ | +- Add a file separator. -- Alain Javier Guarnieri del Gesu - [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: Building Maven
Horn, Cameron [EMAIL PROTECTED] wrote on 06/11/2003 02:57:36
PM:
You have been extremely helpful, which has been the most promising
thing so far. Thank you. On the other hand, it does seem like
maven still needs a heck of a lot of work.
Sure does. As does Ant, JUnit and any other piece of software.
It also seems like maven has a very singular way of working that
doesn't really suit the way I want to work. Is there interest in
broadening the way maven can work (say, satisfying dependencies with
CVS), or should efforts to that end be devoted to a different project?
You can specify that your jars are not in the repository using a 'jar
override' feature.
See the user's guide,
http://maven.apache.org/reference/user-guide.html#Overriding%20Stated%20Dependencies
, for more information.
The users guide gives an example of how you can use the jar override to
point to jars 'in CVS', in that case, in ${basedir}/lib.
Re: task appearance
Odd, that. Does the annoying ASCII art supercede task labels?
Supercede, no. Augment, yes.
Re: dependencies
This behavior also suggests that it would be impossible to lock
down a potential set of dependencies that a project can use. Even
Maven does not force people to use or lock down a set of dependencies.
What ever you can get into the local repo can be used to build.
[snip]
Re: return codes
I'll submit an issue for it tomorrow, but if anyone was curious,
here's a snippet:
snip
[exec] +
[exec] | Building Maven VDoclet Plug-in
[exec] | Memory: 156M/158M
[exec] +
snip
[exec] java:compile:
[exec] [echo] Compiling to C:
\blah\jbuild\maven\src\plugins-build\vdoclet/target/classes
[exec] [javac] Compiling 1 source file to C:
\blah\jbuild\maven\src\plugins-build\vdoclet\target\classes
[exec] BUILD FAILED
[exec] com.werken.werkz.UnattainableGoalException: Unable to
obtain goal [plugin] -- file:/C:/Documents and Settings/hornc/.
maven/plugins/java/:55:48: ant:javac Error starting modern compiler
snip very long error description
[exec] Unable to obtain goal [plugin] -- file:/C:/Documents and
Settings/hornc/.maven/plugins/java/:55:48: ant:javac Error
starting modern compiler
[echo]
[echo]
+--+
[echo] ||
[echo] | I N S T A L L I N G T H E P L U G I N S|
[echo] ||
[echo]
+--+
[echo]
snip happily continuing build
I don't know when this was taken from, but CVS HEAD no longer has the
vdoclet plugin as part of the bootstrap process.
BTW, the bootstrap process is built in Ant for the most part. I suppose we
could update the bootstrap exec to failonerror.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
