Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3741511E9D for ; Wed, 2 Apr 2014 10:59:19 +0000 (UTC) Received: (qmail 15089 invoked by uid 500); 2 Apr 2014 10:59:14 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 14905 invoked by uid 500); 2 Apr 2014 10:59:09 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 14860 invoked by uid 99); 2 Apr 2014 10:59:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 10:59:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of anders.g.hammar@gmail.com designates 209.85.212.173 as permitted sender) Received: from [209.85.212.173] (HELO mail-wi0-f173.google.com) (209.85.212.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 10:58:59 +0000 Received: by mail-wi0-f173.google.com with SMTP id z2so5113314wiv.0 for ; Wed, 02 Apr 2014 03:58:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=FvfAls4AB5eXPfAwdFDRAIiQjGyZyJUWf/Zcw2QA0+E=; b=Zmwj6YKy/HON23IbmQCdQxsMz0QoSXJmbUcymH6o+BJ8s0n+mXKWdPGIrZlWnZ8tRk O6DqFB+52yCjuYxR432Jp4Kh1FdMUzcAhaPq6YPQ7V3HX4YIQeCa5julEP4tHp4wU3ab A2LgIAKVfb5p1U2jfdr77LnZwLT5AVge/duThsWUJhz6eKn6TYmWoABwwN/gsKSMHGEu 8yJbKdpfDjEEiHLaCAFj7nBSatipQY/epGwYJvJ0TirVOG5hNghXMfBUf6XUOFp9EkFe 1W8UyxrdVx5TixBYDwCU4fPN7v6BQwECPpErsw/a11kGmwEXo2l/DNWSdXGpZibCT6G3 KPmA== MIME-Version: 1.0 X-Received: by 10.180.98.165 with SMTP id ej5mr923453wib.33.1396436318596; Wed, 02 Apr 2014 03:58:38 -0700 (PDT) Sender: anders.g.hammar@gmail.com Received: by 10.194.200.162 with HTTP; Wed, 2 Apr 2014 03:58:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Apr 2014 12:58:38 +0200 X-Google-Sender-Auth: yqBJg0J8yhGkebSSS9RgWyrezMA Message-ID: Subject: Re: What packaging for Jira excel reports with maven? From: Anders Hammar To: Maven Users List Content-Type: multipart/alternative; boundary=f46d044286c6b8b4db04f60d2a2e X-Virus-Checked: Checked by ClamAV on apache.org --f46d044286c6b8b4db04f60d2a2e Content-Type: text/plain; charset=ISO-8859-1 I categorize different usage of Maven into two categories: A) As a build tool B) As a utility tool A) would be for example building a Java web application, i.e. using the full build lifecycle of Maven. B) on the other hand is where you just want to do one specific "thing", for example generate Java classes from an xml schema or creating a jar of existing Java classes. So the first question is if your usage would fit into A or B? To narrow things down a little bit, do you want this excel file to be generated as part of the build of your software and then deployed together with that to the repository? If so, it would be A. If you're just trying to find a tool to generate this excel file on demand, we would be in B. My point here is that if you're in category A then Maven is absolutely appropriate. At least if you're building everything else with Maven. But if you're in category B, then Maven is just one of many options you have. I would even go as far as saying that there are simpler solutions, one being a shell script (or Windows batch file) where you just have you Java command with the jar on the classpath and the options to have the excel file generated. Using Maven here would just add an additional dependency (to Maven) which could just complicate things. My two cents, /Anders On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang wrote: > I have access to a Jar-file that contains code that: > - Reads an excel file containing a JQL query, the names of the fields > from the JQL results to include in excel, as well as the sheets that > are to be populated > - Talks to Jira, using the Jira REST API, to do the query and extract > the results > - Exports a new excel file populated with the query results > > The Jar-file resides in a plexus archive, so I thought that having a > small maven project, containing a pom.xml and the template excel > spreadshet in src/main/resources/ would be a good match. > > The idea was that I could: > - set the Jar-file containing the excel export code as a dependency > - use exec-maven-plugin to run the Jar > - have the output of exec-maven-plugin (an excel file) as the build > artifact > > But the idea stopped on that I don't know what packaging should be used > for the pom: "jar" didn't seem appropriate, so I tried "pom", but that > doesn't do anything (no target directory created). > > Is maven appropriate for what I'm trying to do? Is there an appropriate > packaging to use? > > Thanks! > > > - Steinar > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > > --f46d044286c6b8b4db04f60d2a2e--