[
https://issues.apache.org/jira/browse/BUILDR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586133#action_12586133
]
Tomas Carlsson commented on BUILDR-59:
--------------------------------------
Ok, I see your point. Although I don't completely agree.
The use case I'm working with is that I need to include ejb components
developed by other projects but still within our company; these components are
available through an internal m2 repository.
I guess that what I'd really want is to be able to include them as ejb
components but without modifying them. Since there are quite a few of them I'd
like to avoid cloning them all.
And by the way, the following is in the doc for EarTask (in packaging.rb):
# # will add an ejb entry for the-cool-ejb-2.5.jar in application.xml
# package(:ear).add 'org.coolguys:the-cool-ejb:jar:2.5', :type=>:ejb
# # A better syntax for this is:
# package(:ear).add :ejb=>'org.coolguys:the-cool-ejb:jar:2.5'
:-)
I think it would be perfectly reasonable to include external artifacts as ejbs
in the above way; but without modifying the manifest.
> 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.
