maven dependency issue (sqljdbc4.jar not picked up during junit test)

Hi, I am scratching my head on this one. Have this component that rely on MSSQL Server 2008. The one developed this rely on sqljdbc4.jar (v3.0) being added to the local java installation (JAVA_HOME/jre/lib/etc/ I found this a bit silly that each developer working on this component need to tweak

Re: Archiva vs. Nexus

I have never used Nexus, but this "error" seem like a classic windows "long file names" issue - I suggest you specify C:\program~\Sonatype\ instead of C:\Program Files\Sonatype\... Alternatively surround long file names/paths with quotes - not sure if this is part of the standard installatio

is it safe to upgrade maven from v3.0.4 to v3.2.1 ?

Hi, Just wonder if I could expect issues to crop up by upgrading maven from v3.0.4 to the most recent stable version available (v3.2.1 while writing this) cheers - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/is-it-safe-to-upgrade-maven-from-v3-0-

Re: Aw: database/users lost after upgrade from archiva 1.3.6 to 2.0.1

sorry about that - just closely linked to both maven and archiva - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/database-users-lost-after-upgrade-from-archiva-1-3-6-to-2-0-1-tp5790266p5790270.html Sent from the Maven - Users mailing list archive a

database/users lost after upgrade from archiva 1.3.6 to 2.0.1

Hi, I have run into a problem when upgrading Archiva 1.3.6 to v2.0.1 Even though I retained the data/database/users directory, archiva fail to validate accounts. I have tried this a few times now and the problem is the same. It's running on tomcat-7.0.42 Starts up nicely and performs the upgrade

Re: maven release-plugin 2.5 bug - releasing snapshots...

> So if I understand correctly you want to use SNAPSHOTs because: > - you don't want the artifact to end up in the "releases"-repository yes, correct > because QA needs to be done first Not quite - occasionally projects (still in development state but nearing its end) engage formal internal te

Re: maven release-plugin 2.5 bug - releasing snapshots...

Fully agree but with a snapshot not should be treated an release. The concept of "official snapshots" along with full site info and branch tagging don't seem wrong where I come from. If a project going through some stringent QA where formal test teams want to keep track of what they testing agains

Re: maven release-plugin 2.5 bug - releasing snapshots...

Doing it as I explained did NOT allow you to do a release or refer to it within other resources during a legic release phase What you triggered was a release (as if legit) to go into the snapshot repo - cant see any issues with that kind of behavior and have turned out to be very useful when imple

Re: maven release-plugin 2.5 bug - releasing snapshots...

That's a way to general statement to be made - that also is incorrect ! A snapshot is not allowed for final release - but could still be released into a shapshot repo for test purposes ! The question really bogs down to how much control you'd like to have against a release snapshot. Anyone can

Re: maven release-plugin 2.5 bug - releasing snapshots...

Sorry for that - I was just in the process of updating this a simple copy/paste mistake I am using 2.5 when the problem occur - as illustrated on the image below As you can see the prompt "What is

Re: maven release-plugin 2.5 bug - releasing snapshots...

I don't think this issue have been rectified. The maven release plugin I use (downloaded from maven central via my plugin) is as follows... This fail: org.apache.maven.plugins maven-release-plugin

maven release-plugin 2.5 bug - releasing snapshots...

Hi,Occasionally we have a need to perform a formal release on unfinished work so it can be tracked.These snapshot releases would in effect be releases identical to a formal release with the exception that the snapshot for a set release is tagged with a time stamp when released into archiva's snapsh

centralized settings.xml vs local question

Hi, I am a strong advocate of maven & Archiva where I administer our departments archiva & svn and site server server where we use maven to build/release stuff. I don't claim to be an expert in the field (but I am not completely dumb either when it comes to this :) - so if my question is silly ple