Bug#454077: maven2: maven-eclipse-plugin does not exist
paul-debian at home.paulcager.org
Mon Dec 3 00:31:37 UTC 2007
Amelia A Lewis wrote:
>> I'm not sure that I understand the problem correctly. Debian has
>> packaged Maven, but not any of its plugins - so the plugins should be
>> downloaded normally (i.e. in the same way as a non-Debian Maven
>> installation). Is this not the case?
> Doesn't seem to work, for me.
Amy, if you have loads of spare time would you mind trying with the
non-Debian version of Maven (e.g. as downloaded from
)? Only if you have spare time, of course. It might help eliminate /
incriminate the Debian packaging.
> Hmmmm. Think it's a machine-specific issue? Mine never shows the line:
> [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking
> or updates from central
> (from your example)
> Is the location of "central" encoded into the binary or the config files
> somewhere? Maybe I could check that?
I believe it is defined in the "super-pom" held in
/usr/share/java/maven2.jar (org/apache/maven/project/pom-4.0.0.xml). I
can't think of any way that could change accidentally.
In file /etc/maven2/settings.xml is the value of "offline" set to false
(the default value)?
Are you behind a HTTP proxy or firewall? (My apologies if I am stating
> Hmmm. Or a permissions problem? Where would plugins be stored when
The downloaded plugins would be stored in $HOME/.m2 (which Maven creates
automatically). Debian doesn't try to centrally cache the downloaded
artefacts, or anything clever like that.
> The output above indicates the location of the project that
> you were building (or so I assume), but I can't determine where in the
> Debian installation plugins go.
> Looks like needs more work from me. Ah, well.
More information about the pkg-java-maintainers