You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by abhishekagarwal87 <gi...@git.apache.org> on 2016/03/17 15:34:05 UTC
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
GitHub user abhishekagarwal87 opened a pull request:
https://github.com/apache/storm/pull/1231
STORM-1637: Correct the master version of storm in storm-mongodb module
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/abhishekagarwal87/storm patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1231.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1231
----
commit 4fe225cd07b6905f7024969751271425059316d6
Author: abhishekagarwal87 <ab...@gmail.com>
Date: 2016-03-17T14:33:50Z
STORM-1637: Correct the master version of storm in storm-mongodb module
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by revans2 <gi...@git.apache.org>.
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-197933343
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by HeartSaVioR <gi...@git.apache.org>.
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-198409022
The difference is...
* https://travis-ci.org/apache/storm/jobs/116573241 (oraclejdk7, `!storm-core`)
```
[INFO] Scanning for projects...
[INFO] Downloading: https://repository.apache.org/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/maven-metadata.xml
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
...
```
No error to download metadata of Storm 2.0.0 SNAPSHOT from repository.apache.org.
*This is the strange point.*
* https://travis-ci.org/apache/storm/jobs/116573242 (oraclejdk8, `!storm-core`)
```
[INFO] Scanning for projects...
[INFO] Downloading: https://repository.apache.org/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloading: https://nexus.codehaus.org/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.storm:storm:2.0.0-SNAPSHOT/maven-metadata.xml from/to codehaus-snapshots (https://nexus.codehaus.org/snapshots/): nexus.codehaus.org: unknown error
[INFO] Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/storm-2.0.0-SNAPSHOT.pom
[INFO] Downloading: https://repository.apache.org/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/storm-2.0.0-SNAPSHOT.pom
[INFO] Downloading: https://nexus.codehaus.org/snapshots/org/apache/storm/storm/2.0.0-SNAPSHOT/storm-2.0.0-SNAPSHOT.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.apache.storm:storm-mongodb:[unknown-version] (/home/travis/build/apache/storm/external/storm-mongodb/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not transfer artifact org.apache.storm:storm:pom:2.0.0-SNAPSHOT from/to codehaus-snapshots (https://nexus.codehaus.org/snapshots/): nexus.codehaus.org and 'parent.relativePath' points at wrong local POM @ line 21, column 13: Unknown host nexus.codehaus.org -> [Help 2]
```
It can't find the metadata from repository.apache.org so go on finding alternative repositories.
And stuck on nexus.codehaus.org, because all codehaus services have now been terminated and maven too.
Please refer https://www.codehaus.org/
I don't have an idea why it searches nexus.codehaus.org, but anyway that's the point why build failed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by HeartSaVioR <gi...@git.apache.org>.
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-198368607
Not wanted to take another action, but just leaving a note: according to BYLAWS, change of pom.xml belongs source code change, so we should wait 1 day for initial patch. That's why I didn't merge #1228 after receiving +1 from dossett.
If we want to make exception cases like hotfix (this seems to go to hotfix), I'd love to discuss and reflect to BYLAWS.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by abhishekagarwal87 <gi...@git.apache.org>.
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-197963621
Actually @revans2 had already created a JIRA for this. @HeartSaVioR has a PR open for the same bug I think. So this JIRA can be resolved as duplicate.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1231
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by harshach <gi...@git.apache.org>.
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-197961516
+1. @abhishekagarwal87 Thanks for the patch. For small fixes like this lets not file a jira
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by abhishekagarwal87 <gi...@git.apache.org>.
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-197915314
This build error is definitely unrelated (intermittent failure in storm-kafka)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by vesense <gi...@git.apache.org>.
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-198389354
BTW, I think @revans2 's main concern is **why JDK7 builds pass while JDK8 builds fail with** in JIRA [STORM-1637](https://issues.apache.org/jira/browse/STORM-1637).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] storm pull request: STORM-1637: Correct the master version of stor...
Posted by abhishekagarwal87 <gi...@git.apache.org>.
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1231#issuecomment-198401568
Yes. It is weird. I am taking a look at it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---