Re: Maven Install on Mac OS X

It sounds to me like you're having a problem getting a clean download. Be sure to check the MD5 for your download. If it doesn't match the one published on the download page, then your download has errors. bandrm wrote: This is my first time on a Mac. I have maven 2.2.1 installed on a

Re: Maven Install on Mac OS X

Run the command: md5sum apache-maven-2.2.1-bin.tar.bz2 Check to be sure that the result matches the published checksum on the download page: http://maven.apache.org/download.html bandrm wrote: Here are the version details... Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) Java

How to refer to project's classpath for plugin configuration?

I'm having a problem with the Liquibase plugin. A custom change set is unable to find a classpath resource in target/classes. I think it could be that the plugin isn't using the correct classpath. So, I'd like to configure it by hand. How can I refer to the Maven classpath for the

Re: How to refer to project's classpath for plugin configuration?

I had not, but I have now, and that doesn't help, either. I've got a similar post on the Liquibase list to see if anyone there can help. Ryan Connolly wrote: Did you try maven.compile.classpath instead of project.classpath? On 12/1/09, David C. Hicks dhi...@i-hicks.org wrote: I'm having

maven-changes-plugin: automatic update for release?

Hi folks, I'm using the Changes plugin to both produce a report for my Site and to distribute email announcements of changes. The problem is that if we're not careful to remember to update the changes.xml file itself, then our release build fails because it doesn't find a change set with the

Re: maven-changes-plugin: automatic update for release?

. You can filter your changes.xml if you cannot use current version only. Use ci system to run the site and changes report so you know if it'll work or not before the release. Kalle On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks dhi...@i-hicks.org wrote: Hi folks, I'm using the Changes

Re: maven-changes-plugin: automatic update for release?

Of course...the build will break after a release because the new changes.xml won't have a section for the new release version. Come to think of it, will that even work? Since the CI sees a SNAPSHOT version, and the changes.xml doesn't include SNAPSHOT. David C. Hicks wrote: Good suggestion. I

Re: maven-changes-plugin: automatic update for release?

is capable of handling that difference. Thanks again, Dave Kalle Korhonen wrote: On Wed, Nov 18, 2009 at 1:46 PM, David C. Hicks dhi...@i-hicks.org wrote: Of course...the build will break after a release because the new changes.xml won't have a section for the new release version. Come

Re: -DskipTests=true gets ignored

I think it's an order-of-evaluation problem. I suspect that your -DskipTests=true is getting overridden by the property in your pom.xml. Yaakov Chaikin wrote: Ok, Checked documentation, googled. Still not understanding why the following is happening. I have a multi-module project. In the

Re: -DskipTests=true gets ignored

this? Thanks, Yaakov. On Thu, Nov 12, 2009 at 5:23 PM, David C. Hicks dhi...@i-hicks.org wrote: I think it's an order-of-evaluation problem. I suspect that your -DskipTests=true is getting overridden by the property in your pom.xml. Yaakov Chaikin wrote: Ok, Checked documentation

Re: -DskipTests=true gets ignored

that don't hit any outside resources like a DB). How would I do that? Thanks for your help! Yaakov. On Thu, Nov 12, 2009 at 5:49 PM, David C. Hicks dhi...@i-hicks.org wrote: I generally use a Profile when I want to do something of this nature. So, for your case, you might have something

Re: Suck, cannot build, repository down??

For this very reason, I've set up my builds to only build the full dependency report when I specify it - normally for nightly and release builds. It keeps my development and continuous integration builds short and sweet. It's a simple thing to activate a profile for the longer builds to produce

Re: Maven-release-plugin checking in the pom twice

Typically, you will be developing a SNAPSHOT version of the release version. In other words, you might be working on 3.0-SNAPSHOT. When you do the release, you should release 3.0. Your next development version would then be 3.1-SNAPSHOT. Your submodules will generally have the same version as

Re: Question from a Maven NewBie. Can not run any mvn goal.

Do you have a proxy that you must use to get to the Internet for browsing? Something is blocking you from downloading the various plugins that Maven requires to run. KDLS wrote: I am new to the Java, Maven, etc. I just downloaded and installed Maven. Followed all their instructions. I can

Re: Newbie question about defining goals

build pluginManagement plugins plugin groupIdgroup/groupId artifactIdp/artifactId version1.0/version /plugin plugins pluginManagement plugins

Re: maven-release-plugin, svn and parent pom.xml

Owen, I've only ever seen this done with the SCM setup mirroring the local setup (ie. all projects located beneath the parent within the SCM). If you can, it may be worthwhile to move those projects. I've found that trying to make Maven (and plugins) behave in a way that isn't natural to

Re: How to update parent during release:prepare

The autoVersionSubmodules property can be used to tell the release plugin to use the Parent's version for all of the child modules. Are your modules all the same version as your parent? If so, then it should work as-is. I normally use the command: mvn -DautoVersionSubmodules=true

Any integration with Version One ? (maven-changes-plugin)

My group is being forced, more or less, to use this project planning and tracking system, called Version One. -- http://www.versionone.com/ Since all of the information about stories, fixes, etc. will be kept in this location, it would be really cool to be able to get that information into the

Re: inject version into source?

I have done this by setting up a properties file that gets filtered at build time. Then, I use that properties file in a Spring PlaceholderConfigurer to get the value injected where I need it. James Russo wrote: Hello, New maven user here. Really am liking it, just trying to get project

Help with batch-mode release?

I'm trying to set up a script to handle an automated release process. I'm using the releaseVersion and developmentVersion properties to give me some flexibility with respect to the assigned versions. However, they don't seem to be sticking. For instance, my current version is 0.9.27-SNAPSHOT.

Re: Help with batch-mode release?

/prepare-mojo.html -Original Message- From: David C. Hicks [mailto:dhi...@allureglobal.com] Sent: Thursday, August 27, 2009 12:51 AM To: Maven Users Subject: Help with batch-mode release? I'm trying to set up a script to handle an automated release process. I'm using the releaseVersion

Re: Help with batch-mode release?

want to go slowly Good luck Arnaud DOSTES -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Thursday, August 27, 2009 3:41 PM To: Maven Users List Subject: Re: Help with batch-mode release? Tried autoVersionSubmodules last night. It didn't appear to work

Help with batch-mode release?

I'm trying to set up a script to handle an automated release process. I'm using the releaseVersion and developmentVersion properties to give me some flexibility with respect to the assigned versions. However, they don't seem to be sticking. For instance, my current version is 0.9.27-SNAPSHOT.

Re: Help with batch-mode release?

I had already gone through that page. It was just not real clear to me if one must really specify the version for each module in a multi-module batch build. At your suggestion, I added autoVersionSubmodules to my command line, but that didn't have any noticeable effect on the result. The new

Assembly will not deploy.

Hi, I have a module in my project that creates an assembly to be deployed to our Nexus repository - only the assembly won't deploy. This was working until this particular build. I've been using the deprecated attach goal to cause the assembly to be added to the list of artifacts to be

Re: Profile Activation Help?

Yes. I also tried adding the inherited tag with the plugin defined in the build section (not as a profile). I got the same result. The children still executed the plugin. I defined it to execute on the deploy phase. Stephen Connolly wrote: Are you saying that if you do sth like this:

Profile Activation Help?

I'm trying to get a profile to activate for my parent project but not for the children. Unfortunately, the children inherit from the parent to get dependency information. So, they also inherit everything else. My solution (or so I thought) was to use the project.artifactId property in my

Re: Profile Activation Help?

That would substitute the actual name of the artifact in the name tag, though, wouldn't it? Jonathan Woods wrote: ${project.artifactId} might help. Jon -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: 10 August 2009 18:12 To: Maven Users Subject

Re: Profile Activation Help?

the trick for me. I thought I'd share what I found for posterity. Dave David C. Hicks wrote: I'm trying to get a profile to activate for my parent project but not for the children. Unfortunately, the children inherit from the parent to get dependency information. So, they also inherit everything

Re: Profile Activation Help?

I take it back. That doesn't help me, either. I guess once the profile has been activated at the parent POM level, it stays that way for all the children. David C. Hicks wrote: I must have been blind when reading through my MDG last night. I found what I believe will be my solution

Re: Profile Activation Help?

. Hicks dhi...@i-hicks.org I take it back. That doesn't help me, either. I guess once the profile has been activated at the parent POM level, it stays that way for all the children. David C. Hicks wrote: I must have been blind when reading through my MDG last night. I found what I

Re: Profile Activation Help?

