It produces a tgz by executing some code in a couple of jars it depends on that acts on a dependent tgz:
A.jar + B.jar + B.tgz -> unpack B.tgz -> exec plugin on unpacked B.tgz -> assembly plugin to build B-processed.tgz Nothing top secret by any stretch. On Fri, Aug 6, 2010 at 4:20 PM, Ron Wheeler <[email protected]>wrote: > On 06/08/2010 2:48 PM, C. Benson Manica wrote: > >> No, it's not a pom, its purpose is to go download other dependencies and >> repackage them nicely. >> >> So it does produce an artifact. What kind of Artifact? > What exactly are you trying to do. Give enough detail so that someone can > help you. > BTW. It still could be a POM. It might use a plug-in to make something but > I would just be guessing, wouldn't I. > > If you want to get help, you actually have to disclose some facts. > If it is a secret, you need to hire a consultant and have him sign a > non-disclosure after checking his references. not post to a public forum. > > > Ron > > On Tue, Aug 3, 2010 at 4:49 PM, Anders Hammar<[email protected]> wrote: >> >> A pom project? >>> >>> /Anders >>> >>> On Tue, Aug 3, 2010 at 16:22, C. Benson Manica<[email protected]> >>> wrote: >>> >>> Is it possible to configure a Maven project so that it doesn't build or >>>> deploy the main artifact? I have projects that are essentially shells >>>> to >>>> download and package dependencies, but there are no Java sources to >>>> >>> compile >>> >>>> or package as a jar (or anything else). Am I condemned to have empty >>>> >>> jars >>> >>>> deployed along with the artifacts I want, or are there configuration >>>> options >>>> that can address this? >>>> >>>> -- >>>> C. Benson Manica >>>> [email protected] >>>> >>>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- C. Benson Manica [email protected]
