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 2010/09/18 20:46:33 UTC

[jira] Updated: (BUILDR-493) Eclipse task should generate javadocpath

     [ https://issues.apache.org/jira/browse/BUILDR-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert updated BUILDR-493:
---------------------------------

          Summary: Eclipse task should generate javadocpath  (was: Eclipse task does not generate javadocpath)
       Issue Type: New Feature  (was: Wish)
    Fix Version/s: 1.4.2

> Eclipse task should generate javadocpath
> ----------------------------------------
>
>                 Key: BUILDR-493
>                 URL: https://issues.apache.org/jira/browse/BUILDR-493
>             Project: Buildr
>          Issue Type: New Feature
>          Components: IDE
>    Affects Versions: 1.4.1
>         Environment: Buildr 1.4.1 (JRuby 1.5.1)
> java version "1.6.0_18" openjdk
> Ubuntu 10.04
>            Reporter: Nikos Maris
>             Fix For: 1.4.2
>
>         Attachments: buildfile, ivy.xml, ivysettings.xml
>
>
> When: jruby -S buildr package eclipse
> directory structure{
> src/HelloWorld.java
> buildfile
> ivy.xml
> ant-scripts/ivysettings.xml
> }
> Then: Some lines in the generated classpath are:
> <classpathentry kind="lib" path="ivy-home/cache/org.jbehave/jbehave-core/jars/jbehave-core-2.5.9.jar"/>
> <classpathentry kind="lib" path="ivy-home/cache/org.jbehave/jbehave-core/javadocs/jbehave-core-2.5.9-javadoc.jar"/>
> Expected:
> <classpathentry kind="lib" path="ivy-home/cache/org.jbehave/jbehave-core/javadocs/jbehave-core-2.5.9.jar" javadocpath="ivy-home/cache/org.jbehave/jbehave-core/javadocs/jbehave-core-2.5.9-javadoc.jar"/>
> Is there any ruby workaround?

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