OK sounds I'm making confusion with other projects :) I'll investigate
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:58 PM, sebb wrote:
> On 14 October 2011 14:50, Simone Tri
On 14 October 2011 14:50, Simone Tripodi 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
just to speak about it: what about putting the .vm template in the
remote-resources that bring the LICENSE and NOTICE txt files?
If it could work, we could put as well basic assemblies descriptor -
and components that require customization can easily modify them...
Simo
http://people.apache.org/~s
On 14 October 2011 14:02, Simone Tripodi 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
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!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://ww
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 sa
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://peop
Ok,
then no objection from my side.
Sent from my mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 14.24, "Simone Tripodi" ha
scritto:
> having the changes.xml is what we already do in all other Commons
> component, for the specific reason that the JIR
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
having the changes.xml is what we already do in all other Commons
component, for the specific reason that the JIRA report just collect
the list of fixed issues, collecting changes allows grouping them by
release.
+1 for changes
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.liv
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
wrote:
> Jiira is also able to compute release notes.
>
> ATM I can't, I will post a link later.
>
> Sent from my mobile device, so please excu
Jiira is also able to compute release notes.
ATM I can't, I will post a link later.
Sent from my mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 13.34, "Christian Grobmeier" ha
scritto:
> Hey guys,
>
> i would like to suggest we make consequent use
Hey guys,
i would like to suggest we make consequent use of changes.xml.
Whatever we do, we should open an issue, fix the stuff, and then add a
comment to changes.xml. We do this in log4php and I feel it is very
good: you always can find the changes per issues (via Fisheye- just
check in with the
13 matches
Mail list logo
