You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/08/19 02:47:15 UTC

[jira] Created: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Release task assumes _1.3.4_ command-line argument convention works across platforms
------------------------------------------------------------------------------------

                 Key: BUILDR-303
                 URL: https://issues.apache.org/jira/browse/BUILDR-303
             Project: Buildr
          Issue Type: Bug
            Reporter: Alex Boisvert


Joel Muzzerall reported:

I am trying to run

buildr release

but it produces this error:

/usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
development clean upload DEBUG=no
(in *snip*, development)
Buildr aborted!
Don't know how to build task '_1.3.4_'


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert resolved BUILDR-303.
----------------------------------

       Resolution: Invalid
    Fix Version/s: 1.4.4

Closing issue.

Added some documentation about version selection under the install section.  (Website will be updated later)

boisvert@smudge:~/git/buildr$ git commit -m "More documentation about buildr version selection" .
[trunk efeabd4] More documentation about buildr version selection
 1 files changed, 9 insertions(+), 0 deletions(-)
boisvert@smudge:~/git/buildr$ git svn dcommit
Committing to https://svn.apache.org/repos/asf/buildr/trunk ...
	M	doc/installing.textile
Committed r1026946
	M	doc/installing.textile
r1026946 = 0ac784180fd32c1472981b8dd0aa6d73d5bab065 (refs/remotes/origin/trunk)


> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>             Fix For: 1.4.4
>
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924380#action_12924380 ] 

Gerolf Seitz commented on BUILDR-303:
-------------------------------------

Alex, thanks for the clarification. It was indeed an environment issue + layer 8 fail.
First, my /usr/bin/buildr was a softlink to the (outdated) buildr executable in /var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr.
Second, only after installing the buildr gem again with verbose output did I see that there's also a script at /var/lib/gems/1.8/bin/buildr. 
This script has all the magic wrt to the _1.4.3_ parameter.

Since I only use ruby and rubygems for buildr, I'm not very familiar with the gem environment and I only looked for the buildr script in the .../1.8/gems/buildr-xxx directory.
With the correct link in place, all is fine now.

Maybe it would be good to mention this on the website in the install section.

Thanks for the help and please feel free to close this issue again.

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884588#action_12884588 ] 

Antoine Toulme commented on BUILDR-303:
---------------------------------------

I think this is an environment issue. Most likely a buildr executable in the path before the gem executable.

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924277#action_12924277 ] 

Alex Boisvert commented on BUILDR-303:
--------------------------------------

Gerolf, just to clarify, there are normally 2 "buildr" executables installed via rubygems

1)  /usr/bin/buildr   (exact path location may vary)

This version dispatches to the version specified using the _1.4.3_ syntax, if specified, and contains the following code:

--- start ---
#!/usr/bin/ruby1.8
#
# This file was generated by RubyGems.
#
# The application 'buildr' is installed as part of a gem, and
# this file is here to facilitate running it.
#
require 'rubygems'

version = ">= 0"

if ARGV.first =~ /^_(.*)_$/ and Gem::Version.correct? $1 then
  version = $1
  ARGV.shift
end

gem 'buildr', version
load Gem.bin_path('buildr', 'buildr', version)
--- end ---

2) /usr/lib/ruby/gems/1.8/gems/buildr-1.4.3/bin/buildr

This file is the buildr bootstrap and is called by the preceeding one.

--- start ---
#!/usr/bin/env ruby
# Licensed to the Apache Software Foundation (ASF) under one or more
# ...

require 'rubygems'
require 'buildr'
Buildr.application.run
--- end ---

The first file should be on your PATH and should be the one run by buildr during the release.   The second one shouldn't be on the PATH and is usually called indirectly.

Also, you may want to make sure your RUBYPATH environment variable is empty (at is usually is).

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924218#action_12924218 ] 

Gerolf Seitz commented on BUILDR-303:
-------------------------------------

here's the log output with trace=all:


