Re: Recreating Tomahawk 1.1.6
Thank you, Simon! With a checkout of the branch and install of the artifact, the Tomahawk 1.1.6 tag builds and works. With this build of Tomahawk 1.1.6, I have validated Rodrigo Macedo's patch for TOMAHAWK-1249. Thanks, again! -Jan On Thu, Aug 21, 2008 at 1:27 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] schrieb: >> >> Jan Nielsen schrieb: >>> >>> To get a bug fix into 1.1.6, I would like to recreate the Tomahawk >>> 1.1.6 build. I grabbed the code at: >>> >>> http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_6 >>> >>> and tried to build that with "mvn -Djsf=12 -Dtomahawk=12 clean >>> package" but it fails to resolve the dependency on >>> myfaces-shared-tomahawk 2.0.6: >>> >>> org.apache.myfaces.shared:myfaces-shared-tomahawk:jar:2.0.6 >>> >>> Reviewing a couple of repositories, it looks like 2.0.x releases are >>> there, /except/ for 2.0.6. I'm fine with building it myself but it >>> also looks like the 2.0.6 is missing from subversion: >>> >>> http://svn.apache.org/repos/asf/myfaces/shared/tags >>> >>> So, can the Tomahawk 1.1.6 build be reproduced? Is there a recipe, a >>> wiki, a script, or a spot in subversion from which the Tomahawk 1.1.6 >>> release can be built? >>> >>> >> >> Hmm..that is weird indeed. I'll check the email archives. >> >> Tomahawk 1.1.6 does indeed depend on shared-2.0.6, and as you say there >> appears to be neither a tag nor a released jar for shared-2.0.6. >> >> The jsf1.2 "flavour" of tomahawk has only been added *after* the 1.1.6 >> tomahawk release. So the "-Djsf=12 -Dtomahawk=12" options are not valid when >> building the 1.1.6 release. Note that normal tomahawk 1.1.x runs fine on >> both JSF1.1 and JSF1.2. However there are some optimisations that can be >> added by building against JSF1.2, hence the new "flavour". But that doesn't >> change the fact that shared-2.0.6 is missing. > > I see there is a 2.0.6 dir in > http://svn.apache.org/repos/asf/myfaces/shared/branches > > And the pom there has the released version number. > > So I would guess that whoever did the release did a "mvn install" from that > branch dir, then build the final release of tomahawk but forgot to: > * move the branch to the tags dir > * deploy the shared jar to the release repo > > So to rebuild tomahawk 1.1.6, you should be able to check out that branch > dir, do "mvn install" locally then build tomahawk 1.1.6. > > In some ways it *is* a little odd to deploy the shared jar to the release > repo, as nobody will actually ever use it - except people like yourself who > want to rebuild the official release. But for tidiness it probably *should* > be done. And certainly an svn copy should have existed in the tag dir, not > just "branches" (although there is technically no difference when using > svn). > > Regards, > Simon > >
Re: [commons] upload myfaces commons site
thank you very much !! On Thu, Aug 21, 2008 at 6:59 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > Hi > > This mail is for inform the intention of create and upload a site for > myfaces commons (1.1 and 1.2). We don't have any release yet, but I hope to > do it soon. > > The idea is have a base module and separate sites for 1.1 and 1.2. This > layout probably will be used on tomahawk. > > If no objections I'll update the site soon. > > regards > > Leonardo Uribe > > > -- Matthias Wessendorf Need JSF and Web 2.0? http://code.google.com/p/facesgoodies further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
[commons] upload myfaces commons site
Hi This mail is for inform the intention of create and upload a site for myfaces commons (1.1 and 1.2). We don't have any release yet, but I hope to do it soon. The idea is have a base module and separate sites for 1.1 and 1.2. This layout probably will be used on tomahawk. If no objections I'll update the site soon. regards Leonardo Uribe
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Matthias Wessendorf-4 wrote: > > On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote: >> Hi, >> >> isn't the fixVersion field needed for unresolved issues to prepare the >> roadmap? > > yes. I think the main point is, that actually bug-filers abuse the field. > They understand it as a "wish list", like "you have to fix my bug in > version 'yesterday'" :) > > -Matthias > > Hi, Just for statistics: me inadvertently misused 'fixVersion' to notify that a patch, I've submitted for an issue, is against this specific version. And a little offtopic: what is the policy of Trinidad's issues triage/review? For instance, are patches for unresolved issues reviewed before the release of the next version? Thanks, Alexey -- View this message in context: http://www.nabble.com/Jira-configuration---%28was-Fwd%3A--Trinidad--Missing-issue-in-1.0.8%29-tp18839302p19089778.html Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
On Thu, Aug 21, 2008 at 11:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
> Maybe we could restrict the EditScreen to commiters?
+1
> Bug-filers can add comments if they want to make changes/additions.
+1
it is really odd, that the jira software isn't able to have that.
so... +1 on a feature request as well.
Do we (ASF) have a special contact form (for "customers")?
-Matthias
>
> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
>> Ok, re-enabled the "fix version" on the edit screen.
>> --Manfred
>>
>> On Thu, Aug 21, 2008 at 10:50 AM, Matthias Wessendorf <[EMAIL PROTECTED]>
>> wrote:
>>> On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
Hi,
isn't the fixVersion field needed for unresolved issues to prepare the
roadmap?
>>>
>>> yes. I think the main point is, that actually bug-filers abuse the field.
>>> They understand it as a "wish list", like "you have to fix my bug in
>>> version 'yesterday'" :)
>>>
>>> -Matthias
>>>
Regards,
Volker
2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
> The "Fix version" field is still there on the "Resolve Issue" page!
> That is where it belongs to. Right?
>
> But: I see that there are 964 issues (in all MyFaces projects) with
> Status "Resolved" that have no "Fix Version". Which is weird!
>
> What I COULD do is (re)enable the "fix version" on the Edit Screen.
> But I CANNOT restrict it to committers only. There is no way in Jira
> AFAIK.
>
> What I suggest:
> - Leave it that way. Fix versions normally set during resolve workflow.
> - Fix missing fix versions by doing bulk operations ("Fix version" is
> editable there)
>
> Thoughts?
>
> --Manfred
>
>
>
>
>
> On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
> <[EMAIL PROTECTED]> wrote:
>> Hello Manfred,
>>
>> how can I edit the fix version field, now?
>>
>> I would like to prepare the tobago-1.0.18 release.
>>
>> Can you revert the MyFaces Screen configuration for Tobago.
>>
>> Regards
>>
>> Bernd
>>
>> Manfred Geiler schrieb:
>>> The Jira permissions settings cannot be adjusted on field level.
>>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>>> With this configuration the "Fix version" field should no longer show
>>> up on the "Edit" screen.
>>> I activated this scheme for Trinidad.
>>> Please check it out. If ok, I will activate this scheme for all other
>>> MyFaces projects as well.
>>>
>>> --Manfred
>>>
>>>
>>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL
>>> PROTECTED]> wrote:
Hi,
we had the discussion already in the past.
I'd love to see that the fix-version/s is not! editable by filers.
Greetings,
Matthias
-- Forwarded message --
From: Rottstock, Sven <[EMAIL PROTECTED]>
Date: Tue, Aug 5, 2008 at 10:35 AM
Subject: [Trinidad] Missing issue in 1.0.8
To: dev@myfaces.apache.org
Hi Devs,
i have seen that the patch of TRINIDAD-1010 was not included in the
1.0.8 release but was listed in the release notes. Is there anything
wrong with it or was the patch only forgotten to submit?
Regards,
Sven
>>>
>
--
inexso - information exchange solutions GmbH
Bismarckstraße 13 | 26122 Oldenburg
Tel.: +49 441 4082 356 |
FAX: +49 441 4082 355 | www.inexso.de
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> Need JSF and Web 2.0?
>>> http://code.google.com/p/facesgoodies
>>>
>>> further stuff:
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> mail: matzew-at-apache-dot-org
>>
>
>
>
> --
> inexso - information exchange solutions GmbH
> Bismarckstraße 13 | 26122 Oldenburg
> Tel.: +49 441 4082 356 |
> FAX: +49 441 4082 355 | www.inexso.de
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Maybe we could restrict the EditScreen to commiters?
Bug-filers can add comments if they want to make changes/additions.
2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
> Ok, re-enabled the "fix version" on the edit screen.
> --Manfred
>
> On Thu, Aug 21, 2008 at 10:50 AM, Matthias Wessendorf <[EMAIL PROTECTED]>
> wrote:
>> On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> isn't the fixVersion field needed for unresolved issues to prepare the
>>> roadmap?
>>
>> yes. I think the main point is, that actually bug-filers abuse the field.
>> They understand it as a "wish list", like "you have to fix my bug in
>> version 'yesterday'" :)
>>
>> -Matthias
>>
>>>
>>>
>>> Regards,
>>>Volker
>>>
>>> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
The "Fix version" field is still there on the "Resolve Issue" page!
That is where it belongs to. Right?
But: I see that there are 964 issues (in all MyFaces projects) with
Status "Resolved" that have no "Fix Version". Which is weird!
What I COULD do is (re)enable the "fix version" on the Edit Screen.
But I CANNOT restrict it to committers only. There is no way in Jira
AFAIK.
What I suggest:
- Leave it that way. Fix versions normally set during resolve workflow.
- Fix missing fix versions by doing bulk operations ("Fix version" is
editable there)
Thoughts?
--Manfred
On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
<[EMAIL PROTECTED]> wrote:
> Hello Manfred,
>
> how can I edit the fix version field, now?
>
> I would like to prepare the tobago-1.0.18 release.
>
> Can you revert the MyFaces Screen configuration for Tobago.
>
> Regards
>
> Bernd
>
> Manfred Geiler schrieb:
>> The Jira permissions settings cannot be adjusted on field level.
>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>> With this configuration the "Fix version" field should no longer show
>> up on the "Edit" screen.
>> I activated this scheme for Trinidad.
>> Please check it out. If ok, I will activate this scheme for all other
>> MyFaces projects as well.
>>
>> --Manfred
>>
>>
>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
>> wrote:
>>> Hi,
>>>
>>> we had the discussion already in the past.
>>> I'd love to see that the fix-version/s is not! editable by filers.
>>>
>>> Greetings,
>>> Matthias
>>>
>>>
>>> -- Forwarded message --
>>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>>> Date: Tue, Aug 5, 2008 at 10:35 AM
>>> Subject: [Trinidad] Missing issue in 1.0.8
>>> To: dev@myfaces.apache.org
>>>
>>>
>>> Hi Devs,
>>>
>>> i have seen that the patch of TRINIDAD-1010 was not included in the
>>> 1.0.8 release but was listed in the release notes. Is there anything
>>> wrong with it or was the patch only forgotten to submit?
>>>
>>> Regards,
>>>
>>> Sven
>>>
>>>
>>
>>>
>>>
>>>
>>> --
>>> inexso - information exchange solutions GmbH
>>> Bismarckstraße 13 | 26122 Oldenburg
>>> Tel.: +49 441 4082 356 |
>>> FAX: +49 441 4082 355 | www.inexso.de
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> Need JSF and Web 2.0?
>> http://code.google.com/p/facesgoodies
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
>
--
inexso - information exchange solutions GmbH
Bismarckstraße 13 | 26122 Oldenburg
Tel.: +49 441 4082 356 |
FAX: +49 441 4082 355 | www.inexso.de
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Thanks Manfred,
maybe we should open a feature request at Atlassian.
Regards
Bernd
Manfred Geiler schrieb:
> Ok, re-enabled the "fix version" on the edit screen.
> --Manfred
>
> On Thu, Aug 21, 2008 at 10:50 AM, Matthias Wessendorf <[EMAIL PROTECTED]>
> wrote:
>> On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> isn't the fixVersion field needed for unresolved issues to prepare the
>>> roadmap?
>> yes. I think the main point is, that actually bug-filers abuse the field.
>> They understand it as a "wish list", like "you have to fix my bug in
>> version 'yesterday'" :)
>>
>> -Matthias
>>
>>>
>>> Regards,
>>>Volker
>>>
>>> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
The "Fix version" field is still there on the "Resolve Issue" page!
That is where it belongs to. Right?
But: I see that there are 964 issues (in all MyFaces projects) with
Status "Resolved" that have no "Fix Version". Which is weird!
What I COULD do is (re)enable the "fix version" on the Edit Screen.
But I CANNOT restrict it to committers only. There is no way in Jira
AFAIK.
What I suggest:
- Leave it that way. Fix versions normally set during resolve workflow.
- Fix missing fix versions by doing bulk operations ("Fix version" is
editable there)
Thoughts?
--Manfred
On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
<[EMAIL PROTECTED]> wrote:
> Hello Manfred,
>
> how can I edit the fix version field, now?
>
> I would like to prepare the tobago-1.0.18 release.
>
> Can you revert the MyFaces Screen configuration for Tobago.
>
> Regards
>
> Bernd
>
> Manfred Geiler schrieb:
>> The Jira permissions settings cannot be adjusted on field level.
>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>> With this configuration the "Fix version" field should no longer show
>> up on the "Edit" screen.
>> I activated this scheme for Trinidad.
>> Please check it out. If ok, I will activate this scheme for all other
>> MyFaces projects as well.
>>
>> --Manfred
>>
>>
>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
>> wrote:
>>> Hi,
>>>
>>> we had the discussion already in the past.
>>> I'd love to see that the fix-version/s is not! editable by filers.
>>>
>>> Greetings,
>>> Matthias
>>>
>>>
>>> -- Forwarded message --
>>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>>> Date: Tue, Aug 5, 2008 at 10:35 AM
>>> Subject: [Trinidad] Missing issue in 1.0.8
>>> To: dev@myfaces.apache.org
>>>
>>>
>>> Hi Devs,
>>>
>>> i have seen that the patch of TRINIDAD-1010 was not included in the
>>> 1.0.8 release but was listed in the release notes. Is there anything
>>> wrong with it or was the patch only forgotten to submit?
>>>
>>> Regards,
>>>
>>> Sven
>>>
>>>
>>>
>>>
>>> --
>>> inexso - information exchange solutions GmbH
>>> Bismarckstraße 13 | 26122 Oldenburg
>>> Tel.: +49 441 4082 356 |
>>> FAX: +49 441 4082 355 | www.inexso.de
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> Need JSF and Web 2.0?
>> http://code.google.com/p/facesgoodies
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
>
[jira] Resolved: (TOMAHAWK-1317) CSS error
[ https://issues.apache.org/jira/browse/TOMAHAWK-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cagatay Civici resolved TOMAHAWK-1317. -- Resolution: Duplicate This issue is same as TOMAHAWK-1076 which is resolved > CSS error > - > > Key: TOMAHAWK-1317 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1317 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: Stylesheet >Affects Versions: 1.1.6 > Environment: irrelevant >Reporter: Jean-David Maillefer >Priority: Trivial > Attachments: theme.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > missing units causing CSS errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-1317) CSS error
[ https://issues.apache.org/jira/browse/TOMAHAWK-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-David Maillefer updated TOMAHAWK-1317: --- Status: Open (was: Patch Available) > CSS error > - > > Key: TOMAHAWK-1317 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1317 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: Stylesheet >Affects Versions: 1.1.6 > Environment: irrelevant >Reporter: Jean-David Maillefer >Priority: Trivial > Attachments: theme.patch > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > missing units causing CSS errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-1317) CSS error
[ https://issues.apache.org/jira/browse/TOMAHAWK-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-David Maillefer updated TOMAHAWK-1317: --- Status: Patch Available (was: Open) > CSS error > - > > Key: TOMAHAWK-1317 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1317 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: Stylesheet >Affects Versions: 1.1.6 > Environment: irrelevant >Reporter: Jean-David Maillefer >Priority: Trivial > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > missing units causing CSS errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-1317) CSS error
CSS error - Key: TOMAHAWK-1317 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1317 Project: MyFaces Tomahawk Issue Type: Bug Components: Stylesheet Affects Versions: 1.1.6 Environment: irrelevant Reporter: Jean-David Maillefer Priority: Trivial missing units causing CSS errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Ok, re-enabled the "fix version" on the edit screen.
--Manfred
On Thu, Aug 21, 2008 at 10:50 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> isn't the fixVersion field needed for unresolved issues to prepare the
>> roadmap?
>
> yes. I think the main point is, that actually bug-filers abuse the field.
> They understand it as a "wish list", like "you have to fix my bug in
> version 'yesterday'" :)
>
> -Matthias
>
>>
>>
>> Regards,
>>Volker
>>
>> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
>>> The "Fix version" field is still there on the "Resolve Issue" page!
>>> That is where it belongs to. Right?
>>>
>>> But: I see that there are 964 issues (in all MyFaces projects) with
>>> Status "Resolved" that have no "Fix Version". Which is weird!
>>>
>>> What I COULD do is (re)enable the "fix version" on the Edit Screen.
>>> But I CANNOT restrict it to committers only. There is no way in Jira
>>> AFAIK.
>>>
>>> What I suggest:
>>> - Leave it that way. Fix versions normally set during resolve workflow.
>>> - Fix missing fix versions by doing bulk operations ("Fix version" is
>>> editable there)
>>>
>>> Thoughts?
>>>
>>> --Manfred
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
>>> <[EMAIL PROTECTED]> wrote:
Hello Manfred,
how can I edit the fix version field, now?
I would like to prepare the tobago-1.0.18 release.
Can you revert the MyFaces Screen configuration for Tobago.
Regards
Bernd
Manfred Geiler schrieb:
> The Jira permissions settings cannot be adjusted on field level.
> As a workaround I added a new "MyFaces Screen" configuration to Jira.
> With this configuration the "Fix version" field should no longer show
> up on the "Edit" screen.
> I activated this scheme for Trinidad.
> Please check it out. If ok, I will activate this scheme for all other
> MyFaces projects as well.
>
> --Manfred
>
>
> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>> we had the discussion already in the past.
>> I'd love to see that the fix-version/s is not! editable by filers.
>>
>> Greetings,
>> Matthias
>>
>>
>> -- Forwarded message --
>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>> Date: Tue, Aug 5, 2008 at 10:35 AM
>> Subject: [Trinidad] Missing issue in 1.0.8
>> To: dev@myfaces.apache.org
>>
>>
>> Hi Devs,
>>
>> i have seen that the patch of TRINIDAD-1010 was not included in the
>> 1.0.8 release but was listed in the release notes. Is there anything
>> wrong with it or was the patch only forgotten to submit?
>>
>> Regards,
>>
>> Sven
>>
>>
>
>>>
>>
>>
>>
>> --
>> inexso - information exchange solutions GmbH
>> Bismarckstraße 13 | 26122 Oldenburg
>> Tel.: +49 441 4082 356 |
>> FAX: +49 441 4082 355 | www.inexso.de
>>
>
>
>
> --
> Matthias Wessendorf
>
> Need JSF and Web 2.0?
> http://code.google.com/p/facesgoodies
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
> Hi,
>
> isn't the fixVersion field needed for unresolved issues to prepare the
> roadmap?
yes. I think the main point is, that actually bug-filers abuse the field.
They understand it as a "wish list", like "you have to fix my bug in
version 'yesterday'" :)
-Matthias
>
>
> Regards,
>Volker
>
> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
>> The "Fix version" field is still there on the "Resolve Issue" page!
>> That is where it belongs to. Right?
>>
>> But: I see that there are 964 issues (in all MyFaces projects) with
>> Status "Resolved" that have no "Fix Version". Which is weird!
>>
>> What I COULD do is (re)enable the "fix version" on the Edit Screen.
>> But I CANNOT restrict it to committers only. There is no way in Jira
>> AFAIK.
>>
>> What I suggest:
>> - Leave it that way. Fix versions normally set during resolve workflow.
>> - Fix missing fix versions by doing bulk operations ("Fix version" is
>> editable there)
>>
>> Thoughts?
>>
>> --Manfred
>>
>>
>>
>>
>>
>> On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
>> <[EMAIL PROTECTED]> wrote:
>>> Hello Manfred,
>>>
>>> how can I edit the fix version field, now?
>>>
>>> I would like to prepare the tobago-1.0.18 release.
>>>
>>> Can you revert the MyFaces Screen configuration for Tobago.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>> Manfred Geiler schrieb:
The Jira permissions settings cannot be adjusted on field level.
As a workaround I added a new "MyFaces Screen" configuration to Jira.
With this configuration the "Fix version" field should no longer show
up on the "Edit" screen.
I activated this scheme for Trinidad.
Please check it out. If ok, I will activate this scheme for all other
MyFaces projects as well.
--Manfred
On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> we had the discussion already in the past.
> I'd love to see that the fix-version/s is not! editable by filers.
>
> Greetings,
> Matthias
>
>
> -- Forwarded message --
> From: Rottstock, Sven <[EMAIL PROTECTED]>
> Date: Tue, Aug 5, 2008 at 10:35 AM
> Subject: [Trinidad] Missing issue in 1.0.8
> To: dev@myfaces.apache.org
>
>
> Hi Devs,
>
> i have seen that the patch of TRINIDAD-1010 was not included in the
> 1.0.8 release but was listed in the release notes. Is there anything
> wrong with it or was the patch only forgotten to submit?
>
> Regards,
>
> Sven
>
>
>>
>
>
>
> --
> inexso - information exchange solutions GmbH
> Bismarckstraße 13 | 26122 Oldenburg
> Tel.: +49 441 4082 356 |
> FAX: +49 441 4082 355 | www.inexso.de
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Hi,
isn't the fixVersion field needed for unresolved issues to prepare the roadmap?
Regards,
Volker
2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
> The "Fix version" field is still there on the "Resolve Issue" page!
> That is where it belongs to. Right?
>
> But: I see that there are 964 issues (in all MyFaces projects) with
> Status "Resolved" that have no "Fix Version". Which is weird!
>
> What I COULD do is (re)enable the "fix version" on the Edit Screen.
> But I CANNOT restrict it to committers only. There is no way in Jira
> AFAIK.
>
> What I suggest:
> - Leave it that way. Fix versions normally set during resolve workflow.
> - Fix missing fix versions by doing bulk operations ("Fix version" is
> editable there)
>
> Thoughts?
>
> --Manfred
>
>
>
>
>
> On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
> <[EMAIL PROTECTED]> wrote:
>> Hello Manfred,
>>
>> how can I edit the fix version field, now?
>>
>> I would like to prepare the tobago-1.0.18 release.
>>
>> Can you revert the MyFaces Screen configuration for Tobago.
>>
>> Regards
>>
>> Bernd
>>
>> Manfred Geiler schrieb:
>>> The Jira permissions settings cannot be adjusted on field level.
>>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>>> With this configuration the "Fix version" field should no longer show
>>> up on the "Edit" screen.
>>> I activated this scheme for Trinidad.
>>> Please check it out. If ok, I will activate this scheme for all other
>>> MyFaces projects as well.
>>>
>>> --Manfred
>>>
>>>
>>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
>>> wrote:
Hi,
we had the discussion already in the past.
I'd love to see that the fix-version/s is not! editable by filers.
Greetings,
Matthias
-- Forwarded message --
From: Rottstock, Sven <[EMAIL PROTECTED]>
Date: Tue, Aug 5, 2008 at 10:35 AM
Subject: [Trinidad] Missing issue in 1.0.8
To: dev@myfaces.apache.org
Hi Devs,
i have seen that the patch of TRINIDAD-1010 was not included in the
1.0.8 release but was listed in the release notes. Is there anything
wrong with it or was the patch only forgotten to submit?
Regards,
Sven
>>>
>
--
inexso - information exchange solutions GmbH
Bismarckstraße 13 | 26122 Oldenburg
Tel.: +49 441 4082 356 |
FAX: +49 441 4082 355 | www.inexso.de
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
The "Fix version" field is still there on the "Resolve Issue" page!
That is where it belongs to. Right?
But: I see that there are 964 issues (in all MyFaces projects) with
Status "Resolved" that have no "Fix Version". Which is weird!
What I COULD do is (re)enable the "fix version" on the Edit Screen.
But I CANNOT restrict it to committers only. There is no way in Jira
AFAIK.
What I suggest:
- Leave it that way. Fix versions normally set during resolve workflow.
- Fix missing fix versions by doing bulk operations ("Fix version" is
editable there)
Thoughts?
--Manfred
On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
<[EMAIL PROTECTED]> wrote:
> Hello Manfred,
>
> how can I edit the fix version field, now?
>
> I would like to prepare the tobago-1.0.18 release.
>
> Can you revert the MyFaces Screen configuration for Tobago.
>
> Regards
>
> Bernd
>
> Manfred Geiler schrieb:
>> The Jira permissions settings cannot be adjusted on field level.
>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>> With this configuration the "Fix version" field should no longer show
>> up on the "Edit" screen.
>> I activated this scheme for Trinidad.
>> Please check it out. If ok, I will activate this scheme for all other
>> MyFaces projects as well.
>>
>> --Manfred
>>
>>
>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
>> wrote:
>>> Hi,
>>>
>>> we had the discussion already in the past.
>>> I'd love to see that the fix-version/s is not! editable by filers.
>>>
>>> Greetings,
>>> Matthias
>>>
>>>
>>> -- Forwarded message --
>>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>>> Date: Tue, Aug 5, 2008 at 10:35 AM
>>> Subject: [Trinidad] Missing issue in 1.0.8
>>> To: dev@myfaces.apache.org
>>>
>>>
>>> Hi Devs,
>>>
>>> i have seen that the patch of TRINIDAD-1010 was not included in the
>>> 1.0.8 release but was listed in the release notes. Is there anything
>>> wrong with it or was the patch only forgotten to submit?
>>>
>>> Regards,
>>>
>>> Sven
>>>
>>>
>>
[jira] Resolved: (TOMAHAWK-1315) Focus feature for toggleLink
[ https://issues.apache.org/jira/browse/TOMAHAWK-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cagatay Civici resolved TOMAHAWK-1315. -- Resolution: Fixed Fix Version/s: 1.1.7-SNAPSHOT > Focus feature for toggleLink > > > Key: TOMAHAWK-1315 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1315 > Project: MyFaces Tomahawk > Issue Type: New Feature >Affects Versions: 1.1.7-SNAPSHOT >Reporter: Cagatay Civici >Assignee: Cagatay Civici >Priority: Minor > Fix For: 1.1.7-SNAPSHOT > > > This new feature allows focusing on the component being shown when toggleLink > is clicked. The new attribute onClickFocusId will identify the component that > will receive the focus manually, if this attribute is not supplied the > component stated with the "for" attribute of toggleLink should be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
I missed the edit as well. So, it would be cool: -fix version NOT available on "create issue" (currently implemented) -fix versin available on edit. BUT! only for committers -Matthias On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann <[EMAIL PROTECTED]> wrote: > Hello Manfred, > > how can I edit the fix version field, now? > > I would like to prepare the tobago-1.0.18 release. > > Can you revert the MyFaces Screen configuration for Tobago. > > Regards > > Bernd > > Manfred Geiler schrieb: >> The Jira permissions settings cannot be adjusted on field level. >> As a workaround I added a new "MyFaces Screen" configuration to Jira. >> With this configuration the "Fix version" field should no longer show >> up on the "Edit" screen. >> I activated this scheme for Trinidad. >> Please check it out. If ok, I will activate this scheme for all other >> MyFaces projects as well. >> >> --Manfred >> >> >> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]> >> wrote: >>> Hi, >>> >>> we had the discussion already in the past. >>> I'd love to see that the fix-version/s is not! editable by filers. >>> >>> Greetings, >>> Matthias >>> >>> >>> -- Forwarded message -- >>> From: Rottstock, Sven <[EMAIL PROTECTED]> >>> Date: Tue, Aug 5, 2008 at 10:35 AM >>> Subject: [Trinidad] Missing issue in 1.0.8 >>> To: dev@myfaces.apache.org >>> >>> >>> Hi Devs, >>> >>> i have seen that the patch of TRINIDAD-1010 was not included in the >>> 1.0.8 release but was listed in the release notes. Is there anything >>> wrong with it or was the patch only forgotten to submit? >>> >>> Regards, >>> >>> Sven >>> >>> >> > -- Matthias Wessendorf Need JSF and Web 2.0? http://code.google.com/p/facesgoodies further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)
Hello Manfred, how can I edit the fix version field, now? I would like to prepare the tobago-1.0.18 release. Can you revert the MyFaces Screen configuration for Tobago. Regards Bernd Manfred Geiler schrieb: > The Jira permissions settings cannot be adjusted on field level. > As a workaround I added a new "MyFaces Screen" configuration to Jira. > With this configuration the "Fix version" field should no longer show > up on the "Edit" screen. > I activated this scheme for Trinidad. > Please check it out. If ok, I will activate this scheme for all other > MyFaces projects as well. > > --Manfred > > > On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]> > wrote: >> Hi, >> >> we had the discussion already in the past. >> I'd love to see that the fix-version/s is not! editable by filers. >> >> Greetings, >> Matthias >> >> >> -- Forwarded message -- >> From: Rottstock, Sven <[EMAIL PROTECTED]> >> Date: Tue, Aug 5, 2008 at 10:35 AM >> Subject: [Trinidad] Missing issue in 1.0.8 >> To: dev@myfaces.apache.org >> >> >> Hi Devs, >> >> i have seen that the patch of TRINIDAD-1010 was not included in the >> 1.0.8 release but was listed in the release notes. Is there anything >> wrong with it or was the patch only forgotten to submit? >> >> Regards, >> >> Sven >> >> >
Re: Recreating Tomahawk 1.1.6
[EMAIL PROTECTED] schrieb: Jan Nielsen schrieb: To get a bug fix into 1.1.6, I would like to recreate the Tomahawk 1.1.6 build. I grabbed the code at: http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_6 and tried to build that with "mvn -Djsf=12 -Dtomahawk=12 clean package" but it fails to resolve the dependency on myfaces-shared-tomahawk 2.0.6: org.apache.myfaces.shared:myfaces-shared-tomahawk:jar:2.0.6 Reviewing a couple of repositories, it looks like 2.0.x releases are there, /except/ for 2.0.6. I'm fine with building it myself but it also looks like the 2.0.6 is missing from subversion: http://svn.apache.org/repos/asf/myfaces/shared/tags So, can the Tomahawk 1.1.6 build be reproduced? Is there a recipe, a wiki, a script, or a spot in subversion from which the Tomahawk 1.1.6 release can be built? Hmm..that is weird indeed. I'll check the email archives. Tomahawk 1.1.6 does indeed depend on shared-2.0.6, and as you say there appears to be neither a tag nor a released jar for shared-2.0.6. The jsf1.2 "flavour" of tomahawk has only been added *after* the 1.1.6 tomahawk release. So the "-Djsf=12 -Dtomahawk=12" options are not valid when building the 1.1.6 release. Note that normal tomahawk 1.1.x runs fine on both JSF1.1 and JSF1.2. However there are some optimisations that can be added by building against JSF1.2, hence the new "flavour". But that doesn't change the fact that shared-2.0.6 is missing. I see there is a 2.0.6 dir in http://svn.apache.org/repos/asf/myfaces/shared/branches And the pom there has the released version number. So I would guess that whoever did the release did a "mvn install" from that branch dir, then build the final release of tomahawk but forgot to: * move the branch to the tags dir * deploy the shared jar to the release repo So to rebuild tomahawk 1.1.6, you should be able to check out that branch dir, do "mvn install" locally then build tomahawk 1.1.6. In some ways it *is* a little odd to deploy the shared jar to the release repo, as nobody will actually ever use it - except people like yourself who want to rebuild the official release. But for tidiness it probably *should* be done. And certainly an svn copy should have existed in the tag dir, not just "branches" (although there is technically no difference when using svn). Regards, Simon
Re: Recreating Tomahawk 1.1.6
Jan Nielsen schrieb: To get a bug fix into 1.1.6, I would like to recreate the Tomahawk 1.1.6 build. I grabbed the code at: http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_6 and tried to build that with "mvn -Djsf=12 -Dtomahawk=12 clean package" but it fails to resolve the dependency on myfaces-shared-tomahawk 2.0.6: org.apache.myfaces.shared:myfaces-shared-tomahawk:jar:2.0.6 Reviewing a couple of repositories, it looks like 2.0.x releases are there, /except/ for 2.0.6. I'm fine with building it myself but it also looks like the 2.0.6 is missing from subversion: http://svn.apache.org/repos/asf/myfaces/shared/tags So, can the Tomahawk 1.1.6 build be reproduced? Is there a recipe, a wiki, a script, or a spot in subversion from which the Tomahawk 1.1.6 release can be built? Hmm..that is weird indeed. I'll check the email archives. Tomahawk 1.1.6 does indeed depend on shared-2.0.6, and as you say there appears to be neither a tag nor a released jar for shared-2.0.6. The jsf1.2 "flavour" of tomahawk has only been added *after* the 1.1.6 tomahawk release. So the "-Djsf=12 -Dtomahawk=12" options are not valid when building the 1.1.6 release. Note that normal tomahawk 1.1.x runs fine on both JSF1.1 and JSF1.2. However there are some optimisations that can be added by building against JSF1.2, hence the new "flavour". But that doesn't change the fact that shared-2.0.6 is missing. Regards, Simon
