You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Simone Tripodi <si...@gmail.com> on 2010/08/29 11:03:16 UTC
[Digester] working toward a release
Hi All guys,
since the Commons PMC awarded me giving me the writing rights, I'd
like to work on the Digester to publish a new release, since a new
feature will be contained.
For what I can see, there are few build-related minor issues:
- ant build: dropped in Gump, do we want to maintain it or completely remove?
- maven build: do we want to maintain the current directory structure
or move to the default structure?
- documentation: It would be nice, IMHO, porting the current
documentation from the package.html files to apt format to be included
in the generated site. Existing xdoc can also ported to the apt ormat.
WDYT?
- code: a review wouldn't be bad :P
Please let me know, have a nice day!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Aug 31, 2010 at 12:02 PM, sebb <se...@gmail.com> wrote:
> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Rahul,
>> I just added the xdoc version of the documentation present in the
>> package.html files.
>
<snip/>
Nice. BTW, you can even deploy the site if you mark the menu heading
as "Guide (SVN latest)" or some such. The [digester] site is fairly
well structured so may be deployed between releases.
> The package.html files are normally used to annotate the Javadoc output.
>
> However in this case these files have got a lot more content than is
> normally present in the Javadoc.
>
>> Do you think these last can be removed, since
>> would be redundant with the new developers guide?
>
<snap/>
I checked and it doesn't look like there are a lot of non-Commons
sites that link to the old package guide. So I think its OK to remove
(and we certainly don't want two copies to get out of sync).
> There should at least be minimal package.html files for Javadoc usage,
> so I don't think the files should be removed entirely, but they could
> be replaced with much simpler versions.
>
>> At this stage, we
>> should maintain two different data sources with same information, I'd
>> propose to drop the existing one, but let choose together.
>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>> that contains informations that maven can generate automatically, do
>> you think we can drop it, when dropping the ant build?
>
> +1 to dropping MANIFEST.MF.
>
<snip/>
Yup, its legacy stuff, +1 to removal as well.
-Rahul
>> Thanks in advance, have a nice day!
>> Simo
>>
>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Sep 10, 2010 at 11:53 AM, sebb <se...@gmail.com> wrote:
> On 10 September 2010 08:30, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Seb,
>> thanks for your feedbacks. The problem I have is that even if I omit
>> the password waiting for the prompt, once the builds arrives ad the
>> gpg:sign execution, it is completely blocked :(
>> I'm using gpg 1.4.9, shall I have to upgrade to 2?
>
<snip/>
If your questions are purely related to Maven or its plugins, you may
have better luck (and response time) on the Maven list.
-Rahul
> Current is 1.4.10.
>
> Gpg2 behaves very differently for passwords - it uses a background
> process that caches the password for a while.
>
> Unfortunately, gpg2 does not play well with secret keys on a USB
> stick, see: http://jira.codehaus.org/browse/MGPG-30
>
> For testing purposes, I created a dummy key and added both keyname and
> password as a profile in my local settings file. It's then easy to use
> the test-deploy profile to check that the correct items are created
> and signed.
>
> For example, I just tried:
>
> mvn -Prc deploy -Ptest-deploy -PkeyTest
>
> and it created and signed the Maven and non-Maven artifacts OK.
>> Many thanks in advance, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Thu, Sep 9, 2010 at 9:10 PM, sebb <se...@gmail.com> wrote:
>>> On 9 September 2010 19:54, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi all guys,
>>>> I'm trying to push an RC release, but the gpg plugin execution is
>>>> blocked when signing arifacts :( Follow below my attempts:
>>>>
>>>> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=XXXX\
>>>> -Dgpg.passphrase=XXXX
>>>> mvn release:prepare -DdryRun=true -Dgpg.passphrase=XXXX (the keyname
>>>> is defined as preferred in the gpg.conf)
>>>> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
>>>>
>>>> Do you have any idea why? Many thanks in advance,
>>>> Simo
>>>
>>> I use a profile in my settings.xml which defines the keyname, so I
>>> don't have to remember the hex string.
>>> One can also define gpg.homedir and gpg.executable (if required)
>>>
>>> The password you can omit - it should be prompted for, but how depends
>>> on whether you are using gpg1 or gpg2.
>>>
>>> For testing gpg signing, you can use the new "test-deploy" profile.
>>>
>>> Don't you need to use mvn deploy ?
>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
>>>> <si...@gmail.com> wrote:
>>>>> Hi Rahul,
>>>>> don't worry I won't publish the site before the release; about the
>>>>> Menu reorganization I like the b) too, it is much more coherent with
>>>>> previous releases.
>>>>> Thanks a lot, have a nice day,
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>>> Hi all, Rahul,
>>>>>>> what about the latest deployed website?
>>>>>> <snip/>
>>>>>>
>>>>>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>>>>>
>>>>>>
>>>>>>> Can I proceed modifying the
>>>>>>> homepage in order to propose a release?
>>>>>> <snap/>
>>>>>>
>>>>>> Sure, but please don't deploy it after those changes until the release
>>>>>> is done. Before posting the vote, the site is previewed w/ the rc
>>>>>> profile (-Prc) in the site-deploy command -- this will deploy the site
>>>>>> to the pao/commons/builds area where the other artifacts for the vote
>>>>>> will get posted as well.
>>>>>>
>>>>>> WRT the new additions to the LHS menu, currently we have (indentation
>>>>>> implies nesting):
>>>>>>
>>>>>> Developers Guide (SVN latest)
>>>>>> Core APIs
>>>>>> Plugins
>>>>>> Substitution
>>>>>> XML Rules
>>>>>> Annotations
>>>>>> FAQ
>>>>>>
>>>>>> I see two options for the 2.1 release:
>>>>>>
>>>>>> (a) Use the above (but change SVN latest to 2.1)
>>>>>>
>>>>>> (b) Use the following:
>>>>>>
>>>>>> Release 2.1 (Current)
>>>>>> Guide
>>>>>> Core APIs
>>>>>> Plugins
>>>>>> Substitution
>>>>>> XML Rules
>>>>>> Annotations
>>>>>> FAQ
>>>>>> Javadoc
>>>>>> Release Notes
>>>>>>
>>>>>> Release 2.0
>>>>>> ... (current content for 2.0 menu)
>>>>>>
>>>>>>
>>>>>> I think (b) will work better as it aligns with menu for previous
>>>>>> releases -- note the FAQ indentation in (b) BTW as its different --
>>>>>> WDYT?
>>>>>>
>>>>>> -Rahul
>>>>>>
>>>>>>
>>>>>>> Thanks in advance, all the best,
>>>>>>> Simo
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>>>>> Hi Rahul,
>>>>>>>>> thanks a lot for your feedbacks, actions have been completed following
>>>>>>>>> your suggestions.
>>>>>>>>> my final 2 questions:
>>>>>>>>> - I didn't find any reference on wiki about
>>>>>>>>> ${commons.deployment.protocol}... can we have a private chat?
>>>>>>>> <snip/>
>>>>>>>>
>>>>>>>> Sure, though it helps to have things in the list archives for the next
>>>>>>>> person in line, so the responses are best when archived :-)
>>>>>>>>
>>>>>>>> The deployment protocol bit is for wagon and defaults to scp (see
>>>>>>>> parent pom). If you want to use some other (for example, scpexe with
>>>>>>>> PuTTY), then it can be changed via an active profile in
>>>>>>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>>>>>>> probably don't need to do anything new for Commons.
>>>>>>>>
>>>>>>>>
>>>>>>>>> - Is it the case to migrate the group id to org.apache.commons?
>>>>>>>> <snap/>
>>>>>>>>
>>>>>>>> No, not for 2.1 (archives have this topic at length).
>>>>>>>>
>>>>>>>> -Rahul
>>>>>>>>
>>>>>>>>
>>>>>>>>> Many thanks in advance, namaste
>>>>>>>>> Simo
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>> http://www.99soft.org/
>>>>>>>>>
>>>>>>>>>
>>>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 10 September 2010 08:30, Simone Tripodi <si...@gmail.com> wrote:
> Hi Seb,
> thanks for your feedbacks. The problem I have is that even if I omit
> the password waiting for the prompt, once the builds arrives ad the
> gpg:sign execution, it is completely blocked :(
> I'm using gpg 1.4.9, shall I have to upgrade to 2?
Current is 1.4.10.
Gpg2 behaves very differently for passwords - it uses a background
process that caches the password for a while.
Unfortunately, gpg2 does not play well with secret keys on a USB
stick, see: http://jira.codehaus.org/browse/MGPG-30
For testing purposes, I created a dummy key and added both keyname and
password as a profile in my local settings file. It's then easy to use
the test-deploy profile to check that the correct items are created
and signed.
For example, I just tried:
mvn -Prc deploy -Ptest-deploy -PkeyTest
and it created and signed the Maven and non-Maven artifacts OK.
> Many thanks in advance, have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Thu, Sep 9, 2010 at 9:10 PM, sebb <se...@gmail.com> wrote:
>> On 9 September 2010 19:54, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi all guys,
>>> I'm trying to push an RC release, but the gpg plugin execution is
>>> blocked when signing arifacts :( Follow below my attempts:
>>>
>>> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=XXXX\
>>> -Dgpg.passphrase=XXXX
>>> mvn release:prepare -DdryRun=true -Dgpg.passphrase=XXXX (the keyname
>>> is defined as preferred in the gpg.conf)
>>> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
>>>
>>> Do you have any idea why? Many thanks in advance,
>>> Simo
>>
>> I use a profile in my settings.xml which defines the keyname, so I
>> don't have to remember the hex string.
>> One can also define gpg.homedir and gpg.executable (if required)
>>
>> The password you can omit - it should be prompted for, but how depends
>> on whether you are using gpg1 or gpg2.
>>
>> For testing gpg signing, you can use the new "test-deploy" profile.
>>
>> Don't you need to use mvn deploy ?
>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
>>> <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> don't worry I won't publish the site before the release; about the
>>>> Menu reorganization I like the b) too, it is much more coherent with
>>>> previous releases.
>>>> Thanks a lot, have a nice day,
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>> Hi all, Rahul,
>>>>>> what about the latest deployed website?
>>>>> <snip/>
>>>>>
>>>>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>>>>
>>>>>
>>>>>> Can I proceed modifying the
>>>>>> homepage in order to propose a release?
>>>>> <snap/>
>>>>>
>>>>> Sure, but please don't deploy it after those changes until the release
>>>>> is done. Before posting the vote, the site is previewed w/ the rc
>>>>> profile (-Prc) in the site-deploy command -- this will deploy the site
>>>>> to the pao/commons/builds area where the other artifacts for the vote
>>>>> will get posted as well.
>>>>>
>>>>> WRT the new additions to the LHS menu, currently we have (indentation
>>>>> implies nesting):
>>>>>
>>>>> Developers Guide (SVN latest)
>>>>> Core APIs
>>>>> Plugins
>>>>> Substitution
>>>>> XML Rules
>>>>> Annotations
>>>>> FAQ
>>>>>
>>>>> I see two options for the 2.1 release:
>>>>>
>>>>> (a) Use the above (but change SVN latest to 2.1)
>>>>>
>>>>> (b) Use the following:
>>>>>
>>>>> Release 2.1 (Current)
>>>>> Guide
>>>>> Core APIs
>>>>> Plugins
>>>>> Substitution
>>>>> XML Rules
>>>>> Annotations
>>>>> FAQ
>>>>> Javadoc
>>>>> Release Notes
>>>>>
>>>>> Release 2.0
>>>>> ... (current content for 2.0 menu)
>>>>>
>>>>>
>>>>> I think (b) will work better as it aligns with menu for previous
>>>>> releases -- note the FAQ indentation in (b) BTW as its different --
>>>>> WDYT?
>>>>>
>>>>> -Rahul
>>>>>
>>>>>
>>>>>> Thanks in advance, all the best,
>>>>>> Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>>>> Hi Rahul,
>>>>>>>> thanks a lot for your feedbacks, actions have been completed following
>>>>>>>> your suggestions.
>>>>>>>> my final 2 questions:
>>>>>>>> - I didn't find any reference on wiki about
>>>>>>>> ${commons.deployment.protocol}... can we have a private chat?
>>>>>>> <snip/>
>>>>>>>
>>>>>>> Sure, though it helps to have things in the list archives for the next
>>>>>>> person in line, so the responses are best when archived :-)
>>>>>>>
>>>>>>> The deployment protocol bit is for wagon and defaults to scp (see
>>>>>>> parent pom). If you want to use some other (for example, scpexe with
>>>>>>> PuTTY), then it can be changed via an active profile in
>>>>>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>>>>>> probably don't need to do anything new for Commons.
>>>>>>>
>>>>>>>
>>>>>>>> - Is it the case to migrate the group id to org.apache.commons?
>>>>>>> <snap/>
>>>>>>>
>>>>>>> No, not for 2.1 (archives have this topic at length).
>>>>>>>
>>>>>>> -Rahul
>>>>>>>
>>>>>>>
>>>>>>>> Many thanks in advance, namaste
>>>>>>>> Simo
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Seb,
thanks for your feedbacks. The problem I have is that even if I omit
the password waiting for the prompt, once the builds arrives ad the
gpg:sign execution, it is completely blocked :(
I'm using gpg 1.4.9, shall I have to upgrade to 2?
Many thanks in advance, have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Thu, Sep 9, 2010 at 9:10 PM, sebb <se...@gmail.com> wrote:
> On 9 September 2010 19:54, Simone Tripodi <si...@gmail.com> wrote:
>> Hi all guys,
>> I'm trying to push an RC release, but the gpg plugin execution is
>> blocked when signing arifacts :( Follow below my attempts:
>>
>> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=XXXX\
>> -Dgpg.passphrase=XXXX
>> mvn release:prepare -DdryRun=true -Dgpg.passphrase=XXXX (the keyname
>> is defined as preferred in the gpg.conf)
>> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
>>
>> Do you have any idea why? Many thanks in advance,
>> Simo
>
> I use a profile in my settings.xml which defines the keyname, so I
> don't have to remember the hex string.
> One can also define gpg.homedir and gpg.executable (if required)
>
> The password you can omit - it should be prompted for, but how depends
> on whether you are using gpg1 or gpg2.
>
> For testing gpg signing, you can use the new "test-deploy" profile.
>
> Don't you need to use mvn deploy ?
>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
>> <si...@gmail.com> wrote:
>>> Hi Rahul,
>>> don't worry I won't publish the site before the release; about the
>>> Menu reorganization I like the b) too, it is much more coherent with
>>> previous releases.
>>> Thanks a lot, have a nice day,
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Hi all, Rahul,
>>>>> what about the latest deployed website?
>>>> <snip/>
>>>>
>>>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>>>
>>>>
>>>>> Can I proceed modifying the
>>>>> homepage in order to propose a release?
>>>> <snap/>
>>>>
>>>> Sure, but please don't deploy it after those changes until the release
>>>> is done. Before posting the vote, the site is previewed w/ the rc
>>>> profile (-Prc) in the site-deploy command -- this will deploy the site
>>>> to the pao/commons/builds area where the other artifacts for the vote
>>>> will get posted as well.
>>>>
>>>> WRT the new additions to the LHS menu, currently we have (indentation
>>>> implies nesting):
>>>>
>>>> Developers Guide (SVN latest)
>>>> Core APIs
>>>> Plugins
>>>> Substitution
>>>> XML Rules
>>>> Annotations
>>>> FAQ
>>>>
>>>> I see two options for the 2.1 release:
>>>>
>>>> (a) Use the above (but change SVN latest to 2.1)
>>>>
>>>> (b) Use the following:
>>>>
>>>> Release 2.1 (Current)
>>>> Guide
>>>> Core APIs
>>>> Plugins
>>>> Substitution
>>>> XML Rules
>>>> Annotations
>>>> FAQ
>>>> Javadoc
>>>> Release Notes
>>>>
>>>> Release 2.0
>>>> ... (current content for 2.0 menu)
>>>>
>>>>
>>>> I think (b) will work better as it aligns with menu for previous
>>>> releases -- note the FAQ indentation in (b) BTW as its different --
>>>> WDYT?
>>>>
>>>> -Rahul
>>>>
>>>>
>>>>> Thanks in advance, all the best,
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>>> Hi Rahul,
>>>>>>> thanks a lot for your feedbacks, actions have been completed following
>>>>>>> your suggestions.
>>>>>>> my final 2 questions:
>>>>>>> - I didn't find any reference on wiki about
>>>>>>> ${commons.deployment.protocol}... can we have a private chat?
>>>>>> <snip/>
>>>>>>
>>>>>> Sure, though it helps to have things in the list archives for the next
>>>>>> person in line, so the responses are best when archived :-)
>>>>>>
>>>>>> The deployment protocol bit is for wagon and defaults to scp (see
>>>>>> parent pom). If you want to use some other (for example, scpexe with
>>>>>> PuTTY), then it can be changed via an active profile in
>>>>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>>>>> probably don't need to do anything new for Commons.
>>>>>>
>>>>>>
>>>>>>> - Is it the case to migrate the group id to org.apache.commons?
>>>>>> <snap/>
>>>>>>
>>>>>> No, not for 2.1 (archives have this topic at length).
>>>>>>
>>>>>> -Rahul
>>>>>>
>>>>>>
>>>>>>> Many thanks in advance, namaste
>>>>>>> Simo
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 9 September 2010 19:54, Simone Tripodi <si...@gmail.com> wrote:
> Hi all guys,
> I'm trying to push an RC release, but the gpg plugin execution is
> blocked when signing arifacts :( Follow below my attempts:
>
> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=XXXX\
> -Dgpg.passphrase=XXXX
> mvn release:prepare -DdryRun=true -Dgpg.passphrase=XXXX (the keyname
> is defined as preferred in the gpg.conf)
> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
>
> Do you have any idea why? Many thanks in advance,
> Simo
I use a profile in my settings.xml which defines the keyname, so I
don't have to remember the hex string.
One can also define gpg.homedir and gpg.executable (if required)
The password you can omit - it should be prompted for, but how depends
on whether you are using gpg1 or gpg2.
For testing gpg signing, you can use the new "test-deploy" profile.
Don't you need to use mvn deploy ?
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Hi Rahul,
>> don't worry I won't publish the site before the release; about the
>> Menu reorganization I like the b) too, it is much more coherent with
>> previous releases.
>> Thanks a lot, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi all, Rahul,
>>>> what about the latest deployed website?
>>> <snip/>
>>>
>>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>>
>>>
>>>> Can I proceed modifying the
>>>> homepage in order to propose a release?
>>> <snap/>
>>>
>>> Sure, but please don't deploy it after those changes until the release
>>> is done. Before posting the vote, the site is previewed w/ the rc
>>> profile (-Prc) in the site-deploy command -- this will deploy the site
>>> to the pao/commons/builds area where the other artifacts for the vote
>>> will get posted as well.
>>>
>>> WRT the new additions to the LHS menu, currently we have (indentation
>>> implies nesting):
>>>
>>> Developers Guide (SVN latest)
>>> Core APIs
>>> Plugins
>>> Substitution
>>> XML Rules
>>> Annotations
>>> FAQ
>>>
>>> I see two options for the 2.1 release:
>>>
>>> (a) Use the above (but change SVN latest to 2.1)
>>>
>>> (b) Use the following:
>>>
>>> Release 2.1 (Current)
>>> Guide
>>> Core APIs
>>> Plugins
>>> Substitution
>>> XML Rules
>>> Annotations
>>> FAQ
>>> Javadoc
>>> Release Notes
>>>
>>> Release 2.0
>>> ... (current content for 2.0 menu)
>>>
>>>
>>> I think (b) will work better as it aligns with menu for previous
>>> releases -- note the FAQ indentation in (b) BTW as its different --
>>> WDYT?
>>>
>>> -Rahul
>>>
>>>
>>>> Thanks in advance, all the best,
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>> Hi Rahul,
>>>>>> thanks a lot for your feedbacks, actions have been completed following
>>>>>> your suggestions.
>>>>>> my final 2 questions:
>>>>>> - I didn't find any reference on wiki about
>>>>>> ${commons.deployment.protocol}... can we have a private chat?
>>>>> <snip/>
>>>>>
>>>>> Sure, though it helps to have things in the list archives for the next
>>>>> person in line, so the responses are best when archived :-)
>>>>>
>>>>> The deployment protocol bit is for wagon and defaults to scp (see
>>>>> parent pom). If you want to use some other (for example, scpexe with
>>>>> PuTTY), then it can be changed via an active profile in
>>>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>>>> probably don't need to do anything new for Commons.
>>>>>
>>>>>
>>>>>> - Is it the case to migrate the group id to org.apache.commons?
>>>>> <snap/>
>>>>>
>>>>> No, not for 2.1 (archives have this topic at length).
>>>>>
>>>>> -Rahul
>>>>>
>>>>>
>>>>>> Many thanks in advance, namaste
>>>>>> Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi all guys,
I'm trying to push an RC release, but the gpg plugin execution is
blocked when signing arifacts :( Follow below my attempts:
mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=XXXX\
-Dgpg.passphrase=XXXX
mvn release:prepare -DdryRun=true -Dgpg.passphrase=XXXX (the keyname
is defined as preferred in the gpg.conf)
mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
Do you have any idea why? Many thanks in advance,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi Rahul,
> don't worry I won't publish the site before the release; about the
> Menu reorganization I like the b) too, it is much more coherent with
> previous releases.
> Thanks a lot, have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi all, Rahul,
>>> what about the latest deployed website?
>> <snip/>
>>
>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>
>>
>>> Can I proceed modifying the
>>> homepage in order to propose a release?
>> <snap/>
>>
>> Sure, but please don't deploy it after those changes until the release
>> is done. Before posting the vote, the site is previewed w/ the rc
>> profile (-Prc) in the site-deploy command -- this will deploy the site
>> to the pao/commons/builds area where the other artifacts for the vote
>> will get posted as well.
>>
>> WRT the new additions to the LHS menu, currently we have (indentation
>> implies nesting):
>>
>> Developers Guide (SVN latest)
>> Core APIs
>> Plugins
>> Substitution
>> XML Rules
>> Annotations
>> FAQ
>>
>> I see two options for the 2.1 release:
>>
>> (a) Use the above (but change SVN latest to 2.1)
>>
>> (b) Use the following:
>>
>> Release 2.1 (Current)
>> Guide
>> Core APIs
>> Plugins
>> Substitution
>> XML Rules
>> Annotations
>> FAQ
>> Javadoc
>> Release Notes
>>
>> Release 2.0
>> ... (current content for 2.0 menu)
>>
>>
>> I think (b) will work better as it aligns with menu for previous
>> releases -- note the FAQ indentation in (b) BTW as its different --
>> WDYT?
>>
>> -Rahul
>>
>>
>>> Thanks in advance, all the best,
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Hi Rahul,
>>>>> thanks a lot for your feedbacks, actions have been completed following
>>>>> your suggestions.
>>>>> my final 2 questions:
>>>>> - I didn't find any reference on wiki about
>>>>> ${commons.deployment.protocol}... can we have a private chat?
>>>> <snip/>
>>>>
>>>> Sure, though it helps to have things in the list archives for the next
>>>> person in line, so the responses are best when archived :-)
>>>>
>>>> The deployment protocol bit is for wagon and defaults to scp (see
>>>> parent pom). If you want to use some other (for example, scpexe with
>>>> PuTTY), then it can be changed via an active profile in
>>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>>> probably don't need to do anything new for Commons.
>>>>
>>>>
>>>>> - Is it the case to migrate the group id to org.apache.commons?
>>>> <snap/>
>>>>
>>>> No, not for 2.1 (archives have this topic at length).
>>>>
>>>> -Rahul
>>>>
>>>>
>>>>> Many thanks in advance, namaste
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul,
don't worry I won't publish the site before the release; about the
Menu reorganization I like the b) too, it is much more coherent with
previous releases.
Thanks a lot, have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
>> Hi all, Rahul,
>> what about the latest deployed website?
> <snip/>
>
> Looks good overall, though I haven't taken a fine-toothed comb to it.
>
>
>> Can I proceed modifying the
>> homepage in order to propose a release?
> <snap/>
>
> Sure, but please don't deploy it after those changes until the release
> is done. Before posting the vote, the site is previewed w/ the rc
> profile (-Prc) in the site-deploy command -- this will deploy the site
> to the pao/commons/builds area where the other artifacts for the vote
> will get posted as well.
>
> WRT the new additions to the LHS menu, currently we have (indentation
> implies nesting):
>
> Developers Guide (SVN latest)
> Core APIs
> Plugins
> Substitution
> XML Rules
> Annotations
> FAQ
>
> I see two options for the 2.1 release:
>
> (a) Use the above (but change SVN latest to 2.1)
>
> (b) Use the following:
>
> Release 2.1 (Current)
> Guide
> Core APIs
> Plugins
> Substitution
> XML Rules
> Annotations
> FAQ
> Javadoc
> Release Notes
>
> Release 2.0
> ... (current content for 2.0 menu)
>
>
> I think (b) will work better as it aligns with menu for previous
> releases -- note the FAQ indentation in (b) BTW as its different --
> WDYT?
>
> -Rahul
>
>
>> Thanks in advance, all the best,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> thanks a lot for your feedbacks, actions have been completed following
>>>> your suggestions.
>>>> my final 2 questions:
>>>> - I didn't find any reference on wiki about
>>>> ${commons.deployment.protocol}... can we have a private chat?
>>> <snip/>
>>>
>>> Sure, though it helps to have things in the list archives for the next
>>> person in line, so the responses are best when archived :-)
>>>
>>> The deployment protocol bit is for wagon and defaults to scp (see
>>> parent pom). If you want to use some other (for example, scpexe with
>>> PuTTY), then it can be changed via an active profile in
>>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>>> probably don't need to do anything new for Commons.
>>>
>>>
>>>> - Is it the case to migrate the group id to org.apache.commons?
>>> <snap/>
>>>
>>> No, not for 2.1 (archives have this topic at length).
>>>
>>> -Rahul
>>>
>>>
>>>> Many thanks in advance, namaste
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi <si...@gmail.com> wrote:
> Hi all, Rahul,
> what about the latest deployed website?
<snip/>
Looks good overall, though I haven't taken a fine-toothed comb to it.
> Can I proceed modifying the
> homepage in order to propose a release?
<snap/>
Sure, but please don't deploy it after those changes until the release
is done. Before posting the vote, the site is previewed w/ the rc
profile (-Prc) in the site-deploy command -- this will deploy the site
to the pao/commons/builds area where the other artifacts for the vote
will get posted as well.
WRT the new additions to the LHS menu, currently we have (indentation
implies nesting):
Developers Guide (SVN latest)
Core APIs
Plugins
Substitution
XML Rules
Annotations
FAQ
I see two options for the 2.1 release:
(a) Use the above (but change SVN latest to 2.1)
(b) Use the following:
Release 2.1 (Current)
Guide
Core APIs
Plugins
Substitution
XML Rules
Annotations
FAQ
Javadoc
Release Notes
Release 2.0
... (current content for 2.0 menu)
I think (b) will work better as it aligns with menu for previous
releases -- note the FAQ indentation in (b) BTW as its different --
WDYT?
-Rahul
> Thanks in advance, all the best,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi Rahul,
>>> thanks a lot for your feedbacks, actions have been completed following
>>> your suggestions.
>>> my final 2 questions:
>>> - I didn't find any reference on wiki about
>>> ${commons.deployment.protocol}... can we have a private chat?
>> <snip/>
>>
>> Sure, though it helps to have things in the list archives for the next
>> person in line, so the responses are best when archived :-)
>>
>> The deployment protocol bit is for wagon and defaults to scp (see
>> parent pom). If you want to use some other (for example, scpexe with
>> PuTTY), then it can be changed via an active profile in
>> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
>> probably don't need to do anything new for Commons.
>>
>>
>>> - Is it the case to migrate the group id to org.apache.commons?
>> <snap/>
>>
>> No, not for 2.1 (archives have this topic at length).
>>
>> -Rahul
>>
>>
>>> Many thanks in advance, namaste
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi all, Rahul,
what about the latest deployed website? Can I proceed modifying the
homepage in order to propose a release?
Thanks in advance, all the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Rahul,
>> thanks a lot for your feedbacks, actions have been completed following
>> your suggestions.
>> my final 2 questions:
>> - I didn't find any reference on wiki about
>> ${commons.deployment.protocol}... can we have a private chat?
> <snip/>
>
> Sure, though it helps to have things in the list archives for the next
> person in line, so the responses are best when archived :-)
>
> The deployment protocol bit is for wagon and defaults to scp (see
> parent pom). If you want to use some other (for example, scpexe with
> PuTTY), then it can be changed via an active profile in
> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
> probably don't need to do anything new for Commons.
>
>
>> - Is it the case to migrate the group id to org.apache.commons?
> <snap/>
>
> No, not for 2.1 (archives have this topic at length).
>
> -Rahul
>
>
>> Many thanks in advance, namaste
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi <si...@gmail.com> wrote:
> Hi Rahul,
> thanks a lot for your feedbacks, actions have been completed following
> your suggestions.
> my final 2 questions:
> - I didn't find any reference on wiki about
> ${commons.deployment.protocol}... can we have a private chat?
<snip/>
Sure, though it helps to have things in the list archives for the next
person in line, so the responses are best when archived :-)
The deployment protocol bit is for wagon and defaults to scp (see
parent pom). If you want to use some other (for example, scpexe with
PuTTY), then it can be changed via an active profile in
~/.m2/settings.xml. If you've used the m2 release plugin before, you
probably don't need to do anything new for Commons.
> - Is it the case to migrate the group id to org.apache.commons?
<snap/>
No, not for 2.1 (archives have this topic at length).
-Rahul
> Many thanks in advance, namaste
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul,
thanks a lot for your feedbacks, actions have been completed following
your suggestions.
my final 2 questions:
- I didn't find any reference on wiki about
${commons.deployment.protocol}... can we have a private chat?
- Is it the case to migrate the group id to org.apache.commons?
Many thanks in advance, namaste
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 3, 2010 at 10:16 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Fri, Sep 3, 2010 at 3:34 PM, Simone Tripodi <si...@gmail.com> wrote:
>> Sorry,
>> forgot to ask your opinion on dropping the STATUS.html[1] file that
>> seems has not been updated anymore since 1.7 release... WDYT?
> <snip/>
>
> Yup, lets scrap that.
>
> -Rahul
>
> ---------------------------------------------------------------------
> 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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Sep 3, 2010 at 3:34 PM, Simone Tripodi <si...@gmail.com> wrote:
> Sorry,
> forgot to ask your opinion on dropping the STATUS.html[1] file that
> seems has not been updated anymore since 1.7 release... WDYT?
<snip/>
Yup, lets scrap that.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Sorry,
forgot to ask your opinion on dropping the STATUS.html[1] file that
seems has not been updated anymore since 1.7 release... WDYT?
Thanks in advance,
Simo
[1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/STATUS.html
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 3, 2010 at 9:32 PM, Simone Tripodi <si...@gmail.com> wrote:
> Hi again Rahul, all,
> just to ask opinions about other details: I'd move the checkstyle
> stuff (checkstyle.xml and file-header.txt), on the project root, to a
> proper src/test/checkstyle dir to keep the root dir as much clean as
> possible, removing verification tools configuration and keep metadata
> build only. WDYT?
> Namaste,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Fri, Sep 3, 2010 at 5:46 PM, Simone Tripodi <si...@gmail.com> wrote:
>> Thanks for the suggestions, I'll follow the path you showed me!
>> thanks a lot,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Sep 3, 2010 at 5:28 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>> On Fri, Sep 3, 2010 at 10:54 AM, Simone Tripodi
>>> <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> thanks a lot!!! I just need to fix the svn cp we discussed in the
>>>> other thread, write the release notes and I'll be ready to calla a
>>>> vote.
>>> <snip/>
>>>
>>> Two suggestions:
>>> * Digester release notes have been written by hand (rather than
>>> generating them as mentioned on the wiki) -- look to prior releases
>>> for examples.
>>> * I'd deploy the latest site here [1] (mvn site-deploy) first and
>>> wait for feedback given there have been a number of site changes. That
>>> way you won't have to spin another RC to fix any site tweaks.
>>>
>>> -Rahul
>>>
>>> [1] http://commons.apache.org/digester/
>>>
>>>
>>>> I'll use the m2 rc profile, I'm already used to do it with the release
>>>> plugin and found it comfortable.
>>>> Have a nice day,m
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Fri, Sep 3, 2010 at 3:14 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>> On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>> Hi Rahul,
>>>>>> thanks for your feedbacks!!! :)
>>>>>> At that point I'd try to call a vote for a new release, WDYT? Can you
>>>>>> point me please at some wiki page where described the release
>>>>>> procedure?
>>>>> <snip/>
>>>>>
>>>>> Depends who is cutting the release. We have atleast three flavors:
>>>>>
>>>>> * Use Nexus [1]
>>>>> * Use the m2 rc profile [2]
>>>>> * A manual scp of artifacts to people
>>>>>
>>>>> I use the rc profile which effectively amounts to doing this once the
>>>>> prep is done, to post the RC:
>>>>>
>>>>> mvn -Prc release:prepare
>>>>> mvn -Prc release:perform
>>>>> mvn -Prc site-deploy
>>>>>
>>>>> You can read [2] for all the details.
>>>>>
>>>>> -Rahul
>>>>>
>>>>> [1] http://wiki.apache.org/commons/UsingNexus
>>>>> [2] http://wiki.apache.org/commons/CreatingReleases
>>>>>
>>>>>
>>>>>
>>>>>> Many thanks in advance, have a nice day!
>>>>>> Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Sep 3, 2010 at 3:32 PM, Simone Tripodi <si...@gmail.com> wrote:
> Hi again Rahul, all,
> just to ask opinions about other details: I'd move the checkstyle
> stuff (checkstyle.xml and file-header.txt), on the project root, to a
> proper src/test/checkstyle dir to keep the root dir as much clean as
> possible, removing verification tools configuration and keep metadata
> build only. WDYT?
<snip/>
If we are going to move those, perhaps src/main/config is a better
location (and thats what some other Commons components that don't have
those files at project root use).
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi again Rahul, all,
just to ask opinions about other details: I'd move the checkstyle
stuff (checkstyle.xml and file-header.txt), on the project root, to a
proper src/test/checkstyle dir to keep the root dir as much clean as
possible, removing verification tools configuration and keep metadata
build only. WDYT?
Namaste,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 3, 2010 at 5:46 PM, Simone Tripodi <si...@gmail.com> wrote:
> Thanks for the suggestions, I'll follow the path you showed me!
> thanks a lot,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Fri, Sep 3, 2010 at 5:28 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Fri, Sep 3, 2010 at 10:54 AM, Simone Tripodi
>> <si...@gmail.com> wrote:
>>> Hi Rahul,
>>> thanks a lot!!! I just need to fix the svn cp we discussed in the
>>> other thread, write the release notes and I'll be ready to calla a
>>> vote.
>> <snip/>
>>
>> Two suggestions:
>> * Digester release notes have been written by hand (rather than
>> generating them as mentioned on the wiki) -- look to prior releases
>> for examples.
>> * I'd deploy the latest site here [1] (mvn site-deploy) first and
>> wait for feedback given there have been a number of site changes. That
>> way you won't have to spin another RC to fix any site tweaks.
>>
>> -Rahul
>>
>> [1] http://commons.apache.org/digester/
>>
>>
>>> I'll use the m2 rc profile, I'm already used to do it with the release
>>> plugin and found it comfortable.
>>> Have a nice day,m
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Fri, Sep 3, 2010 at 3:14 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>>> On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Hi Rahul,
>>>>> thanks for your feedbacks!!! :)
>>>>> At that point I'd try to call a vote for a new release, WDYT? Can you
>>>>> point me please at some wiki page where described the release
>>>>> procedure?
>>>> <snip/>
>>>>
>>>> Depends who is cutting the release. We have atleast three flavors:
>>>>
>>>> * Use Nexus [1]
>>>> * Use the m2 rc profile [2]
>>>> * A manual scp of artifacts to people
>>>>
>>>> I use the rc profile which effectively amounts to doing this once the
>>>> prep is done, to post the RC:
>>>>
>>>> mvn -Prc release:prepare
>>>> mvn -Prc release:perform
>>>> mvn -Prc site-deploy
>>>>
>>>> You can read [2] for all the details.
>>>>
>>>> -Rahul
>>>>
>>>> [1] http://wiki.apache.org/commons/UsingNexus
>>>> [2] http://wiki.apache.org/commons/CreatingReleases
>>>>
>>>>
>>>>
>>>>> Many thanks in advance, have a nice day!
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Thanks for the suggestions, I'll follow the path you showed me!
thanks a lot,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 3, 2010 at 5:28 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Fri, Sep 3, 2010 at 10:54 AM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Hi Rahul,
>> thanks a lot!!! I just need to fix the svn cp we discussed in the
>> other thread, write the release notes and I'll be ready to calla a
>> vote.
> <snip/>
>
> Two suggestions:
> * Digester release notes have been written by hand (rather than
> generating them as mentioned on the wiki) -- look to prior releases
> for examples.
> * I'd deploy the latest site here [1] (mvn site-deploy) first and
> wait for feedback given there have been a number of site changes. That
> way you won't have to spin another RC to fix any site tweaks.
>
> -Rahul
>
> [1] http://commons.apache.org/digester/
>
>
>> I'll use the m2 rc profile, I'm already used to do it with the release
>> plugin and found it comfortable.
>> Have a nice day,m
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Sep 3, 2010 at 3:14 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>>> On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> thanks for your feedbacks!!! :)
>>>> At that point I'd try to call a vote for a new release, WDYT? Can you
>>>> point me please at some wiki page where described the release
>>>> procedure?
>>> <snip/>
>>>
>>> Depends who is cutting the release. We have atleast three flavors:
>>>
>>> * Use Nexus [1]
>>> * Use the m2 rc profile [2]
>>> * A manual scp of artifacts to people
>>>
>>> I use the rc profile which effectively amounts to doing this once the
>>> prep is done, to post the RC:
>>>
>>> mvn -Prc release:prepare
>>> mvn -Prc release:perform
>>> mvn -Prc site-deploy
>>>
>>> You can read [2] for all the details.
>>>
>>> -Rahul
>>>
>>> [1] http://wiki.apache.org/commons/UsingNexus
>>> [2] http://wiki.apache.org/commons/CreatingReleases
>>>
>>>
>>>
>>>> Many thanks in advance, have a nice day!
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Sep 3, 2010 at 10:54 AM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi Rahul,
> thanks a lot!!! I just need to fix the svn cp we discussed in the
> other thread, write the release notes and I'll be ready to calla a
> vote.
<snip/>
Two suggestions:
* Digester release notes have been written by hand (rather than
generating them as mentioned on the wiki) -- look to prior releases
for examples.
* I'd deploy the latest site here [1] (mvn site-deploy) first and
wait for feedback given there have been a number of site changes. That
way you won't have to spin another RC to fix any site tweaks.
-Rahul
[1] http://commons.apache.org/digester/
> I'll use the m2 rc profile, I'm already used to do it with the release
> plugin and found it comfortable.
> Have a nice day,m
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Fri, Sep 3, 2010 at 3:14 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi Rahul,
>>> thanks for your feedbacks!!! :)
>>> At that point I'd try to call a vote for a new release, WDYT? Can you
>>> point me please at some wiki page where described the release
>>> procedure?
>> <snip/>
>>
>> Depends who is cutting the release. We have atleast three flavors:
>>
>> * Use Nexus [1]
>> * Use the m2 rc profile [2]
>> * A manual scp of artifacts to people
>>
>> I use the rc profile which effectively amounts to doing this once the
>> prep is done, to post the RC:
>>
>> mvn -Prc release:prepare
>> mvn -Prc release:perform
>> mvn -Prc site-deploy
>>
>> You can read [2] for all the details.
>>
>> -Rahul
>>
>> [1] http://wiki.apache.org/commons/UsingNexus
>> [2] http://wiki.apache.org/commons/CreatingReleases
>>
>>
>>
>>> Many thanks in advance, have a nice day!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul,
thanks a lot!!! I just need to fix the svn cp we discussed in the
other thread, write the release notes and I'll be ready to calla a
vote.
I'll use the m2 rc profile, I'm already used to do it with the release
plugin and found it comfortable.
Have a nice day,m
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Sep 3, 2010 at 3:14 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Rahul,
>> thanks for your feedbacks!!! :)
>> At that point I'd try to call a vote for a new release, WDYT? Can you
>> point me please at some wiki page where described the release
>> procedure?
> <snip/>
>
> Depends who is cutting the release. We have atleast three flavors:
>
> * Use Nexus [1]
> * Use the m2 rc profile [2]
> * A manual scp of artifacts to people
>
> I use the rc profile which effectively amounts to doing this once the
> prep is done, to post the RC:
>
> mvn -Prc release:prepare
> mvn -Prc release:perform
> mvn -Prc site-deploy
>
> You can read [2] for all the details.
>
> -Rahul
>
> [1] http://wiki.apache.org/commons/UsingNexus
> [2] http://wiki.apache.org/commons/CreatingReleases
>
>
>
>> Many thanks in advance, have a nice day!
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Sep 3, 2010 at 1:40 AM, Simone Tripodi <si...@gmail.com> wrote:
> Hi Rahul,
> thanks for your feedbacks!!! :)
> At that point I'd try to call a vote for a new release, WDYT? Can you
> point me please at some wiki page where described the release
> procedure?
<snip/>
Depends who is cutting the release. We have atleast three flavors:
* Use Nexus [1]
* Use the m2 rc profile [2]
* A manual scp of artifacts to people
I use the rc profile which effectively amounts to doing this once the
prep is done, to post the RC:
mvn -Prc release:prepare
mvn -Prc release:perform
mvn -Prc site-deploy
You can read [2] for all the details.
-Rahul
[1] http://wiki.apache.org/commons/UsingNexus
[2] http://wiki.apache.org/commons/CreatingReleases
> Many thanks in advance, have a nice day!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul,
thanks for your feedbacks!!! :)
At that point I'd try to call a vote for a new release, WDYT? Can you
point me please at some wiki page where described the release
procedure?
Many thanks in advance, have a nice day!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Thu, Sep 2, 2010 at 11:21 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Thu, Sep 2, 2010 at 4:54 PM, Simone Tripodi <si...@gmail.com> wrote:
>> Hi again,
>> I've been fixing PMD-CPD-Checkstyle errors, by now PMD warnings could
>> be considered trivial since they're detected on Deprecated
>> methods/constructor, there is a CPD warning I'd like to fix:
>>
>> File Line
>> org/apache/commons/digester/SetNextRule.java 198
>> org/apache/commons/digester/SetRootRule.java 191
>>
>> SetNextRule[1] class looks like to SetRootRule[2], what do you think
>> about adding an abstract class that generalizes the behavior of both
>> classes?
> <snip/>
>
> We can leave those as-is, thats not a newly flagged CPD output.
>
> In theory, an abstract class where the method may be called on the
> root, (top -1) or any stack index in between seems the generic base
> class functionality. However, in practice, root and (top - 1) are most
> common and the duplication we see isn't too bad or new either.
>
> -Rahul
>
>
>> Thanks in advance, have a nice day!!!
>> Simo
>>
>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetNextRule.java
>> [2] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetRootRule.java
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Thu, Sep 2, 2010 at 4:54 PM, Simone Tripodi <si...@gmail.com> wrote:
> Hi again,
> I've been fixing PMD-CPD-Checkstyle errors, by now PMD warnings could
> be considered trivial since they're detected on Deprecated
> methods/constructor, there is a CPD warning I'd like to fix:
>
> File Line
> org/apache/commons/digester/SetNextRule.java 198
> org/apache/commons/digester/SetRootRule.java 191
>
> SetNextRule[1] class looks like to SetRootRule[2], what do you think
> about adding an abstract class that generalizes the behavior of both
> classes?
<snip/>
We can leave those as-is, thats not a newly flagged CPD output.
In theory, an abstract class where the method may be called on the
root, (top -1) or any stack index in between seems the generic base
class functionality. However, in practice, root and (top - 1) are most
common and the duplication we see isn't too bad or new either.
-Rahul
> Thanks in advance, have a nice day!!!
> Simo
>
> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetNextRule.java
> [2] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetRootRule.java
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi again,
I've been fixing PMD-CPD-Checkstyle errors, by now PMD warnings could
be considered trivial since they're detected on Deprecated
methods/constructor, there is a CPD warning I'd like to fix:
File Line
org/apache/commons/digester/SetNextRule.java 198
org/apache/commons/digester/SetRootRule.java 191
SetNextRule[1] class looks like to SetRootRule[2], what do you think
about adding an abstract class that generalizes the behavior of both
classes?
Thanks in advance, have a nice day!!!
Simo
[1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetNextRule.java
[2] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/main/java/org/apache/commons/digester/SetRootRule.java
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Thu, Sep 2, 2010 at 6:37 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Thu, Sep 2, 2010 at 1:54 AM, Simone Tripodi <si...@gmail.com> wrote:
>> Hi all,
>> just to give you a brief recap of the completed actions:
>> - tests have been migrated to JUnit 4;
>> - project structure has been moved to default Maven archetype structure;
>> - ant build & config have been removed;
>> - whole documentation has been moved to site, in the xdoc format.
>>
> <snip/>
>
> Great :-)
>
>
>> There still is the 'examples' dir that's using ant to build the small
>> subprojects, what do you think on moving them too to a maven build?
> <snap/>
>
> I don't think thats a requirement for the next release. I also don't
> think we want to introduce a multi-module m2 build for digester, so
> best to keep that build on its own (even if moved to m2) as it is now.
>
> In effect -- if someone wants to do it, sure.
>
> -Rahul
>
>
>> Thanks in advance, have a nice day :)
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Wed, Sep 1, 2010 at 2:27 PM, Simone Tripodi <si...@gmail.com> wrote:
>>> Unfortunately they are just components mocks used in proper unit
>>> tests, they don't contain test methods, so 1) should be the better
>>> solution.
>>> Thanks Seb!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Wed, Sep 1, 2010 at 12:50 PM, sebb <se...@gmail.com> wrote:
>>>> On 1 September 2010 09:24, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Hi guys,
>>>>> migrating to Junit4 I met a small issue that can be easily resolved in
>>>>> more that 1 way, I'd like to discuss with you how we want doing it:
>>>>>
>>>>> Tests in error:
>>>>> initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
>>>>> initializationError(org.apache.commons.digester.plugins.TestObject)
>>>>> initializationError(org.apache.commons.digester.TestObjectCreationFactory)
>>>>> initializationError(org.apache.commons.digester.xmlrules.TestObject)
>>>>>
>>>>> These classes are not unit test at all but rather classes to support
>>>>> tests, but because of the name pattern, surefire tries to execute them
>>>>> as unit test, but Junit4 fails because no test methods are present in
>>>>> these classes.
>>>>>
>>>>> AFAIK we can fix it in 2 ways:
>>>>>
>>>>> 1) renaming all the class name;
>>>>> 2) adding fake test methods
>>>>>
>>>>> I'm for 1, what do you suggest to proceed?
>>>>
>>>> Or one can:
>>>>
>>>> 3) Add exclusions to the POM.
>>>> - just added for completeness, as I prefer 1)
>>>>
>>>> However, if there is a useful test that can be added to a support
>>>> class, then 2) is the way to go.
>>>>
>>>>> Thanks in advance, best regards!
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>>> Thanks a lot guys,
>>>>>> now the scope is much more clear to me. I'll proceed according to what
>>>>>> we agreed.
>>>>>> Have a nice day!!!
>>>>>> Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>>>>>>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>>>>>>> <si...@gmail.com> wrote:
>>>>>>>>> Hi guys,
>>>>>>>>> one more question: what about keeping or removing the Test
>>>>>>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>>>>>>> needed...
>>>>>>>> <snip/>
>>>>>>>>
>>>>>>>> Don't have a strong opinion -- if someone wants to do it.
>>>>>>>
>>>>>>> Forgot to say I'm +1 on removing these.
>>>>>>>
>>>>>>> Just need to be careful in case there is a suite which is used to
>>>>>>> ensure that certain tests are run in a particular order.
>>>>>>>
>>>>>>> Otherwise, the main() and suite() methods are unnecessary, and it's
>>>>>>> too easy to add a test class and forget to add the class to the suite.
>>>>>>>
>
> ---------------------------------------------------------------------
> 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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Thu, Sep 2, 2010 at 1:54 AM, Simone Tripodi <si...@gmail.com> wrote:
> Hi all,
> just to give you a brief recap of the completed actions:
> - tests have been migrated to JUnit 4;
> - project structure has been moved to default Maven archetype structure;
> - ant build & config have been removed;
> - whole documentation has been moved to site, in the xdoc format.
>
<snip/>
Great :-)
> There still is the 'examples' dir that's using ant to build the small
> subprojects, what do you think on moving them too to a maven build?
<snap/>
I don't think thats a requirement for the next release. I also don't
think we want to introduce a multi-module m2 build for digester, so
best to keep that build on its own (even if moved to m2) as it is now.
In effect -- if someone wants to do it, sure.
-Rahul
> Thanks in advance, have a nice day :)
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Wed, Sep 1, 2010 at 2:27 PM, Simone Tripodi <si...@gmail.com> wrote:
>> Unfortunately they are just components mocks used in proper unit
>> tests, they don't contain test methods, so 1) should be the better
>> solution.
>> Thanks Seb!
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Wed, Sep 1, 2010 at 12:50 PM, sebb <se...@gmail.com> wrote:
>>> On 1 September 2010 09:24, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi guys,
>>>> migrating to Junit4 I met a small issue that can be easily resolved in
>>>> more that 1 way, I'd like to discuss with you how we want doing it:
>>>>
>>>> Tests in error:
>>>> initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
>>>> initializationError(org.apache.commons.digester.plugins.TestObject)
>>>> initializationError(org.apache.commons.digester.TestObjectCreationFactory)
>>>> initializationError(org.apache.commons.digester.xmlrules.TestObject)
>>>>
>>>> These classes are not unit test at all but rather classes to support
>>>> tests, but because of the name pattern, surefire tries to execute them
>>>> as unit test, but Junit4 fails because no test methods are present in
>>>> these classes.
>>>>
>>>> AFAIK we can fix it in 2 ways:
>>>>
>>>> 1) renaming all the class name;
>>>> 2) adding fake test methods
>>>>
>>>> I'm for 1, what do you suggest to proceed?
>>>
>>> Or one can:
>>>
>>> 3) Add exclusions to the POM.
>>> - just added for completeness, as I prefer 1)
>>>
>>> However, if there is a useful test that can be added to a support
>>> class, then 2) is the way to go.
>>>
>>>> Thanks in advance, best regards!
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Thanks a lot guys,
>>>>> now the scope is much more clear to me. I'll proceed according to what
>>>>> we agreed.
>>>>> Have a nice day!!!
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>>>>>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>>>>>> <si...@gmail.com> wrote:
>>>>>>>> Hi guys,
>>>>>>>> one more question: what about keeping or removing the Test
>>>>>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>>>>>> needed...
>>>>>>> <snip/>
>>>>>>>
>>>>>>> Don't have a strong opinion -- if someone wants to do it.
>>>>>>
>>>>>> Forgot to say I'm +1 on removing these.
>>>>>>
>>>>>> Just need to be careful in case there is a suite which is used to
>>>>>> ensure that certain tests are run in a particular order.
>>>>>>
>>>>>> Otherwise, the main() and suite() methods are unnecessary, and it's
>>>>>> too easy to add a test class and forget to add the class to the suite.
>>>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi all,
just to give you a brief recap of the completed actions:
- tests have been migrated to JUnit 4;
- project structure has been moved to default Maven archetype structure;
- ant build & config have been removed;
- whole documentation has been moved to site, in the xdoc format.
There still is the 'examples' dir that's using ant to build the small
subprojects, what do you think on moving them too to a maven build?
Thanks in advance, have a nice day :)
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 1, 2010 at 2:27 PM, Simone Tripodi <si...@gmail.com> wrote:
> Unfortunately they are just components mocks used in proper unit
> tests, they don't contain test methods, so 1) should be the better
> solution.
> Thanks Seb!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Wed, Sep 1, 2010 at 12:50 PM, sebb <se...@gmail.com> wrote:
>> On 1 September 2010 09:24, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi guys,
>>> migrating to Junit4 I met a small issue that can be easily resolved in
>>> more that 1 way, I'd like to discuss with you how we want doing it:
>>>
>>> Tests in error:
>>> initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
>>> initializationError(org.apache.commons.digester.plugins.TestObject)
>>> initializationError(org.apache.commons.digester.TestObjectCreationFactory)
>>> initializationError(org.apache.commons.digester.xmlrules.TestObject)
>>>
>>> These classes are not unit test at all but rather classes to support
>>> tests, but because of the name pattern, surefire tries to execute them
>>> as unit test, but Junit4 fails because no test methods are present in
>>> these classes.
>>>
>>> AFAIK we can fix it in 2 ways:
>>>
>>> 1) renaming all the class name;
>>> 2) adding fake test methods
>>>
>>> I'm for 1, what do you suggest to proceed?
>>
>> Or one can:
>>
>> 3) Add exclusions to the POM.
>> - just added for completeness, as I prefer 1)
>>
>> However, if there is a useful test that can be added to a support
>> class, then 2) is the way to go.
>>
>>> Thanks in advance, best regards!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
>>>> Thanks a lot guys,
>>>> now the scope is much more clear to me. I'll proceed according to what
>>>> we agreed.
>>>> Have a nice day!!!
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>>>>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>>>>> <si...@gmail.com> wrote:
>>>>>>> Hi guys,
>>>>>>> one more question: what about keeping or removing the Test
>>>>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>>>>> needed...
>>>>>> <snip/>
>>>>>>
>>>>>> Don't have a strong opinion -- if someone wants to do it.
>>>>>
>>>>> Forgot to say I'm +1 on removing these.
>>>>>
>>>>> Just need to be careful in case there is a suite which is used to
>>>>> ensure that certain tests are run in a particular order.
>>>>>
>>>>> Otherwise, the main() and suite() methods are unnecessary, and it's
>>>>> too easy to add a test class and forget to add the class to the suite.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Unfortunately they are just components mocks used in proper unit
tests, they don't contain test methods, so 1) should be the better
solution.
Thanks Seb!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 1, 2010 at 12:50 PM, sebb <se...@gmail.com> wrote:
> On 1 September 2010 09:24, Simone Tripodi <si...@gmail.com> wrote:
>> Hi guys,
>> migrating to Junit4 I met a small issue that can be easily resolved in
>> more that 1 way, I'd like to discuss with you how we want doing it:
>>
>> Tests in error:
>> initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
>> initializationError(org.apache.commons.digester.plugins.TestObject)
>> initializationError(org.apache.commons.digester.TestObjectCreationFactory)
>> initializationError(org.apache.commons.digester.xmlrules.TestObject)
>>
>> These classes are not unit test at all but rather classes to support
>> tests, but because of the name pattern, surefire tries to execute them
>> as unit test, but Junit4 fails because no test methods are present in
>> these classes.
>>
>> AFAIK we can fix it in 2 ways:
>>
>> 1) renaming all the class name;
>> 2) adding fake test methods
>>
>> I'm for 1, what do you suggest to proceed?
>
> Or one can:
>
> 3) Add exclusions to the POM.
> - just added for completeness, as I prefer 1)
>
> However, if there is a useful test that can be added to a support
> class, then 2) is the way to go.
>
>> Thanks in advance, best regards!
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
>>> Thanks a lot guys,
>>> now the scope is much more clear to me. I'll proceed according to what
>>> we agreed.
>>> Have a nice day!!!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>>>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>>>> <si...@gmail.com> wrote:
>>>>>> Hi guys,
>>>>>> one more question: what about keeping or removing the Test
>>>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>>>> needed...
>>>>> <snip/>
>>>>>
>>>>> Don't have a strong opinion -- if someone wants to do it.
>>>>
>>>> Forgot to say I'm +1 on removing these.
>>>>
>>>> Just need to be careful in case there is a suite which is used to
>>>> ensure that certain tests are run in a particular order.
>>>>
>>>> Otherwise, the main() and suite() methods are unnecessary, and it's
>>>> too easy to add a test class and forget to add the class to the suite.
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 1 September 2010 09:24, Simone Tripodi <si...@gmail.com> wrote:
> Hi guys,
> migrating to Junit4 I met a small issue that can be easily resolved in
> more that 1 way, I'd like to discuss with you how we want doing it:
>
> Tests in error:
> initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
> initializationError(org.apache.commons.digester.plugins.TestObject)
> initializationError(org.apache.commons.digester.TestObjectCreationFactory)
> initializationError(org.apache.commons.digester.xmlrules.TestObject)
>
> These classes are not unit test at all but rather classes to support
> tests, but because of the name pattern, surefire tries to execute them
> as unit test, but Junit4 fails because no test methods are present in
> these classes.
>
> AFAIK we can fix it in 2 ways:
>
> 1) renaming all the class name;
> 2) adding fake test methods
>
> I'm for 1, what do you suggest to proceed?
Or one can:
3) Add exclusions to the POM.
- just added for completeness, as I prefer 1)
However, if there is a useful test that can be added to a support
class, then 2) is the way to go.
> Thanks in advance, best regards!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
>> Thanks a lot guys,
>> now the scope is much more clear to me. I'll proceed according to what
>> we agreed.
>> Have a nice day!!!
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>>> <si...@gmail.com> wrote:
>>>>> Hi guys,
>>>>> one more question: what about keeping or removing the Test
>>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>>> needed...
>>>> <snip/>
>>>>
>>>> Don't have a strong opinion -- if someone wants to do it.
>>>
>>> Forgot to say I'm +1 on removing these.
>>>
>>> Just need to be careful in case there is a suite which is used to
>>> ensure that certain tests are run in a particular order.
>>>
>>> Otherwise, the main() and suite() methods are unnecessary, and it's
>>> too easy to add a test class and forget to add the class to the suite.
>>>
>>> ---------------------------------------------------------------------
>>> 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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi guys,
migrating to Junit4 I met a small issue that can be easily resolved in
more that 1 way, I'd like to discuss with you how we want doing it:
Tests in error:
initializationError(org.apache.commons.digester.xmlrules.TestDigesterRulesSource)
initializationError(org.apache.commons.digester.plugins.TestObject)
initializationError(org.apache.commons.digester.TestObjectCreationFactory)
initializationError(org.apache.commons.digester.xmlrules.TestObject)
These classes are not unit test at all but rather classes to support
tests, but because of the name pattern, surefire tries to execute them
as unit test, but Junit4 fails because no test methods are present in
these classes.
AFAIK we can fix it in 2 ways:
1) renaming all the class name;
2) adding fake test methods
I'm for 1, what do you suggest to proceed?
Thanks in advance, best regards!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 1, 2010 at 7:38 AM, Simone Tripodi <si...@gmail.com> wrote:
> Thanks a lot guys,
> now the scope is much more clear to me. I'll proceed according to what
> we agreed.
> Have a nice day!!!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
>> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>>> <si...@gmail.com> wrote:
>>>> Hi guys,
>>>> one more question: what about keeping or removing the Test
>>>> classes/methods that just declare the Suite? AFAIK are not more
>>>> needed...
>>> <snip/>
>>>
>>> Don't have a strong opinion -- if someone wants to do it.
>>
>> Forgot to say I'm +1 on removing these.
>>
>> Just need to be careful in case there is a suite which is used to
>> ensure that certain tests are run in a particular order.
>>
>> Otherwise, the main() and suite() methods are unnecessary, and it's
>> too easy to add a test class and forget to add the class to the suite.
>>
>> ---------------------------------------------------------------------
>> 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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Thanks a lot guys,
now the scope is much more clear to me. I'll proceed according to what
we agreed.
Have a nice day!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 1, 2010 at 12:22 AM, sebb <se...@gmail.com> wrote:
> On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
>> <si...@gmail.com> wrote:
>>> Hi guys,
>>> one more question: what about keeping or removing the Test
>>> classes/methods that just declare the Suite? AFAIK are not more
>>> needed...
>> <snip/>
>>
>> Don't have a strong opinion -- if someone wants to do it.
>
> Forgot to say I'm +1 on removing these.
>
> Just need to be careful in case there is a suite which is used to
> ensure that certain tests are run in a particular order.
>
> Otherwise, the main() and suite() methods are unnecessary, and it's
> too easy to add a test class and forget to add the class to the suite.
>
> ---------------------------------------------------------------------
> 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
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 31 August 2010 22:54, Rahul Akolkar <ra...@gmail.com> wrote:
> On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Hi guys,
>> one more question: what about keeping or removing the Test
>> classes/methods that just declare the Suite? AFAIK are not more
>> needed...
> <snip/>
>
> Don't have a strong opinion -- if someone wants to do it.
Forgot to say I'm +1 on removing these.
Just need to be careful in case there is a suite which is used to
ensure that certain tests are run in a particular order.
Otherwise, the main() and suite() methods are unnecessary, and it's
too easy to add a test class and forget to add the class to the suite.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Aug 31, 2010 at 2:45 PM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi guys,
> one more question: what about keeping or removing the Test
> classes/methods that just declare the Suite? AFAIK are not more
> needed...
<snip/>
Don't have a strong opinion -- if someone wants to do it.
-Rahul
> Thanks in advance,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, Aug 31, 2010 at 8:29 PM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Hi Seb,
>> thanks for your feedbacks, always appreciated! I know and understand
>> the need of having the package.html files, but what do you think about
>> replacing them with the package-info.java files? It should be the
>> same, or not? I've been working with them and found it very
>> comfortables.
>> I'll start staking care of migrating the JUnit dependency, is it fine
>> for you just adding the @Test annotation on existing methods, without
>> renaming them? The number of tests is quite large... :P
>> Thanks in advance, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Tue, Aug 31, 2010 at 6:09 PM, sebb <se...@gmail.com> wrote:
>>> On 31 August 2010 17:02, sebb <se...@gmail.com> wrote:
>>>> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>>>>> Hi Rahul,
>>>>> I just added the xdoc version of the documentation present in the
>>>>> package.html files.
>>>>
>>>> The package.html files are normally used to annotate the Javadoc output.
>>>>
>>>> However in this case these files have got a lot more content than is
>>>> normally present in the Javadoc.
>>>>
>>>>> Do you think these last can be removed, since
>>>>> would be redundant with the new developers guide?
>>>>
>>>> There should at least be minimal package.html files for Javadoc usage,
>>>> so I don't think the files should be removed entirely, but they could
>>>> be replaced with much simpler versions.
>>>>
>>>>> At this stage, we
>>>>> should maintain two different data sources with same information, I'd
>>>>> propose to drop the existing one, but let choose together.
>>>>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>>>>> that contains informations that maven can generate automatically, do
>>>>> you think we can drop it, when dropping the ant build?
>>>>
>>>> +1 to dropping MANIFEST.MF.
>>>>
>>>>> Thanks in advance, have a nice day!
>>>>> Simo
>>>>>
>>>>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>>>>
>>>
>>> Forgot to add - could update JUnit to the latest 4.x release, i.e. 4.8.1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi guys,
one more question: what about keeping or removing the Test
classes/methods that just declare the Suite? AFAIK are not more
needed...
Thanks in advance,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Aug 31, 2010 at 8:29 PM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi Seb,
> thanks for your feedbacks, always appreciated! I know and understand
> the need of having the package.html files, but what do you think about
> replacing them with the package-info.java files? It should be the
> same, or not? I've been working with them and found it very
> comfortables.
> I'll start staking care of migrating the JUnit dependency, is it fine
> for you just adding the @Test annotation on existing methods, without
> renaming them? The number of tests is quite large... :P
> Thanks in advance, have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, Aug 31, 2010 at 6:09 PM, sebb <se...@gmail.com> wrote:
>> On 31 August 2010 17:02, sebb <se...@gmail.com> wrote:
>>> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> I just added the xdoc version of the documentation present in the
>>>> package.html files.
>>>
>>> The package.html files are normally used to annotate the Javadoc output.
>>>
>>> However in this case these files have got a lot more content than is
>>> normally present in the Javadoc.
>>>
>>>> Do you think these last can be removed, since
>>>> would be redundant with the new developers guide?
>>>
>>> There should at least be minimal package.html files for Javadoc usage,
>>> so I don't think the files should be removed entirely, but they could
>>> be replaced with much simpler versions.
>>>
>>>> At this stage, we
>>>> should maintain two different data sources with same information, I'd
>>>> propose to drop the existing one, but let choose together.
>>>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>>>> that contains informations that maven can generate automatically, do
>>>> you think we can drop it, when dropping the ant build?
>>>
>>> +1 to dropping MANIFEST.MF.
>>>
>>>> Thanks in advance, have a nice day!
>>>> Simo
>>>>
>>>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>>>
>>
>> Forgot to add - could update JUnit to the latest 4.x release, i.e. 4.8.1
>>
>> ---------------------------------------------------------------------
>> 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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Tue, Aug 31, 2010 at 4:12 PM, sebb <se...@gmail.com> wrote:
> On 31 August 2010 19:29, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Seb,
>> thanks for your feedbacks, always appreciated! I know and understand
>> the need of having the package.html files, but what do you think about
>> replacing them with the package-info.java files? It should be the
>> same, or not? I've been working with them and found it very
>> comfortables.
>
> Never used them, so I don't know.
>
> Do they cause any problems with IDEs or Maven?
> They are .java files - so do they end up as .class files?
>
<snip/>
Depends on the JDK and IDE version(s) I suppose. Having used them, I
don't recollect seeing those .class files in m2 built jars (IIRC, that
was with JDK 1.6). However, I also do recollect seeing such .class
files in my IDE (IIRC, some older Eclipse at the time). It'd be good
to check the build artifacts but modulo that am generally in favor of
moving to the now preferred package-info.java instead.
>> I'll start staking care of migrating the JUnit dependency, is it fine
>> for you just adding the @Test annotation on existing methods, without
>> renaming them? The number of tests is quite large... :P
>
> I would not bother with converting the existing tests.
>
<snap/>
Agreed.
-Rahul
>> Thanks in advance, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 31 August 2010 19:29, Simone Tripodi <si...@gmail.com> wrote:
> Hi Seb,
> thanks for your feedbacks, always appreciated! I know and understand
> the need of having the package.html files, but what do you think about
> replacing them with the package-info.java files? It should be the
> same, or not? I've been working with them and found it very
> comfortables.
Never used them, so I don't know.
Do they cause any problems with IDEs or Maven?
They are .java files - so do they end up as .class files?
> I'll start staking care of migrating the JUnit dependency, is it fine
> for you just adding the @Test annotation on existing methods, without
> renaming them? The number of tests is quite large... :P
I would not bother with converting the existing tests.
> Thanks in advance, have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Tue, Aug 31, 2010 at 6:09 PM, sebb <se...@gmail.com> wrote:
>> On 31 August 2010 17:02, sebb <se...@gmail.com> wrote:
>>> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>>>> Hi Rahul,
>>>> I just added the xdoc version of the documentation present in the
>>>> package.html files.
>>>
>>> The package.html files are normally used to annotate the Javadoc output.
>>>
>>> However in this case these files have got a lot more content than is
>>> normally present in the Javadoc.
>>>
>>>> Do you think these last can be removed, since
>>>> would be redundant with the new developers guide?
>>>
>>> There should at least be minimal package.html files for Javadoc usage,
>>> so I don't think the files should be removed entirely, but they could
>>> be replaced with much simpler versions.
>>>
>>>> At this stage, we
>>>> should maintain two different data sources with same information, I'd
>>>> propose to drop the existing one, but let choose together.
>>>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>>>> that contains informations that maven can generate automatically, do
>>>> you think we can drop it, when dropping the ant build?
>>>
>>> +1 to dropping MANIFEST.MF.
>>>
>>>> Thanks in advance, have a nice day!
>>>> Simo
>>>>
>>>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>>>
>>
>> Forgot to add - could update JUnit to the latest 4.x release, i.e. 4.8.1
>>
>> ---------------------------------------------------------------------
>> 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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Seb,
thanks for your feedbacks, always appreciated! I know and understand
the need of having the package.html files, but what do you think about
replacing them with the package-info.java files? It should be the
same, or not? I've been working with them and found it very
comfortables.
I'll start staking care of migrating the JUnit dependency, is it fine
for you just adding the @Test annotation on existing methods, without
renaming them? The number of tests is quite large... :P
Thanks in advance, have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Aug 31, 2010 at 6:09 PM, sebb <se...@gmail.com> wrote:
> On 31 August 2010 17:02, sebb <se...@gmail.com> wrote:
>> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi Rahul,
>>> I just added the xdoc version of the documentation present in the
>>> package.html files.
>>
>> The package.html files are normally used to annotate the Javadoc output.
>>
>> However in this case these files have got a lot more content than is
>> normally present in the Javadoc.
>>
>>> Do you think these last can be removed, since
>>> would be redundant with the new developers guide?
>>
>> There should at least be minimal package.html files for Javadoc usage,
>> so I don't think the files should be removed entirely, but they could
>> be replaced with much simpler versions.
>>
>>> At this stage, we
>>> should maintain two different data sources with same information, I'd
>>> propose to drop the existing one, but let choose together.
>>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>>> that contains informations that maven can generate automatically, do
>>> you think we can drop it, when dropping the ant build?
>>
>> +1 to dropping MANIFEST.MF.
>>
>>> Thanks in advance, have a nice day!
>>> Simo
>>>
>>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>>
>
> Forgot to add - could update JUnit to the latest 4.x release, i.e. 4.8.1
>
> ---------------------------------------------------------------------
> 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
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 31 August 2010 17:02, sebb <se...@gmail.com> wrote:
> On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Rahul,
>> I just added the xdoc version of the documentation present in the
>> package.html files.
>
> The package.html files are normally used to annotate the Javadoc output.
>
> However in this case these files have got a lot more content than is
> normally present in the Javadoc.
>
>> Do you think these last can be removed, since
>> would be redundant with the new developers guide?
>
> There should at least be minimal package.html files for Javadoc usage,
> so I don't think the files should be removed entirely, but they could
> be replaced with much simpler versions.
>
>> At this stage, we
>> should maintain two different data sources with same information, I'd
>> propose to drop the existing one, but let choose together.
>> Another small question: in src/conf there is a MANIFEST.MF[1] file
>> that contains informations that maven can generate automatically, do
>> you think we can drop it, when dropping the ant build?
>
> +1 to dropping MANIFEST.MF.
>
>> Thanks in advance, have a nice day!
>> Simo
>>
>> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>>
Forgot to add - could update JUnit to the latest 4.x release, i.e. 4.8.1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [Digester] working toward a release
Posted by sebb <se...@gmail.com>.
On 31 August 2010 14:39, Simone Tripodi <si...@gmail.com> wrote:
> Hi Rahul,
> I just added the xdoc version of the documentation present in the
> package.html files.
The package.html files are normally used to annotate the Javadoc output.
However in this case these files have got a lot more content than is
normally present in the Javadoc.
> Do you think these last can be removed, since
> would be redundant with the new developers guide?
There should at least be minimal package.html files for Javadoc usage,
so I don't think the files should be removed entirely, but they could
be replaced with much simpler versions.
> At this stage, we
> should maintain two different data sources with same information, I'd
> propose to drop the existing one, but let choose together.
> Another small question: in src/conf there is a MANIFEST.MF[1] file
> that contains informations that maven can generate automatically, do
> you think we can drop it, when dropping the ant build?
+1 to dropping MANIFEST.MF.
> Thanks in advance, have a nice day!
> Simo
>
> [1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sun, Aug 29, 2010 at 7:59 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Sun, Aug 29, 2010 at 5:03 AM, Simone Tripodi
>> <si...@gmail.com> wrote:
>>> Hi All guys,
>>> since the Commons PMC awarded me giving me the writing rights, I'd
>>> like to work on the Digester to publish a new release, since a new
>>> feature will be contained.
>> <snip/>
>>
>> Super!
>>
>>
>>> For what I can see, there are few build-related minor issues:
>>>
>>> - ant build: dropped in Gump, do we want to maintain it or completely remove?
>> <snap/>
>>
>> Upto you, can remove IMO.
>>
>>
>>> - maven build: do we want to maintain the current directory structure
>>> or move to the default structure?
>> <snip/>
>>
>> If you want to improve it, great.
>>
>>
>>> - documentation: It would be nice, IMHO, porting the current
>>> documentation from the package.html files to apt format to be included
>>> in the generated site. Existing xdoc can also ported to the apt ormat.
>>> WDYT?
>> <snap/>
>>
>> +1 to porting to package.html to a "guide" on the website.
>>
>> I like xdoc, I don't like apt much. However, its unlikely that I will
>> be writing much [digester] documentation hereafter. Perhaps its best
>> that you write the new docs in the format of your choosing and leave
>> any of the old stuff as-is.
>>
>>
>>> - code: a review wouldn't be bad :P
>>>
>> <snip/>
>>
>> Generally looked OK. You can help yourself to Checkstyle, Clirr, CPD,
>> FindBugs, PMD, RAT and friends (in fact, it'd be great to do that
>> before the release anyway).
>>
>> -Rahul
>>
>>
>>
>>> Please let me know, have a nice day!!!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul,
I just added the xdoc version of the documentation present in the
package.html files. Do you think these last can be removed, since
would be redundant with the new developers guide? At this stage, we
should maintain two different data sources with same information, I'd
propose to drop the existing one, but let choose together.
Another small question: in src/conf there is a MANIFEST.MF[1] file
that contains informations that maven can generate automatically, do
you think we can drop it, when dropping the ant build?
Thanks in advance, have a nice day!
Simo
[1] https://svn.apache.org/repos/asf/commons/proper/digester/trunk/src/conf/MANIFEST.MF
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Aug 29, 2010 at 7:59 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sun, Aug 29, 2010 at 5:03 AM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Hi All guys,
>> since the Commons PMC awarded me giving me the writing rights, I'd
>> like to work on the Digester to publish a new release, since a new
>> feature will be contained.
> <snip/>
>
> Super!
>
>
>> For what I can see, there are few build-related minor issues:
>>
>> - ant build: dropped in Gump, do we want to maintain it or completely remove?
> <snap/>
>
> Upto you, can remove IMO.
>
>
>> - maven build: do we want to maintain the current directory structure
>> or move to the default structure?
> <snip/>
>
> If you want to improve it, great.
>
>
>> - documentation: It would be nice, IMHO, porting the current
>> documentation from the package.html files to apt format to be included
>> in the generated site. Existing xdoc can also ported to the apt ormat.
>> WDYT?
> <snap/>
>
> +1 to porting to package.html to a "guide" on the website.
>
> I like xdoc, I don't like apt much. However, its unlikely that I will
> be writing much [digester] documentation hereafter. Perhaps its best
> that you write the new docs in the format of your choosing and leave
> any of the old stuff as-is.
>
>
>> - code: a review wouldn't be bad :P
>>
> <snip/>
>
> Generally looked OK. You can help yourself to Checkstyle, Clirr, CPD,
> FindBugs, PMD, RAT and friends (in fact, it'd be great to do that
> before the release anyway).
>
> -Rahul
>
>
>
>> Please let me know, have a nice day!!!
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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
Re: [Digester] working toward a release
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sun, Aug 29, 2010 at 5:03 AM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi All guys,
> since the Commons PMC awarded me giving me the writing rights, I'd
> like to work on the Digester to publish a new release, since a new
> feature will be contained.
<snip/>
Super!
> For what I can see, there are few build-related minor issues:
>
> - ant build: dropped in Gump, do we want to maintain it or completely remove?
<snap/>
Upto you, can remove IMO.
> - maven build: do we want to maintain the current directory structure
> or move to the default structure?
<snip/>
If you want to improve it, great.
> - documentation: It would be nice, IMHO, porting the current
> documentation from the package.html files to apt format to be included
> in the generated site. Existing xdoc can also ported to the apt ormat.
> WDYT?
<snap/>
+1 to porting to package.html to a "guide" on the website.
I like xdoc, I don't like apt much. However, its unlikely that I will
be writing much [digester] documentation hereafter. Perhaps its best
that you write the new docs in the format of your choosing and leave
any of the old stuff as-is.
> - code: a review wouldn't be bad :P
>
<snip/>
Generally looked OK. You can help yourself to Checkstyle, Clirr, CPD,
FindBugs, PMD, RAT and friends (in fact, it'd be great to do that
before the release anyway).
-Rahul
> Please let me know, have a nice day!!!
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org