[
https://issues.apache.org/jira/browse/BUILDR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586431#action_12586431
]
Victor Hugo Borja commented on BUILDR-59:
-----------------------------------------
IIRC the original EarTask patch actually created internal copies of its
components. Anyway I've solved this as proposed by Assaf. Now the EarTask
creates internal tasks to copy its non-lib components so that modifying their
manifest has no side effect on the original artifact being clonned.
Thank you Tomas & Assaf for helping with your comments on this.
> EarTask: component type cannot be specified for Artifact
> --------------------------------------------------------
>
> Key: BUILDR-59
> URL: https://issues.apache.org/jira/browse/BUILDR-59
> Project: Buildr
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 1.3
> Environment: Windows XP SP2, JRuby 1.1, buildr trunk (rev 645177)
> Reporter: Tomas Carlsson
> Assignee: Victor Hugo Borja
> Priority: Minor
>
> Trying to specify component type for Artifact when packaging ear:s fails with:
> undefined method `manifest' for #<Buildr::Artifact:0x1202d8a>
> Example buildfile:
> repositories.remote << "http://repo1.maven.org/maven2";
> define 'myproj' do
> project.version=1
> project.group = "foo"
> define 'this_works' do
> package(:ear).add "log4j:log4j:jar:1.2.14"
> end
> define 'does_not_work' do
> package(:ear).add :ejb => "log4j:log4j:jar:1.2.14"
> end
> end
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
