Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Commit

Permalink
Merge pull request #207 from vrockai/HAWKULAR-334
Browse files Browse the repository at this point in the history
HAWKULAR-334: Refactored the link profile
  • Loading branch information
mtho11 committed Jun 12, 2015
2 parents 4e3a0dc + 0c8f539 commit 9ff9411
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 15 deletions.
24 changes: 10 additions & 14 deletions ui/README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -46,22 +46,18 @@ The advantage of this approach is, that is scans for file changes in the source
into the target directory (`$HAWKULAR_ROOT/dist/target/hawkular-x.y.x-SNAPSHOT/wildfly-x.y.z.Final/`), which is suitable for console
developing since it doesn't require the whole maven build to see the actual changes in the console UI.

If you want to use your local version of hawkular-ui-components, you can use the `link` profile and the
https://oncletom.io/2013/live-development-bower-component/[bower link functionality]. In the hawkular-ui-components,
link your bower package with:

`bower link`

and then build Hawkular with:
== Other packages development

`mvn clean install -Plink`
If you want to use a local version of a bower component, you can use the `link` profile together with the
https://oncletom.io/2013/live-development-bower-component/[bower link functionality]. In your bower component,
link the bower package with:

== Other packages development
`bower link`

The `link` profile links the hawkular-ui-components as a default package to link. But you can use it for any other package
as well. Just set the `bower.link.package` parameter, i.e.:
and then build Hawkular with the `bower.link.package` property pointing to the package name, i.e.:

`mvn clean install -Pdev,link -Dbower.link.package=hawkular-charts`
`mvn clean install -Pdev -Dbower.link.package=hawkular-charts`

Please, be aware, that you can combine the `link` profile with other profiles, like the `dev` profile. Don't forget to
run `bower link` in the package you're about to link before running maven `link` profile.
You don't have to specify the link profile itself with the `-P`, since it's activated everytime the `bower.link.package`
property is passed to the build. Please, be aware, that you can combine the `link` profile with other profiles, like the
`dev` profile. Don't forget to run `bower link` in the package you're about to link before using the maven `link` profile.
8 changes: 7 additions & 1 deletion ui/console/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
<hawkular.console.timestamp>${maven.build.timestamp}</hawkular.console.timestamp>
<hawkular.console.context>/</hawkular.console.context>
<hawkular.console.index.html.base.href>/</hawkular.console.index.html.base.href>
<bower.link.package>hawkular-ui-components</bower.link.package>
<bower.link.package></bower.link.package>
<node.version>v0.10.33</node.version>
<node.npm.version>2.1.10</node.npm.version>
<node.maven.plugin.version>0.0.23</node.maven.plugin.version>
Expand Down Expand Up @@ -225,6 +225,12 @@

<profile>
<id>link</id>
<activation>
<property>
<name>bower.link.package</name>
<value></value>
</property>
</activation>
<properties>
<hawkular.console.context>/</hawkular.console.context>
<hawkular.console.index.html.base.href>/</hawkular.console.index.html.base.href>
Expand Down

0 comments on commit 9ff9411

Please sign in to comment.