Skip to content

Commit

Permalink
update instructions for minimal install
Browse files Browse the repository at this point in the history
  • Loading branch information
@dancingfrog
dancingfrog committed Dec 6, 2016
1 parent 9512db5 commit 4f78b14
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions INSTALL.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,15 @@ The [Vertx From Zero To (Micro)Hero](http://escoffier.me/vertx-hol/#_let_s_start
If you would like to avoid packaging and installing incomplete versions of these modules on your system, it's possible to only install the common classes in `vertx-workshop-common` and the parent project's pom file, so that you are able to build each of the other modules one-by-one as you complete the relevant code sections (which the tutorial systematically guides you through).

After cd'ing into `vertx-workshop-common` and running `mvn clean install`, these files are installed in the local user's Maven repository:

`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/_remote.repositories`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/maven-metadata-local.xml`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT.jar`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT.pom`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT-sources.jar`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT-tests.jar`
`.../.m2/repository/io/vertx/workshop/vertx-workshop-common/maven-metadata-local.xml`
```
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/_remote.repositories
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/maven-metadata-local.xml
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT.jar
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT.pom
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT-sources.jar
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/1.0-SNAPSHOT/vertx-workshop-common-1.0-SNAPSHOT-tests.jar
.../.m2/repository/io/vertx/workshop/vertx-workshop-common/maven-metadata-local.xml
```

Create a new directory in the Maven repository:

Expand Down

1 comment on commit 4f78b14

@atfreddos
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This lab appears to be a very good thing, however, and this is a big pain-in-the-a., the use of Maven for a multi-module project for this kind of lab is absurd overkill. Simply not necessary. Moreover multi-module use of Maven means the student/novice needs to be expert in Maven to get it to work, which is unlikely. The kind of absurd hack suggested above by a user (not by the authors!) is insane. Seriously, we need to hack the local Maven repository?! And the author's don't see the absurdity of this! This is the first time I have heard of such a thing in twenty years! And it doesn't work anyway, not on my setup. Either the author's add some detailed and extensive tutorial material on how to work with Maven in this lab, or else do without. Pity, since the lab itself seems to be a very good thing. But the project management Maven smart-arsery is shite.

Please sign in to comment.