does eclipse provide ant tasks to do the plugin building?
I've done exactly the same for netbeans modules,
a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant
tasks.
At least the lifecycle definition might be of interest you,
I added a testcase : a sample report generated for maven-plugin-plugin
see http://jira.codehaus.org/browse/MPLUGIN-11 plugin-info.html attachement
I'm interested in any suggestion to enhance the text (my english is not
always very good ;) )
I really think this will help a lot for Maven adoption
Hi Yann,
in the last few days I experimented a bit with the solution you proposed,
also sharing my experience on irc:#maven, and I ended up having more doubts
than before.
if I choose the approach you proposed, every developer must checkout the
whole project, even if he's in charge of only one
Hi,
You need to use ${settings.localRepository}.
Martin
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Verzonden: vrijdag 6 januari 2006 20:59
Aan: Maven Users List
Onderwerp: [m2] - ${localRepository} values - weired problem
Hi All,
I using some antrun
Hi,
Has anyone had a chance to look at this?
On 12/23/05, Arik Kfir [EMAIL PROTECTED] wrote:
Hi,
I've received the following exception while running mvn site on a
multi-module project (using maven from SVN):
java.lang.NullPointerException
at
When putting them into your 2.0.1 lib directory, did you delete the
equivalent jars that were already there?
-Stephen
On 1/6/06, KC Baltz [EMAIL PROTECTED] wrote:
This is failing for me. I am continuing to get the session is down
exception.
I'm not sure what debugging information you'd like
Grégory Joseph wrote:
http://xdoclet.codehaus.org/Maven2+Plugin
Darryl,
What did you try, what is not working for you ?
The page in question doesn't explain anything, it only says what to do
for one particular case. For example, the first thing I need to do is
incorporate Hibernate into
Hi,
The page in question doesn't explain anything, it only says what to do
for one particular case.
For one sample case, I would say. Using other xdoclet2-plugins is
totally similar, and should be a no brainer if you'd know how xdoclet2
generally works. Other pages might help in this respect,
Grégory Joseph wrote:
For one sample case, I would say. Using other xdoclet2-plugins is
totally similar, and should be a no brainer if you'd know how xdoclet2
generally works. Other pages might help in this respect, although I'll
gladly hear your feedback, because we know they're probably
Vote for this issue:
http://jira.codehaus.org/browse/XDOCLET-41
Maven2 must use better the feature of archetypes in order to facilitate
the migration and adoption of it's technologies.
Srgjan
-
To unsubscribe, e-mail: [EMAIL
Neither will work. You can't obtain the local repository in an
expression in the POM. FWIW, you DO NOT want to include the whole
local repository in your classpath. IT would be huge.
You should use the maven.[compile|runtime|test].classpath refid, and
list the appropriate dependencies.
- Brett
Any one with succussfull use of maven-release-plugin with your project in
cvs yet?
see http://jira.codehaus.org/browse/SCM-128
and http://jira.codehaus.org/browse/SCM-129
Advice is greatly appreciated.
-Dan
Thanks for the point Allan. However, I need to clarify that I'm not trying to
resolve the dependencies within my plugin. My plugin does create a dependency
report similar to project-info-reports:dependencies, however with the output as
XML file, so that it can be rendered into various formats
Take a look at the http://mojo.codehaus.org/dependency-maven-plugin all
the code in there is about resolving dependencies and walking through
various dependency lists to filter type,scope, etc. I imagine all the
code you need will be in there. Basically you just need to call
project.getArtifacts
Brian,
Thanks for the pointer. I will take a look at the code of the plugin.
However, just a fyi:
project.getArtifacts() returns an empty list for me (even that I have
dependencies defined, and I get them listed with my own plugin and with mvn
site).
The same with
I just verified with a local project, it is going much deeper than 1
level. I looked at the jdom pom...the jaxen dependency is optional.
Optional means don't transitively include, so any project including jdom
shouldn't get jaxen and thus anything jaxen includes.
-Original Message-
From:
You'd think as the author of the dependEncy plugin, I would know how to
spell dependEncy.
Change the resolution line to have an e instead of an a:
* @requiresDependencyResolution compile
I tested this quickly and once that is corrected, it listed all my
dependEncies.
Brian,
I actually did the test with dom4j 1.6 (not jdom as I mentioned - I always
confuse those two). The dom4j 1.6 POM has a dependency on Jaxen specified as:
dependency
groupIdjaxen/groupId
artifactIdjaxen/artifactId
version1.1-beta-4/version
/dependency
Jaxen
Indeed this fixes it and I start to see something going ... Thanks a lot!
Last question:
the diff between project.getDependencies() and project.getDependencyArtifacts()
is basically that getDependencies() returns also transitive dependencies? I'm
assuming it follows the guidelines as
Is it normal that a mojo with resolution set to compile has the
following behavior:
project.getArtifacts returns things in the compile scope including
transitive dependencies.
project.getDependencyArtifacts returns only the direct dependencies, but
also includes things in the test scope.
I
Last question:
the diff between project.getDependencies() and
project.getDependencyArtifacts() is basically that getDependencies()
returns also transitive dependencies?
Yes. Although see my previous message under dependencyResolution
question because I noticed that test scope things where
http://jira.codehaus.org/browse/MNG-1944
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 07, 2006 11:52 PM
To: Maven Users List; [EMAIL PROTECTED]
Subject: RE: [m2] dependency-plugin: Doesn't copy transitive
dependencies deeper than first level
I
22 matches
Mail list logo
