Re: Maven 2 inheritance which elements get inherited ?
Thanks i did that too but the profiles were missing so i wanted to be sure and asked here. Thanks for your help. Jörg Schaible-2 wrote: Hi kuku, kukudas wrote at Mittwoch, 28. Januar 2009 15:20: Thanks, so when i activate a profile by using the command line (ex.: mvn clean install -P int) within a child and the profile (int) is definied in the parent it should work right? Yes, but why don't you simply setup two minimal POMs and use mvn effetive:pom to explore the results ? - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Maven-2-inheritance-which-elements-get-inherited---tp21701498p21722535.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How do i use maven in my development environment
Hi, i m new to maven and have been asked to set up new development environment in my office. Mine is a small office of 8-10 developers. Till now we have CVS on one of remote servers and app servers(TOMCAT 5.x) running on individual developer machine. we use Eclipse 3.3 as Java IDE. Al the developers commit their work respective works from their machines and we create WAR file of the application manually through ANT using build.xml file. Our application is a non-EJB application with the following folder structure. myApplication |-- CSS(folder) |-- images |-- java scripts(folder) |-- JSP(folder) |-- WEB_INF(folder) ||-- classes ||-- lib ||-- src || |-- com || |-- companyName || |-- applicationName || |-- Java files in their respective folders || || ||--struts-config.xml | |--build.xm |--build.properties In the new development environment, we need CVS on a remote server, and Maven doing the ANT thing automatically on week-ends. We need Maven to compile our project and package it to WAR file and deploy it at a specific location on the server. I have been reading Maven 2.0.9 documentation and other helping material from last 3-4 days, but couldn't figure out how to use it practically. Where to put my applications JAVA files, lib folder, JSP's, etc. Please help. -- View this message in context: http://www.nabble.com/How-do-i-use-maven-in-my-development-environment-tp21722621p21722621.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE : RE : maven / osgi / repositories
In your OSGI bundle project, you will use the maven-assembly-plugin to generate your OSGI bundle artifact (artifactId-version-classifier.jar) with: - configuration of the Manifest to specify specific OSGI information: plugin artifactIdmaven-assembly-plugin/artifactId configuration [...] archive manifest [...] /manifest /archive /configuration [...] /plugin - a classifier set in the assembly id of the assembly descriptor. To reference a dependence on a OSGI bundle, you should use the dependencies mechanism: dependencies [...] dependency groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version classifierosgi/classifier /dependency [...] /dependencies So you have in your repository: an artifact usable as simple library (the default artifact) and another one usable as a OSGI bundle. I never try a such configuration, but I imagine that it should work fine. ___ Christophe DENEUX / Capgemini Sud / Méditerranée Integration Architect / OW2 PEtALS Comitter www.capgemini.com http://www.capgemini.com/ Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE Join the Collaborative Business Experience ___ Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness. De: Henri Gomez [mailto:henri.go...@gmail.com] Date: mer. 28/01/2009 18:04 À: Maven Users List Objet : Re: RE : maven / osgi / repositories 2009/1/28 Deneux, Christophe christophe.den...@capgemini.com: Isn't the role of the classifier field ? instead of : groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version we could use : groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version classifierosgi/classifier Good but how do you specify such classifier in dependants projects ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Problems with release:prepare on the resolution of a dependency with test classifier
Sound's like a known issue: http://jira.codehaus.org/browse/SCM-406 hth, - martin On Wednesday 28 January 2009 Thiago Moreira (timba) wrote: Thank you Barrie! Now it is working fine BUT I'm getting a new error... [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label floggy-1.2.0... [INFO] Executing: svn --non-interactive copy --file /tmp/maven-scm-200887962.commit . https://floggy.svn.sourceforge.net/svnroot/floggy/tags/floggy-1.2.0 [INFO] Working directory: /home/tmoreira2020/projects/floggy/trunk-fr2536956 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svnroot/floggy/tags/floggy-1.2.0/eclipse-floggy-feature/pom.xml' already exists [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 22 seconds [INFO] Finished at: Wed Jan 28 00:24:11 PST 2009 [INFO] Final Memory: 9M/82M [INFO] That file don't exist! You can check the project structure here http://floggy.svn.sourceforge.net/viewvc/floggy/ Has anyone else experienced something like this?? Cheers On Tue, Jan 27, 2009 at 6:36 PM, Barrie Treloar baerr...@gmail.com wrote: On Wed, Jan 28, 2009 at 4:34 AM, Thiago Moreira (timba) tmoreira2...@gmail.com wrote: Ok, I took a look on the source code of the maven-release-plugin and there is no way to set the preparationGoals from the command line!!! The method mergeCommandLineConfig http://maven.apache.org/plugins/maven-release-plugin/xref/org/apache/ma ven/plugins/release/PrepareReleaseMojo.html#181 of the PrepareReleaseMojo class only merge the releaseVersions and developmentVersions properties. We have the same scenario that you have and we are using release fine. You may want to use dependency groupIdMYGROUP/groupId artifactIdMYARTIFACT/artifactId versionMYVERSION/version typetest-jar/type scopetest/scope /dependency type = test-jar instead of classifier = test. There are some wierd inconsistencies with this. Straight from our release page in our wiki: mvn release:prepare -Dmaven.scm.provider.cvs.implementation=cvs_native -DpreparationGoals=clean,install -Dusername=CVS_userid - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org signature.asc Description: This is a digitally signed message part.
Re: How do i use maven in my development environment
First, re-arrange your project like this : http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Then, you write your pom.xml (either look for examples, or let Maven generate your project with the command) : mvn archetype:generate Choose : 18: internal - maven-archetype-webapp (A simple Java web application) enter any groupId, artifactID, version (1.0-SNAPSHOT). And you'll get a simple project set up (with an pom.xml example). 2009/1/29 MacMohan manmohanaror...@gmail.com: Hi, i m new to maven and have been asked to set up new development environment in my office. Mine is a small office of 8-10 developers. Till now we have CVS on one of remote servers and app servers(TOMCAT 5.x) running on individual developer machine. we use Eclipse 3.3 as Java IDE. Al the developers commit their work respective works from their machines and we create WAR file of the application manually through ANT using build.xml file. Our application is a non-EJB application with the following folder structure. myApplication |-- CSS(folder) |-- images |-- java scripts(folder) |-- JSP(folder) |-- WEB_INF(folder) ||-- classes ||-- lib ||-- src || |-- com || |-- companyName || |-- applicationName || |-- Java files in their respective folders || || ||--struts-config.xml | |--build.xm |--build.properties In the new development environment, we need CVS on a remote server, and Maven doing the ANT thing automatically on week-ends. We need Maven to compile our project and package it to WAR file and deploy it at a specific location on the server. I have been reading Maven 2.0.9 documentation and other helping material from last 3-4 days, but couldn't figure out how to use it practically. Where to put my applications JAVA files, lib folder, JSP's, etc. Please help. -- View this message in context: http://www.nabble.com/How-do-i-use-maven-in-my-development-environment-tp21722621p21722621.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE : RE : maven / osgi / repositories
Good idea. Did you have sample pom.xml for study ? Thanks Christophe 2009/1/29 Deneux, Christophe christophe.den...@capgemini.com: In your OSGI bundle project, you will use the maven-assembly-plugin to generate your OSGI bundle artifact (artifactId-version-classifier.jar) with: - configuration of the Manifest to specify specific OSGI information: plugin artifactIdmaven-assembly-plugin/artifactId configuration [...] archive manifest [...] /manifest /archive /configuration [...] /plugin - a classifier set in the assembly id of the assembly descriptor. To reference a dependence on a OSGI bundle, you should use the dependencies mechanism: dependencies [...] dependency groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version classifierosgi/classifier /dependency [...] /dependencies So you have in your repository: an artifact usable as simple library (the default artifact) and another one usable as a OSGI bundle. I never try a such configuration, but I imagine that it should work fine. ___ Christophe DENEUX / Capgemini Sud / Méditerranée Integration Architect / OW2 PEtALS Comitter www.capgemini.com http://www.capgemini.com/ Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE Join the Collaborative Business Experience ___ Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness. De: Henri Gomez [mailto:henri.go...@gmail.com] Date: mer. 28/01/2009 18:04 À: Maven Users List Objet : Re: RE : maven / osgi / repositories 2009/1/28 Deneux, Christophe christophe.den...@capgemini.com: Isn't the role of the classifier field ? instead of : groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version we could use : groupIdorg.apache.ant/groupId artifactIdant/artifactId version1.7.1/version classifierosgi/classifier Good but how do you specify such classifier in dependants projects ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Assemblies
Hi David, Thanks for your help. I kept seeing the assembly file referenced, but nothing too much on where it should be. http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html) Isn't this enough ? Or do i misunderstand things ? There are two issues I am having: 1). In the tarball, the lib directory is owned by build/user, but the bin and conf directory is owned by 0/0. Is there a way to set this? I didn't see anything in the Assembly settings. http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_fileSet You should take a look at the filemode ... Hm. under which user are you running maven ? 2). My boss wants to know why is the assembly file called bin.xml. I told him because the assembly file is a bin type, and you name the assembly file after the assembly type. He wants to see documentation to this effect. Is there such documentation? I know you can call your assembly file anything you want, but if this is the Maven standard, I want to stick with it. First you can call it the way you like but there are some defaults in there http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html#descriptorRefs Or in Maven: The definitive Guid at section Predefined Assembly Descriptors...you can see things linke bin are referenced... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse CTRL-SHIFT-T Open Type dialog is missing
2009/1/28 Lincoln Baxter, III lincolnbax...@gmail.com: Hi Mavenites, When I install the m2eclipse plugin, version 0.9.6, my Open Type dialog box disappears. I can't bring it up with a shortcut. The menu item is gone. It's just missing. Is this intentional? I really rely on this dialog quite a bit. How can I get it back? Hi, I had the same issue and In my case restoring default shortcuts in Eclipse Preferences solved this problem Cheers Matthew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype create v. generate
Hi Dave,create is deprecate, generate is a way to go. If you want it not interactive, read: http://maven.apache.org/plugins/maven-archetype-plugin/examples/generate-batch.html HTH, Hubert. On Tue, Jan 27, 2009 at 9:03 PM, Dave Newton newton.d...@yahoo.com wrote: Just a ping to see if anybody had any input--I haven't had a chance to investigate further yet but need to commit some changes to some archetypes and update some documentation soon. Thanks, Dave Dave Newton wrote: What's the approved way to create archetypes when there's an archetype metadata file? So far it seems like I can either do archetype:create, which (so far) isn't shuffling the files around from my archetype metadata file, or archetype:generate, which does, but has that interactive bit I'd like to avoid. I think I'm using Version: 2.0-alpha-4, which is actually different from the one I *thought* I was using, so I'll re-visit my process and see what's currently happening, but I'd still appreciate any input. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Hubert Iwaniuk
Re: m2eclipse CTRL-SHIFT-T Open Type dialog is missing
Thanks! You nailed it. For some reason the Maven plugin disabled my Perspective - Customize - Commands - Java Open Type option. Happier... --Lincoln On Thu, 2009-01-29 at 12:53 +0100, Mateusz Grzechociński wrote: 2009/1/28 Lincoln Baxter, III lincolnbax...@gmail.com: Hi Mavenites, When I install the m2eclipse plugin, version 0.9.6, my Open Type dialog box disappears. I can't bring it up with a shortcut. The menu item is gone. It's just missing. Is this intentional? I really rely on this dialog quite a bit. How can I get it back? Hi, I had the same issue and In my case restoring default shortcuts in Eclipse Preferences solved this problem Cheers Matthew
Plugin calling shell script
Hello, I have written a plugin that uses Wagon to remotely execute a command on a remote machine. But now I find that instead of executing a simple unix command, I need to execute a whole shell script. So I created a shell script and placed it in src/main/resources, so that it correctly gets bundled in the root of my plugin jar. However, the problem is that how do users of my plugin get at that shell script. My users have configured my plugin in their poms. The corporate maven repo holds my plugin jar also. But when they run the mvn command, and my plugin is dutifully downloaded from the corporate maven repo to their local repo. From there, however, things don't work. The plugin cannot find the shell script because altho the shell script is in the plugin jar (in their local repo), it is not in the classpath of the maven execution. So how do I invoke a shell script that is bundled as a part of the plugin? I even tried URL url = MultiplexerMojo.class.getResource(sql.bash); but url evaluates to null because sql.bash is not found (because the plugin jar is not in the cp). Is there anyway I can use plexus to inject the sql.bash into my plugin? Or somehow add to the classpath that is examined by maven ? Any help will be much appreciated! Thanks, Pankaj -- View this message in context: http://www.nabble.com/Plugin-calling-shell-script-tp21727380p21727380.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin calling shell script
What about packaging another jar which holds your script (s) (e.g. mojo-scritps.jar) and add this in the specific plugin dependencies section, something like: plugin dependencies dependency artifactIdmojo-scripts.jar/artifactId /dependency /dependencies /plugin Would this solve your problem? (not sure if I completely understood the problem) HTH, Gab 2009/1/29 Pankaj Tandon pankajtan...@gmail.com Hello, I have written a plugin that uses Wagon to remotely execute a command on a remote machine. But now I find that instead of executing a simple unix command, I need to execute a whole shell script. So I created a shell script and placed it in src/main/resources, so that it correctly gets bundled in the root of my plugin jar. However, the problem is that how do users of my plugin get at that shell script. My users have configured my plugin in their poms. The corporate maven repo holds my plugin jar also. But when they run the mvn command, and my plugin is dutifully downloaded from the corporate maven repo to their local repo. From there, however, things don't work. The plugin cannot find the shell script because altho the shell script is in the plugin jar (in their local repo), it is not in the classpath of the maven execution. So how do I invoke a shell script that is bundled as a part of the plugin? I even tried URL url = MultiplexerMojo.class.getResource(sql.bash); but url evaluates to null because sql.bash is not found (because the plugin jar is not in the cp). Is there anyway I can use plexus to inject the sql.bash into my plugin? Or somehow add to the classpath that is examined by maven ? Any help will be much appreciated! Thanks, Pankaj -- View this message in context: http://www.nabble.com/Plugin-calling-shell-script-tp21727380p21727380.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Gabriele Columbro Alfresco ECM Product Strategy Consultant +31 627 565 103 Sourcesense - Making sense of open Source (http://www.sourcesense.com)
Snapshots not being updated?
I have a SNAPSHOT artifact (foo.bar) who has a dependency of: dependency groupIdsaxon/groupId artifactIdsaxon/artifactId version9/version /dependency I changed the group for saxon (internal repo) and changed the SNAPSHOT to depend on dependency groupIdnet.sf/groupId artifactIdsaxon/artifactId version9/version /dependency Above this project I had another artifact that used this as a dependency. dependency groupIdfoo/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version /dependency Before I changed saxon's groupId I had packaged this project and was able to pull down bar SNAPSHOT w/ saxon.saxon as it's dependency. That's fine. I redeployed saxon as net.sf.saxon and then redeployed foo.bar with an updated pom that reflected this groupId change (it is showing correctly in my nexus repo). But when I rerun my project it still pulls the old foo.bar that wants saxon in the saxon group. Even a snapshot-policy and -U doesn't force it to regrab the SNAPSHOT. Anyone know what is causing this behavior? -- Bill Cosby - A word to the wise ain't necessary - it's the stupid ones that need the advice.
How to refer to SNAPSHOT timestamp from Web site
Hello,
I'm creating a project Web site using the Maven site plugin. The project is
currently in a SNAPSHOT state, that is, the assembly that I create (and
artifacts) have a timestamp suffix attached to their file name when the get
deployed to some Maven repository.
Assuming that the build process runs mvn deploy site-deploy I would like
the Web site to render the link referring the the current assembly file,
i.e., using the current snapshot timestamp. How can this be achieved? Is
there a property like ${timestamp} that I could use to get the current
value?
Thanks,
Thorsten
--
View this message in context:
http://www.nabble.com/How-to-refer-to-SNAPSHOT-timestamp-from-Web-site-tp21730328p21730328.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype create v. generate
Hubert Iwaniuk wrote: Hi Dave,create is deprecate, generate is a way to go. If you want it not interactive, read: http://maven.apache.org/plugins/maven-archetype-plugin/examples/generate-batch.html HTH, It does--thanks much! Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
nexus can't find maven-archetype-plugin?
hi, i'm playing around with nexus as repository manager and now have a little problem: the maven-archetype-plugin can't be found. most of the other plugins work maven uses the standard public repository group in nexus. what do i have to do for being able to use em all??? -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven / osgi / repositories
On 27-Jan-09, at 6:41 PM, Barrie Treloar wrote: repositories. They might become OBRs at some point when OSGi becomes more mainstream. One thing I have been toying with for a while is to auto-magically extend maven-jar-plugin to add the OSGi headers. I really don't think this is a great idea. I think for a bundle to be useful someone needs to provide proper imports and exports. I haven't given a lot of thought into what I need to do, but if I recall correctly, getting a simple OSGified jar isn't much work and if Maven did this out of the box then the maven repository would become OSGified over time as projects release their artifacts. We've toyed around with this idea, but if you want something useful I think it's really hard to infer something useful. Making a manifest that is workable with OSGi is not that hard and the author of a package is probably the person to do it. I think what we can do is give a brief guideline as to what's commonly expected and help people create correct and useful bundles. Maven central is the biggest bundle repository in waiting :-) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Dependent jars not included in package
I'm trying to include jars inside jars.. From: Morgovsky, Alexander (US - Glen Mills) [mailto:amorgov...@deloitte.com] Sent: Sunday, January 25, 2009 3:53 AM To: Jude Prakash (WT01 - Communication and Media) Cc: users@maven.apache.org Subject: Dependent jars not included in package If you are creating a jar, are you trying to include jars in your jars, or are you creating a war or ear or other object? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Maven Assemblies
On Thu, Jan 29, 2009 at 5:37 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi David, Thanks for your help. I kept seeing the assembly file referenced, but nothing too much on where it should be. http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html) Isn't this enough ? Or do i misunderstand things ? That was handy, but when you're reading what is suppose to be the definitive Maven reference book on Assemblies, and the book doesn't mention whether or not the Assembly file is suppose to be a separate file or where it is stored... Well, you can see why I can get frustrated. There may be a lot of information about Maven out there, but it can be difficult to track down. For example, I spent hours on the distribution plugin: http://maven.apache.org/maven-1.x/plugins/dist/goals.html which I found doing a Google search. I just couldn't get it to work. I finally decided that maybe I have to put the plugin into my local repository, went to the download page and suddenly realized not one of those links points to a downloadable distribution plugin file. Each one was one 404 error after another. (Yes, I now realize that this is a Maven 1.x plugin). When I went up the Maven web page hierarchy, I discovered that this plugin was not listed. http://maven.apache.org/plugins/index.html. So, I then looked at the Packaging Types/Tools since a tarball is a type of package. I then played with the shade type since it says this is an Uber-Jar, I thought maybe that's a way to package things instead of using tarballs or zip files. Spent another few hours playing with that. It took me a while to realize what I wanted to do was to create an Assembly. It is certainly difficult to look at the description of an Assembly on Maven's plugin page to realize that this would be a tool you need in order to actually build a tarball or zip file. It isn't even listed under packaging tools. However, once I realized I wanted to create an Assembly, I could start reading the chapter on Assemblies in Maven -- The Definitive Guide. But as I mentioned above, the book doesn't seem to mention where assembly files are stored or even if they are a separate file from your POM. It isn't that I am new at using open source software world. Nor, do I expect to be trained or have people do my work for me. But, Maven is an extremely complex piece of software and the documentation is not well organized. Take a look at Subversion. One of the reasons Subversion has done so well is that it has excellent documentation. The definitive Subversion book isn't merely a reference, but a well written step-by-step manual explaining how Subversion is used. It then goes through administration, explaining possible gotchas, and gives some nice examples. The FAQ section is quite clear. Ant's documentation isn't quite as nice, but at least it gives some nice examples on how the various tasks are used. It took me a while to learn Ant, but I was able to through the web page. Plus, there are a lot of excellent books on Ant. The whole purpose of Maven was to eliminate the need for me, the CM, to do the build scripting. I've spent most of my career writing or helping developers to write makefiles and later on Ant build scripts. Most of the time, it falls on me to do this type of work. Maven was suppose to be a way for developers not to worry about how builds happen because Maven will take care of it. Now, I am sitting around and writing Maven POMs for my developers. And, because the way Maven works, I now have to fiddle with the source code, something I didn't have to do with Ant and Makefiles. Our developers hate Maven and simply find it incomprehensible. Here's the latest request from one of our developers: Thanks for arranging the folder structure to generate deployable artifact as per requirement. We have taken latest code from SVN. We need following change in generated 'target' folder when we run the 'mvn compile' command. 1) Generated 'target' folder contains 'test-classes'. But some of the test cases are failing because they have dependency on 'conf' and 'data' folders. Can you please modify the maven script such a way that it will put 'conf' and 'data' into 'target\test-classes\' Why in the F in RFTM am I responsible for this? I was doing this for developers in Ant build.xml files. Maven is suppose to take me out of the picture! So, please understand my frustration. I am not a developer, and this is the first time I am working with Maven. Once you get the hang of everything in Maven, it might be easier to understand and tweak things the way you want. But, Maven is a difficult piece of software to understand, and the documentation for Maven is still in a rather preliminary state. There are two issues I am having: 1). In the tarball, the lib directory is owned by build/user, but the bin and conf directory is owned by 0/0. Is there a way to set this? I didn't see anything in the Assembly
Re: maven / osgi / repositories
One thing I have been toying with for a while is to auto-magically extend maven-jar-plugin to add the OSGi headers. I really don't think this is a great idea. I think for a bundle to be useful someone needs to provide proper imports and exports. Right, but it make took years ;( I haven't given a lot of thought into what I need to do, but if I recall correctly, getting a simple OSGified jar isn't much work and if Maven did this out of the box then the maven repository would become OSGified over time as projects release their artifacts. We've toyed around with this idea, but if you want something useful I think it's really hard to infer something useful. Making a manifest that is workable with OSGi is not that hard and the author of a package is probably the person to do it. I think what we can do is give a brief guideline as to what's commonly expected and help people create correct and useful bundles. Maven central is the biggest bundle repository in waiting :-) So you recommand education and lobbying. May be ASF should show the way, there is tons of projects today still not OSGIfied in ASF repo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Ecosystem Component Categories/Acronyms
What is a good generic term and acronym for Nexus? Would it be repository manager / rm What about repo browsers (viewvc, fisheye)? examples: source code management - scm continuous integration - ci issue management system - ims I'm trying to set up friendly URLs and dns redirects for use in development. e.g. http://scm.someteam.somecompany.com/svn/ points to our svn repo, http://ci.someteam.somecompany.com/hudson/ points to our Hudson instance Luke -- View this message in context: http://www.nabble.com/Ecosystem-Component-Categories-Acronyms-tp21731367p21731367.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven / osgi / repositories
I think what we can do is give a brief guideline as to what's commonly expected and help people create correct and useful bundles. Clearing up the version vs. classifier issue would be a good first step. From: Jason van Zyl [mailto:jvan...@sonatype.com] Sent: Tue 1/27/2009 10:43 PM To: Maven Users List Subject: Re: maven / osgi / repositories On 27-Jan-09, at 6:41 PM, Barrie Treloar wrote: repositories. They might become OBRs at some point when OSGi becomes more mainstream. One thing I have been toying with for a while is to auto-magically extend maven-jar-plugin to add the OSGi headers. I really don't think this is a great idea. I think for a bundle to be useful someone needs to provide proper imports and exports. I haven't given a lot of thought into what I need to do, but if I recall correctly, getting a simple OSGified jar isn't much work and if Maven did this out of the box then the maven repository would become OSGified over time as projects release their artifacts. We've toyed around with this idea, but if you want something useful I think it's really hard to infer something useful. Making a manifest that is workable with OSGi is not that hard and the author of a package is probably the person to do it. I think what we can do is give a brief guideline as to what's commonly expected and help people create correct and useful bundles. Maven central is the biggest bundle repository in waiting :-) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Accessing release:prepare properties
I'd like to run the release:prepare goal in batch mode and override the default
scm tag name. Currently the default tag name seems to be
${artifactId}-${releaseVersion} where the releaseVersion is based on removing
SNAPSHOT from the current project version. I would like to change the tag to
be x-${releaseVersion} but I always get a null value for that property. Does
anyone know a) if the releaseVersion property is available and b) what the
correct property name is?
Thanks,
Bill
Accessing release:prepare properties
I'd like to run the release:prepare goal in batch mode and override the default
scm tag name. Currently the default tag name seems to be
${artifactId}-${releaseVersion} where the releaseVersion is based on removing
SNAPSHOT from the current project version. I would like to change the tag to
be x-${releaseVersion} but I always get a null value for that property. Does
anyone know a) if the releaseVersion property is available and b) what the
correct property name is?
Thanks,
Bill
RE: nexus can't find maven-archetype-plugin?
Little hard to diagnose with that info. How is your settings.xml setup? What repos are in your group? What exactly is maven saying (log)? We have a nexus user list where your questions will be noticed quicker: http://nexus.sonatype.org/dev/mailing-lists.html -Original Message- From: Jens Rapp [mailto:tec_la...@gmx.de] Sent: Wednesday, January 28, 2009 4:17 AM To: users@maven.apache.org Subject: nexus can't find maven-archetype-plugin? hi, i'm playing around with nexus as repository manager and now have a little problem: the maven-archetype-plugin can't be found. most of the other plugins work maven uses the standard public repository group in nexus. what do i have to do for being able to use em all??? -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problems with assembly
Greetings,
I am trying to use a top-level POM to assemble all the artifacts of
several modules into a single assembly for delivery (exactly what the
assembly plugin is for, I think). I've got it almost there, but I keep
running into a strange problem: [WARNING] The following patterns were
never triggered in this artifact inclusion filter
Specifically, for most of the modules, I use the moduleSet in the
following bin.xml:
assembly
idzip/id
formats
formatzip/format
/formats
moduleSets
moduleSet
includes
includecom.verdiem.polaris:api/include
includecom.verdiem.polaris:core/include
/includes
binaries
outputDirectorylib/outputDirectory
unpackfalse/unpack
/binaries
/moduleSet
/moduleSets
/assembly
This works great, with the following in the top-level POM:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assembly/bin.xml/descriptor
/descriptors
/configuration
/plugin
The file is there and everything is good and as expected.
However, one of the modules I need to build as a
jar-with-dependencies and include in a different part of the
assembly. To do that, I've got another module, extentions, with the
following:
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
idassemble-extension/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefjar-with-dependencies/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
When this is commented out in the extensions/pom.xml, everything
works (except for building the needed jar-with-deps). When it is not
commented out, I get the following error:
[INFO] [assembly:single {execution: assemble-extension}]
[INFO] Reading assembly descriptor: src/main/assembly/bin.xml
[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o 'com.verdiem.polaris:api'
o 'com.verdiem.polaris:core'
[WARNING] NOTE: Currently, inclusion of module dependencies may
produce unpredictable results if a version conflict occurs.
[INFO]
[ERROR] BUILD ERROR
My hope is that I can get the jar-with-dependencies built and then
included in the final assembly with a fileSet in the bin.xml.
I have also tried this using another module specifically for the final
assembly, but I cannot get the moduleSet to work in that module.
Any ideas on how I can get the assembly working?
Thanks,
- philion
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven / osgi / repositories
On Wed, Jan 28, 2009 at 2:13 PM, Jason van Zyl jvan...@sonatype.com wrote: On 27-Jan-09, at 6:41 PM, Barrie Treloar wrote: repositories. They might become OBRs at some point when OSGi becomes more mainstream. One thing I have been toying with for a while is to auto-magically extend maven-jar-plugin to add the OSGi headers. I really don't think this is a great idea. I think for a bundle to be useful someone needs to provide proper imports and exports. I haven't given a lot of thought into what I need to do, but if I recall correctly, getting a simple OSGified jar isn't much work and if Maven did this out of the box then the maven repository would become OSGified over time as projects release their artifacts. We've toyed around with this idea, but if you want something useful I think it's really hard to infer something useful. Making a manifest that is workable with OSGi is not that hard and the author of a package is probably the person to do it. I think what we can do is give a brief guideline as to what's commonly expected and help people create correct and useful bundles. Maven central is the biggest bundle repository in waiting :-) I agree it is sub-optimal. I think I would be suggesting a very broad approach. * OSGi bundle id matching group/artifactId combos. * exporting everything that is within the current artifact * wiring OSGi dependencies to match artifact dependencies probably without version ranges. Without thinking about it properly I think that would get people 80%-90% there with OSGi without having to re-wrap artifacts. I can't see how it will make things worse. This approach has some down sides * it exposes more than the author would expect * the dependencies may not yet be OSGified (but as they get released via maven that would get fixed) * OSGi headers may not be what the author would prefer (but they would be consistent with maven guidelines) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven eclipse work space resolution doesnot work
Hi all, I'm using eclipse maven (m2) plugin. I have a maven project which has a parent maven project and another maven project. But when I enable the work space resolution and run the project, I am getting a run time error that it cannot find the other dependent classes in other maven projects. So I have to disable the work space resolution to run the project (so it will copy the jars in to my lib). But when I need to debug, it is not possible as I cannot jump in to the code of other maven projects (or even to the parent project). How to solve this issue? Why the enable work space resolution does not work properly? Thanks in advance.
Maven for the internet afraid
Asking this embarrasses me, but must be done. I work for a company where the internet terrifies Them. They want to use Maven, but they think it should never go online, so they want a locked down internal repository containing whatever artifacts some couple hundred developers might need. Can we, as I believe, not effectively use Maven this way? If so, what are the alternatives? I see a few: 1. Only worry about the release bundle Compare dependency reports in continuous integration to some approved jar list, flagging anomalies along the way. Once ready for release, run some thorough check on the jar-with-dependencies. 2. wget all of Central A blunt instrument, but it would more or less work. How, though, do I go to the people who vet jars and say, Hey, someone might someday need some of these... 3. Build against some proxy repo for a while, then block it Obvious problems ensue. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven for the internet afraid
On Thu, Jan 29, 2009 at 9:27 PM, Merv Green paradeofh...@gmail.com wrote: Asking this embarrasses me, but must be done. I work for a company where the internet terrifies Them. They want to use Maven, but they think it should never go online, so they want a locked down internal repository containing whatever artifacts some couple hundred developers might need. Can we, as I believe, not effectively use Maven this way? It _can_ work, and it's actually a very good idea. You are not alone. :) Run a repository manager (Archiva, Nexus, Artifactory) internally, and tightly control its contents. Establish some process for developers to request uploads to the repo, and have the team responsible for that go through the motions of retrieving the artifacts, verifying the signatures, etc., then uploading. You can usually upload through the web interface of the repo manager. For larger uploads (a plugin and its bunch of dependencies) I've had good luck using the assembly plugin to package all the artifacts in remote repo format, then copying that into the managed repo. Where I am, a governance board controls open source and third party dependencies. They review the license as well as consider whether it's something that they want used within the development organization. Access to external repos is prevented by the settings.xml in our custom Maven distribution, so that everything builds against the approved artifacts in the internal repos. If there's a really huge new project coming on, you might configure a separate repo and let that proxy central for a while, then shut it down and go through everything it has proxied to determine what needs to be moved into the approved repo. HTH, -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Looking for a workaround for MNG-3228 (activate inherited profile)
Any idea? The main reason why we want to do this is to be able to have different types of projects. Each type has different pom settings which we want to maintain in a central place. At the moment we have a master pom per project type which limits us in combination with module builds as Maven doesn't support multiple inheritance at the moment (master pom+ module parent). That's why we want to implement profiles but don't know how to workaround MNG-3228. Any input highly appreciated! Thanks Stefan Original Message Subject: Looking for a workaround for MNG-3228 (activate inherited profile) Date: Wed, 28 Jan 2009 08:11:34 +0100 From: Stefan Fritz sfritz.nos...@gmx.at Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org References: 9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com 562346790901200455i39250a79vd311d152b3884...@mail.gmail.com 9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com Hi all, We try to define profiles in our master pom. When we trigger a build we want to activate a specific profile via a property in the projects pom. (activation via -P works fine). But it seems we ran into the following issue: http://jira.codehaus.org/browse/MNG-3228 Is there any workaround to be able to activate a profile (defined in a master pom) per project? Thanks Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
