RE: Style of generated site
Hi Gilles,
Gilles Dodinet wrote on Wednesday, January 14, 2004 6:58 PM:
Jorg,
there is three css used (site.jsl), if im not wrong :
o maven-base.css (always)
o theme - property maven.xdoc.theme.url,
defaults to ${relativePath}/style/maven-theme.css
o ${maven.docs.src}/style/project.css
Ah, well, thnx, this enlightens me much. At least this is currently not documented:
http://maven.apache.org/reference/plugins/xdoc/properties.html
and building the docs from the CVS version fails because of
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPTASKLIST-6
and therefore I requested for
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=13551
:)
Regards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: javadoc plugin - multiple package tags
On a related note, is there any plan to support multiple package tags in
the POM? I know that the Maven way revolves around building one package, but
I want to build a site that documents a number of related packages in one
place. Currently I can only specify one package tag so my javadoc plug-in
only generates javadoc for that one package.
Any suggestions?
Jason
-Original Message-
From: Jake Ewerdt [mailto:[EMAIL PROTECTED]
Sent: 14 January 2004 15:01
To: Maven Users List
Subject: Re: javadoc plugin
Yeah, same thing happened to me. I modified the javadoc's plugin.jelly to
get it working. Here's the diff:
93,94c93
packagenames=${pom.package}
sourcepath=${pom.build.sourceDirectory}
---
packagenames=${pom.package}.*
109a108,124
ant:fileset dir=${pom.build.sourceDirectory}
ant:include name=**/*.java/
!-- FIXME: This is a bad cut and paste --
!-- handle source modifications --
j:forEach var=sm items=${pom.build.sourceModifications}
ant:available property=classPresent
classname=${sm.className}/
j:if test=${classPresent != 'true'}
j:forEach var=exclude items=${sm.excludes}
ant:exclude name=${exclude}/
/j:forEach
j:forEach var=include items=${sm.includes}
ant:include name=${include}/
/j:forEach
/j:if
/j:forEach
/ant:fileset
and then in your project.xml file, put a line like:
packagejava.util,java.lang,javax.xml.parsers/package
I'm using JDK 1.3.1 and Maven 1.0-rc1
-jake
On Wednesday 14 January 2004 07:25 am, Ebersole, Steven wrote:
whenever I run the maven javadoc plugin, it does not generate any package
information (package-list is blank and package-summary is missing). Any
ideas what I am missing?
-
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 and EJB Testing
Done. See http://jakarta.apache.org/cactus/integration/maven/ Thanks -Vincent -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rob Moore Sent: 13 January 2004 08:19 To: [EMAIL PROTECTED] Subject: Re: Maven and EJB Testing I noticed you made a lot of changes in December to assist with testing EJBs. Any chance you might provide the updated plug-in jar on the site? Thanks, Rob Vincent Massol wrote: Hi Tim, One solution is by using the Cactus plugin for Maven. -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]
Generating md5 checksums
Are there any details available on goals/properties necessary for generating md5 checksums for distributions and jars produced by maven? Thanks, -Mark -- 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: Generating md5 checksums
Simply use the artifact tags : http://maven.apache.org/reference/plugins/artifact/ -emmanuel Selon Mark R. Diggory [EMAIL PROTECTED]: Are there any details available on goals/properties necessary for generating md5 checksums for distributions and jars produced by maven? Thanks, -Mark -- 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: single artifact mantra and ejb projects
Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 6:41 PM To: [EMAIL PROTECTED] Subject: Re: single artifact mantra and ejb projects Hi, Ryan, I just reviewed your wiki posting pretty extensively and found it to be a great help. However, I've had a problem with the part about running 'maven multiproject:install' in the root project. I get this error: Starting the reactor... BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 IO error scanning directory c:\WUTemp\myproject\root\..\ Total time: 3 seconds Finished at: Wed Jan 14 18:37:35 CST 2004 Have you seen this kind of thing before? Also, I was curious about your statement regarding Eclipse compatibility. Can you offer a bit more on what happens within Eclipse if the more 'traditional' approach is taken? I find the root project difficult to swallow -- but will accept it if I must. :^) Thanks, Rob Sonnek, Ryan wrote: I just finished added an entry to the wiki about how I have structured my EJB project. I would be very interested in hearing some feedback if it is on target with what other developers are doing. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan - 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]
Using an older xerces
I've got some code that sadly requires an old version of xerces, 1.4.4. The dependency in my project is dependency groupIdxerces/groupId artifactIdxerces/artifactId version1.4.4/version urlhttp://xml.apache.org/xerces-j//url /dependency However, compilation never succeeds under Maven. I'm getting undefined symbols, as if it's picking up a newer xerces (perhaps the one in $MAVEN_HOME/lib/endorsed/xerces-2.4.0.jar). With debug output on, I can cut-and-paste the generated compile command onto a javac command line and it works fine. What's the secret to getting this to work under Maven? (Or maybe it's at last time to upgrade this old code?) --Sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
Hello Ryan, thanks for writing this documentation. I just set up such an environment following your description. One question: If I start maven I will always get an exception: = snip org.apache.maven.verifier.UnsatisfiedDependencyException: The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar (no download url specified) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:219) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:135) at org.apache.maven.project.Project.verifyDependencies(Project.java:1384) at org.apache.maven.plugin.JellyPlugin.load(JellyPlugin.java:190) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:324) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:311) at org.apache.maven.plugin.PluginManager.processPluginFile(PluginManager.java:227) at org.apache.maven.plugin.PluginManager.expandPluginJars(PluginManager.java:209) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:297) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:242) at org.apache.maven.MavenSession.initialize(MavenSession.java:209) at org.apache.maven.cli.App.doMain(App.java:481) at org.apache.maven.cli.App.main(App.java:1145) 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) = snap Did you modify locally your xdoclet-plugin? It seems to express its dependency with the id-tag and cannot find the xjavadoc-1.0.2 on ibiblio (although it is there ...). I also added this artifact in my root project.xml (like you did), but it does not help here. Any hint? Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
The problem you are havins is due to the xdoclet plugin looking for the xjavadoc artifact in the xjavadoc groupId (which doesn't exist on ibiblio). I've filed a upload request to have xjavadoc moved into it's own groupId, but it hasn't been done yet. That being said, there's more wrong with the xdoclet plugin than just the xjavadoc dependency.. I originally the wiki documentation with the intent of using the xdoclet-maven-plugin. After several failed attempts to get it up and working, I reverted to my existing build using only the xdoclet ant tags within maven.xml. I don't know if this is the correct direction, but IMO the xdoclet-maven-plugin is absolutely atrocious. I would rather have the maintenance of my maven.xml script over trying to use the xdoclet plugin. I would check out the latest changes I made on the wiki, and uninstall the xdoclet plugin (just delete it), and try building again. I didn't have any problems getting the listed documentation up and running. Let me know if you have any other problems. Ryan -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 10:44 AM To: Maven Users List Subject: RE: single artifact mantra and ejb projects Hello Ryan, thanks for writing this documentation. I just set up such an environment following your description. One question: If I start maven I will always get an exception: = snip org.apache.maven.verifier.UnsatisfiedDependencyException: The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar (no download url specified) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyV erifier.java:219) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java: 135) at org.apache.maven.project.Project.verifyDependencies(Project.java:1384) at org.apache.maven.plugin.JellyPlugin.load(JellyPlugin.java:190) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:324) at org.apache.maven.plugin.PluginManager.loadPlugin(PluginManager.java:311) at org.apache.maven.plugin.PluginManager.processPluginFile(PluginManager.java:2 27) at org.apache.maven.plugin.PluginManager.expandPluginJars(PluginManager.java:20 9) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:297) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:242) at org.apache.maven.MavenSession.initialize(MavenSession.java:209) at org.apache.maven.cli.App.doMain(App.java:481) at org.apache.maven.cli.App.main(App.java:1145) 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) = snap Did you modify locally your xdoclet-plugin? It seems to express its dependency with the id-tag and cannot find the xjavadoc-1.0.2 on ibiblio (although it is there ...). I also added this artifact in my root project.xml (like you did), but it does not help here. Any hint? Regards, Jörg - 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: single artifact mantra and ejb projects
You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Feel free to ask any other questions, or if you think there is a better way, I'd love to hear it! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:02 AM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - 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: single artifact mantra and ejb projects
A little investigation into the wiki has shown me the light... I was able to upload a sample project in a ZIP format. -Original Message- From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:38 AM To: 'Maven Users List' Subject: RE: single artifact mantra and ejb projects You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Feel free to ask any other questions, or if you think there is a better way, I'd love to hear it! Ryan -Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:02 AM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Ryan, First off all, many thanks for your continued work on the wiki entry. Here are some questions/points: 1. Might I suggest that you add a jar/zip file containing the example code? 2. What is the eclipse.dependency declaration do in the ejb project.xml? It seems odd to see it in the ejb project.xml. I guess I'd assume it would be in the ejb-client project.xml if it depends on the ejb project. 3. I noticed that you are referencing version 1.2b4 of the xdoclet-jboss-module. Is there a reason you are using that version and not 1.2 (as you do everywhere else)? dependency groupIdxdoclet/groupId artifactIdxdoclet-jboss-module/artifactId version1.2b4/version urlhttp://xdoclet.sourceforge.net/url /dependency 4. I just created the project using the changes you posted and I get the following error: BUILD FAILED File.. file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/ Element... maven:reactor Line.. 174 Column 9 Unable to obtain goal [multiproject:install-callback] -- file:/C:/Documents and Settings/Rob/.maven/plugins/maven-multiproject-plugin-1.1/:210:61: attainGoal No goal [jar :install] Total time: 12 seconds Finished at: Thu Jan 15 10:54:45 CST 2004 Notice the space between 'jar' and ':install' on the attainGoal line. Also, I have a project of my own built using the guidelines you put forward and I see something similar when I try to run maven multiproject:install in my root project, except the line is 'No goal [ejb: install]'. Rob Sonnek, Ryan wrote: Thanks for the response Rob. I went through the documentation I had posted and updated a couple things (eclipse explanation, changing common to ejb-client, some of the maven script). I had the same problem as you, and I fixed it by making sure that all of my property files didn't have an extra space at the end of each line. That will throw off pretty much everything. If you could try again (maybe grab the updated files off the wiki), and let me know if you have any other problems. Thanks! Ryan - 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]
Xerces-2.6
Hello Is there any particular reason the ibiblio archives have not been updated to include later versions of xerces (2.5.0, 2.6.0)? Bruce Chenoweth Sr SW Engineer 4100 Hamline Av N St.Paul MN 55112-5798 Phone: (651) 582-7801 Fax:(651) 582-5300 [EMAIL PROTECTED] www.guidant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Regarding the xdoclet plugin. I hacked it myself to fix the issue. All you need to change is the last dependency in the project.xml so that it has this: dependency groupIdxdoclet/groupId artifactIdxjavadoc/artifactId version1.0.2/version urlhttp://xdoclet.sourceforge.net/url /dependency I've attached my hacked version of the original plugin. Hopefully it will make it through. Rob Sonnek, Ryan wrote: The problem you are havins is due to the xdoclet plugin looking for the xjavadoc artifact in the xjavadoc groupId (which doesn't exist on ibiblio). I've filed a upload request to have xjavadoc moved into it's own groupId, but it hasn't been done yet. That being said, there's more wrong with the xdoclet plugin than just the xjavadoc dependency.. maven-xdoclet-plugin-1.2.jar Description: application/java-archive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Sonnek, Ryan wrote: You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). D'oh! I forgot about checking the maven.multiproject.type line for a trailing space. Sorry about that... The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. Ah, yes. I set up my own repository just for that reason. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. Down at the very bottom of the page is an action called Attach File. Easy to miss. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Okay, so the Java files that are used by the EJB project are really in the client project. In other words, these 'shared' files don't live in the parent project at all. Is that correct? Thanks again, Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: single artifact mantra and ejb projects
Sonnek, Ryan wrote: A little investigation into the wiki has shown me the light... I was able to upload a sample project in a ZIP format. Cool! Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: single artifact mantra and ejb projects
-Original Message- From: Rob Moore [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 12:29 PM To: Maven Users List Subject: Re: single artifact mantra and ejb projects Sonnek, Ryan wrote: You have to make sure all the properties files contain no extra space after the value. Clear those out and you won't have a problem (ie: change maven.multiproject.type=jar_ to maven.multiproject.type=jar). D'oh! I forgot about checking the maven.multiproject.type line for a trailing space. Sorry about that... The jboss plugin is version 1.2b4 because the final 1.2 module is not on ibiblio. I've put in a JIRA request for it to be uploaded, but it hasn't been done yet. I don't know if there was a reason it was not put on ibiblio, or if it was just accidentally overlooked. Ah, yes. I set up my own repository just for that reason. If I knew how to attach a zip file of the sample to the wiki I certainly would! I have never done that before, so if there's a way, let me know and I'll put it up there. Down at the very bottom of the page is an action called Attach File. Easy to miss. The eclipse dependency is used to map the EJB classes to their interfaces. In my example, I package the EJB interfaces and Data Objects (or value objects), into the ejb-client. IMO, this is the easiest way for 3rd party apps to gain access to your application. They only need this one jar file and they're good to go. Because the data objects are in the ejb-client subproject, and the data objects are used within the signatures of the ejb java code, there is a dependency between the two. You'll notice that in the ejb's maven.xml, I intentionally delete the interfaces and data objects after they are generated to avoid duplicate classes existing. Okay, so the Java files that are used by the EJB project are really in the client project. In other words, these 'shared' files don't live in the parent project at all. Is that correct? Right on. I wouldn't really call the EJB project the parent, but yes, the interfaces and data classes ONLY exist in the ejb-client project. Thanks again, Rob - 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: Multiple remote repsitories + proxy settings
Hi Gilles Works perfectly, that is exactly what I wanted to setup. Merci ;) Eric. -Original Message- From: Gilles Dodinet [mailto:[EMAIL PROTECTED] Sent: January 13, 2004 7:49 PM To: Maven Users List Subject: Re: Multiple remote repsitories + proxy settings Eric, you might want to look at MavenProxy. Ive never used it but it seems you can specify proxy policies per repository. http://wiki.codehaus.org/maven/MavenProxy -- gd Eric Giguere wrote: Hi all A quick one. We're behind a firewall and use a proxy server to go on the Net. And we have a remote repository for jars that is on our internal network. Lets say I want to still use the one at ibiblio.org as a fallback repository. I know how to configure multiple remote repositories but, is it possible to specify proxy settings for lets say only the second remote repository in the list? I ask because if I set proxy settings, I can access the default repository, but not our local one. If I don't set proxy properties, then its the fallback (ibiblio.org) that becomes innaccessible because of our proxy server. Is there a work around? thx for any help - 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: Using an older xerces
Sean Kelly wrote: I've got some code that sadly requires an old version of xerces, 1.4.4. The dependency in my project is dependency groupIdxerces/groupId artifactIdxerces/artifactId version1.4.4/version urlhttp://xml.apache.org/xerces-j//url /dependency However, compilation never succeeds under Maven. I'm getting undefined symbols, as if it's picking up a newer xerces (perhaps the one in $MAVEN_HOME/lib/endorsed/xerces-2.4.0.jar). With debug output on, I can cut-and-paste the generated compile command onto a javac command line and it works fine. Probably you met unresolved classloader issues. I had similiar problem with maven-beta10, but the bug (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-71) is still not closed, so it seems the bug is still in effect. I'am afraid it is time to upgrade, if you want to use maven to compile your project. -- Norbert Pabi Nobody expects the Debian Inquisition! Our two weapons are fear and surprise... and ruthless efficiency! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Build of severals subprojects
Example : I have two 2 subprojects mavenproject/subproject1 mavenproject/subproject2 subproject1 is a framework subproject2 is an EJB subproject2 uses classes from subproject1 (the EJB uses utility classes) subproject1 uses classes from subproject2 (using interfaces when call EJB) The build of subproject1 failed = ok because classes of subproject2 are needed. The build of subproject2 failed = ok because classes of subproject1 are needed. What's the maven logic to resolve this problem ? what's the best way ? Must I compile all classes in a third project and put it in repository to make subproject1 subproject2 with a dependancy ? Thanks --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build of severals subprojects
I would recommend breaking your ejb interfaces into a separate project (something like an ejb-client project). I've got an example up on the maven wiki if you want an example. Feel free to comment if this setup works for you or if you see any possible improvements. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan -Original Message- From: Jyl [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 2:15 PM To: [EMAIL PROTECTED] Subject: Build of severals subprojects Example : I have two 2 subprojects mavenproject/subproject1 mavenproject/subproject2 subproject1 is a framework subproject2 is an EJB subproject2 uses classes from subproject1 (the EJB uses utility classes) subproject1 uses classes from subproject2 (using interfaces when call EJB) The build of subproject1 failed = ok because classes of subproject2 are needed. The build of subproject2 failed = ok because classes of subproject1 are needed. What's the maven logic to resolve this problem ? what's the best way ? Must I compile all classes in a third project and put it in repository to make subproject1 subproject2 with a dependancy ? Thanks --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004 - 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]
Release plugin question
I've added an echo message to the release plugin like so:
| goal name=release:build-distribution-src
prereqs=release:init,scm:checkout-project
ant:echo
message=dir=${maven.scm.checkout.dir}/${maven.scm.cvs.module}/
archive:gzip name=${releaseNameSrc}
dir=${maven.scm.checkout.dir}/${maven.scm.cvs.module}/
archive:zip name=${releaseNameSrc}
dir=${maven.scm.checkout.dir}/${maven.scm.cvs.module}/
/goal|
And determined that the dir property ends up looking like this ' / '.
So it tries to zip up my root directory (thankfullly it fails).
I have the SCM properties in my project set. They look like this:
| repository
connectionscm:cvs:pserver:[EMAIL PROTECTED]:/usr/local/cvs/wrycanCode:wrycan/core/connection
/repository
|Any ideas on what I might be doing wrong would be appreciated. I'm
using bootstrap builds about a week old for my maven and release plugin
code base.
Christopher Farnham
Senior Consultant at Wrycan, Inc.
[EMAIL PROTECTED]
http://www.wrycan.com
Jason van Zyl wrote:
On Fri, 2004-01-09 at 20:18, Incze Lajos wrote:
In the long run and in the new Maven code I won't be promoting Jelly for
plugins at all, but will be promoting the use of beanshell. I'm sure XML
programming will remain wildly popular and if that is the case I will be
reimplementing Jelly taking it down to the bare metal with xpp3 and
using OGNL for expressions. I am no longer a fan of Jelly. I know people
seem to love XML programming but I think it's the single biggest mistake
I've made with Maven and it has cost us all dearly. I won't be making
any similiar mistakes in the future.
I would consider using groovy in the long run.
Possibly, in the very long run. I'm aware of Groovy.
It is a real scripting
language has all the structures (designed in) that were important in
jelly scripting (ant builder, xml builder, can emit xml sax events, etc.)
has excellent structures which could be important in workflows (closures
are, in fact, 1st class object code snippets that could be called on
worflow stages), can be interpreted AND compiled to bytecode, the same
way easy bean integration as in the jelly scripting, etc. And last but
not least: the syntax is not XML, but real programming language with
pretty good collection interfaces (which seems to be one of the most
important factors in project builders). Seemingly, the current codebase
can be 'mechanically' transported from jelly to groovy.
It's all good on paper, but beanshell 2.0 in my mind is the option I'm
leaning toward right now simply because it's gone though an iteration or
two. But who knows in time. At this point in time I'm not jumping in
head first into Groovy.
incze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build of severals subprojects
I would recommend decoupling the utility classes used by both subproject1 and subproject2 into a separate subproject (subprojectutil?). Then, you'd have the dependency chain of subproject1 DEPENDS ON subprojectutil + subproject2, subproject2 DEPENDS ON subprojectutil. Matt John Casey wrote: IMO, that's not really going to help anything. It seems that the subprojects here constitute a cyclic dependency issue. In this case, it's not possible to compile one subproject without compiling the other at the same time. Why are these separated in the first place? If there isn't a good reason, then I'd put them in the same project and compile them together... my 2 cents. -john On Thu, 2004-01-15 at 15:51, Sonnek, Ryan wrote: I would recommend breaking your ejb interfaces into a separate project (something like an ejb-client project). I've got an example up on the maven wiki if you want an example. Feel free to comment if this setup works for you or if you see any possible improvements. http://wiki.codehaus.org/maven/CreatingEjbApplications Ryan -Original Message- From: Jyl [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 2:15 PM To: [EMAIL PROTECTED] Subject: Build of severals subprojects Example : I have two 2 subprojects mavenproject/subproject1 mavenproject/subproject2 subproject1 is a framework subproject2 is an EJB subproject2 uses classes from subproject1 (the EJB uses utility classes) subproject1 uses classes from subproject2 (using interfaces when call EJB) The build of subproject1 failed = ok because classes of subproject2 are needed. The build of subproject2 failed = ok because classes of subproject1 are needed. What's the maven logic to resolve this problem ? what's the best way ? Must I compile all classes in a third project and put it in repository to make subproject1 subproject2 with a dependancy ? Thanks --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004 - 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]
Constructing Dates on the Fly?
Folks-- I need to rename my war file to meet some hosting / production /process requirement. Changing the name is no problem. However, I'd like to be able to insert a date in the middle of it so I can do something like: project-date-lifecycle.war Is there an obvious way to get a date (and format it) using jelly or some other thing in maven.xml? Perusing the jelly core tags, I suppose I could instantiate a jave.util.Date object, then a simple date formatter object, but that seems like a lot of work. Alternately, I could manually change the currentVersion/ element in project.xml, or use some other property I manually set (using -D for instance), but, well, it would be ever so much nicer if there was something like: j:setDate var=mydate when=current format=-MM-dd/ Do I dare hope? Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Constructing Dates on the Fly?
You might like to try war:install/deploy-snapshot which does this automatically with a UTC timestamp on the end as the version. To get a date yourself, are you sure there isn't a jelly taglib for that? I thought there was a fmt:/ or something, after all it is mimicing a lot of JSTL. You could also use an appropriate ant tag (although its been so long I've forgotten what its called - tstamp/ I think). Cheers, Brett -Original Message- From: Keith Irwin [mailto:[EMAIL PROTECTED] Sent: Friday, 16 January 2004 10:21 AM To: Maven Users List Subject: Constructing Dates on the Fly? Folks-- I need to rename my war file to meet some hosting / production /process requirement. Changing the name is no problem. However, I'd like to be able to insert a date in the middle of it so I can do something like: project-date-lifecycle.war Is there an obvious way to get a date (and format it) using jelly or some other thing in maven.xml? Perusing the jelly core tags, I suppose I could instantiate a jave.util.Date object, then a simple date formatter object, but that seems like a lot of work. Alternately, I could manually change the currentVersion/ element in project.xml, or use some other property I manually set (using -D for instance), but, well, it would be ever so much nicer if there was something like: j:setDate var=mydate when=current format=-MM-dd/ Do I dare hope? Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Constructing Dates on the Fly?
Ah hah!
I knew if I wrote to the list it would speed my discovery. This seems
to work:
goal name=productionWar
ant:tstamp
ant:format property=DSTAMP pattern=-MM-dd/
/ant:tstamp
j:set var=${maven.war.final.name} value=yo-${DSTAMP}-yo.war/
/goal
Easy!
:)
Keith
On Thu, 2004-01-15 at 15:21, Keith Irwin wrote:
Folks--
I need to rename my war file to meet some hosting / production /process
requirement.
Changing the name is no problem.
However, I'd like to be able to insert a date in the middle of it so I
can do something like:
project-date-lifecycle.war
Is there an obvious way to get a date (and format it) using jelly or
some other thing in maven.xml?
Perusing the jelly core tags, I suppose I could instantiate a
jave.util.Date object, then a simple date formatter object, but that
seems like a lot of work.
Alternately, I could manually change the currentVersion/ element in
project.xml, or use some other property I manually set (using -D for
instance), but, well, it would be ever so much nicer if there was
something like:
j:setDate var=mydate when=current format=-MM-dd/
Do I dare hope?
Keith
-
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: Constructing Dates on the Fly?
On Thu, 2004-01-15 at 15:35, Brett Porter wrote: You might like to try war:install/deploy-snapshot which does this automatically with a UTC timestamp on the end as the version. To get a date yourself, are you sure there isn't a jelly taglib for that? I thought there was a fmt:/ or something, after all it is mimicing a lot of JSTL. Yeah, I was looking at that. It would be great, but you know, they never have any examples in their docs, so I have to go scraping through plugins hoping to find something, which is how I found: You could also use an appropriate ant tag (although its been so long I've forgotten what its called - tstamp/ I think). Exactly. Worked like a dream. ;) See my reply to my reply. The production guys want three builds for three environments so I now have a goal that does them all at once. Keith Cheers, Brett -Original Message- From: Keith Irwin [mailto:[EMAIL PROTECTED] Sent: Friday, 16 January 2004 10:21 AM To: Maven Users List Subject: Constructing Dates on the Fly? Folks-- I need to rename my war file to meet some hosting / production /process requirement. Changing the name is no problem. However, I'd like to be able to insert a date in the middle of it so I can do something like: project-date-lifecycle.war Is there an obvious way to get a date (and format it) using jelly or some other thing in maven.xml? Perusing the jelly core tags, I suppose I could instantiate a jave.util.Date object, then a simple date formatter object, but that seems like a lot of work. Alternately, I could manually change the currentVersion/ element in project.xml, or use some other property I manually set (using -D for instance), but, well, it would be ever so much nicer if there was something like: j:setDate var=mydate when=current format=-MM-dd/ Do I dare hope? Keith - 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: Xerces-2.6
Noone's requested it. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Chenoweth, Bruce (STP) [EMAIL PROTECTED] wrote on 16/01/2004 05:11:01 AM: Hello Is there any particular reason the ibiblio archives have not been updated to include later versions of xerces (2.5.0, 2.6.0)? Bruce Chenoweth Sr SW Engineer 4100 Hamline Av N St.Paul MN 55112-5798 Phone: (651) 582-7801 Fax:(651) 582-5300 [EMAIL PROTECTED] www.guidant.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]
Newbie questions
Hi, I am a newbie to Maven, and also to a lot of its ancestors. But I want to use maven to create a website for my java project. I installed maven and edited project.xml. Here are a few queries I have... I could not find answers to these. If they have been previously discussed, please do not bash me, if its possible, please direct me to the answers. 1. How do I change the default look and feel of the project website? Do I have to edit any css etc? Do I need to use any plugins? 2. project.xml has a description element. This is displayed on the project main page. Can I have multiple sections in this? What tags can be added inside the text for this, that goes into project.xml? Is there some other file that can list all this the way I want it? 3. Can I change the menus on the left hand side? I saw a few maven-powered websites but don't know how to do it. Thanks and Regards, Mamata - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie questions
On Thu, 2004-01-15 at 20:37, Mamata Desai wrote: Hi, I am a newbie to Maven, and also to a lot of its ancestors. But I want to use maven to create a website for my java project. I installed maven and edited project.xml. Here are a few queries I have... I could not find answers to these. If they have been previously discussed, please do not bash me, if its possible, please direct me to the answers. 1. How do I change the default look and feel of the project website? Do I have to edit any css etc? Do I need to use any plugins? If you use the version of the xdoc plugin that came with the last release then you can change simple things like colour with properties. Changing the layout is more tedious. If you use the version of the plugin that is currently in CVS then it's all done by editing the CSS files which were intentionally revamped to be simple. 2. project.xml has a description element. This is displayed on the project main page. Can I have multiple sections in this? What tags can be added inside the text for this, that goes into project.xml? Is there some other file that can list all this the way I want it? The description is only used to generate a default index page when an index.xml isn't provided by you. If you want a decent home page for your site then you should make an index.xml file. You can look at Maven's own index.xml for an example: http://cvs.apache.org/viewcvs.cgi/maven/xdocs/index.xml?rev=1.11view=auto 3. Can I change the menus on the left hand side? I saw a few maven-powered websites but don't know how to do it. Using the navigation.xml file, again you can look at Maven's own navigation.xml: http://cvs.apache.org/viewcvs.cgi/maven/xdocs/navigation.xml?rev=1.37view=auto Thanks and Regards, Mamata - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jars/classes not visible to ant tasks
I'm trying to use ant:script task to execute jacl script in order to setup websphere resources. This ant:script task does not accept nested ant:classpath specification. I've specified the necessary jars (bsf.jar, tcljava.jar, jacl.jar) as dependencies but looks like they are not visible to ant:script task. I've also tried to specify different classloaders (root, root.maven) for the dependencies but with no success. Here is the snippet of what I'm trying to do: goal name=websphere:init description=Init websphere script language=jacl ![CDATA[ package require java puts Hello World! ]] /script /goal I'm getting the following output (script is not processed): script language=jaclpackage require java puts Hello World!/script If I drop the bsf.jar, tcljava.jar and jacl.jar into jre extension directory then I get the correct output: Hello World! Does anybody know how to solve this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
