• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: War deploy; maven archetypes problems; web.xml filtering
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: War deploy; maven archetypes problems; web.xml filtering


  • Subject: Re: War deploy; maven archetypes problems; web.xml filtering
  • From: Henrique Prange <email@hidden>
  • Date: Fri, 23 Oct 2009 11:03:17 -0200

Hi Greg,

Mr. G Brown wrote:
I put version 2.1-beta-1 into the archetype created pom and now filtering works! (Maven downloaded many things like maven-filtering/1.0-beta-2, etc. )

I had version 2.1-alpha-1 ; and that didn't work, that appears to be the problem here.

Should the archetype create a pom with a group id for _maven_-war-_plugin?_


The org.apache.maven.plugins groupId is the default groupId for plug-ins. You can suppress this information without problem.


Is there a good way to update plugins?


The versions-maven-plugin [1] can be used to check for plug-in or dependency updates. Take a look at the versions:display-plugin-updates goal and the versions:display-dependency-updates goal.


I think we could use a status page, as all these things change so often, which would have what versions of archetypes, plugins, wolips, etc which are recommended.

Is there a recommended set of plugins which work well together?


Every Maven release comes with a set of basic plug-ins defined in the Super POM. That is why your build uses the maven-war-plugin 2.1-alpha-1 instead of the latest release (2.1-beta-1).


I haven't found problems with the default set of plug-ins defined by Maven 2.2.1. Anyway, it is always recommended to explicitly declare the version of each plug-in used in your build to enforce build reproducibility. IIRC, in Maven 3 this will be a requirement.

In a week (or two)  I'll solicit some ideas.......

The web.xml <http://web.xml> looks better, but I still get error from jetty or tomcat


I don't have WO 5.3.3 on my machine. But I was able to run the 'mvn clean jetty:run-war' command on your sample application with WO 5.4.3 and it worked.


Could you provide more information about the problem? A complete stack trace would be very appreciated.

[1]http://mojo.codehaus.org/versions-maven-plugin/

Cheers,

Henrique
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: War deploy; maven archetypes problems; web.xml filtering (From: Henrique Prange <email@hidden>)
 >Re: War deploy; maven archetypes problems; web.xml filtering (From: Mr.G Brown <email@hidden>)

  • Prev by Date: Re: Can't access a Resource file (was:reading a file form a component NoSuchFileException)
  • Next by Date: Re: reading a file form a component NoSuchFileException
  • Previous by thread: Re: War deploy; maven archetypes problems; web.xml filtering
  • Next by thread: Re: War deploy; maven archetypes problems; web.xml filtering
  • Index(es):
    • Date
    • Thread