Using a previous version of release and/or the maven SCM plugin
I seem to be stumbling hard over a few bugs that have already been identified, reported, and it looks like patches are available - http://jira.codehaus.org/browse/SCM-415. Almost all of my environment is using token based authentication with Perforce, so I thought I'd just push back to the previous version of the Maven SCM plugin (1.0) until a fix is formally released. Unfortunately, I don't seem to be quite grokking how to do that. I've tried adding the following into my project POM stanza, but it's not terribly happy about it: build plugins groupIdorg.apache.maven.release/groupId artifactIdmaven-release/artifactId version4/version /plugins ... /build I've also tried just aiming it at the SCM plugin: build plugins groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm/artifactId version1.0/version /plugins ... /build I've got 1.0 working fine on another system, but I'm at a complete loss on how to specify that I want to use an earlier version of the SCM or release plugin (and it's dependencies) until the kinks get worked out of this latest version. Can anyone enlighten me? -joe Joseph Heck Disney Interactive Media Group - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using a previous version of release and/or the maven SCM plugin
Ah, nevermind - After I asked, I tried a few more variations, finally actually LOOKING at the super-pom to find out where it was supposed to go. GFor the reference archives, my solution is: build ... pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-7/version /plugin /plugins /pluginManagement ... /build -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Heck, Joe Sent: Wednesday, November 05, 2008 3:27 PM To: Maven Users List Cc: Jackson, Brian R Subject: Using a previous version of release and/or the maven SCM plugin I seem to be stumbling hard over a few bugs that have already been identified, reported, and it looks like patches are available - http://jira.codehaus.org/browse/SCM-415. Almost all of my environment is using token based authentication with Perforce, so I thought I'd just push back to the previous version of the Maven SCM plugin (1.0) until a fix is formally released. Unfortunately, I don't seem to be quite grokking how to do that. I've tried adding the following into my project POM stanza, but it's not terribly happy about it: build plugins groupIdorg.apache.maven.release/groupId artifactIdmaven-release/artifactId version4/version /plugins ... /build I've also tried just aiming it at the SCM plugin: build plugins groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm/artifactId version1.0/version /plugins ... /build I've got 1.0 working fine on another system, but I'm at a complete loss on how to specify that I want to use an earlier version of the SCM or release plugin (and it's dependencies) until the kinks get worked out of this latest version. Can anyone enlighten me? -joe Joseph Heck Disney Interactive Media Group - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SURVEY] How does your team retrieve artifacts?
On May 20, 2008, at 11:15 PM, Jason van Zyl wrote: [X] Our team uses HTTP to retrieve our artifacts [ ] Our team intends to use HTTP to retrieve our artifacts [ ] Our team uses the filesystem [X] Our team does not use HTTP or the filesystem because please say what protocol you use and the reason We also use SMB fileshare access. -joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Artifacts not being indexed
I've run into the same issue, but I don't normally push in files through the file system directly. In the logging, I saw that the system was finding the file, but it wasn't making it through it's steps to getting pushed into the index. I never found a real way around this issue, and just instantiated a whole new archiva setup with the data in there before I fired everything up to resolve the issue for myself. I know that doesn't help Carlton's issue, but I thought I'd mention it. -joe -- Joseph Heck Walt Disney Internet Group -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Brown, Carlton Sent: Friday, February 15, 2008 10:31 AM To: [EMAIL PROTECTED] Subject: RE: Artifacts not being indexed -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 1:17 PM To: [EMAIL PROTECTED] Subject: Re: Artifacts not being indexed On Fri, Feb 15, 2008 at 11:06 AM, Brown, Carlton [EMAIL PROTECTED] wrote: I've got a problem where an artifact downloaded to the filesystem cannot be browsed. There's some problem with either the database scanning or repository indexing. The maven metadata files are not being generated. The pom file appears to be good. By downloaded, do you mean you are using Archiva as a proxy? Or do you have an external process that is writing to the filesystem? External process writing to the filesystem. The first thing I'd track down is why there is no metadata file. There is a checkbox in the Archiva config that will make it create missing metadata files. Try checking that box and then clicking 'scan' and then 'update database'. Does it now show up in browse? It does not. That checkbox appears to be enabled by default, and I have been doing 'scan' and 'update database', so no luck there. Strangely, when this happens, the artifacts show up in a search, but you can't browse to them. I mean they don't show up under the /archiva/browse URL, you can use the /repository URL and see them there just fine. (I've seen it create missing metadata files. I'm less sure about its ability to repair broken ones.) It does create missing metadata files, but the process seems to be very hit-or-miss, and shows almost nothing in the way of useful feedback or diagnostics. Is there some other, more decisive manual way to force it to re-scan the entire filesystem and recreate the metadata files? - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
RE: java - java2wsdl - wsdl2java
We've had a similar problem with some of our multimodule projects. We found adding this additional configuration for the release plugin helped resolve the issue: plugin artifactIdmaven-release-plugin/artifactId configuration preparationGoalsinstall/preparationGoals /configuration /plugin -joe Joseph Heck Walt Disney Internet Group -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of deckrider Sent: Wednesday, February 13, 2008 3:44 PM To: Maven Users List Subject: java - java2wsdl - wsdl2java I have a multi-module project that begins with java, needs to generate a wsdl, and then from that wsdl needs to generate more java. The plugin I'm using for this is the axistools-maven-plugin. Unfortunately this approach does not play well with the release plugin. It works fine until it comes time for a release. The problem appears to be that I need to have the jar created from the original java in the _plugin_ dependencies, and that somehow causes the following error during release:deploy that the jar (in a the first sibling module) has not yet been uploaded to our archiva instance. Anyone know how I can work around this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Achiva and Proximity
That process (dropping in new directories to an archiva instance) is exactly what I'm doing - works very nicely. One tidbit that I noticed in version 1.0 is that if you have established an internal repository and then add *to it* after the fact, the artifacts don't always get indexed properly. I found that getting the directory in place prior to launching archiva for the first time (I was shoving all my artifacts into the default internal repository) worked to resolve that issue. -joe -Original Message- Sent: Monday, February 04, 2008 9:15 AM To: [EMAIL PROTECTED] Subject: Re: Achiva and Proximity Sure - since both use repositories stored in the file system you can configure Archiva to point at the disk location of the repositories when you add managed repositories. They'll be scanned and indexed after they are added. Archiva doesn't however have an option for importing configuration from Proximity. Cheers, Brett On 04/02/2008, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Hi All, Is it possible to migrate an existing Proximity repository to use Archiva ? Many thanks Jon This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom. -- Brett Porter Blog: http://www.devzuz.org/blogs/bporter/
RE: Which technology stack are you using?
Maven (2), with a few Ant plugins and custom tidbits added on Perforce CruiseControl (bagged Continuum 1.0 because it didn't play well with Perforce. 1.1alpha is much better, but waiting for a release to not torque over our developers too much) Proximity (pending looking at some of the newer caching repository services/servers) Eclipse (mostly, also some IDEA) - minimal integration, but looking back at it again with the recent (past few months) improvement in the m2eclipse plugin at CodeHaus. -joe [EMAIL PROTECTED] Walt Disney Internet Group - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Uploading the .jar to my internal repository
You want to use the maven deploy plugin - details on usage here: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin A.Villalobos Sent: Thursday, June 21, 2007 1:40 PM To: users@maven.apache.org Subject: Uploading the .jar to my internal repository Hello, I've a question? I'm trying to upload a .jar to my internal repository. Somebody can helpme with a detailed howto about this task? Thanks for all. Martin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven build listener?
You can build a plugin to bind to any lifecycle phase of the build
process - or you can use the AntRun plugin to bind in a specific ant
task (or set of tasks) pretty quickly. Not sure what events you want to
trigger it, but if just want messages coming out at specific points of
the build life cycle, then using the Antrun plugin is probably the
fastest option.
Something like:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idfoo/id !-- make this unique among all antrun plugin
bindings in this pom --
phaseinitialize/phase
configuration
tasks
echoSending a message!!!/echo
!-- echo${project.basedir}/echo --
echoRunning on ${os.name}/echo
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
-joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Erez Nahir
Sent: Wednesday, May 16, 2007 2:12 PM
To: Maven Users List
Subject: Maven build listener?
Hi,
I would like to add to the build summary additional information, it
doesn't have to be embedded in the final message, can be just on top of
it.
I was thinking to use some kind of listener that will print my message
to the screen, something like:
[INFO]
[INFO] My message goes here
[INFO]
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed May 16 17:08:43 EDT 2007
[INFO] Final Memory: 1M/3M
[INFO]
Is there a way to add some kind of maven listener to the build?
Thanks,
Erez.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven users in the industry
This may or may not apply - We've only recently moved to Maven adoption, and while there have been some problems with the move, the reasons for moving were always very clear - concrete delineation of our dependencies (We have a fairly deep dependency tree, with a lot of older code). That was recognized as a problem across the board, and just having that as a concrete point made a big difference. We also expended a fairly significant period of time with one or two folks to just learn Maven. Learn it deep, convert builds, try it out - make sure it really worked. We generated internal task-based documentation from that process, and we showed it working in a number of brown-bag kinds of meeting and one on one's. Having someone available to answer questions for anyone attempting to convert was/is crucial. Frustrations have come up around control - Maven has the very definitive life-cycle of builds, but within a phase of the lifecycle things become very undefined in terms of what goes first and for our more complex product builds, we need some level of control. Maven is also clearly most beneficial for Java, and more just another thing to wrap when it comes to any other style of build. Some of our product uses both java development, C++, and C# all in one combined product suite. We've got it building with Maven - to the heroic effort of some of the devs - but only because they were enthusiastic about the tool set and the potential for both now and into the future. -joe Kalle Korhonen wrote: I second that. On a large organization, with lesser Java knowledge and only very few strong engineering leads, any change meets resistance. I went through the same converting our project to Maven and there's still resistance. The most common arguments I hear: - We have no expertise on Maven (they want somebody to teach them how to do things rather than assuming the responsibility of their own learning) Here, the luck of Maven's documentation join the game, if we only had good (and short;-) docs describing what is a life cycle, when and why the local repository should be cleaned up and more and more referring the whole team to read Better Builds With Maven does not work for engineers looking for the fast and short solution (but, it's a great book). - Build's no different from Ant (managers don't see the benefits because proper metrics aren't gathered and they don't give it enough time. All they see is an immediate disturbance in way things are done) - No benefit in Maven related goodies (e.g. Maven site, Continuum - I set up both, people don't see the benefit: unofficial, not in use, extra, nobody looks at reports. I mostly think the organization's as a whole is just not at the maturity level they could do software differently, based on test-driven and continous integration principles) Most of my managers does use the reports, but here comes the other issue, if we have a 50 component project, you can't see the project's status, you can only see the component's status, for example: unit tests summary on a project's level, code coverage rate, even the javadoc aggregation is broken. - Builds break of unknown reasons, server down, plugins not found (somewhat legitimate. Explain again why my build machine needs http to build? We resorted to using a file repository only. I think a better way to solve this problem is with better maven proxies, like Archiva, and of course setting the versions of everything you are using) Yep, and add repositories downtime... - We don't know the plugins and transitive dependencies we are using (I mostly attribute this to people just being lazy and not bothering to check reports and understand the architecture) - What's a snapshot, how do we version properly (module versioning had never before been used - only the product as a whole) so we were not in any worse position. But the truth is that release planning and doing it properly takes time, even with Maven) So, I think you can find some of Maven's disadvantages from the recent emails, but don't get it wrong, I think Maven is the way to go. Erez. Kalle On 4/12/07, Erez Nahir [EMAIL PROTECTED] wrote: I assume you did not have the opportunity to convince the old C++/Make guys to change their habits... :-) Erez. Barrie Treloar wrote: On 4/12/07, Erez Nahir [EMAIL PROTECTED] wrote: Here in Cisco we use Maven2. If you can, when your presentation is ready, please share it, we still have some resistance from old make/ant supporters... How can there be resistance? Once you get things up and running m2 is so much more simpler to maintain/manage. Ant still has it's place for scripting things outside the build lifecylce. Make definitely isn't needed anymore. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
need help with a multimodule build - binding an assembly to package it all up
I have several multi-module builds all rolling with Maven, and I'm having a little trouble figuring out how to bind an assembly directive to the master pom's build cycle so that it can pull all the results together into the master pom's target directory. The structure I have now: Master +-- pom.xml (pom packaging, assembly defined with moduleSets) +-- model-jar (jar packaging) +-- guest webapp (war packaging) +-- admin webapp (war packaging) I've got it all working such that I can invoke mvn clean package assembly:directory or mvn clean package assembly:assembly and get the results that I'm looking for in the master pom's target directory. When I try to add in a stanza to bind the assembly to the package phase of the master pom, things start breaking. I started with: build plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/assemble/ops.xml/descriptor /descriptors /configuration /plugin /plugins /build And updated it to: build plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/assemble/ops.xml/descriptor /descriptors /configuration executions execution idmake-assembly/id phasepackage/phase goals goalattached/goal /goals /execution /executions /plugin /plugins /build The result is that it looks like the assembly is being invoke *prior* to the modules getting built - not at all what I expected. Is there a mechanism that I'm overlooking to indicate that I want the modules all built/processed prior to the assembly in the master pom getting invoked? I've tried binding in different goals to the assembly, but single, and directory-inline, and attached didn't appear to make much difference in this case. Am I coming at this problem from the wrong angle? -joe Joseph Heck Walt Disney Internet Group x8664-4352
RE: release:prepare problem with Perforce SCM
When you run the command with -X -e (to get all the debugging output - i.e. mvn -X -e release:prepare ), what do you see towards that failure? I've just run into a similar problem myself, and from what I've gathered so far, it is related to having a parent pom that's in the repository. Still debugging it though... -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jefferson, David Sent: Tuesday, February 20, 2007 1:21 AM To: users@maven.apache.org Subject: release:prepare problem with Perforce SCM I am evaluating maven for my company and have come across the following problem in my test application. I have a parent project and a child project. In the parent pom I have the following: scm connectionscm:perforce://users/jeffersd/maventest/connection developerConnectionscm:perforce://users/jeffersd/maventest/developerC onnection urlscm:perforce://users/jeffersd/maventest/url /scm I have the P4CLIENT set in my environment. But when I do a release:prepare I get the following error message: [INFO] Checking in modified POMs... [INFO] Tagging release with the label Insight-1.0... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: Tag failed Command output: Label Insight-1.0 not changed. I have tried maven 2.0.4 and 2.0.5 on Windows and Unix. Any ideas? Thanks, Dave -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as KBC FP). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided as is, without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: release:prepare problem with Perforce SCM
I'm not sure that's 100% accurate, as we're using Perforce and are also using the release plug-in without too much issue. A few quirks here and there, but mostly it's been our own learning curve of how to do X. The one issue we've unexpectedly hit most recently was using a disassociated parent POM for some inheritance goodies, and when we attempted to run mvn release:prepare --batch-mode on a project that specified this remote POM as a parent, it attempted to submit a changelist for the parent POM instead of the one we were actually twiddling. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jackman Sent: Tuesday, February 27, 2007 10:28 AM To: Maven Users List Subject: RE: release:prepare problem with Perforce SCM We're also using Perforce, and apparently Perforce support wasn't added to the release plugin until after the current (beta 4) release. I haven't seen anything about when beta 5 will release to fix this problem, but I was able to get the release plugin code and build it myself and releases work fine. Hope this helps. If you need more information on how to get that code and build it, I can look it up again. ..David.. -Original Message- From: Heck, Joe [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 11:08 AM To: Maven Users List Cc: Jefferson, David Subject: RE: release:prepare problem with Perforce SCM When you run the command with -X -e (to get all the debugging output - i.e. mvn -X -e release:prepare ), what do you see towards that failure? I've just run into a similar problem myself, and from what I've gathered so far, it is related to having a parent pom that's in the repository. Still debugging it though... -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jefferson, David Sent: Tuesday, February 20, 2007 1:21 AM To: users@maven.apache.org Subject: release:prepare problem with Perforce SCM I am evaluating maven for my company and have come across the following problem in my test application. I have a parent project and a child project. In the parent pom I have the following: scm connectionscm:perforce://users/jeffersd/maventest/connection developerConnectionscm:perforce://users/jeffersd/maventest/developerC onnection urlscm:perforce://users/jeffersd/maventest/url /scm I have the P4CLIENT set in my environment. But when I do a release:prepare I get the following error message: [INFO] Checking in modified POMs... [INFO] Tagging release with the label Insight-1.0... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: Tag failed Command output: Label Insight-1.0 not changed. I have tried maven 2.0.4 and 2.0.5 on Windows and Unix. Any ideas? Thanks, Dave -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as KBC FP). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided as is, without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: skipping tests
If you bundle your tests into modules, you can define which modules are dependencies with a profile, and then drive their run/not run based on whether or not a profile is defined. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:26 PM To: Maven Users List Subject: skipping tests So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: skipping tests
Heh - I know the feeling. I'm basing this on some examples and discussion I found on running functional tests integrated into a Maven2 build. Not exactly what you're wanting, but the on/off switch mechanism could be used almost identically. I'm not a guru on making profiles work, but the gist would be to put all the unit tests into a module under your master build, and instead of defining them in the modules.../modules XML stanza of the POM, set it up in the profiles.../profiles section. As an example: modules moduleexample-jar/module moduleexample-war/module /modules ... profiles profile idfunctional-test/id activation property nameenableCiProfile/name valuetrue/value /property /activation modules modulefunctional-test/module /modules /profile /profiles And then when you wanted to invoke including that module in the build, you'd simple invoke the profile on the command line. i.e. mvn clean test -P functional-test Does that help? -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:42 PM To: Maven Users List Subject: RE: skipping tests Sorry - this makes my eyes go googly - can you explain a bit more in detail? We have everything modularized, but typically build from the topmost level of the project. I was hoping to find a -Dmaven.test.skipthese=somelist kind of a solution. From the commandline would be the best option. Specifying a profile via the commandline would be second best. -Original Message- From: Heck, Joe [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 3:29 PM To: Maven Users List Subject: RE: skipping tests If you bundle your tests into modules, you can define which modules are dependencies with a profile, and then drive their run/not run based on whether or not a profile is defined. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EJ Ciramella Sent: Thursday, December 07, 2006 12:26 PM To: Maven Users List Subject: skipping tests So I know about the: -Dmaven.test.skip=true setting, but is there a way to skip packages or modules worth of tests? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question about transitive dependencies
I couldn't answer this for one of the devs in our team, so I thought I'd push the question to you all for any feedback you could provide. Any insight would be great... -joe -- -- Can anyone explain to me why transitive dependencies (even of dependencies that are specified as compile scope in your project) are put on the compile time classpath? It seems to me that transitive dependencies on the compile time classpath are useless at best, since you shouldn't need them to build the project. If you have a transitive dependency that you actually do need for your project to build, doesn't that pretty much by definition mean that it should be a direct dependency of your project instead? For example say that I have a project in which I specify the artifact Foo as a dependency, and foo has a dependency on project Bar. If my project doesn't have any direct dependency on Bar then there's no reason I need Bar to be in my classpath when I build, but having it there should be benign. But if my project does depend on Bar then just specifying Foo as a dependency could cause my project to build fine. It might not even be obvious that I'm getting my Bar dependency through Foo. This situation could potentially lead to bugs in my build or in my code if the Foo project decides to upgrade to Bar 2.0 and my code isn't compatible with it or if Foo drops its dependency on Bar altogether. So, is there a reason I'm missing for why you'd ever want to put a transitive dependency on your compile time classpath? Is there a way to cause a project to not put transitive dependencies on its compile time classpath but to keep them on the runtime classpath? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2 RMI
I never found an RMI plugin, but I resolved the issue by binding in an
ant-based task to generate the RMIC stubs to the process-classes phase.
Here's the relevant POM snippet...
It gets specific to the project (defining which classes get the RMIC
task invoked on them), but it has worked reasonably well for us.
-joe
project...
...
build
...
plugins
...
plugin
...
executions
...
execution
idprocess-classes-rmic/id !-- needs to be unique among
executions --
phaseprocess-classes/phase
configuration
tasks
echoRunning RMIC/echo
rmic base=${project.build.directory}
classpathref=maven.compile.classpath
classname=com.disney.foo.bar /
rmic base=${project.build.directory}
classpathref=maven.compile.classpath
classname=com.disney.foo.baz /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Borut Bolcina
Sent: Wednesday, September 06, 2006 10:44 AM
To: maven
Subject: Maven 2 RMI
Hello,
anybody have a Maven 2 RMI compiler plugin? I can't find any.
Thanks,
Borut
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Integration Testing
We have several different mechanisms running - but most of them are honestly manual. The automated solution that one of our teams have come up and and stuck with is the following: 1) set up a multi-module maven2 project, with one of those modules being a functional test suite, another the WAR that we're pushing and banging on. 2) using cargo, we deploy the WAR produced to an instance of Tomcat running on an available and preset QA machine. 3) We invoke the functional tests (primarily httpunit stuff) locally. The how to for the separate functional test module setup was on this earlier - the big pieces to note being that the functional test module is set with POM packaging, and then plugins manually bound to the various steps (in this case, the maven-surefire-plugin bound to the integration-test phase and the cargo plugin bound to the pre-integration-test phase) We've additionally set it up so that functional tests are only included with a specific profile (originally named functional-tests) so that your personal builds will invoke them only when desired. Anything much more complex than this, and I think we'd need to reach out of maven with a custom AntTask bound in there to do setup/teardown kinds of work. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruel Loehr Sent: Wednesday, August 30, 2006 1:33 PM To: Maven Users List Subject: Integration Testing I'd like to query the community and see how you guys are handling integration testing in real world environments. I've looked through the list and the Better builds book, but didn't like what I saw.. Here is the use case: Use Case A: A user has a project which builds a war. For integration testing the war needs to be deployed in an app server. The process will be to startup the app server, deploy the war, run unit tests, stop the app server. Here is the gotcha. App servers can have many configurations. In this case, we would like to test the functionality of this war on three different app server configurations. Use case A would need to be executed 3 times automatically, each time with a different server configuration. Assuming I already know how to modify the appserver configs, any suggestions on how the repeated execution of this use could be achived in scalable fashion (e.g. if I have 25 server configurations my build file won't be a nightmare to maintain). In ant, it's pretty simple as I can just string together targets until my heart is content. With maven, I feel I am imprisoned by the lifecycle in this case. Ruel Loehr JBoss, a division of Red Hat QA -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.7/433 - Release Date: 8/30/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why switch to Maven?
This might be under your category of lack of good documentation: the tool really doesn't help you determine what's happening. The error messages are obscure, and there is now easy way to determine what is even easily available from the command line. To learn anything about maven, you need to be dedicated to really wanting to use it and be willing to dive into online documentation. The Better Builds with Maven online book was a huge benefit - we are making the switch for some projects, and we never would have been able to enable that without the online book. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Redmond Sent: Tuesday, August 29, 2006 10:55 AM To: Maven Users List Subject: [POLL] Why switch to Maven? Hi all Maven users! I'm beginning a study to outline the real reasons that people have for avoiding Maven. My questions to you all are: What were your anxieties about using Maven? If you use Maven: what helped you make the decision? If you don't: why did you avoid it? Here are some that I have heard in the past: * Lack of good documentation. * Community unwilling to help me with my problems. * Not industry supported or mainstream enough. * I don't like conforming to the Maven project layout. * My project is too complex to switch. * There are not enough plugins available. * We already have a large investement in tool X. * I have to build native/non-Java code. Any more reasons? Care to expand these ideas? Thanks for your help! Eric Redmond http://codehaus.org/~eredmond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cargo Tomcat
We've been using Cargo to deploy out WARs to instances of tomcat on local dev boxes beautifully. The relevant stanza we're using: plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId configuration container containerIdtomcat5x/containerId homec:/apps/stock-tomcat-5.0.28/home /container configuration dirc:/apps/stock-tomcat-5.0.28/dir /configuration /configuration /plugin Although there's a lot more information on the cargo plugin site for options and how-to. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Ferguson Sent: Wednesday, August 23, 2006 1:59 PM To: users Subject: RE: Cargo Tomcat I just located tomcat-maven-plugin at codehaus and cargo doesn't seem to be listed. Is tomcat-maven-plugin the cargo replacement? Also, in the maven book, I read about a continuous deploy for jetty. Is there anything like that available for tomcat? -Original Message- From: Douglas Ferguson Sent: Wednesday, August 23, 2006 3:44 PM To: users Subject: Cargo Tomcat Anybody using cargo with tomcat? I'm curious about how you deal with quick dev cycle changes where you might want to push 1 file but don't want to do an entire build to do so. D- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cargo Tomcat
http://cargo.codehaus.org/ specifically I'd recommend taking a once over http://cargo.codehaus.org/Quick+start -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Ferguson Sent: Wednesday, August 23, 2006 2:18 PM To: users Subject: RE: Cargo Tomcat Where can I find the cargo docs? Also, do you ever do any file deploys. I.E. After updating just 1 jsp... -Original Message- From: Heck, Joe [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 4:11 PM To: Maven Users List Subject: RE: Cargo Tomcat We've been using Cargo to deploy out WARs to instances of tomcat on local dev boxes beautifully. The relevant stanza we're using: plugin groupIdorg.codehaus.cargo/groupId artifactIdcargo-maven2-plugin/artifactId configuration container containerIdtomcat5x/containerId homec:/apps/stock-tomcat-5.0.28/home /container configuration dirc:/apps/stock-tomcat-5.0.28/dir /configuration /configuration /plugin Although there's a lot more information on the cargo plugin site for options and how-to. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Ferguson Sent: Wednesday, August 23, 2006 1:59 PM To: users Subject: RE: Cargo Tomcat I just located tomcat-maven-plugin at codehaus and cargo doesn't seem to be listed. Is tomcat-maven-plugin the cargo replacement? Also, in the maven book, I read about a continuous deploy for jetty. Is there anything like that available for tomcat? -Original Message- From: Douglas Ferguson Sent: Wednesday, August 23, 2006 3:44 PM To: users Subject: Cargo Tomcat Anybody using cargo with tomcat? I'm curious about how you deal with quick dev cycle changes where you might want to push 1 file but don't want to do an entire build to do so. D- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Graphical View of Dependencies
You might check out http://www.artima.com/forums/flat.jsp?forum=106thread=155342 and (a thread about JarAnalyzer) and see if that will do what you're looking for. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Koh, Pin (STL) Sent: Tuesday, August 15, 2006 2:20 PM To: users@maven.apache.org Subject: Graphical View of Dependencies Is there a good graphic tool to visualize jar dependencies? Pin Koh *** Confidentiality Notice *** This email, its electronic document attachments, and the contents of its website linkages may contain confidential health information. This information is intended solely for use by the individual or entity to whom it is addressed. If you have received this information in error, please notify the sender immediately and arrange for the prompt destruction of the material and any accompanying attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Corporate Environment Problems
+1 - we used this ourselves, and it's made maven2 significantly smoother for us. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamás Cservenák Sent: Friday, August 04, 2006 10:10 AM To: Maven Users List Subject: Re: Corporate Environment Problems Hi, you can look at here: http://proximity.abstracthorizon.org/ Here you will find some examples for settings.xml and creating environment. ~t~ On 8/4/06, Flynn, Adam [EMAIL PROTECTED] wrote: I have just began to use maven 2. I have ran into a problem whilst attempting to setup my first project. It appears that because I am behind a proxy maven cannot gain access to the archetype plugin. I need to establish some form of local repository of plugins. Could somebody please tell me how I could go about setting up such a repository manually (i.e what directory structure will be required) and what changes I'll need to make to settings.xml. Thanks Adam Flynn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] is there a way to utilize an 'unless' clause in an ant-run?
I'm converting a few builds from Ant into Maven2, and the ant targets are using an unless clause to do a little conditional work. Is there a mechanism by which we can specify an unless class in an ant-run task? -joe
RE: Problem with checksum generation
Probably easiest would be to generate the POM and associated hashes to a new location and then copy them back into place. Take a look into the 4k jar and see what's there. I'm not sure, but at a guess there'll be some Maven manifest information. -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of v_waran Sent: Friday, July 07, 2006 2:38 PM To: users@maven.apache.org Subject: Problem with checksum generation Hi, I am trying to create POM and checksum for existing jar file. When I tried to run the below command POM and checksum files are created but jar file is overwritten to 4k.( I tried with different jar files but consistenly its overwritten to size of 4k.). Command used is mvn deploy:deploy-file -DrepositoryId=localRepository -Dpackaging=jar -Durl=file:\\D:\test\extlib2 -Dversion=1.0 -DgroupId=aopalliance -DartifactId=aopalliance -Dfile=..\..\extlib2\aopalliance\aopalliance\1.0\aopalliance-1.0.jar 1. Is their any option to not to overwrite the jar file (if it already exist) ? If not why does it create only to 4k ? Any idea ? 2. Any alternative way to create POM checksum file(s) for the existing jar file ? Any input is highly valuable. Regards, waran -- View this message in context: http://www.nabble.com/Problem-with-checksum-generation-tf1908797.html#a5 225095 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Null Pointer Exception when trying to load my own Ant mojo/plugin
I've been trying to build my own plugin using an Ant mojo, and when I attempt to load it up into maven, I'm getting a null pointer exception. How does one go about debugging this to determine where I've made a mistake in the plugin? This is all being driven in a move to convert a pre-ant build mechanism up to Maven. Should I consider just bagging the plugin and pushing this into the POM with an Ant task? [INFO] Scanning for projects... [INFO] [INFO] Building tea [INFO]task-segment: [clean, package] [INFO] [INFO] artifact WDIG:wdig-beandoc-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1252) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java: 982) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.jav a:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Thu Jun 29 08:40:54 PDT 2006 [INFO] Final Memory: 1M/4M [INFO] -joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Any news about the update of Maven2 book with corrected errata ?
I would be happy to be a technical reviewer -joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of natalie burdick Sent: Monday, June 26, 2006 5:10 PM To: Maven Users List Subject: Re: Any news about the update of Maven2 book with corrected errata ? Sebastien, Are you volunteering as an author or a reviewer? Please let me know and I will contact you directly off the mailing list - and if there are any other volunteers interested in being reviewers, please feel free to respond to this thread. Natalie On 6/23/06, Sebastien Arbogast [EMAIL PROTECTED] wrote: Any news about the updated version of Maven2 book ? If you need help, I'm volunteer :oP -- Sébastien Arbogast The Epseelon Project : http://www.epseelon.net Blog : http://sebastien-arbogast.epseelon.net TagSpot : http://www.tagspot.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
