Re: How to Specify 'Links' In the Javadoc Plugin
On 6/10/06, Lyndon Washington <[EMAIL PROTECTED]> wrote: I saw from the javadoc-mojo page, http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html, that there is a links tag which takes an ArrayList. It also says that the Strings are comma separate. I added an example to the wiki: http://docs.codehaus.org/display/MAVENUSER/Javadoc+Plugin maven-javadoc-plugin http://java.sun.com/j2se/1.4.2/docs/api http://jakarta.apache.org/commons/chain/apidocs -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to Specify 'Links' In the Javadoc Plugin
Lyndon Washington wrote: > Hi, > > I am migrating an Ant build to Maven. One portion is generating javadocs. > In the Ant one there are 3 link tags . . . > http://logging.apache.org/log4j/docs/api/"/> > http://java.sun.com/j2se/1.5.0/docs/api/"/> > http://www.dom4j.org/apidocs/"/> > > I saw from the javadoc-mojo page, > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html, > that > there is a links tag which takes an ArrayList. It also says that the > Strings are comma separate. > > What does this actually mean? I have tried placing the URLS as comma > separated values within the links tag, but I get an error that it was > expecting an ArrayList and received a String. This works for me: org.apache.maven.plugins maven-javadoc-plugin http://java.sun.com/j2se/1.5.0/docs/api/ HTH, -dirk -- A: Maybe because some people are too annoyed by top-posting. Q: Why do I not get an answer to my question(s)? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to Specify 'Links' In the Javadoc Plugin
Hi, I am migrating an Ant build to Maven. One portion is generating javadocs. In the Ant one there are 3 link tags . . . http://logging.apache.org/log4j/docs/api/"/> http://java.sun.com/j2se/1.5.0/docs/api/"/> http://www.dom4j.org/apidocs/"/> I saw from the javadoc-mojo page, http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html, that there is a links tag which takes an ArrayList. It also says that the Strings are comma separate. What does this actually mean? I have tried placing the URLS as comma separated values within the links tag, but I get an error that it was expecting an ArrayList and received a String. Any help would be most appreciated. Cheers, -Lyndon-
Inheriting properties from the parent POM
Hi all,
I use a filter to inject properties in a config file. Because the properties
file to use depend on the environment, I defined several profiles.
i.e.:
${db-properties}
src/main/resources
true
And:
blahblah
src/main/filters/dev-env.properties
Now, this works fine when I put the and definitions in
the same POM; but when I move the section to the parent POM files
(because I would like to keep all profile-related information in the same
place), the properties are not passed to the child POM.
I would like to keep all profile-related information in the same place
Is there a way I can pass properties from a parent POM to a child?
Or is there a better way to deal with this situation?
Thanks for your help,
Theo.
Re: NoClassDefFoundErrorfor a few classes that seems to be in the classp
Thanks for the tip. The problem is that all four (4) developers have this issue on their computer. But, I'll will follow your instructions tomorrow and check checksums etc. Regards, Jimisola -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be-in-the-classpath-t1767398.html#a4812501 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NoClassDefFoundErrorfor a few classes that seems to be in the classp
Make sure that the specific class(es) you get the exceptions for really are in the jars that exist in your local repo (i.e. rule out the possibility that you got a bad jar file, failed download, or the wrong version, etc.). Maven has some options to verify checksums (-C and -c), though I am not certain if they will be verified for dependencies that were already downloaded. This might ensure the integrity of the downloads. You could also move/delete your ~/.m2/repository dir to see if re-downloading them all fixes the issue. In maven1, I remember having some bad jars as a result of hitting ctrl-C while maven was downloading a jar. You can look inside the dependency jars in Eclipse to verify the presence of the class(es) you got the exceptions for. I also find JarsBrowser to be a convenient tool for this kind of thing. You don't even need to install it, just run this command to "Java WebStart" it: javaws http://cmarton.free.fr/jarsbrowser/jarsbrowser.jnlp ...and then point it at ~/.m2/repository. Then start to type the class file name (use slashes between the package names, as opposed to dots) that you are looking for in the Search field: org/foo/bar/fubar -Max Jimisola Laursen wrote: I have added a few libraries to our internal repository, e.g. mocquer. All added libraries our found in my local repository as well as in our internal one. root POM: [...] c3p0 c3p0 0.9.0.4 dom4j dom4j 1.6.1 xmlrpc xmlrpc 2.0.1 commons-codec commons-codec 1.3 commons-httpclient commons-httpclient 3.0.1 commons-lang commons-lang 2.1 org.postgresql pg-jdbc 74.215.jdbc3 derby org.apache.derby 10.1.2.1 derbytools org.apache.derby 10.1.2.1 bcel bcel 5.1 jaxen jaxen 1.1-beta-9 jtds net.sourceforge.jtds 1.2 xmlunit xmlunit 1.0 test junit junit 3.8.2 test org.jingle.mocquer mocquer 0.9.3 test log4j log4j 1.2.13 aspectjrt aspectj 1.5.0 javax.mail mail 1.3.3_01 xmlunit xmlunit 1.0 test dbunit dbunit 2.1 test server module pom: [...] xmlrpc xmlrpc commons-codec commons-codec commons-httpclient commons-httpclient commons-lang commons-lang org.apache.derby derby org.apache.derby derbytools net.sourceforge.jtds jtds org.postgresql pg-jdbc c3p0 c3p0 log4j log4j aspectj aspectjrt junit junit dbunit dbunit agent module pom: [...] junit junit org.jingle.mocquer mocquer xmlrpc xmlrpc commons-codec commons-codec commons-httpclient commons-httpclient commons-lang commons-lang dom4j dom4j jaxen jaxen log4j log4j javax.mail mail -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be-in-the-classpath-t1767398.html#a4811533 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 sources/javadocs installation question
My experience is that the Eclipse plugin does setup intra-project dependencies properly. so long as you run 'mvn eclipse:eclipse' from the root of the project (as opposed to running it for each module individually). If I have a project with moduleA and moduleB, and moduleB depends on moduleA, I will get an Eclipse project dependency (as opposed to a dependency on the M2_REPO/.../moduleA-1.0.jar) when I run 'mvn eclipse:eclipse' from the root of the project. In what way is the eclipse plugin not creating these dependencies properly for you? -Max Brad Davis wrote: Because the eclipse plugin doesn't properly set up intra project relationships it would be nice to have an explicit build step that could generate and deploy javadoc and source jars, even for snapshot releases. Brad - Original Message - From: "Stephen Duncan" <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Friday, June 09, 2006 6:11 PM Subject: Re: Maven 2 sources/javadocs installation question You can simply run mvn -DperformRelease=true install This will build source & javadoc jars & install them. No configuration option. -Stephen On 6/9/06, Matt Wheeler <[EMAIL PROTECTED]> wrote: Never mind my last email. I moved the plugin under build outside of profiles and added a package phase, and it works now. Matt W. -- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- -- Forwarded message -- From: "Matt Wheeler" <[EMAIL PROTECTED]> To: users@maven.apache.org Date: Fri, 09 Jun 2006 09:45:29 -0600 Subject: Maven 2 sources/javadocs installation question I have a project that I run install on to install the project and all of its sub project's main artifacts in the local repository. However, I would also like to "automatically" install the sources and the javadocs as well. I can generate these using sources:jar and javadoc:jar commands, however, I cannot get them to be automatically generated using the profile section in the pom that is shown in the documentation under "Introduction to the POM" at http://maven.apache.org/guides/introduction/introduction-to-the-pom.html. What would I need to do to make that example work? Also, even if I coudl get the profile to generate the source and javadoc jars, I am not sure how to install them. I assume that I could use install:install-file, but I woudl really like a more automated way if there is one. I have tried to install them manually, but the problem is that I can't get it to install in the same directory as the projects main artifact. For instance, say my project artifact is in .m2/repository/org/whatever/2.0-SNAPSHOT/stack-code-2.0-SNAPSHOT.jar. Well, if I then run a commond something like: mvn install:install-file -DartifactId=stack-code -DgroupId=org.lds.stack -Dpackaging=jar -Dversion=2.0-SNAPSHOT -Dfile=D:/Projects/Stack/stack-code/target/stack-code-2.0-SNAPSHOT-sources.jar Then, it overwrites the projects main artifact stack-code-2.0-SNAPSHOT.jar. However, if I change the version to 2.0-SNAPSHOT-sources, then it put the jar (this time with the correct name stack-code-2.0-SNAPSHOT-sources) out in the repository, but under a 2.0-SNAPSHOT-sources directory instead of under the 2.0-SNAPSHOT directory with the main artifact. I am am seeing sources placed correctly on ibiblio however, so I am just wondering what I am doing wrong, or if there is an easier way to accomplish this? Thanks, Matt W. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.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]
RE: NoClassDefFoundErrorfor a few classes that seems to be in the classp
I have added a few libraries to our internal repository, e.g. mocquer. All added libraries our found in my local repository as well as in our internal one. root POM: [...] c3p0 c3p0 0.9.0.4 dom4j dom4j 1.6.1 xmlrpc xmlrpc 2.0.1 commons-codec commons-codec 1.3 commons-httpclient commons-httpclient 3.0.1 commons-lang commons-lang 2.1 org.postgresql pg-jdbc 74.215.jdbc3 derby org.apache.derby 10.1.2.1 derbytools org.apache.derby 10.1.2.1 bcel bcel 5.1 jaxen jaxen 1.1-beta-9 jtds net.sourceforge.jtds 1.2 xmlunit xmlunit 1.0 test junit junit 3.8.2 test org.jingle.mocquer mocquer 0.9.3 test log4j log4j 1.2.13 aspectjrt aspectj 1.5.0 javax.mail mail 1.3.3_01 xmlunit xmlunit 1.0 test dbunit dbunit 2.1 test server module pom: [...] xmlrpc xmlrpc commons-codec commons-codec commons-httpclient commons-httpclient commons-lang commons-lang org.apache.derby derby org.apache.derby derbytools net.sourceforge.jtds jtds org.postgresql pg-jdbc c3p0 c3p0 log4j log4j aspectj aspectjrt junit junit dbunit dbunit agent module pom: [...] junit junit org.jingle.mocquer mocquer xmlrpc xmlrpc commons-codec commons-codec commons-httpclient commons-httpclient commons-lang commons-lang dom4j dom4j jaxen jaxen log4j log4j javax.mail mail -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be-in-the-classpath-t1767398.html#a4811533 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trouble with profile activation
I need help understanding this: "If a profile that's embedded in POM is activated by a means other than , then all triggers are suppressed." -- http://jira.codehaus.org/browse/MNG-2136 I have a profile that gets activated when JDK 1.5 is in use. I need another profile (id=myfaces) to be active by default and bring in the MyFaces JSF implementation and API jars. That is, 'mvn install' should Just Work, and use MyFaces. And then I need a way to say, "Don't use MyFaces, use the JSF Reference Implementation from Sun instead." (Another profile with id=jsfri) Right now, I have the 'myfaces' profile set as activeByDefault, but it gets suppressed by the rule quoted above, since the jdk15 profile was activated by the use of JDK 1.5 to compile. That means we always have to specify -Pmyfaces or -Pjsfri, or the project won't compile. Here's the pom in question: * http://svn.apache.org/repos/asf/struts/shale/branches/mvn_reorg/pom.xml Any ideas on how to get exactly one of the myfaces or jsfri profiles activated? Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NoClassDefFoundErrorfor a few classes that seems to be in the classp
Let's see the dependency def's you have for the problem ones. -Original Message- From: Jimisola Laursen [mailto:[EMAIL PROTECTED] Sent: Saturday, June 10, 2006 2:53 PM To: users@maven.apache.org Subject: RE: NoClassDefFoundErrorfor a few classes that seems to be in the classp Hi! I guess I didn't express myself good enough. I have everything setup with dependencies of course. The main pom have all dependency versions setup in the main pom and the modules' pom have the dependcies that each of them need. The libraries seem to be included correctly based on dependencies (transitive dependencies as well). However, when running the unit tests I keep getting NoClassDefFoundError.. What I need is help on how to trouble-shoot. I've read the guide you linked to previously. Regards, -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be -in-the-classpath-t1767398.html#a4811003 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NoClassDefFoundErrorfor a few classes that seems to be in the classp
Hi! I guess I didn't express myself good enough. I have everything setup with dependencies of course. The main pom have all dependency versions setup in the main pom and the modules' pom have the dependcies that each of them need. The libraries seem to be included correctly based on dependencies (transitive dependencies as well). However, when running the unit tests I keep getting NoClassDefFoundError.. What I need is help on how to trouble-shoot. I've read the guide you linked to previously. Regards, -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be-in-the-classpath-t1767398.html#a4811003 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NoClassDefFoundErrorfor a few classes that seems to be in the classpath
I think the basic idea you need first is that Maven's classpath is derived from the project's dependency list. So if you need a jar on the classpath, specify it as a dependency. That understanding will jump you over the next hurdles you face :-). This should help too: http://maven.apache.org/guides/introduction/introduction-to-dependency-mecha nism.html > -Original Message- > From: Jimisola Laursen [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 10, 2006 2:04 PM > To: users@maven.apache.org > Subject: NoClassDefFoundErrorfor a few classes that seems to > be in the classpath > > > Hi! > > Recently just migrated from Ant to Maven. It's a quite big > project with a main (parent) pom.xml and six-seven modules. > > Everything compiles nicely for all modules, both main and > test. However, I have two modules, server and agent, were I > keep getting NoClassDefFoundError during executing of test cases. > > - server (NoClassDefFoundError for dbunit) > - agent (NoClassDefFoundError for mocqurer and jaxen) > > I've spent a lot of time trying to figure out the problem, > but so far no luck. > What is the best way from here to try solve this matter. > > Known facts: > > - I have the same error whether I run Maven from command > line or from within Eclipse using m2eclipse > - the libraries are included in Eclipse under "Maven2 Dependencies" > - the libraries are listed in the classpath string when I > run maven in debug mode (-X) > - I started out with scope = test, but left out scope completely. > - junit-3.8.2.jar is needed by the tests as well and shows > in classpath just like the other three mentioned above > - all tests depending only on plain JUnit succeeds > > I really appreciate help on this matter since it a show > stopper for me right now. > > Also, is there a way that I can have the "test run" outputed > on stdout/stderr? E.g. "mvn test -Dsurefire.show=all" > > Regards, > Jimisola > -- > View this message in context: > http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-th > at-seems-to-be-in-the-classpath-t1767398.html#a4810522 > Sent from the Maven - Users forum at Nabble.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]
NoClassDefFoundErrorfor a few classes that seems to be in the classpath
Hi! Recently just migrated from Ant to Maven. It's a quite big project with a main (parent) pom.xml and six-seven modules. Everything compiles nicely for all modules, both main and test. However, I have two modules, server and agent, were I keep getting NoClassDefFoundError during executing of test cases. - server (NoClassDefFoundError for dbunit) - agent (NoClassDefFoundError for mocqurer and jaxen) I've spent a lot of time trying to figure out the problem, but so far no luck. What is the best way from here to try solve this matter. Known facts: - I have the same error whether I run Maven from command line or from within Eclipse using m2eclipse - the libraries are included in Eclipse under "Maven2 Dependencies" - the libraries are listed in the classpath string when I run maven in debug mode (-X) - I started out with scope = test, but left out scope completely. - junit-3.8.2.jar is needed by the tests as well and shows in classpath just like the other three mentioned above - all tests depending only on plain JUnit succeeds I really appreciate help on this matter since it a show stopper for me right now. Also, is there a way that I can have the "test run" outputed on stdout/stderr? E.g. "mvn test -Dsurefire.show=all" Regards, Jimisola -- View this message in context: http://www.nabble.com/NoClassDefFoundErrorfor-a-few-classes-that-seems-to-be-in-the-classpath-t1767398.html#a4810522 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to setup log4j with different settings for main, test and develo
Hi Doug, Thank you for the setup information, but I don't find it to be a good enough solution. Basically because we test cases that implement/extend classes other than JUnit TestCase as well. Still hoping that someone has had the same issue and have a solution. Regards, Jimisola Jimisola, FWIW, our team developed a small set of abstract test support classes that extend Junit TestCase. The base class of this set of classes is LoggingTestCase which configures log4j from a non-default " test-log4j.properties" file in the same package as the test case. Such a setup handles #2 and #3 quite nicely without any conflict with #1. HTH, Doug -- View this message in context: http://www.nabble.com/How-to-setup-log4j-with-different-settings-for-main%2C-test-and-developmen-t1766805.html#a4810402 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Combined site for multiple modules?
Hello, I split up my project into multiple modules, with one parent module. At the moment each module generate its own reports and its own site. Site documentation is placed in the parent module's site, so it would be nice if it would be possible to combine the reports (javadoc, cobutera, surefire, pmd, checkstyle) into one report (more exactly: to create one report of all sources). I only found a solution for the javadoc plugin (true). thanks :) Dennis
Re: [ANN] Maven Archetype Plugin 1.0-alpha-4 Released
will it pick up the groupId from the parent? is the groupId a required parameter in such a case? Milos On 6/6/06, Brett Porter <[EMAIL PROTECTED]> wrote: Sort of. If you have a multi-module project, and you run archetype from the parent pom location, the subproject is created, added to the modules list of the parent, and the parent added to the created suproject. - Brett On 06/06/06, Willie Vu <[EMAIL PROTECTED]> wrote: > Can someone explain "when creating a new module inside a directory > with a pom that has , update "? Does it mean > archetype supports modules? > > On 5/8/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > The Maven team is pleased to announce the release of the Maven Archetype > > Plugin, version 1.0-alpha-4. > > > > http://maven.apache.org/plugins/maven-archetype-plugin/ > > > > The Maven Archetype Plugin produces a project skeleton based on a template. > > > > You can run mvn -U to get the latest version of the plugin. > > > > Changes: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&styleName=Text&version=12410 > > > > * [ARCHETYPE-19] - archetype creation broken > > * [ARCHETYPE-14] - Archtype:create does not > > * [ARCHETYPE-28] - when creating a new module inside a directory with a > > pom that has , update > > * [ARCHETYPE-31] - Create a tool that will generate an archetype from an > > existing project > > * [ARCHETYPE-13] - testArchetype update > > * [ARCHETYPE-22] - Always generates groupId directories > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Willie Vu > > HKJUG - http://hkjug.dev.java.net > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Apache Maven - http://maven.apache.org "Better Builds with Maven" book - http://library.mergere.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]
[m2] Add timestamp to properties file using filtering
Hi, Is there a way to put a timestamp in a properties file? I am thinking in filtering, but is there a pom variable that returns the timestamp or current date? Thanks! Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn eclipse:eclipse on linux M2_REPO/path not found by eclipse
On Sat, Jun 10, 2006 at 12:19:03PM -0400, Alexandre Poitras wrote: > Just do it manually : > http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html Works fine. Thanks. I should have restarted eclipse and not just updating using F5.. Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spotlight: Maven Repository at Java.Net with GlassFish components
Hi Srgjan... We are not yet using Maven to build GlassFish, but we are refining the whole project building framework as part of the startup for GlassFish v2 (see http://blogs.sun.com/theaquarium) and that topic continues to come up. I expect substantially improved modularization as part of GlassFish v3 (which we are planning to start in parallel late summer), but something simpler like this may happen ahead of v3. We have a lot of work in our TODO list so for now we are just updating our repository but we would be happy to see the content synchronized with ibiblio - I just checked and there are some very old files in there. If people are interested in helping with that, or if they have ideas on how to improve the structure of the repository, please send mail to the DEV mailing list ([EMAIL PROTECTED]). Thanks, - eduard/o Srepfler Srgjan <[EMAIL PROTECTED]> wrote: Serge Emmanuel Pagop wrote: Sorry, the java persistence api is already available. I greet the initiative, we should just add your repository to our settings or will you synchronize with the ibiblio repository? Your file structure is strange, lib > jars/poms/sources and then artifacts crammed inside, is this standard? Are you guys using maven to build glassfish or individual libs or is this some manual overtime work? Keep up the good work! Srgjan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error looking up lifecycle mapping to retrieve optional mojos
native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond <[EMAIL PROTECTED]> wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-application Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: maven-plugin-plugin ruby org.codehaus.mojo rubyscript-maven-plugin 1.0-alpha-3-SNAPSHOT Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > Has somebody else also had this error? What can I do about it? > > Thanks, > _ ___ _ > //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com >`-` >Andreas Ebbert-Karroum >Senior Software Design Engineer > Nokia Networks Services / Middleware > phone: +49-211-94123928, fax: +49-211-9412-3838 > Heltorfer Straße 1, 40472 Düsseldorf, Germany > > -- > This message is confidential. If you have received this message in error, > please delete it from your system. You should not copy it for any purpose, > or disclose its contents to any other person. Internet communications are > not secure and therefore Nokia GmbH does not accept legal responsibility > for the contents of this message as it has been transmitted over a public > network. Thank you. > Nokia GmbH, Nokia Networks is a German Company. Further information > about the Company is available from its principal offices at > Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the > website at http://www.nokia.com/ > -- > > >-Original Message- > >From: ext > >[EMAIL PROTECTED] > >e.org > >[mailto:[EMAIL PROTECTED] > >en.apache.org] > >Sent: 08 June, 2006 01:09 > >To: users@maven.apache.org > >Subject: Error looking up lifecycle mapping to retrieve optional mojos > > > >Hi, > > > >I've defined my own plugin (with the maven-plugin-tools-ant > >plugin) with it's own lifecycle and artifact handler. when I > >now try to use the plugin in another project, it works fine, > >but I'm getting this debug warning - and I have no clue, what > >it is about - can it be fixed, and if yes, how? > > > >[DEBUG] Error looking up lifecycle mapping to retrieve > >optional mojos. Lifecycle ID: default. Error: > > Component descriptor cannot be found in the component > >repository: org.apache.maven.lifecycle.mappin > >g.LifecycleMappingtigerstripe-application. > >org.codehaus.plexus.component.repository.exception.ComponentLoo > >kupException: Component descriptor ca nnot be found in the > >component repository: > >org.apache.maven.lifecycle.mapping.LifecycleMappingtigers > >tripe-application. > >at > >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus > >Container.java:323) > >at > >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus > >Container.java:440) > >at > >org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona > >lMojosForLifecycle(Default > >LifecycleExecutor.java:1106) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc > >leForPackaging(DefaultLife > >cycleExecutor.java:994) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi > >fecycleMappings(DefaultLif > >ecycleExecutor.java:975) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > >(DefaultLifecycleExecutor. > >java:453) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > >AndHandleFailures(DefaultL > >ifecycleExecutor.java:306) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask > >Segments(DefaultLifecycleE > >xecutor.java:273) > >at > >org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def > >aultLifecycleExecutor.java > >:140) > >at > >org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > >at org.apache.ma
Re: How to setup log4j with different settings for main, test and developmen
Jimisola, FWIW, our team developed a small set of abstract test support classes that extend Junit TestCase. The base class of this set of classes is LoggingTestCase which configures log4j from a non-default " test-log4j.properties" file in the same package as the test case. Such a setup handles #2 and #3 quite nicely without any conflict with #1. HTH, Doug On 6/10/06, Jimisola Laursen <[EMAIL PROTECTED]> wrote: Hi! I've seen various posts on log4j and Maven, but I haven't seen any answer to what I want to do. I want to be able to use different settings for log4j for: 1. main (releases using mvn assembly) 2. tests (unit tests) 3. development (when running/debugging the program within Eclipse or outside with more extra logging) I know that I should place log4j.properties under main/resources and test/resources. This will hopefully solve 1) and 2) . However, I read something about Maven giving precedence to main/resources instead of test/resources - is that still the case? I would like to avoid a long line of system properties on the command line since they're easy to forget and especially for new develepors to get. I'd then prefer to just add one "environment" property (main, test, development) which can then be used throughout our Maven environment in case we have similiar situations. Any ideas? Regards, Jimisola -- View this message in context: http://www.nabble.com/How-to-setup-log4j-with-different-settings-for-main%2C-test-and-developmen-t1766805.html#a4808936 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn eclipse:eclipse on linux M2_REPO/path not found by eclipse
Just do it manually : http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html On 6/10/06, Marc Weber <[EMAIL PROTECTED]> wrote: Hi. After running mvn eclipse:eclipse -Dproject=projectname I get my .classpath file. Fine. BUILD SUCCESFUL. But eclipse still can't resolve it. Even mvn eclipse:add-maven-repo -Declipse.workspace=/home/marc/workspace the classpath entries look like this didn't help. What am I doing still wrong? Marc - 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: Spotlight: Maven Repository at Java.Net with GlassFish components
Hi Serge. We just pushed fresh copies of the JavaPersistence API and TopLink Essentials JARs. Check: http://blogs.sun.com/roller/page/theaquarium?entry=java_persistence_and_ejb_jars The plan is to update these components as part of our regular builds, but this may take a few more weeks. But any and all help would be very appreciated. re: javaee.jar -- Bill mentioned to me that he now knew how to create such a thing, so we will get that done "soon". - eduard/o > From Serge Emmanuel Pagop" <[EMAIL PROTECTED]> > > Sorry, the java persistence api is already available. > > On 6/5/06, Serge Emmanuel Pagop <[EMAIL PROTECTED]> wrote: >> >> Hello Eduardo, >> >> this is a cool Idea. But one most important artifact is missing the >> javaee.jar for jpa, ejb3, >> >> Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to setup log4j with different settings for main, test and developmen
Hi! I've seen various posts on log4j and Maven, but I haven't seen any answer to what I want to do. I want to be able to use different settings for log4j for: 1. main (releases using mvn assembly) 2. tests (unit tests) 3. development (when running/debugging the program within Eclipse or outside with more extra logging) I know that I should place log4j.properties under main/resources and test/resources. This will hopefully solve 1) and 2) . However, I read something about Maven giving precedence to main/resources instead of test/resources - is that still the case? I would like to avoid a long line of system properties on the command line since they're easy to forget and especially for new develepors to get. I'd then prefer to just add one "environment" property (main, test, development) which can then be used throughout our Maven environment in case we have similiar situations. Any ideas? Regards, Jimisola -- View this message in context: http://www.nabble.com/How-to-setup-log4j-with-different-settings-for-main%2C-test-and-developmen-t1766805.html#a4808936 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I'm looking for a simple aspectJ example with mvn
Hi! Add a dependency on the aspect runtime aspectjrt aspectj 1.5.0 and then a build configuration org.codehaus.mojo aspectj-maven-plugin 1.5 1.5 compile test-compile I hope this helps. I am a Maven newbie myself, but this works for me. Note: source/target sets AspectJ to compile for JDK 1.5. Regards, Jimisola -- View this message in context: http://www.nabble.com/I%27m-looking-for-a-simple-aspectJ-example-with-mvn-t1765989.html#a4808856 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error looking up lifecycle mapping to retrieve optional mojos
Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-application Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: maven-plugin-plugin ruby org.codehaus.mojo rubyscript-maven-plugin 1.0-alpha-3-SNAPSHOT Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- >-Original Message- >From: ext >[EMAIL PROTECTED] >e.org >[mailto:[EMAIL PROTECTED] >en.apache.org] >Sent: 08 June, 2006 01:09 >To: users@maven.apache.org >Subject: Error looking up lifecycle mapping to retrieve optional mojos > >Hi, > >I've defined my own plugin (with the maven-plugin-tools-ant >plugin) with it's own lifecycle and artifact handler. when I >now try to use the plugin in another project, it works fine, >but I'm getting this debug warning - and I have no clue, what >it is about - can it be fixed, and if yes, how? > >[DEBUG] Error looking up lifecycle mapping to retrieve >optional mojos. Lifecycle ID: default. Error: > Component descriptor cannot be found in the component >repository: org.apache.maven.lifecycle.mappin >g.LifecycleMappingtigerstripe-application. >org.codehaus.plexus.component.repository.exception.ComponentLoo >kupException: Component descriptor ca nnot be found in the >component repository: >org.apache.maven.lifecycle.mapping.LifecycleMappingtigers >tripe-application. >at >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus >Container.java:323) >at >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus >Container.java:440) >at >org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona >lMojosForLifecycle(Default >LifecycleExecutor.java:1106) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc >leForPackaging(DefaultLife >cycleExecutor.java:994) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi >fecycleMappings(DefaultLif >ecycleExecutor.java:975) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal >(DefaultLifecycleExecutor. >java:453) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal >AndHandleFailures(DefaultL >ifecycleExecutor.java:306) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask >Segments(DefaultLifecycleE >xecutor.java:273) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def >aultLifecycleExecutor.java >:140) >at >org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso >rImpl.java:39) >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho >dAccessorImpl.java:25) >at java.lang.r
mvn eclipse:eclipse on linux M2_REPO/path not found by eclipse
Hi. After running mvn eclipse:eclipse -Dproject=projectname I get my .classpath file. Fine. BUILD SUCCESFUL. But eclipse still can't resolve it. Even mvn eclipse:add-maven-repo -Declipse.workspace=/home/marc/workspace the classpath entries look like this didn't help. What am I doing still wrong? Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie archetype question
Ben, That's the kind of feedback I was looking for, yes. For some reason, I had it in my head that you shouldn't touch the directory structure once the archetype did it's work, but as I think about it, the pom that both archetypes create is almost the same. Thinking along those lines, adding the directories manually begins to make sense. Thanks much for your responses, Mike On 6/10/06, ben short <[EMAIL PROTECTED]> wrote: Mike, I have used maven for a couple of webapps, usally I use the webapp archetype to generate the pom and initial structure then I create the java directory manually. Once you have created them maven will compile the jva source as normal, and the class files get moved to the correct place in the produced war. I dont know of a archtype that does this for you, but that dosent mean there isn't one. Also I have created a project that has a webapp module and a java module. For this I used the quick start archetype to create the jar module, and the webapp to create the webapp module. I then moved the out directory's produced under a project directory and created the project pom manually. I hope this is of some help... Ben On 6/10/06, Mike Lundin <[EMAIL PROTECTED]> wrote: > Ben, > > I was assuming that there was an archetype out there that would generate > that structure for me. Is that not the case? > > Mike > > On 6/9/06, ben short <[EMAIL PROTECTED]> wrote: > > > > Mike, > > > > You can just create the directorys you need from the link .. > > > > > > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > > > > Or you can create a seperate project that has the java source and add > > it as a dependacy of your webapp. > > > > > > > > Ben > > > > On 6/10/06, Mike Lundin <[EMAIL PROTECTED]> wrote: > > > I'm working on creating a new webapp project using maven and the > > > archetype:create with the maven-archetype-webapp archetype. I may not > > > understand things correctly, but I don't see some directories that I > > would > > > assume would be in there. There is nothing for Java src files or > > anything > > > like that in there. > > > > > > Should those be in there, or is the preferred method to created multiple > > > maven projects and make them all dependencies on each other? I tried > > > creating archetypes within archetypes (by changing package to pom), but > > that > > > seem to disregard the archetype I sent in and only ever used the > > quickStart > > > archetype. > > > > > > Any help on this would be greatly appreciated -- and feel free to point > > me > > > to a URL that has more information. I've looked through the resources I > > > know and am not finding anything definitive. > > > > > > Thanks much, > > > Mike > > > > > > > > > > > > -- > Mike Lundin > > -- Mike Lundin
RE: Error looking up lifecycle mapping to retrieve optional mojos
Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- >-Original Message- >From: ext >[EMAIL PROTECTED] >e.org >[mailto:[EMAIL PROTECTED] >en.apache.org] >Sent: 08 June, 2006 01:09 >To: users@maven.apache.org >Subject: Error looking up lifecycle mapping to retrieve optional mojos > >Hi, > >I've defined my own plugin (with the maven-plugin-tools-ant >plugin) with it's own lifecycle and artifact handler. when I >now try to use the plugin in another project, it works fine, >but I'm getting this debug warning - and I have no clue, what >it is about - can it be fixed, and if yes, how? > >[DEBUG] Error looking up lifecycle mapping to retrieve >optional mojos. Lifecycle ID: default. Error: > Component descriptor cannot be found in the component >repository: org.apache.maven.lifecycle.mappin >g.LifecycleMappingtigerstripe-application. >org.codehaus.plexus.component.repository.exception.ComponentLoo >kupException: Component descriptor ca nnot be found in the >component repository: >org.apache.maven.lifecycle.mapping.LifecycleMappingtigers >tripe-application. >at >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus >Container.java:323) >at >org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus >Container.java:440) >at >org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona >lMojosForLifecycle(Default >LifecycleExecutor.java:1106) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc >leForPackaging(DefaultLife >cycleExecutor.java:994) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi >fecycleMappings(DefaultLif >ecycleExecutor.java:975) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal >(DefaultLifecycleExecutor. >java:453) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal >AndHandleFailures(DefaultL >ifecycleExecutor.java:306) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask >Segments(DefaultLifecycleE >xecutor.java:273) >at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def >aultLifecycleExecutor.java >:140) >at >org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso >rImpl.java:39) >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho >dAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:585) >at >org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at >org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > >My plugins component.xml: > > > > >org.apache.maven.lifecycle.mapping.LifecycleMapping > tigerstripe-application > >org.apache.maven.lifecycle.mapping.DefaultLifec >ycleMapping > > > >ossj.jsr264:maven-tigerstripe-plugin:tigerstr >ipe-generate > >org.apache.maven.plugins:maven-source-plugin:jar > >org.apache.maven.plugins:maven-install-plugin:install< >/install> > > > > > >org.apache.maven.artifact.handler.Artif
I'm looking for a simple aspectJ example with mvn
Hi. I've used eclipse and the aspecJ plugin successfully to create some simple aspects. Did work except that the ide source code verifier didn't recognize all aspects but it compiled fine. In the end I think packaging is more important than eclipse and now I want to know how to do things with mvn only. I've found the maven-aspectJ-plugin which can weave apsectJ-libraries into .jar files. Fine. How do I create those aspectJ-libraries? Is the aspectJ compiler a module from mvn or do I have to install it seperately as the java-sdk? Is the default maven-compiler-plugin capable of compiling apsects? Another related question: Do you already use aspects in production systems? Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Standard Directory Layout
On 6/10/06, Max Cooper <[EMAIL PROTECTED]> wrote: wolverine my wrote: > The src/main/resources directory contains only the configurations > which will be loaded by the classloader? So we really need to study > the 3rd party library configurations to see if they are loaded via the > classloader... Do you want the files to end up in WEB-INF/classes (i.e. loaded from classpath) or just WEB-INF (or some other directory, relative to webapp root)? Maven doesn't really complicate things much here, since you have to make those choices anyway. You don't need to look at the source code of the component that does the loading in most cases. > > What should the src/main/config contains? > Nothing that I am aware of. > Typicaly we have the scripts to start application or server, and > scripts for utilities (backup, housekeeping), and what do you think if > we save these scripts in /src/main/bin directory? Or do we save these > scripts into difference directories? src/main/bin sounds reasonable. You'll probably need to (eventually) consider how you want these files to end up in a build artifact, and then how you are going to tell maven to find them. You can also create 2 modules, one for your webapp, one for your whole distribution, and move all resources non required to create/test your webapp into the distribution package, e.g. under src/main/resources. I usually have something like src/main/resources/bin src/main/resources/conf src/main/resources/lib etc... and use the assembly plugin to bundle everything together. Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie archetype question
Mike, I have used maven for a couple of webapps, usally I use the webapp archetype to generate the pom and initial structure then I create the java directory manually. Once you have created them maven will compile the jva source as normal, and the class files get moved to the correct place in the produced war. I dont know of a archtype that does this for you, but that dosent mean there isn't one. Also I have created a project that has a webapp module and a java module. For this I used the quick start archetype to create the jar module, and the webapp to create the webapp module. I then moved the out directory's produced under a project directory and created the project pom manually. I hope this is of some help... Ben On 6/10/06, Mike Lundin <[EMAIL PROTECTED]> wrote: Ben, I was assuming that there was an archetype out there that would generate that structure for me. Is that not the case? Mike On 6/9/06, ben short <[EMAIL PROTECTED]> wrote: > > Mike, > > You can just create the directorys you need from the link .. > > > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > > Or you can create a seperate project that has the java source and add > it as a dependacy of your webapp. > > > > Ben > > On 6/10/06, Mike Lundin <[EMAIL PROTECTED]> wrote: > > I'm working on creating a new webapp project using maven and the > > archetype:create with the maven-archetype-webapp archetype. I may not > > understand things correctly, but I don't see some directories that I > would > > assume would be in there. There is nothing for Java src files or > anything > > like that in there. > > > > Should those be in there, or is the preferred method to created multiple > > maven projects and make them all dependencies on each other? I tried > > creating archetypes within archetypes (by changing package to pom), but > that > > seem to disregard the archetype I sent in and only ever used the > quickStart > > archetype. > > > > Any help on this would be greatly appreciated -- and feel free to point > me > > to a URL that has more information. I've looked through the resources I > > know and am not finding anything definitive. > > > > Thanks much, > > Mike > > > > > -- Mike Lundin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
