buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikos Maris (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BUILDR-493) Eclipse task does not generate javadocpath
Date Fri, 27 Aug 2010 13:36:56 GMT

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

Nikos Maris updated BUILDR-493:
-------------------------------

    Issue Type: Wish  (was: Bug)

I wish javadocpath was supported. Maven and m2eclipse are superior at this point.

> Eclipse task does not generate javadocpath
> ------------------------------------------
>
>                 Key: BUILDR-493
>                 URL: https://issues.apache.org/jira/browse/BUILDR-493
>             Project: Buildr
>          Issue Type: Wish
>          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
>         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.


Mime
View raw message