You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fortress@directory.apache.org by "Oleksandr Bodriagov (Polystar)" <ol...@polystar.com> on 2015/04/30 17:02:17 UTC
small bugs in fortress-web
Hi,
I have 4 problems with fortress-web.
Problem #1:
I wanted to add two permissions using fortress-web, but it didn't work.
Permission 1:
- Object Name = https://galileo/blabla
- Operation Name = GET
- Roles = myreader
Permission 2:
- Object Name = https://galileo/blabla
- Operation Name = POST
- Roles = myreader
I got two POST permissions instead.
Problem #2:
Role's temporal constraints End Date 09/01/2111 is shown as 21110801 in the role list/table.
Problem #3:
Roles defined via fortress-web lose Begin Time in the table view after modifying lock dates.
Problem #4:
Modification of Begin Date (or Begin Time) leads to the month change in Begin Lock and End Lock.
/Oleksandr
Re: small bugs in fortress-web
Posted by Shawn McKinney <sm...@apache.org>.
> On Apr 30, 2015, at 11:02 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>
> Hi Oleksandr,
>
> thanks a lot for all those bugs reports, they are extremelly useful !
>
> May I suggest you use a slightly more sophisticated tool to fill such
> bugs report ? We are using JIRA for that (see on
> http://directory.apache.org/issue-tracking.html).
>
> The biggest advantage of using JIRA, for you and for us, is that you can
> be sure we won't forget to check and fix the issues, as they will be
> added to the project roadmap, while mails may slip unoticed for a few
> days, then be totally forgotten...
>
> Many thanks !
This time because the bugs were easy to find and fix I went ahead and took care of creating the issue:
https://issues.apache.org/jira/browse/FC-98
But I agree with Emmanuel. It would be helpful to us Oleksandr as you find problems to go ahead and create jira issues. In addition to ensuring we don’t lose sight of anything, jira is useful to post additional forensic info, e.g. logs, screen shots, etc..
Shawn
smckinney@apache.org
Re: small bugs in fortress-web
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 30/04/15 17:02, Oleksandr Bodriagov (Polystar) a écrit :
> Hi,
Hi Oleksandr,
thanks a lot for all those bugs reports, they are extremelly useful !
May I suggest you use a slightly more sophisticated tool to fill such
bugs report ? We are using JIRA for that (see on
http://directory.apache.org/issue-tracking.html).
The biggest advantage of using JIRA, for you and for us, is that you can
be sure we won't forget to check and fix the issues, as they will be
added to the project roadmap, while mails may slip unoticed for a few
days, then be totally forgotten...
Many thanks !
>
> I have 4 problems with fortress-web.
> Problem #1:
> I wanted to add two permissions using fortress-web, but it didn't work.
> Permission 1:
> - Object Name = https://galileo/blabla
> - Operation Name = GET
> - Roles = myreader
> Permission 2:
> - Object Name = https://galileo/blabla
> - Operation Name = POST
> - Roles = myreader
>
> I got two POST permissions instead.
>
> Problem #2:
> Role's temporal constraints End Date 09/01/2111 is shown as 21110801 in the role list/table.
>
> Problem #3:
> Roles defined via fortress-web lose Begin Time in the table view after modifying lock dates.
>
> Problem #4:
> Modification of Begin Date (or Begin Time) leads to the month change in Begin Lock and End Lock.
>
> /Oleksandr
>
>
>
Re: small bugs in fortress-web
Posted by Shawn McKinney <sm...@apache.org>.
> On May 1, 2015, at 6:32 AM, Oleksandr Bodriagov (Polystar) <ol...@polystar.com> wrote:
>
> Ok, I will use Jira next time. I was just being too lazy. I have forgotten
> my Jira password and didnąt want to go through all the hustle of restoring
> it and creating issues :)
>
> Coming back to the permissions, I have create a ticket for it with a
> detailed description and screenshots:
> https://issues.apache.org/jira/browse/FC-100
>
> By the way, I do not know if it is possible in Jira to give users rights
> to modify issues created by them, but it definitely would be something
> useful.
I believe it is possible. Agree it would be useful. Assuming it has been explicitly disabled. Will look into it.
Shawn
smckinney@apache.org
Re: small bugs in fortress-web
Posted by "Oleksandr Bodriagov (Polystar)" <ol...@polystar.com>.
Hi Shawn,
Ok, I will use Jira next time. I was just being too lazy. I have forgotten
my Jira password and didn¹t want to go through all the hustle of restoring
it and creating issues :)
Coming back to the permissions, I have create a ticket for it with a
detailed description and screenshots:
https://issues.apache.org/jira/browse/FC-100
By the way, I do not know if it is possible in Jira to give users rights
to modify issues created by them, but it definitely would be something
useful.
/Oleksandr
On 1/5/2015 06:11 , "Shawn McKinney" <sm...@apache.org> wrote:
>
>> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar)
>><ol...@polystar.com> wrote:
>>
>> I have 4 problems with fortress-web.
>> Problem #1:
>> I wanted to add two permissions using fortress-web, but it didn¹t work.
>> Permission 1:
>> - Object Name = https://galileo/blabla
>> - Operation Name = GET
>> - Roles = myreader
>> Permission 2:
>> - Object Name = https://galileo/blabla
>> - Operation Name = POST
>> - Roles = myreader
>>
>> I got two POST permissions instead.
>>
>
>Did you add https://galileo/blabla as object to the Perm Object Page
>first? Once you do that, you can use the object name as a reference in
>the permission page for your get and post. I tested to make sure and it
>worked fine on my machine.
>
>>
>> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar)
>><ol...@polystar.com> wrote:
>>
>> Problem #2:
>> Role¹s temporal constraints End Date 09/01/2111 is shown as 21110801 in
>>the role list/table.
>>
>> Problem #3:
>> Roles defined via fortress-web lose Begin Time in the table view after
>>modifying lock dates.
>>
>> Problem #4:
>> Modification of Begin Date (or Begin Time) leads to the month change in
>>Begin Lock and End Lock.
>>
>
>Good catches! I have made a couple of changes that should help. Can you
>do another git pull on your fortress-web and try again?
>
>Here¹s the issue we¹ve created:
>
>https://issues.apache.org/jira/browse/FC-98
>
>Thanks
>
>Shawn
>smckinney@apache.org
Re: small bugs in fortress-web
Posted by Shawn McKinney <sm...@apache.org>.
> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar) <ol...@polystar.com> wrote:
>
> I have 4 problems with fortress-web.
> Problem #1:
> I wanted to add two permissions using fortress-web, but it didn’t work.
> Permission 1:
> - Object Name = https://galileo/blabla
> - Operation Name = GET
> - Roles = myreader
> Permission 2:
> - Object Name = https://galileo/blabla
> - Operation Name = POST
> - Roles = myreader
>
> I got two POST permissions instead.
>
Did you add https://galileo/blabla as object to the Perm Object Page first? Once you do that, you can use the object name as a reference in the permission page for your get and post. I tested to make sure and it worked fine on my machine.
>
> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar) <ol...@polystar.com> wrote:
>
> Problem #2:
> Role’s temporal constraints End Date 09/01/2111 is shown as 21110801 in the role list/table.
>
> Problem #3:
> Roles defined via fortress-web lose Begin Time in the table view after modifying lock dates.
>
> Problem #4:
> Modification of Begin Date (or Begin Time) leads to the month change in Begin Lock and End Lock.
>
Good catches! I have made a couple of changes that should help. Can you do another git pull on your fortress-web and try again?
Here’s the issue we’ve created:
https://issues.apache.org/jira/browse/FC-98
Thanks
Shawn
smckinney@apache.org