Community
Participate
Working Groups
the default mvn clean install do not work since we have a duplicate product item [ERROR] Failed to execute goal org.eclipse.rcptt:rcptt-maven-plugin:2.0.1:resources (default-resources) on project org.eclipse.papyrusrt.rcptt.tests: The explicit location /export/home/flefevre/gitNeon/org.eclipse.papyrus-rt/releng/org.eclipse.papyrusrt.rcptt/../papyrusrt.product/target/products/org.eclipse.papyrusrt.product-linux.gtk.x86_64.zip is not valid -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :org.eclipse.papyrusrt.rcptt.tests [flefevre@is227415 releng]$ ll /export/home/flefevre/gitNeon/org.eclipse.papyrus-rt/releng/org.eclipse.papyrusrt.rcptt/../papyrusrt.product/target/products/org.eclipse.papyrusrt.product-linux.gtk.x86_64.zip ls: impossible d'accéder à /export/home/flefevre/gitNeon/org.eclipse.papyrus-rt/releng/org.eclipse.papyrusrt.rcptt/../papyrusrt.product/target/products/org.eclipse.papyrusrt.product-linux.gtk.x86_64.zip: Aucun fichier ou dossier de ce type [flefevre@is227415 releng]$ ll /export/home/flefevre/gitNeon/org.eclipse.papyrus-rt/releng/org.eclipse.papyrusrt.rcptt/../papyrusrt.product/pom.xml
New Gerrit change created: https://git.eclipse.org/r/69255
Gerrit change https://git.eclipse.org/r/69255 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus-rt/org.eclipse.papyrus-rt.git/commit/?id=c58e88b0bb9cce2b16c8a8feb52cdaff4720a70c
(In reply to Eclipse Genie from comment #2) > Gerrit change https://git.eclipse.org/r/69255 was merged to [master]. > Commit: > http://git.eclipse.org/c/papyrus-rt/org.eclipse.papyrus-rt.git/commit/ > ?id=c58e88b0bb9cce2b16c8a8feb52cdaff4720a70c The fix was submitted in March, over 5 months ago. Can this bug be resolved/closed?
