On 30/07/2010 5:09 PM, Paul Benedict wrote:
You can use -X for a debug log. Or you can funnel system out to a file. I
believe tools like Continuum or Hudson do such things.
Paul
On Fri, Jul 30, 2010 at 4:07 PM, Shan Syed<shan...@gmail.com> wrote:
no, this isn't in regard to our own published artifacts
I regret starting this thread, I apologize
Don 't be sorry. You are getting really good advice from some very
knowledgeable people who just want to help you.
You are not doing things in a way that make it easy for you to satisfy
your client and your life is much harder than it needs to be.
No need to apologize. That is what the forum is for.
Take a close look at what is being proposed and ask the questions that
you need to have answered.
Everyone has clients to satisfy and sometimes they don't ask for what
they really need in the most direct way but you can give them what they
need to do their job in a better way than your current approach and you
will have a lot less work to do as well.
Ron
I didn't mean this question to be an affront to maven conventions - I just
need to figure out a better way to capture a full log
they even want a log of how the build environment was downloaded and
installed
On Fri, Jul 30, 2010 at 5:04 PM, Paul Benedict<pbened...@apache.org>
wrote:
There is a maxim to follow when deploying: "do not redeploy a version
more
than once". Once you deploy version X.Y.Z, it should never be updated,
and
those who download it never need to download it again. So, back to the
original problem, are you guys doing that?
On Fri, Jul 30, 2010 at 3:57 PM, Shan Syed<shan...@gmail.com> wrote:
it only applies to our final release cuts, not our day-to-day
just once for this project really; I wanted to insert such this switch
(if
existed) in our "delivery build" profile
we use archiva for everything else, and actually only make use of
public
maven repositories when we up a version of our dependencies, which is
rare
because of change control
it's all weird stuff, I know, but sometimes I just don't question it
On Fri, Jul 30, 2010 at 4:51 PM, Wayne Fay<wayne...@gmail.com> wrote:
deleting the m2 works, I was just curious to see if there was a
switch
in
maven to force all downloads again
This makes absolutely no sense, doesn't change your BOM, and is
just
wasteful. Consumes bandwidth unnecessarily from a resource that is
being
used by the whole Maven community.
I'd think that if you had enough developers doing this on every
machine on a consistent basis (eg every build), it might add up to
enough traffic to get you on a blacklist somewhere... You really need
to install Nexus or another MRM, this is just plain dumb.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
