Re: uhmm... installation?
Dear Elias, Elias Sinderson <[EMAIL PROTECTED]> wrote on 17/09/2003 02:34:36 AM: > Dear Maven Community, > [snip] > I'm attempting to set up maven for the first time. I visited the web > page, where I was able to download the latest distribution > (1.0-beta-10) without difficulty. I untarred the file, set my > environment variables, and attempted to run the command: > > $MAVEN_HOME/bin/install_repo.sh $HOME/.maven/repository Don't do that. The web site is for the current UNRELEASED code. This is a problem we'll be fixing with the next release. [snip] > So I checked the FAQ, no help there. I searched the mailing list > archives for install_repo.sh, but no matches were found... Believe me, I > would really like to use this tool but the developers seem bent on > making it unnecessarily difficult. I should think that having up to date We are not trying to make it unnecessarily difficult. We make mistakes. We only have limited time. We give you software for free. > and accurate installation instructions would be a higher priority than > it appears to be. Please respond to this email on the list so that > others facing the same issues might find a useful resource where no > others appear to be. Until then, I'm off to file a bug in Jira about > this glaring oversight... -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Navigation & FAQ with multi-projects
Do you have the faq plugin in the top level project.xml? Does the top level project have a navigation.xml? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Benoit Xhenseval <[EMAIL PROTECTED]> wrote on 17/09/2003 07:18:32 AM: > Hi All, > > We're using the multiprojects features for our project (with > modules/ejb, war, etc). > top > |-modules > |-ejb > |-src > |-java > |-test > |-xdocs > |-navigation.xml > |-common > |-src > |-java > |-test > |-xdocs > |-navigation.xml > |-xdocs > |-navigation.xml > |-faq.fml > > > We've added a faq.xml and a xdoc/navigation.xml in each module; > Both FAQ and navigation are working fine when it is generated at the > module level but it does not > seem to work at the top level when we use the multiproject:site in "top" > > Is this a know bug/feature in multiproject? Or are we doing something wrong? > How could we include a special navigation and/or faq at the top level? > > Many thanks > > Benoit. > > > > - > 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: sun jars
Nathan: I've been looking into this problem in relation to component deployment requirements related to the Avalon Merlin project [1]. Merlin provides support for composite components (i.e. coponents that are created dynamically based on service provided by other components). The James mail server is such as example - it is a composite component it pulls in Avalon Cornersone components as part of its implementation strategy. However, in order to deploy James you need the sun activation and mail jar files. Traditionally James has packaged and deployed thair product using container specific solutions - however, recent developments over in Avalon are providing solutions that are totally linked to the Maven repository model. For example, if you have the Merlin prouduct installed [2], you can do the following: $ merlin -install http://dpml.net/james/james-server.bar This command basically populates your local repository with the james application including the necessary bundled Sun jar files. The Merlin repository uses the same structure as the Maven repository so you can do thing like: $merlin -install -repository %MAVEN_HOME%\repository We already have a Maven plugin that provides support for component deployment based on the content of the Maven repo and it would not be too hard to update this to include the install capabilities relative to project dependencies. Stephen. [1] http://avalon.apache.org/sandbox/merlin [2] http://dpml.net/merlin/distributions Nathan Coast wrote: Hi, Just wondering if there had been any movement on the licensing of sun jars recently? http://maven.apache.org/sun-licensing-journey.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00641.html Until such a time as these jars become available via maven (if they ever do) what is the best approach to getting round dependencies? Up until now I've been placing some jar that contains dependencies into the repo and creating a dependency to it. E.g. j2ee.jar, weblogic.jar. Whilst this works, it seems a bit ham-fisted, once you start sharing the project with other people - unless they're sharing the same local repo. cheers Nathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen J. McConnell mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
sun jars
Hi, Just wondering if there had been any movement on the licensing of sun jars recently? http://maven.apache.org/sun-licensing-journey.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg00641.html Until such a time as these jars become available via maven (if they ever do) what is the best approach to getting round dependencies? Up until now I've been placing some jar that contains dependencies into the repo and creating a dependency to it. E.g. j2ee.jar, weblogic.jar. Whilst this works, it seems a bit ham-fisted, once you start sharing the project with other people - unless they're sharing the same local repo. cheers Nathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-reports
Want: my extra FAQs in maven-reports.html In my root project.xml I register the faq plugin in the Then in the root maven.xml: as instructed. Now in attempt to add several other FAQs for my project members, I tried this in the same preGoal Worked fine, but since we are never satisfied I wanted them all listed in the "project reports". I saw this in the faq-plugin so I did that for each extra FAQ right before the . This also did "most" of what I wanted. in the navcolum under the collapsable Project Reports I see all 3 of my faqs. However it is not listed in the Maven Generated Reports table out in maven-reports.html Ok, how do I add things to that table? --- "Some people say porosity implies permeability ..." kevinHagel http://hagelnx.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: uhmm... installation?
The problem has been discussed on the mailing list about the documentation actually being too up to date - this reflects an unreleased version of Maven. The install_repo.sh step is there to save some downloading on your part, but it wasn't present in beta-10. I've updated the JIRA issue to indicate we should get a consistent site for a release, and maintain previous release documentation too, as well as keeping other doucmentation up to date (like the FAQ, news and status, etc). - Brett > -Original Message- > From: Elias Sinderson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 17 September 2003 7:59 AM > To: Maven Users List > Subject: Re: uhmm... installation? > > > FYI, I did the same thing and have been able to build my > project without > any further difficulties. I did, however, enter a bug into Jira as to > the installation instructions being out of date ... > > > Cheers, > Elias > > > Lisa Kavanaugh wrote: > > >I ran into the same issue, and just skipped that step. I have been > >cruising along since & haven't missed it. > > > >-Original Message- > >From: Elias Sinderson [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, September 16, 2003 9:35 AM > >To: [EMAIL PROTECTED] > >Subject: uhmm... installation? > > > > > >Dear Maven Community, > > > >Do help me out with this one, I hope I'm not missing > something entirely > >obvious... (Don't you just love requests for help that > start off like > >this? ;-) > > > >I'm attempting to set up maven for the first time. I visited the web > >page, where I was able to download the latest distribution > >(1.0-beta-10) without difficulty. I untarred the file, set my > >environment variables, and attempted to run the command: > > > >$MAVEN_HOME/bin/install_repo.sh $HOME/.maven/repository > > > >as instructed on the installation page. Guess what? There is no > >'install_repo.sh' in the $MAVEN_HOME/bin directory! I thought I must > >have the wrong version, as the instructions clearly state > that they are > >for maven-1.0-beta-8, so I downloaded that version as well > and untarred > >it. Guess what? There is no 'install_repo.sh' included in that > >distribution either! Just in case, I also checked the > maven-1.0-beta-9 > >distribution as well, and no 'install_repo.sh' was to be found. In > >frustration, I downloaded and checked the .zip distributions > as well ... > >no 'install_repo.sh' to be found anywhere. > > > >So I checked the FAQ, no help there. I searched the mailing list > >archives for install_repo.sh, but no matches were found... > Believe me, I > >would really like to use this tool but the developers seem bent on > >making it unnecessarily difficult. I should think that > having up to date > >and accurate installation instructions would be a higher > priority than > >it appears to be. Please respond to this email on the list so that > >others facing the same issues might find a useful resource where no > >others appear to be. Until then, I'm off to file a bug in Jira about > >this glaring oversight... > > > > > >For the love of god, > >Elias > > > > > >- > >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] >
J2EE projects layout
Hy, I have a question regarding the maven J2EE project layout proposed by vincent massol, that is : ROOT\ \applications \myEAR \modules \myAPI \myEJB \myWAR \containers \myJ2EEContainer \nodes \myDatabase \myHost Suppose i have a .properties file associated with myWAR, but that i want this .properties file to be deployed outside the WAR, under a directory specified by the guys who rules exploitation... How do you achieve this ? By storing the .properties file under ROOT\modules\myWAR\src\conf and building two artifacts for myWAR (the war and the .properties file, or the war and a zip file which contains the .properties file, etc...) ? Or by storing the .properties file under another project (myHost ? ... ?). Thanks for your help ! Sebastien Brunot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build problem related to test distribution
On Tue, 16 Sep 2003, Mark Langley wrote: > We also desire to make test utility classes (primarily Mock Objects) > available for use in testing of dependent projects. The approach of creating > XYZ.jar and XYZ-tests.jar artifacts from project XYZ seems to be the best > approach to this. Subsequent projects could then prescribe XYX-tests.jar as > a test-dependency in their project.xml if needed. > > I don't think this runs counter to any of the arguments presented on the > WhyYouCantCreateMultipleArtifactsInOneProject wiki page. Packaging an > additional jar from the test code need not impact any of the plugins (except > for a new test:deploy goal), and the build settings need not change. There > is no risk of recreating the multi-project plugin within a single project. > > Alternate suggestion #1 of distributing test code inside a production jar is > not a realistic solution in many (most?) environments. Point taken :) > > Alternate suggestion #2 of creating a new XYZ-test-support project creates a > circular dependency - I can't test XYZ without the support classes, and I > can't build the support classes without XYZ. I don't follow you here, perhaps you should try to clearify with a example In your original mail you wanted to create a source distribution and a test distribution. What is a test distribution? The src/main/java directory is for the source files of a artifact and the src/test/java is a set of tests for testing the artifact. They are not supposed to be general classes for use outside of the artifact. If you have a set of general test cases/util objects they really belong in a separate project. > > I am curious to learn if the concept of a XYX-tests.jar artifact has been > discussed before, and if so, why it would be rejected. > > Thanks, > > Mark > > > -Original Message- > From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] > Sent: September 16, 2003 3:35 AM > To: Maven Users List > Subject: Re: Build problem related to test distribution > > > On Mon, 15 Sep 2003, Gil César Faria wrote: > > > Hello everybody! > > > > I have a basic project where I have some general utility classes used by > > all other maven projects. > > Inside this general project, i have some abstract test classes that > > should be used within all other > > test classes of all projects. All test classes, including those abstract > > classes are under test directory. > > > > When maven builds the distribution for this general project, it only > > includes the source classes, not > > the test classes. But when i try to build other projects that depends > > upon this general project, i cannot > > compile the tests because the abstract test classes cannot be found. > > > > I am not sure about the best solution for this problem and would like an > > advise from our > > more maven experienced coleagues: > > > > Can i generate more than one artifact (jar) for a single project ? some > > kind of source distribution and test distribution ... > > No > > http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject > > > > > Should i generate only a single jar with all source and test classes > > inside it ? > > Don't see why not. The test class isnt a class for testing the artifact, > rather a part of you general stuff. Bear in mind that the testcase class > will be included if you end up building war or uberjars. > > > > > Should i create a new project to hold only the abstract test classes, > > and include it as a dependency for all other projects ? > > This is also a solution. Currently you can only state _dependencies_ for a > project so it doesn't add much value, but with a later version you can > state runtime/testtime dependencies and then it might be a good idea to > have it as a separate project. > > Guess the rest of your questions are answered by now? :) > > > > > Should i redefine dist:build to create a test distribution ? > > > > There is an automated way to tell maven that the test classes should be > > considered as a dependency ? > > > > There is another way to organize my project classes to solve this problem? > > > > Can I define source dependencies and test dependencies separatelly? > > > > Any other suggestions? > > > > Thanks in advance! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: uhmm... installation?
FYI, I did the same thing and have been able to build my project without any further difficulties. I did, however, enter a bug into Jira as to the installation instructions being out of date ... Cheers, Elias Lisa Kavanaugh wrote: I ran into the same issue, and just skipped that step. I have been cruising along since & haven't missed it. -Original Message- From: Elias Sinderson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: uhmm... installation? Dear Maven Community, Do help me out with this one, I hope I'm not missing something entirely obvious... (Don't you just love requests for help that start off like this? ;-) I'm attempting to set up maven for the first time. I visited the web page, where I was able to download the latest distribution (1.0-beta-10) without difficulty. I untarred the file, set my environment variables, and attempted to run the command: $MAVEN_HOME/bin/install_repo.sh $HOME/.maven/repository as instructed on the installation page. Guess what? There is no 'install_repo.sh' in the $MAVEN_HOME/bin directory! I thought I must have the wrong version, as the instructions clearly state that they are for maven-1.0-beta-8, so I downloaded that version as well and untarred it. Guess what? There is no 'install_repo.sh' included in that distribution either! Just in case, I also checked the maven-1.0-beta-9 distribution as well, and no 'install_repo.sh' was to be found. In frustration, I downloaded and checked the .zip distributions as well ... no 'install_repo.sh' to be found anywhere. So I checked the FAQ, no help there. I searched the mailing list archives for install_repo.sh, but no matches were found... Believe me, I would really like to use this tool but the developers seem bent on making it unnecessarily difficult. I should think that having up to date and accurate installation instructions would be a higher priority than it appears to be. Please respond to this email on the list so that others facing the same issues might find a useful resource where no others appear to be. Until then, I'm off to file a bug in Jira about this glaring oversight... For the love of god, Elias - 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: uhmm... installation?
I ran into the same issue, and just skipped that step. I have been cruising along since & haven't missed it. -Original Message- From: Elias Sinderson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: uhmm... installation? Dear Maven Community, Do help me out with this one, I hope I'm not missing something entirely obvious... (Don't you just love requests for help that start off like this? ;-) I'm attempting to set up maven for the first time. I visited the web page, where I was able to download the latest distribution (1.0-beta-10) without difficulty. I untarred the file, set my environment variables, and attempted to run the command: $MAVEN_HOME/bin/install_repo.sh $HOME/.maven/repository as instructed on the installation page. Guess what? There is no 'install_repo.sh' in the $MAVEN_HOME/bin directory! I thought I must have the wrong version, as the instructions clearly state that they are for maven-1.0-beta-8, so I downloaded that version as well and untarred it. Guess what? There is no 'install_repo.sh' included in that distribution either! Just in case, I also checked the maven-1.0-beta-9 distribution as well, and no 'install_repo.sh' was to be found. In frustration, I downloaded and checked the .zip distributions as well ... no 'install_repo.sh' to be found anywhere. So I checked the FAQ, no help there. I searched the mailing list archives for install_repo.sh, but no matches were found... Believe me, I would really like to use this tool but the developers seem bent on making it unnecessarily difficult. I should think that having up to date and accurate installation instructions would be a higher priority than it appears to be. Please respond to this email on the list so that others facing the same issues might find a useful resource where no others appear to be. Until then, I'm off to file a bug in Jira about this glaring oversight... For the love of god, Elias - 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: Build problem related to test distribution
We also desire to make test utility classes (primarily Mock Objects) available for use in testing of dependent projects. The approach of creating XYZ.jar and XYZ-tests.jar artifacts from project XYZ seems to be the best approach to this. Subsequent projects could then prescribe XYX-tests.jar as a test-dependency in their project.xml if needed. I don't think this runs counter to any of the arguments presented on the WhyYouCantCreateMultipleArtifactsInOneProject wiki page. Packaging an additional jar from the test code need not impact any of the plugins (except for a new test:deploy goal), and the build settings need not change. There is no risk of recreating the multi-project plugin within a single project. Alternate suggestion #1 of distributing test code inside a production jar is not a realistic solution in many (most?) environments. Alternate suggestion #2 of creating a new XYZ-test-support project creates a circular dependency - I can't test XYZ without the support classes, and I can't build the support classes without XYZ. I am curious to learn if the concept of a XYX-tests.jar artifact has been discussed before, and if so, why it would be rejected. Thanks, Mark -Original Message- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: September 16, 2003 3:35 AM To: Maven Users List Subject: Re: Build problem related to test distribution On Mon, 15 Sep 2003, Gil César Faria wrote: > Hello everybody! > > I have a basic project where I have some general utility classes used by > all other maven projects. > Inside this general project, i have some abstract test classes that > should be used within all other > test classes of all projects. All test classes, including those abstract > classes are under test directory. > > When maven builds the distribution for this general project, it only > includes the source classes, not > the test classes. But when i try to build other projects that depends > upon this general project, i cannot > compile the tests because the abstract test classes cannot be found. > > I am not sure about the best solution for this problem and would like an > advise from our > more maven experienced coleagues: > > Can i generate more than one artifact (jar) for a single project ? some > kind of source distribution and test distribution ... No http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject > > Should i generate only a single jar with all source and test classes > inside it ? Don't see why not. The test class isnt a class for testing the artifact, rather a part of you general stuff. Bear in mind that the testcase class will be included if you end up building war or uberjars. > > Should i create a new project to hold only the abstract test classes, > and include it as a dependency for all other projects ? This is also a solution. Currently you can only state _dependencies_ for a project so it doesn't add much value, but with a later version you can state runtime/testtime dependencies and then it might be a good idea to have it as a separate project. Guess the rest of your questions are answered by now? :) > > Should i redefine dist:build to create a test distribution ? > > There is an automated way to tell maven that the test classes should be > considered as a dependency ? > > There is another way to organize my project classes to solve this problem? > > Can I define source dependencies and test dependencies separatelly? > > Any other suggestions? > > Thanks in advance! > > Trygve - 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]
uhmm... installation?
Dear Maven Community, Do help me out with this one, I hope I'm not missing something entirely obvious... (Don't you just love requests for help that start off like this? ;-) I'm attempting to set up maven for the first time. I visited the web page, where I was able to download the latest distribution (1.0-beta-10) without difficulty. I untarred the file, set my environment variables, and attempted to run the command: $MAVEN_HOME/bin/install_repo.sh $HOME/.maven/repository as instructed on the installation page. Guess what? There is no 'install_repo.sh' in the $MAVEN_HOME/bin directory! I thought I must have the wrong version, as the instructions clearly state that they are for maven-1.0-beta-8, so I downloaded that version as well and untarred it. Guess what? There is no 'install_repo.sh' included in that distribution either! Just in case, I also checked the maven-1.0-beta-9 distribution as well, and no 'install_repo.sh' was to be found. In frustration, I downloaded and checked the .zip distributions as well ... no 'install_repo.sh' to be found anywhere. So I checked the FAQ, no help there. I searched the mailing list archives for install_repo.sh, but no matches were found... Believe me, I would really like to use this tool but the developers seem bent on making it unnecessarily difficult. I should think that having up to date and accurate installation instructions would be a higher priority than it appears to be. Please respond to this email on the list so that others facing the same issues might find a useful resource where no others appear to be. Until then, I'm off to file a bug in Jira about this glaring oversight... For the love of god, Elias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Navigation & FAQ with multi-projects
Hi All, We're using the multiprojects features for our project (with modules/ejb, war, etc). top |-modules |-ejb |-src |-java |-test |-xdocs |-navigation.xml |-common |-src |-java |-test |-xdocs |-navigation.xml |-xdocs |-navigation.xml |-faq.fml We've added a faq.xml and a xdoc/navigation.xml in each module; Both FAQ and navigation are working fine when it is generated at the module level but it does not seem to work at the top level when we use the multiproject:site in "top" Is this a know bug/feature in multiproject? Or are we doing something wrong? How could we include a special navigation and/or faq at the top level? Many thanks Benoit. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse Plugin - eclipse.dependency
I have two projects, A and B. Project A depends on project B, so I set eclipse.dependency to true like this inside project.xml for project A: projectB projectB 1.1 true When I load up both projects in Eclipse and run "Build All" everything seems to build just fine. However, when I attempt to run, I get this: ServiceProperties: MissingResourceException - Can't find bundle for base name resources.properties.Services, locale en_US Unable to get server reference: null java.lang.NullPointerException The bundle in question lies within project B. If I leave out eclipse.dependency, then the project B JAR will show up as a build path library but it doesn't show up as a project dependency in Eclipse. So what I've had to do is just leave in eclipse.dependency and then manually add the JAR to the build path. Is there a way (perhaps another property to set) to have the project dependency and the library both show up? Yoway Buorn Software Engineer Imagery Systems Engineering GENERAL DYNAMICS Advanced Information Systems 112 Lakeview Canyon Road Thousand Oaks, CA 91362-5027 Tel 805 497 5074 Fax 805 497 5050 [EMAIL PROTECTED] So one day these two muffins were baking in an oven. One muffin turned to the other muffin and said, "Boy it sure is hot in here." The other muffin turned to the first muffin and said, "Holy crap! A talking muffin!" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
incomplete JNLP-Plugin documentation
Hi, The documentation is missing the property maven.jnlp.properties which is quite important to specify system-properties for the main-jar. Thanks for adding it to the documentation Christian -Original Message- From: Van Rompaey, Danny [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 10:48 AM To: '[EMAIL PROTECTED]' Subject: Project.xml not at top-level question Hi, Is it possible to generate reports starting from top-level but not having your project.xml at top-level ? I have the following structure : project project/ant/maven (this is the dir where my project.xml and project.properties are) project/src project/resource I tried playing with the -d, -p and -f option but with no luck. (reports are generated, but only for the project/ant/maven dir) The project files must stay in that dir and no files can be added to the top-level but executing maven can be done from the top-level dir or from the project/ant/maven dir. Any ideas ? Thx, Danny - 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: Multiproject help
Is one planned? Can you give me some clues so I can rough out something in maven.xml? -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, September 15, 2003 7:50 PM > To: Maven Users List > Subject: RE: Multiproject help > > > There isn't a multiproject:dist-build yet. > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > > > "Howard M. Lewis Ship" <[EMAIL PROTECTED]> wrote on > 16/09/2003 07:28:26 > AM: > > > Hm. I'm now making some progress; still not sure how to build a > > binary / source distribution. > > What's the equivalent of dist:build for multiprojects? I'd like a > > binary dist that include all the > > jars for all the subprojects ... or do I have to allow each > > subproject to generate its own dist? > > > > -- > > Howard M. Lewis Ship > > Creator, Tapestry: Java Web Components > > http://jakarta.apache.org/tapestry > > http://jakarta.apache.org/commons/sandbox/hivemind/ > > http://javatapestry.blogspot.com > > > > > -Original Message- > > > From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED] > > > Sent: Monday, September 15, 2003 5:02 PM > > > To: 'Maven Users List' > > > Subject: RE: Multiproject help > > > > > > > > > Ok, I guess you leave the element out in the top-level > > > project.xml. > > > > > > -- > > > Howard M. Lewis Ship > > > Creator, Tapestry: Java Web Components > > > http://jakarta.apache.org/tapestry > > > http://jakarta.apache.org/commons/sandbox/hivemind/ > > > http://javatapestry.blogspot.com > > > > > > > -Original Message- > > > > From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED] > > > > Sent: Monday, September 15, 2003 4:29 PM > > > > To: Maven Users List > > > > Subject: Multiproject help > > > > > > > > > > > > I'm trying to split up my existing Maven project into a master > > > > project containing sub-projects. Is this even the > right thing to > > > > do? > > > > > > > > I'm getting the following error: > > > > > > > > bash-2.05b$ maven multiproject:site > > > > __ __ > > > > | \/ |__ _Apache__ ___ > > > > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > > > |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT > > > > > > > > Starting the reactor... > > > > Our processing order: > > > > HiveMind Services and Configuration Microkernel > > > > + > > > > | Gathering project list HiveMind Services and Configuration > > > > Microkernel > > > > | Memory: 3M/11M > > > > + > > > > > > > > BUILD FAILED > > > > File.. file:/C:/Documents and > > > > > > > > Settings/Howard/.maven/plugins/maven-multiproject-plugin-1.1-SNAPSHO > > > T/ > > > > Element... fail > > > > Line.. 105 > > > > Column 101 > > > > You must exclude commons-hivemind:commons-hivemind (the top > > > > level project) from the subproject set Total time: 3 seconds > > > > Finished at: Mon Sep 15 16:21:39 EDT 2003 > > > > > > > > > > > > What does that mean? > > > > > > > > Should my top-level project build the HiveMind framework (in > > > > advance of child projects building add-ons and examples?) > > > > > > > > Couldn't find info in the wiki. > > > > > > > > -- > > > > Howard M. Lewis Ship > > > > Creator, Tapestry: Java Web Components > > > > http://jakarta.apache.org/tapestry > > > > > > > http://jakarta.apache.org/commons/sandbox/hivemind/ > > > http://javatapestry.blogspot.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] > > > > > > > > > > - > > 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]
Goal [xxx] has no action definition
Hi, I saw a bug reported for a similar error. It waas regarding the multiproject:site goal. The problem does not seem to be specific to multiproject plugin. Looks to be a generic reactor problem. For instance, I run the reactor more than once on various goals and get the same sort of error : Here is my maven xml snippet: I run : maven foo and the build fails when running the reactor a second time. In the above snippet I ran "java:compile" but running "site" and "clean" also give errors. What am i doing wrong? or is this a reactor feature/bug. If this is how the reactor works then how can I run a reactor to do my compiling then a reactor to do my site - the build fails when running the second reactor. Regards Elton ___ The views expressed in this email are, unless otherwise stated, those of the author and not those of the FirstRand Banking Group or its management. The information in this e-mail is confidential and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is, for whatever reason, corrupted or does not reach its intended destination. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: J2EE projects layout
Hi Sebastien, Here's what I do: - If the config file is supposed to be packaged in the jar/war/rar/etc, then I store it in the src tree of that jar/war/rar/etc - if the config file is supposed to be tuned for production, i.e. it has to be visible by the production guys for example, then I consider this file a config file of the whole application in the container. I put it in the container project. Maybe what you find misleading are the names: - the "applications" projects are not the application per see (an application is really an EAR deployed in a container and properly configured) - the "container" project really represent the executable application. For example if you were developing a native executable C application, you would write the code instead of the container and that would clearly be your application. It's the same here. If you have better name, please feel free to propose them as I'm not too happy about them ;-) Thanks -Vincent > -Original Message- > From: BRUNOT Sébastien [mailto:[EMAIL PROTECTED] > Sent: 16 September 2003 14:42 > To: 'Vincent Massol' > Cc: '[EMAIL PROTECTED]' > Subject: J2EE projects layout > > Hy, > > I have a question regarding the maven J2EE project layout proposed by > vincent massol, that is : > > ROOT\ > \applications > \myEAR > \modules > \myAPI > \myEJB > \myWAR > \containers > \myJ2EEContainer > \nodes > \myDatabase > \myHost > > Suppose i have a .properties file associated with myWAR, but that i want > this .properties file to be deployed outside the WAR, under a directory > specified by the guys who rules exploitation... How do you achieve this ? > By > storing the .properties file under ROOT\modules\myWAR\src\conf and > building > two artifacts for myWAR (the war and the .properties file, or the war and > a > zip file which contains the .properties file, etc...) ? Or by storing the > .properties file under another project (myHost ? ... ?). > > Thanks for your help ! > > Sebastien Brunot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Project.xml not at top-level question
Hi, Is it possible to generate reports starting from top-level but not having your project.xml at top-level ? I have the following structure : project project/ant/maven (this is the dir where my project.xml and project.properties are) project/src project/resource I tried playing with the -d, -p and -f option but with no luck. (reports are generated, but only for the project/ant/maven dir) The project files must stay in that dir and no files can be added to the top-level but executing maven can be done from the top-level dir or from the project/ant/maven dir. Any ideas ? Thx, Danny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cactus Plugin
> -Original Message- > From: Bryce Fischer [mailto:[EMAIL PROTECTED] > Sent: 16 September 2003 04:04 > To: Maven Users List > Subject: Re: Cactus Plugin > > Sorry so late getting back on this. I'm responding on the Maven list, as > this deals with the Cactus Plugin, and project organization, and may be > of interest to others. > > You mentioned: > > > - Have separate projects for each J2EE module (EJB-JAR, WAR, RAR, simple > > jar libraries) > > Done. I'm assuming the Cactus tests (for each module) go in these > projects. The test sources, yes. For the execution of them, not necessarily (see below). > > > - Have a project for the application (EAR in most cases) which is the > > aggregation of the different J2EE module projects > > Done. > > > - (optional) Have a project for the container holding the application > > (this project will contain the container's configuration files) > > I assume this is for stuff like jboss.xml file, etc. I skipped this as > I'm using XDoclet to generate those files in the specific projects. > > > I would run the cactus tests in the container project as Cactus tests > > run in a running container. > > If I understand correctly, this is different than the optional step > above. This project would be a stand alone war file that will actually > run the Cactus test? > > When running cactus:test, It runs the tests in the specified container > (specified in the build.properties file?). For example, I've set > cactus.home.jboss3x, so it should run using that container? If you want to be logical, the best place to run your Cactus tests is when you have your application configured to run in your app server. This is in the container project (or EAR, or WAR if your application is only made of a single WAR). That said, as the Cactus plugin provides a full working environment for you, it is not strictly necessary to run in your own defined environment. You can run in the Cactus provided one. That said, the cactus environment is a default and basic one and if you need to modify any config file for a container, you'll have to provide them to cactus. And the place where you will have these files defined is in the container project (or EAR, or WAR). -Vincent > > Thanks again for your help. > > -- > Bryce Fischer <[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: jxr-plugin fails if '_' in packagename
The problem is in the class org.apache.maven.jxr.pacman.JavaFileImpl. The
used StreamTokenizer has to be extended by '_' as a word character:
private StreamTokenizer getTokenizer() throws IOException
{
...
stok.commentChar('*');
stok.wordChars('_', '_'); // add here the underscore character as
an word character
...
}
Regards, Matthias
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build problem related to test distribution
On Mon, 15 Sep 2003, Gil César Faria wrote: > Hello everybody! > > I have a basic project where I have some general utility classes used by > all other maven projects. > Inside this general project, i have some abstract test classes that > should be used within all other > test classes of all projects. All test classes, including those abstract > classes are under test directory. > > When maven builds the distribution for this general project, it only > includes the source classes, not > the test classes. But when i try to build other projects that depends > upon this general project, i cannot > compile the tests because the abstract test classes cannot be found. > > I am not sure about the best solution for this problem and would like an > advise from our > more maven experienced coleagues: > > Can i generate more than one artifact (jar) for a single project ? some > kind of source distribution and test distribution ... No http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject > > Should i generate only a single jar with all source and test classes > inside it ? Don't see why not. The test class isnt a class for testing the artifact, rather a part of you general stuff. Bear in mind that the testcase class will be included if you end up building war or uberjars. > > Should i create a new project to hold only the abstract test classes, > and include it as a dependency for all other projects ? This is also a solution. Currently you can only state _dependencies_ for a project so it doesn't add much value, but with a later version you can state runtime/testtime dependencies and then it might be a good idea to have it as a separate project. Guess the rest of your questions are answered by now? :) > > Should i redefine dist:build to create a test distribution ? > > There is an automated way to tell maven that the test classes should be > considered as a dependency ? > > There is another way to organize my project classes to solve this problem? > > Can I define source dependencies and test dependencies separatelly? > > Any other suggestions? > > Thanks in advance! > > Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
