The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.1.
This version fixes mostly the support of Java annotations for Maven plugins (
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-
annotations.html
)
The Maven Plugin Plugin is used to
Hi Wayne,
The app version is '1.0-SNAPSHOT'.
The Maven is:
$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /opt/maven
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: /opt/jdk1.6.0_29/jre
Default locale: en_US, platform encoding: UTF-8
OS
Hi Jirong,
hujirong wrote:
I found CDIPubSubMgmtMed-0.0.1-SNAPSHOT-scripts.zip in Nexus in this
folder:
local:8080/nexus/content/groups/mdm-
public/com/nbfg/max/wesb/CDIPubSubMgmtMed/0.0.1-SNAPSHOT/
So I guess because the project is depending on the following:
dependency
On 3 July 2012 15:55, Dmitry Trunikov dmitry.truni...@zoral.com.ua wrote:
Hi All,
It seems that my question has an obvious answer. Unfortunately googling
didn't give me a good one.
Prerequisites:
I have a classical multi-module project. The root POM declares two
modules: 'api' and
javac will only recompile classes that have changed. it does not do
dependency analysis, so a breaking change will only cause a compile
failure until you do clean
Thank you for clarification.
Is there any way (except explicit 'clean') to turn on dependency
analysis during compilation.
The
Wayne
100%-nail-hit! how did you know that
xalan-2.7.1.jar xalan-2.7.1.pom
and other stuff . . .
when downloaded as maven-artifact
from the repository, comes down with
such a bunch of HTML rubbish in it?
Who deposits xalan-2.7.1.jar é all?
Before I deleted the mirrors in my
settings.xml,
On 4 July 2012 09:46, Dmitry Trunikov dmitry.truni...@zoral.com.ua wrote:
javac will only recompile classes that have changed. it does not do
dependency analysis, so a breaking change will only cause a compile failure
until you do clean
Thank you for clarification.
Is there any way
Ok Wayne
or anybody else
we have a corporate repository acting as a proxy to central !
fine - this safes you a lot bandwidth and us time.
But what shall I do if I get same rubbish from our repository as well as from
central when I ask for pom / jar? for an artifact?
I just cleared out my
what is returned to an depencey invoked artifact download
if the link to the artifact does not hit a .pom or the .jar wanted
but is redirected by the receiving repository server to a basic
html page explaing the user that artifacts have been moved?
i.e. currently for
The way I do this is to use my IDE's dependency analysis to have my
IDE do a Make (which rebuilds all the downstream changes)... then
before I commit I will do a mvn clean verify to make sure that my
changes are good
Yes my IDE does the analysis too.
The problem is in my colleague.
He is
AFAIK xalan has the groupId:artifactId xalan:xalan see
http://repo.maven.apache.org/maven2/xalan/xalan/
Maybe you declare the repository
http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a
project you are using)
2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
To answer part of my question:
if a project has a dependency on xalan, and somehow maven-magic the artifact is
said to be at
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
however, there, a redirect happens, and the pom or the jar just ends in the
Hi Josef,
Stadelmann Josef wrote:
Ok Wayne
or anybody else
[snip]
What I do not understand is, why xalan-* and a few other artifacts must
come down from
http://shibboleth.internet2.edu/downloads/maven2/org/apache/
Where can I prevent this? can I? can I black-list proactively the
that is what I want to tell you that you will not find any artifacy at
-Ursprüngliche Nachricht-
Von: Olivier Lamy [mailto:ol...@apache.org]
Gesendet: Mittwoch, 4. Juli 2012 16:37
An: Maven Users List
Betreff: Re: [mvn] bad artifacs returned
AFAIK xalan has the groupId:artifactId
so in such case a solution is to exclude org.apache.xalan:xalan from
the shibboleth artifact.
and add a dependency to xalan:xalan.
And contact those folks who publish bad poms.
2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
that is what I want to tell you that you will not find
Keep in mind that the reactor in general resolves the jar within the
multi-module project... so you don't know which source files changed as
easily and therefore you don't know which .class files to remove
If you run with -DskipTests most builds are very fast anyway (hey I
regularly rebuild all
Thank you for the help, here is the result:
C:\Sandbox\MDM\WESBmvn dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WESB Deployment R2-0.0.1-SNAPSHOT
[INFO]
It appears you have a bad dependency definition.
Only you can fix it.
The right one is
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
It appears that you have
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
Ron
I would not say that - because I just found out that the artifact
org/apache/rampart/rampart-project/1.6.2/rampart-project-1.6.1.pom
has the following snippet in it. AND
My project so far depends on this artifact and it comes from apache !
Now I will check if I can make it without this
And opensaml-2.2.3.pom has a reference as well
repositories
repository
idshibboleth.internet2.edu/id
nameInternet2/name
layoutdefault/layout
urlhttp://shibboleth.internet2.edu/downloads/maven2/url
snapshots
That is why one should not put repo definitions in poms.
The people at fault are the opensaml authors.
It is also why you mirror ALL references to repos that Maven makes so
that they all go to your repo manager and then your repo manager will
decide what external repos should be consulted.
in fact content of any jar or pom or sha downloaded is the html page
explaining the user that
*** Internet2 Shibboleth Project has moved ***
what is wrong ?
who has to act ?
This is the result of a poorly configured Maven repository. This is
not Maven's fault.
The shibboleth repository
100%-nail-hit! how did you know that
xalan-2.7.1.jar xalan-2.7.1.pom
and other stuff . . .
when downloaded as maven-artifact
from the repository, comes down with
such a bunch of HTML rubbish in it?
This is not entirely uncommon. I have seen it happen myself (from old
java.net repo, don't
There should be a BIG note on the Maven front page and on the download page.
Do NOT even think about using Maven until you have your Maven repo running!
This means you!!! When applied without a repo, Maven is hazardous and
may cause rage, intense loathing of your vocation and a desire to kick
This whole problem would not even be in the forum if a repo had been
installed.
Well, Josef did say in another post:
we have a corporate repository acting as a proxy to central !
...
But bad luck, our repository is really just a mirror of central and
contains the same rubbish for
I think that the suggestion to validate items returned is a good one
that we should raise with, I think, Aether.
On Wed, Jul 4, 2012 at 2:38 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
There should be a BIG note on the Maven front page and on the download page.
Do NOT even think
Ideally there would be some Maven magic which checks the contents of
the file and ensures it seems like a reasonable pom, jar, war, etc
before saving it to the local repo cache but that does not currently
exist beyond a feature request in JIRA.
I think that the suggestion to validate items
Am I mistaken to think that a
mirrors
mirror
!--This sends everything else to /public --
idnexus/id
mirrorOf*/mirrorOf
urlhttp://myRepoURL:8081/nexus/content/groups/public/url
/mirror
/mirrors
in my settings.xml will stop Maven from reaching a repo that someone
I am not sure I understand the reluctance to test that POMs are well-formed.
A POM that is not well-formed is worthy of a note at least.
Compared to the cost of a download, the test for well-formed XML should
be pretty small for a file the size of a POM.
It should be possible to recognize the
29 matches
Mail list logo
