commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [ognl] Make us of changes.xml
Date Fri, 14 Oct 2011 13:58:13 GMT
On 14 October 2011 14:50, Simone Tripodi <simonetripodi@apache.org> wrote:
> just to speak about it: what about putting the .vm template in the
> remote-resources that bring the LICENSE and NOTICE txt files?

AFAIK, we don't use that.

Anyway, the NOTICE file is specific to each component.

> If it could work, we could put as well basic assemblies descriptor -
> and components that require customization can easily modify them...

I've no idea how to do that.

> Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Fri, Oct 14, 2011 at 3:37 PM, sebb <sebbaz@gmail.com> wrote:
>> On 14 October 2011 14:02, Simone Tripodi <simonetripodi@apache.org> wrote:
>>> I love Seb's approach, if we could specify a way to reuse a shared
>>> template to generate the release note s in every component, without
>>> any extra setting, would be amazing!
>>
>> I looked into that already.
>> I don't remember the exact details, but it was quite complicated and messy.
>> AFAICT it's not possible to include the template in Commons Parent
>> (that only works for site.xml).
>>
>> But of course if a Maven guru can fix it so it's easier to use, please advise.
>>
>> The advantage of the current method is that the template can be
>> tweaked locally if required (but hopefully that's not necessary).
>>
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Fri, Oct 14, 2011 at 2:38 PM, sebb <sebbaz@gmail.com> wrote:
>>>> You can also use changes.xml to produce a release notes text file
>>>> which can be included in the archives (and used in announces if
>>>> required).
>>>>
>>>> This was added to Commons Parent recently:
>>>>
>>>>>>>
>>>> mvn changes:announcement-generate -Prelease-notes
>>>>
>>>> Requires file src/changes/release-notes.vm.
>>>>          A sample template is available from:
>>>>          https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
>>>> <<<
>>>>
>>>> Formatting of the description can be tweaked by using double-space to
>>>> generate a new-line (this does not affect the HTML version).
>>>>
>>>> On 14 October 2011 13:28, Simone Tripodi <simonetripodi@apache.org>
wrote:
>>>>> see my previous message; just to give an example, take a look at the
>>>>> [digester] reports:
>>>>>
>>>>> http://commons.apache.org/digester/changes-report.html (changes.xml
>>>>> introduced only in last release)
>>>>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>>>>
>>>>> does it make sense?
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>>>>> <maurizio.cucchiara@gmail.com> wrote:
>>>>>> I still no have preference, I would like to understand why we should
add
>>>>>> optional work.
>>>>>> If there is a valid reason, why not?
>>>>>> I guess that the next answer is could jiira automatically do what
xml is
>>>>>> able to do?
>>>>>>
>>>>>> Sent from my mobile device, so please excuse typos and brevity.
>>>>>>
>>>>>> Maurizio Cucchiara
>>>>>>
>>>>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <grobmeier@gmail.com>
ha
>>>>>> scritto:
>>>>>> So your preference is to get rid of changes.xml?
>>>>>> Because changes would be visible on the site too....
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>>>>> <maurizio.cucchiara@gmail.com> wrote:
>>>>>>> Jiira i...
>>>>>> --
>>>>>> http://www.grobmeier.de
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-u...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message