[
https://issues.apache.org/jira/browse/BUILDR-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420132#comment-15420132
]
Antoine Toulme commented on BUILDR-604:
---------------------------------------
A possible rather elegant workaround:
{code}
define 'problematic', :version => '1.0.0', 'group' => "com.foo" do
define 'foo' do
package :war
package :jar # Add a jar packaging, that will be picked up.
end
define 'bar' do
compile.with project('foo')
p compile.dependencies.map(&:to_s)
end
end
{code}
> Eclipse task generates incorrect classpath entries
> --------------------------------------------------
>
> Key: BUILDR-604
> URL: https://issues.apache.org/jira/browse/BUILDR-604
> Project: Buildr
> Issue Type: Bug
> Components: IDE
> Affects Versions: 1.4.6
> Reporter: Matteo Vaccari
> Assignee: Antoine Toulme
> Fix For: 1.5
>
>
> In the setup that follows,
> define 'problematic', :version => '0.0' do
> define 'foo' do
> package :war
> end
>
> define 'bar' do
> compile.with project('foo').compile.target,
> project('foo').test.compile.target
> end
> end
> the eclipse task generates incorrect .classpath entries for project bar
> <classpath>
> <classpathentry
> path="/Users/matteo/work/.../problematic/foo/target/classes" kind="src"
> excluding="**/.svn/|**/CVS/"/>
> <classpathentry
> path="/Users/matteo/work/.../problematic/foo/target/test/classes" kind="src"
> excluding="**/.svn/|**/CVS/"/>
> ...
> </classpath>
> The absolute paths are not recognized by Eclipse, that interprets the
> /Users... paths as it they were relative to the workspace.
> There is a workaround with eclipse.exclude_lib that I documented here:
> https://cwiki.apache.org/confluence/display/BUILDR/How+to+depend+on+a+war-packaged+project
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
