[
https://issues.apache.org/jira/browse/BUILDR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783467#comment-13783467
]
Tammo van Lessen commented on BUILDR-394:
-----------------------------------------
The following patch works for me, but I'm not sure about the implications on
other setups:
{code}
diff --git a/lib/buildr/core/build.rb b/lib/buildr/core/build.rb
index 8a4b097..6d03ced 100644
--- a/lib/buildr/core/build.rb
+++ b/lib/buildr/core/build.rb
@@ -331,10 +331,10 @@ module Buildr #:nodoc:
@this_version = extract_version
check
with_release_candidate_version do |release_candidate_buildfile|
- args = '-S', 'buildr', "_#{Buildr::VERSION}_", '--buildfile',
release_c+ args = 'buildr', "_#{Buildr::VERSION}_", '--buildfile',
release_candida args << '--environment' << Buildr.environment unless
Buildr.environment args << 'clean' << 'upload' << 'DEBUG=no'
- ruby *args
+ sh *args
end
tag_release resolve_tag
update_version_to_next if this_version !=
resolve_next_version(this_versi(E
{code}
> Release task fails with standalone distribution
> -----------------------------------------------
>
> Key: BUILDR-394
> URL: https://issues.apache.org/jira/browse/BUILDR-394
> Project: Buildr
> Issue Type: Bug
> Components: JRuby
> Reporter: Antoine Toulme
> Fix For: 1.5
>
>
> The release task fails with the current trunk, trying to do a release by
> calling jruby:
> /home/release/tools/buildr-1.4.0-jruby-1.4.0/bin/jruby -S buildr _1.4.0_
> --buildfile
> /home/release/tools/hudson/config/jobs/Process_Designer_Release_Build/workspace/oryx/Buildfile.next
> --environment development clean upload DEBUG=no
> :1: /home/release/tools/buildr-1.4.0-jruby-1.4.0/bin/buildr:17: , unexpected
> kIN (SyntaxError)
> case "`uname`" in
> ^
> I think we can bypass jruby -S since we have a buildr executable now.
--
This message was sent by Atlassian JIRA
(v6.1#6144)