/file /activation Since this is the only module that will have a changes.xml file, this should do the trick for me. I thought I'd share what I found for posterity. Dave David C. Hicks wrote: I'm trying to get a profile to activate for my parent project

Site generation - no index.html for modules.

I still haven't figured out why I get no index.html files for my sub-modules (or even if I should). It seems to me like it was working fine just a week or two ago, then something changed to cause it not to work. Anyway, I started creating index.apt files in all of my modules (bowing to the

problem with maven-changes-plugin in a multi-module project

Hi folks, I've got a multi-module project in which I'm using the Changes plugin to publish both a page in the site and an announcement email at release time. However, I only have a changes.xml file at the Parent project level. My release blows up because it cannot find changes.xml in the

Default index.html from Site plugin?

Is there some way to get the Site plugin to create an index.html if one is not supplied? I really don't want to have to go set up src/site for every module in my project, but it seems like the site that gets generated won't work if I don't. When I click on one of the module links, I'm taken to

Release from branch - Subversion is not happy.

I am getting this error when attempting to release:prepare from a branch: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22'

Re: Default index.html from Site plugin?

#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site David C. Hicks wrote: Is there some way to get the Site plugin to create an index.html if one is not supplied? I really don't want to have to go set up src/site for every module in my project, but it seems like the site that gets generated won't work

Re: Release from branch - Subversion is not happy.

, Aug 6, 2009 at 5:53 AM, David C. Hicks dhi...@i-hicks.org wrote: I am getting this error when attempting to release:prepare from a branch: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source

Site deploy - missing site descriptor?

I keep getting the error Missing site information in the distribution management element in the project.., but I clearly have a site descriptor in that section... site idags-utilities.allureglobal.com/id nameAGS Utilities/name url${site.deploy.base}/url

Re: Site deploy - missing site descriptor?

Oops! Nevermind. Chalk this one up to blondness. :-) David C. Hicks wrote: I keep getting the error Missing site information in the distribution management element in the project.., but I clearly have a site descriptor in that section... site idags

Text documents from APT ?

Pardon my ignorance, please. Is there a way to generate a nice looking text document out of an APT file? Surely, there's a plugin for doing that. I'd love to publish my release notes as part of my project site but still retain the ability to produce a text document (for those who just can't

Re: Text documents from APT ?

-plugin to manage release notes and to generate text-only announcement emails. This may help: http://maven.apache.org/plugins/maven-changes-plugin/ On Mon, Aug 3, 2009 at 12:01 PM, David C. Hicks dhi...@i-hicks.org wrote: Pardon my ignorance, please. Is there a way to generate a nice

Re: Text documents from APT ?

reports reportchanges-report/report /reports /reportSet /reportSets /plugin /plugins /reporting On Mon, Aug 3, 2009 at 3:44 PM, David C. Hicks dhi...@i-hicks.org wrote: Thanks for the tip, Ryan. I like

Help with branching?

Hi gang, I need to branch from a prior release tag to fix a defect. I thought I had the right process, but something is not happy. We do have the project enabled for the maven-release-plugin. Here are the steps I took: 1) Check code out of SVN from the previous release tag. 2) Using

Re: Help with branching?

I guess I was wrong...it *did* screw up my tagged code. Now, I have to figure out how badly and get that all fixed, too. Why would the release:branch goal put changes back into the source tree? David C. Hicks wrote: Hi gang, I need to branch from a prior release tag to fix a defect. I

Re: Help with branching?

it and throws an error. I assume that when this happens, the release plugin loses itself and ends up checking the pom.xml changes back into the tags folder instead of branches. Maybe someone else will find this information useful in the future. Dave David C. Hicks wrote: I guess I was wrong...it *did

Re: How can I deploy multiple wars using the tomcat plugin in maven?

The first question is relatively straightforward. Since your wars are created in different projects, just set up a third project that has the artifact WAR files from the other two as dependencies. If your war files are generated in different modules of the same project, you would accomplish the

Re: How can I deploy multiple wars using the tomcat plugin in maven?

Oh, no, you misunderstood my intention. You don't build a war file using the two other wars as a dependency. The only reason you make them dependencies is to make them available to the plugin for deployment. Your third project doesn't really have its own artifact, other than the *.pom file. nagl

Re: [ANN] Maven Project Info Reports Plugin 2.1.2 Released

