You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Papapara Tudu <pa...@poczta.onet.pl> on 2008/02/27 10:53:44 UTC
Problem with snapshots
Hello,
maybe I misunderstand something about snapshots, but I have the following
problem:
1. I have a non-Maven project which I export into a jar file and then
install as a snapshot onto my local repository running on Archiva with this
command:
mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
-DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
-DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
-DrepositoryId=archiva.default
2. The very first version of that jar that was deployed onto the repository
is saved as project-2.2-SNAPSHOT.jar.
3. As expected, any further jars that I deploy onto the local repository get
saved as e.g. project-2.2-20080226.143100-1.jar
4. The problem is that when I reference that jar in any other project, when
I build the other project, only the project-2.2-SNAPSHOT.jar version (the
very first one that was installed) is picked up in the output war and ear
files.
5. I can see that the actual snapshots, e.g.
project-2.2-20080226.143100-1.jar do get downloaded from the internal
repository and installed onto my local repository, but they're never used by
referencing projects.
6. I'm using the Maven Plugin for Eclipse and what is strange is that in the
Maven Dependencies tree in all referencing projects, I see the
project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
see this:
project: resolved to version project-2.2-20080226.143100-1 from repository
myRepository
7. I reference this jar in other projects as:
<dependency>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<version>[2,)</version>
</dependency>
(I also tried this configuration:
<dependency>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<version>2.2-SNAPSHOT</version>
</dependency>
but it had exactly the same results)
8. My pom.xml config is:
<distributionManagement>
<snapshotRepository>
<id>myRepository</id>
<url>
dav:http://[someip]/archiva/repository/myRepository/
</url>
</snapshotRepository>
</distributionManagement>
<pluginRepositories>
<pluginRepository>
<id>myRepository</id>
<url>
dav:http://[someip]/archiva/repository/myRepository/
</url>
</pluginRepository>
</pluginRepositories>
<repositories>
<repository>
<id>myRepository</id>
<name>myRepository</name>
<url>http://[someip]/archiva/repository/myRepository</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</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-tp15709789s177p15709789.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
simon.kitching@chello.at wrote:
>
> 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 to have an appropriate date
> suffix.
>
The problem is that when I install new versions of that jar, they don't get
picked up by the build - although the -SNAPHSOT version is NOT the newest
anymore then.
And this all has to work without deleting anything from the internal or
local repositories - otherwise the problem will reoccur whenever new
snapshots are created.
I believe my understanding is correct: here's a quote from the "Better
builds with Maven book:
"You'll see that it is treated differently than when it was installed in the
local repository. The filename
that is used is similar to proficio-api-1.0-20060211.131114-1.jar. In this
case, the version
used is the time that it was deployed (in the UTC timezone) and the build
number. If you were to
deploy again, the time stamp would change and the build number would
increment to 2.
This technique allows 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-with-snapshots-tp15709789s177p15711423.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by "simon.kitching@chello.at" <si...@chello.at>.
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 to have an appropriate date
suffix.
Regards,
Simon
Papapara Tudu schrieb:
> Hello,
> maybe I misunderstand something about snapshots, but I have the following
> problem:
> 1. I have a non-Maven project which I export into a jar file and then
> install as a snapshot onto my local repository running on Archiva with this
> command:
>
> mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
> -DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
> -DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
> -DrepositoryId=archiva.default
>
> 2. The very first version of that jar that was deployed onto the repository
> is saved as project-2.2-SNAPSHOT.jar.
>
> 3. As expected, any further jars that I deploy onto the local repository get
> saved as e.g. project-2.2-20080226.143100-1.jar
>
> 4. The problem is that when I reference that jar in any other project, when
> I build the other project, only the project-2.2-SNAPSHOT.jar version (the
> very first one that was installed) is picked up in the output war and ear
> files.
>
> 5. I can see that the actual snapshots, e.g.
> project-2.2-20080226.143100-1.jar do get downloaded from the internal
> repository and installed onto my local repository, but they're never used by
> referencing projects.
>
> 6. I'm using the Maven Plugin for Eclipse and what is strange is that in the
> Maven Dependencies tree in all referencing projects, I see the
> project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
> see this:
> project: resolved to version project-2.2-20080226.143100-1 from repository
> myRepository
>
>
> 7. I reference this jar in other projects as:
> <dependency>
> <groupId>com.company.project</groupId>
> <artifactId>project</artifactId>
> <version>[2,)</version>
> </dependency>
>
> (I also tried this configuration:
> <dependency>
> <groupId>com.company.project</groupId>
> <artifactId>project</artifactId>
> <version>2.2-SNAPSHOT</version>
> </dependency>
> but it had exactly the same results)
>
> 8. My pom.xml config is:
>
> <distributionManagement>
> <snapshotRepository>
> <id>myRepository</id>
> <url>
> dav:http://[someip]/archiva/repository/myRepository/
> </url>
> </snapshotRepository>
> </distributionManagement>
>
> <pluginRepositories>
> <pluginRepository>
> <id>myRepository</id>
> <url>
> dav:http://[someip]/archiva/repository/myRepository/
> </url>
> </pluginRepository>
> </pluginRepositories>
>
> <repositories>
> <repository>
> <id>myRepository</id>
> <name>myRepository</name>
> <url>http://[someip]/archiva/repository/myRepository</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
>
> I wonder what I am doing wrong.
>
> Thanks in advance for the help.
>
> Papapara Tudu
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
Jeff MAURY wrote:
>
> Can you submit your output with -X option ?
>
> Jeff MAURY
>
>
Maven produced 200 kB of logs, so I'll skip the rest, to me the most
relevant seem to be these few lines:
[INFO] snapshot com.company.project:project:2.2-SNAPSHOT: checking for
updates from myRepository
[DEBUG] Skipping disabled repository central
[DEBUG] project: resolved to version 2.2-20080304.145740-2 from repository
myRepository
[DEBUG] com.company.project:project:jar:2.2-SNAPSHOT:compile (selected for
compile)
So Maven does see and download the new snapshot, but then it still uses the
old one 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 from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
I have identified some more things in my confiaguration, maybe someone will
have any other ideas as to what could be wrong?
1. When I deploy my snapshot onto my local repository with this command:
mvn install:install-file -Dfile=Project.jar -DgroupId=com.company.project
-DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
-DgeneratePom=true
what happens is that the project-2.2-SNAPSHOT.jar gets overwritten with the
new file and then as before, this file is used for the compiled war.
2. I also run automated builds on the same machine where I have the archiva
repository. What is strange there is that it always picks up the most recent
version of the snapshot for the compiled version. So for some reason my
problem only occurs on local builds, and not on the continuous integration
build on my build machine.
Could that be because there's a difference in the metadata xmls between my
internal repo and the local repo?
This is my maven-metadata-local.xml file from the
com/company/project/project folder:
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<version>2.2-SNAPSHOT</version>
<versioning>
<versions>
<version>2.2-SNAPSHOT</version>
</versions>
<lastUpdated>20080312101739</lastUpdated>
</versioning>
</metadata>
And this is the one from my Archiva repo:
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<versioning>
<latest>2.2-SNAPSHOT</latest>
<versions>
<version>2.2-SNAPSHOT</version>
</versions>
</versioning>
</metadata>
Now these are the respective files from the
com/company/project/project/2.2-SNAPSHOT folder:
1. local repository:
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<version>2.2-SNAPSHOT</version>
<versioning>
<snapshot>
<localCopy>true</localCopy>
</snapshot>
<lastUpdated>20080312101739</lastUpdated>
</versioning>
</metadata>
2. archiva:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>com.company.project</groupId>
<artifactId>project</artifactId>
<version>2.2-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>19</buildNumber>
<timestamp>20080311.132319</timestamp>
</snapshot>
<lastUpdated>20080311132319</lastUpdated>
</versioning>
</metadata>
--
View this message in context: http://www.nabble.com/Problem-with-snapshots-tp15709789s177p16001438.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by amit kumar <am...@gmail.com>.
Owing to amateurism I have configured the repository with snapshots at two
places, in the pom.xml and in settings.xml. It has been working fine for me.
Will try playing around with it and let you know.
Regards,
Amit Kumar
On Wed, Mar 5, 2008 at 6:20 AM, Papapara Tudu <pa...@poczta.onet.pl>
wrote:
>
>
> amit kumar-18 wrote:
> >
> > You mean even from the local repository the maven is not able to pick up
> > the
> > latest of the jars?
> >
> Yes, that's the problem - I can see that the latest jars are downloaded to
> my local repository, but they aren't used for the compiled war and ear
> files.
>
> Cheers,
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
amit kumar-18 wrote:
>
> You mean even from the local repository the maven is not able to pick up
> the
> latest of the jars?
>
Yes, that's the problem - I can see that the latest jars are downloaded to
my local repository, but they aren't used for the compiled war and ear
files.
Cheers,
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by amit kumar <am...@gmail.com>.
You mean even from the local repository the maven is not able to pick up the
latest of the jars?
Regards,
Amit
On Tue, Mar 4, 2008 at 8:50 PM, Papapara Tudu <pa...@poczta.onet.pl>
wrote:
>
>
> amit kumar-18 wrote:
> >
> > Well I faced a similar problem but configuring my remote repository for
> > snapshots worked for me. I had to add the below to my repository
> >
> > <repository>
> > <id>my-internal-site</id>
> > <url>file:///\\\\192.168.x.x/Repository</url>
> > <snapshots>
> > <enabled>true</enabled>
> > <updatePolicy>always</updatePolicy>
> > <checksumPolicy>warn</checksumPolicy>
> > </snapshots>
> > </repository>
> >
> > I started getting latest of the jars present under the project-SNAPSHOT
> > folder in the repository.
> >
> >
>
> I tried two configurations:
> 1. using my local 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 the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
amit kumar-18 wrote:
>
> Well I faced a similar problem but configuring my remote repository for
> snapshots worked for me. I had to add the below to my repository
>
> <repository>
> <id>my-internal-site</id>
> <url>file:///\\\\192.168.x.x/Repository</url>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>always</updatePolicy>
> <checksumPolicy>warn</checksumPolicy>
> </snapshots>
> </repository>
>
> I started getting latest of the jars present under the project-SNAPSHOT
> folder in the repository.
>
>
I tried two configurations:
1. using my local 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 the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by amit kumar <am...@gmail.com>.
Well I faced a similar problem but configuring my remote repository for
snapshots worked for me. I had to add the below to my repository
<repository>
<id>my-internal-site</id>
<url>file:///\\\\192.168.x.x/Repository</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
</repository>
I started getting latest of the jars present under the project-SNAPSHOT
folder in the repository.
Hope this works for you as well.
Regards,
Amit Kumar
2008/3/4 Jeff MAURY <je...@jeffmaury.com>:
> Can you submit your output with -X option ?
>
> Jeff MAURY
>
> On Tue, Mar 4, 2008 at 11:35 AM, Papapara Tudu <
> papaparatudu@poczta.onet.pl>
> wrote:
>
> >
> > 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 - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
Re: Problem with snapshots
Posted by Jeff MAURY <je...@jeffmaury.com>.
Can you submit your output with -X option ?
Jeff MAURY
On Tue, Mar 4, 2008 at 11:35 AM, Papapara Tudu <pa...@poczta.onet.pl>
wrote:
>
> 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 - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
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 - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by Papapara Tudu <pa...@poczta.onet.pl>.
Jeff MAURY wrote:
>
> This is because the file name with the timestamp is something internal to
> the repository. When the dependency is resolved to your WAR, the original
> file name is restored based on the artifactId and the version you mention
> in
> your POM.
> Maybe if you put Maven in debug mode, you could see that the file
> retrieved
> from your local repository is the one with the timestamp.
>
OK but I believe it should still work in the following way: when I build a
referencing project, it takes the latest version of the jar (so that will be
the project-2.2-20080226.143100-1.jar 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 from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Problem with snapshots
Posted by Jeff MAURY <je...@jeffmaury.com>.
This is because the file name with the timestamp is something internal to
the repository. When the dependency is resolved to your WAR, the original
file name is restored based on the artifactId and the version you mention in
your POM.
Maybe if you put Maven in debug mode, you could see that the file retrieved
from your local repository is the one with the timestamp.
Regards
Jeff MAURY
On Wed, Feb 27, 2008 at 10:53 AM, Papapara Tudu <pa...@poczta.onet.pl>
wrote:
>
> Hello,
> maybe I misunderstand something about snapshots, but I have the following
> problem:
> 1. I have a non-Maven project which I export into a jar file and then
> install as a snapshot onto my local repository running on Archiva with
> this
> command:
>
> mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
> -DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
> -DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
> -DrepositoryId=archiva.default
>
> 2. The very first version of that jar that was deployed onto the
> repository
> is saved as project-2.2-SNAPSHOT.jar.
>
> 3. As expected, any further jars that I deploy onto the local repository
> get
> saved as e.g. project-2.2-20080226.143100-1.jar
>
> 4. The problem is that when I reference that jar in any other project,
> when
> I build the other project, only the project-2.2-SNAPSHOT.jar version (the
> very first one that was installed) is picked up in the output war and ear
> files.
>
> 5. I can see that the actual snapshots, e.g.
> project-2.2-20080226.143100-1.jar do get downloaded from the internal
> repository and installed onto my local repository, but they're never used
> by
> referencing projects.
>
> 6. I'm using the Maven Plugin for Eclipse and what is strange is that in
> the
> Maven Dependencies tree in all referencing projects, I see the
> project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
> see this:
> project: resolved to version project-2.2-20080226.143100-1 from repository
> myRepository
>
>
> 7. I reference this jar in other projects as:
> <dependency>
> <groupId>com.company.project</groupId>
> <artifactId>project</artifactId>
> <version>[2,)</version>
> </dependency>
>
> (I also tried this configuration:
> <dependency>
> <groupId>com.company.project</groupId>
> <artifactId>project</artifactId>
> <version>2.2-SNAPSHOT</version>
> </dependency>
> but it had exactly the same results)
>
> 8. My pom.xml config is:
>
> <distributionManagement>
> <snapshotRepository>
> <id>myRepository</id>
> <url>
>
> dav:http://[someip]/archiva/repository/myRepository/
> </url>
> </snapshotRepository>
> </distributionManagement>
>
> <pluginRepositories>
> <pluginRepository>
> <id>myRepository</id>
> <url>
>
> dav:http://[someip]/archiva/repository/myRepository/
> </url>
> </pluginRepository>
> </pluginRepositories>
>
> <repositories>
> <repository>
> <id>myRepository</id>
> <name>myRepository</name>
>
> <url>http://[someip]/archiva/repository/myRepository</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</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-tp15709789s177p15709789.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com