Skip to content
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

Fixes to build_release.sh script #607

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mrflip
Copy link
Collaborator

@mrflip mrflip commented Jun 25, 2013

  • maven is putting the storm-* jar files in target/release+provided, not target/provided. Fixed path.
  • storm-netty had a dependency itself on storm-core, so the storm-core jar was in both _release and _release/lib. Removing the dupe jar from lib/
  • storm-console-processor was letting clojure-1.2 meet its dependency list, making for two clojure jars in the tarball. Added a dependency to its project.clj.
  • build_releases.sh should fail if the build_modules.sh script fails. Made build_modules.sh run with set -e, and made build_releases.sh fail if it does
  • made pretty banners, made paths be properly quoted
  • bin/ directory files copy with permissions intact. Also now remove build_release.sh and build_modules.sh, since they won't work
  • rather than remove _release and *.zip, only removes the specific subdirectory and .zip file. If you run with STORM_KEEP_RELEASE=true, it will not delete the release dir at the end of script (only at beginning)

@mrflip
Copy link
Collaborator Author

mrflip commented Jun 27, 2013

Just saw this overlaps with #597 -- let me know if I should rebase. (This patch implements the same functionality)

cd ..
cd $module
mvn dependency:copy-dependencies || exit 1
cp -f target/release/dependency/*.jar "$DIR/lib/"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me these dirs don't exist, I just have target/dependency.

@nathanmarz
Copy link
Owner

I tried running this and it doesn't work on my computer. No jars are copied to the release distribution.

@mrflip
Copy link
Collaborator Author

mrflip commented Jul 10, 2013

Gah sounds like I'm gonna have to read some maven documentation. I'll update the pull request once I know why we get different destinations.

On Jul 9, 2013, at 1:03 PM, Nathan Marz [email protected] wrote:

I tried running this and it doesn't work on my computer. No jars are copied to the release distribution.


Reply to this email directly or view it on GitHub.

@mrflip
Copy link
Collaborator Author

mrflip commented Jul 13, 2013

Looks like technomancy/leiningen@a1d7b6f3eabe4eb made it append the profile name to the target directory -- if you installed lein before May, you got a pom with <directory>target</directory>; with recent lein, <directory>target/release</directory>.

I made the project.clj file fix the directory as just plain target, and rebased on top of current master.

Philip (flip) Kromer added 2 commits July 20, 2013 23:06
* storm-console-processor was letting clojure-1.2 meet its dependency list, making for two clojure jars in the tarball. Added a dependency to its project.clj
* storm-netty had a dependency itself on storm-core, so the storm-core jar was in both _release and _release/lib. removing the dupe jar from lib/
* build_releases should fail if the build_modules script fails. Made build_modules run set -e, and made build_releases fail if it does
* maven is putting the storm-* jar files in target/release+provided, not target/provided. Fixed path.
* made pretty banners, made paths be properly quoted
* bin/ directory files copy with permissions intact. Also now remove build_release.sh and build_modules.sh, since they won't work
* rather than remove _release and *.zip, only removes the specific subdirectory and .zip file. If you run with STORM_KEEP_RELEASE=true, it will not delete the release dir at the end of script (only at beginning)
* bin/storm tells you how to roll your own release if you try to launch from a git checkout
Recent leiningen (technomancy/leiningen@a1d7b6f3eabe4eb) appends the profile name to the target directory -- if you installed lein before may, you got a pom with build dir = target/; recent leins set it to target/{profile_name}. This expressly fixes it to be just plain 'target'.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants