I've thought about using ivy to resolve JavaScript frameworks. Is this a bad idea?
On Tue, Jun 23, 2009 at 5:36 AM, Joshua Tharp<[email protected]> wrote: > I understand what you are asking. It's not whether or not you CAN publish > these things, it's a question of SHOULD you do it. > > I publish a zip file installation package, but since I deliver my war file > in an ear, and I build it as part of a multi-module build (never by itself) > I chose not to publish the war to the repository separately. > > Josh > > On Mon, Jun 22, 2009 at 7:08 PM, Kevin Gann <[email protected]> wrote: > >> Yes. I know that I can publish anything, but didn't know if there was a >> reason why jar files are used in all the examples, defaults, etc... I >> suppose it's just that it's the most common Java artifact... >> >> 2009/6/22 Georges Labrèche <[email protected]> >> >> > You can publish any file type you want. Just be sure to do the >> appropriate >> > configuration in the ivy file with the publication tag. For instance: >> > >> > <publications> >> > <artifact name="MyWarArtifact" type="war" ext="war"/> >> > </publications> >> > >> > -----Original Message----- >> > From: Kevin Gann [mailto:[email protected]] >> > Sent: Monday, June 22, 2009 8:53 PM >> > To: [email protected] >> > Subject: publishing war/ear files... >> > >> > All, >> > >> > Since Ivy defaults to jar files I'm curious what best practices are. I >> have >> > an ear that depends on a war is it common to publish war files? >> > >> > Thanks... >> > >> > -- Richard Hauswald Blog: http://tnfstacc.blogspot.com/ LinkedIn: http://www.linkedin.com/in/richardhauswald