Dennis Lundberg wrote: David C. Hicks wrote: Maybe I misunderstand the meaning of some of this message. MPIR-160 is listed in the release notes. Does this mean it should be fixed in this release? I bumped the version of this plugin in my current project. It still seems

Re: [ANN] Maven Project Info Reports Plugin 2.1.2 Released

Maybe I misunderstand the meaning of some of this message. MPIR-160 is listed in the release notes. Does this mean it should be fixed in this release? I bumped the version of this plugin in my current project. It still seems to be fetching artifacts remotely. Dave Dennis Lundberg wrote: The

Re: quick question: set version for deploy

The version is normally bumped by the maven-release-plugin. The typical release process would look like: mvn release:prepare mvn release:perform In general, the whole process does several things: change the version from SNAPSHOT to a release form, build your code to make sure it will build and

Re: help with multi-module build

It's hard to say from your description, but it sounds like you need to do some serious restructuring of your project. Here's what I think you need to have: base-of-project/ pom.xml myproj-plugin/ pom.xml src/main/scala code goes here myproj-base/ pom.xml

Re: help with multi-module build

files in those sub-directories. It's possible that using mvn compile could be part of your problem. When you only run the compile goal, you don't get to the package goal, which is when the jar file would be created. Nicholas Tung wrote: On Tue, Jul 21, 2009 at 9:47 PM, David C. Hicks dhi...@i

Re: Creating multiple artifacts for a single project

Chetan Sarva wrote: While it feels like unnecessary overhead, having the second project makes things a bit more flexible in the end. You'll find that having your code split apart will also lead you down the path to better interfaces. So, that extra overhead will pay big dividends in the

Surefire/Cobertura roll-up reports?

In a multi-module project, is it possible to get Surefire and/or Cobertura to roll up their results at the top-most level? I haven't found anything that leads me to believe they can. Figured it was time to inquire. Thanks, Dave

Re: Surefire/Cobertura roll-up reports?

Adam Purkiss wrote: As for surefire - no idea, but using Hudson as our CI tool I have it setup to roll up the Junit results to a top level using its reporting. We use Hudson, as well, but we've noticed that between Surefire and Cobertura, we end up with two or three copies of each test

Re: Surefire/Cobertura roll-up reports?

I'll have a closer look at our Hudson configuration. Someone else set the server up originally. I should not assume that everything is optimal. Thanks for the feedback! Adam Purkiss wrote: I see, The setting I have for publish JUnit results is: **/target/surefire-reports/*.xml and I have

Re: Resource filtering is escaping backslashes.

(and I have planned to do this in the next weeks). -- Olivier [1] http://jira.codehaus.org/browse/MRESOURCES-81 2009/7/15 David C. Hicks dhi...@i-hicks.org: Hi guys, One of the fellows working on my project is suddenly having a problem with one module. We've narrowed down the problem

Re: escape ${some-value}

Hi Jane, I just happened to be looking for other information about escaping when I saw your question. Looks like you can use: \${foobar} To cause the literal to be used. Here's a link to the page where I found this: http://maven.apache.org/shared/maven-filtering/ Dave Jane Young wrote:

Re: escape ${some-value}

This may be of relevance, too... http://maven.apache.org/plugins/maven-resources-plugin/examples/escape-filtering.html David C. Hicks wrote: Hi Jane, I just happened to be looking for other information about escaping when I saw your question. Looks like you can use: \${foobar

Re: escape ${some-value}

You can configure other directories to be considered for filtering. I'm not familiar with configuring the JAR plugin to add entries to the Manifest, though. So, I'd be out of place trying to offer any advice on that. Jane Young wrote: Hi David, Thanks for responding. Looks like escaping

Re: site.xml for parent/child site which are siblings

change the skin in site.xml) Thanks, mohan kr -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Tuesday, July 14, 2009 6:57 PM To: Maven Users List Subject: Re: site.xml for parent/child site which are siblings I would really like to know if you're using

Re: site.xml for parent/child site which are siblings

Thanks for the workaround, Benson. I was able to get it to work in my little test project. Now, I'm going after the big project. Benson Margulies wrote: yes On Wed, Jul 15, 2009 at 2:50 PM, jaybytezjayby...@gmail.com wrote: Is this the post:

Re: exclude format for assembly descriptors

This is an excerpt from my assembly.xml. It uses the Maven style descriptors for inclusion. Versions are assumed to be those referenced by the module (or in dependency management). dependencySets dependencySet includes

