Hello,
This morning, I updated our Nexus version from 1.3.1.1 to 1.3.2. After
that my builds did not run because they failed to download snapshot
dependencies from a hosted repository. As yesterday everything was still
fine, I suspected a regression in Nexus, went back to 1.3.1.1, but the
Whenever you see Maven making requests for -SNAPSHOT (and you don't have
it configured with useUnique = false) it always means that the
maven-metadata.xml file for that snapshot is wrong or couldn't be found.
It's hard to say why that could have happened, but this often happens if
you do a
version2.2-SNAPSHOT/version
versioning
snapshot
buildNumber19/buildNumber
timestamp20080311.132319/timestamp
/snapshot
lastUpdated20080311132319/lastUpdated
/versioning
/metadata
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots
Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15848863.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
,
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15848863.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
I just wanted to bring this topic up again as I still don't know what the
reason for my problem is. Does anyone have any other ideas? Thanks!
Cheers,
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15824504.html
Sent from the Maven
Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15824504.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
,
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15824504.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
for compilation. Shouldn't the new snapshot
(project-2.2-20080304.145740-2.jar) instantly replace the old
project-2.2-SNAPSHOT.jar file when it's downloaded from Archiva?
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15829461.html
Sent
repository both for releases and snapshots
2. having a separate local repo for releases and a separate one for
snapshots.
Both results were identical though :(
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15829527.html
Sent from
one for
snapshots.
Both results were identical though :(
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15829527.html
Sent from the Maven - Users mailing list archive at Nabble.com
enabledtrue/enabled
/snapshots
/repository
/repositories
I wonder what I am doing wrong.
Thanks in advance for the help.
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots
/repository
/repositories
I wonder what I am doing wrong.
Thanks in advance for the help.
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15709789.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi,
The problem is that maven assumes that the -SNAPSHOT is the newest, not
the oldest version available.
You obviously have projects that declare dependencies on just -SNAPSHOT,
but want the latest *dated* version to be used. So I suggest you delete
the original -SNAPSHOT version, or rename it
you to continue using the latest version by declaring
a dependency on 1.0-
SNAPSHOT, or to lock down a stable version by declaring the dependency
version to be the specific
equivalent such as 1.0-20060211.131114-1.
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem
and not project-2.2-SNAPSHOT.jar) and
puts it in the output war file.
What it does though is it just takes the project-2.2-SNAPSHOT.jar file and
puts it in the output war file.
Papapara Tudu
--
View this message in context:
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15711493.html
Sent
suffix?
Thanks a lot
--
View this message in context:
http://www.nabble.com/problem-deploying-snapshots-tf4529303s177.html#a12924327
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
-SNAPSHOT-20070927.154235-1.jar
Whats happening with the snapshot suffix?
Thanks a lot
--
View this message in context:
http://www.nabble.com/problem-deploying-snapshots-tf4529303s177.html#a12924327
Sent from the Maven - Users mailing list archive at Nabble.com
Hello,
This is normal maven behavior for snapshots deployment: each snapshot
is deployed with a unique version number. The metadata reflects this
and defines the lates snapshot so that when you ask for
foo:bar:1.0-SNAPSHOT you really get foo:bar:1.0-2342344234665.2423.
I think you can change this
We are trying out using ant/m2 tasks for ant to assemble an legacy
application.
When using the dependencies task it will download the specified
snapshot dependencies but they are not included in fileset when
copying. It works nice if the snapshots were built on the same
machine. Is it broken? Or
-artifact-ant might introduce other problems as
well - works for us though...
Regards
Ingo
-Original Message-
From: Konstantin Polyzois [mailto:[EMAIL PROTECTED]
Sent: Friday, January 27, 2006 10:25 AM
To: Maven Users List
Subject: [m2] problem with snapshots and Maven 2.0.2 Tasks for Ant
Hello,
In our organization we want to use snapshot versions of
some of our libraries, during developing.
Normally, this would be done by stating the version number
for the library as SNAPSHOT in project.xml
But this practice is not allowed by our build managers,
they only want references to
://oness.sourceforge.net
-Original Message-
From: Marcel Vehof [mailto:[EMAIL PROTECTED]
Sent: Friday, July 23, 2004 10:45 AM
To: '[EMAIL PROTECTED]'
Subject: problem using snapshots in JAR override
Hello,
In our organization we want to use snapshot versions of some
of our libraries, during
'
Subject: RE: problem using snapshots in JAR override
Hi,
You must specify the full name of the file
maven.jar.mylibrary=path_to_file/mylibrary-SNAPSHOT.jar
This is designed to use different file names, what you're doing using
different versions is a *very bad* idea.
Regards
Carlos Sanchez
, 2004 10:45 AM
To: '[EMAIL PROTECTED]'
Subject: problem using snapshots in JAR override
Hello,
In our organization we want to use snapshot versions of
some of our libraries, during developing.
Normally, this would be done by stating the version number
for the library as SNAPSHOT
Mmm, you should raise an issue to JIRA.
It's a very bad idea because you are trying to cheat your build managers.
-Original Message-
From: Marcel Vehof [mailto:[EMAIL PROTECTED]
Sent: Friday, July 23, 2004 11:45 AM
To: 'Maven Users List'
Subject: RE: problem using snapshots in JAR
On Jul 23, 2004, at 04:51, Maczka Michal wrote:
In m2 we have already one single install goal which is smart enough
to
check project's type and version .
It means that soon you will be able to do:
maven install
and this will do what (depending of the context) what jar:install,
27 matches
Mail list logo
