[jboss-dev] AS trunk is broke

Stan Silvert ssilvert at redhat.com
Fri Jun 4 08:51:47 EDT 2010


Jaikiran Pai wrote:
> As an aside, are SNAPSHOT dependencies of non-AS modules, like this 
> one, allowed in AS trunk?
This is an AS module.  Is there some reason I need to do a release at 
this point in development?  That's rather time-consuming.  I wasn't 
planning to do a release until we get closer to code freeze.
>
> -Jaikiran
> Stan Silvert wrote:
>> Just a guess, but maybe your settings.xml is not set up for the JBoss 
>> snapshot repo?
>> http://community.jboss.org/wiki/MavenGettingStarted-Developers
>>
>> Andrew Dinn wrote:
>>>  > Some of us had seen the checksum errors (there's a mail in this dev
>>>  > list) too. It kept slowing down the build, but I ignored it. As 
>>> for the
>>>  > other error you are seeing, could you post the build logs? And what
>>>  > command do you use to build the trunk? From what I know, the 
>>> recommended
>>>  > way is to mvn clean install from the trunk root.
>>>  >
>>>  > P.S: I think we should really have the hudson.qa instances build 
>>> the AS
>>>  > trunk against a clean repo using the *public* repo. Right now, 
>>> it's just
>>>  > a false impression that the AS trunk is building fine.
>>>
>>> I initially used bash build.sh in the build directory. However, 
>>> after posting I retried using mvn clean install and the source of 
>>> the problem became more evident:
>>>
>>> [INFO] [dependency:unpack {execution: unpack}]
>>> [INFO] Configured Artifact: 
>>> org.jboss.jsf.integration:jboss-jsf-deployer:1.0.0-SNAPSHOT:jar
>>> [INFO] 
>>> ------------------------------------------------------------------------ 
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO] 
>>> ------------------------------------------------------------------------ 
>>>
>>> [INFO] Unable to find artifact.
>>>
>>> Embedded error: Unable to download the artifact from any repository
>>>
>>> I assume this is why the deployer was not found.
>>>
>>> regards,
>>>
>>>
>>> Andrew Dinn
>>> -----------
>>>
>>>   
>>
>>
>





More information about the jboss-development mailing list