-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package extensions in tarball + run_druid_server goodness #1640
Conversation
a2057d8
to
caa7558
Compare
👍 |
1 similar comment
👍 |
hmmm... when run locally : |
- move assembly out of druid-services into a 'distribution' module - create separate 'extensions-distribution' module and assembly to package extensions and their dependencies into a local maven repository - include this extensions maven repository in the binaries tarball
- Use local repo in run_example_server. - Add extensions-repo to common.runtime.properties for the tarball.
caa7558
to
5ca440f
Compare
@drcrallen ah that was just an artifact of us working on the 0.8.1-rc branch. Fixed the pom versions and everything should be happy again. |
Extends build time by 30s on my local box. Seems to work well, and the packaging mechanism is some crazy maven-foo.
Looks good to me 👍 (waiting for Travis) |
LGTM |
Package extensions in tarball + run_druid_server goodness
Is
|
Expected? no |
@guobingkun make sure to |
@xvrl Yeah, It happened on a clean state build machine.
|
@guobingkun it looks like your |
@xvrl #1644 fixes the problem I had when I ran
|
@guobingkun what version of maven are you running? |
|
@guobingkun can you try a more recent version of maven, e.g. 3.3.3? |
@xvrl I tried |
@guobingkun it looks like you might be running into https://issues.apache.org/jira/browse/MASSEMBLY-677 |
@xvrl that would be a problem. we have corp level maven mirror that contains public maven + internal stuff. All the machines get a [internally certified]wrapped version of maven that uses those mirrors. It is not possible to change things inside settings.xml in most cases and this will continue to fail build for us. |
@himanshug @guobingkun I can try disabling embedding the maven metadata into the local maven repo and see if that still works. If not, I suggest we make the tarball assembly optional as part of a separate release profile that we can activate when needed to make the release. Would that work? |
@xvrl if it works by disabling the maven metadata, good or else making it optional sounds good to me as most people dont need to build that. |
@himanshug @guobingkun can you try with this fix #1650 ? |
#1650 fixed the issue, merged. |
No description provided.