stop the build from happening, but you can stop the artifact from being
deployed.
-Original Message-
From: baz themail [mailto:bazthem...@gmail.com]
Sent: Wednesday, January 05, 2011 12:55 PM
To: Maven Users List
Subject: Re: Is there any way to stop the same version of pom file
, baz themail bazthem...@gmail.com wrote:
Todd, thats one of the function that I thought Nexus has... but I
cannot find the usage for it. Is it only available in Pro version?
On Wed, Jan 5, 2011 at 9:58 AM, Thiessen, Todd (Todd)
tthies...@avaya.com wrote:
Configure your Nexus server to not allow
to have it. It isn't a Pro feature, the free version
also has it.
With regards,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Jan 6, 2011 at 7:08 PM, baz themail bazthem...@gmail.com wrote:
Nick
On Thu, Jan 6, 2011 at 7:24 PM, baz themail bazthem...@gmail.com wrote:
How is the upgrade process from 1.3.6 to 1.8.0.1? Painless?
On Thu, Jan 6, 2011 at 10:12 AM, Nick Stolwijk nick.stolw...@gmail.com
wrote:
I've also checked 1.3.6 (still in production here, Saturday we are
moving to 1.8.0.1
wrote:
On Tue, Jan 4, 2011 at 12:28 PM, baz themail bazthem...@gmail.com wrote:
Hi,
Is there any way to stop the same version of pom file/build being
built more than once?
Being _built_? Probably not... anyone can check out a tag and
re-build that version locally, nothing to prevent
Hi,
Is there any way to stop the same version of pom file/build being
built more than once?
Thanks.
B.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Hi,
1. What is the best and recommended way to limit the size of the local
maven repo? Currently, I am having a cron job to remove older
SNAPSHOT.
2. Is there any way to keep certain release builds but not others?
Meaning, is there any type of promotion mechanism in maven to mark
some releases
I am sorry if i cause the group to over-react about this real issue
that i am here.
I read the wiki page
http://maven.apache.org/plugins/maven-deploy-plugin/usage.html three
(or more) times now. I still not sure how to deploy older artifacts
from local repository to remote repository without the
suggestions as to how to make this more obvious, feel free to submit
documentation JIRAs and I'm sure the plugin developers will take those
under advisement.
On 9/23/10 11:42 AM, baz themail wrote:
I am sorry if i cause the group to over-react about this real issue
that i am here.
I read
anders,
Yes, i am planning to back up the local repo first.
Thanks guys...
On Thu, Sep 23, 2010 at 10:43 AM, Anders Hammar and...@hammar.net wrote:
As you don't seem to be fully comfortable with Maven, I suggest that you
either use the staging feature of Nexus Pro or (if you're using Nexus
just recover the files from there.
Otherwise you could manually load the files from your local into
nexus' storage folder, the do a clear cache and reindex.
Sent from my iPad
On Sep 23, 2010, at 9:15 AM, baz themail bazthem...@gmail.com wrote:
Ummm, thanks. I read that and i understand
Hi,
If the data in the remote release repository is corrupted and no
backups. However, I found the artifacts in the local repository from a
build machine. Can i re-deploy them into remote repository? How to do
deploy a specific version like that without changing anything? Do i
still need the
On Wed, Sep 22, 2010 at 23:20, baz themail bazthem...@gmail.com wrote:
Hi,
If the data in the remote release repository is corrupted and no
backups. However, I found the artifacts in the local repository from a
build machine. Can i re-deploy them into remote repository? How to do
deploy
If there are version 1.0.0.0, 2.0.0.0 and 3.0.0.0 of A in my local
repo. If I go to the location/workspace where I built A. If I type
mvn deploy -Dversion=2.0.0.0, then will this deploy command deploy
the 2.0.0.0 from my local repository to remote repository without
re-building it?
Thanks. A.
On
Hi,
We are using Nexus here. I am pretty sure the parent pom file has been
deployed and in use already. However, for some reason, I cannot see it
in Nexus, why? How can i find it?
Thank you.
A.
-
To unsubscribe, e-mail:
.
Is there any way that i can verify?
On Tue, Sep 21, 2010 at 11:52 AM, Nayan Hajratwala na...@chikli.com wrote:
On Sep 21, 2010, at 2:50 PM, baz themail wrote:
Hi,
We are using Nexus here. I am pretty sure the parent pom file has been
deployed and in use already.
What makes you think it has
the parent pom file
deployment process?
On Tue, Sep 21, 2010 at 2:03 PM, Bryan Loofbourrow
bryan.loofbour...@amdocs.com wrote:
-Original Message-
From: baz themail [mailto:bazthem...@gmail.com]
Sent: Tuesday, September 21, 2010 1:39 PM
To: Maven Users List
Subject: Re: why I do not see
Hi,
How can i test release plugin locally in my machine? Specifically, can
i release the artifacts into my local repository on my machine? Can i
configure it so that i do not need to make actual updates to pom files
in perforce but only in local source tree?
Thank you.
A.
Ron, Bengt, and all,
I am definitely looking forward to the best practice for handling
release and via maven release plug-in.
Meanwhile,
1. I agreed to what Ron's example about messaging v.1.8.3. If we
structure the code and build correctly, and if we can separate
messaging as a stable module,
Thanks for the replies.
Yes, i know about DryRun. So, my question is: Does DryRun correctly
run without SCM information such as P4 userid and password?
Thanks. B.
On Thu, Sep 16, 2010 at 7:47 AM, Nayan Hajratwala na...@chikli.com wrote:
On Sep 16, 2010, at 10:45 AM, baz themail wrote:
Hi
Another question. Is this possible to release into local repository
without giving SCM information such as P4 username and password? I do
not mean dryRun this time.
On Thu, Sep 16, 2010 at 10:12 AM, baz themail bazthem...@gmail.com wrote:
Thanks for the replies.
Yes, i know about DryRun. So
confirm the creation of new
version'ed jar in both dryRun or actual log?
On Thu, Sep 16, 2010 at 11:16 AM, baz themail bazthem...@gmail.com wrote:
Another question. Is this possible to release into local repository
without giving SCM information such as P4 username and password? I do
not mean
] to
install instead of deploy.
[1]
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Thu, Sep 16, 2010 at 8:25 PM, baz themail bazthem...@gmail.com wrote
Hi,
I have been searching the maven website and articles but not sure if i
get the best practice for managing snapshots and release.
Specifically, if continuous builds produce maven snapshot builds, then
when will i produce maven release builds using maven release plug-in?
Will I ever produce a
24 matches
Mail list logo
