buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BUILDR-84) IDE Meta Generation Should Not Require Sources
Date Sun, 28 Feb 2010 15:45:05 GMT

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

Alex Boisvert updated BUILDR-84:
--------------------------------

    Fix Version/s: Wish List

> IDE Meta Generation Should Not Require Sources
> ----------------------------------------------
>
>                 Key: BUILDR-84
>                 URL: https://issues.apache.org/jira/browse/BUILDR-84
>             Project: Buildr
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: 1.3.2
>         Environment: eclipse
>            Reporter: Daniel Spiewak
>             Fix For: Wish List
>
>
> The `eclipse` task (and I assume `idea` as well) requires at least one source file of
the relevant type to be found within a source directory.  For example, for project meta generation
to succeed, the src/main/java/ directory (and/or subdirectories) must contain at least one
.java file.  The same holds for scala.  If these source files are not specified, the task
silently fails and just doesn't generate any project meta.
> It seems to me that this would be a fairly common use-case: using Buildr to setup a project
prior to creating any sources and then doing the actual coding within an IDE.  I would propose
that the source autodetection be fixed to just assume that there will be source files within
the relevant source dirs if they exist.  At the very least, a warning should be printed regarding
the absence of sources and that this prevents IDE meta gen.

-- 
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