Hi,
I'm pretty new to Java and Maven, so my question may be very naive
and/or stupid, apologies for that.
I'm trying to compile an open-source project (if that matters, it's
https://plugins.atlassian.com/plugin/details/4832 ), which is supposed
to be built with Maven. I've got Maven 3 installed
Hi,
Okay, but to be able to help, we need more:
1) where are the sources you try to build? (especially POM)
2) what is the failure? dependency resolution fails as missing a
dependency or what?
3) check for network failures on your side, and repeat builds with -U to
force maven to try again (the
Hello Tamas,
1) Sources are checked out from SVN to the local drive.
2) Yes, missing dependencies. The problems stem from things like
missing maven-metadata files in the public repos. (I've checked that,
the repo maintainers do know about the inconsistencies, but they
refuse to fix it.)
3) I've
On Fri, Dec 10, 2010 at 7:22 AM, Mate Varga mate.va...@gmail.com wrote:
However, I have all of the first level (direct) dependencies resolved.
As far as my knowledge goes, it's enough to have the first level
dependencies to compile a Java project,
Not necessarily... it depends on whether the
Thanks.
You mentioned you have an internal repo already, so if the maintainers
of the remote repos you're trying to pull from won't cooperate, put
the needed artifacts in your own repo and you'll be good to go.
Yeah, that's what I wanted to avoid. I will do it if there is no other
way, but I
Hi Mate,
you can, as a workaround, download the pom.xml of your dependency and copy
those dependencies into your own pom.xml (or another one which only contains
those). Then change/add the scope of all those dependencies to provided,
which should effectively disable deeper dependency
Thanks, that's a good idea.
On Fri, Dec 10, 2010 at 2:07 PM, Stefan Seidel ssei...@vub.de wrote:
Hi Mate,
you can, as a workaround, download the pom.xml of your dependency and copy
those dependencies into your own pom.xml (or another one which only contains
those). Then change/add the
Mate,
You might get more help if you actually provided some details about what
is your build is actually saying and what repos are broken.
Ron
On 10/12/2010 9:07 AM, Stefan Seidel wrote:
Hi Mate,
you can, as a workaround, download the pom.xml of your dependency and copy those dependencies
Ron,
I didn't want to dump mvn output here -- I know what the problem is,
namely that some repositories are not properly set up (for example:
https://maven.atlassian.com/content/repositories/public/com/atlassian/jira/atlassian-jira-webapp/3.12-SNAPSHOT/
-- there is no valid metadata file here, so
Hm,
ping Atlassian to clean-up their Nexus ;)
Also, if you specify an exact dependency with some version (let's say the
timestamped one in this repo) in the depMgt of the POM you are building, it
should override all transitive deps your build tries to pull in.
Thanks,
~t~
On Fri, Dec 10, 2010
10 matches
Mail list logo
