Re: [jbosstools-dev] Funkyness with .target using google adt site
On Wed, Mar 27, 2013 at 11:21:01PM -0400, Nick Boldt wrote:
On 03/27/2013 09:08 PM, Max Andersen wrote:
>Were you able to run mvn install on my repo without any errors ?
Yes - which is why I said I could not reproduce your error.
very weird.
>Why does one have to do All these steps when adding just a
dependency for testing? Seems like massive overkill.
>What does fix version do that isn't already present when I've specified the
exact versions ?
To verify that the sites listed are still current with respect to the
list of IUs. Maybe something has changed. Maybe the list of IUs you
added have new versions. Rather than having to look at all the URLs by
hand, you can simply run the version update step, wait a few seconds,
and be sure that it's all current and up to date.
Thats fine but this is not something that should be run blindly since you might
inadvertenly update
dependency versions you did not expect.
"Massive overkill" only takes a few seconds. But if you know
for sure
that the list of URLs and IUs in your target file are current and up
to date, then yes, it's an unnecessary step. You would therefore need
only steps 2 and 3:
pushd jbosstools/multiple && mvn clean install && popd
pushd jbosstools/unified && mvn install
-DtargetRepositoryUrl=file://path/to/jbosstools/multiple/target/jbosstools-multiple.target.repo/
&& popd
why not just:
$ cd jbosstools
$ mvn install
-DtargetRepositoryUrl=file://path/to/jbosstools/multiple/target/jbosstools-multiple.target.repo/
That should produce the same should it not ?
/max