Re: maven adding wrong jar files in war lib

2009-03-14 Thread agent59624285
I have attached the pom file. If I generate war file from an empty project (without any source code), I get correct jar files in the war file. But when my source code is present, it adds asm-1.5.3.jar, asm-attrs-1.5.3.jar, cglib-2.1_3.jar,xml-apis-1.0.b2.jar, .. etc .. (as I said previously, these

Re: How can I force maven download dependency?

2009-03-14 Thread Wendy Smoak
On Tue, Mar 10, 2009 at 3:20 AM, Sahoo wrote: > Although this is a core assumption in maven, many people don't know this. > The question that I have is why does maven not try to protect itself from > human error? Should mvn-deploy not refuse to overwrite an artifact by > default? You might want

Re: Corporate pom naming conventions

2009-03-14 Thread Blake Martin
We call ours the "standards" POM, as that's what's in there; it contains our standard plugin executions and default versions/scopes of certain artifacts (such as jsp-api) which are managed by the container. On Fri, Mar 6, 2009 at 2:09 AM, Merv Green wrote: > This post, > http://www.sonatype.com/

Re: [Surefire plugin] Executing test "typologies"

2009-03-14 Thread Blake Martin
Have you consider using test suites? You'd have to explicitly specify what tests belong to which test suites, but it should get the job done. http://open.ncsu.edu/se/tutorials/junit/#section3_0 This also can be used to solve the problem of tests executing in a specific order; some of our Selenium

Re: archetypes location

2009-03-14 Thread Wayne Fay
> Where are these located? In http://repo2.maven.org/maven2? http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-catalog.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For addi

Re: How can I force maven download dependency?

2009-03-14 Thread Blake Martin
I can definitely confirm that deploy overwrites the previous deployment; it never "ignores" the new version. However, as Stephen mentioned above, if you deploy twice and you have the artifact from the first deployment in your local repository, you'll have to delete it in order to get the new versio

archetypes location

2009-03-14 Thread ChadDavis
When I run mvn archetype:generate, I get a list of 41 archetypes. Where are these located? In http://repo2.maven.org/maven2? If so, why doesn't it pick up the struts 2 archetypes that are also inside of that repo? - To unsubscri

Install phase ignore in command: mvn -e install jboss:deploy

2009-03-14 Thread Nafter
Before I want to deploy my WAR to Jboss, I want maven to generate the WAR first. Normally when I only enter: mvn -e install all dependent jars are created, and finally the WAR is created. So each java change is taken into the new WAR. Now I just want to add the 'jboss:deploy' command in order t

Re: Problem in release:prepare

2009-03-14 Thread Stephen Connolly
I have read reports that svn compiled with serf and not neon works with tagging no problemo I'll have a shot at confirming this on monday -Stephen 2009/3/14 Olivier Lamy > Hi Folks, > I have added some proposals here : http://jira.codehaus.org/browse/SCM-262 > > Comments are welcome ! > Th

Re: Problem in release:prepare

2009-03-14 Thread Olivier Lamy
Hi Folks, I have added some proposals here : http://jira.codehaus.org/browse/SCM-262 Comments are welcome ! Thanks, -- Olivier 2009/3/14 Jochen Wiedmann : > On Fri, Mar 13, 2009 at 11:43 PM, Edelson, Justin > wrote: > >> This looks like http://jira.codehaus.org/browse/SCM-406. Run svn up and >>

Re: Problem in release:prepare

2009-03-14 Thread Jochen Wiedmann
On Fri, Mar 13, 2009 at 11:43 PM, Edelson, Justin wrote: > This looks like http://jira.codehaus.org/browse/SCM-406. Run svn up and > rerun release:prepare. Thanks for the hint, Justin! -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because

Re: maven adding wrong jar files in war lib

2009-03-14 Thread Baptiste MATHUS
Dependency:tree shows every jars transitively. If you want to compare the war content and something other, use dependency:list instead. Anyway, which jar is listed in the dependency:tree that you think should be included in the war and isn't? Please show us the corresponding block part from your