REVERTED MAVEN THIRDPARTY BUILD Re: [jboss-dev] differences between pom.xml / build-thirdparty.xml

[Paul Gier]

See inline answers.

Thomas Diesler wrote:
> Hi Paul,
> 
> do you have documentation on how to publish stuff to the maven 
> repository? The jbossws artifacts need be published properly as well.
> 

There is some information on the wiki here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseRepository
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSnapshotRepository

> How do dependencies work? Previously, when I put a dependency in 
> component-info.xml, the build pulled that dependency in automatically 
> and detected inconsistencies with other modules declaring a dependency 
> on the same artifact.
> 
> http://repository.jboss.com/jboss/jbossws/snapshot/component-info.xml
> 
If the dependency is specified in the pom, then that one will take priority.  If 
the two versions are both transitive, then I believe maven uses a nearest 
dependency first mechanism.  Scott pointed out this jira issue 
(http://jira.codehaus.org/browse/MNG-612).  And there is this discussion in the 
build forum http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131752.

> I publish stuff to bin, lib and resources - how can I do this for the 
> maven repository?
> 

This is also an open discussion in the build forum 
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131803

> BTW, your move to get rid of build-thirdparty.xml was the bravest I've 
> seen so far ;-)
> 

Unfortunately, my first attempt seems to be a failure :(
Hopefully, I can get the remaining issues resolved and try again next week.

> cheers
> -thomas
> 
> Paul Gier wrote:
>> Ok, I will work on this on the branch.  Is there any way we can have a 
>> dependency freeze for a couple days or something, so I can update all 
>> the dependencies to match?  One of the issues I have is that every 
>> time I change dependencies in the pom, the versions change again in 
>> build-thirdparty so I get stuck being constantly out of date.
>>
>> Adrian Brock wrote:
>>> I've committed this change.
>>>
>>> The build before it was reverted it can be found here:
>>>
>>> https://svn.jboss.org/repos/jbossas/branches/maven_thirdparty_temp/
>>>
>>> I'll do a clean checkout and build to make sure it works properly
>>> so unless your adventurous wait for a subsequent message
>>> before resynching. ;-)
>>>
>>> On Thu, 2008-03-13 at 14:53 -0700, Scott M Stark wrote:
>>>> Yes, let's do that. Create a tmp branch to work this out Paul.
>>>>
>>>> Adrian Brock wrote:
>>>>> On Thu, 2008-03-13 at 22:45 +0200, Dimitris Andreadis wrote:
>>>>>  
>>>>>> The components versions in the two files are very much out-of-sync:
>>>>>>     
>>>>> You didn't mention jaxb or the jboss-managed problem?
>>>>>
>>>>> I say we invoke "Bill's rule" and revert back to the previous
>>>>> build until this is working properly.
>>>>> This should never have been committed in this state.
>>>>>
>>>>> The server doesn't even boot, how can people work?
>>>>>
>>>>> I have a working build by
>>>>> 1) reverting
>>>>> build/build.xml
>>>>> build/build-thirdparty.xml
>>>>> testsuite/build-thirdparty.xml
>>>>>
>>>>> 2) rm -rf thirdparty/*
>>>>>
>>>>> 3) build clean most
>>>>>   
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>