Resource filtering is escaping backslashes.

Hi guys, One of the fellows working on my project is suddenly having a problem with one module. We've narrowed down the problem, but I have no idea why it's happening. One of the resources in the test/resources tree gets filtered with the ${project.build.directory}. In his case, he gets a lot

Re: site.xml for parent/child site which are siblings

Thanks for the workaround, Benson. I was able to get it to work in my little test project. Now, I'm going after the big project. Benson Margulies wrote: yes On Wed, Jul 15, 2009 at 2:50 PM, jaybytezjayby...@gmail.com wrote: Is this the post:

Re: site.xml for parent/child site which are siblings

Benson Margulies wrote: I've filed a JIRA on this and also posted a workaround, you have to set up the URL for each project yourself. If you can't find my posted workaround I can post it again. Benson, can you give us a JIRA number? I didn't find anything that appeared to be the right one

Re: site.xml for parent/child site which are siblings

I would really like to know if you're using the menu ref=parent/ and if it works?? I've been playing with it for the better part of two days, and I cannot get the parent link to show up at all. I've also been playing with breadcrumbs, but they appear to be severely broken - or, I just don't

Re: exec:java problem

The warning you get is fairly standard. It happens when you don't declare the character set encoding that you want to use for the copying of resources. This probably has nothing to do with your error. The error is indicating that the class org.sonatype.mavenbook.weather.Main does not exist.

Re: exec:java problem

Did you check to make sure that the class was in the target/classes directory? The UTF-8 encoding is normal on Linux. That's the default encoding when one is not specified. ykyuen wrote: Hi all, i just did the same thing in Linux environemt. the program can be executed without any

Re: Examples of multi-module site generation?

with that configuration, I didn't figure it out when it does not work well, but there are some cases that it doesnt. Good Luck with that.. :-) On Mon, Jul 13, 2009 at 5:54 AM, David C. Hicks dhi...@i-hicks.org wrote: Can anyone point me to anything that actually works? I've tried every example I can

Re: Dependency Report searching outside repositories?

fixed. But I'm able to get around this by setting the plugin configuration dependencyLocationsEnabled to false and dependencyDetailsEnabled to false Thanks, mohan kr -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Saturday, July 11, 2009 2:56 PM

Examples of multi-module site generation?

Can anyone point me to anything that actually works? I've tried every example I can find via Google (what few there are), and I cannot get the modules to generate a link back to the parent project. Breadcrumbs don't seem to behave, either. Maybe I'm an oddball and the only person who doesn't

Dependency Report searching outside repositories?

It looks to me like the Dependencies report, created during site generation, is searching external repositories to find the information it needs. But, it seems like that information should already be in my local repository, assuming that the code had to be built before we can generate the site.

Re: Dependency Report searching outside repositories?

fixed. But I'm able to get around this by setting the plugin configuration dependencyLocationsEnabled to false and dependencyDetailsEnabled to false Thanks, mohan kr -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Saturday, July 11, 2009 2:56 PM

Site generation tutorials?

Is there a decent tutorial out there anywhere on how to build the project site within Maven? I've found nothing that I would consider useful. MDG is rather short on details, too. I've got a multi-module project that I'm trying to get the site built and deployed for. It seems to build, but

Re: How can I set maven memory size?

Seems like I remember seeing a way to specify it on the Maven command line, but I can't recall the details. youhaodeyi wrote: Can I use it as command line argument instead of setting environment variable? dchicks wrote: set the MAVEN_OPTS environment variable... export

Re: How can I set maven memory size?

set the MAVEN_OPTS environment variable... export MAVEN_OPTS=-Xms256m -Xmx1024m Something like that. youhaodeyi wrote: I got a maven project and compile it by maven. Then I got the error java.lang.OutOfMemoryError: Java heap space. How can I set the memory size running mvn command?

Re: Build gets extra dependencies.

with it, right now. I'll just have to accept that we're in good shape (for now) and move on. Weird! Jörg Schaible wrote: David C. Hicks wrote at Mittwoch, 1. Juli 2009 00:18: I've got an automated build that runs on Hudson that is producing a WAR that cannot load and run. It appears

Build gets extra dependencies.

I've got an automated build that runs on Hudson that is producing a WAR that cannot load and run. It appears that it is picking up extra dependencies during the build process. One of those is spring-2.0.6.jar. I believe this is causing my load/run problem because the error I get is related to

Document Artifacts - HOWTO?

I'm sure there is an accepted way of handling this problem, but I haven't found it, yet. I have a text document (release notes) that I need to include in my assembly. Right now, I just use a FileDependency tag in the assembly.xml to go grab the document from its module. The document lives in

Re: Quandary over testing support classes.

Barrie Treloar wrote: 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) Almost, but not quite. TestSupport does depend on Model, because it includes the

Re: Quandary over testing support classes.

Barrie Treloar wrote: 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) Almost, but not quite. TestSupport does depend on Model, because it includes the

Re: Quandary over testing support classes.

Matt Brown wrote: Is it possible for you to refactor the TestSupport classes that the Model unit tests depend on into a third artifact, which both projects (Model and TestSupport) can then rely on (with scope=testing)? That's essentially what I've been working on the last hour or so.

Re: Quandary over testing support classes.

Matt Brown wrote: Is it possible for you to refactor the TestSupport classes that the Model unit tests depend on into a third artifact, which both projects (Model and TestSupport) can then rely on (with scope=testing)? That's essentially what I've been working on the last hour or so. So,

Re: Quandary over testing support classes.

Barrie Treloar wrote: You have a cyclic dependency. The solution is to break the cycle. There isn't another way. Your choices on breaking it are: * Move TestSupport into Model (not ideal) * Move the code in Model that TestSupport relies upon into its own module. Yeah, that's what I

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

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.

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

Re: Just shoot me now and get it over with

Did you happen to do anything funny to your Eclipse workspace? I believe that those variables are kept in a hidden file in your workspace. Perhaps you just have a corrupt file of some kind. Steve Cohen wrote: I am working in a sort of bastardized Eclipse-maven world for months now. I have had

How to efficiently configure a transient repository?

Hi gang, We have a Maven plugin that we use to provide a packaging type for our Integration Test module. It resides in our Nexus repository at the office. When we work there, all is good. When we work at home, however, is a different story. Sometimes we may be connected to the office via our

How to efficiently configure a transient repository?

Hi gang, We have a Maven plugin that we use to provide a packaging type for our Integration Test module. It resides in our Nexus repository at the office. When we work there, all is good. When we work at home, however, is a different story. Sometimes we may be connected to the office via our

Re: Is maven so inflexible?

I think the maven-dependency-plugin is probably what you need to use, in this case. On 4/21/09 5:52 AM, João Pereira wrote: Here's the scenario I have a the Alfresco SDK which depends on a lot of libraries, some of them I can find in the standard repos, others I don't. I wish that the SDK

Re: Is maven so inflexible?

Are the jars part of the project, or are they artifacts that you depend on? That seems to be a large part of what you may need to change. If the jars are artifacts that can be found in a standard repository, just mark them up as dependencies. If they are generated by your project, they

Help with patching a release?

Hi gang, I need to apply a small patch to a project that has already been released. In general, I understand that I need to branch the tag under which the code was released, make the change, then create a new release. I'm running into a problem, I guess with the release plugin, though.

Re: Help with patching a release?

. -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Friday, April 03, 2009 12:32 PM To: Maven Users Subject: Help with patching a release? Hi gang, I need to apply a small patch to a project that has already been released. In general, I understand that I need

Re: Help with patching a release?

with patching a release? Easiest thing is to roll the poms to a snapshot and then do a traditional release. This assumes that the project you are patching is your own and the scm info is correct. -Original Message- From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Friday, April 03, 2009

Re: Using release plugin to build scm project

Check the archives over the last month and you'll find plenty of discussion on this subject. :-) My own solution was to set my preparationGoals=clean install Todd Thiessen wrote: I made a change to the scm project to fix a bug that was bugging me. Built the 1.3-SNAPSHOT version of the latest

Re: Maven Release release:prepare / perform etc.

Hey Karl, This issue has been coming up quite a bit, lately. Some will disagree with me, but here is my solution to this problem. mvn release:prepare -DpreparationGoals=clean install The release:prepare normally only does a packaging, so the install step never happens. It really should

Re: Release plugin and multimodule interdependent childs

There was a pretty long thread about this exact issue about two or three weeks ago. I encountered the same issue. My solution, eventually, was to use the preparationGoals property when I run release:prepare to force an install. The problem appears to be that maven-release-plugin fails to

  1   2   3   >