That's completely reasonable -- we don't have more than one version in
production at a given time, however.
On Tue, Feb 1, 2011 at 9:29 PM, Ron Wheeler
rwhee...@artifact-software.comwrote:
On 01/02/2011 11:03 AM, Mate Varga wrote:
Perforce, and we're strict about comments as well, but we
Hi,
we're using an internal repository manager (Artifactory) for storing our
internal artifacts. Local builds always have a version number of ''
(instead of SNAPSHOT, there are good reasons for that) -- we're only using
simple numbers for versioning internal artifacts, A.B.C -like
to type on the
screen
On 1 Feb 2011 11:13, Mate Varga mate.va...@gmail.com wrote:
give a short description of the issues that made you abandon
SNAPSHOTS?
Ron
On 01/02/2011 9:22 AM, Mate Varga wrote:
What assumptions do I break except the immutability of an artifact with a
specific version? (Which is only broken locally, and mvn should not really
know about
(we have Nexus) is not really
a determining factor in our selection of a methodology and development
protocol.
Ron
On 01/02/2011 10:14 AM, Mate Varga wrote:
That sounds right.
As far as I know, Maven assumes that releases are immutable, but snapshots
are not. So I could just use {some
Hello,
I've got an Ant task which is bound to 'generate-resources' phase. If I try
to deploy the project, the task gets executed twice (before and after the
tests).
Any ideas about how could I prevent that?
# 'release' and 'local' are my own profiles.
(~/)\mvn -P release,-local clean deploy
/execution
...
On Fri, Dec 17, 2010 at 10:25 AM, Mate Varga mate.va...@gmail.com wrote:
Hello,
I've got an Ant task which is bound to 'generate-resources' phase. If I try
to deploy the project, the task gets executed twice (before and after the
tests).
Any ideas about how could I prevent
Never mind, I've spend half day with this and it was my fault. :(
(
mvn -Drelease-version=43 -P release,-local clean test deploy
)
test / deploy both run tests.
On Fri, Dec 17, 2010 at 10:35 AM, Mate Varga mate.va...@gmail.com wrote:
It also seems that this has nothing to do with whatever
Hi,
I'm pretty new to Java and Maven, so my question may be very naive
and/or stupid, apologies for that.
I'm trying to compile an open-source project (if that matters, it's
https://plugins.atlassian.com/plugin/details/4832 ), which is supposed
to be built with Maven. I've got Maven 3 installed
for network failures on your side, and repeat builds with -U to
force maven to try again (the fact that a dep was not found is cached)
Thanks,
~t~
On Fri, Dec 10, 2010 at 1:22 PM, Mate Varga mate.va...@gmail.com wrote:
Hi,
I'm pretty new to Java and Maven, so my question may be very naive
Thanks.
You mentioned you have an internal repo already, so if the maintainers
of the remote repos you're trying to pull from won't cooperate, put
the needed artifacts in your own repo and you'll be good to go.
Yeah, that's what I wanted to avoid. I will do it if there is no other
way, but I
the scope of all those dependencies to provided,
which should effectively disable deeper dependency resolution.
Stefan
On Fri, 10 Dec 2010 12:56:49 +
Mate Varga mate.va...@gmail.com wrote:
Hello Tamas,
1) Sources are checked out from SVN to the local drive.
2) Yes, missing dependencies
Ron,
I didn't want to dump mvn output here -- I know what the problem is,
namely that some repositories are not properly set up (for example:
https://maven.atlassian.com/content/repositories/public/com/atlassian/jira/atlassian-jira-webapp/3.12-SNAPSHOT/
-- there is no valid metadata file here, so
13 matches
Mail list logo
