[jira] [Resolved] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera resolved JCLOUDS-1495. - Resolution: Fixed > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task > Components: jclouds-core >Affects Versions: 2.1.2 >Reporter: Olaf Flebbe >Priority: Major > Fix For: 2.2.0, 2.1.3 > > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 40m > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera updated JCLOUDS-1495: Component/s: jclouds-core > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task > Components: jclouds-core >Affects Versions: 2.1.2 >Reporter: Olaf Flebbe >Priority: Major > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 40m > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera updated JCLOUDS-1495: Fix Version/s: 2.1.3 2.2.0 > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task > Components: jclouds-core >Affects Versions: 2.1.2 >Reporter: Olaf Flebbe >Priority: Major > Fix For: 2.2.0, 2.1.3 > > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 40m > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera updated JCLOUDS-1495: Affects Version/s: 2.1.2 > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task >Affects Versions: 2.1.2 >Reporter: Olaf Flebbe >Priority: Major > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 40m > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815034#comment-16815034 ] ASF subversion and git services commented on JCLOUDS-1495: -- Commit af364d5b10ba1a7a52b54ca21d5776b42840f984 in jclouds's branch refs/heads/2.1.x from Olaf Flebbe [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=af364d5 ] JCLOUDS-1495: maven plugins are not correctly referred to (#24) > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task >Reporter: Olaf Flebbe >Priority: Major > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jclouds] nacx edited a comment on issue #24: JCLOUDS-1495: maven plugins are not correctly referred to
nacx edited a comment on issue #24: JCLOUDS-1495: maven plugins are not correctly referred to URL: https://github.com/apache/jclouds/pull/24#issuecomment-481945335 Thanks! Chery-picked to 2.1.x. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] nacx merged pull request #24: JCLOUDS-1495: maven plugins are not correctly referred to
nacx merged pull request #24: JCLOUDS-1495: maven plugins are not correctly referred to URL: https://github.com/apache/jclouds/pull/24 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815033#comment-16815033 ] ASF subversion and git services commented on JCLOUDS-1495: -- Commit 2fbf10c9c9940a8ba0865949b37f932bd0aa98aa in jclouds's branch refs/heads/master from Olaf Flebbe [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=2fbf10c ] JCLOUDS-1495: maven plugins are not correctly referred to (#24) > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task >Reporter: Olaf Flebbe >Priority: Major > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > Time Spent: 20m > Remaining Estimate: 0h > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jclouds] nacx commented on issue #24: JCLOUDS-1495: maven plugins are not correctly referred to
nacx commented on issue #24: JCLOUDS-1495: maven plugins are not correctly referred to URL: https://github.com/apache/jclouds/pull/24#issuecomment-481945335 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] oflebbe opened a new pull request #24: JCLOUDS-1495: maven plugins are not correctly referred to
oflebbe opened a new pull request #24: JCLOUDS-1495: maven plugins are not correctly referred to URL: https://github.com/apache/jclouds/pull/24 Some maven plugins are not properly addressed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (JCLOUDS-1495) maven plugins are not correctly referred to
[ https://issues.apache.org/jira/browse/JCLOUDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olaf Flebbe updated JCLOUDS-1495: - Attachment: 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > maven plugins are not correctly referred to > --- > > Key: JCLOUDS-1495 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 > Project: jclouds > Issue Type: Task >Reporter: Olaf Flebbe >Priority: Major > Attachments: > 0001-JCLOUDS-1495-maven-plugins-are-not-correctly-referre.patch > > > While trying to upgrade maven plugins to a current level, some of my attempts > didn't work because the tag for some maven standard plugins are > missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JCLOUDS-1495) maven plugins are not correctly referred to
Olaf Flebbe created JCLOUDS-1495: Summary: maven plugins are not correctly referred to Key: JCLOUDS-1495 URL: https://issues.apache.org/jira/browse/JCLOUDS-1495 Project: jclouds Issue Type: Task Reporter: Olaf Flebbe While trying to upgrade maven plugins to a current level, some of my attempts didn't work because the tag for some maven standard plugins are missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jclouds] ak58588 commented on issue #23: draft - disable AccessPolicy check for SAS Authorised azureblob
ak58588 commented on issue #23: draft - disable AccessPolicy check for SAS Authorised azureblob URL: https://github.com/apache/jclouds/pull/23#issuecomment-481790176 the `catch (CacheLoader.InvalidCacheLoadException e)` can't catch the `CacheLoader.InvalidCacheLoadException`, but catches `com.google.common.util.concurrent.UncheckedExecutionException`. getUnchecked method throws it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] nacx commented on issue #23: draft - disable AccessPolicy check for SAS Authorised azureblob
nacx commented on issue #23: draft - disable AccessPolicy check for SAS Authorised azureblob URL: https://github.com/apache/jclouds/pull/23#issuecomment-481778347 I think it probably makes more sense here to have a custom exception such as `InsufficientAccessRightsException` or something like that that properly designates the error to handle instead of a generic loading exception? /cc @gaul This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] danielestevez edited a comment on issue #21: Adds methods listAll and listByLocation to VirtualMachineAPI
danielestevez edited a comment on issue #21: Adds methods listAll and listByLocation to VirtualMachineAPI URL: https://github.com/apache/jclouds/pull/21#issuecomment-481736540 Just a quick update on the state of this PR: The changes to the adapter were minor but i found one of those nasty ARM API behaviour with case-sensitivity. In short, these new methods return the resourcegroup part of the resource id in capital letters randomly and this causes some of the LiveTests to fail, so it's not safe to add them to the adapter yet The goal to make all the provider case-insensitive (as Microsoft [recommends](https://stackoverflow.com/a/50082864/2369157) in integrations) is too wide for this PR but i found a way to fix this problem just for the resourcegroups. Running all the LiveTests with this fix i only found a problem still in `AzureComputeServiceLiveTest#testListNodesByIds` that i will try to fix too This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] danielestevez commented on issue #21: Adds methods listAll and listByLocation to VirtualMachineAPI
danielestevez commented on issue #21: Adds methods listAll and listByLocation to VirtualMachineAPI URL: https://github.com/apache/jclouds/pull/21#issuecomment-481736540 Just a quick update on the state of this PR: The changes to the adapter were minor but i found one of those nasty ARM API behaviour with case-sensitivity. In short, these new methods return the resourcegroup part of the resource id in capital letters in randomly and this causes some of the LiveTests to fail, so it's not safe to add them to the adapter yet The goal to make all the provider case-insensitive (as Microsoft [recommends](https://stackoverflow.com/a/50082864/2369157) in integrations) is too wide for this PR but i found a way to fix this problem just for the resourcegroups. Running all the LiveTests with this fix i only found a problem still in `AzureComputeServiceLiveTest#testListNodesByIds` that i will try to fix too This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jclouds] ak58588 opened a new pull request #23: draft - disable AccessPolicy check for SAS Authorised azureblob
ak58588 opened a new pull request #23: draft - disable AccessPolicy check for SAS Authorised azureblob URL: https://github.com/apache/jclouds/pull/23 This is a draft. I have a problem with it: even though I am throwing a `CacheLoader.InvalidCacheLoadException` exception in `containerAcls` method in `AzureBlobStoreContextModule.java`, I still can't catch it in the try-catch close in `BlobPropertiesToBlobMetadata.java` with `catch (CacheLoader.InvalidCacheLoadException e)`. Nevertheless, I can catch this` CacheLoader.InvalidCacheLoadException` when I do `catch (Exception e)`. Do you have any idea of the reason why this is happening and how to omit catching unspecified Exception? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
