[jira] Created: (MAVENUPLOAD-1990) Upload request for swingx 0.9.2
Upload request for swingx 0.9.2 --- Key: MAVENUPLOAD-1990 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1990 Project: maven-upload-requests Issue Type: Task Reporter: Jan Haderka SwingX is all about Swing components. It focuses both on extensions to existing Swing components as well as brand new ones. SwingX contains a lot of great components that you can use in your applications today. -- 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: (MDEPLOY-74) Add an option to be able to abort if an artifact is already present in the deployment repository
[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129123#action_129123 ] Baptiste MATHUS commented on MDEPLOY-74: Well, according to Brian E. Fox, this behaviour is already the default in the "new code" (maven 2.1), cf. http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-present-to16329568s177.html#a16353467 So, I guess the "fix version" of this bug report could be updated to show it's been fixed, isn't? > Add an option to be able to abort if an artifact is already present in the > deployment repository > > > Key: MDEPLOY-74 > URL: http://jira.codehaus.org/browse/MDEPLOY-74 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Reporter: Baptiste MATHUS >Priority: Minor > > Hi all, > Would be great if it was possible to use a command like: > mvn deploy -DfailIfPresent=true (false by default, to behave as currently) > That switch would do a build failure if the artifact is found in the > deployment repository. > Alternatively or in addition, a -DdryRun=true could add a simulation mode to > this plugin. Particularly, it would clearly display if the artifact would be > overriding an already present one or not. > Cheers. -- 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: (MWAR-152) mvn clean does not clean up target directories and build logs from integration tests
mvn clean does not clean up target directories and build logs from integration tests Key: MWAR-152 URL: http://jira.codehaus.org/browse/MWAR-152 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.1-alpha-2 Reporter: Wendy Smoak Priority: Minor After adding an integration test for MWAR-131, I noticed that 'mvn clean' didn't clean up after it properly. $ mvn install; mvn clean $ svn status ? src/it/MWAR-131/build.log ? src/it/MWAR-131/mwar131-webapp/target ? src/it/MWAR-131/mwar131-test/target ? src/it/MWAR-131/mwar131-webapp2/target However: $ find . -name target ./src/it/MWAR-129/target ./src/it/MWAR-131/mwar131-test/target ./src/it/MWAR-131/mwar131-webapp/target ./src/it/MWAR-131/mwar131-webapp2/target ./src/it/MWAR-139/target ./src/it/MWAR-143/war-common/target ./src/it/MWAR-143/war-filter-overlay/target ./src/it/MWAR-62/target ./src/it/MWAR-96/target ./src/it/scoped-dependency-same-artifact/target ./src/it/simple-war-no-webxml/target ./src/it/simple-war-project/target $ find . -name build.log ./src/it/MWAR-129/build.log ./src/it/MWAR-131/build.log ./src/it/MWAR-139/build.log ./src/it/MWAR-143/build.log ./src/it/MWAR-62/build.log ./src/it/MWAR-96/build.log ./src/it/scoped-dependency-same-artifact/build.log ./src/it/simple-war-no-webxml/build.log ./src/it/simple-war-project/build.log Instead of the clean plugin being configured to delete these files, the svn:ignore property is set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3489) StringIndexOutOfBoundsException in AbstractMavenReportRenderer.applyPattern
[ http://jira.codehaus.org/browse/MNG-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129128#action_129128 ] Herve Boutemy commented on MNG-3489: please attach a testcase to reproduce the problem > StringIndexOutOfBoundsException in AbstractMavenReportRenderer.applyPattern > --- > > Key: MNG-3489 > URL: http://jira.codehaus.org/browse/MNG-3489 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 > Environment: Maven embedder being called from Hudson 1.199 >Reporter: Elifarley Callado Coelho >Priority: Blocker > > Maybe the problem is in > 'ProjectSummaryReport$ProjectSummaryRenderer.renderBody'. > Here is the stack trace: > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -221 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -221 > at java.lang.String.substring(String.java:1768) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.applyPattern(AbstractMavenReportRenderer.java:533) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.linkPatternedText(AbstractMavenReportRenderer.java:353) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:213) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.tableCell(AbstractMavenReportRenderer.java:193) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.tableRow(AbstractMavenReportRenderer.java:225) > at > org.apache.maven.report.projectinfo.ProjectSummaryReport$ProjectSummaryRenderer.renderBody(ProjectSummaryReport.java:109) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ProjectSummaryReport.executeReport(ProjectSummaryReport.java:39) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > 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) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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) -- 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
