[jboss-dev] EAP 5.1.2 build failure

Paul Gier pgier at redhat.com
Fri Jul 1 09:38:30 EDT 2011


On 07/01/2011 05:22 AM, Richard Opalka wrote:
> Hi Folks,
> 
>     I'm trying to build EAP 5.1.2 locally from branch
> 
> https://svn.jboss.org/repos/jbossas/branches/JBPAPP_5_1
> 
> and I'm getting the following error:
> 
> ---
>        [jar] Building jar: 
> /home/opalka/svn/jbossas/branches/JBPAPP_5_1/thirdparty/gnu-getopt/lib/getopt.jar-unsigned
>        [jar] Manifest is invalid: Manifest line "" is not valid as it 
> does not contain a name and a value separated by ': '
> 
> BUILD FAILED
> /home/opalka/svn/jbossas/branches/JBPAPP_5_1/build/build.xml:1467: The 
> following error occurred while executing this line:
> /home/opalka/svn/jbossas/branches/JBPAPP_5_1/build/build.xml:1591: The 
> following error occurred while executing this line:
> /home/opalka/svn/jbossas/branches/JBPAPP_5_1/build/build.xml:1601: 
> Invalid Manifest: null
> ---
> 
> The corrupted artifact is located in:
> 
> http://repository.jboss.org/nexus/content/groups/public/gnu-getopt/getopt/1.0.13/getopt-1.0.13.jar
> 
> If I'm having a look to it's MANIFEST.MF file, it's really corrupted and 
> not fulfilling MANIFEST.MF specification :(
> 
> I'm wondering if it was downloaded from some thirdparty maven repository 
> or we provided it on our own?
> 
> Rio
> 

If you add "?describe" to the end of the URL you can get all the
metadata about the artifact.  If you find the field
"originatingRepository" you can see that this is in our Thirdparty
Releases repository, so it was provided by us.


More information about the jboss-development mailing list