On Wed, Sep 3, 2008 at 12:21 PM, gotama <[EMAIL PROTECTED]> wrote:
>
> what is not clear to me is why 'alpha' versions make it into the releases
> repository. I previously did not set my version for the maven-war-plugin.
> 2.1-alpha-2 is the default version. In the Maven world, I thought alpha/beta
a
versions = SNAPSHOTS.
--
View this message in context:
http://www.nabble.com/-INFO--Dependency-...-has-changed-...-messages-during-build-tp19276739p19296172.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
if you have further ideas about this message.
Thanks.
--
View this message in context:
http://www.nabble.com/-INFO--Dependency-...-has-changed-...-messages-during-build-tp19276739p19279904.html
Sent from the Maven - Users mailing list a
You do see the differences, right?
> {groupId=com.stubhub.mycompany.globalLib, artifactId=saxon-xpath, version=8,
> {groupId=com.mycompany.legacy.globalLib, artifactId=saxon-xpath, version=8,
com.stubhub...
vs
...legacy.globalLib
Don't ask me what is going on -- I have no idea. But this is certai
why it is saying the dependency
"has changed".
What's this message about and how do I make it go away?
Thanks!
--
View this message in context:
http://www.nabble.com/-INFO--Dependency-...-has-changed-...-messages-during-build-tp19276739p19276739.html
Sent from the Maven - Use
