You can't do exactly what you are aiming to do dynamically but you could
hard code that structure into your pom's.
Look into the property;
project.build.directory
If you defined that in the respective pom's as below;
project.build.directory=/tmp/grandfarther/target
Hi,
grandfather
|
| pom.xml
|
| father
|
| pom.xml
|
| son
|
| pom.xml
If I build that project, I will have these target directories:
Thanks, John, for answering my question. There's no special reason, I have the
project on a SSD drive and don't want to write to that so often.
On Friday, May 30, 2014 5:28 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
grandfather
|
| pom.xml
|
So I'm guessing you then have mapped tmp to a ram drive, otherwise tmp will
still be on your SSD unless you also have a non-SSD too which is mapped to
tmp.
Honestly as long as it's a new ish SSD, your not writing GB and GB per hour
constantly 24/7, your SSD is under about 60% full then I would
Hi,
This has probably been answered before, but I haven't been able to find the
answer and I'm hoping someone knows.
I'm writing several apps that talk to a Microsoft SQL database, so I'm using
the Hibernate dependency. Since Microsoft doesn't make the sqljdbc4 jar
available on Maven, I've
Hi Matt,
Have you seen this article?
http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html
If you cannot deploy the Microsoft JARs to your own internal Maven
repository, then you could try the non-maven-jar-plugin approach. It is
strongly recommended over the basedir
I don't think you should make a project for your sql jar. My guess is when
you build+install that, you're creating an empty and useless jar file and
overwriting the good one you already placed in your local repo. The
mvn:install:install-file thing works and is what I would expect as the
answer.
Hi Curtis,
I'll take a look at that, thanks! Ideally, I'll eventually be able to have an
internal Maven repository
so that I can do everything right. What I had been trying to do in the meantime
is having it set up
so that when we set up a new development station, the user can simply clone the
I understand but you can't achieve this using a project to represent a
pre-existing jar. Your attempt won't work. The install-file command is
the correct solution; that is how you get it into your local repo without
downloading it from a remote repo.
On May 30, 2014 4:36 PM, Matt Whiteman
