thanks, guys!
so which manager would you suggest? i read a bit about nexus, archiva and
artifactory on the very feature of prohibiting redeploy. nexus does it for
sure (though role-based), while the other two seem not to handle this (and
that is my question - is it really?).
--
View this
matinh wrote:
Archiva has an open issue for it:
https://jira.codehaus.org/browse/MRM-747
i know very well how long it takes in opensource projects ;). i've seen this
issue, but i need already implemented and tested solution, as this feature
is one of the main requirements (and besides we
yep, i've already found out how to do that in nexus :)
--
View this message in context:
http://www.nabble.com/possibility-to-control-an-artifact-version-when-installing-deploying-releasing--tp21119401p21133856.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Yoav Landman wrote:
True. We are updating the 1.3 docs towards the final release in a couple
of days :).
great, looking forward to reading the updated docs!
Yoav Landman wrote:
And yes, full LDAP/AD integration is already there for quite some time in
1.3 with full UI
the feature i'm interested in is to be able to prohibit a developer to
install/deploy/release an updated artifact under the same version that is
already in the repository.
our previous release management system was build around the concept of
complete uniqueness of a version, which meant that if
Stephen Connolly-2 wrote:
afaik, the deploy plugin will not overwrite a version that has
previously been deployed
and what would it do then? fail the deploy?
Stephen Connolly-2 wrote:
certainly, the major repository managers do not allow re-deployment
ah, so the policy is up to
using version 2.1-alpha-1 (tested on 2.0.2 also). used the same configuration
as described in FAQ of the plugin, when i do mvn install only the war is
installed but not the jar with classes. also classesClassifier seem to have
no effect on the jar generated with archiveClasses.
maybe there's
well org.apache.maven.model.io.xpp3 does all the stuff, but now i experience
that the pom.xml it generates using a Model object constructed by myself is
just empty o.O. are there any requirements on that?
--
View this message in context:
hi there.
my question is simple: has Maven got a reusable API to do with POM fiddling?
what i want to do is to integrate mvn with our existing build/release system
and especially generate/automatically correct POMs. and i just don't want
to deal with parsing and validating POMs myself, so i
