AW: AW: installing sources to local repository by means of install plugin
Hi Jochen sorry for bugging you but I also tried it out without the generatePom=true option, and it always turns my "myArtifactId-myVersion-sources.jar" into "myArtifactId-myVersion.jar" once I import it into the repository as described below (without generatePom) ... Simon -Ursprüngliche Nachricht- Von: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 24. August 2006 11:24 An: Maven Users List Betreff: Re: AW: installing sources to local repository by means of install plugin Gunzenreiner Simon wrote: > I tried to use install:install-file like this: > > mvn install:install-file -DgeneratePom=true -Dpackaging=jar > -DgroupId=myGroupId -Dversion=myVersion -DartifactId=myArtifactId > -Dclassifier=sources -Dfile=myArtifactId-myVersion-sources.jar > > but it didn't install my sources.jar correctly - the binary jar file was > simply replaces. It looks to me like the classifier option is not really > supported .. Classifier works, believe me. I'd guess that the "generatePom=true" is a problem. Jochen - 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]
AW: installing sources to local repository by means of install plugin
Hi allan I tried to use install:install-file like this: mvn install:install-file -DgeneratePom=true -Dpackaging=jar -DgroupId=myGroupId -Dversion=myVersion -DartifactId=myArtifactId -Dclassifier=sources -Dfile=myArtifactId-myVersion-sources.jar but it didn't install my sources.jar correctly - the binary jar file was simply replaces. It looks to me like the classifier option is not really supported .. Thanks Simon -Ursprüngliche Nachricht- Von: Allan Ramirez [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 24. August 2006 02:48 An: Maven Users List Betreff: Re: installing sources to local repository by means of install plugin Hi Simon, classifier is also supported for the install:install-file goal, so it should do the same with the deploy:deploy-file goal. allan Gunzenreiner Simon wrote: > Hi all > > I am missing documentation about how to install sources packed by the source > plugin into the local repository. I want to avoid file copying because I > assume I should be able to do it with the install plugin. I assume that the > "sources" postfix is a dependency classifier, so I was hoping to be able to > use a "classifier" argument to the install:install-file plugin, as it is > possible with the deploy:deploy-file plugin. > > Any hints appreciatet, > Simon > > > - 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]
installing sources to local repository by means of install plugin
Hi all I am missing documentation about how to install sources packed by the source plugin into the local repository. I want to avoid file copying because I assume I should be able to do it with the install plugin. I assume that the "sources" postfix is a dependency classifier, so I was hoping to be able to use a "classifier" argument to the install:install-file plugin, as it is possible with the deploy:deploy-file plugin. Any hints appreciatet, Simon
AW: Problem with maven-ear-plugin?
Hi, Don't know whether it will help, but apparently you have to set true . My ear plugin config looks like this (I don't think you need the module section except for java client modules). org.apache.maven.plugins maven-ear-plugin EarContent true 1.4 winterthur.jackpot.sample sample-ejb-client Good luck, Simon -Ursprüngliche Nachricht- Von: Tom Cunningham [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 27. April 2006 15:44 An: users@maven.apache.org Betreff: Problem with maven-ear-plugin? Hi, I'm trying to build an ear in Maven 2 with the maven-ear-plugin.The problem I'm seeing is that the plugin is generating two different application.xml's and the one that gets stuck into the ear doesn't seem correct.The one that gets stuck into the ear doesn't give any entries for the ejbModules I have defined. My project has three dependencies and each should be a module in the application.xml.Here's what I have defined in my pom.xml : vfa facility-war 8.0 war vfa persistence provided 8.0 ejb vfa facility 8.0 ejb org.apache.maven.plugins maven-ear-plugin vfa facility / vfa facility-war vfa vfa persistence / When I run "maven install", I find an application.xml in the target directory that looks okay to me: http://java.sun.com/dtd/application_1_3.dtd";> facility-ear facility-8.0.jar facility-war-8.0.war vfa persistence-8.0.jar However, this isn't the application.xml that gets into the ear.The one going into the ear has no ejb modules defined. http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="ht tp://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com /xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";> Facility Prototype Facility Prototype facility-war-8.0.war /vfa Am I doing something wrong here? Is this a bug? - 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]
AW: Re: AW: AW: M2: Assembling modules in an ear
Hi But commons-lang is not a java client module in the j2ee sense, since it does not have a main classe to be executed as j2ee client. So it does not have to be listed in the application.xml (but just included in the ear - and this is what happens). Regards, Simon -Ursprüngliche Nachricht- Von: news [mailto:[EMAIL PROTECTED] Auftrag von Wojciech Gdela Gesendet: Donnerstag, 20. April 2006 09:40 An: users@maven.apache.org Betreff: Re: AW: AW: M2: Assembling modules in an ear Hello, >> 2) jar in the dependency and >> >> >> winterthur.jackpot.sample >> sample-ejb-client > > Add > > true > >> >> >> where the java client module is not added to the generated application.xml > > You see, this is false by default, another indication that this is not > the normal way to do things.. ;) What if we will talk about a normal jar (not ejb-client), for example commons-lang. When I add commons-lang dependency to my ejb project's pom.xml, I have to remeber to add also commons-lang javaModule to ear project's pom.xml. Shouldn't this be handled by transitive dependencies? -- Best regards, Wojciech Gdela. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: M2: Assembling modules in an ear
I got it all working, the true helped, maybe something for the docs on http://maven.apache.org/plugins/maven-ear-plugin/howto.html. I don't want to be too pedantic, but regarding this >> I have my client >> interfaces in a separate project (and I think as long as deployed in the >> same ear and referenced through Class-Path this is still ok with the >> spec ..). > No it is not. The spec says that ejb modules must have impl + api > in the same jar. But you can try, maybe your container doesn't honor the > spec :) this is what I found in the spec (EJB 3 19.3): The ejb-jar file must contain, either by inclusion or by reference, the class files of each enterprise bean as follows: • The enterprise bean class. • The enterprise bean business interfaces, web service endpoint interfaces, and home and component interfaces. We say that a jar file contains a second file “by reference” if the second file is named in the Class-Path attribute in the Manifest file of the referencing jar file or is contained (either by inclusion or by reference) in another jar file that is named in the Class-Path attribute in the Manifest file of the referencing jar file. Thanks a lot, Simon -Ursprüngliche Nachricht- Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 19. April 2006 19:05 An: Maven Users List Betreff: Re: AW: AW: M2: Assembling modules in an ear On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: > That has helped a lot - was not aware of the in . > > Regarding not having to include ejb-client: I think > generateClient is false for the ejb goal. Anyway, I have my client > interfaces in a separate project (and I think as long as deployed in the > same ear and referenced through Class-Path this is still ok with the > spec ..). No it is not. The spec says that ejb modules must have impl + api in the same jar. But you can try, maybe your container doesn't honor the spec :) > So I tried with to add my client module with either > 1) ejb-client in the dependency, and get >Missing: >-- >1) > winterthur.jackpot.sample:sample-ejb-client:ejb-client:client:1.0-SNAPSHOT That can be right - you don't have an artifact with that type. You need generateClient=true in an ejb-packaging project for that. I first started out by separating the client classes from the bean classes, but soon had to merge them. I think you will have to do that too after you find out that your beans don't work.. > 2) jar in the dependency and > > > winterthur.jackpot.sample > sample-ejb-client Add true > > > where the java client module is not added to the generated application.xml You see, this is false by default, another indication that this is not the normal way to do things.. ;) > > Any ideas? Thanks a lot again. No problem! -- Kenney > > Simon > > > > -Ursprüngliche Nachricht- > Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 19. April 2006 18:18 > An: Maven Users List > Betreff: Re: AW: M2: Assembling modules in an ear > > > On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: > > > Hi Kenny > > > > Thanks a lot. I removed the config, and set > > generateApplicationXml to true. Please find my pom.xml attached. Now the > > ear is created with the dependent libraries, but the generated > > application.xml is simply > > > > > > > "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" > > "http://java.sun.com/dtd/application_1_3.dtd";> > > > > sample > > > > > > I expected it to list my ejb module. > > Ok. > > Normal 'jar' dependencies are NOT added to the EAR by default; for those > you need to specify a (and add them as a > dependency). > > Next, you don't seem to add any J2EE jars at all - the dependencies > don't specify a tag. If you want to include a .war you have > to specify war for the dependency. If you want to include > an ejb archive you need to specify ejb. > > You should NOT include any ejb-client (ejb-client) > dependencies: if you have a project with ejb, > the contents of the ejb-client version are already present in the > main ejb artifact. That is a J2EE requirement: the bean implementations > and the local/home/remote interfaces should all be in one jar. > > That said, I don't think you'll need to include any jars at all. > > Hope this helps a bit! > > -- Kenney > > > > > > Thanks, > > Simon > > > > -Ursprngliche Nachricht- > > Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 19. April 2006 17:41 > > An: Maven Us
AW: AW: M2: Assembling modules in an ear
That has helped a lot - was not aware of the in . Regarding not having to include ejb-client: I think generateClient is false for the ejb goal. Anyway, I have my client interfaces in a separate project (and I think as long as deployed in the same ear and referenced through Class-Path this is still ok with the spec ..). So I tried with to add my client module with either 1) ejb-client in the dependency, and get Missing: -- 1) winterthur.jackpot.sample:sample-ejb-client:ejb-client:client:1.0-SNAPSHOT 2) jar in the dependency and winterthur.jackpot.sample sample-ejb-client where the java client module is not added to the generated application.xml Any ideas? Thanks a lot again. Simon -Ursprüngliche Nachricht- Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 19. April 2006 18:18 An: Maven Users List Betreff: Re: AW: M2: Assembling modules in an ear On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: > Hi Kenny > > Thanks a lot. I removed the config, and set generateApplicationXml > to true. Please find my pom.xml attached. Now the ear is created with the > dependent libraries, but the generated application.xml is simply > > >"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" > "http://java.sun.com/dtd/application_1_3.dtd";> > > sample > > > I expected it to list my ejb module. Ok. Normal 'jar' dependencies are NOT added to the EAR by default; for those you need to specify a (and add them as a dependency). Next, you don't seem to add any J2EE jars at all - the dependencies don't specify a tag. If you want to include a .war you have to specify war for the dependency. If you want to include an ejb archive you need to specify ejb. You should NOT include any ejb-client (ejb-client) dependencies: if you have a project with ejb, the contents of the ejb-client version are already present in the main ejb artifact. That is a J2EE requirement: the bean implementations and the local/home/remote interfaces should all be in one jar. That said, I don't think you'll need to include any jars at all. Hope this helps a bit! -- Kenney > > Thanks, > Simon > > -Ursprngliche Nachricht- > Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 19. April 2006 17:41 > An: Maven Users List > Betreff: Re: M2: Assembling modules in an ear > > > On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: > > - Drop the compile - it's the default anyway, and not > needed for compilation of the ear > > - the modules section is only needed for modules that need special > configuration, like a war module usually gets a contextRoot > > - do you provide your own application.xml somewhere or do you use the > GenerateApplicationXmlMojo? > > - Did you specify the configuration at the global level or in executions? > > If you could paste your plugin configuration in the mail, that would be > helpful. > > -- Kenney > > > I am trying to create an ear by assembling multiple other projects in Maven > > 2.0.4. My ear config files are located in a separate project with > > ear. All dependent projects are listed as > > with scope compile. In addition, I added the > > configuration as described here: > > http://maven.apache.org/plugins/maven-ear-plugin/howto.html. > > > > I am facing two problems now: > > - I get an Error message if I add my EJB project to the list: > > Artifact[myGroupId:sample-ejb:ejb] is not a dependency of the project. > > although I added this project to the dependency list as well as to the > > module list. > > - Java (client) modules are not added to the generated application.xml > > > > Any hints really appreciated. > > > > Thanks > > Simon > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: M2: Assembling modules in an ear
Hi Kenny Thanks a lot. I removed the config, and set generateApplicationXml to true. Please find my pom.xml attached. Now the ear is created with the dependent libraries, but the generated application.xml is simply http://java.sun.com/dtd/application_1_3.dtd";> sample I expected it to list my ejb module. Thanks, Simon -Ursprüngliche Nachricht- Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 19. April 2006 17:41 An: Maven Users List Betreff: Re: M2: Assembling modules in an ear On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: - Drop the compile - it's the default anyway, and not needed for compilation of the ear - the modules section is only needed for modules that need special configuration, like a war module usually gets a contextRoot - do you provide your own application.xml somewhere or do you use the GenerateApplicationXmlMojo? - Did you specify the configuration at the global level or in executions? If you could paste your plugin configuration in the mail, that would be helpful. -- Kenney > I am trying to create an ear by assembling multiple other projects in Maven > 2.0.4. My ear config files are located in a separate project with > ear. All dependent projects are listed as > with scope compile. In addition, I added the > configuration as described here: > http://maven.apache.org/plugins/maven-ear-plugin/howto.html. > > I am facing two problems now: > - I get an Error message if I add my EJB project to the list: > Artifact[myGroupId:sample-ejb:ejb] is not a dependency of the project. > although I added this project to the dependency list as well as to the > module list. > - Java (client) modules are not added to the generated application.xml > > Any hints really appreciated. > > Thanks > Simon > > - > 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] 4.0.0 winterthur.jackpot.sample sample ear 1.0-SNAPSHOT winterthur.jackpot jp-base 5.0.1 winterthur.jackpot.sample sample-ejb-client-view 1.0-SNAPSHOT winterthur.jackpot.sample sample-ejb 1.0-SNAPSHOT winterthur.jackpot.sample sample-ejb-client 1.0-SNAPSHOT org.apache.maven.plugins maven-ear-plugin EarContent true - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2: Assembling modules in an ear
I am trying to create an ear by assembling multiple other projects in Maven 2.0.4. My ear config files are located in a separate project with ear. All dependent projects are listed as with scope compile. In addition, I added the configuration as described here: http://maven.apache.org/plugins/maven-ear-plugin/howto.html. I am facing two problems now: - I get an Error message if I add my EJB project to the list: Artifact[myGroupId:sample-ejb:ejb] is not a dependency of the project. although I added this project to the dependency list as well as to the module list. - Java (client) modules are not added to the generated application.xml Any hints really appreciated. Thanks Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Maven2: Class-Path from dependencies for EJB packaging
Found the solution myself. Had to add org.apache.maven.plugins maven-ejb-plugin true to the build section. Pitty though that this is not the default ... Thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2: Class-Path from dependencies for EJB packaging
Hi I am building a ejb project (with WTP project layout), which has provided and compile dependencies. I was expecting the compile dependencies to be included in the ejb jar files manifest Class-Path - but that didn't happen. Acutally, there was no Class-Path attribute generated at all. Does m2 not support Class-Path attribute generation from the dependency list, or is a special configuration needed? Thanks a lot, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bug database?
Does anyone know whether there is something like a bug database for maven? I would like to report some missing features / bugs that I find while working with maven ... Thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-jalopy-plugin incorrect java:compile prereq ?
Hello I want to format my java code before it get's compiled. I therefore call jalopy:format in a preGoal for java:compile. But I notice that the jalopy:format has the java:compile as a prerequisite: My question now: Does this make sense at all and how could I achieve my goal? Tanks a lot, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
