Using xfire interface to initiate the build of a project?
Hi can I use the Xfire/SOAP interface to initiate the build of a project, as suggested by: http://maven.apache.org/continuum/guides/mini/guide-soap-api.html If so, where can I find the jar file to link against ? Regards Mark Donszelmann
Re: Working with maven 2 course notes released under Creative Commons
Hi Arnaud, Sure! How do you see this progressing? On 9 Dec 2005, at 21:55, Arnaud Bailly wrote: ir. ing. Jan Dockx wrote: Good point! (me idiot). http://cvs.peopleware.be/training/maven/maven2/> On 9 Dec 2005, at 17:21, Matt Raible wrote: I'm assuming this is some sort of document we can look at online? Matt On 12/9/05, ir. ing. Jan Dockx [EMAIL PROTECTED]> wrote: We just released the course notes of our 3-day course Working with Maven 2 under a Creative Commons License (only attribution required). Given the time we spend in finding things out, other people new to Maven 2 might benefit from the notes, although they are only bullet-style. That's really nice, would you share sources (as a maven2 site ?). I plan to make that kind of course here in first quarter so I could share slides, screenshots, rewriting... -- Arnaud Bailly - Ingénieur de Recherche NORSYS 1, rue de la Cense des Raines ZAC du Moulin 59710 ENNEVELIN Tel : (33) 3 28 76 56 76 Fax : (33) 3 28 76 57 00 Web : http://www.norsys.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] x-tad-smallerMet vriendelijke groeten, Jan Dockx /x-tad-smallerx-tad-smaller PeopleWare NV - Head Office/x-tad-smallerx-tad-smaller Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 /x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller PeopleWare NV - Branch Office Geel/x-tad-smallerx-tad-smaller Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25/x-tad-smallerx-tad-bigger /x-tad-biggerx-tad-smaller http://www.peopleware.be/ /x-tad-smallerx-tad-smallerhttp://www.mobileware.be//x-tad-smaller smime.p7s Description: S/MIME cryptographic signature
Re: How to upgrade the checkstyle plugin of Maven 1.x to CheckStyle4.0
Lukas, Thanks for your help. I tried downloading the 3.0 plugin, but maven failed to download (though both my project.properties and the command line contained proxy details) C:\Temp\mtestmaven plugin:download -DartifactId=maven-checkstyle-plugin -Dgroup Id=maven -Dversion=3.0-SNAPSHOT - Dmaven.repo.remote=http://cvs.apache.org/reposi tory -Dmaven.proxy.host=proxy.mycomp.com -Dmaven.proxy.port=80 __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 Attempting to download commons-jelly-tags-interaction-1.0.jar. WARNING: Failed to download commons-jelly-tags-interaction-1.0.jar. Attempting to download jdom-b10.jar. WARNING: Failed to download jdom-b10.jar. The build cannot continue because of the following unsatisfied dependencies: commons-jelly-tags-interaction-1.0.jar jdom-b10.jar Any suggestions to overcome this issue? Thanks, Girish On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote: The upcoming checkstyle-plugin-3.0 uses Checkstyle 4.0. A snapshot is available for testing: maven plugin:download -DartifactId=maven-checkstyle-plugin -DgroupId=maven -Dversion=3.0-SNAPSHOT -Dmaven.repo.remote=http://cvs.apache.org/repository -Lukas Girish Nagaraj wrote: Hello, Current checkstyle plugin available with Maven 1.1 beta 2 errors out when the code contains java generics. Checkstyle 4.0 supports generics. Is there a way I can change the plugin or get a new version of the plugin for Maven 1.x so that it uses CheckStyle 4.0? Thanks, Girish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Lukas, Jeff,
It seems to be a very basic problem and in both cases we are hitting the
ListOrderedSet: method init()V not found error.
I could reproduce this problem with both Maven 1.1 beta1 and beta2 with a
very simple project.xml (from the 10 minute test doc) and a simple java file
which has a single javadoc error (missing @param).
I have provided the test project at
http://jira.codehaus.org/browse/MPJAVADOC-61
Hope this gets resolved soon :-)
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to help
diagnose. Your error situation may be different than mine. Our results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated with
Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java file
in
the project.
Just add any java file which contains a javadoc warning (like no @param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on the
console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter name.':
org.apache.commons.collections.set.ListOrderedSet:
method in
it()V not found
and the javadoc warnings report contains just the number of files having
warnings.
Could somebody please suggest how to fix this problem? Is upgrading to
Maven
2 only soln to resolve this problem :( ?
Thanks
Girish
On 11/19/05, Girish Nagaraj [EMAIL PROTECTED] wrote:
Hello,
When I run maven site, the javadoc warnings report fails to get
generated correctly.It just contains the number of files, but does not
list the javadoc problems (though there are many).
The following message shows up on the console
*** WARNING: exception parsing line ' [javadoc] .java:726:
warning
- Tag @inheritDoc cannot be used in constructor documentation. It can
only be used in the following types of documentation: method, inline
text.':
org.apache.commons.collections.set.ListOrderedSet: method init()V
not found
Is there anyway this I can be fix this?
Thanks,
Girish
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building without unit tests
Guy, You can run your maven build like this % mvn -Dmaven.test.skip=true install where the test phase is skipped. Is that of any help? Cheers IV --- Guy Rixon [EMAIL PROTECTED] wrote: Hi, is there some way to build the principal artifact of a project without also running the unit tests? In our development process, running and assessing the unit tests is one stage and building the artifact is a separate stage. When we do the build it saves a lot of time not to have to re-run the tests. One of our projects takes over half an hour to grind through its tests. If this is not current possible, could it be supported in later versions of the appropriate plug-ins? Cheers, Guy Guy Rixon [EMAIL PROTECTED] Institute of AstronomyTel: +44-1223-337542 Madingley Road, Cambridge, UK, CB3 0HAFax: +44-1223-337523 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Great, thanks for finding a simple recipe like this!
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 6:55 AM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with
Maven 1.1 beta1 and beta2
Lukas, Jeff,
It seems to be a very basic problem and in both cases we are hitting the
ListOrderedSet: method init()V not found error.
I could reproduce this problem with both Maven 1.1 beta1 and beta2 with a
very simple project.xml (from the 10 minute test doc) and a simple java file
which has a single javadoc error (missing @param).
I have provided the test project at
http://jira.codehaus.org/browse/MPJAVADOC-61
Hope this gets resolved soon :-)
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to
help diagnose. Your error situation may be different than mine.
Our results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if
nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java
file
in
the project.
Just add any java file which contains a javadoc warning (like no
@param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on
the console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter name.':
org.apache.commons.collections.set.ListOrderedSet:
method in
it()V not found
and the javadoc warnings report contains just the number of files
having warnings.
Could somebody please suggest how to fix this problem? Is upgrading
to
Maven
2 only soln to resolve this problem :( ?
Thanks
Girish
On 11/19/05, Girish Nagaraj [EMAIL PROTECTED] wrote:
Hello,
When I run maven site, the javadoc warnings report fails to get
generated correctly.It just contains the number of files, but does
not list the javadoc problems (though there are many).
The following message shows up on the console
*** WARNING: exception parsing line ' [javadoc] .java:726:
warning
- Tag @inheritDoc cannot be used in constructor documentation. It
can only be used in the following types of documentation: method,
inline
text.':
org.apache.commons.collections.set.ListOrderedSet: method init()V
not found
Is there anyway this I can be fix this?
Thanks,
Girish
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to help
diagnose. Your error situation may be different than mine. Our results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated with
Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java file
in
the project.
Just add any java file which contains a javadoc warning (like no @param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on the
console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter name.':
org.apache.commons.collections.set.ListOrderedSet:
method in
it()V not found
and the javadoc warnings report contains just the number of files having
warnings.
Could somebody please suggest how to fix this problem? Is upgrading to
Maven
2 only soln to resolve this problem :( ?
Thanks
Girish
On 11/19/05, Girish Nagaraj [EMAIL PROTECTED] wrote:
Hello,
When I run maven site, the javadoc warnings report fails to get
generated correctly.It just contains the number of files, but does not
list the javadoc problems (though there are many).
The following message shows up on the console
*** WARNING: exception parsing line ' [javadoc] .java:726:
warning
- Tag @inheritDoc cannot be used in constructor documentation. It can
only be used in the following types of documentation: method, inline
text.':
org.apache.commons.collections.set.ListOrderedSet: method init()V
not found
Is there anyway this I can be fix this?
Thanks,
Girish
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to upgrade the checkstyle plugin of Maven 1.x to CheckStyle4.0
For non-snapshot dependencies, you also have to include the main ibiblio reopository in the repo arg: maven plugin:download -DartifactId=maven-checkstyle-plugin -DgroupId=maven -Dversion=3.0-SNAPSHOT -Dmaven.repo.remote=http://cvs.apache.org/repository,http://www.ibiblio.org/maven HTH, -Lukas Girish Nagaraj wrote: Lukas, Thanks for your help. I tried downloading the 3.0 plugin, but maven failed to download (though both my project.properties and the command line contained proxy details) C:\Temp\mtestmaven plugin:download -DartifactId=maven-checkstyle-plugin -Dgroup Id=maven -Dversion=3.0-SNAPSHOT - Dmaven.repo.remote=http://cvs.apache.org/reposi tory -Dmaven.proxy.host=proxy.mycomp.com -Dmaven.proxy.port=80 __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 Attempting to download commons-jelly-tags-interaction-1.0.jar. WARNING: Failed to download commons-jelly-tags-interaction-1.0.jar. Attempting to download jdom-b10.jar. WARNING: Failed to download jdom-b10.jar. The build cannot continue because of the following unsatisfied dependencies: commons-jelly-tags-interaction-1.0.jar jdom-b10.jar Any suggestions to overcome this issue? Thanks, Girish On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote: The upcoming checkstyle-plugin-3.0 uses Checkstyle 4.0. A snapshot is available for testing: maven plugin:download -DartifactId=maven-checkstyle-plugin -DgroupId=maven -Dversion=3.0-SNAPSHOT -Dmaven.repo.remote=http://cvs.apache.org/repository -Lukas Girish Nagaraj wrote: Hello, Current checkstyle plugin available with Maven 1.1 beta 2 errors out when the code contains java generics. Checkstyle 4.0 supports generics. Is there a way I can change the plugin or get a new version of the plugin for Maven 1.x so that it uses CheckStyle 4.0? Thanks, Girish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0
Check out the ibiblio.org repository for a look at the differences between how the repositories are set up. You are familiar with maven 1, so ibiblio for maven 2 is just in the directory /maven2 instead. project.properties do not exist in Maven 2. All definition is done in the project.xml, or sometimes settings.xml. More information is on http://maven.apache.org/ On 12/9/05, Deepika.M [EMAIL PROTECTED] wrote: Hi all, I know little bit about Maven1.x regarding how a repository gets created and how cache get created(dependency jars) Now I want to know about Mavne 2.0 . I am unable to differenciate between Maven 1.x and 2.x regarding repository creation. I want the difference between two versions of maven regarding repository creation along with simple example if possible. How do Mavne 2.0 uses properties with out project.proerties file Where should I mention goals with out maven.xml file Thank for kenny for previous reply Deepika.S - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Repository question - plz help!
in the same line with stephen, you can settup mirror in your settings.xml
mirrors
mirror
idyour-repo/id
namemaven-proxy/name
urlhttp://your-internal-rep/url
mirrorOfcentral/mirrorOf
/mirror
mirror
idyour-plugin-repo/id
namemaven-proxy/name
urlhttp://your-internal-repo/url
mirrorOfcentral-plugins/mirrorOf
/mirror
/mirrors
The main idea here is to route to default repos to your own internal repos
-Dan
On 12/9/05, Stephen Duncan [EMAIL PROTECTED] wrote:
I think if you define your internal repository with an id of central
it will replace the default external repository. If you also don't
want Maven's plugins to be downloaded externally, you'll need to
define a pluginRepository too, and I don't know if the id would still
be central.
-Stephen
On 12/9/05, Vernik, Gary [EMAIL PROTECTED] wrote:
Dan,
Thank you for your reply! I am still struggling with repositories.
Do I understand correctly that there are 2 possible scenarios:
1. Use Maven in off-line mode. Then only local repository will be used
and if artifact is not there then build fails.
2. Regular (not off-line) mode. Then local repository can receive
artifacts from internal (pre-configured) repositories as well as from
central repository.
If I am right then here is my problem. I would like to make sure that
artifacts can be received from internal repository only (nothing comes
of external sources). So on the one hand I do need to be able to use
internal repositories, on the other hand I don't want to be getting
anything from external sources. Is that feasible?
Thanks,
Gary Vernik
Member of Technical Staff
System Management Software
Network Appliance
408-822-3120
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 07, 2005 3:29 PM
To: Maven Users List
Subject: Re: [m2] Repository question - plz help!
On 12/7/05, Vernik, Gary [EMAIL PROTECTED] wrote:
Dan,
First of, thank you for a prompt reply!
Second, I couldn't figure how to post my reply to the
mailing list. I
am using this archive (
http://www.mail-archive.com/users@maven.apache.org/msg30199.html) and
it only shows reply to Dan)...
Now to your message:
- Checkin all your dependencies to SCM using maven format.
Exactly what I was planning.
Then mirror it to a web server ( use a cron to regularly update the
webserver).
Then specify the web server as one of your repo.
This seems to be overly complicated and I am pretty sure
that it won't
fly by the build team. They are using ant and make and probably not
looking into making their life more complicated.
Sorry, i thought you are using maven at your comp.
Understood that it is tough to move to new modernizied build
system when you have every thing in place.
And if one day, you can convince your team, maven repo is
safe to use
;-),
then you dont need the SCM for your dependencies any more.
It is not that I don't trust you but you are
over-simplifying the problem.
public maven repo has a tiny subset of dependencies we will
end up using.
1. Not all open source libraries are part of maven repo.
2. We will be buying 3rd party libraries and they need to be stored
into SCM anyways.
3. All builds needs to be 100% reproducible from scratch at
any point
of time (including 10 years from now). Thus we need a total control
which can be achieved thru SCM only.
1. You can request to upload missing OS libraries maven repo.
2. I place i all my private thirdparty libraries in my
internal maven repo.
3. If internal maven repo is protected ( itself is a SCM for
binary artifacts), i dont see any reason, maven can not
repoduce the build.
Sorry I am just optimistic ;-)
My further investigation showed that I can do
either
urlfile://.\repo/url
or
urlfile://${basedir}/repo/url Do you see any
problems with
that? Any other suggestions?
yes, but i seems that you will have a repo for each maven project?
BTW, when I am installing 3rd party's library into my local
repo with
install:install-file, is there a way to generate md5
checksum for it?
I think the lastest maven-install-plugin may have that, you
now can deploy file as well using deploy:deploy-file
otherwise, open a JIRA for it.
There is also some work at maven-scm to store and retreive
artfifacts from SCM. You may want to tune in for this project.
Dan, again, I greatly appreciate your attention!!
Thanks,
*Gary Vernik*
*Member of Technical Staff*
*System Management Software*
*Network Appliance*
*408-822-3120*
-
To
[Idea-plugin]
I ran maven idea:multiproject at the root of my multiproject structure, and when I opened the project in IDEA, I got an error message saying the core module was corrupted. Then I deleted the corresponding module file (all the other modules are fine) and ran idea:module in this specific module subdirectory. Then there was a build error with the following message : File.. C:\Documents and Settings\daneel\.maven\cache\maven- idea-plugin-1.6\p lugin.jelly Element... j:import Line.. 78 Column 79 file:/C:/Documents and Settings/daneel/.maven/cache/maven-idea-plugin-1.6 /plugin -resources/templates/v4/module.jelly:41:106: maven:makeRelativePath You must d efine an attribute called 'path' for this tag. Total time: 5 seconds Finished at: Sat Dec 10 19:24:42 CET 2005 Is it a known bug in idea plugin ? -- Sébastien Arbogast Blog : http://www.sebastien-arbogast.com The Epseelon Project : http://www.epseelon.org Projet Phénix : http://phenix.netbios.fr Lens : http://www.squidoo.com/useful-computers/
Groovy depedency problem?
I'm in the process of converting my project (HiveMind) from an Ant build to Maven 2.0. We have a compile-time dependency on Groovy. I've tried the following: dependency groupIdgroovy/groupId artifactIdgroovy-all/artifactId version1.0-jsr-03/version scopecompile/scope /dependency But get the following error: bash-3.00$ mvn install [INFO] Scanning for projects... [INFO] [INFO] Building HiveMind Standard Library [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-03/groovy-all-1.0-jsr-03.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-03/groovy-all-1.0-jsr-03.jar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: groovy ArtifactId: groovy-all Version: 1.0-jsr-03 Reason: Unable to download the artifact from any repository groovy:groovy-all:1.0-jsr-03:jar from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Sat Dec 10 10:23:29 PST 2005 [INFO] Final Memory: 3M/6M [INFO] bash-3.00$ I can see that the files are there, though I don't understand the maven 2 repository layout: http://www.ibiblio.org/maven2/groovy/groovy-all-1.0-jsr/03/ Thanks! -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Lukas,
Sorry, beta 3 doesn't solve it for me. I could not bootstrap build (see
error below), but did a use maven to build maven.
I also:
- cleared out my local repo so all plugins were re-downloaded
- tried it with and without a javadoc-1.8-SNAPSHOT dependency
I may have found a clue, if not the culprit, though. I think it crashes
while trying to parse this entry in the report.txt file:
[javadoc]
C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\va
ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag @link:
reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator.
[javadoc] PremiumCreatorStrategyCredit
Note that the FQCL wraps to the next line. Perhaps this is the parse
error?? Can it handle that in your sandbox?
Bootstrap error:
[exec] [delete] Deleting directory
C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\temp
latesTest\target
[exec] BUILD FAILED
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable to
obtain goal [plugin:test] -- file:/C:/Documents and
Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT/plugin.jelly:
499:34: maven:maven Unable to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trunk/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject
failure occurred
[snip]
[exec] Root cause
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable to
obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trunk/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject
failure occurred
[exec] at org.apache.maven.werkz.Goal.fire(Goal.java:663)
I would prefer nightly build snapshots, but I don't think Maven does that
nor could I find any...
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 10:37 AM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with
Maven 1.1 beta1 and beta2
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to
help diagnose. Your error situation may be different than mine. Our
results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if
nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java
file
in
the project.
Just add any java file which contains a javadoc warning (like no
@param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on the
console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter name.':
org.apache.commons.collections.set.ListOrderedSet:
method in
it()V not found
and the javadoc warnings report contains just the number of files
having warnings.
Could somebody please suggest how to fix this problem? Is upgrading
to
Maven
2 only soln to resolve this problem :( ?
Thanks
Girish
On 11/19/05, Girish Nagaraj [EMAIL PROTECTED] wrote:
Hello,
When I run maven site, the javadoc warnings report fails to get
generated correctly.It just contains the number of files, but does
not list the javadoc problems (though there are many).
The following message shows up on the console
*** WARNING: exception parsing line ' [javadoc] .java:726:
warning
- Tag @inheritDoc cannot be used in constructor documentation. It
can only be used in the following types of documentation: method,
inline
text.':
org.apache.commons.collections.set.ListOrderedSet: method init()V
not found
Is there anyway this I can be fix this?
Thanks,
Girish
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To
Re: Groovy depedency problem?
Things suddenly clicked for me: dependency groupIdgroovy/groupId artifactIdgroovy-all-1.0-jsr/artifactId version03/version scopecompile/scope /dependency On 12/10/05, Howard Lewis Ship [EMAIL PROTECTED] wrote: I'm in the process of converting my project (HiveMind) from an Ant build to Maven 2.0. We have a compile-time dependency on Groovy. I've tried the following: dependency groupIdgroovy/groupId artifactIdgroovy-all/artifactId version1.0-jsr-03/version scopecompile/scope /dependency But get the following error: bash-3.00$ mvn install [INFO] Scanning for projects... [INFO] [INFO] Building HiveMind Standard Library [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-03/groovy-all-1.0-jsr-03.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-03/groovy-all-1.0-jsr-03.jar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: groovy ArtifactId: groovy-all Version: 1.0-jsr-03 Reason: Unable to download the artifact from any repository groovy:groovy-all:1.0-jsr-03:jar from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Sat Dec 10 10:23:29 PST 2005 [INFO] Final Memory: 3M/6M [INFO] bash-3.00$ I can see that the files are there, though I don't understand the maven 2 repository layout: http://www.ibiblio.org/maven2/groovy/groovy-all-1.0-jsr/03/ Thanks! -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 xdoclet Null Pointer Exception
Hello,
i'm new to m2 and i want to move a little project with xdoclet for
hibernate mapping from ant to maven 2.
I'm not sure if i'm on the right way.. I've added to the generated pom
following :
plugin
groupIdxdoclet/groupId
artifactIdmaven-xdoclet-plugin/artifactId
version1.2/version
dependencies
dependency
groupIdxdoclet/groupId
artifactIdxjavadoc/artifactId
version1.1-j5-v4/version
/dependency
/dependencies
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
hibernatedoclet
destdir=${basedir}/src
fileset
dir=${basedir}/src/main/java/myproject/model
includes=**/*.java/
hibernate
version=3.0/
/hibernatedoclet
/tasks
/configuration
/execution
/executions
/plugin
Question : With this i get following error in a mvn compile:
[DEBUG] maven-resources-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-resour
ces-plugin:maven-plugin:2.0
[DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-compil
er-plugin:maven-plugin:2.0
[INFO]
-
---
[ERROR] FATAL ERROR
[INFO]
-
---
[INFO] null
[INFO]
-
---
[DEBUG] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM
anager.java:292)
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De
faultPluginManager.java:198)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug
inManager.java:163)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
ultLifecycleExecutor.java:1095)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifec
ycle(DefaultLifecycleExecutor.java:1060)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl
eMappings(DefaultLifecycleExecutor.java:869)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Hi all,
Girish, I'm sorry, I didn't see your first mail.
The error org.apache.commons.collections.set.ListOrderedSet: method
init()V not found comes from an incompability between two commons
collections releases :
http://jakarta.apache.org/commons/collections/compatibility.html
As we share the classloader between the core and the plugins we had some
issues due to this incompability.
I cleaned up all our dependencies and it should fix this problem.
I'll upload a SNAPSHOT of maven beta 3 in some hours.
For the bootstrap problem, can you send me the log or open an issue please.
Arnaud
On 12/10/05, Jeff Jensen [EMAIL PROTECTED] wrote:
Lukas,
Sorry, beta 3 doesn't solve it for me. I could not bootstrap build (see
error below), but did a use maven to build maven.
I also:
- cleared out my local repo so all plugins were re-downloaded
- tried it with and without a javadoc-1.8-SNAPSHOT dependency
I may have found a clue, if not the culprit, though. I think it crashes
while trying to parse this entry in the report.txt file:
[javadoc]
C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\state\va
ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag @link:
reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator.
[javadoc] PremiumCreatorStrategyCredit
Note that the FQCL wraps to the next line. Perhaps this is the parse
error?? Can it handle that in your sandbox?
Bootstrap error:
[exec] [delete] Deleting directory
C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-test\temp
latesTest\target
[exec] BUILD FAILED
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable to
obtain goal [plugin:test] -- file:/C:/Documents and
Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT
/plugin.jelly:
499:34: maven:maven Unable to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trunk/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject
failure occurred
[snip]
[exec] Root cause
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable to
obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trunk/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject
failure occurred
[exec] at org.apache.maven.werkz.Goal.fire(Goal.java:663)
I would prefer nightly build snapshots, but I don't think Maven does that
nor could I find any...
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 10:37 AM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated
with
Maven 1.1 beta1 and beta2
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to
help diagnose. Your error situation may be different than mine. Our
results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if
nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java
file
in
the project.
Just add any java file which contains a javadoc warning (like no
@param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on the
console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter name.':
org.apache.commons.collections.set.ListOrderedSet:
method in
it()V not found
and the javadoc warnings report contains just the number of files
having warnings.
Could somebody please suggest how to fix this problem? Is upgrading
to
Maven
2 only soln to resolve this problem :( ?
Thanks
Girish
On 11/19/05, Girish Nagaraj [EMAIL PROTECTED] wrote:
Hello,
When I run maven site, the javadoc
Re: Building without unit tests
Hi, In Maven2, this is done by configuring the surefire plugin: build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration testFailureIgnoretrue/testFailureIgnore /configuration /plugin /plugins /pluginManagement /build Hope it helps. -- Arnaud Bailly - Ingénieur de Recherche NORSYS 1, rue de la Cense des Raines ZAC du Moulin 59710 ENNEVELIN Tel : (33) 3 28 76 56 76 Fax : (33) 3 28 76 57 00 Web : http://www.norsys.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Ant Task: How to reference other dependencies?
I'd like to specify only one master list of dependencies for several targets in my build.xml. I'm creating a webapp, so there's a place for compile, test, runtime and provided scopes. The problem I seem to face is that I have to specify useScope on a per-dependency list basis. So, there's no way for my compile task to reference the master dependency list for useScope=compile, and for my file copy tasks to reference the *same* master dependency list for useScope=runtime, and for my test tasks to do the same for useScope=test. However, I could be misunderstanding it all. In any case, I don't want to specify multiple lists, because that ends up increasing he maintenance workload and the possibility of introducing errors. I mean, I suppose I could do it, but I'd like to find a way so that each list has mutually-exclusive dependencies in it. (Hmmm...maybe I should just try it). Part of the problem is how to avoid including all the transitive dependencies' out-of-scope items? Is there any way for me to say: artifact:dependencies pathId=list1 remoteRepository refid=km.repository/ remoteRepository refid=main.repository/ dependency groupId=javax.activation artifactId=activation version=1.0.2 scope=runtime/ dependency groupId=commons-beanutils artifactId=commons- beanutils-core version=1.7.0 scope=compile/ /artifact:dependencies artifact:dependencies pathId=list2 include stuff in list 1/ include stuff in list 1 for useScope=foo/ /artifact:dependencies Thanks! -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Hi Arnaud,
Thank you for looking at this.
This issue has the log attachment:
http://jira.codehaus.org/browse/MAVEN-1733
Looking forward to trying the latest build!
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 3:04 PM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with
Maven 1.1 beta1 and beta2
Hi all,
Girish, I'm sorry, I didn't see your first mail.
The error org.apache.commons.collections.set.ListOrderedSet: method
init()V not found comes from an incompability between two commons
collections releases :
http://jakarta.apache.org/commons/collections/compatibility.html
As we share the classloader between the core and the plugins we had some
issues due to this incompability.
I cleaned up all our dependencies and it should fix this problem.
I'll upload a SNAPSHOT of maven beta 3 in some hours.
For the bootstrap problem, can you send me the log or open an issue please.
Arnaud
On 12/10/05, Jeff Jensen [EMAIL PROTECTED] wrote:
Lukas,
Sorry, beta 3 doesn't solve it for me. I could not bootstrap build
(see error below), but did a use maven to build maven.
I also:
- cleared out my local repo so all plugins were re-downloaded
- tried it with and without a javadoc-1.8-SNAPSHOT dependency
I may have found a clue, if not the culprit, though. I think it
crashes while trying to parse this entry in the report.txt file:
[javadoc]
C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\st
ate\va
ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag @link:
reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator.
[javadoc] PremiumCreatorStrategyCredit
Note that the FQCL wraps to the next line. Perhaps this is the parse
error?? Can it handle that in your sandbox?
Bootstrap error:
[exec] [delete] Deleting directory
C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-tes
t\temp
latesTest\target
[exec] BUILD FAILED
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable
to obtain goal [plugin:test] -- file:/C:/Documents and
Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT
/plugin.jelly:
499:34: maven:maven Unable to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trun
k/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor
subproject failure occurred
[snip]
[exec] Root cause
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable
to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trun
k/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor
subproject failure occurred
[exec] at org.apache.maven.werkz.Goal.fire(Goal.java:663)
I would prefer nightly build snapshots, but I don't think Maven does
that nor could I find any...
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 10:37 AM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to
help diagnose. Your error situation may be different than mine.
Our results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if
nobody
cares
about the javadoc warnings report of if I am the only using the report.
I am still seeing this problem even with a very simple single java
file
in
the project.
Just add any java file which contains a javadoc warning (like no
@param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr Some error
*/
public MyTest(String foo, String bar)
{
}
}
Maven javadoc can be seen error out with the following warning on
the console
*** WARNING: exception parsing line ' [javadoc]
C:\Temp\mtest\src\main\java\ora
cle\mds\persistence\MyTest.java:20: warning - @param argument oldAttr
is
not a parameter
Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
thanks.
You can download a snapshot of maven 1.1 beta 3 (zip archive only) here :
http://people.apache.org/~aheritier/maven/1.X/snapshots/
Arnaud
On 12/11/05, Jeff Jensen [EMAIL PROTECTED] wrote:
Hi Arnaud,
Thank you for looking at this.
This issue has the log attachment:
http://jira.codehaus.org/browse/MAVEN-1733
Looking forward to trying the latest build!
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 3:04 PM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated
with
Maven 1.1 beta1 and beta2
Hi all,
Girish, I'm sorry, I didn't see your first mail.
The error org.apache.commons.collections.set.ListOrderedSet: method
init()V not found comes from an incompability between two commons
collections releases :
http://jakarta.apache.org/commons/collections/compatibility.html
As we share the classloader between the core and the plugins we had some
issues due to this incompability.
I cleaned up all our dependencies and it should fix this problem.
I'll upload a SNAPSHOT of maven beta 3 in some hours.
For the bootstrap problem, can you send me the log or open an issue
please.
Arnaud
On 12/10/05, Jeff Jensen [EMAIL PROTECTED] wrote:
Lukas,
Sorry, beta 3 doesn't solve it for me. I could not bootstrap build
(see error below), but did a use maven to build maven.
I also:
- cleared out my local repo so all plugins were re-downloaded
- tried it with and without a javadoc-1.8-SNAPSHOT dependency
I may have found a clue, if not the culprit, though. I think it
crashes while trying to parse this entry in the report.txt file:
[javadoc]
C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\st
ate\va
ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag
@link:
reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator.
[javadoc] PremiumCreatorStrategyCredit
Note that the FQCL wraps to the next line. Perhaps this is the parse
error?? Can it handle that in your sandbox?
Bootstrap error:
[exec] [delete] Deleting directory
C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-tes
t\temp
latesTest\target
[exec] BUILD FAILED
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable
to obtain goal [plugin:test] -- file:/C:/Documents and
Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT
/plugin.jelly:
499:34: maven:maven Unable to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trun
k/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor
subproject failure occurred
[snip]
[exec] Root cause
[exec] org.apache.maven.werkz.UnattainableGoalException: Unable
to obtain goal [testPlugin] --
file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/trun
k/gena
pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor
subproject failure occurred
[exec] at org.apache.maven.werkz.Goal.fire(Goal.java:663)
I would prefer nightly build snapshots, but I don't think Maven does
that nor could I find any...
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 10:37 AM
To: Maven Users List
Subject: Re: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to
investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVADOC-61
Does it apply to your situation? If so, please add your details to
help diagnose. Your error situation may be different than mine.
Our results
are
the same though, an empty report.
-Original Message-
From: Girish Nagaraj [mailto:[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 5:07 AM
To: users@maven.apache.org
Subject: [m1] Re: Javadoc warnings report is not getting generated
with Maven 1.1 beta1 and beta2
Hello All,
Unfortunately I did not get any response to my email. Wonder if
nobody
cares
about the javadoc warnings report of if I am the only using the
report.
I am still seeing this problem even with a very simple single java
file
in
the project.
Just add any java file which contains a javadoc warning (like no
@param
or
something like that) public class MyTest {
/**
** Constructor.
** @param oldAttr
Maven 2 xdoclet Null Pointer Exception
Hello, i'm new to m2 and i want to move a little project with xdoclet for hibernate mapping from ant to maven 2. I'm not sure if i'm on the right way.. I've added to the generated pom following : build plugins plugin groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version executions execution phasegenerate-sources/phase goals goalxdoclet/goal /goals configuration tasks !-- here i think must be the hibernatedoclet : -- /tasks /configuration /execution /executions /plugin /plugins /build Question 1: With this i get following error in a mvn compile: [DEBUG] maven-resources-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-resour ces-plugin:maven-plugin:2.0 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compil er-plugin:maven-plugin:2.0 [INFO] - --- [ERROR] FATAL ERROR [INFO] - --- [INFO] null [INFO] - --- [DEBUG] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM anager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De faultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug inManager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa ultLifecycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifec ycle(DefaultLifecycleExecutor.java:1060) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl eMappings(DefaultLifecycleExecutor.java:869) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] - Question 2: Are the paramters for hibernatedoclet like the hibernatedoclet -ant-task? Hope that sounds not too stupid, but in my web researches i got nothing what this explain.. Uli - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven2 plugin suggestions
Thanks for all the replies. I actually got most of what I wanted from the jar and assembly plugin. I configured the following in my pom.xml: ... build ... plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/main/assembly/bin.xml/descriptor /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassnet.sf.toolinstaller.ui.cli.Main/mainClass packageNamenet.sf.toolinstaller/packageName addClasspathtrue/addClasspath /manifest /archive /configuration /plugin ... /build ... The jar plugin generates the manifest so that the classpath is generated and the mainclass is specified. This means that my run script merely contains: java.exe -jar ../lib/toolinstaller-0.2-SNAPSHOT.jar %* The only thing missing here is automatic substitution of the version in the jar filename - but I can handle doing that manually for now. Then, I've configured the assembly plugin with src/main/assembly/bin.xml which copies the required artifacts into the assembled artifact for distribution. Awesome - great work from the maven developers. If you want to look at the full pom.xml and src/main/assembly/bin.xml files have a look at my files in the CVS repository: http://cvs.sourceforge.net/viewcvs.py/toolinstaller/toolinstaller/ I wonder if it would be a good idea to enable substitutions when the assembly plugin copies resources. Thanks again, Paul. --- Paul Rule [EMAIL PROTECTED] wrote: I often write stand alone apps, and I've often thought it would be good to have a plugin to bundle up a build complete with all the dependent jars, scripts, config files etc - and to even generate the run.bat run.sh scripts. Is there anything like this currently (I talking maven2) - if I wrote it would anyone else find it useful? Also, would anyone find a plugin that generated the java service wrapper configuration useful? Do you Yahoo!? The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database. http://au.movies.yahoo.com Send instant messages to your online friends http://au.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2
Thanks - the beta 3 snapshot downloaded from your site does not fix the Javadoc parsing problem. I have updated notes here on that: http://jira.codehaus.org/browse/MPJAVADOC-61 -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 5:53 PM To: Maven Users List Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2 thanks. You can download a snapshot of maven 1.1 beta 3 (zip archive only) here : http://people.apache.org/~aheritier/maven/1.X/snapshots/ Arnaud On 12/11/05, Jeff Jensen [EMAIL PROTECTED] wrote: Hi Arnaud, Thank you for looking at this. This issue has the log attachment: http://jira.codehaus.org/browse/MAVEN-1733 Looking forward to trying the latest build! -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 3:04 PM To: Maven Users List Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2 Hi all, Girish, I'm sorry, I didn't see your first mail. The error org.apache.commons.collections.set.ListOrderedSet: method init()V not found comes from an incompability between two commons collections releases : http://jakarta.apache.org/commons/collections/compatibility.html As we share the classloader between the core and the plugins we had some issues due to this incompability. I cleaned up all our dependencies and it should fix this problem. I'll upload a SNAPSHOT of maven beta 3 in some hours. For the bootstrap problem, can you send me the log or open an issue please. Arnaud On 12/10/05, Jeff Jensen [EMAIL PROTECTED] wrote: Lukas, Sorry, beta 3 doesn't solve it for me. I could not bootstrap build (see error below), but did a use maven to build maven. I also: - cleared out my local repo so all plugins were re-downloaded - tried it with and without a javadoc-1.8-SNAPSHOT dependency I may have found a clue, if not the culprit, though. I think it crashes while trying to parse this entry in the report.txt file: [javadoc] C:\devroot\customers\dhs\perforce\healthmatchbatch\main\src\java\us\ st ate\va ntage\hm\batch\ar\policy\premiumcreator\package.html: warning - Tag @link: reference not found: us.state.vantage.hm.batch.ar.policy.premiumcreator. [javadoc] PremiumCreatorStrategyCredit Note that the FQCL wraps to the next line. Perhaps this is the parse error?? Can it handle that in your sandbox? Bootstrap error: [exec] [delete] Deleting directory C:\devroot\reference\maven\maven-1\plugins\trunk\genapp\src\plugin-t es t\temp latesTest\target [exec] BUILD FAILED [exec] org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [plugin:test] -- file:/C:/Documents and Settings/jjensen/.maven/cache/maven-plugin-plugin-1.7-SNAPSHOT /plugin.jelly: 499:34: maven:maven Unable to obtain goal [testPlugin] -- file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/tr un k/gena pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject failure occurred [snip] [exec] Root cause [exec] org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [testPlugin] -- file:/C:/devroot/reference/maven/maven-1/core/trunk/../../plugins/tr un k/gena pp/src/plugin-test/maven.xml:20:127: maven:reactor Reactor subproject failure occurred [exec] at org.apache.maven.werkz.Goal.fire(Goal.java:663) I would prefer nightly build snapshots, but I don't think Maven does that nor could I find any... -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 10:37 AM To: Maven Users List Subject: Re: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2 Hope this gets resolved soon :-) Seems to be resolved already :) - see my comment on JIRA. -Lukas Thanks, Girish On 12/9/05, Lukas Theussl [EMAIL PROTECTED] wrote: If it's not the same issue please open a new one. I am seeing empty javadoc warning reports too, but I haven't had the time to investigate. -Lukas Jeff Jensen wrote: We miss this report for summarizing Javadoc errors. I entered this JIRA on 27/Sep/05: http://jira.codehaus.org/browse/MPJAVADOC-61 Does it apply to your situation? If so, please add your details to help diagnose. Your error situation may be different than mine. Our results are the same though, an empty report. -Original Message- From: Girish Nagaraj [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 5:07 AM To: users@maven.apache.org Subject: [m1] Re: Javadoc warnings report is not getting generated with Maven 1.1 beta1 and beta2 Hello All,
AutoSynched Maven Repo for Apache Projects?
Pluto 1.1 is about to be released. For the life of me, I can't seem to find the maven 2 repository for apache projects that is auto-synced to ibiblio. Is there one, or do I need upload the request to jira like everyone else? David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoSynched Maven Repo for Apache Projects?
There is a repo: http://www.apache.org/dist/maven-repository Please follow the rules in README.txt (not visible from the web for some reason). It's not synced yet - but we'll do it manually once its in there. Cheers, Brett On 12/10/05, David H. DeWolf [EMAIL PROTECTED] wrote: Pluto 1.1 is about to be released. For the life of me, I can't seem to find the maven 2 repository for apache projects that is auto-synced to ibiblio. Is there one, or do I need upload the request to jira like everyone else? David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions on assembly plugin
Henry Isidro wrote: You can override them by creating an assembly descriptor and placing bin or src in the id tag. I see that I can specify *one* such descriptor via the plugins descriptor property. But what, if I want to override both? Haven't tried this yet, but you can use executions to assemble a bin then an src. What are executions? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions on assembly plugin
you can run maven-assembly-plugin multiple times ... build ... plugins plugin artifactIdmaven-assembly-plugin/artifactId executions execution phasepackage/phase configuration ... /configuration goals goalassembly/goal /goals /execution execution phasepackage/phase configuration... /configuration goals goalassembly/goal /goals /execution /executions /plugin /plugins /build *Conclusion* On 12/10/05, Jochen Wiedmann [EMAIL PROTECTED] wrote: Henry Isidro wrote: You can override them by creating an assembly descriptor and placing bin or src in the id tag. I see that I can specify *one* such descriptor via the plugins descriptor property. But what, if I want to override both? Haven't tried this yet, but you can use executions to assemble a bin then an src. What are executions? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions on assembly plugin
dan tran wrote: you can run maven-assembly-plugin multiple times Thanks for the hint. I may be doing something wrong, but so far it doesn't work. Here's what I did: - Added the executions section to the assembly plugins configuration. - Removed my existing configuration section. - Invoked mvn assembly:assembly Result is the following error message: POM Location: /home/jwi/workspace/ws-xmlrpc-2/pom.xml Validation Messages: [0] You cannot have two plugin executions with the same (or missing) id/ elements. Offending execution Id: 'default' Plugin:'org.apache.maven.plugins:maven-assembly-plugin' Reason: Failed to validate POM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Questions on assembly plugin
Hi you need to add an idsomeId/id inside the execution element. different for each execution. Regards Mark Donszelmann -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Saturday, December 10, 2005 7:38 PM To: Maven Users List Subject: Re: Questions on assembly plugin dan tran wrote: you can run maven-assembly-plugin multiple times Thanks for the hint. I may be doing something wrong, but so far it doesn't work. Here's what I did: - Added the executions section to the assembly plugins configuration. - Removed my existing configuration section. - Invoked mvn assembly:assembly Result is the following error message: POM Location: /home/jwi/workspace/ws-xmlrpc-2/pom.xml Validation Messages: [0] You cannot have two plugin executions with the same (or missing) id/ elements. Offending execution Id: 'default' Plugin:'org.apache.maven.plugins:maven-assembly-plugin' Reason: Failed to validate POM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Questions on assembly plugin
If you assigned an id to each that is different it will be ok. - Brett On 12/10/05, Jochen Wiedmann [EMAIL PROTECTED] wrote: dan tran wrote: you can run maven-assembly-plugin multiple times Thanks for the hint. I may be doing something wrong, but so far it doesn't work. Here's what I did: - Added the executions section to the assembly plugins configuration. - Removed my existing configuration section. - Invoked mvn assembly:assembly Result is the following error message: POM Location: /home/jwi/workspace/ws-xmlrpc-2/pom.xml Validation Messages: [0] You cannot have two plugin executions with the same (or missing) id/ elements. Offending execution Id: 'default' Plugin:'org.apache.maven.plugins:maven-assembly-plugin' Reason: Failed to validate POM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 1.x Repository on Ibiblio remapped
In the interests of simplifying maintenance of the Maven 1.x and Maven 2.x repositories, I have setup ibiblio to map all requests from http://www.ibiblio.org/maven to http://www.ibiblio.org/maven2 If you are experiencing any difficulties, please let us know. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
