geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <d...@iq80.com>
Subject Re: 'new' build should now work
Date Sat, 03 Dec 2005 23:29:34 GMT
They simply don't work unless they are valid poms.  The transitive  
dependency system basically forces all of the poms to be valid.   
Trust me, we have discussed every possible hack for this and came to  
the conclusion we just need to bite the bullet and fix all the poms.

-dain

On Dec 3, 2005, at 3:15 PM, Jason Dillon wrote:

> Is this a hard requirement to switch?  You can still use the  
> existing maven1 repo in legacy mode to pull any artifacts that do  
> not already exist in the maven2 repo.
>
> --jason
>
>
> On Dec 3, 2005, at 3:11 PM, Dain Sundstrom wrote:
>
>> Hopefully we can be on maven 2 for geronimo 1.1, but we need to  
>> get valid maven 2 poms for every all of our dependencies.  We are  
>> tracking the progress here:
>>
>> http://wiki.apache.org/geronimo/Maven2Conversion
>>
>> -dain
>>
>> On Dec 3, 2005, at 2:15 PM, Jason Dillon wrote:
>>
>>> Is there a plan/timeline for switching to Maven2?
>>>
>>> --jason
>>>
>>>
>>> On Dec 3, 2005, at 2:02 PM, Dain Sundstrom wrote:
>>>
>>>> I just did a full rebuild and it worked perfectly :)
>>>>
>>>> Thanks David!
>>>>
>>>> -dain
>>>>
>>>> On Dec 3, 2005, at 10:21 AM, David Jencks wrote:
>>>>
>>>>> Following some hints from Brett I investigated using the maven  
>>>>> reactor directly and think I've fixed the 'new' build.  So, for  
>>>>> me,
>>>>>
>>>>> maven -o new
>>>>>
>>>>> builds all the geronimo-related projects I have checked out  
>>>>> using the configs/assemblies based build.
>>>>>
>>>>> Please try it and report problems
>>>>>
>>>>> thanks
>>>>> david jencks
>>>>
>>


Mime
View raw message