, 2012 11:24 AM
To: Maven Users List
Subject: Re: Migration to Maven - Best Practices
Do you always deploy A and B together?
Do you always release A and B together?
On Friday, 21 December 2012, Scott Klein wrote:
crap, that came out all horrible looking, let me try to fix that
section up
, December 21, 2012 11:24 AM
To: Maven Users List
Subject: Re: Migration to Maven - Best Practices
Do you always deploy A and B together?
Do you always release A and B together?
On Friday, 21 December 2012, Scott Klein wrote:
crap, that came out all horrible looking, let me try to fix that
section up
: Friday, December 21, 2012 11:24 AM
To: Maven Users List
Subject: Re: Migration to Maven - Best Practices
Do you always deploy A and B together?
Do you always release A and B together?
On Friday, 21 December 2012, Scott Klein wrote:
crap, that came out all horrible looking, let me try
, 2012 11:24 AM
To: Maven Users List
Subject: Re: Migration to Maven - Best Practices
Do you always deploy A and B together?
Do you always release A and B together?
On Friday, 21 December 2012, Scott Klein wrote:
crap, that came out all horrible looking, let me try to fix that
section up
I am working on converting a number of products over to Maven and after reading
quite a bit I wanted to get some advice on best practices - especially after
reading the thread Recursive Maven considered harmful and about the clean
install problem (which is where I ended up after my first
to read it in
context
-Original Message-
From: Scott Klein [mailto:scott.kl...@goldenhour.com]
Sent: Friday, December 21, 2012 12:37 PM
To: users@maven.apache.org
Subject: Migration to Maven - Best Practices
I am working on converting a number of products over to Maven and after reading
quite
PM
To: users@maven.apache.org javascript:;
Subject: Migration to Maven - Best Practices
I am working on converting a number of products over to Maven and after
reading quite a bit I wanted to get some advice on best practices -
especially after reading the thread Recursive Maven considered
]
Sent: Friday, December 21, 2012 11:24 AM
To: Maven Users List
Subject: Re: Migration to Maven - Best Practices
Do you always deploy A and B together?
Do you always release A and B together?
On Friday, 21 December 2012, Scott Klein wrote:
crap, that came out all horrible looking, let me try
Hi,
I am just getting up to speed with maven and I have a couple of projects that
use maven. I have been fighting with with maven / dependencies / mirrors and
repositories for the better part of a week now with my projects always ending
up with being unable to resolve dependencies. Usually on a
On 24 Nov 2011, at 15:02, Martin Sweeney wrote:
Hi,
I am just getting up to speed with maven and I have a couple of projects that
use maven. I have been fighting with with maven / dependencies / mirrors and
repositories for the better part of a week now with my projects always ending
up
Hello,
I'm testing out migration to Maven 3.0.1 from 2.2.1.
All phases run fine except for the deploy phase.
When I first run mvn clean deploy with 2.2.1, everything runs fine.
Then I make the switch to 3.0.1 and run the same command and everything goes
fine except for the top most maven
vratnagiri wrote:
Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to
deploy metadata: Could not transfer metadata
com.***.deployment:ThirdPartyDeploymentProject:0.0.1-SNAPSHOT/maven-metadata.xml
from/to deploymentRepoSnapshot
Thanks Ben! That was the problem and setting maven.metadata.legacy=true
solves it.
--
View this message in context:
http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml-tp3332094p3332497.html
Sent from the Maven - Users
maven.metadata.legacy=true
solves it.
--
View this message in context:
http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml-tp3332094p3332497.html
Sent from the Maven - Users mailing list archive at Nabble.com
Yes Yoav, the artifactory migration is in the pipeline. You're right. Once we
do that we won't need the workaround anymore.
--
View this message in context:
http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml
?
The last question is crucial for us, as we have several hundreds of projects
to cope with.
I'm sorry if these questions are too naiv or something like that - its just
important for our roadmap :-)
Thanks for any help and input
--
View this message in context:
http://old.nabble.com/Migration
important for our roadmap :-)
Thanks for any help and input
--
View this message in context:
http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.html
Sent from the Maven - Users mailing list archive at Nabble.com
to cope with.
I'm sorry if these questions are too naiv or something like that - its
just
important for our roadmap :-)
Thanks for any help and input
--
View this message in context:
http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.html
Sent from the Maven - Users mailing
if these questions are too naiv or something like that - its
just
important for our roadmap :-)
Thanks for any help and input
--
View this message in context:
http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.html
Sent from the Maven - Users mailing list archive at Nabble.com
naiv or something like that - its
just
important for our roadmap :-)
Thanks for any help and input
--
View this message in context:
http://old.nabble.com/Migration-to-Maven--%21-tp28484923p28484923.html
Sent from the Maven - Users mailing list archive at Nabble.com
In Hudson I can currently only set up a Maven2 project - is this also
working with Maven 3 oder do we have to wait till the maven plugin in
hudson
is updated ?
You could try building with M2 on Hudson and use M3 on your
developer's desktops (assuming you're doing nothing weird, it should
[Joke]
Hey ! Marty McFly should be able to see in the future with its dolorean !
By doing this, you should know when m3 will be released :-)
[/joke]
Joke apart, using Freestyle jobs doesn't allow to use maven oriented plugin
in the builds (like release hudson plugin).
To my part, I won't migrate
Same here,
I don't want to use freestyle jobs to maven as I base my releases to the
m2-release plugin of Hudson (yes I know about the freestyle release plugin,
but it doesn't fit exactly to the needs of a maven release)
I also think that having different versions of maven in development and CI
Hi,
We (the Apache Directory Studio Team) are currently working on switching our
build system from Ant+Ivy to Maven to unify the whole build system of the
Directory project (as we were the only subproject to use Ant+Ivy, while the
others were using Maven for a while now).
We've faced a few
Hi Jeff,
Thanks for your answer.
We tried this plugin some time ago, but it did not fit our needs.
We wanted to be able to build our application without having Eclipse
installed on the machine, as well as be able to build all our distributions
(Mac OS X, Linux, Windows) from one single machine
My experience with Eclipse plugins is not to use a Maven repository. The
reason for that is because Eclipse uses its own internal way of resolving
the dependencies for Eclipse plugins (using your Eclipse installation or
your workspace), it will require you to synchronize your MANIFEST.MF and you
26 matches
Mail list logo
