[jboss-dev] AS trunk is broke

[Jason Greene]

Yes, to restate. Mainline branches (including trunk) must never include snapshots. 

Also we seem to be doing a pretty bad job at running the testsuite before committing.

On Jun 4, 2010, at 9:26 AM, Brian Stansberry wrote:

> Jason can give the official response, but my understanding is committing 
> a component-matrix/pom.xml that directly or indirectly pulls in a 
> snapshot dependency is verboten.
> 
> During the 6.0.0 M2 dev process we made a brief (IIRC one day) exception 
> to that for Hibernate so we could let hudson run the AS testsuite using 
> their-about-to-be-tagged-final code. I agreed to that only because a 
> Hibernate release really is a big thing; would have taken Steve a full 
> day to do a formal CR for us to test.
> 
> On 06/04/2010 08:04 AM, Jaikiran Pai wrote:
>> Hi Stan,
>> 
>> Stan Silvert wrote:
>>> 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.
>> 
>> By AS module, I meant, a module within the AS/trunk project hierarchy.
>> The jboss-jsf-int appears to be a separate project with its own release
>> cycle
>> http://anonsvn.jboss.org/repos/jbossas/projects/jboss-jsf-int/trunk.
>> The reason, that I am aware of, for restricting (non-timestamped)
>> SNAPSHOT dependencies of such artifacts is because they are not
>> reliable. You never really know which SNAPSHOT you are testing against.
>> I however don't know if this policy has changed now.
>> 
>> regards,
>> -Jaikiran
>>>> 
>>>> -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
>>>>>> -----------
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> 
> -- 
> Brian Stansberry
> Lead, AS Clustering
> JBoss by Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development