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 87ABD10143 for ; Wed, 13 Nov 2013 22:33:28 +0000 (UTC) Received: (qmail 70725 invoked by uid 500); 13 Nov 2013 22:33:26 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 70653 invoked by uid 500); 13 Nov 2013 22:33:26 -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 70645 invoked by uid 99); 13 Nov 2013 22:33:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 22:33:26 +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 ctrueden.wisc@gmail.com designates 209.85.212.49 as permitted sender) Received: from [209.85.212.49] (HELO mail-vb0-f49.google.com) (209.85.212.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 22:33:19 +0000 Received: by mail-vb0-f49.google.com with SMTP id o19so837517vbm.36 for ; Wed, 13 Nov 2013 14:32:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=q33GRVjKSiVmF6j8r2s6p7/RFe0exF0OmANB3K82/UQ=; b=wsbQfJPLQCNKfPas/PmOS34Cl3gOdXDt7mVOFi1sxtwaopnZDQh4bfDHyUvnaIixmU n63HZ2QK2LQ9Sz5+d62xz5kLP7jmUHxFA6PMxJ/afjmi37FUHgWx082A8pZ6pJ02ymqd tTsaK2FMafaHSkmT5H3TWurdz0mSnf2YjQJtrtG1Av7tIyYqQZR0BVktip3CE1OPtGNq UwSIn2qVEw5cyEnWBYmegTiAM2lkiMMuh8wFcHY8tf7lNEpis4rF9IZPTyfjesAr7dYe pMU+Mr85YohYiEWqPB2zjEaItJM0elbCeFjifn+T7ugNMNI2lIwPFRwHX4fKoqe0uQAr m+/w== X-Received: by 10.52.28.110 with SMTP id a14mr270173vdh.79.1384381979027; Wed, 13 Nov 2013 14:32:59 -0800 (PST) MIME-Version: 1.0 Sender: ctrueden.wisc@gmail.com Received: by 10.58.24.101 with HTTP; Wed, 13 Nov 2013 14:32:28 -0800 (PST) In-Reply-To: References: <20131112130552.CA3CFC5F@athena.apache.org> <20131113140015.4411D816024@nike.apache.org> From: Curtis Rueden Date: Wed, 13 Nov 2013 16:32:28 -0600 X-Google-Sender-Auth: ilpR28xIZADXja632LiwLAF2Vh4 Message-ID: Subject: Re: Strange issue with generated jars To: Maven Users List Content-Type: multipart/alternative; boundary=20cf3079bc5217f7bf04eb168c51 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3079bc5217f7bf04eb168c51 Content-Type: text/plain; charset=ISO-8859-1 Hi, org.apache.maven.user@io7m.com wrote: > Can anyone else reproduce this problem? OK, I ran the example ("mvn clean package") and the project builds successfully on my system: $ mvn -v Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 10:22:22-0500) Maven home: /usr/local/Cellar/maven/3.1.1/libexec Java version: 1.7.0_45, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac" $ jar tf code/target/code-0.1.0.jar |wc 11 11 270 $ jar tf resources/target/resources-0.1.0.jar |wc 65547 65547 2151861 George Wilson wrote: > the restriction is in regards to building a larger project like a > maven build. Well, it's 38 lines of code: $ find . -name '*.java' | xargs wc 10 18 157 ./code/src/main/java/com/io7m/jarbug/Main.java 28 74 694 ./resources/src/main/java/com/io7m/jarbug/MakeSources.java 38 92 851 total If you just look at it, you can see that it doesn't do anything bad. > I am not sure that it is really necessary to ask people to go out of > their way to build VM systems I am not the OP, and was not asking you to do anything. I was merely inquiring whether you could perhaps avoid your company's bureaucracy via some technical means. > It seems that since you have run this and generated errors, it would > be easier as a first step diagnostic to post your error messages- > output cleaned if need be of course. I agree that it wouldn't hurt for the OP to post his error messages, too. But that said, IMHO, posting a complete example project demonstrating the issue is about the *best* thing you can do. Regards, Curtis On Wed, Nov 13, 2013 at 4:16 PM, George Wilson wrote: > A crippling restriction or not, it is company policy which I do not > have any authority over. Its one thing to try a snippet from stack > overflow but the restriction is in regards to building a larger > project like a maven build. The concern is not being able to evaluate > what the code or individual scripts do. > I do not have time right this minute to set up a VM instance but > perhaps could later on workload permitting. It seems that since you > have run this and generated errors, it would be easier as a first step > diagnostic to post your error messages- output cleaned if need be of > course. FWIW, I am not sure that it is really necessary to ask people > to go out of their way to build VM systems, when the error output > might solve the problem immediately. > > On Wed, Nov 13, 2013 at 11:37 AM, Curtis Rueden wrote: > > Hi George, > > > > That's a new one on me. Can you build in an isolated VM? On a personal > > machine while at work? Not being able to try out code from the Internet > > seems like a crippling restriction to me. > > > > -Curtis > > On Nov 13, 2013 1:34 PM, "George Wilson" wrote: > > > >> Unfortunately, my company's security policies do not allow for the > >> downloading and building of external projects without approval from IT > >> and security so I cannot really test your code (not without going to a > >> committee, etc...). Any chance you can post the errors you are > >> getting? Is this a JVM heap issue perhaps? Have you tried increasing > >> your Java memory? Just a thought since you mentioned that javac is > >> what seems to die here. > >> > >> On Wed, Nov 13, 2013 at 5:57 AM, > wrote: > >> > On Tue, 12 Nov 2013 13:02:46 +0000 > >> > wrote: > >> > > >> >> Hello. > >> >> > >> >> I've run into a strange but easily reproduced problem with the jar > files > >> >> generated by Maven. Essentially, if I generate a jar file containing > a > >> >> large number of files (>= 65536, in practice), then javac becomes > unable > >> >> to resolve classes from that jar file. This only occurs with jars > >> produced > >> >> by the Maven jar plugin, and only when the number of files is large > (as > >> >> demonstrated below). > >> >> > >> >> An example build, using the maven exec plugin to generate a large > >> >> number (65525) of files: > >> >> > >> >> http://waste.io7m.com/2013/11/12/jarbug.zip > >> > > >> > Can anyone else reproduce this problem? This would seem to indicate a > >> serious > >> > bug somewhere. I'm trying to eliminate Maven as a cause. > >> > > >> > M > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > >> > For additional commands, e-mail: users-help@maven.apache.org > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > >> For additional commands, e-mail: users-help@maven.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > > --20cf3079bc5217f7bf04eb168c51--