Re: maven-dependency-plugin doesn't find all dependencies in several repositories
Nick Stolwijk-4 wrote: Because of this piece I think there is something wrong with the pom file of your Z artifact. Can you take a look in your local repository in the pom file of Z to see if the dependency is really compile? It shouldn't matter in which repo an artifact lives. In my pom.xml of Z there are just these two dependencies. dependencies dependency groupIdorg.apache/groupId artifactIdbatik/artifactId version1.0/version /dependency dependency groupIdorg.objectweb/groupId artifactIdasm/artifactId version1.5.3/version /dependency /dependencies That's my original part of Z's pom.xml. I never defined any scope in none of my pom.xmls and dependenxy:tree for Z also shows compile. I also don't have any pure snapshot-repository. This special repository is really only a release-repository. So it should work I think, shouldn't it? -- View this message in context: http://www.nabble.com/maven-dependency-plugin-doesn%27t-find-all-dependencies-in-several-repositories-tp23961970p24029230.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
No one here using OSGI + Maven? What about the plugin I found: http://mvn-dp-plugin.sourceforge.net/site/plugin-info.html Could that do the trick? Thanks, Peter
Re: Maven + OSGI
2009/6/15 Peter Horlock peter.horl...@googlemail.com No one here using OSGI + Maven? I'm sure there are several people here using OSGi + Maven (me for one) however, this doesn't sound like a general OSGi issue as such, because OSGi doesn't actually mandate a specific layout of bundles - instead your layout is specific to Equinox, the OSGi framework used by Eclipse (and therefore BIRT which is an Eclipse project) you could perhaps look into using the headless Eclipse/PDE build, but this can be painful to use - IMHO the best (and simplest) option is just use the assembly plugin to arrange everything What about the plugin I found: http://mvn-dp-plugin.sourceforge.net/site/plugin-info.html Could that do the trick? well that plugin generates standard OSGi deployment packages: http://www.osgi.org/javadoc/r4v41/org/osgi/service/deploymentadmin/DeploymentPackage.html which are a way to atomically install and update a collection of bundles, managed by the deployment admin bundle (so you need this installed) - while you can use this to deploy apps onto a framework it won't help you do the initial bootstrapping, so you'd still need to mimic some of the Equinox layout another option might be to use pax-runner to generate the Equinox layout: http://issues.ops4j.org/browse/PAXRUNNER-177 http://paxrunner.ops4j.org/space/Pax+Runner but I still think using the assembly plugin would be simplest approach initially Thanks, Peter -- Cheers, Stuart
Antwort: aspectj-maven-plugin
Hi, what kind of problems do you have? I´m using that plugin to weave some aspects in existing 3rdparty jars and that´s working. In your sample you dont have a dependencies section - but weaveDependencies to get the aspectj compiler satisfied, you need the dependencies too. Torsten Yanko, Curtis curt_ya...@uhc.com 04.06.2009 17:07 Bitte antworten an Maven Users List users@maven.apache.org An Maven Users List users@maven.apache.org Kopie Thema aspectj-maven-plugin Is anyone having any luck with this plugin? It seems pretty broken to me. I have scoured the web and can find little, if any documentation. It also seems as if the guy at anydoby.com re-wrote the plugin to work?! Here is what I have so far: plugin groupIdorg.codehaus.mojo/groupId artifactIdaspectj-maven-plugin/artifactId version1.1/version executions execution goals goalcompile/goal !-- use this goal to weave all your main classes -- goaltest-compile/goal !-- use this goal to weave all your test classes -- /goals /execution /executions configuration source1.5/source target1.5/target showWeaveInfotrue/showWeaveInfo verbosetrue/verbose outxmlfalse/outxml proceedOnErrortrue/proceedOnError includes include**/*.aj/include /includes !--excludes exclude**/logging/*.aj/exclude /excludes-- weaveDependencies weaveDependency groupIdorg.springframework/groupId artifactIdspring-aspects/artifactId /weaveDependency /weaveDependencies aspectLibrarys aspectLibrary groupIdorg.springframework/groupId artifactIdspring-aspects/artifactId /aspectLibrary /aspectLibrarys /configuration /plugin == Curtis Yanko Application Developer Infrastructure Services Source-Build-Deploy This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Tomcat Maven Plugin - 401 error
Thanks Oliver, but the explicit username/password configuration doesn't change
anything.
tomcat:run isn't a workable idea in the long-term, I need to get the tomcat
plugin working in its most basic form...
Can anyone else help?
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier
Lamy
Sent: 15 June 2009 00:20
To: Maven Users List
Subject: Re: Tomcat Maven Plugin - 401 error
Hi,
Perso, I'm using a configuration as this one:
configuration
...
username${tomcat.user}/username
password${tomcat.password}/password
/configuration
But if you are in a dev phase (working locally), you don't have to
deploy to a local tomcat instance just use : tomcat:run.
--
Olivier
2009/6/14 Dean Pullen dean.pul...@msp-uk.com:
Hi all,
Trying to deploy my first app to Tomcat using the Tomcat Maven Plugin.
I only ever seem to get this error however I configure the plugin:
[INFO] Deploying war to http://localhost:8080/suzcrmdata-web
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot invoke Tomcat manager
Embedded error: Server returned HTTP response code: 401 for URL:
http://localhost:8080/manager/deploy?path=%2Fsuzcrmdata-webwar=
My tomcat-users.xml file states:
tomcat-users
role rolename=manager/
role rolename=admin/
user username=admin password=admin roles=admin,manager/
/tomcat-users
My settings.xml states:
servers
server
idlocalserver/id
usernameadmin/username
passwordadmin/password
/server
/servers
My pom.xml states:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
configuration
serverlocalserver/server
path/suzcrmdata/path
warFileC:/Home/MSPDev/trunk/suzcrmdata/web/target/suzcrmdata-web-1.0-SNAPSHOT.war/warFile
/configuration
/plugin
I'm not sure why it tries to deploy using a null war param and also why it
tries to deploy to suzcrmdata-web when I've put put the path in the plugin
configuration as 'suzcrmdata'.
Any advice would be very much appreciated.
Regards,
Dean.
Scanned by MailDefender - managed email security from intY -
www.maildefender.net
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Scanned by MailDefender - managed email security from intY -
www.maildefender.net
Scanned by MailDefender - managed email security from intY -
www.maildefender.net
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Unpack some jar files in WEB-INF/classes folder
Thanks, it works like a charm... //Jacob Anders Hammar wrote: http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html On Fri, Jun 12, 2009 at 13:41, Jacob Bergööjacob.ber...@gmail.com wrote: Hi, I have a need to unpack some specific jar files to WEB-INF classes in my war project. The jar files are separate Maven projects and now it get packed in my war file in the WEB-INF/lib folder, but I need them to be extracted to WEB-INF/classes. How do I do this in Maven 2? Thanks for any pointers or examples // Jacob -- View this message in context: http://www.nabble.com/Unpack-some-jar-files-in-WEB-INF-classes-folder-tp23997323p23997323.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 -- View this message in context: http://www.nabble.com/Unpack-some-jar-files-in-WEB-INF-classes-folder-tp23997323p24030355.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
Hello Stuart, thanks for your reply. Could you please send me your assembly plugin settings? Thanks in advance, Peter
Re: Public repository for open source project
On 13 Jun 2009, jjjaime wrote: I participate in an open source project: http://en.wikipedia.org/wiki/IST-MUSIC and up to now we've used an private maven repository during the implementation. We are still using a SNAPSHOT repository until the project is mature enough. We would like to move to a public repository. Is there any public repository for mvn deploy? What's the most recommendable repository for an open source project? Hav a look at https://docs.sonatype.com/display/NX/OSS+Repository+Hosting hth, - martin signature.asc Description: PGP signature
Plugin / Tool for local repository
Hi to all, I wonder if there is a plugin/tool available to clean a local repository ? After some time repository could became huge with many snapshots or versions (when using ranges) and the only way, for now, is just to clean up by hand. Repository managers like Nexus or Archiva does this cleanup, that's why I wonder if such service could exist in a maven plugin. Regards - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
packaging tuscany based java application with maven
Hello, I have a java application based on apache-tuscany infrastructure. the appllication is a webservice and it comes up and listens at a port to requests from a client. I'm using maven for dependency management and test managment, and It is working freat from the Eclipse IDE. I now need to install the program on a server. there is tomcat running on the server. can you please assist me on deciding which kind of package I need to create, and how can I make maven put all the necessary information in it? I created a jar, and I asked maven to put the dependencies in it, but I still cant execute the jar... Thanks, Renana Heller
merge-maven-repos from local file system
Hi, I am trying to stage the deployment to a repository on the local file system and then merge to a remote repository. Steps: mvn deploy -DaltDeploymentRepository=stage::default::file:///export/stage-repository mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file:///export/stage-repository -Dwagon.target=scpexe://hostname/export/remote-repository -Dwagon.targetId=ssh-repository -s /export/setting.xml No problem with the deployment but when executing merge-maven-repos goal, I got the following error: Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Path is not a directory: org/glassfish/build/build/3.0-SNAPSHOT/build-3.0-SNAPSHOT.pom at org.apache.maven.wagon.providers.file.FileWagon.getFileList(FileWagon.java:235) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:283) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scan(WagonDirectoryScanner.java:245) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.getFileList(DefaultWagonDownload.java:51) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.download(DefaultWagonDownload.java:59) at org.codehaus.mojo.wagon.shared.DefaultMavenRepoMerger.merge(DefaultMavenRepoMerger.java:80) at org.codehaus.mojo.wagon.MergeMavenRepoMojo.copy(MergeMavenRepoMojo.java:42) at org.codehaus.mojo.wagon.AbstractCopyMojo.execute(AbstractCopyMojo.java:49) ... 18 more Any idea why wagon-maven-plugin is trying to get a file list from a file? I'm using Maven version 2.0.10 and JDK 1.6. Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: merge-maven-repos from local file system
http://mojo.codehaus.org/wagon-maven-plugin/usage.html the provided example specifies java.io.tmpdir (folder) mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://people.apache.org/~olamy/staging-repo \ -Dwagon.target=scp://localhost/$LOGNAME/maven-repo \ -Djava.io.tmpdir=target Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Mon, 15 Jun 2009 03:48:59 -0700 From: jane.yo...@sun.com Subject: merge-maven-repos from local file system To: users@maven.apache.org Hi, I am trying to stage the deployment to a repository on the local file system and then merge to a remote repository. Steps: mvn deploy -DaltDeploymentRepository=stage::default::file:///export/stage-repository mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file:///export/stage-repository -Dwagon.target=scpexe://hostname/export/remote-repository -Dwagon.targetId=ssh-repository -s /export/setting.xml No problem with the deployment but when executing merge-maven-repos goal, I got the following error: Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Path is not a directory: org/glassfish/build/build/3.0-SNAPSHOT/build-3.0-SNAPSHOT.pom at org.apache.maven.wagon.providers.file.FileWagon.getFileList(FileWagon.java:235) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:283) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scan(WagonDirectoryScanner.java:245) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.getFileList(DefaultWagonDownload.java:51) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.download(DefaultWagonDownload.java:59) at org.codehaus.mojo.wagon.shared.DefaultMavenRepoMerger.merge(DefaultMavenRepoMerger.java:80) at org.codehaus.mojo.wagon.MergeMavenRepoMojo.copy(MergeMavenRepoMojo.java:42) at org.codehaus.mojo.wagon.AbstractCopyMojo.execute(AbstractCopyMojo.java:49) ... 18 more Any idea why wagon-maven-plugin is trying to get a file list from a file? I'm using Maven version 2.0.10 and JDK 1.6. Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009
RE: update all projects maven version
Lol - yeah - sent this to the wrong mailing list Sorry for the noise! -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Saturday, June 13, 2009 3:45 PM To: Maven Users List Subject: Re: update all projects maven version that is the project version, the OP wants tochange the version of Hudson used in a group of Hudson projects 1.0-beta-1-SNAPSHOT supports versions:set -DnewVersion= (with one minor bug which I will fix on Mon/tue) On 13/06/2009, Arnaud HERITIER aherit...@gmail.com wrote: http://mojo.codehaus.org/versions-maven-plugin/update-child-modules-mo jo.htmlYou change the version in the reactor and you call mvn versions:update-child-modules Cheers, Arnaud # Arnaud Héritier # http://blog.aheritier.net On Sat, Jun 13, 2009 at 5:42 PM, EJ Ciramella ecirame...@upromise.comwrote: Is there a way to programattically update all the projects maven version (or jdk or ant or w/e else)? With cruise control, we'd just check out 20 or so projname.config.xml files and just search/replace all the paths to the maven installation directory. I see the CLI bit for hudson, but not sure if this is how I should do it. - 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: Plugin / Tool for local repository
http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html /Anders On Mon, Jun 15, 2009 at 10:46, Henri Gomezhenri.go...@gmail.com wrote: Hi to all, I wonder if there is a plugin/tool available to clean a local repository ? After some time repository could became huge with many snapshots or versions (when using ranges) and the only way, for now, is just to clean up by hand. Repository managers like Nexus or Archiva does this cleanup, that's why I wonder if such service could exist in a maven plugin. Regards - 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: maven-dependency-plugin doesn't find all dependencies in several repositories
Is it possible that the dependency-plugin uses information from localRepository instead of Repos 1 and 2? I recognized the follwoing behavior: Every time I install an artifact into Repos 2 using deploy:file, the jar and the pom.xml are installed into correctly into Repos 2 (with all the correct dependency-entries in the pom.xml). but also the pom.xml of the artifact in my localRepository is replaced with a new one, containing no dependecies ... Just for explanation: Artifact Z is built by another group and deployed in their own repository using deploy-phase. Maven also installs it in localRepository in the install-phase. If tests are ok, Artifact Z (and pom.xml) are deployed into Repos 2, where other groups also may use it as dependency. As described above, this seems to kill the pom.xml in localRepository. May be a bug in deploy-plugin? But dependency-plugin shouldn't use any information stored in localRepositories in my oppinion! -- View this message in context: http://www.nabble.com/maven-dependency-plugin-doesn%27t-find-all-dependencies-in-several-repositories-tp23961970p24034808.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: [PLEASE TEST] Maven 2.2.0-RC3
I had Friday off, so I logged onto the maven IRC channel at home via ChatZilla, but unfortunately JDCASEY was not logged on when I tried several times. I tried again on Saturday, but again JDCASEY was not online. Today, Monday, I tried from work and found that the corporate firewell blocks IRC. I've been able to use Google IM in the past through the firewall. So, I've opened up gmail and have it on the chat page. JDCASEY, if you see this please consider sending a chat message to my gmail account. My email address there is robertglove...@gmail.com Meanwhile, I'll see I I can build the source code of maven 2.2 RC3 to have log messages to pinpoint the exact line of code causing the proxy problem. --- On Fri, 6/12/09, John Casey jdca...@commonjava.org wrote: From: John Casey jdca...@commonjava.org Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 To: Maven Users List users@maven.apache.org Date: Friday, June 12, 2009, 4:18 PM Do you have the ability to join our IRC channel at irc.codehaus.org (#maven) to talk more about this? If you have a firewall/proxy in the way of an IRC connection, you might also be able to use the CGI client at http://irc.codehaus.org. From looking at your output in the original message on this thread, it seems like Maven doesn't think you're supplying any authentication information... Maybe if we could talk more about this, I could help you look for the reason behind it all. I'm on IRC most days; my nickname is 'jdcasey'. Please come find me if you have the ability, and maybe we can figure this out. Thanks, -john Robert Glover wrote: Below is the message from Wayne I was referring to. Now that I have downloaded and built maven 2.2-RC3, I guess I could put log messages into it to pin-point the exact line of code where the proxy fails. But already as it is, in running maven 2.2-RC3 it already has debug level logging turned on and is showing a lot more information than was being shown when this problem started occuring when I upgraded from maven 2.0.9 to maven 2.1. The sad thing is I have been keeping this maven proxy problem to myself because we have only been using maven for a few months. If I make it be known that it won't work and there is no solution if we upgrade to any version higher than maven 2.0.9, it is likely the managers will ban maven from being used. -- Proxy issues are, by their very nature, almost impossible for an outsider to investigate and resolve. There are literally hundreds (or more) of proxy server software packages in the world, and while they all more or less work for basic web browsing, most have issues with various pieces of software like Maven. I won't claim to know all the changes made to the Maven codebase from 2.0.9 to 2.1.0 (much less the changes in supporting utility libraries) but it would seem that some change has caused your proxy to stop working. If you seriously want to see this resolved, it will probably take some effort on your part to get Maven and all its libraries running in a debugger to try to track down what is different. Unless a ton of people start complaining about similar problems or the issue can be tracked to a specific change made in Maven (or a util library), I don't see this being resolved in any well-defined timeframe. So, I'd stick with 2.0.9 for now. Have you tried 2.0.10 yet? Wayne - Original Message From: John Casey jdca...@commonjava.org To: Maven Users List users@maven.apache.org Sent: Friday, June 12, 2009 10:38:30 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 Can you tell me what Wayne's explanation was for your proxy problem? Or, if Wayne's around, maybe he can chime in. I'm not familiar with this particular discussion, so I'm not sure how to help. Proxies can be incredibly hard to debug remotely, when I don't have access to probe the running system and find out where things are coming apart. -john Robert Glover wrote: The proxy error using 2.2.0-RC3 (see email below) was using the binary download. Since then, I've built 2.2.0-RC3 from source and am looking at it in Eclipse. It builds cleanly if I set it to not test; however I don't know how to run it (with it pointed to a pom.xml to build), so I'm just looking at the source code). The proxy problem I am having (see email below) is from org.apache.maven.artifact.manager.DefaultWagonManage; I can't pinpoint the exact line of source code. I cannot really take this further myself, with my level of expertise (or lack there-of), other than to have noticed that something similar to my problem is reported in a Jira that was opened around roughly the same time my problem first started happening. That Jira is: https://issues.sonatype.org/browse/NEXUS-515 I sure would be a happy camper if my
Re: merge-maven-repos from local file system
please use maven 2.1, its built in wagon-file has this fix -D On Mon, Jun 15, 2009 at 6:12 AM, Martin Gaintymgai...@hotmail.com wrote: http://mojo.codehaus.org/wagon-maven-plugin/usage.html the provided example specifies java.io.tmpdir (folder) mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://people.apache.org/~olamy/staging-repo \ -Dwagon.target=scp://localhost/$LOGNAME/maven-repo \ -Djava.io.tmpdir=target Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Mon, 15 Jun 2009 03:48:59 -0700 From: jane.yo...@sun.com Subject: merge-maven-repos from local file system To: users@maven.apache.org Hi, I am trying to stage the deployment to a repository on the local file system and then merge to a remote repository. Steps: mvn deploy -DaltDeploymentRepository=stage::default::file:///export/stage-repository mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file:///export/stage-repository -Dwagon.target=scpexe://hostname/export/remote-repository -Dwagon.targetId=ssh-repository -s /export/setting.xml No problem with the deployment but when executing merge-maven-repos goal, I got the following error: Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Path is not a directory: org/glassfish/build/build/3.0-SNAPSHOT/build-3.0-SNAPSHOT.pom at org.apache.maven.wagon.providers.file.FileWagon.getFileList(FileWagon.java:235) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:283) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scan(WagonDirectoryScanner.java:245) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.getFileList(DefaultWagonDownload.java:51) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.download(DefaultWagonDownload.java:59) at org.codehaus.mojo.wagon.shared.DefaultMavenRepoMerger.merge(DefaultMavenRepoMerger.java:80) at org.codehaus.mojo.wagon.MergeMavenRepoMojo.copy(MergeMavenRepoMojo.java:42) at org.codehaus.mojo.wagon.AbstractCopyMojo.execute(AbstractCopyMojo.java:49) ... 18 more Any idea why wagon-maven-plugin is trying to get a file list from a file? I'm using Maven version 2.0.10 and JDK 1.6. Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin / Tool for local repository
Good stuff but I also needed the various versions of the project to be removed. 2009/6/15 Anders Hammar and...@hammar.net: http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html /Anders On Mon, Jun 15, 2009 at 10:46, Henri Gomezhenri.go...@gmail.com wrote: Hi to all, I wonder if there is a plugin/tool available to clean a local repository ? After some time repository could became huge with many snapshots or versions (when using ranges) and the only way, for now, is just to clean up by hand. Repository managers like Nexus or Archiva does this cleanup, that's why I wonder if such service could exist in a maven plugin. Regards - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin / Tool for local repository
I saw an interested thread on mojo-dev about a local repository purge plugin. http://www.nabble.com/local-repository-purge-plugin-td16937047.html Any one know it status ? 2009/6/15 Henri Gomez henri.go...@gmail.com: Good stuff but I also needed the various versions of the project to be removed. 2009/6/15 Anders Hammar and...@hammar.net: http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html /Anders On Mon, Jun 15, 2009 at 10:46, Henri Gomezhenri.go...@gmail.com wrote: Hi to all, I wonder if there is a plugin/tool available to clean a local repository ? After some time repository could became huge with many snapshots or versions (when using ranges) and the only way, for now, is just to clean up by hand. Repository managers like Nexus or Archiva does this cleanup, that's why I wonder if such service could exist in a maven plugin. Regards - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven 2.1.0 why it is looking at servicemix.org?
Wayne, thanks for the suggestions. I did not find anything in my ~/.m2 that contained servicemix.org except for the problematic jars that contained javascript/html instead of the pom.xml. I also ran a mvn help:effective-pom and did not see servicemix.org. When I changed mirrorOfcentral/mirrorOf to mirrorOfexternal:*/mirrorOf in my settings.xml, I was able to download the jars that had been a problem. I get the same results if I use mirrorOf*/mirrorOf. (This seems to have fixed my original problem.) My new problem with the mirrorOfexternal:*/mirrorOf is that I can no longer access any of my local repositories except for thirdparty. My guess is that one of my local repository names conflicts with another repository. My local repository names are: internal thirdparty ga snapshots I'm guessing that I had a problem with these jars because one of our local repositories has a conflict with the repositoryId (which is why it was looking for servicemix.org): commons-pool-1.2 commons-pool-1.3 geronimo--jta_1.1_spec howl-1.0.1-1 slf4j-api-1.4.3 xerces-2.0.2 Can anyone confirm my guess about conflicting repositoryId's? From: Wayne Fay [wayne...@gmail.com] Sent: Friday, June 12, 2009 8:32 PM To: Maven Users List Subject: Re: maven 2.1.0 why it is looking at servicemix.org? Any ideas on how I can determine where the servicemix.org is coming from? Grep your ~/.m2/ directory for servicemix.org and see if it might be in a random artifact's pom that is being brought into your build as a direct dependency or transitive. Probably your settings.xml does not specify mirrorOf*/mirrorOf but only mirrorOfcentral. This means only central will be accessed via your Archiva instance. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. This footer also confirms that this e-mail message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Iowa Student Loan. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven 2.1.0 why it is looking at servicemix.org?
SOLVED! We changed our mirror settings based upon the advanced guide: http://maven.apache.org/guides/mini/guide-mirror-settings.html Our settings.xml now excludes our local repositories (local meaning in our building, not on the local machine): mirror idthirdparty/id mirrorOf*,!internal,!ga,!snapshots/mirrorOf nameISL Third Party Proxy Repository/name urlhttp://m2repo/archiva/repository/thirdparty/url /mirror Thanks for the suggestions, it lead us down the right path to find the solution. From: Tim Andersen [tander...@studentloan.org] Sent: Monday, June 15, 2009 9:35 AM To: Maven Users List Subject: RE: maven 2.1.0 why it is looking at servicemix.org? Wayne, thanks for the suggestions. I did not find anything in my ~/.m2 that contained servicemix.org except for the problematic jars that contained javascript/html instead of the pom.xml. I also ran a mvn help:effective-pom and did not see servicemix.org. When I changed mirrorOfcentral/mirrorOf to mirrorOfexternal:*/mirrorOf in my settings.xml, I was able to download the jars that had been a problem. I get the same results if I use mirrorOf*/mirrorOf. (This seems to have fixed my original problem.) My new problem with the mirrorOfexternal:*/mirrorOf is that I can no longer access any of my local repositories except for thirdparty. My guess is that one of my local repository names conflicts with another repository. My local repository names are: internal thirdparty ga snapshots I'm guessing that I had a problem with these jars because one of our local repositories has a conflict with the repositoryId (which is why it was looking for servicemix.org): commons-pool-1.2 commons-pool-1.3 geronimo--jta_1.1_spec howl-1.0.1-1 slf4j-api-1.4.3 xerces-2.0.2 Can anyone confirm my guess about conflicting repositoryId's? From: Wayne Fay [wayne...@gmail.com] Sent: Friday, June 12, 2009 8:32 PM To: Maven Users List Subject: Re: maven 2.1.0 why it is looking at servicemix.org? Any ideas on how I can determine where the servicemix.org is coming from? Grep your ~/.m2/ directory for servicemix.org and see if it might be in a random artifact's pom that is being brought into your build as a direct dependency or transitive. Probably your settings.xml does not specify mirrorOf*/mirrorOf but only mirrorOfcentral. This means only central will be accessed via your Archiva instance. Wayne This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. This footer also confirms that this e-mail message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Iowa Student Loan. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Fwd: Custom lifecycle. Changing the default resource plugin confiduration.
Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Custom lifecycle. Changing the default resource plugin confiduration.
Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009
Re: Custom lifecycle. Changing the default resource plugin confiduration.
*Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list for development on maven and its plugins itself. I'd be happy to follow up on the thread there. To help you along, you don't need to overwrite the default lifecycle - just bind different goals to it. You can't configure goals when you do that - I'm a bit unsure whether you are putting your plugin in there, or the resources plugin, or both. What you are likely looking to do is extend the resources plugin with the new configuration and functionality and bind that by default. An example of declaring a new packaging type is here: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 On 13/06/2009, at 6:37 AM, Erick Dovale wrote: Folks, I am writing a plugin that builds an artifact that needs no compilation or tests whatsever as it is only resources. I am overwriting the default lifecycle to only run the resources phases, the packaging phases and the install phases. I need to change the resource plugin configuration to write the file to a folder other than classes. How can I achieve this from a plugin? Thanks. Erick. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009
RE: Custom lifecycle. Changing the default resource plugin confiduration.
de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /pluginhttp://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component /components /component-set It is all working fine except for the fact that I need to resources plugin to output all the resources into a folder called theme instead of the default classes. This is to ease the creation of a zip file that most have all content inside one single directory at the root of the zip (the theme directory). How can I do this from inside a plugin?? Thanks a lot. Erick. -- Forwarded message -- From: Brett Porter br...@apache.org Date: Fri, Jun 12, 2009 at 11:57 PM Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. To: Maven Developers List d...@maven.apache.org This is still a more appropriate question for users@maven.apache.org, as this is the list
RE: How to set up SCM/CVS/Maven integration with public key authentication?
For anyone who runs into this problem in the future: After downloading the scm plugin source, I discovered that the plugin is using an empty string for the passphrase when authenticating with a public key. To tell the scm/CVS plugin the correct passphrase to use, you need to set a System property for the key maven.scm.cvs.java.ssh.passphrase, i.e. mvn scm:status -Dmaven.scm.cvs.java.ssh.passphrase=my passphrase A little disappointing that the system properties the CVS/SCM plugin uses aren't mentioned in the documentation for the plugin. -Original Message- From: Matt Brown [mailto:matt.br...@citrixonline.com] Sent: Thursday, June 11, 2009 1:11 PM To: users@maven.apache.org Subject: How to set up SCM/CVS/Maven integration with public key authentication? I have a scm section in a POM that looks something like this: scm connectionscm:cvs:ext:myhostname:/cvsroot/repo:module_name/connection /scm I typically use publickey auth to authentication against this cvs server, although it should accept my password as well. When I attempt to run 'mvn scm:update', 'mvn release:prepare', or any Maven goal that involves connecting to this scm, I get the following failure: [INFO] Executing: cmd.exe /X /C cvs -z3 -f -q update -d [INFO] Working directory: C:\Documents and Settings\matt.brown\workspace\projectname org.netbeans.lib.cvsclient.connection.AuthenticationException: Cannot authenticate. Reason: Publickey authentication failed. at org.apache.maven.scm.provider.cvslib.cvsjava.util.ExtConnection.open(ExtConnection.java:136) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connect(CvsConnection.java:166) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:498) at org.apache.maven.scm.provider.cvslib.cvsjava.command.update.CvsJavaUpdateCommand.executeCvsCommand(CvsJavaUpdateCommand.java:53) at org.apache.maven.scm.provider.cvslib.command.update.AbstractCvsUpdateCommand.executeUpdateCommand(AbstractCvsUpdateCommand.java:78) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:63) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:750) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(AbstractCvsScmProvider.java:348) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:821) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:770) at org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmManager.java:526) at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:89) (lots more of the stacktrace) And further down in the stacktrace: Caused by: java.io.IOException: Decrypted PEM has wrong padding, did you specify the correct password? at ch.ethz.ssh2.crypto.PEMDecoder.removePadding(PEMDecoder.java:109) at ch.ethz.ssh2.crypto.PEMDecoder.decryptPEM(PEMDecoder.java:286) at ch.ethz.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:319) Followed by: [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: I'm running this on a Windows machine, with no cvs executable on the PATH. I do have my public key available under $HOME/.ssh, but it doesn't seem as if cvs/maven/scm is loading it here - as I'm not asked for the keyphrase for it. So, I have a few questions: 1. How do I properly tell maven when using scm where my public key resides? Do I need to do it explicitly? 2. From the stacktrace, does it look as if this is even the correct error - or is something else going on? I can see traffic exchanged between my machine and the CVS host when I run this command if I use wireshark, so I know some sort of communication is going on. Thanks - 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: How to set up SCM/CVS/Maven integration with public key authentication (need help!)?
For anyone who runs into this problem in the future: After downloading the scm plugin source, I discovered that the plugin is using an empty string for the passphrase when authenticating with a public key. To tell the scm/CVS plugin the correct passphrase to use, you need to set a System property for the key maven.scm.cvs.java.ssh.passphrase, i.e. mvn scm:status -Dmaven.scm.cvs.java.ssh.passphrase=my passphrase A little disappointing that the system properties the CVS/SCM plugin uses aren't mentioned in the documentation for the plugin. -Original Message- From: Matt Brown [mailto:matt.br...@citrixonline.com] Sent: Friday, June 12, 2009 12:14 PM To: scm-us...@maven.apache.org Subject: How to set up SCM/CVS/Maven integration with public key authentication (need help!)? I have a scm section in a POM that looks something like this: scm connectionscm:cvs:ext:myhostname:/cvsroot/repo:module_name/connection /scm I typically use publickey auth to authentication against this cvs server, although it should accept my password as well. When I attempt to run 'mvn scm:update', 'mvn release:prepare', or any Maven goal that involves connecting to this scm, I get the following failure: [INFO] Executing: cmd.exe /X /C cvs -z3 -f -q update -d [INFO] Working directory: C:\Documents and Settings\matt.brown\workspace\projectname org.netbeans.lib.cvsclient.connection.AuthenticationException: Cannot authenticate. Reason: Publickey authentication failed. at org.apache.maven.scm.provider.cvslib.cvsjava.util.ExtConnection.open(ExtConnection.java:136) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connect(CvsConnection.java:166) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:498) at org.apache.maven.scm.provider.cvslib.cvsjava.command.update.CvsJavaUpdateCommand.executeCvsCommand(CvsJavaUpdateCommand.java:53) at org.apache.maven.scm.provider.cvslib.command.update.AbstractCvsUpdateCommand.executeUpdateCommand(AbstractCvsUpdateCommand.java:78) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:63) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:750) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(AbstractCvsScmProvider.java:348) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:821) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:770) at org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmManager.java:526) at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:89) (lots more of the stacktrace) And further down in the stacktrace: Caused by: java.io.IOException: Decrypted PEM has wrong padding, did you specify the correct password? at ch.ethz.ssh2.crypto.PEMDecoder.removePadding(PEMDecoder.java:109) at ch.ethz.ssh2.crypto.PEMDecoder.decryptPEM(PEMDecoder.java:286) at ch.ethz.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:319) Followed by: [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: I'm running this on a Windows machine, with no cvs executable on the PATH. I do have my public key available under $HOME/.ssh, but it doesn't seem as if cvs/maven/scm is loading it here - as I'm not asked for the keyphrase for it. So, I have a few questions: 1. How do I properly tell maven when using scm where my public key resides? Do I need to do it explicitly? 2. From the stacktrace, does it look as if this is even the correct error - or is something else going on? I can see traffic exchanged between my machine and the CVS host when I run this command if I use wireshark, so I know some sort of communication is going on. Thanks
RE: Plugin / Tool for local repository
same here, interested in any updates on the plugin from the discussion below. Don't want to whip out another one if it already exists. Thanks, mohan kr -Original Message- From: Henri Gomez [mailto:henri.go...@gmail.com] Sent: Monday, June 15, 2009 9:32 AM To: Maven Users List Subject: Re: Plugin / Tool for local repository I saw an interested thread on mojo-dev about a local repository purge plugin. http://www.nabble.com/local-repository-purge-plugin-td16937047.html Any one know it status ? 2009/6/15 Henri Gomez henri.go...@gmail.com: Good stuff but I also needed the various versions of the project to be removed. 2009/6/15 Anders Hammar and...@hammar.net: http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-reposito ry-mojo.html /Anders On Mon, Jun 15, 2009 at 10:46, Henri Gomezhenri.go...@gmail.com wrote: Hi to all, I wonder if there is a plugin/tool available to clean a local repository ? After some time repository could became huge with many snapshots or versions (when using ranges) and the only way, for now, is just to clean up by hand. Repository managers like Nexus or Archiva does this cleanup, that's why I wonder if such service could exist in a maven plugin. Regards - 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 - 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: Custom lifecycle. Changing the default resource plugin confiduration.
As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 11:49:43 -0400 Subject: Fwd: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org Brett, I went through the doc you send me below but could nor find an answer to my question there. I have redefined the lifecycle in my components.xml as follows: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hintcstheme/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases process-resourcesorg.apache.maven.plugins:maven-resources-plugin:resources/process-resources packagecom.syncapse.clearspace:maven-theme-plugin:package/package installorg.apache.maven.plugins:maven-install-plugin:install/install /phases /configuration /component
hibernate3-maven-plugin runs in the wrong project
In the parent project, when I run mvn -Plocalhost-hsql package, for example, it runs the hibernate3 plugin which generates the database, using an embedded hsql database. It's running the database generation in the parent project's directory and creating the files there, but the tests in the database project that use that database are running in the database project's directory. The database file that hsql uses and was created is in the parent project's target directory and, it seems to me, should be in the target directory of the database project. After the hibernate3 plugin runs my directories look like this: waitlist-parent/ target/ database.script (it's really waitlist.script) database.properties (it's really waitlist.properties) waitlist-db/ target/ (no database files) I want it to run the database creation stuff only when I specify the localhost-hsql profile. Is it possible to set this up? I'm hoping that I'm not doing something correctly. The database project's pom file starts like this: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdwaitlist-parent/artifactId groupIdedu.berkeley.ist.waitlist/groupId version1.1-SNAPSHOT/version relativePath../waitlist-parent/pom.xml/relativePath /parent artifactIdwaitlist-db/artifactId packagingjar/packaging And ends with a profile with a build section to do the database generation (in the middle of the pom is a buildpluginsplugin section that configures the hibernate3 plugin): profiles profile idlocalhost-hsql/id activation activeByDefaultfalse/activeByDefault /activation properties db2.urljdbc:hsqldb:file:target/waitlist;shutdown=true/db2.url db2.usersa/db2.user db2.password / jdbc-db2.driverClassorg.hsqldb.jdbcDriver/jdbc-db2.driverClass db2.schemapublic/db2.schema db2.hibernate.dialectorg.hibernate.dialect.HSQLDialect/db2.hibernate.dialect hbmtool.haltOnErrorfalse/hbmtool.haltOnError /properties build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId executions execution phaseprocess-classes/phase goals goalhbm2ddl/goal /goals /execution /executions /plugin /plugins /build /profile /profiles /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to set up SCM/CVS/Maven integration with public key authentication?
Hi, Could you please file a jira regarding this so that it can be fixed? /Anders On Mon, Jun 15, 2009 at 20:16, Matt Brownmatt.br...@citrixonline.com wrote: For anyone who runs into this problem in the future: After downloading the scm plugin source, I discovered that the plugin is using an empty string for the passphrase when authenticating with a public key. To tell the scm/CVS plugin the correct passphrase to use, you need to set a System property for the key maven.scm.cvs.java.ssh.passphrase, i.e. mvn scm:status -Dmaven.scm.cvs.java.ssh.passphrase=my passphrase A little disappointing that the system properties the CVS/SCM plugin uses aren't mentioned in the documentation for the plugin. -Original Message- From: Matt Brown [mailto:matt.br...@citrixonline.com] Sent: Thursday, June 11, 2009 1:11 PM To: users@maven.apache.org Subject: How to set up SCM/CVS/Maven integration with public key authentication? I have a scm section in a POM that looks something like this: scm connectionscm:cvs:ext:myhostname:/cvsroot/repo:module_name/connection /scm I typically use publickey auth to authentication against this cvs server, although it should accept my password as well. When I attempt to run 'mvn scm:update', 'mvn release:prepare', or any Maven goal that involves connecting to this scm, I get the following failure: [INFO] Executing: cmd.exe /X /C cvs -z3 -f -q update -d [INFO] Working directory: C:\Documents and Settings\matt.brown\workspace\projectname org.netbeans.lib.cvsclient.connection.AuthenticationException: Cannot authenticate. Reason: Publickey authentication failed. at org.apache.maven.scm.provider.cvslib.cvsjava.util.ExtConnection.open(ExtConnection.java:136) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connect(CvsConnection.java:166) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:498) at org.apache.maven.scm.provider.cvslib.cvsjava.command.update.CvsJavaUpdateCommand.executeCvsCommand(CvsJavaUpdateCommand.java:53) at org.apache.maven.scm.provider.cvslib.command.update.AbstractCvsUpdateCommand.executeUpdateCommand(AbstractCvsUpdateCommand.java:78) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:63) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:750) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(AbstractCvsScmProvider.java:348) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:821) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:770) at org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmManager.java:526) at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:89) (lots more of the stacktrace) And further down in the stacktrace: Caused by: java.io.IOException: Decrypted PEM has wrong padding, did you specify the correct password? at ch.ethz.ssh2.crypto.PEMDecoder.removePadding(PEMDecoder.java:109) at ch.ethz.ssh2.crypto.PEMDecoder.decryptPEM(PEMDecoder.java:286) at ch.ethz.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:319) Followed by: [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: I'm running this on a Windows machine, with no cvs executable on the PATH. I do have my public key available under $HOME/.ssh, but it doesn't seem as if cvs/maven/scm is loading it here - as I'm not asked for the keyphrase for it. So, I have a few questions: 1. How do I properly tell maven when using scm where my public key resides? Do I need to do it explicitly? 2. From the stacktrace, does it look as if this is even the correct error - or is something else going on? I can see traffic exchanged between my machine and the CVS host when I run this command if I use wireshark, so I know some sort of communication is going on. Thanks - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to set up SCM/CVS/Maven integration with public key authentication?
Created: http://jira.codehaus.org/browse/SCM-477 Thanks. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Monday, June 15, 2009 3:46 PM To: Maven Users List Subject: Re: How to set up SCM/CVS/Maven integration with public key authentication? Hi, Could you please file a jira regarding this so that it can be fixed? /Anders On Mon, Jun 15, 2009 at 20:16, Matt Brownmatt.br...@citrixonline.com wrote: For anyone who runs into this problem in the future: After downloading the scm plugin source, I discovered that the plugin is using an empty string for the passphrase when authenticating with a public key. To tell the scm/CVS plugin the correct passphrase to use, you need to set a System property for the key maven.scm.cvs.java.ssh.passphrase, i.e. mvn scm:status -Dmaven.scm.cvs.java.ssh.passphrase=my passphrase A little disappointing that the system properties the CVS/SCM plugin uses aren't mentioned in the documentation for the plugin. -Original Message- From: Matt Brown [mailto:matt.br...@citrixonline.com] Sent: Thursday, June 11, 2009 1:11 PM To: users@maven.apache.org Subject: How to set up SCM/CVS/Maven integration with public key authentication? I have a scm section in a POM that looks something like this: scm connectionscm:cvs:ext:myhostname:/cvsroot/repo:module_name/connecti on /scm I typically use publickey auth to authentication against this cvs server, although it should accept my password as well. When I attempt to run 'mvn scm:update', 'mvn release:prepare', or any Maven goal that involves connecting to this scm, I get the following failure: [INFO] Executing: cmd.exe /X /C cvs -z3 -f -q update -d [INFO] Working directory: C:\Documents and Settings\matt.brown\workspace\projectname org.netbeans.lib.cvsclient.connection.AuthenticationException: Cannot authenticate. Reason: Publickey authentication failed. at org.apache.maven.scm.provider.cvslib.cvsjava.util.ExtConnection.open(E xtConnection.java:136) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connec t(CvsConnection.java:166) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.proces sCommand(CvsConnection.java:498) at org.apache.maven.scm.provider.cvslib.cvsjava.command.update.CvsJavaUpd ateCommand.executeCvsCommand(CvsJavaUpdateCommand.java:53) at org.apache.maven.scm.provider.cvslib.command.update.AbstractCvsUpdateC ommand.executeUpdateCommand(AbstractCvsUpdateCommand.java:78) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeComma nd(AbstractUpdateCommand.java:63) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.j ava:59) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCom mand(AbstractCvsScmProvider.java:750) at org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(Abs tractCvsScmProvider.java:348) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmPr ovider.java:821) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmPr ovider.java:770) at org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmMana ger.java:526) at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:89) (lots more of the stacktrace) And further down in the stacktrace: Caused by: java.io.IOException: Decrypted PEM has wrong padding, did you specify the correct password? at ch.ethz.ssh2.crypto.PEMDecoder.removePadding(PEMDecoder.java:109) at ch.ethz.ssh2.crypto.PEMDecoder.decryptPEM(PEMDecoder.java:286) at ch.ethz.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:319) Followed by: [ERROR] Provider message: [ERROR] The cvs command failed. [ERROR] Command output: I'm running this on a Windows machine, with no cvs executable on the PATH. I do have my public key available under $HOME/.ssh, but it doesn't seem as if cvs/maven/scm is loading it here - as I'm not asked for the keyphrase for it. So, I have a few questions: 1. How do I properly tell maven when using scm where my public key resides? Do I need to do it explicitly? 2. From the stacktrace, does it look as if this is even the correct error - or is something else going on? I can see traffic exchanged between my machine and the CVS host when I run this command if I use wireshark, so I know some sort of communication is going on. Thanks - 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
RE: Custom lifecycle. Changing the default resource plugin confiduration.
http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-with-property-file.html create the archetype with included properties to create a catalog $ cat archetype.properties archetype.groupId=my.group.id archetype.artifactId=archetype-with-properties archetype.version=2.0 archetype.filteredExtensions=java archetype.languages=groovy an_additional_property=my specific value output-directory=/usr/erick/theme //create archetype $ cd some-project $ mvn archetype:create-from-project -Darchetype.properties=../archetype.properties //install the archetype $ cd target/generated-sources/archetype/ $ mvn install //run it $ mvn archetype:generate -DarchetypeCatalog=local Ayuda? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 14:42:13 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org As a last resource solution yes. The thing is I don't want to force the clients of the plugin to have to do this. instead i just want them to declared an specific packaging type and that's it. Unfortunately they will have to still define the my theme plugin in their poms.xml as it needs to have the extensions parameter set to true; but forcing them to also define the resources plugin to change this particular configuration parameter is plain wrong. There most be another way of doing this that does not involve the clients of the plugins doing anything special; that's what I am looking for. Gracias nuevamente. Erick. On Mon, Jun 15, 2009 at 2:15 PM, Martin Gainty mgai...@hotmail.com wrote: de nada can you use a configuration parameter for output-directory? plugin groupIdsample.plugin/groupId artifactIdmaven-erick-plugin/artifactId version1.0/version configuration output-directorytheme/output-directory /configuration /plugin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Quizas? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 15 Jun 2009 13:50:32 -0400 Subject: Re: Custom lifecycle. Changing the default resource plugin confiduration. From: edov...@gmail.com To: users@maven.apache.org *Martin, I don't think that will work here as maven it self is the one calling the copy-resources goal on the resources-plugin. What I need is a declarative way to pass the output directory into maven from within my plugin. Gracias. Erick * On Mon, Jun 15, 2009 at 1:32 PM, Martin Gainty mgai...@hotmail.com wrote: Hi Erick could you call resources:copyResources -DoutputDirectory=/theme http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html ? Saludos Cordiales Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Re: maven-remote-resources-plugin and org.apache:apache-jar-resource-bundle
I'll answer my own question. It seems that org.apache:apache-jar-resource-bundle versions 1.3 is more flexible and so does exactly what I want. The question is: Why did it regressed by forcing the This product includes software developed at The Apache Software Foundation ( http://www.apache.org/). entry? Is it because maven, the plugin and the bundle content are used? That would be a little harsh since none of these are delivered. Any specific reason? Thanks, Henri On Sun, Jun 14, 2009 at 8:53 PM, Henri Tremblay henri.tremb...@gmail.comwrote: Yes :-( But is there a bundle that was made for external projects? And am I right to say that without these two lines (so if there was a if to replace or removed them, the bundle would be usable for external projects? On Sun, Jun 14, 2009 at 11:58 AM, Dennis Lundberg denn...@apache.orgwrote: Hi The apache-jar-resource-bundle serves one purpose and that is to create releases that comply with the rules set up by the Apache Software Foundation. It is a tool for Apache projects. As you have discovered, that is not necessarily the same thing as a project released under the Apache license. Henri Tremblay wrote: Hi, I'm moving a project to Apache license. The easiest for jar packaging seems to use the maven-remote-resources-plugin and org.apache:apache-jar-resource-bundle. However, I'm annoyed by two lines in the notice: This product includes software developed at The Apache Software Foundation (http://www.apache.org/). Since it's an external project, that's just not true. My question is: - Is there another bundle for external projects somewhere? - I don't really need to NOTICE file at all. Is there a way to get rid of it? - Or may I suggest a modification to the template to have #if ($isApacheProject) This product includes software developed at The Apache Software Foundation (http://www.apache.org/). #end with the default being true to be backward compatible. Thanks a lot, Henri -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCEMENT] - UNIX Maven Plugin 1.0-alpha-4 released
I'm happy to announce the fourth alpha release of unix-maven-plugin. This is still primarily a technology preview, but is fully functional. = New in this release = o support for creating zip archives o added support for classes for pkg o %doc and %config for RPM o Lots of documentation, including a PDF. == Technical changes == MUNIX-18: Simplify the script mechanism MUNIX-17: Document how versions and revisions are calculated MUNIX-16: Document how the scripts directories work MUNIX-15: Improve error message when an artifact is not found MUNIX-12: Add support for creating zip files MUNIX-6: set-attributes doesn't pick up paths that aren't explicitly created with mkdirs (Filed by Marius Gravdal MUNIX-4: Add support for the %doc directive for RPM (filed by Erik Drolshammer) MUNIX-3: Add support for the %config directive for RPM (filed by Erik Drolshammer) MUNIX-1: the release portion of the rpm does not have to be an int (filed by Brett Okken) = About the plugin = The unix-maven-plugin is a Maven plugin for producing installation packages for UNIX platforms. The current release is 1.0-alpha-4. This release is meant as a technology preview release. The plugin is useful but work is in progress to make sure it support even more use cases. The plugin has gained a substantial amount of documentation, available at [1]. The plugin combines the work of the deb, solaris and rpm Maven plugins and also handles the aspect of assembling the packages without using the assembly plugin. Supported platforms: * Debian (.deb) * RedHat and Fedora (.rpm) * SysV packages for Solaris (.pkg) * Generic Zip files (.zip) The development happens on the Codehaus Mojo project [2], if you want to try it out, have found an issue or just want your use case supported get in touch through the mailing lists [3]. [1]: http://mojo.codehaus.org/unix/usage.html [2]: http://mojo.codehaus.org/unix/ [3]: http://mojo.codehaus.org/unix/mail-lists.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why is version 2.0 NOT same as 2.0.0?
I guess it is because the plugins are handled not by ArtifactVersion but by the DefaultPluginVersionManager. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Sun, Jun 14, 2009 at 8:13 PM, B Smith-Mannschottbsmith.o...@gmail.com wrote: 2009/6/14 B Smith-Mannschott bsmith.o...@gmail.com: On Sat, Jun 13, 2009 at 22:56, Jim Sellersjim.sell...@gmail.com wrote: I assume that maven treats them as Strings internally, not doubles. Just like version 3.0-RC1 and 1.0.3-beta3 are valid versions. Doubles!? How would you make a double out of 2.0.0? Nonsensical. http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html Maven version numbers generally have this form: major version.minor version.incremental version-qualifier The version parts are treated as integers. Missing numeric parts are considered zero. The qualifier is compared as a string. Any version not following this syntax is treated purely as a string. I don't recall if unparseable versions always sort before or always after parseable version numbers. It's been a while since I read the code that actually takes care of this. It made me throw up a little inside. // ben On Sun, Jun 14, 2009 at 19:25, Stephen Connollystephen.alan.conno...@gmail.com wrote: however 2.0 and 2.0.0 are both parseable versions. True, and they should be equivalent. Indeed the OP's second post demonstrates this. So, whatever the explanation for the OP's issue, it's not that parsing and comparision of versions is somehow mysteriously broken. // ben - 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
Maven assembly - include/exclude by classifier
I am using Assembly plugin to package application that makes use of JNI and I am using classifiers for the native libraries. I'd like to have assembly descriptor as follows, but currently it doesn't work (I'm hacking this by creating different artifacts for native libs). Am I missing anything? Is it a valid use case? Shall I add a JIRA request? Dimitar assembly fileSets fileSet outputDirectory//outputDirectory directorysrc/main/assembly/directory excludesexclude*.xml/exclude/excludes /fileSet /fileSets dependencySets dependencySet outputDirectorylib/outputDirectory useStrictFilteringtrue/useStrictFiltering excludes exclude*:zip:jni-*/exclude /excludes /dependencySet dependencySet outputDirectorylib/win32/outputDirectory useStrictFilteringtrue/useStrictFiltering unpacktrue/unpack includes include*:*:jni-win32:*/include /includes /dependencySet dependencySet outputDirectorylib/solaris-spark/outputDirectory useStrictFilteringtrue/useStrictFiltering unpacktrue/unpack includes include*:*:jni-solaris-spark:*/include /includes /dependencySet /dependencySets /assembly -- View this message in context: http://www.nabble.com/Maven-assembly---include-exclude-by-classifier-tp24044167p24044167.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: merge-maven-repos from local file system
Thanks, Dan. Switching to maven 2.1. fixes this issue. Jane Dan Tran wrote: please use maven 2.1, its built in wagon-file has this fix -D On Mon, Jun 15, 2009 at 6:12 AM, Martin Gaintymgai...@hotmail.com wrote: http://mojo.codehaus.org/wagon-maven-plugin/usage.html the provided example specifies java.io.tmpdir (folder) mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://people.apache.org/~olamy/staging-repo \ -Dwagon.target=scp://localhost/$LOGNAME/maven-repo \ -Djava.io.tmpdir=target Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Mon, 15 Jun 2009 03:48:59 -0700 From: jane.yo...@sun.com Subject: merge-maven-repos from local file system To: users@maven.apache.org Hi, I am trying to stage the deployment to a repository on the local file system and then merge to a remote repository. Steps: mvn deploy -DaltDeploymentRepository=stage::default::file:///export/stage-repository mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file:///export/stage-repository -Dwagon.target=scpexe://hostname/export/remote-repository -Dwagon.targetId=ssh-repository -s /export/setting.xml No problem with the deployment but when executing merge-maven-repos goal, I got the following error: Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Path is not a directory: org/glassfish/build/build/3.0-SNAPSHOT/build-3.0-SNAPSHOT.pom at org.apache.maven.wagon.providers.file.FileWagon.getFileList(FileWagon.java:235) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:283) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:322) at org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scan(WagonDirectoryScanner.java:245) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.getFileList(DefaultWagonDownload.java:51) at org.codehaus.mojo.wagon.shared.DefaultWagonDownload.download(DefaultWagonDownload.java:59) at org.codehaus.mojo.wagon.shared.DefaultMavenRepoMerger.merge(DefaultMavenRepoMerger.java:80) at org.codehaus.mojo.wagon.MergeMavenRepoMojo.copy(MergeMavenRepoMojo.java:42) at org.codehaus.mojo.wagon.AbstractCopyMojo.execute(AbstractCopyMojo.java:49) ... 18 more Any idea why wagon-maven-plugin is trying to get a file list from a file? I'm using Maven version 2.0.10 and JDK 1.6. Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Quandary over testing support classes.
Hi gang, I've been trying to find a reasonable solution to a problem we have with our Maven-based project. We have a collection of Builder classes that can create Model objects for testing purposes. These are segregated into a separate module (TestSupport) which has the Model artifact as a dependency. This works great for almost everything. The catch is that the more complex Model classes have unit tests that rely on these builders to make the test code easier to read and maintain. So, in that case the Model artifact would need to have the TestSupport artifact as a dependency. Obviously, this isn't going to fly. For the time being, the more complicated unit tests are being held in the TestSupport module, but this really isn't where they belong. We need to keep the Builders in an artifact of their own because they are used by other modules for unit and functional tests. I can see an argument that I might hear, that the Model classes should be simple beans - DTO's, if you will - that have no real need for unit tests. That's a step away from OO, though, isn't it? Maybe we're trying too hard to be as OO as possible? I really don't like the idea of stripping a class of its behavior. On the other hand, maybe there's a better way to get my Maven build set up that will solve this problem for me. Any help? Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
dependency version at pom level
i'm new to maven, but have decades of experience with builds and java. after a basic survey of maven, one of the first things i asked my self is how i could force a version of a dependency at the parent pom. the general use case is that you are working with a series of third-party dependencies (and their respective poms) that specify conflicting versions of a particular library commons-logging for example, and you want to force a specific version that you know you will be running with. let's say you want to verify behavior of those third party dependencies with this specific version using the test goal. i did some research and found some mailing list archives which basically said this wasn't supported and that the technique to address this would involved the use of exclusions, but you may end up having to exclude the same transitive dependency across multiple direct dependencies. this seems to violate the don't repeat yourself (DRY) principle, and i was wondering why there wasn't some thing like an override flag for dependencies in the dependencyManagement section to provide the option to ratchet down the version of a potentially repetitively occurring transitive dependency in one fell swoop. i came up with a round about way of accomplishing that by declaring a pom-type dependency, and specifying the exclusion there, but it seems on the awkward side. so basically, i just wanted to verify this behavior and ask if anyone was aware of any outstanding jira entries requesting this type of feature, or if this is an old topic that has been dismissed as a improper or something. thanks,tony. -- View this message in context: http://www.nabble.com/dependency-version-at-pom-level-tp24046046p24046046.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: Quandary over testing support classes.
On Tue, Jun 16, 2009 at 11:01 AM, David C. Hicksdhi...@i-hicks.org wrote: Hi gang, I've been trying to find a reasonable solution to a problem we have with our Maven-based project. We have a collection of Builder classes that can create Model objects for testing purposes. These are segregated into a separate module (TestSupport) which has the Model artifact as a dependency. This works great for almost everything. The catch is that the more complex Model classes have unit tests that rely on these builders to make the test code easier to read and maintain. So, in that case the Model artifact would need to have the TestSupport artifact as a dependency. Obviously, this isn't going to fly. For the time being, The main code depending on test code is bad design. Pull out the pieces of the code from the test directories and promote it to main code. You should be able to untangle just enough for the main code to no longer depend on test. the more complicated unit tests are being held in the TestSupport module, but this really isn't where they belong. We need to keep the Builders in an artifact of their own because they are used by other modules for unit and functional tests. [del] On the other hand, maybe there's a better way to get my Maven build set up that will solve this problem for me. Either pull out the pieces and place into src/main/java as suggested above, or create another module that can contain the helper/build methods and have your main code depend on the helper artifacts. Using another module will mean that those helper classes are already built and available for your use. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Quandary over testing support classes.
I think my original message may not have been clear. I've tried to clarify it below. Barrie Treloar wrote: On Tue, Jun 16, 2009 at 11:01 AM, David C. Hicksdhi...@i-hicks.org wrote: Hi gang, I've been trying to find a reasonable solution to a problem we have with our Maven-based project. We have a collection of Builder classes that can create Model objects for testing purposes. These are segregated into a separate module (TestSupport) which has the Model artifact as a dependency. This works great for almost everything. The catch is that the more complex Model classes have unit tests that rely on these builders to make the test code easier to read and maintain. So, in that case the Model artifact would need to have the TestSupport artifact as a dependency. Obviously, this isn't going to fly. For the time being, The main code depending on test code is bad design. Pull out the pieces of the code from the test directories and promote it to main code. You should be able to untangle just enough for the main code to no longer depend on test. I think maybe my description was poor. The Model code itself does not rely on the test support classes, but rather the unit tests of those Model classes depend on the test support classes. Let's see if I can draw a picture... MainProject Model Module src/main/java - model classes src/test/java - unit tests for model classes TestSupport Module src/main/java - helper/builder classes - used by other modules in the Test Scope, only src/test/java - current contains unit tests for model classes for which the presence of helper/builders is needed Other modules - most of these have dependencies on both of the above modules, but only rely on TestSupport in the Test scope the more complicated unit tests are being held in the TestSupport module, but this really isn't where they belong. We need to keep the Builders in an artifact of their own because they are used by other modules for unit and functional tests. [del] On the other hand, maybe there's a better way to get my Maven build set up that will solve this problem for me. Either pull out the pieces and place into src/main/java as suggested above, or create another module that can contain the helper/build methods and have your main code depend on the helper artifacts. The helper/builder classes are in a module of their own. I think maybe my clarification, above, helps clear that up. Using another module will mean that those helper classes are already built and available for your use. Yep, that's the idea. We just have the problem of this chicken/egg business. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Quandary over testing support classes.
On Tue, Jun 16, 2009 at 11:59 AM, David C. Hicksdhi...@i-hicks.org wrote: I think my original message may not have been clear. I've tried to clarify it below. [del] I think maybe my description was poor. The Model code itself does not rely on the test support classes, but rather the unit tests of those Model classes depend on the test support classes. Let's see if I can draw a picture... MainProject Model Module src/main/java - model classes src/test/java - unit tests for model classes TestSupport Module src/main/java - helper/builder classes - used by other modules in the Test Scope, only src/test/java - current contains unit tests for model classes for which the presence of helper/builders is needed Other modules - most of these have dependencies on both of the above modules, but only rely on TestSupport in the Test scope I think I see what you are saying. Model (test) depends upon Test Support (main and test jars) I am going to assume that Test Support does not depend upon Model (either main or test) What you need to do is * to tell maven-jar-plugin to build the test jar * depend upon the test jar. See http://maven.apache.org/plugins/maven-jar-plugin/ In TestSupport you want something like build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution goals goaltest-jar/goal /goals /execution /executions /plugin /plugins /build In Model you want /dependencies ... dependency groupIdX/groupId artifactIdTestSupport/artifactId typetest-jar/type scopetest/scope /dependency /dependencies /project Does this sound correct? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Quandary over testing support classes.
Hi gang, I've been trying to find a reasonable solution to a problem we have with our Maven-based project. We have a collection of Builder classes that can create Model objects for testing purposes. These are segregated into a separate module (TestSupport) which has the Model artifact as a dependency. This works great for almost everything. The catch is that the more complex Model classes have unit tests that rely on these builders to make the test code easier to read and maintain. So, in that case the Model artifact would need to have the TestSupport artifact as a dependency. Obviously, this isn't going to fly. For the time being, the more complicated unit tests are being held in the TestSupport module, but this really isn't where they belong. We need to keep the Builders in an artifact of their own because they are used by other modules for unit and functional tests. I can see an argument that I might hear, that the Model classes should be simple beans - DTO's, if you will - that have no real need for unit tests. That's a step away from OO, though, isn't it? Maybe we're trying too hard to be as OO as possible? I really don't like the idea of stripping a class of its behavior. On the other hand, maybe there's a better way to get my Maven build set up that will solve this problem for me. Any help? Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
