Re: Maven and ejbdoclet/xdoclet examples
Thanks!
I will try this.
Nathan
Dennis Geurts wrote:
Hi nathan,
the thing is, maven does not complain about missing dependencies ( for
instance, the jmx-module is needed, but if you don't add its jar to the
list of dependencies, maven won't tell !!) -- maybe this is even the
cause you're experiencing failure to generate the interfaces...
running 'maven -X ...' will probably warn you saying: missing
'xxx.jar' but it will be easy to miss
I myself have used ejbdoclet in combination with middlegen. I personally
didn't like to use the ejbdoclet plugin. Instead, I used
the ant task from within maven:
- relevant dependencies in project.xml are included in deps.txt
- relevant properties are included in props.txt
Since I used the Ant task, I needed to define some extra goals in the
maven.xml
- relevant goals are included in goals.txt
I really hope this helps getting you on the road.
Since I'm new at this list, please excuse me if this is totally off topic...
Dennis Geurts
On 6/16/05, *Nathan Sowatskey* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi
I have tried to follow the examples that I can find for Maven and
xdoclet, and I have it apparently running, that it doesn't complain
about dependencies, but it doesn't seem to be processing my EJB to
generate the interfaces and deployment descriptors that I expect.
I can get this to work with Ant, but not Maven it seems.
Does anyone have any pointers to a project that I could peruse to get
some hints please? I looked at geronimo, but it doesn't seem to employ
ejbdoclet.
Many thanks
Nathan
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk
+44-208-824-4259/+1-408-527-2595 - Mobile +44-7740-449794 - AIM id
NathanCisco - [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
!-- XDoclet dependencies --
dependency
groupIdservletapi/groupId
artifactIdservletapi/artifactId
version2.3/version
typejar/type
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet/artifactId
version1.2/version
typejar/type
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-web-module/artifactId
version1.2/version
typejar/type
urlhttp://xdoclet.sf.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-ejb-module/artifactId
version1.2/version
typejar/type
urlhttp://xdoclet.sf.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-jmx-module/artifactId
version1.2/version
typejar/type
urlhttp://xdoclet.sf.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxjavadoc/artifactId
version1.0.2/version
typejar/type
urlhttp://xdoclet.sf.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdmaven-xdoclet-plugin/artifactId
version1.2/version
typeplugin/type
urlhttp://xdoclet.sf.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-jboss-module/artifactId
version1.2/version
typejar/type
/dependency
gen.dir=${maven.build.dir}/middlegen/cmp20
ejb.dir=${maven.build.dir}/xdoclet/ejbdoclet
ejb.meta.dir=${maven.build.dir}/xdoclet/ejb
xdoclet.ejbdoclet.mergedir=${maven.src.dir}/merge/xdoclet/ejbdoclet
maven.eclipse.classpath.include=target/middlegen/cmp20/,target/xdoclet/ejbdoclet
maven.war.webapp.dir=${maven.build.dir}/xdoclet/webdoclet
maven.xdoclet.webdoclet.0=true
maven.xdoclet.webdoclet.0.destDir=${maven.build.dir}/xdoclet/webdoclet/WEB-INF
maven.xdoclet.webdoclet.0.mergeDir=${maven.src.dir}/merge/xdoclet
maven.xdoclet.webdoclet.deploymentdescriptor.0.destDir=${maven.build.dir}/xdoclet/webdoclet/WEB-INF
maven.xdoclet.webdoclet.deploymentdescriptor.0.mergeDir=${maven.src.dir}/merge/xdoclet
preGoal name=java:compile
!-- mkdir dir=${maven.build.dir}/xdoclet/webdoclet/WEB-INF /--
!-- attainGoal name=xdoclet:webdoclet /--
attainGoal name=ejbdoclet /
/preGoal
goal name=ejbdoclet
ant:taskdef name=ejbdoclet
site:deploy on multiproject
Hi Using maven site:deploy generates the site and use configured method to deploy site on my HTTP server But my project is the parent of a multiproject application. Running site:deploy doesn't run the multiproject:site goal to produce the full site. Is they're some property to set to get this to run fine ? I have to run multiproject:site and the site:xxdeply to get the expected result. Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Lines of Code aggregator for dashboard?
Hi, is there an aggregator for dashboard to calculate the (non-comments) lines of code of the production and the testcode. I currently use Clover and this gives me a figure, but I suspect this is only the LOC and NCLOC of the production code? regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Component Descriptor Error Message
Simon McClenahan wrote:
I'm running Maven under Windows, and I was unable to specify the drive
letter. Conveniently I do everything on my C: drive, and I have ended up
using the following:
maven.repo.remote=file:///localhost/projects/online/trunk/,http://www.ib
iblio.org/maven/
I know it doesn't seem right, but I figured this out by trial and error.
I'm using Maven 1.0.2.
- Simon
If you're using Maven 1.0.2, you could just place the jars in your local
repository and not go through the trouble of mirroring a remote
repository on your machine. Maven checks the local repository first for
dependencies before attempting to download from the remote repository.
Usually, the local repository is found in ${maven.home.local}/repository
where maven.home.local is ${user.home}/.maven. So if you're using
Windows, and your user name is for example, User1, your local repository
would be found in C:\Documents and Settings\User1\.maven.
Hope this clears up a few things. Regards,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
wsdl2java
Hi I'm trying to use the axis plugin (from maven-plugins.sf.net) to generate wsdl from my java classes. I get error Attempted to write schema for bad QName (no namespace) There is no doc about this feature on plugin site. Can someone give me a working example ? Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:[m2] Overriding webapp source directory
I guess my webmail is quite buggy then :)
I was already given the solution for the build tag,
but thanks for the detail about ${basedir} !
Regards,
Yann
-- Mail d'origine ---
De : quot;Kenney Westerhofquot; [EMAIL PROTECTED]
A : quot;Maven Users Listquot;
users@maven.apache.org
Cc :
Date : Thu, 16 Jun 2005 11:21:43 +0200 (CEST)
Objet : Re:[m2] Overriding webapp source directory
-On Thu, 16 Jun 2005, Yann LE DU wrote:
-
-The first post seemed fine :)
-
-I guess you're using the maven-war-plugin (you
specified war
-as the packaging in the pom?). In that case,
-add the following below your build tag:
-
- plugins
- plugin
- artifactIdmaven-war-plugin/artifactId
- configuration
-
warSourceDirectoryfinal-foo/WebContent/warSourceDirectory
- /configuration
-/plugin
- /plugins
-
-Btw it's best to prepend ${basedir} to those paths,
because
-if the project is part of a multiproject build the current
-directory is taken as a starting point which may be bad ;)
-
--- Kenney
-
-
- So much for my project tree, all blanks were gotten rid
- of :)
-
- Here is another try :
-
- - foo
- - |-- final-foo
- - |-- JavaSource
- - |-- com
- - |-- ...
- - |-- WebContent
- - |-- WEB-INF
- - |-- ...
- - |--...
-
-
- Yann
-
-
-
- -- Mail d'origine ---
-
- De : quot;Yann LE DUquot; [EMAIL PROTECTED]
- A : users@maven.apache.org
- Cc :
- Date : Thu, 16 Jun 2005 11:06:11 +0200
- Objet : [m2] Overriding webapp source directory
-
-
-
- -Hi there,
- -
- -I'm 2-week-old to Maven and trying to build a small
- -webapp with Maven (for POC). The thing is, my corp. is
- -already using Eclipse Web Tools, which forces us into
- -this kind of project structure (I hid test directories
- -for readability) :
- -
- -foo
- -|-- final-foo
- -|-- JavaSource
- -|-- com
- -|-- ...
- -|-- WebContent
- -|-- WEB-INF
- -|-- ...
- -|--...
- -
- -Even though I know this isn't the way Maven is supposed
- -to work :) , I partly solved the issue by including the
- -following in my foo/pom.xml :
- -
- -build
- -
sourceDirectoryfinal-foo/JavaSource/sourceDirectory
- -/build
- -
- -...which is working well, but I'd like to do the same
- -for the webapp directory, that is, something like :
- -
-
-webappSourceDirectoryfinal-foo/WebContent/webappSourceDirectory
- -
- -I haven't found anything in docs, JIRA, user lists. Is
- -there any way ?
- -
- -Yann
- -
- -
-
--
- -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]
-
-
-
---
-Kenney Westerhof
-http://www.neonics.com
-GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
--
-To unsubscribe, e-mail: [EMAIL PROTECTED]
-For additional commands, e-mail:
[EMAIL PROTECTED]
-
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[solved] Re: wsdl2java
I made it work I just didnt' understood the requirement for a property for each service to set location and namespace : maven.axis.classnames = com.MyService com.MyService = http://location,urn:namespace Nico. Nicolas De Loof a crit : Hi I'm trying to use the axis plugin (from maven-plugins.sf.net) to generate wsdl from my java classes. I get error Attempted to write schema for bad QName (no namespace) There is no doc about this feature on plugin site. Can someone give me a working example ? Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
while run the Goal, how can I get Status by mail
Hai Maven Users 1.I integrated all goals in maven.xml. While run one goal, it initiates all dependent goals also ok, how I can get through mail all goals status. 2.what is the purpose of following tag in project.xml developer nameSasikumar/name idSasi/id email[EMAIL PROTECTED]/email organizationABC/organization /developer Thanks in Advance Cheers Sasikumar Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.
Re: site:deploy on multiproject
multiproject:site-deploy ? http://maven.apache.org/reference/plugins/multiproject/goals.html On 6/17/05, Nicolas De Loof [EMAIL PROTECTED] wrote: Hi Using maven site:deploy generates the site and use configured method to deploy site on my HTTP server But my project is the parent of a multiproject application. Running site:deploy doesn't run the multiproject:site goal to produce the full site. Is they're some property to set to get this to run fine ? I have to run multiproject:site and the site:xxdeply to get the expected result. Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:while run the Goal, how can I get Status by mail
Hi Sasikumar, As I understood it, the purpose of developer tag is to collect some info about each developer or contributor in the project, in order to build mailing-lists and generate activity reports. For a good start, see this book : http://mavenbook.xwiki.com/xwiki/bin/view/Main/WebHome The first chapter is free : http://www.oreilly.com/catalog/mavenadn/chapter/ch01.pdf (see page 30 for your question) Regards, Yann -- Mail d'origine --- De : quot;NATARAJAN Sasi Kumarquot; [EMAIL PROTECTED] A : quot;Maven Users Listquot; users@maven.apache.org Cc : Date : Fri, 17 Jun 2005 14:32:06 +0530 Objet : while run the Goal, how can I get Status by mail -Hai Maven Users - - - -1.I integrated all goals in maven.xml. While run one goal, it initiates -all dependent goals also ok, how I can get through mail all goals -status. - -2.what is the purpose of following tag in project.xml - - - - developer - - nameSasikumar/name - - idSasi/id - - email[EMAIL PROTECTED]/email - - organizationABC/organization - - /developer - - - -Thanks in Advance - - - -Cheers - -Sasikumar - - - -Confidentiality Statement: - -This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email. - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiprojects and dependencies list
Thanks Vincent, This is exactly what I was looking for !! Excepted that I will probably read the .classpath file rather than the project.xml file but I'm not sure yet. I'll test both. Best Damien -- Damien Viel | +33 1 41 97 83 20 | [EMAIL PROTECTED] -- __/ \__ | http://www.improve.fr improve | http://www.application-servers.com /_\-| http://www.improve-technologies.com -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vincent Massol Sent: jeudi 16 juin 2005 18:56 To: 'Maven Users List' Subject: RE: Multiprojects and dependencies list Hi Damien, Maybe this will help you: http://mavenbook.xwiki.com/xwiki/bin/view/Main/Tip5ListingDependencies -Vincent -Original Message- From: Damien Viel [mailto:[EMAIL PROTECTED] Sent: jeudi 16 juin 2005 17:34 To: 'Maven Users List' Subject: Multiprojects and dependencies list Hi all, Is it possible to have the list off all the dependecies of the projects included in a multiproject build (like in the dependency-convergence report) ? Thanks Damien ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Tlchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] artifact problem when installing pom.xml in local repo
Already reported: http://jira.codehaus.org/browse/MAVEN-1625 Oddly, it works for me. Somehow it thinks it is running inside Maven 1.0.2 instead of Maven 1.1. - Brett On 6/17/05, Nicolas Chalumeau [EMAIL PROTECTED] wrote: I just install 1.1-beta-1 all seems to be ok except with the pom installation in my local repository... When I execute a war:install the .war, .war.sha1, .war.md5 are copy in local repository war directory but the pom produce an exception. I don't know what is the cause so this is a part of the -X log war:install: [echo] Installing... Uploading to upranet/wars/upranet-common-0.4-SNAPSHOT.war: (11185K) LA CONSTRUCTION A CHOU Fichier... C:\Documents and Settings\chalumeau\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly lement... artifact:artifact-install Ligne. 62 Colonne... -1 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [war:install] -- C:\Documents and Settings\chalumeau\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List; )V at org.apache.maven.werkz.Goal.fire(Goal.java:663) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.werkz.Goal.attainPrecursors(Goal.java:505) at org.apache.maven.werkz.Goal.attain(Goal.java:590) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: C:\Documents and settings\chalumeau\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:193) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78) ... Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.java:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(DefaultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java:160)
Re: Maven 1.1 Beta 1 Released
Hi Brett, It looks like some changes are affecting the javadoc generation. When I run maven javadoc after the maven upgrade, I get the following error: Incompatible initial and maximum heap sizes specified [See the error output below]. I tried running the command with or without setting maven.javadoc.additionalparam=-J-Xmx512m maven.javadoc.maxmemory = 512 Note: I have MAVEN_OPTS set to -Xmx512m in my environment. Any ideas? --mike maven -Dmaven.javadoc.debug=true javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: xdoc:init-i18n: [echo] Init the i18n support xdoc:init: [echo] Generates the directory structure required for xdocs maven-javadoc-plugin:report: [echo] javadoc init [echo] ### Debug mode is on ### == === java plugin properties === == maven.compile.encoding= [] maven.compile.src.set = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/src/java] == === docs properties=== == maven.docs.outputencoding = [ISO-8859-1] == === javadoc plugin properties === == Javadoc properties : maven.javadoc.additionalparam = [-J-Xmx512m] maven.javadoc.debug = [true] maven.javadoc.doclet = [] maven.javadoc.docletpath = [] maven.javadoc.excludepackagenames = [] maven.javadoc.locale = [] maven.javadoc.maxmemory = [512] maven.javadoc.overview= [] maven.javadoc.package = [] maven.javadoc.private = [] maven.javadoc.public = [] maven.javadoc.source = [] maven.javadoc.useexternalfile = [yes] Standard doclet properties : maven.javadoc.author = [true] maven.javadoc.bottom = [Copyright amp;copy; BPS Smart Documents Platforms Group. All Rights Reserved.] maven.javadoc.customtags = [] maven.javadoc.destdir = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/docs/apidocs] maven.javadoc.links = [] maven.javadoc.offlineLinks= [] maven.javadoc.mode.online = [] maven.javadoc.stylesheet = [/home/niemaz/.maven/cache/maven-javadoc-plugin-1.7/plugin-resources/stylesheet.css] maven.javadoc.tagletpath = [] maven.javadoc.taglets = [] maven.javadoc.use = [true] maven.javadoc.version = [true] maven.javadoc.windowtitle = [SmartDocument Blob detector 1.1.1 API] == === Project descriptor === == pom.package = [com.xerox.smartdocument.services.blob] == === javadoc internal variables === == internal_javadoc_jar = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/smartdocument.blob-1.1.1_javadoc.jar] internal_javadoc_needed = [] internal_javadoc_working_dir = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/javadoc] [mkdir] Created dir: /home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/javadoc/src [echo] sourceModifications not used. [echo] internal_javadoc_needed is true [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Error occurred during initialization of VM [javadoc] Incompatible initial and maximum heap sizes specified Brett Porter wrote: The Apache Maven team is pleased to announce the release of Maven 1.1-beta-1 http://maven.apache.org/start/download.html Maven is a project management and project comprehension tool. Maven is based on the concept of a project object model: builds, documentation creation, site publication, and distribution publication are all controlled from the project object model. Maven also provides tools to create source metrics, change logs based directly on source repository, and source cross-references. This release focuses on the following objectives: * Integration of Maven 2 technologies such as Maven Wagon, Maven SCM and the new model code * Ant 1.6.5 support * Upgrade to later releases of dependencies, in particular Jelly * Significant improvements
Re: Maven 1.1 Beta 1 Released
Found the problem: forgot the 'm' after 512 for the maxmemory ... Sorry for that ;-) --mike Michael Niemaz wrote: Hi Brett, It looks like some changes are affecting the javadoc generation. When I run maven javadoc after the maven upgrade, I get the following error: Incompatible initial and maximum heap sizes specified [See the error output below]. I tried running the command with or without setting maven.javadoc.additionalparam=-J-Xmx512m maven.javadoc.maxmemory = 512 Note: I have MAVEN_OPTS set to -Xmx512m in my environment. Any ideas? --mike maven -Dmaven.javadoc.debug=true javadoc __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: xdoc:init-i18n: [echo] Init the i18n support xdoc:init: [echo] Generates the directory structure required for xdocs maven-javadoc-plugin:report: [echo] javadoc init [echo] ### Debug mode is on ### == === java plugin properties === == maven.compile.encoding= [] maven.compile.src.set = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/src/java] == === docs properties=== == maven.docs.outputencoding = [ISO-8859-1] == === javadoc plugin properties === == Javadoc properties : maven.javadoc.additionalparam = [-J-Xmx512m] maven.javadoc.debug = [true] maven.javadoc.doclet = [] maven.javadoc.docletpath = [] maven.javadoc.excludepackagenames = [] maven.javadoc.locale = [] maven.javadoc.maxmemory = [512] maven.javadoc.overview= [] maven.javadoc.package = [] maven.javadoc.private = [] maven.javadoc.public = [] maven.javadoc.source = [] maven.javadoc.useexternalfile = [yes] Standard doclet properties : maven.javadoc.author = [true] maven.javadoc.bottom = [Copyright amp;copy; BPS Smart Documents Platforms Group. All Rights Reserved.] maven.javadoc.customtags = [] maven.javadoc.destdir = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/docs/apidocs] maven.javadoc.links = [] maven.javadoc.offlineLinks= [] maven.javadoc.mode.online = [] maven.javadoc.stylesheet = [/home/niemaz/.maven/cache/maven-javadoc-plugin-1.7/plugin-resources/stylesheet.css] maven.javadoc.tagletpath = [] maven.javadoc.taglets = [] maven.javadoc.use = [true] maven.javadoc.version = [true] maven.javadoc.windowtitle = [SmartDocument Blob detector 1.1.1 API] == === Project descriptor === == pom.package = [com.xerox.smartdocument.services.blob] == === javadoc internal variables === == internal_javadoc_jar = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/smartdocument.blob-1.1.1_javadoc.jar] internal_javadoc_needed = [] internal_javadoc_working_dir = [/home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/javadoc] [mkdir] Created dir: /home/niemaz/smartdocuments_svn/smartdocuments/trunk/smartdocument.services/blobdetector/target/javadoc/src [echo] sourceModifications not used. [echo] internal_javadoc_needed is true [javadoc] Generating Javadoc [javadoc] Javadoc execution [javadoc] Error occurred during initialization of VM [javadoc] Incompatible initial and maximum heap sizes specified Brett Porter wrote: The Apache Maven team is pleased to announce the release of Maven 1.1-beta-1 http://maven.apache.org/start/download.html Maven is a project management and project comprehension tool. Maven is based on the concept of a project object model: builds, documentation creation, site publication, and distribution publication are all controlled from the project object model. Maven also provides tools to create source metrics, change logs based directly on source repository, and source cross-references. This release focuses on the following objectives: * Integration of Maven 2 technologies such as Maven Wagon, Maven SCM and the
Re: while run the Goal, how can I get Status by mail
HI, you can not send mails directly with maven, you can only set a nagemailadress but this you can only use in combination with an other tool. Such an ohter tool is cruisecontrol, anthill or luntbuild. This tools also make the continous integration. NATARAJAN Sasi Kumar wrote: Hai Maven Users 1.I integrated all goals in maven.xml. While run one goal, it initiates all dependent goals also ok, how I can get through mail all goals status. 2.what is the purpose of following tag in project.xml developer nameSasikumar/name idSasi/id email[EMAIL PROTECTED]/email organizationABC/organization /developer Thanks in Advance Cheers Sasikumar Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compiling J2SE 5.0
Another newbie question for you guys (big thanks by the way!): How do I set up Maven so it will compile with a target and source of 1.5. I know how to do this in Ant, and I can see the properties for the compiler:compiler plugin, but I don't really understand where I should set them. I'm using Maven 2.0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Remote repository version control
I am specifying a remote repository because the jar files I need are
stored in my version control system, where I have checked them out into
my local filesystem. I would have like to specify a relative path to the
remote repository, but I don't think that's possible with a URL scheme.
I have not attempted to setup a multiproject configuration in Maven yet,
but what would be the best practice for version control of artifacts in
a remote repository that is referenced locally? Maybe this is the
complicated way of doing it. Should I be creating a remote repository to
upload to on a shared resource (e.g. network drive) instead and not be
concerned about version control?
- Simon
-Original Message-
From: Henry Isidro [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 16, 2005 7:06 PM
To: Maven Users List
Subject: Re: Component Descriptor Error Message
Simon McClenahan wrote:
I'm running Maven under Windows, and I was unable to specify the drive
letter. Conveniently I do everything on my C: drive, and I have ended
up
using the following:
maven.repo.remote=file:///localhost/projects/online/trunk/,http://www.i
b
iblio.org/maven/
I know it doesn't seem right, but I figured this out by trial and
error.
I'm using Maven 1.0.2.
- Simon
If you're using Maven 1.0.2, you could just place the jars in your local
repository and not go through the trouble of mirroring a remote
repository on your machine. Maven checks the local repository first for
dependencies before attempting to download from the remote repository.
Usually, the local repository is found in ${maven.home.local}/repository
where maven.home.local is ${user.home}/.maven. So if you're using
Windows, and your user name is for example, User1, your local repository
would be found in C:\Documents and Settings\User1\.maven.
Hope this clears up a few things. Regards,
Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
NOTE: This message and any included attachments are from HealthCom Partners,
LLC and are intended only for the addressee(s). The information contained
herein may include trade secrets or privileged or otherwise confidential
information. Unauthorized review, forwarding, printing, copying, distributing,
or using such information is strictly prohibited and may be unlawful. If you
received this message in error, or have reason to believe you are not
authorized to receive it, please promptly delete this message and notify the
sender by e-mail.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Exception with maven 1.1-beta-1
I just download maven-1.1-beta-1 and try to run it. 'maven jar:install' works fine with maven 1.0.2 but when I run this command with the latest M1 I got an exception. What does it mean?? BUILD FAILED File.. C:\Documents and Settings\anatol\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly Element... artifact:artifact-install Line.. 62 Column -1 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [jar:install] -- C:\Documents and Settings\anatol\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.werkz.Goal.fire(Goal.java:663) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: C:\Documents and Settings\anatol\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:193) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109) at org.apache.maven.werkz.Goal.fire(Goal.java:656) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.java:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(DefaultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180) ... 19 more Root cause java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.java:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(DefaultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java:160) at
Re: Problem targeting two platform builds with Maven 2.0
I'm a bit confused by the initial problem posed in this thread. This may
expose a fundamental misunderstanding of Java on my part, but if so I'd like
it cleared up by this fine group sooner rather than later.
I routinely build a project for a CDC target using a Sun J2SE 1.3 boot class
path, and run the same class files on Sun J2SE VMs (1.3, 1.4 and 1.5) and
IBM's J9 CDC VM (1.3). Using the CDC classpath would probably be better
since that's the more restrictive environment, but the point is that Java
class files are portable. As long as you build to byte code compatible with
the oldest VM and comply with the API of the most restrictive environment,
the class files should run on any VM regardless of what your classpath looks
like when you compile, right? This has always been my understanding, and has
also been my experience. Optimizing doesn't appear to affect this, either.
So, if the source code is truly unchanged, why not always compile with the
oldest and/or most restrictive JDK libraries, and run it wherever you want?
Have the optimizing compilers gotten so much better that it's worth the
extra hassle of maintaining two sets of distribution jars? Do newer VMs run
notably slower with older byte code, again enough to be worth the
maintenance hassle?
Are you using an ahead-of-time compiler to go all the way to executables?
Even then, I'd think the build solution would be to javac to a jar you could
use anywhere then AOT the jar to your embedded target. Is there JNI, in
which case you have all the usual non-Java problems with target platform
portability?
What am I missing?
Jay
Yes, this is supported through profiles in alpha-3. You can try it from SVN
today, or wait for the release next week. Some of the repository support may
still need some work, so we'd be interested to hear your experiences.
Cheers,
Brett
On 6/17/05, Shane Isbell [EMAIL PROTECTED] wrote:
By separate executions, I mean separate executions of xml.pom[myproject].
On 6/16/05, Shane Isbell [EMAIL PROTECTED] wrote:
Say the project structure is something like
myproject
---pom.xml
+--subproject 1
---pom.xml
+--subproject 2
---pom.xml
In this case, the pom.xml[myproject] is the parent project. What I
am trying to find out is if there is way to type
m2 {target -CDC} install
and have this target request proprogated to pom.xml[subproject 1]
and pom.xml[subproject 2]. Separate executions of m2 {target -CDC}
install and m2 {target -J2SE} install are ok as long as the
repository handles separate versions of the JAR.
Can this be done through the profile?
Thanks,
Shane
On 6/16/05, Brett Porter [EMAIL PROTECTED] wrote:
This sounds more like a profile solution, where the developer
picks which one they want to use.
m2 --profile=CDC package
m2 --profile=j2se package
You said earlier you wanted to have a parent project that would
build both, though. Can you elaborate on that? This is the part
that is not currently supported, the profile executions must be
separate.
Thanks,
Brett
On 6/17/05, Shane Isbell [EMAIL PROTECTED] wrote:
Hi Brett,
The use case is as follows: Each sub project has a single set of
source files. The developer sets a target flag to CDC or J2SE.
Depending on the flag, the build tool compiles the Java source
files under either CDC or J2SE. In the case of CDC, the build
tool uses a different bootclasspath during compilation. Next.
the build tool packages the classes within a jar file, appending
myfile-platform.jar, where platform is either CDC or J2SE,
depending on the target. End.
The reason that I do not want to split these into separate
projects is that the source files are the same. If a developer
modifies, say the CDC source, it is not reflected in the J2SE
source, which leads to versioning problems. Given that I am
compiling with different bootclasspaths, I do not believe that
the solution that you outlined below would work. I will however,
look into it.
Regards,
Shane
On 6/16/05, Brett Porter [EMAIL PROTECTED] wrote:
In Maven, a POM is a unit of work, so a project must have just
one.
Usually, targetting multiple platforms involves setting up
multiple projects.
pom.xml - parent that has modules/ for the following:
+- foo-common/pom.xml - shared information
+- foo-j2se/pom.xml - j2se specific build, depends on
+foo-common
+- foo-cdc/pom.xml - CDC specific build, depends on foo-common
Does this suit your situation? What are the actual differences
between the two platforms?
We currently have a new solution for environmental specifics
in
alpha-3 (profiles), however these are not intended to be used
to build multiple
Re: Exception with maven 1.1-beta-1
it's a blocking problem :-( It's because you defined properties in your dependencies http://jira.codehaus.org/browse/MAVEN-1625 Arnaud On 6/17/05, Anatol Pomozov [EMAIL PROTECTED] wrote: I just download maven-1.1-beta-1 and try to run it. 'maven jar:install' works fine with maven 1.0.2 but when I run this command with the latest M1 I got an exception. What does it mean?? BUILD FAILED File.. C:\Documents and Settings\anatol\.maven\cache\maven-artifact-plugin-1.5.2\plugin.jelly Element... artifact:artifact-install Line.. 62 Column -1 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [jar:install] -- C:\Documents and Settings\anatol\.maven\cache\maven- artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.werkz.Goal.fire(Goal.java:663) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java :693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.apache.commons.jelly.JellyTagException: C:\Documents and Settings\anatol\.maven\cache\maven- artifact-plugin-1.5.2\plugin.jelly:62:-1: artifact:artifact-install org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java :193) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java :102) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:78) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:109) at org.apache.maven.werkz.Goal.fire(Goal.java:656) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java :693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel( PomRewriter.java:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java :57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall( DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install( DefaultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java :160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java :180) ... 19 more Root cause java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel( PomRewriter.java:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java :57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall( DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install( DefaultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java :160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(
Re: Remote repository version control
On 6/17/05, Simon McClenahan [EMAIL PROTECTED] wrote: I am specifying a remote repository because the jar files I need are stored in my version control system, where I have checked them out into my local filesystem. I would have like to specify a relative path to the remote repository, but I don't think that's possible with a URL scheme. I have not attempted to setup a multiproject configuration in Maven yet, but what would be the best practice for version control of artifacts in a remote repository that is referenced locally? Maybe this is the complicated way of doing it. Should I be creating a remote repository to upload to on a shared resource (e.g. network drive) instead and not be concerned about version control? I would say that the cleanest way is to create a repository on a shared resource. If you really want to include your dependencies in your versionning tool, it probably makes sense only if they are included with your project. So in this case, put them in your project tree and copy them at the right place with a maven.xml goal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reactor tag
Does the sort attribute on the Reactory Jelly tag work? I added (sort=true) to the plugin.jelly for the dashboard report, but it didn't seem to do anything. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactor tag
I see the same thing on maven 1.0.2. Since you found it first, could you file a JIRA ;-)? -Dan On 6/17/05, Jon Strayer [EMAIL PROTECTED] wrote: Does the sort attribute on the Reactory Jelly tag work? I added (sort=true) to the plugin.jelly for the dashboard report, but it didn't seem to do anything. - 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: Remote repository version control
Hi Simon, maven encourges not to store binary artifact to version control system, but to be placed in your remote repository (make sure to back it up regularly). Let's maven manages the artifacts for you. If you insist on using artifacts in your VCS, look up maven.jar.override settings. So that you can ask maven to skip the remote lookup but only at your local propriety place. -D On 6/17/05, Guillaume Lederrey [EMAIL PROTECTED] wrote: On 6/17/05, Simon McClenahan [EMAIL PROTECTED] wrote: I am specifying a remote repository because the jar files I need are stored in my version control system, where I have checked them out into my local filesystem. I would have like to specify a relative path to the remote repository, but I don't think that's possible with a URL scheme. I have not attempted to setup a multiproject configuration in Maven yet, but what would be the best practice for version control of artifacts in a remote repository that is referenced locally? Maybe this is the complicated way of doing it. Should I be creating a remote repository to upload to on a shared resource (e.g. network drive) instead and not be concerned about version control? I would say that the cleanest way is to create a repository on a shared resource. If you really want to include your dependencies in your versionning tool, it probably makes sense only if they are included with your project. So in this case, put them in your project tree and copy them at the right place with a maven.xml goal. - 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]
How can I have the xdoclet generated files be included in the compile?
Hi, I am generating java files from xdoclet (into target/xdoclet/ejbdoclet), and I want these files to be included in the compilation along with the src directory. Do I have to copy them into the src dir? (which seems nasty) Or is there a better/right way to do this? Thanks for any info, Aidan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to invoke Ant tasks from Marmalade?
Hi, How can Ant tasks be invoked from Marmalade? I tried (e.g. ) ant:echo message=Hello, World. xmlns:ant=marmalade:ant/ but it did not work. Thanks for any hint, gunter zeilinger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I have the xdoclet generated files be included in the compile?
Hi i think that the maven.ejb.includes property of the maven ejb plugin is what you're looking for. Regards, On 6/17/05, Aidan Donohoe [EMAIL PROTECTED] wrote: Hi, I am generating java files from xdoclet (into target/xdoclet/ejbdoclet), and I want these files to be included in the compilation along with the src directory. Do I have to copy them into the src dir? (which seems nasty) Or is there a better/right way to do this? Thanks for any info, Aidan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Pascal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ejb clients
Can anybody give me a quick reference or example for generating a client for an EJB project? My project is doing just fine getting installed using the Maven 2.0 ejb:ejb goal. However, no client is being generated. Here's what I have now plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin I'm not quite sure what I'm supposed to put inside the generateClient element. I've tried just about everything. Thanks again. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ejb clients
You have the correct configuration, but we have a bug in ejb plugin release with m2 alpha-2. It's fixed in svn. Emmanuel Nathaniel Stoddard wrote: Can anybody give me a quick reference or example for generating a client for an EJB project? My project is doing just fine getting installed using the Maven 2.0 ejb:ejb goal. However, no client is being generated. Here's what I have now plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin I'm not quite sure what I'm supposed to put inside the generateClient element. I've tried just about everything. Thanks again. - 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: Compiling J2SE 5.0
You must configure the source and target paramters in your pom like this : ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build ... Emmanuel Nathaniel Stoddard wrote: Another newbie question for you guys (big thanks by the way!): How do I set up Maven so it will compile with a target and source of 1.5. I know how to do this in Ant, and I can see the properties for the compiler:compiler plugin, but I don't really understand where I should set them. I'm using Maven 2.0. - 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]
WARNING !!!!! - SCM plugin
Ohh shit There must be a major bug in the scm plugin, be carefull. As I used it and tried to checkout a project using the 'scm:checkout-project' goal it started to delete all files and directories where I was standing !!! I lost 2 projects before I got it stop running ;-( (I had the projects in CVS so I had lucky) Is there any one who knows how to make an JIRA-issue on this, How do I make one my self ? maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=mevenide-idea -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/proj ects/mevenide/scm -Dmaven.scm.checkout.dir=. BUILD FAILED File.. C:\Documents and Settings\mattiaso\.maven\cache\maven-scm-plugin-1.5\plugin.jelly Element... scm:checkout Line.. 110 Column 233 Directory . unable to be deleted. Total time : 3 seconds Finished at : den 17 juni 2005 22:54:51 CEST - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mavenizing my existing projects
OK, since I'm new to Maven (and Mevenide-Eclipse) here is what my setup is. I would appreciate help in Maven-izing this. Current state of affairs is in Eclipse I have the following Java (Eclipse) projects (renamed): Common Webapp Framework EJB App1 App2 App3 Etc. The Common project contains a lib and reference directory. The Common/lib contains 3rd party jars e.g. from Sun, Apache, etc., and Common/reference contains jars that I have built from the other projects like Framework, EJB, etc. This is all version controlled (with Subversion) so that when I create a branch I don't need to check out the source code for every project, just the Common project containing the jars for reference. Assuming there is one Eclipse project for one Maven artifact, how do I setup multiproject configuration? When I'm working in a branch, I don't necessarily have or need all of the projects in my workspace, just a select few. Can my project override whatever is in the remote repository? Assuming that my Common project is now obsoleted by Maven's remote repository, where do I reference the jars that I need while I'm in my IDE? The Help documentation for Mevenide says that it does not currently support Eclipse project dependencies. How do I do that by hand? Mevenide has an auto-build feature. Does that replace Eclipse's default internal build system as I edit and save source files that would normally trigger a compile? For the Eclipse project, do I specify Eclipse project dependencies, or configure the dependencies in project.xml and rely on Mevenide's auto-build feature? We have web applications that have customized JSP's, image files, application configuration, etc. for each of our many customers. The Web application jar itself is compiled from a single source, but to create a distribution or WAR file I need to specify the location of where to get these customized files. Does that imply that I need a custom project.properties file for each webapp to deploy? Or can they all be configured in the one file and I can specify on the maven command line which customer I am deploying for? Thanks in advance for any help. - Simon -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Friday, June 17, 2005 11:40 AM To: Maven Users List; Guillaume Lederrey Subject: Re: Remote repository version control Hi Simon, maven encourges not to store binary artifact to version control system, but to be placed in your remote repository (make sure to back it up regularly). Let's maven manages the artifacts for you. If you insist on using artifacts in your VCS, look up maven.jar.override settings. So that you can ask maven to skip the remote lookup but only at your local propriety place. -D On 6/17/05, Guillaume Lederrey [EMAIL PROTECTED] wrote: On 6/17/05, Simon McClenahan [EMAIL PROTECTED] wrote: I am specifying a remote repository because the jar files I need are stored in my version control system, where I have checked them out into my local filesystem. I would have like to specify a relative path to the remote repository, but I don't think that's possible with a URL scheme. I have not attempted to setup a multiproject configuration in Maven yet, but what would be the best practice for version control of artifacts in a remote repository that is referenced locally? Maybe this is the complicated way of doing it. Should I be creating a remote repository to upload to on a shared resource (e.g. network drive) instead and not be concerned about version control? I would say that the cleanest way is to create a repository on a shared resource. If you really want to include your dependencies in your versionning tool, it probably makes sense only if they are included with your project. So in this case, put them in your project tree and copy them at the right place with a maven.xml goal. -- NOTE: This message and any included attachments are from HealthCom Partners, LLC and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WARNING !!!!! - SCM plugin
Please don't cross post your message. You can open an issue here : http://jira.codehaus.org/browse/MPSCM Emmanuel mattias_kontakt wrote: Ohh shit There must be a major bug in the scm plugin, be carefull. As I used it and tried to checkout a project using the 'scm:checkout-project' goal it started to delete all files and directories where I was standing !!! I lost 2 projects before I got it stop running ;-( (I had the projects in CVS so I had lucky) Is there any one who knows how to make an JIRA-issue on this, How do I make one my self ? maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=mevenide-idea -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/proj ects/mevenide/scm -Dmaven.scm.checkout.dir=. BUILD FAILED File.. C:\Documents and Settings\mattiaso\.maven\cache\maven-scm-plugin-1.5\plugin.jelly Element... scm:checkout Line.. 110 Column 233 Directory . unable to be deleted. Total time : 3 seconds Finished at : den 17 juni 2005 22:54:51 CEST - 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 can I have the xdoclet generated files be included in the compile?
Aidan,
I guess you want something like this:
Suppose the generated source code location is referred to with '${gen.dir}'
( 'target/xdoclet/ejbdoclet' in your case )
then you can make sure they get compiled at the same time as your
manually typed java files do, by defining the following preGoal:
preGoal name=java:compile
path id=generated.java.compile.src.set location=${gen.dir}/
maven:addPath id=maven.compile.src.set refid=
generated.java.compile.src.set/
/preGoal
please note that it is stated in the documentation that including sources in
such a way
is discouraged. As you mention correctly, it is unwise to copy the generated
source files
into the 'official' source directory (src/main/java).
furthermore, as an eclipse fan I must add that by adding the property:
'maven.eclipse.classpath.include=${gen.dir}'
to your project and subsequently executing 'maven eclipse'
the generated source file are also included in the classpath of your eclipse
project.
a 'clean project' in eclipse could delete the generated sources
this can be prevented by adding the property: 'maven.gen.src=${gen.dir}'
Dennis
On 6/17/05, Pascal Thivent [EMAIL PROTECTED] wrote:
Hi
i think that the maven.ejb.includes property of the maven ejb plugin
is what you're looking for.
Regards,
On 6/17/05, Aidan Donohoe [EMAIL PROTECTED] wrote:
Hi,
I am generating java files from xdoclet (into target/xdoclet/ejbdoclet),
and I want these files to be included in the compilation along with the
src directory.
Do I have to copy them into the src dir? (which seems nasty)
Or is there a better/right way to do this?
Thanks for any info,
Aidan.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Pascal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How can I have the xdoclet generated files be included in the compile?
Problem solved. Now that I have ejbdoclet working, it looks like java:compile is automatically including the generated files. Thanks. -Original Message- From: Aidan Donohoe Sent: Friday, June 17, 2005 9:52 AM To: Maven Users List Subject: How can I have the xdoclet generated files be included in the compile? Hi, I am generating java files from xdoclet (into target/xdoclet/ejbdoclet), and I want these files to be included in the compilation along with the src directory. Do I have to copy them into the src dir? (which seems nasty) Or is there a better/right way to do this? Thanks for any info, Aidan. - 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]
How to split unit and acceptance tests apart (both use Junit framework)
Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to split unit and acceptance tests apart (both use Junit framework)
Guy, Move your integration/acception test to a separate maven project. Treat it like an application so that you can invoke it on demain. (ie all your test source goto src/main/java) You many need to write some goal wrapper to invoke the test. -D On 6/17/05, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Project relative dependencies
Brett, Thanks for the pointers, see below. On 5/29/05, Brett Porter [EMAIL PROTECTED] wrote: On 5/28/05, John Fallows [EMAIL PROTECTED] wrote: Perhaps we could also create a custom wagon implementation, similar to the FileWagon, but resolve the dependencies from a project-relative location? This is the recommended way. However the requests you will get will be in the repository layout, so you may need to map those paths. Wagon is not aware of any Maven specifics. How does one register such a custom wagon implementation with Maven2? For now - drop it into the lib directory. I have created a custom wagon implementation that seems to meet our current repository needs. It uses a custom protocol in the syntax, eg. custom://..., and the wagon uses custom as the role hint in the plexus component metadata. It can successfully deploy using the custom protocol, which is great! I was having difficulty in getting m2-a2 to recognize additional repository entries other than the default central one. I was also having difficulty overriding the central repository definition. Are these known issues targeted for m2-a3? So, as a workaround, I have been using a mirror of central in settings.xml instead. When I change the central repository mirror url to custom://... for dependency retrieval, I get an error: custom unrecognized protocol during dependency artifact resolution. This appears to be happening because the lightweight http wagon is still used for downloads, and it is trying to create a URL object with protocol custom. Of course, it fails because Java has no URLStreamHandler for the custom protocol. So, is it a bug that the custom wagon is not being used for dependency retrieval, or is some additional step required beyond dropping the custom wagon jar into the lib directory? Perhaps the http wagon is being used because the central repository url is http protocol, even though the mirror is custom protocol? Kind Regards, John Fallows. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Project relative dependencies
On 5/29/05, Brett Porter [EMAIL PROTECTED] wrote: On 5/28/05, John Fallows [EMAIL PROTECTED] wrote: I was having difficulty in getting m2-a2 to recognize additional repository entries other than the default central one. I was also having difficulty overriding the central repository definition. Are these known issues targeted for m2-a3? Recognising additional ones from the POM should work just fine - but it may be related to the other issue you've listed, where overriding doesn't work. That is in JIRA - if you could post additional details (what settings you added to the POM) we can look into that as well. When I change the central repository mirror url to custom://... for dependency retrieval, I get an error: custom unrecognized protocol during dependency artifact resolution. Ah, that's also a bug then. I can fix that relatively easily. I'll drop it into JIRA first though. Thanks, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compiling J2SE 5.0
You might also like to read: http://maven.apache.org/maven2/getting-started.html It has this specific example. - Brett On 6/18/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: You must configure the source and target paramters in your pom like this : ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build ... Emmanuel Nathaniel Stoddard wrote: Another newbie question for you guys (big thanks by the way!): How do I set up Maven so it will compile with a target and source of 1.5. I know how to do this in Ant, and I can see the properties for the compiler:compiler plugin, but I don't really understand where I should set them. I'm using Maven 2.0. - 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 1.1 and cutom properties in POM
You are right, these should be valid in 1.1. Please file an issue in JIRA. Thanks, Brett On 6/17/05, Schoenknecht,Andreas [EMAIL PROTECTED] wrote: Hello, I just tried the Maven 1.1 beta. Unfortunately I get errors when my POMs contains custom properties. Here is an example: At the end of the POM I have a properties section: ... /dependencies properties deputy isAssembly=false rules default value=LATEST RELEASE / enforcements enforcement groupIdtui-iris/groupId artifactIdtuiiris/artifactId version1.0.2/version /enforcement /enforcements deprecations / replacements / removals / /rules /deputy /properties /project As far as I understood it should be possible to have custom properties in the POM. But when I execute any Maven goal I get: org.codehaus.plexus.util.xml.pull.XmlPullParserException: TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...deputy isAssembly=false \r\nrules... @185:20) at org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1059) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:834) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:1621) at org.apache.maven.project.Project.init(Project.java:120) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:185) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:120) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:99) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:232) at org.apache.maven.MavenSession.initialize(MavenSession.java:172) at org.apache.maven.cli.App.doMain(App.java:498) Any ideas? Andreas Schnknecht - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to split unit and acceptance tests apart (both use Junit framework)
What is the reasoning for the extra main level? Why not src/java. Also, couldn't you just set the unitTestSourceDirectory to src/main/java and point sourceDirectory someplace empty? I am going to be going through this same process soon. Please share what you consider to be the best practice here (and why - it really helps to understand). On 6/17/05, dan tran [EMAIL PROTECTED] wrote: Guy, Move your integration/acception test to a separate maven project. Treat it like an application so that you can invoke it on demain. (ie all your test source goto src/main/java) You many need to write some goal wrapper to invoke the test. -D On 6/17/05, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - 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] -- Craig McDaniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remote repository version control
There is nothing saying you can't store the repository in VCS either, by the way - it just needs to be accessible over HTTP in Maven 1, and in the desired format. Maven's objection lies more with storing binary dependencies in your project's VCS as it results in duplicates and bigger checkout/updates. - Brett On 6/18/05, dan tran [EMAIL PROTECTED] wrote: Hi Simon, maven encourges not to store binary artifact to version control system, but to be placed in your remote repository (make sure to back it up regularly). Let's maven manages the artifacts for you. If you insist on using artifacts in your VCS, look up maven.jar.override settings. So that you can ask maven to skip the remote lookup but only at your local propriety place. -D On 6/17/05, Guillaume Lederrey [EMAIL PROTECTED] wrote: On 6/17/05, Simon McClenahan [EMAIL PROTECTED] wrote: I am specifying a remote repository because the jar files I need are stored in my version control system, where I have checked them out into my local filesystem. I would have like to specify a relative path to the remote repository, but I don't think that's possible with a URL scheme. I have not attempted to setup a multiproject configuration in Maven yet, but what would be the best practice for version control of artifacts in a remote repository that is referenced locally? Maybe this is the complicated way of doing it. Should I be creating a remote repository to upload to on a shared resource (e.g. network drive) instead and not be concerned about version control? I would say that the cleanest way is to create a repository on a shared resource. If you really want to include your dependencies in your versionning tool, it probably makes sense only if they are included with your project. So in this case, put them in your project tree and copy them at the right place with a maven.xml goal. - 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: How to split unit and acceptance tests apart (both use Junit framework)
src/main/java is the maven recommend directory structure. This way I can so have src/main/resources, both indicating they are belonging to the main artifact. It is more organized that way unitTestSourceDirectory can only understand by maven-test-plugin the real unit test. So if you point it to your main src, your tests will be automatically invoked after compilation. and you dont want that. Last, if you put your integration test cases as the main artifact, then you can use test:single in maven-test-plugin to invoke your integration. Be prepare to dig into maven-test-plugin to understand test:single requirement. (hmm, perhaps we should start thinking about maven-integration-junit-plugin ;-) -Dan On 6/17/05, Craig McDaniel [EMAIL PROTECTED] wrote: What is the reasoning for the extra main level? Why not src/java. Also, couldn't you just set the unitTestSourceDirectory to src/main/java and point sourceDirectory someplace empty? I am going to be going through this same process soon. Please share what you consider to be the best practice here (and why - it really helps to understand). On 6/17/05, dan tran [EMAIL PROTECTED] wrote: Guy, Move your integration/acception test to a separate maven project. Treat it like an application so that you can invoke it on demain. (ie all your test source goto src/main/java) You many need to write some goal wrapper to invoke the test. -D On 6/17/05, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - 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] -- Craig McDaniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to split unit and acceptance tests apart (both use Junit framework)
I actually did create such a plugin because I wanted my integration tests as part of the same project as the code it was testing. I also didn't want my integration test project to be included by the multiproject (and didn't want to hard-code an exclude for it, either). This sort of thing comes up a lot, and I think it's a vaild scenario. I didn't want to have to create a whole new plugin to run the other set of tests, but was forced to because the test plugin doesn't allow for overriding the test source directory--it pulls it directly from the pom, no questions asked. It would be better if the test plugin used a property for the test source dir, which defaulted to the directory mentioned in the pom; then a goal could override it. ..David.. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Fri 6/17/2005 9:06 PM To: Maven Users List Subject: Re: How to split unit and acceptance tests apart (both use Junit framework) src/main/java is the maven recommend directory structure. This way I can so have src/main/resources, both indicating they are belonging to the main artifact. It is more organized that way unitTestSourceDirectory can only understand by maven-test-plugin the real unit test. So if you point it to your main src, your tests will be automatically invoked after compilation. and you dont want that. Last, if you put your integration test cases as the main artifact, then you can use test:single in maven-test-plugin to invoke your integration. Be prepare to dig into maven-test-plugin to understand test:single requirement. (hmm, perhaps we should start thinking about maven-integration-junit-plugin ;-) -Dan On 6/17/05, Craig McDaniel [EMAIL PROTECTED] wrote: What is the reasoning for the extra main level? Why not src/java. Also, couldn't you just set the unitTestSourceDirectory to src/main/java and point sourceDirectory someplace empty? I am going to be going through this same process soon. Please share what you consider to be the best practice here (and why - it really helps to understand). On 6/17/05, dan tran [EMAIL PROTECTED] wrote: Guy, Move your integration/acception test to a separate maven project. Treat it like an application so that you can invoke it on demain. (ie all your test source goto src/main/java) You many need to write some goal wrapper to invoke the test. -D On 6/17/05, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - 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] -- Craig McDaniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to split unit and acceptance tests apart (both use Junit framework)
correct, in order to get test:single to work with integration as the main artifact one needs to fool test:single that it has test to run (that is why I say prepare to dig into test:single source to understand its requirements ) perhaps you can submit your plugin into plugin's sandbox so we can use it? -D On 6/17/05, David Jackman [EMAIL PROTECTED] wrote: I actually did create such a plugin because I wanted my integration tests as part of the same project as the code it was testing. I also didn't want my integration test project to be included by the multiproject (and didn't want to hard-code an exclude for it, either). This sort of thing comes up a lot, and I think it's a vaild scenario. I didn't want to have to create a whole new plugin to run the other set of tests, but was forced to because the test plugin doesn't allow for overriding the test source directory--it pulls it directly from the pom, no questions asked. It would be better if the test plugin used a property for the test source dir, which defaulted to the directory mentioned in the pom; then a goal could override it. ..David.. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Fri 6/17/2005 9:06 PM To: Maven Users List Subject: Re: How to split unit and acceptance tests apart (both use Junit framework) src/main/java is the maven recommend directory structure. This way I can so have src/main/resources, both indicating they are belonging to the main artifact. It is more organized that way unitTestSourceDirectory can only understand by maven-test-plugin the real unit test. So if you point it to your main src, your tests will be automatically invoked after compilation. and you dont want that. Last, if you put your integration test cases as the main artifact, then you can use test:single in maven-test-plugin to invoke your integration. Be prepare to dig into maven-test-plugin to understand test:single requirement. (hmm, perhaps we should start thinking about maven-integration-junit-plugin ;-) -Dan On 6/17/05, Craig McDaniel [EMAIL PROTECTED] wrote: What is the reasoning for the extra main level? Why not src/java. Also, couldn't you just set the unitTestSourceDirectory to src/main/java and point sourceDirectory someplace empty? I am going to be going through this same process soon. Please share what you consider to be the best practice here (and why - it really helps to understand). On 6/17/05, dan tran [EMAIL PROTECTED] wrote: Guy, Move your integration/acception test to a separate maven project. Treat it like an application so that you can invoke it on demain. (ie all your test source goto src/main/java) You many need to write some goal wrapper to invoke the test. -D On 6/17/05, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm currently using Maven 1 for running our regular unit tests. However I'm in the process of adding larger acceptance/integration tests that cover wide areas of functionality. I am still using the JUnit framework for these acceptance tests, but I was wondering if there was a way to separate out these two test types. The reason being is the time involved. The standard unit tests run in no more than a couple of minutes. However the new acceptance tests require nearly an hour. Ideally, running these acceptance tests would be a different goal (target). I'm hoping to configure CruiseControl to run our unit tests on each build, but only acceptance tests on builds greater than 3 or 4 hours apart. Is this possible with Maven? Perhaps with version 2? Or does this require a custom plugin (based on the current unit test plugin)? Thanks much, Guy - 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] -- Craig McDaniel - 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]
