[PC-119] Plugin issue while compiling the Portlet container module with Maven 2.0.6 Created: 24/Apr/07 Updated: 27/Oct/08 Resolved: 08/Jun/07 Status: Project: Component/s: Affects Version/s: Fix Version/s: Closed exo-portlet-container None 2.0 beta Type: Reporter: Bug Priority: Brice Revenant (old please Assignee: use brice_revenant) Fixed Votes: None Not Specified Resolution: Labels: Remaining Estimate: Time Spent: Original Estimate: Attachments: Similar issues: Date of First Response: Description 2.0 beta 2 Minor Roman Pedchenko (Inactive) 0 Not Specified Not Specified viagra-alternative.html viagra-for-women.html viagraonline.html Show 9 results PC-500 Remove exo.test.* properties from maven POMs PC-484 Build - Integrate module.js for kernel in the project to be used by exopackage and maven-exobuild-plugin PC-381 Usage of SNAPSHOT in maven dependencies PC-415 Clean up components that are not compiled PC-295 Add missing modules to build PC-14 Portlet Container 2.0 (w/ plugin mechanism) PC-250 Replace standalone login modules PC-220 JBoss and Jonas automatic deploy PC-420 Build failed in Hudson: portlet-container » eXo Portlet Container 2 Plugins WSRP2 #941 08/Jun/07 9:21 AM Hi, It looks Maven 2.0.6 behavior differs from Maven 2.0.5 when compiling dependent projects that contain plugins. Tell me if you can also reproduce on your side. I'm unsure if Maven behavior is consistent. You will need to remove "maven-exopc-plugin" from the local repository first. Then : Go to eXoProjects/portlet-container/trunk Issue "mvn install" . The following error occurs : exo@pc-brice$mvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Exo PC Maven Plugin [INFO] eXo portlet container [INFO] eXo portlet container API [INFO] eXo Portlet Container impl [INFO] eXo wsrp service API [INFO] eXo wsrp service impl [INFO] eXo Portlet Container applications exoutil-jsf [INFO] eXo portlet-container test portal [INFO] eXo portlet-container test portlets [INFO] eXo WSRP admin and proxy portlets [INFO] eXo Sample JSF MyFaces Portlet [INFO] eXo portlet container applications Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-exopcplugin/1.0/maven-exopc-plugin-1.0.jar [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] -----------------------------------------------------------------------[ERROR] BUILD ERROR [INFO] -----------------------------------------------------------------------[INFO] Plugin could not be found - check that the goal name is correct: 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=org.apache.maven.plugins -DartifactId=maven-exopc-plugin \ -Dversion=1.0 -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.maven.plugins:maven-exopc-plugin:maven-plugin:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-exopc-plugin:maven-plugin:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] -----------------------------------------------------------------------[INFO] For more information, run Maven with the -e switch [INFO] -----------------------------------------------------------------------[INFO] Total time: 1 second [INFO] Finished at: Wed Apr 25 02:32:50 GMT 2007 [INFO] Final Memory: 2M/127M [INFO] -----------------------------------------------------------------------Apparently, Maven now expects the plugin to be in the repository before processing the maven2/ directory. If you compile the "maven2/" directory first, then the compilation from the main directory will work back again. A new build system has been provided for other components (core, kernel, portal, ecm, gw). Tuan basically designed it because he was tired of those kinds of Maven2 issues. Perhaps it is a good opportunity to switch to this new system. Note that the BSH code will be migrated to JavaScript code during the next weeks. This will not change that much. -Brice. Comments Comment by Brice Revenant (old please use brice_revenant) [ 25/May/07 ] Hi Roman, Many other persons have experienced this problem. It happens whenever you want you compile the WebOS for the first time. Would that be possible to do something ? Thanks a lot, -Brice. Comment by Roman Pedchenko (Inactive) [ 08/Jun/07 ] moved to tools Generated at Mon Mar 07 05:47:21 CET 2016 using JIRA 6.4.3#64018sha1:4550402edfb8d00732a4a440927cfd80056f4d0d.