On Mon, Aug 16, 2010 at 5:53 PM, Trevor Harmon wrote:
> On Aug 16, 2010, at 12:29 PM, Justin Edelson wrote:
>
>>> Okay, let me make sure I understand this. Say I've got a main artifact
>>> and a customized plugin that it depends on. I can configure the plugin
>>> to deploy to my own remote reposit
>-Original Message-
>From: Trevor Harmon [mailto:tre...@vocaro.com]
>
>I don't see the advantage of altDeploymentRepository. What's wrong
>with modifying the POM? I'd prefer not to have to remember a command
>line parameter and just do a simple "mvn deploy".
That sounds useful if you want
>-Original Message-
>From: Trevor Harmon [mailto:tre...@vocaro.com]
>On Aug 16, 2010, at 1:20 AM, Stephen Connolly wrote:
>> Your life would be much easier using a repository manager for your
>> "internal" repository. Nexus is almost trivial to set up, for
example.
>
>It is trivial to set
On Aug 16, 2010, at 12:29 PM, Justin Edelson wrote:
Okay, let me make sure I understand this. Say I've got a main
artifact
and a customized plugin that it depends on. I can configure the
plugin
to deploy to my own remote repository by adding the repository info
to
the plugin POM's .
I wou
On 8/16/10 3:04 PM, Trevor Harmon wrote:
> On Aug 16, 2010, at 10:18 AM, Justin Edelson wrote:
>
>> One "in and out" to learn is that your distinction of "internal" and
>> "external" repositories isn't found in Maven.
>
> I found it here:
>
> http://docs.codehaus.org/display/MAVENUSER/Maven+Conc
On Aug 16, 2010, at 10:18 AM, Justin Edelson wrote:
One "in and out" to learn is that your distinction of "internal" and
"external" repositories isn't found in Maven.
I found it here:
http://docs.codehaus.org/display/MAVENUSER/Maven+Concepts+Repositories
Is the term "external repository" not
On 8/16/10 12:23 PM, Trevor Harmon wrote:
> On Aug 16, 2010, at 7:20 AM, Justin Edelson wrote:
>
>> But if you are a single developer, I'm not sure what value you are
>> looking to get out of this. Your local Maven repository acts as a local
>> cache, so unless you need to blow this away with some
On 16/08/2010 12:23 PM, Trevor Harmon wrote:
On Aug 16, 2010, at 7:20 AM, Justin Edelson wrote:
But if you are a single developer, I'm not sure what value you are
looking to get out of this. Your local Maven repository acts as a local
cache, so unless you need to blow this away with some regul
On 16/08/2010 12:07 PM, Trevor Harmon wrote:
On Aug 16, 2010, at 4:48 AM, Ron Wheeler wrote:
Find a provider that lets you run your own application.
Put it on a cloud service.
Yes, those are ways around the shared hosting problem, but as soon as I have to
purchase and manage separate server
On Aug 16, 2010, at 7:20 AM, Justin Edelson wrote:
> But if you are a single developer, I'm not sure what value you are
> looking to get out of this. Your local Maven repository acts as a local
> cache, so unless you need to blow this away with some regularity, what's
> the point?
Well, I'm a sin
On Aug 16, 2010, at 4:48 AM, Ron Wheeler wrote:
> Find a provider that lets you run your own application.
> Put it on a cloud service.
Yes, those are ways around the shared hosting problem, but as soon as I have to
purchase and manage separate server space just to run a repository manager, it
i
What you are referring to as a "external" repository is essentially a
caching proxy.
If the only repository you are proxying is central, then theoretically
you could use any caching proxy server (including Apache).
But if you are a single developer, I'm not sure what value you are
looking to get
On 16/08/2010 4:56 AM, Trevor Harmon wrote:
On Aug 16, 2010, at 1:20 AM, Stephen Connolly wrote:
Your life would be much easier using a repository manager for your
"internal" repository. Nexus is almost trivial to set up, for example.
It is trivial to set up *if* you have the necessary permi
You should discuss this in the Nexus forum.
Nexus is easy to st up and does not require a separate container.
It does both internal and external with proper access control.
Other repository solutions may also work but I use Nexus for my
development team.
Ron
On 16/08/2010 4:16 AM, Trevor Ha
On Aug 16, 2010, at 1:20 AM, Stephen Connolly wrote:
> Your life would be much easier using a repository manager for your
> "internal" repository. Nexus is almost trivial to set up, for example.
It is trivial to set up *if* you have the necessary permissions to set up the
service. In my case, I
Your life would be much easier using a repository manager for your
"internal" repository. Nexus is almost trivial to set up, for example.
As for internal vs external, there is no difference, you don't need a
repository manager... but your life will always be easier if you use one.
-Stephen
P.S.
Hi,
I've set up an "internal" repository for deploying project artifacts. It was
remarkably easy to do. All I needed was some web space with SCP access. After
that it was only a matter of configuring my POM's to
point to the URL. No repository manager needed.
Now I'd like to set up an "extern
17 matches
Mail list logo
