On 30 Jul 2009, at 20:19, jvsrvcs wrote:
We do have a maven repository manager in place but it's only
accessible
inside the network when we
are on location.
It's trivial to get nexus running on your workstation. I keep one
running on my laptop for when I'm not plugged in to our company
The docs on the mvn install plugin state:
mvn install:install-file -Dfile=your-artifact-1.0.jar \
[-DpomFile=your-pom.xml] \
[-Dsources=src.jar] \
[-Djavadoc=apidocs.jar] \
It's no different than any other plugin. Something like this should
work:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
executions
execution
There is no need to bind it to any phase, right? [?] I think it is a pretty
Maven-style way of solving problem [?] Needa try..
2009/7/30 Edelson, Justin justin.edel...@mtvstaff.com
It's no different than any other plugin. Something like this should
work:
plugin
It does need to be bound to a phase if you want to do more than one
install. Also, the OP said he wanted to use a profile, which implied (to
me at least) that this would be part of the lifecycle. generate-sources
may or may not be the right phase, that's up to the OP.
Justin
I should also say that I personally think using install-file is a bad
idea when there are good repository managers available.
Justin
-Original Message-
From: Edelson, Justin
Sent: Thursday, July 30, 2009 1:13 PM
To: Maven Users List
Subject: RE: How to use mvn install but have all
But I cant find the way how install several files. It seems like
maven-install could be configured only with one file to install. Actually It
wont eat configuration in execution node as you mentioned. Works only that
way
plugin
groupIdorg.apache.maven.plugins/groupId
You should *not* use install plugin manually, but rather let Maven know that
your project is producing multiple artifacts, use classifiers to identify
each and attach them to the module with build-helper plugin.. see example
at: http://mojo.codehaus.org/build-helper-maven-plugin/usage.html.
Kalle
You can define multiple executions.
My advice is the same as Justin's, don't do this. Use a repository
manager.The fact that you have to configure multiple calls to
install-file means that you don't have a good way to distribute internal or
third-party artifacts.
On Thu, Jul 30, 2009 at
Thanks, the reason we are doing this is because:
1. We have a lot of new programmers coming on board (10) that need to
quickly setup their local repo
2. Many of these programmers/consultants are bash handicapped and don't
have cygwin installed
3. Doing it locally first is better than getting
On Thu, Jul 30, 2009 at 1:23 PM, jvsrvcsjvsr...@gmail.com wrote:
Thanks, the reason we are doing this is because:
1. We have a lot of new programmers coming on board (10) that need to
quickly setup their local repo
Use a repository manager. Distribute a settings.xml file.
2. Many of
Any project should have the ability to:
1. check out the code
2. Build it without a repository manager
Repository managers are a necessity but they are being used for things they
were not intended for.
We have the requirement to build from the ground up without the need to be
inside the
We do have a maven repository manager in place but it's only accessible
inside the network when we
are on location.
We have many consultants, some folks work at home on occasion and we want
them to be able to build and write code for a day without having access to
the local network.
Tim
Another things is that we plan to open source the product and post the code
on a website.
People that download will need to build the product. We are not going to
put our repo manager out there for the world to use.
this requirement makes configuring a pom like this a necessity. Ideally it
Hello,
Have you looked at builder-helper plugin? Seems like attach-artifacts
goal exactly
what you need. Am I wrong? [?]
2009/7/31 jvsrvcs jvsr...@gmail.com
Another things is that we plan to open source the product and post the code
on a website.
People that download will need to build the
On Thu, Jul 30, 2009 at 2:19 PM, jvsrvcsjvsr...@gmail.com wrote:
We do have a maven repository manager in place but it's only accessible
inside the network when we
are on location.
We have many consultants, some folks work at home on occasion and we want
them to be able to build and write
build-helper:attach-artifacts attaches artifacts to the build, i.e. so
that they will be installed/deployed at the appropriate stage. This is
almost the opposite of that - the artifacts are dependencies of the
project, not part of the output of it.
Justin
From:
Ow, I got it.
2009/7/31 Edelson, Justin justin.edel...@mtvstaff.com
build-helper:attach-artifacts attaches artifacts to the build, i.e. so
that they will be installed/deployed at the appropriate stage. This is
almost the opposite of that - the artifacts are dependencies of the
project, not
18 matches
Mail list logo
