Could you set the scope on the dependency to compile? D-
-----Original Message----- From: Jim Stafford [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 12:11 PM To: Maven Users List Subject: Re: Building ear, war without including resources (Maven 2.0) This post shows a code-snippet of how one might do it. I wish I knew of a better way to refer to a specific dependency jar file within Ant so that I didn't need the crude use of fileset. Of course, I also wish the assmebly plugin had direct support for this use case as well. http://www.nabble.com/Maven-2.0---Common-resource-problem-tf2146290.html#a5926085 Marco Mistroni wrote: > Hi, > have same situation in my company. > the quick fix i did was to use the maven-antrun-plugin to copy the > content > of those 'resource's directories int he target\ directory of my project > > that was my quick fix, i m sure some maven guru on the list will have a > better solution > > hth > marco > > On 8/23/06, daniele pirola <[EMAIL PROTECTED]> wrote: > >> >> Hi, >> I am novice in Maven. >> I try to investigate if my company projects could be migrated to Maven >> and I have a question. >> We have building many projects creating ear files or war files without >> the corresponding resources, >> that is for example we deploy an application with an ear file and a >> separate directory called 'etc' with the >> application resources (the directory of course is in the CLASSPATH of >> the server). >> This is done principally to permit changing a property value without to >> have to redeploy the application >> (the application refresh the configuration at intervals). >> >> So the question is: >> can we do this type of build with Maven in an easy way? >> Or we have to write for example our own compile plugin or call an Ant >> task to perform the splitting? >> >> (Also notice that the resources we have to bundle must be filtered and >> not only copied). >> >> Thanks. >> >> -- >> Daniele Pirola >> ICTeam S.p.A >> >> >> --------------------------------------------------------------------- >> 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]
