[jira] Commented: (MAVENUPLOAD-2142) Rsync XCluder repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141180#action_141180 ] Manos Batsis commented on MAVENUPLOAD-2142: --- Sorry Carlos, missed that. Here's the info you need: "gr.abiss.xcluder","[EMAIL PROTECTED]:/home/groups/x/xc/xcluder/htdocs/repository/releases","rsync_ssh","Manos Batsis","[EMAIL PROTECTED]",, Many thanks, Manos > Rsync XCluder repo > -- > > Key: MAVENUPLOAD-2142 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2142 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Manos Batsis > Attachments: gr.abiss.xcluder.sh > > > Attached an sh script to rsync the xcluder release repo to maven central. > Thanks! > Manos -- 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: (MAVENUPLOAD-2143) FitNesse and FitLibrary 20080702
FitNesse and FitLibrary 20080702 Key: MAVENUPLOAD-2143 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2143 Project: Maven Upload Requests Issue Type: Wish Reporter: Pål Brattberg FitNesse is a fully integrated standalone wiki and acceptance testing framework using FIT. FitLibrary is an extension for FIT/FitNesse I'm not a developer of FitNesse, but I am for DbFit which is dependant on FitNesse. The official JAR's are found at: http://www.fitnesse.org/FitNesse.DownLoad The JAR's packaged for Maven (with POM) are found at: http://www.palbrattberg.com/wp-content/uploads/2008/07/fitnesse-20080702-bundle.jar http://www.palbrattberg.com/wp-content/uploads/2008/07/fitlibrary-20080702-bundle.jar -- 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: (MAVENUPLOAD-2144) Thinlet GUI toolkit
Thinlet GUI toolkit --- Key: MAVENUPLOAD-2144 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2144 Project: Maven Upload Requests Issue Type: Wish Reporter: Alien Science Thinlet is a lightweight gui toolkit that I think is pretty cool and would like to use it in a maven managed project. Its LGPL licensed and I would be happy to create a POM, convert to a jar and maintain the upload if needed. Many thanks for your consideration. -- 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: (MNG-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141192#action_141192 ] Chris Wewerka commented on MNG-2871: May there be any hope that this very annoying bug will also be fixed in 2.0.x version of maven? > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, > MNG-2871-core-integration-testing-2.diff, > MNG-2871-core-integration-tests.diff, > MNG-2871-maven-project-2.1-SNAPSHOT.diff, MNG-2871-maven-project.diff, > root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > --
[jira] Created: (MDOCCK-13) Set user agent for URL verifications
Set user agent for URL verifications
Key: MDOCCK-13
URL: http://jira.codehaus.org/browse/MDOCCK-13
Project: Maven 2.x Documentation Checker Plugin
Issue Type: Improvement
Affects Versions: 1.0-beta-2
Reporter: Benjamin Bentmann
Priority: Minor
Running the plugin on the JDepend Plugin from Mojo causes a false alarm:
{noformat}
o JDepend Maven Plugin (1 error, 0 warnings)
[ERROR] Cannot reach license 'BSD' with URL:
'http://www.clarkware.com/software/license.txt'.
{noformat}
The URL is fine. After some telnet sessions, it appears the server is blocking
the request (with code 412) just because of the user agent header field which
is currently "Jakarta Commons-HttpClient/3.0.1". That seems like a good reason
to tell the server, who is really knocking on its door.
--
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] Closed: (MDOCCK-13) Set user agent for URL verifications
[
http://jira.codehaus.org/browse/MDOCCK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MDOCCK-13.
---
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.0-beta-3
Fixed in [r675162|http://svn.apache.org/viewvc?view=rev&revision=675162] by
setting UA to "Apache Maven/2.0 (Maven Documentation Checker Plugin)".
> Set user agent for URL verifications
>
>
> Key: MDOCCK-13
> URL: http://jira.codehaus.org/browse/MDOCCK-13
> Project: Maven 2.x Documentation Checker Plugin
> Issue Type: Improvement
>Affects Versions: 1.0-beta-2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.0-beta-3
>
>
> Running the plugin on the JDepend Plugin from Mojo causes a false alarm:
> {noformat}
> o JDepend Maven Plugin (1 error, 0 warnings)
> [ERROR] Cannot reach license 'BSD' with URL:
> 'http://www.clarkware.com/software/license.txt'.
> {noformat}
> The URL is fine. After some telnet sessions, it appears the server is
> blocking the request (with code 412) just because of the user agent header
> field which is currently "Jakarta Commons-HttpClient/3.0.1". That seems like
> a good reason to tell the server, who is really knocking on its door.
--
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: (MDOCCK-12) @Override let QDOX fail for this plugin
[ http://jira.codehaus.org/browse/MDOCCK-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MDOCCK-12: Attachment: MDOCCK-12.zip Sample project. > @Override let QDOX fail for this plugin > --- > > Key: MDOCCK-12 > URL: http://jira.codehaus.org/browse/MDOCCK-12 > Project: Maven 2.x Documentation Checker Plugin > Issue Type: Bug >Affects Versions: 1.0-beta-2 > Environment: Win XP >Reporter: MTStorm >Priority: Minor > Attachments: MDOCCK-12.zip > > > The plugin fails when QDox hit @Override. Here is the stacktrace: > [INFO] Trace > com.thoughtworks.qdox.parser.ParseException: syntax error @[33,5] in ...my > java file > at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) > at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) > at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) > at > com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) > at > com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) > at > org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) > at > org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) > at > org.apache.maven.plugin.docck.CheckPluginDocumentationMojo.checkPackagingSpecificDocumentation(CheckPluginDocumentationMojo.java:67) > at > org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.checkProject(AbstractCheckDocumentationMojo.java:319) > at > org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.execute(AbstractCheckDocumentationMojo.java:149) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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) > [INFO] > > [INFO] Total time: 12 seconds > [INFO] Finished at: Wed Jun 04 10:40:35 CEST 2008 > [INFO] Final Memory: 10M/19M > [INFO] > --
[jira] Closed: (MDOCCK-12) @Override let QDOX fail for this plugin
[ http://jira.codehaus.org/browse/MDOCCK-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MDOCCK-12. --- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.0-beta-3 Fixed in [r675222|http://svn.apache.org/viewvc?view=rev&revision=675222] by using QDOX 1.6.3 which contains the required parser fixes. > @Override let QDOX fail for this plugin > --- > > Key: MDOCCK-12 > URL: http://jira.codehaus.org/browse/MDOCCK-12 > Project: Maven 2.x Documentation Checker Plugin > Issue Type: Bug >Affects Versions: 1.0-beta-2 > Environment: Win XP >Reporter: MTStorm >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.0-beta-3 > > Attachments: MDOCCK-12.zip > > > The plugin fails when QDox hit @Override. Here is the stacktrace: > [INFO] Trace > com.thoughtworks.qdox.parser.ParseException: syntax error @[33,5] in ...my > java file > at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) > at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) > at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) > at > com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) > at > com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) > at > com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) > at > org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) > at > org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) > at > org.apache.maven.plugin.docck.CheckPluginDocumentationMojo.checkPackagingSpecificDocumentation(CheckPluginDocumentationMojo.java:67) > at > org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.checkProject(AbstractCheckDocumentationMojo.java:319) > at > org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.execute(AbstractCheckDocumentationMojo.java:149) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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) > [INFO] > -
[jira] Closed: (MPLUGIN-26) Parsing issue due to qdox regression
[ http://jira.codehaus.org/browse/MPLUGIN-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPLUGIN-26. Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.4.3 Fixed in [r675225|http://svn.apache.org/viewvc?view=rev&revision=675225] by updating to QDOX 1.6.3. which should contain the required parser fix. > Parsing issue due to qdox regression > > > Key: MPLUGIN-26 > URL: http://jira.codehaus.org/browse/MPLUGIN-26 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Jerome Lacoste >Assignee: Benjamin Bentmann >Priority: Blocker > Fix For: 2.4.3 > > > The webstart plugin build broke as the latest qdox (1.6.1) doesn't parse > valid code. > See QDOX-107 -- 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: (JXR-65) FileNotFoundException with different drives
FileNotFoundException with different drives
---
Key: JXR-65
URL: http://jira.codehaus.org/browse/JXR-65
Project: Maven JXR
Issue Type: Bug
Environment: Windows
Reporter: Mickaël MORIER
Suppose:
1 - I worked on Windows
2 - My project is stored on drive letter C
3 - I want to generate site:stage in a directory which is stored on drive
letter D
JXR generate a FileNotFoundException because project directory and staging
directory are on different drives.
Below this exception:
{quote}
[INFO] Generating "Source Xref" report.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Error while generating the HTML
source code of the projet.
D:\Temp\melovie-site\localhost\data\maven\sites\melovie\melovie-common\tedi-client\xref\fr\generali\tedi\adresse\constants\Constants.html
and C:\dev\projects\melovie\melovie-common\tedi-client\target\
site\apidocs have no common parent.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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.MojoExecutionException: Error during page
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:101)
at
org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: Error while generating the HTML source code of the
projet.
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
... 19 more
Caused by: org.apache.maven.reporting.MavenReportException: Error while
generating the HTML source code of the projet.
at
org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:417)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
... 23 more
Caused by: java.io.FileNotFoundException:
D:\Temp\melovie-site\localhost\data\maven\sites\melovie\melovie-common\tedi-client\xref\fr\generali\tedi\adresse\constants\Constants.html
and C:\dev\projects\
melovie\melovie-common\tedi-client\target\site\apidocs have no common parent.
at org.apache.maven.jxr.JXR.getRelativeLink(JXR.java:403)
at org.apache.maven.jxr.JXR.transform(JXR.java:335)
at org.apache.maven.jxr.JXR.processPath(JXR.java:139)
at
[jira] Commented: (JXR-65) FileNotFoundException with different drives
[
http://jira.codehaus.org/browse/JXR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141230#action_141230
]
Dennis Lundberg commented on JXR-65:
What command did you issue?
How does your configuration (POM) look?
What versions of the relevant plugins are you using?
> FileNotFoundException with different drives
> ---
>
> Key: JXR-65
> URL: http://jira.codehaus.org/browse/JXR-65
> Project: Maven JXR
> Issue Type: Bug
> Environment: Windows
>Reporter: Mickaël MORIER
>
> Suppose:
> 1 - I worked on Windows
> 2 - My project is stored on drive letter C
> 3 - I want to generate site:stage in a directory which is stored on drive
> letter D
> JXR generate a FileNotFoundException because project directory and staging
> directory are on different drives.
> Below this exception:
> {quote}
> [INFO] Generating "Source Xref" report.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Error while generating the HTML
> source code of the projet.
> D:\Temp\melovie-site\localhost\data\maven\sites\melovie\melovie-common\tedi-client\xref\fr\generali\tedi\adresse\constants\Constants.html
> and C:\dev\projects\melovie\melovie-common\tedi-client\target\
> site\apidocs have no common parent.
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
> generation
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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.MojoExecutionException: Error during page
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:101)
> at
> org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> rendering Maven report: Error while generating the HTML source code of the
> projet.
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: Error while
> generating the HTML source code of the projet.
> at
> org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:417)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocumen
[jira] Commented: (MECLIPSE-79) exclude dependencies from the Classpath Container
[ http://jira.codehaus.org/browse/MECLIPSE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141231#action_141231 ] Tom Bollwitt commented on MECLIPSE-79: -- Thanks Amaud! I am not sure why I did not notice that goal before. > exclude dependencies from the Classpath Container > - > > Key: MECLIPSE-79 > URL: http://jira.codehaus.org/browse/MECLIPSE-79 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Core : Dependencies resolution and build path > Environment: Windows, Eclipse 3.1.2 >Reporter: Martin Goldhahn >Assignee: nicolas de loof > Fix For: 2.5 > > Attachments: MECLIPSE-79.patch > > > There are some dependencies that need to be in the POM in order to compile > the project (e.g. javax.servlet). When I use Sysdeo's Tomcat plugin, I get an > error because the servlet classes from the POM are included in the classpath > via the classpath container. -- 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: (JXR-65) FileNotFoundException with different drives
[
http://jira.codehaus.org/browse/JXR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141235#action_141235
]
Mickaël MORIER commented on JXR-65:
---
My command is
mvn site:stage -DstagingDirectory=D:\temp\melovie-site
I use maven 2.0.9.
> FileNotFoundException with different drives
> ---
>
> Key: JXR-65
> URL: http://jira.codehaus.org/browse/JXR-65
> Project: Maven JXR
> Issue Type: Bug
> Environment: Windows
>Reporter: Mickaël MORIER
>
> Suppose:
> 1 - I worked on Windows
> 2 - My project is stored on drive letter C
> 3 - I want to generate site:stage in a directory which is stored on drive
> letter D
> JXR generate a FileNotFoundException because project directory and staging
> directory are on different drives.
> Below this exception:
> {quote}
> [INFO] Generating "Source Xref" report.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Error while generating the HTML
> source code of the projet.
> D:\Temp\melovie-site\localhost\data\maven\sites\melovie\melovie-common\tedi-client\xref\fr\generali\tedi\adresse\constants\Constants.html
> and C:\dev\projects\melovie\melovie-common\tedi-client\target\
> site\apidocs have no common parent.
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
> generation
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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.MojoExecutionException: Error during page
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:101)
> at
> org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> rendering Maven report: Error while generating the HTML source code of the
> projet.
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: Error while
> generating the HTML source code of the projet.
> at
> org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:417)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
[jira] Commented: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141240#action_141240 ] Carlos Sanchez commented on MAVENUPLOAD-2116: - asks for password, removed from sync > Please add MigLayout to the auto rsynced list. > -- > > Key: MAVENUPLOAD-2116 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mikael Grev >Assignee: Carlos Sanchez > > "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael > Grev,[EMAIL PROTECTED],, > The password is "maven". > MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being > added to SWT and #10 RFE for being added to the Java SDK. > I own MiGInfoCom AB which owns MigLayout. > Cheers, > Mikael Grev -- 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] Closed: (MAVENUPLOAD-2114) please upload jamon:jamon-2.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2114. --- Assignee: Carlos Sanchez Resolution: Won't Fix the old pom is not going to be changed, you can request the upload of jamon 2.6 under the group com.jamonapi > please upload jamon:jamon-2.6 > - > > Key: MAVENUPLOAD-2114 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2114 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Mark Struberg >Assignee: Carlos Sanchez > > jamon:jamon-2.6 is used in the package > fulcrum:fulcrum-yaafi:jar:1.0.5 > which is therefor currently broken in the repo1.apache.org -- 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: (MAVENUPLOAD-2144) Thinlet GUI toolkit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141242#action_141242 ] Carlos Sanchez commented on MAVENUPLOAD-2144: - we need a bundle or synced repository http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Thinlet GUI toolkit > --- > > Key: MAVENUPLOAD-2144 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2144 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alien Science > > Thinlet is a lightweight gui toolkit that I think is pretty cool and would > like to use it in a maven managed project. Its LGPL licensed and I would be > happy to create a POM, convert to a jar and maintain the upload if needed. > Many thanks for your consideration. -- 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] Closed: (MAVENUPLOAD-2120) Jericho HTML Parser 2.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2120. --- Assignee: Carlos Sanchez Resolution: Fixed > Jericho HTML Parser 2.6 > --- > > Key: MAVENUPLOAD-2120 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2120 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Martin Jericho >Assignee: Carlos Sanchez > > Jericho HTML Parser is a powerful java library allowing analysis and > manipulation of parts of an HTML document, including server-side tags, while > reproducing verbatim any unrecognised or invalid HTML. It also provides > high-level HTML form manipulation functions. -- 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] Closed: (MAVENUPLOAD-2117) Dozer 4.2.1 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2117. --- Assignee: Carlos Sanchez Resolution: Fixed > Dozer 4.2.1 upload > -- > > Key: MAVENUPLOAD-2117 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2117 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Matt Tierney >Assignee: Carlos Sanchez > Attachments: dozer-4.2.1-bundle.jar > > > Dozer is a powerful, yet simple Java Bean to Java Bean mapper that > recursively copies data from one object to another. Typically, these Java > Beans will be of different complex types. > Dozer supports simple property mapping, complex type mapping, bi-directional > mapping, implicit-explicit mapping, as well as recursive mapping. This > includes mapping collection attributes that also need mapping at the element > level. > Dozer not only supports mapping between attribute names, but also converting > between types. Many conversion scenarios are supported out of the box, but > Dozer also allows you to specify custom conversions via XML. > The mapper is used any time you need to take one type of Java Bean and map it > to another type of Java Bean. Most field mapping can be done automatically by > Dozer using reflection, but any custom mapping can be predescribed in XML > format. Mapping is bi-directional so only one relationship between classes > needs defining. If any property names on both objects are the same you do not > even need to do any explicit property mapping for these fields. -- 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: (MAVENUPLOAD-2122) Bundle upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141243#action_141243 ] Carlos Sanchez commented on MAVENUPLOAD-2122: - why the groupId com.rcreations ? see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Bundle upload > - > > Key: MAVENUPLOAD-2122 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2122 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: robert chou > > I'm a developer in gnutsp, please upload! -- 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] Closed: (MAVENUPLOAD-2125) easyb 0.9 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2125. --- Assignee: Carlos Sanchez Resolution: Fixed > easyb 0.9 upload > > > Key: MAVENUPLOAD-2125 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2125 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Rod Coffin >Assignee: Carlos Sanchez > > http://easyb.googlecode.com/files/easyb-0.9-bundle.jar > http://easyb.googlecode.com/files/easyb-dbunit-plugin-0.9-bundle.jar > http://easyb.googlecode.com/files/maven-parent-0.9-bundle.jar > http://easyb.googlecode.com/files/maven-easyb-plugin-0.9-bundle.jar > I am a developer on the easyb project and this can be verified at > http://code.google.com/p/easyb/ where I (username rfciii) am listed as one of > the project owners. -- 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: (MAVENUPLOAD-2124) javaparser-1.0.0-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141246#action_141246 ] Carlos Sanchez commented on MAVENUPLOAD-2124: - groupid should be com.google.code.javaparser > javaparser-1.0.0-bundle.jar > --- > > Key: MAVENUPLOAD-2124 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2124 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alexandr Liahushevich > Attachments: javaparser-1.0.0-bundle.jar, > javaparser-1.0.0-bundle.jar, javaparser-1.0.1-bundle.jar > > > From: Julio Gesser [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 2:38 PM > To: Alexandr Liahushevich > Subject: Re: Java 1.5 Parser - request to put sources into the maven > repository > > Helo Alexandr, > yes, you can put this distribution there, but I think you need to put the > license too. > best regards, > Júlio Vilmar Gesser > 2008/6/24 Alexandr Liahushevich <[EMAIL PROTECTED]>: > One more question please. > We are using Maven technology for our projects. > Is it ok for you and your team that we want to put your > javaparser_2008-06-19.jar file in the http://repo1.maven.org/maven2/ central > maven repository? -- 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: (MAVENUPLOAD-2141) Updated version of JSON Java code from www.json.org
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141247#action_141247 ] Carlos Sanchez commented on MAVENUPLOAD-2141: - why 20080708 ? the zip contents are dated 2008-07-01 > Updated version of JSON Java code from www.json.org > --- > > Key: MAVENUPLOAD-2141 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2141 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Tamm > > There have been some changes since the last release: > http://repo1.maven.org/maven2/org/json/json/20070829 -- 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] Closed: (MAVENUPLOAD-2143) FitNesse and FitLibrary 20080702
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2143. --- Assignee: Carlos Sanchez Resolution: Fixed > FitNesse and FitLibrary 20080702 > > > Key: MAVENUPLOAD-2143 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2143 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pål Brattberg >Assignee: Carlos Sanchez > > FitNesse is a fully integrated standalone wiki and acceptance testing > framework using FIT. > FitLibrary is an extension for FIT/FitNesse > I'm not a developer of FitNesse, but I am for DbFit which is dependant on > FitNesse. > The official JAR's are found at: http://www.fitnesse.org/FitNesse.DownLoad > The JAR's packaged for Maven (with POM) are found at: > http://www.palbrattberg.com/wp-content/uploads/2008/07/fitnesse-20080702-bundle.jar > http://www.palbrattberg.com/wp-content/uploads/2008/07/fitlibrary-20080702-bundle.jar -- 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: (MPIR-112) Dependency Listings is too big: replace it by toogle entries in the dependency tree
[ http://jira.codehaus.org/browse/MPIR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-112: - Description: We need to reduce the size of the Dependency Listings. A solution could be to remove the dependency listings and replace it by toogle entries in the dependency tree. was:We need to reduce the size of the Dependency Listings. Summary: Dependency Listings is too big: replace it by toogle entries in the dependency tree (was: Dependency Listings is too big) > Dependency Listings is too big: replace it by toogle entries in the > dependency tree > --- > > Key: MPIR-112 > URL: http://jira.codehaus.org/browse/MPIR-112 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > > We need to reduce the size of the Dependency Listings. > A solution could be to remove the dependency listings and replace it by > toogle entries in the dependency tree. -- 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: (MPIR-112) Dependency Listings is too big: replace it by toogle entries in the dependency tree
[ http://jira.codehaus.org/browse/MPIR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141249#action_141249 ] Dennis Lundberg commented on MPIR-112: -- Cant' we let this one wait until the next release? > Dependency Listings is too big: replace it by toogle entries in the > dependency tree > --- > > Key: MPIR-112 > URL: http://jira.codehaus.org/browse/MPIR-112 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > > We need to reduce the size of the Dependency Listings. > A solution could be to remove the dependency listings and replace it by > toogle entries in the dependency tree. -- 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] Work started: (MPIR-112) Dependency Listings is too big: replace it by toogle entries in the dependency tree
[ http://jira.codehaus.org/browse/MPIR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MPIR-112 started by Vincent Siveton. > Dependency Listings is too big: replace it by toogle entries in the > dependency tree > --- > > Key: MPIR-112 > URL: http://jira.codehaus.org/browse/MPIR-112 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > We need to reduce the size of the Dependency Listings. > A solution could be to remove the dependency listings and replace it by > toogle entries in the dependency tree. -- 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: (MPIR-112) Dependency Listings is too big: replace it by toogle entries in the dependency tree
[ http://jira.codehaus.org/browse/MPIR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141250#action_141250 ] Vincent Siveton commented on MPIR-112: -- The generated report (just take it from MPIR!) is actually not very userfriendly. I would like to improve it before the release. > Dependency Listings is too big: replace it by toogle entries in the > dependency tree > --- > > Key: MPIR-112 > URL: http://jira.codehaus.org/browse/MPIR-112 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > We need to reduce the size of the Dependency Listings. > A solution could be to remove the dependency listings and replace it by > toogle entries in the dependency tree. -- 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: (MPIR-113) Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project
Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project --- Key: MPIR-113 URL: http://jira.codehaus.org/browse/MPIR-113 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Vincent Siveton -- 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: (MPIR-114) Validate all generated reports with validator.w3.org
Validate all generated reports with validator.w3.org - Key: MPIR-114 URL: http://jira.codehaus.org/browse/MPIR-114 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Affects Versions: 2.1 Reporter: Vincent Siveton Fix For: 2.1 -- 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: (MPIR-113) Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project
[ http://jira.codehaus.org/browse/MPIR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-113: - Fix Version/s: 2.1 > Dependency Tree lists all dependencies: needs to reduce to dependencies used > by the project > --- > > Key: MPIR-113 > URL: http://jira.codehaus.org/browse/MPIR-113 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > -- 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: (MPIR-114) Validate all generated reports with validator.w3.org
[ http://jira.codehaus.org/browse/MPIR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-114: - Fix Version/s: 2.1 > Validate all generated reports with validator.w3.org > - > > Key: MPIR-114 > URL: http://jira.codehaus.org/browse/MPIR-114 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > -- 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: (MPIR-114) Validate all generated reports with validator.w3.org
[ http://jira.codehaus.org/browse/MPIR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141254#action_141254 ] Benjamin Bentmann commented on MPIR-114: You could also try [Validome|http://www.validome.org/lang/en/errors/ALL]. > Validate all generated reports with validator.w3.org > - > > Key: MPIR-114 > URL: http://jira.codehaus.org/browse/MPIR-114 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > -- 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] Closed: (MPIR-112) Dependency Listings is too big: replace it by toogle entries in the dependency tree
[ http://jira.codehaus.org/browse/MPIR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-112. Resolution: Fixed fixed in r675324, snapshot deployed > Dependency Listings is too big: replace it by toogle entries in the > dependency tree > --- > > Key: MPIR-112 > URL: http://jira.codehaus.org/browse/MPIR-112 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > We need to reduce the size of the Dependency Listings. > A solution could be to remove the dependency listings and replace it by > toogle entries in the dependency tree. -- 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] Closed: (MPIR-113) Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project
[ http://jira.codehaus.org/browse/MPIR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-113. Assignee: Vincent Siveton Resolution: Fixed fixed in r675328, snapshot deployed > Dependency Tree lists all dependencies: needs to reduce to dependencies used > by the project > --- > > Key: MPIR-113 > URL: http://jira.codehaus.org/browse/MPIR-113 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > -- 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: (MPIR-115) Make the Sealed column optional in dependencies report
Make the Sealed column optional in dependencies report --- Key: MPIR-115 URL: http://jira.codehaus.org/browse/MPIR-115 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Reporter: Vincent Siveton Sealed column is always present and in several cases it is empty. -- 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: (MNG-3660) "combine.children='append'" not being honored in
"combine.children='append'" not being honored in
-
Key: MNG-3660
URL: http://jira.codehaus.org/browse/MNG-3660
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation, Plugins and Lifecycle, POM
Affects Versions: 2.0.9
Reporter: Brian Lalor
Attachments: maven_config_bug.tgz
I'm trying to combine multiple maven-javadoc-plugin configuration stanzas such
that child modules can append {{}} elements to those specified by the
parent. This supposedly can be done by adding the attribute
"{{combine.children='append'}}" to the {{}} element in the child
module's {{}} element, like so:
{code:xml}
maven-javadoc-plugin
http://static.springframework.org/spring/docs/2.5.x/api/
{code}
What actually happens is that the child module's configuration reflects only
the single {{}}, and not any {{}} elements also defined in the
parent. The output of {{mvn help:effective-pom}} bears this out. Putting the
plugin configuration into the {{}} element instead of {{}}
shows the correct combination occurring (except that the report is obviously
not configured that way...).
The attached tarball contains a barebones multi-module project that shows this
bug, as well as the output of {{help:effective-pom}} in separate files. I've
also included the output of {{mvn -X help:effective-pom}} in the file
{{build.log}}.
--
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] Closed: (MPIR-115) Make the Sealed column optional in dependencies report
[ http://jira.codehaus.org/browse/MPIR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-115. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 Fixed in r675339, snapshot deployed > Make the Sealed column optional in dependencies report > --- > > Key: MPIR-115 > URL: http://jira.codehaus.org/browse/MPIR-115 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > Sealed column is always present and in several cases it is empty. -- 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: (MPIR-114) Validate all generated reports with validator.w3.org
[ http://jira.codehaus.org/browse/MPIR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141268#action_141268 ] Vincent Siveton commented on MPIR-114: -- Thanks Benjamin for this pointer but it seems to strict about javascript and style. > Validate all generated reports with validator.w3.org > - > > Key: MPIR-114 > URL: http://jira.codehaus.org/browse/MPIR-114 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > -- 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] Closed: (MPIR-114) Validate all generated reports with validator.w3.org
[ http://jira.codehaus.org/browse/MPIR-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-114. Assignee: Vincent Siveton Resolution: Fixed fixed in r675341, snapshot deployed > Validate all generated reports with validator.w3.org > - > > Key: MPIR-114 > URL: http://jira.codehaus.org/browse/MPIR-114 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > -- 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] Closed: (MPIR-109) Wrong description of in source repository overview
[
http://jira.codehaus.org/browse/MPIR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MPIR-109.
Resolution: Fixed
> Wrong description of in source repository overview
> --
>
> Key: MPIR-109
> URL: http://jira.codehaus.org/browse/MPIR-109
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.0.1
>Reporter: Michael Osipov
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.1
>
>
> I have defined in my pom.xml
> {code:xml}
>
>
> scm:svn:http://svn.fckeditor.net/FCKeditor.Java/trunk
>
> scm:svn:https://svn.fckeditor.net/FCKeditor.Java/trunk
> http://dev.fckeditor.net/browser/FCKeditor.Java/trunk
>
> {code}
> MPIR writed under developer access: "Everyone can access the Subversion
> repository via HTTPS, but Committers must checkout the Subversion repository
> via HTTPS."
> As far as I understand it should say: "Everyone can access the Subversion
> repository via *HTTP*, but *committers* must checkout the Subversion
> repository via HTTPS." Unless I provide HTTPS access in anonymous access too.
> Continuing more style corrections: "For those users who are stuck behind a
> corporate firewall which is blocking http access to the Subversion
> repository," should be "For those users who are stuck behind a corporate
> firewall which is blocking *HTTP* access to the Subversion repository,"
> More: "Example : Edit the 'servers' file and add something like :" Should be:
> "*Example:* Edit the 'servers' file and add something *like:*" No space
> precedes a colon.
> Note: Bold formatting is only for highlighting purposes
--
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] Closed: (MNG-3380) MavenMetadataSource retrieves ResolutionGroup without consulting ManagedVersionMap, is problem when relocation
[ http://jira.codehaus.org/browse/MNG-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3380. --- Resolution: Fixed Fix Version/s: 2.1-alpha-1 I modified the artifact collector (and artifact metadata source) to allow the resolution of all project relocations before attempting to resolve the child nodes. > MavenMetadataSource retrieves ResolutionGroup without consulting > ManagedVersionMap, is problem when relocation > -- > > Key: MNG-3380 > URL: http://jira.codehaus.org/browse/MNG-3380 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.8 >Reporter: luke w patterson >Assignee: John Casey > Fix For: 2.0.10, 2.1-alpha-1 > > Attachments: MNG-3380-integration-test.zip, > MNG-3380-maven-artifact.patch, patch.txt, repo.zip > > > Consider the following scenario: > > 4.0.0 > root-groupId > root-artifactId > 1 > > > direct-dependency-groupId > direct-dependency-artifactId > 1 > > > > > > transitive-dependency-new-groupId > transitive-dependency-artifactId > 2 > > > > > > 4.0.0 > direct-dependency-groupId > direct-dependency-artifactId > 1 > > > transitive-dependency-old-groupId > transitive-dependency-artifactId > 1 > > > > > > 4.0.0 > transitive-dependency-old-groupId > transitive-dependency-artifactId > 1 > > > transitive-dependency-new-groupId > > > > > 4.0.0 > transitive-dependency-new-groupId > transitive-dependency-artifactId > 1 > > > other-groupId > other-artifactId-a > 1 > > > > > 4.0.0 > transitive-dependency-new-groupId > transitive-dependency-artifactId > 2 > > > other-groupId > other-artifactId-a > 1 > > > other-groupId > other-artifactId-b > 1 > > > > > -- > actual dependency:tree > > root-groupId:root-artifactId:jar:1 > \- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile > \- > transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile > (version managed from 1) >\- other-groupId:other-artifactId-a:jar:1:compile > -- > expected dependency:tree > > root-groupId:root-artifactId:jar:1 > \- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile > \- > transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile > (version managed from 1) >\- other-groupId:other-artifactId-a:jar:1:compile >\- other-groupId:other-artifactId-b:jar:1:compile <-- missing from > actual result > -- > > As you can see from the listing above, > other-groupId:other-artifactId-b:jar:1:compile is missing from the dependency > list. > I have attached the zipped repo which was used when generating the > dependency:tree listings shown above. I also attached a crude temporary > patch which my team is currently using to resolve this issue. After ignoring > whitespace changes, it is about 10 lines different. > Thanks, > Luke -- 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: (MNG-2994) Snapshot repositories are not checked when using ranges
[ http://jira.codehaus.org/browse/MNG-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-2994: Fix Version/s: (was: 2.0.10) 2.0.11 This will need to wait until the other snapshots-in-version-ranges issue (referenced as a prerequisite for this issue) is resolved. Otherwise, we risk changing existing build behavior for version ranges in very bad ways. > Snapshot repositories are not checked when using ranges > --- > > Key: MNG-2994 > URL: http://jira.codehaus.org/browse/MNG-2994 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.6 > Environment: Windows XP, Cygwin >Reporter: Mark Hobson >Assignee: Jason van Zyl > Fix For: 2.0.11 > > Attachments: MNG-2994-2.patch, MNG-2994-3.patch, > MNG-2994-core-it.patch, patch.txt > > > The attached patch demonstrates the problem by adding it0121. If the test > repository has releases enabled, the test passes, when they are disabled, the > test fails. This appears to be due to DefaultArtifact.isSnapshot returning > false for unresolved ranges, thus causing snapshot repositories to be > disabled when resolving artifacts. -- 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: (MNG-2931) DefaultArtifactCollector changes the version of the originatingArtifact if it's in the dependencyManagement with another version
[ http://jira.codehaus.org/browse/MNG-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141278#action_141278 ] John Casey commented on MNG-2931: - For clarity, the attached patch has already been applied. (MNG-2931.patch) > DefaultArtifactCollector changes the version of the originatingArtifact if > it's in the dependencyManagement with another version > > > Key: MNG-2931 > URL: http://jira.codehaus.org/browse/MNG-2931 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.5, 2.0.6 >Reporter: Carlos Sanchez > Fix For: 2.0.10 > > Attachments: MNG-2931.patch > > > DefaultDependencyTreeBuilder > https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree/src/main/java/org/apache/maven/shared/dependency/tree/DefaultDependencyTreeBuilder.java > calls collect like this > collector.collect( project.getDependencyArtifacts(), > project.getArtifact(), managedVersions, repository, >project.getRemoteArtifactRepositories(), > metadataSource, null, >Collections.singletonList( listener ) ); > Problem: > This pom > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-22/plexus-component-api-1.0-alpha-22.pom > extends > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0-alpha-22/plexus-containers-1.0-alpha-22.pom > that in dependencyManagement has > org.codehaus.plexus:plexus-component-api:1.0-alpha-19 > so during collect project.getArtifact().getVersion() is changed to the > managedVersion instead of the original one > Either this is a bug or an exception should be thrown when > originatingArtifact is in managedVersions -- 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: (MNG-2931) DefaultArtifactCollector changes the version of the originatingArtifact if it's in the dependencyManagement with another version
[ http://jira.codehaus.org/browse/MNG-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-2931: Fix Version/s: (was: 2.0.10) 2.0.11 We need a clear test case for this issue, or it's going to be nearly impossible to be sure we have it located and fixed. > DefaultArtifactCollector changes the version of the originatingArtifact if > it's in the dependencyManagement with another version > > > Key: MNG-2931 > URL: http://jira.codehaus.org/browse/MNG-2931 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.5, 2.0.6 >Reporter: Carlos Sanchez > Fix For: 2.0.11 > > Attachments: MNG-2931.patch > > > DefaultDependencyTreeBuilder > https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree/src/main/java/org/apache/maven/shared/dependency/tree/DefaultDependencyTreeBuilder.java > calls collect like this > collector.collect( project.getDependencyArtifacts(), > project.getArtifact(), managedVersions, repository, >project.getRemoteArtifactRepositories(), > metadataSource, null, >Collections.singletonList( listener ) ); > Problem: > This pom > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-22/plexus-component-api-1.0-alpha-22.pom > extends > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0-alpha-22/plexus-containers-1.0-alpha-22.pom > that in dependencyManagement has > org.codehaus.plexus:plexus-component-api:1.0-alpha-19 > so during collect project.getArtifact().getVersion() is changed to the > managedVersion instead of the original one > Either this is a bug or an exception should be thrown when > originatingArtifact is in managedVersions -- 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: (MNG-3560) unable to use plugins that exist in multiple repositories
[
http://jira.codehaus.org/browse/MNG-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3560:
Fix Version/s: (was: 2.0.10)
2.0.11
still waiting on a failing test case so we can be sure this issue is cleared up.
> unable to use plugins that exist in multiple repositories
> -
>
> Key: MNG-3560
> URL: http://jira.codehaus.org/browse/MNG-3560
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0.9
>Reporter: Maria Catherine Tan
>Assignee: Brett Porter
> Fix For: 2.0.11
>
> Attachments: MNG-3560-maven-artifact.patch
>
>
> I created two test cases using maven-2.0.9
> A. Here's the settings for my first test case which builds successfully using
> mvn site or mvn site -up
> 1. Created two remote repository
> - sandbox has maven-project-info-reports-plugin 2.0.1
> - corporate has maven-project-info-reports-plugin 2.0
> 2. No maven-project-info-reports-plugin in my local repository
> 3. Access to central repository is disabled
> 4. The order in my settings.xml for the plugin repositories is sandbox first
> before corporate
>
> sandbox
> http://localhost:9091/repository/sandbox
>
>
> corporate
> http://localhost:9091/repository/corporate
>
> Result:
> * downloaded maven-project-info-reports-plugin 2.0 pom in corporate
> * check maven-project-info-reports-plugin 2.0 jar in sandbox
> * downloaded maven-project-info-reports-plugin 2.0 jar in corporate
> {code}
> [EMAIL PROTECTED]:~/projects/testproject$ mvn site -up
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building testproject
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from sandbox
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from corporate
> [INFO] artifact org.apache.maven.plugins:maven-project-info-reports-plugin:
> checking for updates from central
> [WARNING] repository metadata for: 'artifact
> org.apache.maven.plugins:maven-project-info-reports-plugin' could not be
> retrieved from repository: central due to an error: Error transferring file
> [INFO] Repository 'central' will be blacklisted
> Downloading:
> http://localhost:9091/repository/corporate/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.pom
> 5K downloaded
> Downloading:
> http://localhost:9091/repository/sandbox/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.jar
> Downloading:
> http://localhost:9091/repository/corporate/org/apache/maven/plugins/maven-project-info-reports-plugin/2.0/maven-project-info-reports-plugin-2.0.jar
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [site:site]
> [INFO] Generating "Source Repository" report.
> [INFO] Generating "Issue Tracking" report.
> [INFO] Generating "About" report.
> [INFO] Generating "Project License" report.
> [INFO] Generating "Project Summary" report.
> [INFO] Generating "Dependencies" report.
> [INFO] Generating "Continuous Integration" report.
> [INFO] Generating "Project Team" report.
> [INFO] Generating "Mailing Lists" report.
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> {code}
> B. Here's the settings for my second test case which replicate this issue
> 1. Created two remote repository
> - sandbox has maven-project-info-reports-plugin 2.0.1
> - corporate has maven-project-info-reports-plugin 2.0
> 2. No maven-project-info-reports-plugin in my local repository
> 3. Access to central repository is disabled
> 4. The order in my settings.xml for the plugin repositories is corporate
> first before sandbox
>
> corporate
> http://localhost:9091/repository/corporate
>
>
> sandbox
> http://localhost:9091/repository/sandbox
>
> Result:
> * downloaded maven-project-info-reports-plugin 2.0 pom in sandbox which
> it did not find and never tries to check the corporate where the pom could be
> found
> * downloaded maven-project-info-reports-plugin 2.0 jar in corporate
> {code}
> [EMAIL PROTECTED]:~/projects/testproject$ mvn site -up
> [INF
[jira] Created: (MPIR-116) Make the classifier column optional in dependencies management report
Make the classifier column optional in dependencies management report -- Key: MPIR-116 URL: http://jira.codehaus.org/browse/MPIR-116 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Vincent Siveton -- 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] Closed: (MPIR-116) Make the classifier column optional in dependencies management report
[ http://jira.codehaus.org/browse/MPIR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-116. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r675365, snapshot deployed > Make the classifier column optional in dependencies management report > -- > > Key: MPIR-116 > URL: http://jira.codehaus.org/browse/MPIR-116 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > -- 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: (MECLIPSE-331) Allow to use a packaging model to override the packaging defined in the pom
[
http://jira.codehaus.org/browse/MECLIPSE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141283#action_141283
]
Eelco Hillenius commented on MECLIPSE-331:
--
This doesn't work for me. I have a project that uses swf packaging (flex
mojos), and a plugin configuration in the build section like this:
{code:xml}
org.apache.maven.plugins
maven-eclipse-plugin
jar
target
com.adobe.flexbuilder.project.flexbuilder
com.adobe.flexbuilder.project.flexnature
com.adobe.flexbuilder.project.actionscriptnature
{code}
Unfortunately, this doesn't trigger the maven-eclipse plugin for adding the
javabuilder & javanature to the project, nor does result in the plugin creating
a .classpath file.
I tested this with 2.5 and 2.5.1.
> Allow to use a packaging model to override the packaging defined in the pom
> ---
>
> Key: MECLIPSE-331
> URL: http://jira.codehaus.org/browse/MECLIPSE-331
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
>
> It can be useful to be able to define the packaging to use to generate
> eclipse settings.
> In the case of a customized packaging (a grails application for ex) you would
> like to use a war packaging model to be able to reuse WTP feature, but it is
> actually impossible because the plugin reads directly the pom packaging (and
> not an intermediate configuration variable).
--
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: (MPIR-117) Replaced the table caption in the CI report
Replaced the table caption in the CI report --- Key: MPIR-117 URL: http://jira.codehaus.org/browse/MPIR-117 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: cim Affects Versions: 2.1 Reporter: Vincent Siveton The following text "Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode." is actually a table caption. I suggested to replace it to a paragraph. -- 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] Closed: (MPIR-117) Replaced the table caption in the CI report
[ http://jira.codehaus.org/browse/MPIR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-117. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.1 fixed in r675371, snapshot deployed > Replaced the table caption in the CI report > --- > > Key: MPIR-117 > URL: http://jira.codehaus.org/browse/MPIR-117 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: cim >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > The following text "Configuration for notifying developers/users when a build > is unsuccessful, including user information and notification mode." is > actually a table caption. > I suggested to replace it to a paragraph. -- 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: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141287#action_141287 ] Mikael Grev commented on MAVENUPLOAD-2116: -- Yes, as in the first message the password is "maven". Is that not OK? It is easy to set up rsync to use a password. > Please add MigLayout to the auto rsynced list. > -- > > Key: MAVENUPLOAD-2116 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mikael Grev >Assignee: Carlos Sanchez > > "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael > Grev,[EMAIL PROTECTED],, > The password is "maven". > MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being > added to SWT and #10 RFE for being added to the Java SDK. > I own MiGInfoCom AB which owns MigLayout. > Cheers, > Mikael Grev -- 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: (MPIR-118) Equalize links to project web site for artifactId
Equalize links to project web site for artifactId -- Key: MPIR-118 URL: http://jira.codehaus.org/browse/MPIR-118 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: dependencies, dependency-convergence, dependency-management, plugin-management Affects Versions: 2.1 Reporter: Vincent Siveton Actually, only the "Project Plugin Management" report has a link in artifactId column to its project web site. It should be great to add be default a link to the project Artifact, if it is specified of course. -- 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: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141289#action_141289 ] Carlos Sanchez commented on MAVENUPLOAD-2116: - the sync is automatic, if you want password use rsync over ssh , see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please add MigLayout to the auto rsynced list. > -- > > Key: MAVENUPLOAD-2116 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mikael Grev >Assignee: Carlos Sanchez > > "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael > Grev,[EMAIL PROTECTED],, > The password is "maven". > MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being > added to SWT and #10 RFE for being added to the Java SDK. > I own MiGInfoCom AB which owns MigLayout. > Cheers, > Mikael Grev -- 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: (MASSEMBLY-230) not filtering resources, but does filter
[
http://jira.codehaus.org/browse/MASSEMBLY-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141295#action_141295
]
Kirill Petrov commented on MASSEMBLY-230:
-
I have exact same problem, it does not filter if I build parent project. Very
annoying.
> not filtering resources, but does filter
> --
>
> Key: MASSEMBLY-230
> URL: http://jira.codehaus.org/browse/MASSEMBLY-230
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
> Environment: Windows XP Maven 2.0.5
>Reporter: Mick Knutson
> Fix For: 2.2
>
>
> In my assembly descriptor, this does not filter my resources:
>
> ${basedir}/src/main/resources/deploy
> true
> true
> /
>
> *.sh
> *.bat
>
> 0544
>
> But this DOES filter the same resources just fine:
>
>
>
> ${basedir}/src/main/resources/deploy/deploy.sh.txt
> deploy
> test.sh
> true
> unix
> 0554
>
>
> I have tried 2.2-beta-1 and 2.1 of the plugin and it acts the same way.
> A workaround is to just specify each file individually, but I have dozens of
> files and the descriptor is going to get quite cluttered.
--
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] Closed: (MNGSITE-56) Website cleaning: remove old Maven pages
[
http://jira.codehaus.org/browse/MNGSITE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MNGSITE-56.
--
Assignee: Vincent Siveton
Resolution: Fixed
> Website cleaning: remove old Maven pages
>
>
> Key: MNGSITE-56
> URL: http://jira.codehaus.org/browse/MNGSITE-56
> Project: Maven 2 Project Web Site
> Issue Type: Task
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
>
> A lot of old Maven pages are visible and some of these pages are grossly out
> of date and misleading.
> See below for a list of old pages after running $ find . -mtime +365 -type f
> -name "*"
> {noformat}
> ./ant-guide/*
> ./apache/index.html
> ./archived/*
> ./continuum/*
> ./continuum-stage/*
> ./developers/code-style.html
> ./developers/apache.html
> ./developers/documentation-conventions.html
> ./developers/building-from-source.html
> ./developers/making-releases.html
> ./developers/maven-codestyle.xml
> ./developers/releasing-plugins.html
> ./developers/pmc-gpg-keys.html
> ./developers/pmc-release-process.html
> ./guides/introduction/introduction-to-dependency-management.html
> ./guides/mini/configuration.html
> ./guides/mini/guide-deploy-ftp.html
> ./guides/mini/guide-deploy-ssh-external.html
> ./guides/mini/guide-creating-plugin-with-lifecycle-modifications.html
> ./guides/mini/guide-installing-3rd-party-jars.html
> ./guides/mini/guide-multi-module.html
> ./guides/MavenQuickReferenceCard.odt
> ./m2/*
> ./dependencies.html
> ./auto-faq.html
> ./changelog.html
> ./maven-model/*
> ./maven-settings/*
> ./dev-activity.html
> ./documentation-required.html
> ./examples.html
> ./faq.html
> ./features.html
> ./file-activity.html
> ./foo.html
> ./getting-started.html
> ./goals.html
> ./jxr.html
> ./maven2/*
> ./misc/*
> ./plugins-sandbox/* (NOT SURE)
> ./project/components.html
> ./project/index.html
> ./project/sun-licensing-journey.html
> ./maven_checks.xml
> ./maven-feature-categories.html
> ./maven-navigation-1.0.xsd
> ./maven-reports.html
> ./maven-v3_0_0.xsd
> ./maven-v4_0_0.xsd
> ./musings.html
> ./reference/*
> ./new-design-musings.html
> ./objectives.html
> ./patches.html
> ./plugin-votes.html
> ./repository-manager/*
> ./project-summary.html
> ./quotes.txt
> {noformat}
> Notes:
> * voluntarily, I did not list subprojects like plugins. Release managers
> could clean them.
> * some directories like continuum use redirection
--
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: (MNG-3640) CLI cannot deactivate a profile that's activated in POM via
[
http://jira.codehaus.org/browse/MNG-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3640:
Fix Version/s: 2.0.11
> CLI cannot deactivate a profile that's activated in POM via
> -
>
> Key: MNG-3640
> URL: http://jira.codehaus.org/browse/MNG-3640
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.9
>Reporter: Kohsuke Kawaguchi
> Fix For: 2.0.11
>
>
> Consider the following POM:
> {noformat}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> test
> test
> jar
> 1.0-SNAPSHOT
> test
> http://maven.apache.org
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> yuck
>
> true
>
>
>
>
> no-such-plugin
> just-to-cause-error
>
>
>
>
>
>
> {noformat}
> I'd like to deactivate the "yuck" profile that kicks in by default. I cannot
> do this even if I run "mvn -P -yuck".
> This is because the DefaultProfileManager.getActiveProfiles() is implemented
> as follows:
> {noformat}
> public List getActiveProfiles()
> throws ProfileActivationException
> {
> List activeFromPom = new ArrayList();
> List activeExternal = new ArrayList();
> for ( Iterator it = profilesById.entrySet().iterator(); it.hasNext();
> )
> {
> Map.Entry entry = (Entry) it.next();
> String profileId = (String) entry.getKey();
> Profile profile = (Profile) entry.getValue();
> boolean shouldAdd = false;
> if ( activatedIds.contains( profileId ) )
> {
> shouldAdd = true;
> }
> else if ( !deactivatedIds.contains( profileId ) && isActive(
> profile ) )
> {
> shouldAdd = true;
> }
> if ( shouldAdd )
> {
> if ( "pom".equals( profile.getSource() ) )
> {
> activeFromPom.add( profile );
> }
> else
> {
> activeExternal.add( profile );
> }
> }
> }
> if ( activeFromPom.isEmpty() )
> {
> for ( Iterator it = defaultIds.iterator(); it.hasNext(); )
> {
> String profileId = (String) it.next();
> Profile profile = (Profile) profilesById.get( profileId );
> activeFromPom.add( profile );
> }
> }
> List allActive = new ArrayList( activeFromPom.size() +
> activeExternal.size() );
> allActive.addAll( activeExternal );
> allActive.addAll( activeFromPom );
> return allActive;
> }
> {noformat}
> ... and therefore the {{defaultIds}} set (which contains "yuck") is
> considered active, even if {{deactivatedIds}} contain them. The fix should be
> obvious by now.
--
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: (MNG-3641) Lack of error checks on profiles
[
http://jira.codehaus.org/browse/MNG-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3641:
Fix Version/s: 2.0.11
given the fact that we can trigger settings profiles at the CLI, we can't make
these cases fail the build I don't think...but we could provide a prominent
warning.
> Lack of error checks on profiles
>
>
> Key: MNG-3641
> URL: http://jira.codehaus.org/browse/MNG-3641
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.9
>Reporter: Kohsuke Kawaguchi
> Fix For: 2.0.11
>
>
> DefaultProfileManager performs no error checks on the profile IDs So If I
> specify bogus profile IDs from plugins (like {{mvn -P no-such-profile}}),
> Maven doesn't complain, and it just runs as if nothing was specified. This is
> very error prone.
> Also, I've seen some documentation that says deactivating a profile is "-P
> !profile". As far as I can tell from the code, this is wrong, but because of
> the lack of error check, such usage just gets ignored, and the user is left
> confused as to why the profile isn't deactivated.
--
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: (MNG-3651) mvn.bat returns an incorrect error code
[ http://jira.codehaus.org/browse/MNG-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3651: Fix Version/s: 2.0.10 > mvn.bat returns an incorrect error code > --- > > Key: MNG-3651 > URL: http://jira.codehaus.org/browse/MNG-3651 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: John Casey > Fix For: 2.0.10 > > Attachments: MNG-3651-apache-maven.patch > > > In a number of instances, mvn.bat returns zero when it should be non-zero due > to a build error. -- 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] Closed: (MNG-3651) mvn.bat returns an incorrect error code
[ http://jira.codehaus.org/browse/MNG-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3651. --- Resolution: Fixed Fix Version/s: 2.1-alpha-1 applied, thanks > mvn.bat returns an incorrect error code > --- > > Key: MNG-3651 > URL: http://jira.codehaus.org/browse/MNG-3651 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.9 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: John Casey > Fix For: 2.0.10, 2.1-alpha-1 > > Attachments: MNG-3651-apache-maven.patch > > > In a number of instances, mvn.bat returns zero when it should be non-zero due > to a build error. -- 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: (MNG-3644) Add the list of active profiles to pom.properties
[ http://jira.codehaus.org/browse/MNG-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3644: Fix Version/s: 2.0.11 > Add the list of active profiles to pom.properties > - > > Key: MNG-3644 > URL: http://jira.codehaus.org/browse/MNG-3644 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Affects Versions: 2.0.9 >Reporter: Cristiano Kliemann >Priority: Minor > Fix For: 2.0.11 > > Attachments: MNG-3644-maven-archiver.patch > > > When I create a package, I don't know which profiles were active. > What about adding the list of active profiles to pom.properties? -- 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: (MECLIPSE-331) Allow to use a packaging model to override the packaging defined in the pom
[ http://jira.codehaus.org/browse/MECLIPSE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141315#action_141315 ] Arnaud Heritier commented on MECLIPSE-331: -- Can you submit a testcase to allow me to reproduce your issue ? > Allow to use a packaging model to override the packaging defined in the pom > --- > > Key: MECLIPSE-331 > URL: http://jira.codehaus.org/browse/MECLIPSE-331 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > Fix For: 2.5 > > > It can be useful to be able to define the packaging to use to generate > eclipse settings. > In the case of a customized packaging (a grails application for ex) you would > like to use a war packaging model to be able to reuse WTP feature, but it is > actually impossible because the plugin reads directly the pom packaging (and > not an intermediate configuration variable). -- 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
