[
https://issues.apache.org/jira/browse/STORM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366651#comment-14366651
]
P. Taylor Goetz commented on STORM-706:
---------------------------------------
I think we can handle this better through both documentation and possibly a
change to the build.
It's not pretty, but it can help prevent mistakes. I don't like the idea of
commenting/uncommenting a line in the main {{pom.xml}} file.
One option is to define a `provided.scope` (naming is irrelevant) variable, and
then set it based on a Maven profile.
(In IntelliJ, you would enable the "intellij" profile.):
{code}
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- see comment below... This fixes an annoyance with intellij -->
<provided.scope>provided</provided.scope>
</properties>
<profiles>
<!--
Hack to make intellij behave.
If you use intellij, enable this profile in your IDE.
It should make life easier.
-->
<profile>
<id>intellij</id>
<properties>
<provided.scope>compile</provided.scope>
</properties>
</profile>
</profiles>
{code}
In subsequent dependency elements, you would define the scope like so:
{code}
<scope>${provided.scope}</scope>
{code}
But I agree, this is an annoyance when using IntelliJ.
> Clarify IntelliJ instructions for example running.
> --------------------------------------------------
>
> Key: STORM-706
> URL: https://issues.apache.org/jira/browse/STORM-706
> Project: Apache Storm
> Issue Type: Bug
> Reporter: jay vyas
>
> Since the defaults for the examples topology assume maven scope is provided,
> you have to comment out the "provided" part in order to load the classes and
> run them via any IDE.
> This should be clarified in the README.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