$ > buildr release --trace=all
(in /mnt/data/workspace/buildr_release_test, development)
** Invoke buildr.test (first_time)
** Execute buildr.test
Defining task buildr.test:shell:jirb
Defining task buildr.test:shell:clj
Defining task buildr.test:shell:bsh
** Invoke buildr.test 
** Invoke release (first_time)
** Execute release
/usr/bin/ruby1.8 -S buildr _1.4.3_ --buildfile /mnt/data/workspace/buildr_release_test/buildfile.rb.next --environment development clean upload DEBUG=no
(in /mnt/data/workspace/buildr_release_test, development)
Buildr aborted!
RuntimeError : Don't know how to build task '_1.4.3_'

(See full trace by running task with --trace)
rm /mnt/data/workspace/buildr_release_test/buildfile.rb.next
Buildr aborted!
RuntimeError : Command failed with status (1): [/usr/bin/ruby1.8 -S buildr _1.4.3_ --build...]
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/util.rb:503:in `sh'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/util.rb:533:in `call'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/util.rb:533:in `sh'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:686:in `sh'
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1027:in `ruby'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:686:in `ruby'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/build.rb:294:in `make'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/build.rb:356:in `with_release_candidate_version'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/build.rb:290:in `make'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/build.rb:510
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:634:in `call'
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:634:in `execute'
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:664:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:650:in `invoke_with_call_chain'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:645:in `invoke'
/var/lib/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:232:in `top_level'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:232:in `each'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:232:in `top_level'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:523:in `standard_exception_handling'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:223:in `top_level'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:138:in `run'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:523:in `standard_exception_handling'
/var/lib/gems/1.8/gems/buildr-1.4.3/lib/buildr/core/application.rb:135:in `run'
/usr/bin/buildr:19


> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924017#action_12924017 ] 

Gerolf Seitz edited comment on BUILDR-303 at 10/22/10 4:43 PM:
---------------------------------------------------------------

This happened to me too.
My setup is: 
Ubuntu 9.10
ruby 1.8
buildr 1.4.3

i removed all "buildr" executables from the path and specifically executed the buildr executable from the gem => same result.

As Alex mentioned on the mailing list [0], adding -V removes the symptom, but not the actual issue behind that.

[0] http://markmail.org/message/jck3oabsvobtzvfy

      was (Author: seitz):
    This happened to me too.
My setup is: 
Ubuntu 9.10
ruby 1.8
buildr 1.4.3

i removed all "buildr" executables from the path and specifically executed the buildr executable from the gem => same result.

As Alex mentioned on the mailing list (http://markmail.org/message/jck3oabsvobtzvfy), adding -V removes the symptom, but not the actual issue behind that.
  
> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924017#action_12924017 ] 

Gerolf Seitz commented on BUILDR-303:
-------------------------------------

This happened to me too.
My setup is: 
Ubuntu 9.10
ruby 1.8
buildr 1.4.3

i removed all "buildr" executables from the path and specifically executed the buildr executable from the gem => same result.

As Alex mentioned on the mailing list (http://markmail.org/message/jck3oabsvobtzvfy), adding -V removes the symptom, but not the actual issue behind that.

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924090#action_12924090 ] 

Alex Boisvert commented on BUILDR-303:
--------------------------------------

Gerolf, any chance you could provide a log of the output?   Can you try running with --trace=all ?

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert updated BUILDR-303:
---------------------------------

          Component/s: Core features
    Affects Version/s: 1.3.4

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Toulme resolved BUILDR-303.
-----------------------------------

    Resolution: Cannot Reproduce

Marked as cannot reproduce.

> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (BUILDR-303) Release task assumes _1.3.4_ command-line argument convention works across platforms

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert reopened BUILDR-303:
----------------------------------


> Release task assumes _1.3.4_ command-line argument convention works across platforms
> ------------------------------------------------------------------------------------
>
>                 Key: BUILDR-303
>                 URL: https://issues.apache.org/jira/browse/BUILDR-303
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.4
>            Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.