provided dep + tomcat:deploy + performRelease = "package XXX does not exist"

src/main/java/br/com/seatecnologia/seaup/negocio/ConvertendoXML.java:5: package com.thoughtworks.xstream does not exist [WARNING] import com.thoughtworks.xstream.XStream; [WARNING] ^ [INFO] Building jar: /Users/alegomes/Documents/tmp/seaup.sea/target/seaup- javadoc.jar thanks Alexandre Gomes

Re: How to pass options to the release plugin's 'goals' option?

Problem solved with -Darguments=-Dmaven.tomcat.url=http://.. option. http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments thanks On 9/24/07, Alexandre Gomes <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm using the release plugin as [1] but, w

How to pass options to the release plugin's 'goals' option?

Hi all, I'm using the release plugin as [1] but, when the plugin calls tomcat:redeploy [2], it ignores the -Dmaven.tomcat.url option. How can I pass a -Dsomething to the goals called by release plugin from -Dgoals option? Is that clear? [1] mvn -e release:perform -P homologacao -Dgoals=tomcat:r

Re: jasperreports-maven-plugin question

Forget about it. That's my fault. It was not compiling the *.jrxml files becauce they were already compiled sometime else. thanks anyway On 9/20/07, Alexandre Gomes <[EMAIL PROTECTED]> wrote: > I found it only happens when sourceDirectory option is specified. The > jasperrep

Re: jasperreports-maven-plugin question

ports []s On 9/20/07, Alexandre Gomes <[EMAIL PROTECTED]> wrote: > What's the criteria used by jasperreports-maven-plugin to conclude > that all reports are up to date and don't need to be recompiled [1]? > How can I force it to compile all the reports? > > [1] >

jasperreports-maven-plugin question

What's the criteria used by jasperreports-maven-plugin to conclude that all reports are up to date and don't need to be recompiled [1]? How can I force it to compile all the reports? [1] [INFO] [jasperreports:compile-reports {execution: default}] [INFO] Nothing to compile - all Jasper reports are

Re: Changing paths in maven-war-plugin

Ooops, sorry. I found it [1] org.apache.maven.plugins maven-war-plugin 2.0 ${basedir}/web [1] http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html thanks On 9/19/07, Alexandre

Changing paths in maven-war-plugin

Hi friends, how can I change the src/main/webapp to other path of my choice? thanks a lot! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat Manager username

Ok Mark, isseu created in [1]. Thanks a lot. [1] http://jira.codehaus.org/browse/MOJO-906 []s Alê! On 9/4/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > On 03/09/07, Alexandre Gomes <[EMAIL PROTECTED]> wrote: > > Hi, > > > > based on [1], how can I pass a dif

NetBeans Visual Webpack with Maven2?

Is it possible to use Netbeans with VWP and Maven2? []s - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat Manager username

Hi, based on [1], how can I pass a diferent username for Tomcat Manager, using -D command option (and not settings.xml) ? I tried -D tomcat.server.username=root, but it doesn't seem to work. [1] http://mojo.codehaus.org/tomcat-maven-plugin/configuration.html thanks Ale! ---

Re: release:prepare must be runned twice?

21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Why would you check in release.properties? AFAIK, it is a more common use > case to let your SCM ignore the release.properties. I guess your > release:prepare would run smooth. > > Hth, > > Nick Stolwijk > > > ---

release:prepare must be runned twice?

Hi everybody. Is that a must to run release:prepare twice to have a release prepared under CVS? Look the sequence below. With CVS, the problem in step 5 always happens but not in SVN. Well, I think release:prepare always changes the release.properties file. So, why isn't the plugin smart enough to

Re: Overriding the plugin depencies

Hi, I tried, but it seems not to work. As Johan said, Maven is still getting the old dep version. Why? The dep resolution is a mystery for me as well :-) thanks Alexandre On 5/26/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 5/25/07, Alexandre Gomes <[EMAIL PROTECTED]> wrote: &

Overriding the plugin depencies

Hi, I'm using a plugin [1] that depends of some library [2]. My question is if it's possible to change the plugin dependency without having to update the local repository. Maybe, there is some pom tag tag I could use to change the plugin dependecy. Actually, I'd like to change the antenna versio