helper mojo to add additional source root - where should it be?
Hi folks, Many times, I encounter user asking for a mojo to add additional source root to their pom at run time. This mojo is quite simple as we all agree. Does it make sense that maven-project-helper-plugin supports this feature? If not, what would be a logical plugin name to house this mojo? project-helper-maven-plugin to be at mojo.codehaus.org. ? -Dan
[jira] Closed: (MRM-33) add based on existing indexer for jar classes, packages and filenames
[ http://jira.codehaus.org/browse/MRM-33?page=all ] Edwin Punzalan closed MRM-33: - Resolution: Fixed > add based on existing indexer for jar classes, packages and filenames > - > > Key: MRM-33 > URL: http://jira.codehaus.org/browse/MRM-33 > Project: Maven Repository Manager > Type: Sub-task > Components: indexing > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 18 hours >Time Spent: 14 hours > Remaining: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Thu Dec 22 06:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051222.063000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.063000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MSITE-58) Ability to assign a report to choosen navigation menu
[ http://jira.codehaus.org/browse/MSITE-58?page=comments#action_54004 ] Brett Porter commented on MSITE-58: --- http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence see "Including Generated Content" > Ability to assign a report to choosen navigation menu > -- > > Key: MSITE-58 > URL: http://jira.codehaus.org/browse/MSITE-58 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Michal Maczka > Priority: Minor > Fix For: 2.0 > > > It will be nice to have a possibiliy of deciding per report basis where (in > which menu) given report will appear in the left side navigation instead of > putting all reports into one bag (reports menu). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Thu Dec 22 06:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.060001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MSITE-48) add reusable skin functionality and create skins default, stylus and classic
[ http://jira.codehaus.org/browse/MSITE-48?page=comments#action_54001 ] Brett Porter commented on MSITE-48: --- http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence > add reusable skin functionality and create skins default, stylus and classic > > > Key: MSITE-48 > URL: http://jira.codehaus.org/browse/MSITE-48 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0 > > Original Estimate: 4 hours > Remaining: 4 hours > > add the classic theme from m1, and perhaps a derivative of the new theme for > other sites -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-48) add reusable skin functionality and create skins default, stylus and classic
[ http://jira.codehaus.org/browse/MSITE-48?page=all ] Brett Porter updated MSITE-48: -- Assign To: Brett Porter Remaining Estimate: 4 hours Original Estimate: 4 hours Summary: add reusable skin functionality and create skins default, stylus and classic (was: add other themes) > add reusable skin functionality and create skins default, stylus and classic > > > Key: MSITE-48 > URL: http://jira.codehaus.org/browse/MSITE-48 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0 > > Original Estimate: 4 hours > Remaining: 4 hours > > add the classic theme from m1, and perhaps a derivative of the new theme for > other sites -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Thu Dec 22 05:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.053000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Thu Dec 22 05:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051222.051500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051222.051500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site aggregation (Relocating discussion from confluence to dev)
Hi John, Having discussed this, I agree. So site will remain as a [EMAIL PROTECTED] and the respective reports can do this later. - Brett John Allen wrote: > Re discussion regarding site aggregation > > See: http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence for > previous notes. > > > Hi Brett, > > Re your last comments: > > 'The copy is done from the top level so it can run as an aggregator and the > subprojects can be viewed as a single site and deployed as one. However, I > see that if any of the subprojects have a different URL this won't work, so > it may need to be reconsidered.' > > Although I see the need for a parent project site generation to access and > parse its child projects files to build various composite and aggregate > reports (such as javadoc or the various code analysis tools) I do not see > why this would require copies of the child project's site files themselves. > In fact thinking about it I would expect the composite report generation to > use the 'raw' data files and not the HTML report prepared versions of those > files (i.e. process the surefire XML output or the checkstyle XML output). > > In terms of deployment I do not think we should be breaking the project > independence by trying to deploy child sites via the parent site for the > various reasons I have already described: namely that a child's site > deployment details are not related to the deployment details of its parent, > and therefore all child and parent HTML HREF linking must be via > project.URLs and not filesystem relative locations. > > I am not sure of the real meaning of an @aggregator Mojo (despite hunting > for details on maven.apache.org) so maybe I'm missing some magic here but > the way I see it is that all a child's generated artefacts, including its > site files, are independent of its parent's generated assets in terms of > their addressing and deployment semantics. The child relationship is only > one of build order and POM inheritance, not artefact dependency. > > I will raise a JIRA regarding the fact that project.getParent() returns an > un-interpolated project. > > Cheers, > > John > > > - > 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]
[jira] Commented: (MAVEN-1623) copyResources does not preservelastmodified
[ http://jira.codehaus.org/browse/MAVEN-1623?page=comments#action_54000 ] Laird Nelson commented on MAVEN-1623: - For those who care, here is a port of the copyResources tag in jelly with the added setPreserveLastModified() call thrown in there. Stand back. You'll need to set a jelly variable named "todir" to the destination directory name. Cheers, Laird ([EMAIL PROTECTED]) > copyResources does not preservelastmodified > --- > > Key: MAVEN-1623 > URL: http://jira.codehaus.org/browse/MAVEN-1623 > Project: Maven > Type: Bug > Environment: maven-1.0rc3 > Reporter: Matthias Kerkhoff > Priority: Minor > Fix For: 1.1-beta-3 > > > I noticed that whenever files are copied with the help of maven:copyResources > the lastModified time is updated. > This happens because the underlying ant copyTask is not > called with preserveLastModified=true. > (org.apache.maven.jelly.tags.maven.CopyResources, lines 109-137) > While this is only annoying for me, I can easily imagine situations in which > this behaviour will cause real problems. > For example, commercial software often checks the last > modified timestamp of some files. > Actually, I digged into this because I tried to understand why some ears and > rars in our project are constantly rebuild - even if we didn't change > anything between the builds. So, fixing this (or adding an additional > parameter to the tag) may also result in a performance gain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Thu Dec 22 05:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.05.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 New sandbox plugin - dependency-maven-plugin
dont think we have jarjar yet!!! but on the second thought, this plugin + assembly together can create jarjar. -D On 12/21/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Isn't there a jarjar plugin to do that already? > > -Original Message- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 21, 2005 6:48 PM > To: Maven Developers List > Subject: Re: M2 New sandbox plugin - dependency-maven-plugin > > We should be able to enhance this plugin to provisde jarjar functionality > with no transtive dependency. > > -D > > > On 12/21/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > I want to announce a new plugin in the mojo sandbox: > > http://mojo.codehaus.org/dependency-maven-plugin/introduction.html > > > > This plugin can copy artifacts from the repository into a desired > > location and currently operates separately from the normal > dependancies. > > (perfect for things you need but don't want on the classpath) It can > > get the artifacts from the local or remote repositories and > > understands the dependancyManagement section. It can explode those > artifacts if desired. > > The plugin is currently in alpha state, hence the sandbox, but has > > been used in production by team and possibly a few others. > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[maven2 build trunk - FAILED - update] Thu Dec 22 04:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.043000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: M2 New sandbox plugin - dependency-maven-plugin
Isn't there a jarjar plugin to do that already? -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 21, 2005 6:48 PM To: Maven Developers List Subject: Re: M2 New sandbox plugin - dependency-maven-plugin We should be able to enhance this plugin to provide jarjar functionality with no transtive dependency. -D On 12/21/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Hi all, > I want to announce a new plugin in the mojo sandbox: > http://mojo.codehaus.org/dependency-maven-plugin/introduction.html > > This plugin can copy artifacts from the repository into a desired > location and currently operates separately from the normal dependancies. > (perfect for things you need but don't want on the classpath) It can > get the artifacts from the local or remote repositories and > understands the dependancyManagement section. It can explode those artifacts if desired. > The plugin is currently in alpha state, hence the sandbox, but has > been used in production by team and possibly a few others. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: M2 New sandbox plugin - dependency-maven-plugin
Dan, I'm not able to deploy the site...I wonder if it's because the folder has you as owner? -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 21, 2005 6:48 PM To: Maven Developers List Subject: Re: M2 New sandbox plugin - dependency-maven-plugin We should be able to enhance this plugin to provide jarjar functionality with no transtive dependency. -D On 12/21/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Hi all, > I want to announce a new plugin in the mojo sandbox: > http://mojo.codehaus.org/dependency-maven-plugin/introduction.html > > This plugin can copy artifacts from the repository into a desired > location and currently operates separately from the normal dependancies. > (perfect for things you need but don't want on the classpath) It can > get the artifacts from the local or remote repositories and > understands the dependancyManagement section. It can explode those artifacts if desired. > The plugin is currently in alpha state, hence the sandbox, but has > been used in production by team and possibly a few others. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Thu Dec 22 04:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.04.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Thu Dec 22 03:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051222.031502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051222.031502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Thu Dec 22 03:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.03.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - checkout] Thu Dec 22 01:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051222.013000.txt
[jira] Subscription: Outstanding Repository Maintenance: Uploads
Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (2 issues) Subscriber: mavendevlist Key Summary MAVENUPLOAD-645Jini Service Archetype version 2.0 http://jira.codehaus.org/browse/MAVENUPLOAD-645 MAVENUPLOAD-644Maven Jini Plug-in version 2.0 http://jira.codehaus.org/browse/MAVENUPLOAD-644 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Evangelism
Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (18 issues) Subscriber: mavendevlist Key Summary MEV-255 Problem with junit-addons 1.4 http://jira.codehaus.org/browse/MEV-255 MEV-220 spring-mock should list spring-web and spring-jdbc as optional http://jira.codehaus.org/browse/MEV-220 MEV-126 poms for som emissing sun xml API + javamail 1.3.3 http://jira.codehaus.org/browse/MEV-126 MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype http://jira.codehaus.org/browse/MEV-201 MEV-173 xmlpull JARs exist in two different places on ibiblio http://jira.codehaus.org/browse/MEV-173 MEV-175 spring-1.2.pom invalid http://jira.codehaus.org/browse/MEV-175 MEV-2 Broken dependency for groovy http://jira.codehaus.org/browse/MEV-2 MEV-163 Groovy pom has invalid dependencies http://jira.codehaus.org/browse/MEV-163 MEV-161 acegisecurity lacks dependency for oro and commons-codec http://jira.codehaus.org/browse/MEV-161 MEV-4 Misnamed pom for Postgresql http://jira.codehaus.org/browse/MEV-4 MEV-96 Some jars in ibiblio repository are broken http://jira.codehaus.org/browse/MEV-96 MEV-48 openejb poms http://jira.codehaus.org/browse/MEV-48 MEV-45 Full list of poms that doesn't respect the m2 format http://jira.codehaus.org/browse/MEV-45 MEV-38 POM for commons-jelly-tags-ant has incorrect artifact & references bogus dependency http://jira.codehaus.org/browse/MEV-38 MEV-36 Exo POM(s) missing dependency versions http://jira.codehaus.org/browse/MEV-36 MEV-33 XOM POM references xercesImpl v.2.2.1 which does not exist in repo http://jira.codehaus.org/browse/MEV-33 MEV-31 XOM POM references xmlParserAPIs v2.6.1 which is not in the repo http://jira.codehaus.org/browse/MEV-31 MEV-20 clean up bad IDs in the repository http://jira.codehaus.org/browse/MEV-20 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - checkout] Thu Dec 22 00:30:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051222.003001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051222.003001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - checkout] Thu Dec 22 00:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051222.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051222.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 New sandbox plugin - dependency-maven-plugin
We should be able to enhance this plugin to provide jarjar functionality with no transtive dependency. -D On 12/21/05, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Hi all, > I want to announce a new plugin in the mojo sandbox: > http://mojo.codehaus.org/dependency-maven-plugin/introduction.html > > This plugin can copy artifacts from the repository into a desired > location and currently operates separately from the normal dependancies. > (perfect for things you need but don't want on the classpath) It can get > the artifacts from the local or remote repositories and understands the > dependancyManagement section. It can explode those artifacts if desired. > The plugin is currently in alpha state, hence the sandbox, but has been > used in production by team and possibly a few others. > >
M2 New sandbox plugin - dependency-maven-plugin
Hi all, I want to announce a new plugin in the mojo sandbox: http://mojo.codehaus.org/dependency-maven-plugin/introduction.html This plugin can copy artifacts from the repository into a desired location and currently operates separately from the normal dependancies. (perfect for things you need but don't want on the classpath) It can get the artifacts from the local or remote repositories and understands the dependancyManagement section. It can explode those artifacts if desired. The plugin is currently in alpha state, hence the sandbox, but has been used in production by team and possibly a few others.
Re: Questions about report plugins
Only know the javadoc plugin does it and the only differnce I can find that clover has a @execute and the javadoc hasn't. So giving up for tonight (need some sleep :) and will try a bit more tomorrow. But any pointers would certainly be a big help.. Mvgr, Martin Vincent Massol wrote: Hi there, I have 2 questions about report plugins (I'm working on the clover plugin): * m2 fails on multiprojects because I'm setting a read-only MavenProject field in my mojo. The error message is "Cannot override read-only parameter: project in goal: clover:instrument". Is that to be expected or a bug? * Is it possible for a report plugin to prevent the generation of a menu report item upon a certain condition (like when sources do not exist for example)? I'm trying to look for a plugin doing this but I haven't found so far... for example if the project is of type pom, I want the report not to be executed. How would I specify this? Please don't tell me to generate an empty report! This would be a degraded solution... :-) Thanks -Vincent - 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]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Wed Dec 21 22:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051221.221501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.221501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Wed Dec 21 22:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051221.22.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.22.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 21:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.214500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 21:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.213001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r358293 - /maven/plugins/trunk/maven-clover-plugin/src/site/site.xml
We don't need to rush to do this on all plugins. It will be inherited shortly. - Brett [EMAIL PROTECTED] wrote: > Author: vmassol > Date: Wed Dec 21 05:48:54 2005 > New Revision: 358293 > > URL: http://svn.apache.org/viewcvs?rev=358293&view=rev > Log: > add publish date format > > Modified: > maven/plugins/trunk/maven-clover-plugin/src/site/site.xml > > Modified: maven/plugins/trunk/maven-clover-plugin/src/site/site.xml > URL: > http://svn.apache.org/viewcvs/maven/plugins/trunk/maven-clover-plugin/src/site/site.xml?rev=358293&r1=358292&r2=358293&view=diff > == > --- maven/plugins/trunk/maven-clover-plugin/src/site/site.xml (original) > +++ maven/plugins/trunk/maven-clover-plugin/src/site/site.xml Wed Dec 21 > 05:48:54 2005 > @@ -27,6 +27,7 @@ > > http://maven.apache.org/images/maven-small.gif > > + > > >http://maven.apache.org/maven2/"/> > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 21:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.211500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Dec 21 21:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051221.21.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051221.21.txt
[maven2 build trunk - FAILED - update] Wed Dec 21 21:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.210001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 20:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.204501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Dec 21 20:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051221.203000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051221.203000.txt
[maven2 build trunk - FAILED - update] Wed Dec 21 20:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.203000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1886) Need way to share code between report mojos and main build mojos
Need way to share code between report mojos and main build mojos Key: MNG-1886 URL: http://jira.codehaus.org/browse/MNG-1886 Project: Maven 2 Type: Improvement Components: Plugin API Versions: 2.0.1 Reporter: Vincent Massol For example in the clover plugin i have both report mojos and main build mojos. They need to share lots of configuration elements and common methods but it's not easy to do so because each type needs to extend either AbstractMavenReport or AbstractMojo. Of course I could not extend AbstractMavenReport and instead implement the interface but then I'll have to reimplement all its methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 20:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.201500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 20:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.20.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 19:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.194501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 19:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.193000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 19:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.191501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 19:00:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.190001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1885) Uniquely identify modules by module name and version number
Uniquely identify modules by module name and version number --- Key: MNG-1885 URL: http://jira.codehaus.org/browse/MNG-1885 Project: Maven 2 Type: Improvement Components: design Environment: This is a platform independent issue. Windows XP, Java builds Reporter: John Reynolds Attachments: codetree.doc Currently when buiding project dependencies and/or performing a build via the reactor "-r option" it will not build projects that have the same project id. This works in most unique project scenarios, but in scenarios where you may have the directories for a project broken out by version number, you end up with the same artifact-id for the multiple projects. The only difference would be that they are target at different versions. Example Layout Project X | +--Dev (pom.xml contains artifact "ProjectX" version Dev (Dev head contains latest release) | +--1.0 (pom.xml contains artifact "ProjectX" Version 1.0 | +--2.0 (pom.xml contains artifact "ProjectX" Version 2.0 We may actually build multiple versions of plug-ins that could be deployed and built as a whole. It would simplify the builds if the "-r" option would build each project and version it finds. Today it will only build one of them. The same issue or set of problems is presented to the module concept. It's difficult for a parent project that needs to build multiple projects to point at specific versions. Today they project would require a unique artifact and a module pointing to each directory for the pom. It will only build one of the instances of the artifact ID. This forces changes to the parent pom, to deal with the issue. It would be nice to be able to build a specific version or all the versions related to a module. Multi-Project module builds should have the knowledge of versions when deciding what to build, with an option of including specific versions or all versions of an artifactId The "-r" reactor option should all directories to be recursed and build multiple projects of the same artifact id, regardless over version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Questions about report plugins
Hi there, I have 2 questions about report plugins (I'm working on the clover plugin): * m2 fails on multiprojects because I'm setting a read-only MavenProject field in my mojo. The error message is "Cannot override read-only parameter: project in goal: clover:instrument". Is that to be expected or a bug? * Is it possible for a report plugin to prevent the generation of a menu report item upon a certain condition (like when sources do not exist for example)? I'm trying to look for a plugin doing this but I haven't found so far... for example if the project is of type pom, I want the report not to be executed. How would I specify this? Please don't tell me to generate an empty report! This would be a degraded solution... :-) Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCLOVER-13) Check artifact language
[ http://jira.codehaus.org/browse/MCLOVER-13?page=all ]
Vincent Massol closed MCLOVER-13:
-
Assign To: Vincent Massol
Resolution: Fixed
Applied thanks.
> Check artifact language
> ---
>
> Key: MCLOVER-13
> URL: http://jira.codehaus.org/browse/MCLOVER-13
> Project: Maven 2.x Clover Plugin
> Type: Improvement
> Versions: 2.0-alpha-1
> Reporter: Mario Van Steenberghe
> Assignee: Vincent Massol
> Priority: Minor
> Fix For: 2.0
>
>
> Would it be possible to add an artifact language verification before
> executing your mojos ? This was done in the javadoc plug-in and seems to work
> great.
> In a multi-project build, this allows you to specify the reports for all
> sub-projects at parent level. The generation of the clover report will be
> excluded, since it is not defined as a 'java' artifact.
> ---
> public void executeReport( Locale locale ) throws MavenReportException {
> ArtifactHandler artifactHandler =
> project.getArtifact().getArtifactHandler();
> if ( !"java".equals( artifactHandler.getLanguage() ) ) {
> getLog().info( "Not executing Clover as the project is not a Java
> classpath-capable package" );
> return;
> }
>
> }
> -
> This could be included in both CloverReportMojo and CloverInstrumentMojo.
> Regards,
> Mario.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 18:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.184500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 18:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.183000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCLOVER-14) Do not execute instrumentation if no sources are present
[ http://jira.codehaus.org/browse/MCLOVER-14?page=all ] Vincent Massol closed MCLOVER-14: - Resolution: Fixed Done > Do not execute instrumentation if no sources are present > > > Key: MCLOVER-14 > URL: http://jira.codehaus.org/browse/MCLOVER-14 > Project: Maven 2.x Clover Plugin > Type: Improvement > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > > For example the clover plugin should not try to instrument sources for pom > projects and more generally for any project that has no sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MCLOVER-14) Do not execute instrumentation if no sources are present
Do not execute instrumentation if no sources are present Key: MCLOVER-14 URL: http://jira.codehaus.org/browse/MCLOVER-14 Project: Maven 2.x Clover Plugin Type: Improvement Versions: 2.0-alpha-1 Reporter: Vincent Massol Assigned to: Vincent Massol Fix For: 2.0 For example the clover plugin should not try to instrument sources for pom projects and more generally for any project that has no sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 18:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.181501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 18:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.18.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53968 ] Eugene Kuleshov commented on MNGECLIPSE-15: --- Let's try to look at this from a different angle. why would you need these resources anyways? I can only think that they could be needed to run unit tests. However wWhen you run these tests from Maven resources already taken from the right folders. So, we may just add some support for JUnit runner within Eclipse that will use right resource folders when needed. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MWAR-20) tag doesn't work during aggregated build.
[ http://jira.codehaus.org/browse/MWAR-20?page=all ] Lukas Theussl moved MPWAR-54 to MWAR-20: Key: MWAR-20 (was: MPWAR-54) Project: Maven 2.x War Plugin (was: maven-war-plugin) > tag doesn't work during aggregated build. > --- > > Key: MWAR-20 > URL: http://jira.codehaus.org/browse/MWAR-20 > Project: Maven 2.x War Plugin > Type: Bug > Reporter: David Boden > > > When building parent aggregator, subprojects tag uses the wrong > base directory (perhaps the base directory of the parent?) to search for the > specified web.xml. > > SalesStation > SSBuild > SNAPSHOT > ../SSBuild/pom.xml > > 4.0.0 > SalesStation > SS > war > SNAPSHOT > SalesStation SS webapp > > > WEB-INF/src > SS > > > org.apache.maven.plugins > maven-war-plugin > > . > target/** > > ../SS/WEB-INF/maven-web.xml > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 17:45:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.174501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPWAR-54) tag doesn't work during aggregated build.
tag doesn't work during aggregated build. --- Key: MPWAR-54 URL: http://jira.codehaus.org/browse/MPWAR-54 Project: maven-war-plugin Type: Bug Reporter: David Boden When building parent aggregator, subprojects tag uses the wrong base directory (perhaps the base directory of the parent?) to search for the specified web.xml. SalesStation SSBuild SNAPSHOT ../SSBuild/pom.xml 4.0.0 SalesStation SS war SNAPSHOT SalesStation SS webapp WEB-INF/src SS org.apache.maven.plugins maven-war-plugin . target/** ../SS/WEB-INF/maven-web.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 17:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.173000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJIRA-16) Add Michael Franken to list of contributors
[ http://jira.codehaus.org/browse/MPJIRA-16?page=all ] Lukas Theussl closed MPJIRA-16: --- Resolution: Fixed Fix Version: (was: 1.2) 1.3 I'm sorry Michael but version 1.2 was released a few weeks ago. I have added you as a contributor and republished the plugin site. Thanks a lot for all your contributions! > Add Michael Franken to list of contributors > --- > > Key: MPJIRA-16 > URL: http://jira.codehaus.org/browse/MPJIRA-16 > Project: maven-jira-plugin > Type: Wish > Versions: 1.2 > Reporter: Michael Franken > Priority: Minor > Fix For: 1.3 > > > I've contributed the major part of the documentation and the implementation > of v1.2 Please add me as contributor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 17:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.171500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPMD-9) Link violations to Xref
[ http://jira.codehaus.org/browse/MPMD-9?page=all ] Lukas Theussl moved MPPMD-22 to MPMD-9: --- Key: MPMD-9 (was: MPPMD-22) Project: Maven 2.x Pmd Plugin (was: maven-pmd-plugin) > Link violations to Xref > --- > > Key: MPMD-9 > URL: http://jira.codehaus.org/browse/MPMD-9 > Project: Maven 2.x Pmd Plugin > Type: Improvement > Reporter: Nick Giles > Priority: Minor > Attachments: MPPMD-22.patch > > > The violations should link to their location in the source xref, as happened > in Maven 1. I'll attach a patch for this that does a simple but hopefully > sufficient job. It's based on the latest SCM code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-646) jTDS
[ http://jira.codehaus.org/browse/MAVENUPLOAD-646?page=all ] Micah Schehl closed MAVENUPLOAD-646: Resolution: Incomplete > jTDS > > > Key: MAVENUPLOAD-646 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-646 > Project: maven-upload-requests > Type: Task > Reporter: Micah Schehl > > > http://jtds.sourceforge.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-646) jTDS
jTDS Key: MAVENUPLOAD-646 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-646 Project: maven-upload-requests Type: Task Reporter: Micah Schehl http://jtds.sourceforge.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53966 ] YOKOTA Takehiko commented on MNGECLIPSE-15: --- Sorry, I noticed that the example was wrong. What I meant was I didn't want to gather resources of all *subprojects* into single output folder. As you said, main resource and test resource will gather into the same classpath at certain subproject, but I think that some resources of subproject-A and independent subproject-B's one should not be gathered into single classpath. How about this? So I'd like to separate output folders per subproject, but currently I have no idea for realize this. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 17:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.17.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-524) editing mail notifier during a build
editing mail notifier during a build Key: CONTINUUM-524 URL: http://jira.codehaus.org/browse/CONTINUUM-524 Project: Continuum Type: Bug Components: Mail Notifier Versions: 1.0.2 Environment: W2K, sp4, 1.7 GHz, 1 GB RAM Reporter: Michael Fiedler Priority: Minor While editing the mail notifier entry, but not every time, an exception would occur. When I did get an exception, it is similar to this: jvm 1| 2005-12-20 13:03:34,253 [Thread-1] WARN SQL - Object with id "1069" not found ! jvm 1| 2005-12-20 13:03:34,503 [Thread-1] WARN SQL - Object with id "1069" not found ! jvm 1| 2005-12-20 13:03:34,643 [Thread-1] ERROR BuildController - Error while building project. jvm 1| javax.jdo.JDODataStoreException: Put request failed : INSERT INTO PROJECTNOTIFIER_CONFIGURATION (STRING_VAL,ID_OID,STRING_KEY) VALUES (?,?,?) jvm 1| at org.jpox.store.rdbms.scostore.NormalMapStore.put(NormalMapStore.java:467) jvm 1| at org.jpox.sco.Map.put(Map.java:709) jvm 1| at org.jpox.sco.SCOUtils.updateMapWithMapKeysValues(SCOUtils.java:626) jvm 1| at org.jpox.sco.Map.attachCopy(Map.java:376) jvm 1| at org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) jvm 1| at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) jvm 1| at org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideField(ProjectNotifier.java) jvm 1| at org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideFields(ProjectNotifier.java) jvm 1| at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) jvm 1| at org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) jvm 1| at org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) jvm 1| at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) jvm 1| at org.jpox.sco.List.attachCopy(List.java:326) jvm 1| at org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) jvm 1| at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) jvm 1| at org.apache.maven.continuum.model.project.Project.jdoProvideField(Project.java) jvm 1| at org.apache.maven.continuum.model.project.Project.jdoProvideFields(Project.java) jvm 1| at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) jvm 1| at org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) jvm 1| at org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) jvm 1| at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) jvm 1| at org.jpox.sco.List.attachCopy(List.java:326) jvm 1| at org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) jvm 1| at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) jvm 1| at org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideField(ProjectGroup.java) jvm 1| at org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideFields(ProjectGroup.java) jvm 1| at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) jvm 1| at org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) jvm 1| at org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) jvm 1| at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) jvm 1| at org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:120) jvm 1| at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) jvm 1| at org.apache.maven.continuum.model.project.Project.jdoProvideField(Project.java) jvm 1| at org.apache.maven.continuum.model.project.Project.jdoProvideFields(Project.java) jvm 1| at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) jvm 1| at org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) jvm 1| at org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) jvm 1| at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) jvm 1| at org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1660) jvm 1| at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoContinuumStore.java:679) jvm 1| at org.apache.maven.continuum.store.JdoContinuumStore.updateProject(JdoContinuumStore.java
[jira] Resolved: (SCM-115) log files should not show clear text password for perforce repository access
[ http://jira.codehaus.org/browse/SCM-115?page=all ] mike perham resolved SCM-115: - Assign To: mike perham Resolution: Fixed Fix Version: 1.0-beta-3 > log files should not show clear text password for perforce repository access > > > Key: SCM-115 > URL: http://jira.codehaus.org/browse/SCM-115 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0-beta-2 > Reporter: Mark Richters > Assignee: mike perham > Fix For: 1.0-beta-3 > Attachments: password.patch.txt > > > logs/wrapper.log contains entries like this: > [Thread-1] DEBUG ScmManager - Executing p4 -u mr -P > mypassword -cmyclient sync ... > It should not show mypassword in clear text (see also CONTINUUM-394). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPPMD-22) Link violations to Xref
[ http://jira.codehaus.org/browse/MPPMD-22?page=all ] Nick Giles updated MPPMD-22: Attachment: MPPMD-22.patch > Link violations to Xref > --- > > Key: MPPMD-22 > URL: http://jira.codehaus.org/browse/MPPMD-22 > Project: maven-pmd-plugin > Type: Improvement > Reporter: Nick Giles > Priority: Minor > Attachments: MPPMD-22.patch > > > The violations should link to their location in the source xref, as happened > in Maven 1. I'll attach a patch for this that does a simple but hopefully > sufficient job. It's based on the latest SCM code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-523) mail notifier adding during a build
mail notifier adding during a build --- Key: CONTINUUM-523 URL: http://jira.codehaus.org/browse/CONTINUUM-523 Project: Continuum Type: Bug Components: Mail Notifier Versions: 1.0.2 Environment: W2K, sp4, 1.7 GHz, 1GB Reporter: Michael Fiedler Priority: Minor When adding mail notifiers, they are being persisted with all options on even though I explicitly unchecked the success option. Even when I later edit the entry and re-uncheck them, they eventually become checked again. This stopped happening when I knew the build completed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPPMD-22) Link violations to Xref
Link violations to Xref --- Key: MPPMD-22 URL: http://jira.codehaus.org/browse/MPPMD-22 Project: maven-pmd-plugin Type: Improvement Reporter: Nick Giles Priority: Minor The violations should link to their location in the source xref, as happened in Maven 1. I'll attach a patch for this that does a simple but hopefully sufficient job. It's based on the latest SCM code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 16:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.164500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 16:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.163001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 16:15:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.161501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 16:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.160001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MCHECKSTYLE-24) Jdk14logger exception
Jdk14logger exception - Key: MCHECKSTYLE-24 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-24 Project: Maven 2.x Checkstyle Plugin Type: Bug Environment: Maven 2.0.1, checkstyle plugin 2.0-beta-1, JDK5, Win2000 Reporter: darren hartford Assigned to: Jason van Zyl Priority: Blocker Attachments: checkstyletrace.txt Problem with checkstyle plugin when used with 'site' - see attached trace. 'mvn checkstyle:checkstyle' works fine. Also reference http://jira.codehaus.org/browse/MCHECKSTYLE-10 as may be similar issue/fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MCOMPILER-22) Compilation fails: "The command line is too long."
[ http://jira.codehaus.org/browse/MCOMPILER-22?page=comments#action_53959 ] Matthew Beermann commented on MCOMPILER-22: --- Addendum: I had true attached to the compiler; removing that seemed to fix the issue. This may be related to a more general problem with forking and command-line-too-long that I saw mentioned in the mailing list. > Compilation fails: "The command line is too long." > -- > > Key: MCOMPILER-22 > URL: http://jira.codehaus.org/browse/MCOMPILER-22 > Project: Maven 2.x Compiler Plugin > Type: Bug > Reporter: Matthew Beermann > Assignee: Jason van Zyl > Priority: Critical > > > For one of my project, compilation fails with the message "The command line > is too long". As far as I can tell, it's listing each and every source file, > one at a time, in the -sourcepath attribute. (?!?) Here's the log: > [DEBUG] Source roots: > [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src > [DEBUG] Command line options: > [DEBUG] -d > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > -classpath -sourcepath SOURCE FILES HERE> -g -nowarn -target 1.4 -source 1.4 > Compiling 167 source files to > C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > Failure executing javac, but could not parse the error: > The command line is too long. > [INFO] > > [DEBUG] Trace > org.apache.maven.BuildFailureException: Compilation failure > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > 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(DelegatingMethodAccessorImpl.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) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation > failure > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 15:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.154500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-202) dependency wrong
[ http://jira.codehaus.org/browse/MEV-202?page=all ] Carlos Sanchez closed MEV-202: -- Assign To: Carlos Sanchez Resolution: Won't Fix > dependency wrong > > > Key: MEV-202 > URL: http://jira.codehaus.org/browse/MEV-202 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Adam Hardy > Assignee: Carlos Sanchez > > > javax.xml.namespace doesn't exist on ibiblio > and > javax.xml.xsdlib is xsdlib.xsdlib -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-157) Invalid deps in the dumbster pom
[ http://jira.codehaus.org/browse/MEV-157?page=all ] Carlos Sanchez closed MEV-157: -- Assign To: Carlos Sanchez (was: Edwin Punzalan) Resolution: Fixed Added relocations > Invalid deps in the dumbster pom > - > > Key: MEV-157 > URL: http://jira.codehaus.org/browse/MEV-157 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Matt Todd > Assignee: Carlos Sanchez > > > > > activation > activation > 1.0.2 > > > javamail > mail > 1.3.2 > > > Should be: > > > javax.activation > activation > 1.0.2 > > > javax.mail > mail > 1.3.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPMD-2) pmd has problems with package-info.java.
[ http://jira.codehaus.org/browse/MPMD-2?page=comments#action_53954 ]
darren hartford commented on MPMD-2:
verify issue with package-info.java. Critical for EJB3-type projects.
Sample package-info.java:
=
@javax.persistence.NamedQueries(
{
@javax.persistence.NamedQuery(
name="findAllTable",
queryString="SELECT tbl FROM Table tbl"
),
@javax.persistence.NamedQuery(
name="findAllTable2",
queryString="SELECT tbl FROM Table2 tbl"
)
}
)
package my.package.ejb3;
===
verified against 2.0-alpha-2 release.
> pmd has problems with package-info.java.
>
>
> Key: MPMD-2
> URL: http://jira.codehaus.org/browse/MPMD-2
> Project: Maven 2.x Pmd Plugin
> Type: Bug
> Environment: Ubuntu 5.10
> Reporter: Bernd Bohmann
> Priority: Minor
> Attachments: PmdReport.java.patch
>
>
> pmd has problems with package-info.java. Please exclude package-info.java
> from report.
> package-info.java can be used in place of package.html (which supports only
> comments, not annotations)
> Please update to pmd version 3.3
> Embedded error: Failure executing PMD for:
> myfaces/tobago/taglib/component/package-info.java
> Encountered "package" at line 27, column 1.
> Was expecting one of:
> "class" ...
> "final" ...
> "interface" ...
> ...
> "@" ...
> "public" ...
> "static" ...
> "protected" ...
> "private" ...
> "abstract" ...
> "synchronized" ...
> "native" ...
> "transient" ...
> "volatile" ...
> "strictfp" ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] maven-war-plugin next release
Ah, but don't forget to include http://jira.codehaus.org/browse/MNG-1790 first! -- Eric On Wed, 2005-12-21 at 08:17, Jurgen Lust wrote: > Hi, > > Any idea when there will be a new release (2.0-beta-3) of the > maven-war-plugin? > There are a couple of very nice features in the latest snapshot which I > need, mainly this: > http://jira.codehaus.org/browse/MNG-1507 > > Kind regards, > > Jurgen > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Dec 21 15:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051221.153000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051221.153000.txt
[jira] Closed: (MEV-217) Relocate springframework
[ http://jira.codehaus.org/browse/MEV-217?page=all ] Carlos Sanchez closed MEV-217: -- Assign To: Carlos Sanchez (was: Edwin Punzalan) Resolution: Fixed This is already fixed > Relocate springframework > > > Key: MEV-217 > URL: http://jira.codehaus.org/browse/MEV-217 > Project: Maven Evangelism > Type: Improvement > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > > > Relocate springframework 1.2.5 and 1.2.6 to org.springframework -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-221) transitive dependencies not being picked up
[ http://jira.codehaus.org/browse/MEV-221?page=all ] Carlos Sanchez closed MEV-221: -- Resolution: Cannot Reproduce > transitive dependencies not being picked up > --- > > Key: MEV-221 > URL: http://jira.codehaus.org/browse/MEV-221 > Project: Maven Evangelism > Type: Bug > Reporter: Ryan Sonnek > Assignee: Carlos Sanchez > > > According to the POM for spring-hibernate-1.2.5, the spring-dao and > spring-beans packages should be picked up by transitive dependencies. I can > not compile my application without explicitly adding these to my POM in > addition to spring-hibernate. > > org.springframework > spring-beans > 1.2.5 > > > org.springframework > spring-dao > 1.2.5 > > > javax.transaction > jta > > > > > org.springframework > spring-hibernate > 1.2.5 > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 15:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.153000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-223) commons-email-1.0.pom bad dependencies
[ http://jira.codehaus.org/browse/MEV-223?page=all ] Carlos Sanchez closed MEV-223: -- Assign To: Carlos Sanchez Resolution: Fixed Added relocation poms for javamail and activation May take one day to reach ibiblio > commons-email-1.0.pom bad dependencies > -- > > Key: MEV-223 > URL: http://jira.codehaus.org/browse/MEV-223 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Olivier Lamy > Assignee: Carlos Sanchez > > > The pom has bad dependencies : > > javamail > javamail > 1.3.3 > > > activation > activation > 1.0.2 > > should be : > > javax.mail > mail > 1.3.3 > > > javax.activation > activation > 1.0.2 > > pom's url : > http://www.ibiblio.org/maven2/commons-email/commons-email/1.0/commons-email-1.0.pom > Thanks, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-226) common-collections 2.1 newer than 3.0
[ http://jira.codehaus.org/browse/MEV-226?page=all ] Carlos Sanchez closed MEV-226: -- Assign To: Carlos Sanchez Resolution: Won't Fix Year is not important, maybe you're experiencing MNG-1050 ? > common-collections 2.1 newer than 3.0 > - > > Key: MEV-226 > URL: http://jira.codehaus.org/browse/MEV-226 > Project: Maven Evangelism > Type: Bug > Reporter: denis Cabasson > Assignee: Carlos Sanchez > > > Seems to be something broken in common-collections version. V2.1 is > considered newer than 3.0 (and indeed has a more recent inception year). > This account for some runtime errors in my project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 15:15:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.151502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] maven-war-plugin next release
Hi, Any idea when there will be a new release (2.0-beta-3) of the maven-war-plugin? There are a couple of very nice features in the latest snapshot which I need, mainly this: http://jira.codehaus.org/browse/MNG-1507 Kind regards, Jurgen -- Among flowers, the cherry blossom. Among men, me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1689) Only print relocation warnings in standard output for the current pom
[ http://jira.codehaus.org/browse/MNG-1689?page=all ] Carlos Sanchez closed MNG-1689: --- Resolution: Fixed > Only print relocation warnings in standard output for the current pom > - > > Key: MNG-1689 > URL: http://jira.codehaus.org/browse/MNG-1689 > Project: Maven 2 > Type: Improvement > Components: Logging > Versions: 2.0 > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 2.0.2 > Attachments: MNG-1689-maven-artifact.patch, MNG-1689-maven-project.patch > > > Relocation warnings of transitive dependencies shouldn't be printed in > standard output because people gets confused, ask questions and try to change > other people poms although they work correctly > We should only print the warnings of the current pom so the author can > improve it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (CONTINUUM-401) cannot delete project (stuck on 'in progress')
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=all ] Yann Le Du updated CONTINUUM-401: - Attachment: wrapper-2005-12-21.log > cannot delete project (stuck on 'in progress') > -- > > Key: CONTINUUM-401 > URL: http://jira.codehaus.org/browse/CONTINUUM-401 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: running on linux debian > trying to access from winXP > Reporter: Adam Kiezun > Attachments: palulustuck.JPG, wrapper-2005-11-25.log, wrapper-2005-12-21.log > > > one of my projects got stuck in the 'in progress' state and cannot be deleted > from the web interface. > it's been in this state for > 24 hrs so it seems permanent. > attaching screenshot. > let me know if i should attach a log (and which one) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action
[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53947 ] Eugene Kuleshov commented on MNGECLIPSE-15: --- I am not sure how they can't conflict even when going under separate folders? They will end up in the same classpath anyways. Am I missing something? Another thing is that action "Update Source Folders" intended to free you from worying about what source and target folders should be, as long as you have correct definitions in Maven's POM. we are open for suggestions how to improve it and keep it simple at the same time. > Output folders are not set correctly by 'Update Sources' action > --- > > Key: MNGECLIPSE-15 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Reporter: YOKOTA Takehiko > Assignee: Eugene Kuleshov > > > Although source folders on build path are updated correctly by 'Update > Sources' action, > output folders are not updated at all. > For example, it is expected that output folder for 'src/test/java' and > 'src/test/resources' > is set to 'target/test-classes', but not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1689) Only print relocation warnings in standard output for the current pom
[ http://jira.codehaus.org/browse/MNG-1689?page=all ] Carlos Sanchez updated MNG-1689: Assign To: Carlos Sanchez (was: Edwin Punzalan) Fix Version: (was: 2.0.3) 2.0.2 > Only print relocation warnings in standard output for the current pom > - > > Key: MNG-1689 > URL: http://jira.codehaus.org/browse/MNG-1689 > Project: Maven 2 > Type: Improvement > Components: Logging > Versions: 2.0 > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 2.0.2 > Attachments: MNG-1689-maven-artifact.patch, MNG-1689-maven-project.patch > > > Relocation warnings of transitive dependencies shouldn't be printed in > standard output because people gets confused, ask questions and try to change > other people poms although they work correctly > We should only print the warnings of the current pom so the author can > improve it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1884) settings.xml in home directory/.m2/ doesn't have an effect
[ http://jira.codehaus.org/browse/MNG-1884?page=all ] Eugene Kuleshov updated MNG-1884: - Component: maven-embedder > settings.xml in home directory/.m2/ doesn't have an effect > -- > > Key: MNG-1884 > URL: http://jira.codehaus.org/browse/MNG-1884 > Project: Maven 2 > Type: Bug > Components: maven-embedder > Environment: Windows XP + J2SE 1.5 + Eclipse 3.1.0 > Reporter: Simon Vos > Assignee: Jason van Zyl > > > I have to use a proxy-server to connect to the internet and for that I use a > settings.xml file for maven2 which is configured to use the proxy server and > a local remote server. This remote server is a server in our network which > contains our jars, ejbs, etc. and most of the packages we use to develop our > applications. This all works fine, but the plugin doesn't seem to keep the > settings.xml file into account when trying to retrieve the dependencies. > What I tried was just putting the settings.xml file I use in my home > directory/.m2/, but the plugin doesn't react to that, eventhough it says it's > looking there when I choose to see the debug output.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MNG-1884) settings.xml in home directory/.m2/ doesn't have an effect
[ http://jira.codehaus.org/browse/MNG-1884?page=all ] Eugene Kuleshov moved MNGECLIPSE-16 to MNG-1884: Complexity: Intermediate Workflow: Maven (was: jira) Key: MNG-1884 (was: MNGECLIPSE-16) Project: Maven 2 (was: Maven 2.x Plug-in for Eclipse) > settings.xml in home directory/.m2/ doesn't have an effect > -- > > Key: MNG-1884 > URL: http://jira.codehaus.org/browse/MNG-1884 > Project: Maven 2 > Type: Bug > Components: maven-embedder > Environment: Windows XP + J2SE 1.5 + Eclipse 3.1.0 > Reporter: Simon Vos > Assignee: Eugene Kuleshov > > > I have to use a proxy-server to connect to the internet and for that I use a > settings.xml file for maven2 which is configured to use the proxy server and > a local remote server. This remote server is a server in our network which > contains our jars, ejbs, etc. and most of the packages we use to develop our > applications. This all works fine, but the plugin doesn't seem to keep the > settings.xml file into account when trying to retrieve the dependencies. > What I tried was just putting the settings.xml file I use in my home > directory/.m2/, but the plugin doesn't react to that, eventhough it says it's > looking there when I choose to see the debug output.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-519) scheduler not calling scm's update command at scheduled time
[ http://jira.codehaus.org/browse/CONTINUUM-519?page=all ] Emmanuel Venisse closed CONTINUUM-519: -- Assign To: Emmanuel Venisse Resolution: Fixed Applied. Thanks. > scheduler not calling scm's update command at scheduled time > > > Key: CONTINUUM-519 > URL: http://jira.codehaus.org/browse/CONTINUUM-519 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Environment: xp, starteam > Reporter: Dan Tran > Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-1 > Attachments: CONTINUUM-519.patch > > > The log shows the timer fires correctly but no attempt to call scm's update > command to detect changes > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - < > Continuum 1.0.2 started! > > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >\ ^__^ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > \ (oo)\___ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >(__)\ )\/\ > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >||w | > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - >|| || > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > 4641 [WrapperSimpleAppMain] INFO org.apache.maven.continuum.Continuum - > 4641 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.initialization.ContinuumInitializer - Continuum > initializer running ... > 4985 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Activating > schedules ... > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Mon Dec 19 > 05:00:00 PST 2005 > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Tue Dec 20 > 00:01:00 PST 2005 > 5016 [WrapperSimpleAppMain] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - Thu Jan 01 > 10:15:00 PST 2099 > 5016 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - > Loading on start [role,roleHint]: > [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,build-project] > 5344 [WrapperSimpleAppMain] ERROR > org.codehaus.plexus.velocity.VelocityComponent - > ResourceManager.getResource() parse exception: > org.apache.velocity.exception.ParseErrorException: Lexical error: > org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 121, > column 17. Encountered: after : "" > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - The from mailbox > is not configured, will use the nag email address from the project. > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - From name: > Continuum > 5438 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.notifier.Notifier:mail - Build host name: > uscus-build2 > 5563 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.notification.RecipientSource - To override address is > not configured, will use the nag email address from the project. > 5578 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - > Starting task executor, thread name 'build-project'. > 5578 [WrapperSimpleAppMain] INFO org.codehaus.plexus.PlexusContainer - > Loading on start [role,roleHint]: > [org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,check-out-project] > 5578 [WrapperSimpleAppMain] INFO > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:check-out-project > - Starting task executor, thread name 'check-out-project'. > 2151003 [scheduler1_Worker-8] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - > > Executing build job (DEFAULT_SCHEDULE)... > 2151112 [scheduler1_Worker-8] INFO > org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3 > 5750995 [scheduler1_Worker-7] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - > > Executing build job (DEFAULT_SCHEDULE)... > 5750995 [scheduler1_Worker-7] INFO > org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3 > 9351007 [scheduler1_Worker-13] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - > > Executing build job (DEFAULT_SCHEDULE)... > 9351007 [scheduler1_Worker-13] INFO > org.apache.maven.continuum.store.ContinuumStore:jdo - nb result : 3 > 12950997 [scheduler1_Worker-11] INFO > org.apache.maven.continuum.build.settings.SchedulesActivator - >
[jira] Closed: (MEV-228) dom4j needs xml-apis updated
[ http://jira.codehaus.org/browse/MEV-228?page=all ] Carlos Sanchez closed MEV-228: -- Assign To: Carlos Sanchez Resolution: Won't Fix Warnings are not errors, they will be hidden in next maven versions MNG-1689 > dom4j needs xml-apis updated > > > Key: MEV-228 > URL: http://jira.codehaus.org/browse/MEV-228 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Brian Fox > Assignee: Carlos Sanchez > Attachments: dom4j-1.5.2 > > > Dom4j is dependant on xml-apis:xml-apis:2.0.2 but it should be 1.0.b2. This > seems to be in all the dom4j versions. > See the following url for more info: > http://www.ibiblio.org/maven/xml-apis/jars/README.html > Patch for 1.5.2 will be attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1851) "Duplicate project ID found" message with maven-artifact-ant-2.0.1
[ http://jira.codehaus.org/browse/MNG-1851?page=comments#action_53942 ]
Tomislav Bodor commented on MNG-1851:
-
I *was* looking at trunk. I thought as a bug fix it would make it in there.
Anyway, I checked the maven-2.0.x branch now and I see the change.
Something is still not entirely clear, though: what is the 2.0.2-SNAPSHOT built
from - trunk or that branch (the snapshot I refer to is the one at
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/maven-artifact-ant/2.0.2-SNAPSHOT/maven-artifact-ant-2.0.2-20051220.231658-1-dep.jar)?
I know this is unofficial, but thought it would be useful to test whether this
issue was resolved and to see if I run into any others (at the moment can't get
past the duplicate project ID, so can't tell what else might be broken). So, I
got it and it has the same bahaviour as 2.0.1. Hence the confusion...
> "Duplicate project ID found" message with maven-artifact-ant-2.0.1
> --
>
> Key: MNG-1851
> URL: http://jira.codehaus.org/browse/MNG-1851
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0.1
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.2
>
>
> from the original email:
> I tried upgrading my Maven 2 Ant Tasks' JAR tonight, and after doing
> so, I'm getting the following error:
> foxxy:~/dev/equinox mraible$ ant war
> Buildfile: build.xml
> init:
> [artifact:dependencies] An error has occurred while processing the
> Maven artifact tasks.
> [artifact:dependencies] Diagnosis:
> [artifact:dependencies]
> [artifact:dependencies] Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> [artifact:dependencies] Duplicate project ID found in
> /Users/mraible/Work/equinox/pom.xml
> BUILD FAILED
> /Users/mraible/Work/equinox/build.xml:27: Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> Total time: 2 seconds
> foxxy:~/dev/equinox mraible$
> I haven't been able to find the "duplicate project id" the error is
> referring to. The strange thing is if I run "mvn package" on my
> project, everything works fine with Maven 2.0.1. If I revert my
> maven-artifact-ant-2.0.1-dep.jar to maven-artifact-ant-2.0-dep.jar,
> everything works as expected.
> Here's how I declare the Maven Ant tasks in my build.xml:
>
> uri="urn:maven-artifact-ant">
>
> location="${basedir}/lib/maven-artifact-ant-2.0-dep.jar" />
>
>
>
> Here's line 27 of build.xml:
> filesetId="compile.fileset" useScope="compile">
>
>
> Thanks,
> Matt
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - update] Wed Dec 21 15:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.15.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
