Re: POM inheritance...

Thanks Shash, I will try your suggestion with the "non keel:maven" 
project.xml in orig.project.xml.

Max

> Max,
>
>> I have found that if I add a dependency to my project.xml file and 
>> then run keel:maven, it sucks in all the new dependencies and 
>> overwrites my POM. However, if I now remove my original dependency, 
>> the keel:maven does not remove the others. Perhaps one way of using 
>> POM inheritance is for keel:maven to create a new inherited 
>> project.xml instead of modifying the original. That way you get to 
>> keep your original and have a base point to return to.
>>
>> The keel:maven goal also removes all comments from the POM files.
>>
>> Then again, I probably misunderstand the POM inheritance. Maybe POM's 
>> can have includes?
>
>
> POMs can have includes, but so far we have not used them.  There are 
> some gotchas....let's say you change the included file....how do you 
> know what project.xml's need their version numbers updated?
> Right now, you have to explicitly change the project.xml, and you know 
> whether to bump up the version number or not.
>
> Here's what I do regarding the problem you bring up.  I keep my "non 
> keel:maven" project.xml in orig.project.xml, do my changes only in 
> that, and right before I do "maven keel:maven" I copy orig.project.xml 
> to project.xml.
>
> Shash
>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>
>
> .
>

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com