Hi,All
from maven 2.2.1 to 3.0.1 can't deploy jar to repository.Can someone
help me?
[INFO]
[INFO] --- maven-deploy-plugin:2.5:deploy (default-deploy) @ maven-iwlsvn
---
[INFO] --
[INFO] BUILD FAILURE
[INFO] --
> I was using the default install of maven on the iMac and I forgot to copy the
> settings.xml file I had on Linux.
I guess I'm a little bit curious now about the contents of your
settings.xml file... Must be a profile that does something with your
spring xml file?
Wayne
Hudson?
On Sun, Dec 12, 2010 at 5:34 PM, Stephen Connolly
wrote:
> 2.1 is a dead duck do not use it. There are major issues with it
>
> 2.2 requires java 1.5 to run and is the end of the 2.x code base (i.e. the
> one where the first version of a plugin loaded in a multi module build is
> the onl
2.1 is a dead duck do not use it. There are major issues with it
2.2 requires java 1.5 to run and is the end of the 2.x code base (i.e. the
one where the first version of a plugin loaded in a multi module build is
the only version loaded)
3.0 is the way to go
- Stephen
---
Sent from my Android
It appeared to exhibit the same behavior for me in 3.0.0 and 2.1.0,
which are the versions I keep around. I see that the JIRA is marked
fixed in 3, so either it's not so fixed, or I made some methodological
experiment in trying it in 3 as well as 2.1.
On Sun, Dec 12, 2010 at 2:46 PM, Wendy Smoak
Oh, yes. I don't recommend using anything but Maven 3.0.
/Anders
On Sat, Dec 11, 2010 at 00:38, Phillip Hellewell wrote:
> On Fri, Dec 10, 2010 at 2:45 PM, Anders Hammar wrote:
> > Maven 3.0 rocks! :-)
>
> Would you recommend it in a production environment?
>
> Phillip
>
>
On Sun, Dec 12, 2010 at 1:57 PM, Benson Margulies wrote:
> In a parent profile, I have a profile that is supposed to activate
> based on the presence of a file in the tree of the child that uses the
> parent. It does not, and -X is not helping me ... since it seems to
> contradict itself. I must b
Hi Roland,
On Sun, Dec 12, 2010 at 12:48 PM, Asmann, Roland
wrote:
>
> Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
> are? I am currently running on 2.0.9 and 2.0.10 (depending on the
> project) and I was wondering if I should start migrating.
Any attempt to describe
In a parent profile, I have a profile that is supposed to activate
based on the presence of a file in the tree of the child that uses the
parent. It does not, and -X is not helping me ... since it seems to
contradict itself. I must be missing something simple here, no?
[DEBUG] Profile with id: 'pa
I'd like to have one profile that just does dir and
another with other stuff. Is there any good way to do this?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.
Hi all,
Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
are? I am currently running on 2.0.9 and 2.0.10 (depending on the
project) and I was wondering if I should start migrating.
Currently I am not allowed to upgrade to 3.0 (a 2.x version is still
mandatory), but mayb
By any chance do you use an active by default profile to pull in your
content that is missing on release?
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 12 Dec 2010 04:12,
Thank you!
On Sun, Dec 12, 2010 at 2:50 AM, Anders Hammar wrote:
> Yes, adding a plugin in the pluginManagement section doesn't actual bind
> it.
> For a binding, you need to have it in build.plugins.
>
> /Anders
>
> On Sun, Dec 12, 2010 at 08:33, Elliot Huntington <
> elliot.hunting...@gmail.co
Yes, adding a plugin in the pluginManagement section doesn't actual bind it.
For a binding, you need to have it in build.plugins.
/Anders
On Sun, Dec 12, 2010 at 08:33, Elliot Huntington <
elliot.hunting...@gmail.com> wrote:
> Yes, here is the build section of pom.xml:
>
>
>${artifac
14 matches
Mail list logo
