[jira] (MNG-5454) cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in element 'executions'.
[ https://jira.codehaus.org/browse/MNG-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322094#comment-322094 ] Sebastien Tardif commented on MNG-5454: --- The problem started when upgrading from Spring Source IDE 3.1.x to 3.2.0. > cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in > element 'executions'. > -- > > Key: MNG-5454 > URL: https://jira.codehaus.org/browse/MNG-5454 > Project: Maven 2 & 3 > Issue Type: Bug > Components: POM >Affects Versions: 3.0.4 > Environment: springsource3.2.0_with_Juno3.8.2 >Reporter: Sebastien Tardif > > This generate an error: > > > maven-antrun-plugin >combine.self="override" > > > > default-cli > > > run > > > > > > > > > > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5454) cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in element 'executions'.
Sebastien Tardif created MNG-5454: - Summary: cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to appear in element 'executions'. Key: MNG-5454 URL: https://jira.codehaus.org/browse/MNG-5454 Project: Maven 2 & 3 Issue Type: Bug Components: POM Affects Versions: 3.0.4 Environment: springsource3.2.0_with_Juno3.8.2 Reporter: Sebastien Tardif This generate an error: maven-antrun-plugin default-cli run -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5420) Need to be able to specify running a specific execution by id
Sebastien Tardif created MNG-5420: - Summary: Need to be able to specify running a specific execution by id Key: MNG-5420 URL: https://jira.codehaus.org/browse/MNG-5420 Project: Maven 2 & 3 Issue Type: Improvement Affects Versions: 3.0.4 Reporter: Sebastien Tardif The limitation of not been able to specify executing an execution id of a plug-in is often mentioned. It's very obvious to be a missing feature when you are using a plug-ins that is generic like maven-antrun-plugin or maven*groovy. In other words, I may have a tiny ant script deleting some folders, then still also need the maven-antrun-plugin for other things like preparing a DB. It's insane to be stuck with only default-cli mechanism when all my "execution"s already have an identifier. Instead of been stuck with antrun:run, I should be able to do antrun:myExecutionId -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-624) automatic parent versioning
[ https://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311992#comment-311992 ] Sebastien Tardif commented on MNG-624: -- I agree that Jira shouldn't be used for advertising of services, but since this issue is visibly dragging a lot, even if having so many votes, and that somebody already committed to pay to get the issue resolved, the timing of complaining about this couldn't be worst ;-) As a positive point, at least it's not the assignee that slowed down a path to resolution. > automatic parent versioning > --- > > Key: MNG-624 > URL: https://jira.codehaus.org/browse/MNG-624 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Inheritance and Interpolation >Reporter: Brett Porter >Assignee: Ralph Goers >Priority: Blocker > Fix For: 3.2 > > Attachments: MNG-624-maven-2.0.x-r507648.patch, MNG-624-tests.tar.gz > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > (this may be bumped to 2.1 or even made WON't FIX as it is contentious - see > MNG-521) > currently, you have to specify the parent version when extending which makes > a project stand alone very easily, but has the drawback of being a > maintainance problem when you start development on a new version. Tools can > help, but it would be nice not to have to rely on them. > One alternative is to allow the parent version to be omitted, and when it is > it is assumed you want the latest. The parent is used from the reactor or the > universal source directory. IT may also be read from a LATEST in the > repository though this is contentious - it may be better to simply fail in > that environment and require builds be in a known checkout structure for > building individual projects. > This also introduces the need for tool support to populate the version on > release and deployment for reproducibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-701) NPE org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462)
[ https://jira.codehaus.org/browse/MECLIPSE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285320#comment-285320 ] Sebastien Tardif commented on MECLIPSE-701: --- The Eclipse bug was closed immediately by Igor, extract: please report m2e/wtp integration problems to https://issues.sonatype.org/browse/MECLIPSEWTP > NPE > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > > > Key: MECLIPSE-701 > URL: https://jira.codehaus.org/browse/MECLIPSE-701 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: M2Eclipse support >Affects Versions: 2.8 >Reporter: Sebastien Tardif > Attachments: EclipseIntegration.png, More installation info.png > > > Systematically get NPE when importing simple Maven project to Eclipse > SpringSource Tool Suite 2.8.0 release > Which use m2e 1.0.100.20110804-1717 > Same similar NPE with previous version of Maven integration. I do wonder for > the last 6 months if I'm the only one using Maven integration with Eclipse, > no kidding. > !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:04.383 > !MESSAGE An internal error occurred during: "Importing Maven projects". > !STACK 0 > java.lang.NullPointerException > at > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > at > org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) > at > org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) > at > org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) > at > org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) > at > org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:15.816 > !MESSAGE An internal error occurred during: "Updating Maven Configuration". > !STACK 0 > java.lang.NullPointerException > at > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > at > org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) > at > org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) > at > org.eclipse.m2e.core.ui.internal.UpdateConfigurationJob.runInWorkspace(UpdateConfigurationJob.java:87) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > pom.xml > 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/xsd/maven-4.0.0.xsd";> > 4.0.0 > com.onassignment.ops > functional.tests > jar > 0.0.1-SNAPSHOT > OPS Functional Tests > > > UTF-8 > > > > org.seleniumhq.selenium > selenium-java > 2.9.0 > > > junit > junit > 4.8.2 > test > > > cpsuite > cpsuite > 1.2.5 > test > > > > > http://maven.xwiki.org > http://maven.xwiki.org/externals > > > > >
[jira] Updated: (MECLIPSE-701) NPE org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462)
[ https://jira.codehaus.org/browse/MECLIPSE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastien Tardif updated MECLIPSE-701: -- Attachment: More installation info.png > NPE > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > > > Key: MECLIPSE-701 > URL: https://jira.codehaus.org/browse/MECLIPSE-701 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: M2Eclipse support >Affects Versions: 2.8 >Reporter: Sebastien Tardif > Attachments: EclipseIntegration.png, More installation info.png > > > Systematically get NPE when importing simple Maven project to Eclipse > SpringSource Tool Suite 2.8.0 release > Which use m2e 1.0.100.20110804-1717 > Same similar NPE with previous version of Maven integration. I do wonder for > the last 6 months if I'm the only one using Maven integration with Eclipse, > no kidding. > !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:04.383 > !MESSAGE An internal error occurred during: "Importing Maven projects". > !STACK 0 > java.lang.NullPointerException > at > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > at > org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) > at > org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) > at > org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) > at > org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) > at > org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:15.816 > !MESSAGE An internal error occurred during: "Updating Maven Configuration". > !STACK 0 > java.lang.NullPointerException > at > org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) > at > org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) > at > org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) > at > org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) > at > org.eclipse.m2e.core.ui.internal.UpdateConfigurationJob.runInWorkspace(UpdateConfigurationJob.java:87) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > pom.xml > 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/xsd/maven-4.0.0.xsd";> > 4.0.0 > com.onassignment.ops > functional.tests > jar > 0.0.1-SNAPSHOT > OPS Functional Tests > > > UTF-8 > > > > org.seleniumhq.selenium > selenium-java > 2.9.0 > > > junit > junit > 4.8.2 > test > > > cpsuite > cpsuite > 1.2.5 > test > > > > > http://maven.xwiki.org > http://maven.xwiki.org/externals > > > > > selenium > > http://repo1.maven.org/maven2/org/seleniumhq/selenium/ > > > > >
[jira] Created: (MECLIPSE-701) NPE org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462)
NPE org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) Key: MECLIPSE-701 URL: https://jira.codehaus.org/browse/MECLIPSE-701 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: M2Eclipse support Affects Versions: 2.8 Reporter: Sebastien Tardif Attachments: EclipseIntegration.png Systematically get NPE when importing simple Maven project to Eclipse SpringSource Tool Suite 2.8.0 release Which use m2e 1.0.100.20110804-1717 Same similar NPE with previous version of Maven integration. I do wonder for the last 6 months if I'm the only one using Maven integration with Eclipse, no kidding. !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:04.383 !MESSAGE An internal error occurred during: "Importing Maven projects". !STACK 0 java.lang.NullPointerException at org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) at org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.jobs 4 2 2011-10-27 10:32:15.816 !MESSAGE An internal error occurred during: "Updating Maven Configuration". !STACK 0 java.lang.NullPointerException at org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) at org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) at org.eclipse.m2e.core.ui.internal.UpdateConfigurationJob.runInWorkspace(UpdateConfigurationJob.java:87) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) pom.xml 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/xsd/maven-4.0.0.xsd";> 4.0.0 com.onassignment.ops functional.tests jar 0.0.1-SNAPSHOT OPS Functional Tests UTF-8 org.seleniumhq.selenium selenium-java 2.9.0 junit junit 4.8.2 test cpsuite cpsuite 1.2.5 test http://maven.xwiki.org http://maven.xwiki.org/externals selenium http://repo1.maven.org/maven2/org/seleniumhq/selenium/ org.apache.maven.plugins maven-surefire-plugin 2.10 **/AllTestsSuite*.java
