Thanks Nirmal.  Are you or someone going to handle the jclouds upgrade for 
Stratos?   I can see on the jclouds email alias that Udara is also doing 
something with the neutron API for Stratos.

Hi Udara,
I saw your post on the jclouds alias about testing neutron API on jclouds 
1.7.4.   I assume you were able to upgrade jclouds successfully.  Can you share 
some tips on the changes you made to get pass the build error?  Did you end up 
fixing the jclouds forks?

Thanks,
-Jeffrey


From: Nirmal Fernando <nirmal070...@gmail.com<mailto:nirmal070...@gmail.com>>
Reply-To: "dev@stratos.apache.org<mailto:dev@stratos.apache.org>" 
<dev@stratos.apache.org<mailto:dev@stratos.apache.org>>
Date: Monday, August 18, 2014 10:37 AM
To: dev <dev@stratos.apache.org<mailto:dev@stratos.apache.org>>
Cc: "lak...@wso2.com<mailto:lak...@wso2.com>" 
<lak...@wso2.com<mailto:lak...@wso2.com>>
Subject: Re: Time to upgrade jclouds?

IMO if we need new improvements in latest versions, we should go for it.

For the error you got, I think if we upgrade Jclouds, we should upgrade the 
forked code too. This error is probably due to some version mismatching.


On Mon, Aug 18, 2014 at 10:53 PM, Jeffrey Nguyen (jeffrngu) 
<jeffr...@cisco.com<mailto:jeffr...@cisco.com>> wrote:

Hi Lakmal,

What's our plan for upgrading jclouds?

-Jeffrey

From: jeffrngu <jeffr...@cisco.com<mailto:jeffr...@cisco.com>>
Reply-To: "dev@stratos.apache.org<mailto:dev@stratos.apache.org>" 
<dev@stratos.apache.org<mailto:dev@stratos.apache.org>>
Date: Thursday, August 14, 2014 10:44 PM
To: "dev@stratos.apache.org<mailto:dev@stratos.apache.org>" 
<dev@stratos.apache.org<mailto:dev@stratos.apache.org>>
Subject: Time to upgrade jclouds?

Hi,

I was just wondering when we're going to upgrade jclouds.   Stratos currently 
uses jclouds 1.7.1 with a couple of jclouds forks.   Some of these should be 
available in latest release of jclouds (1.8.0).   I think last time we upgraded 
to version 1.7.1 was around March.

I'm working on an enhancement that allows launching a cartridge with fixed MAC 
addresses attaching to their respective NICs.   This requires neutron API which 
is only supported in jclouds 1.7.3 and beyond.   In fact, some of the neutron 
API in version 1.7.3 were deprecated.   The recommended version is 1.8.0 which 
was released on August 5th.

In my copy of Stratos repository, I changed jclouds version to 1.7.3 in the top 
level pom.xml and built.  The build failed with the error below.   Any idea how 
to resolve this?

[INFO] Apache Stratos - Profile Generation ............... FAILURE [1:36.650s]
[INFO] Apache Stratos - Distribution ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7:14.652s
[INFO] Finished at: Thu Aug 14 21:15:44 PDT 2014
[INFO] Final Memory: 265M/1016M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen (p2 profile generation for 
CC) on project stratos-profile-gen: P2 publisher return code was 13 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen (p2 profile generation for 
CC) on project stratos-profile-gen: P2 publisher return code was 13
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher return 
code was 13
at org.wso2.maven.p2.ProfileGenMojo.execute(ProfileGenMojo.java:180)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher return 
code was 13
at org.wso2.maven.p2.ProfileGenMojo.installFeatures(ProfileGenMojo.java:222)
at org.wso2.maven.p2.ProfileGenMojo.execute(ProfileGenMojo.java:170)
... 21 more
[ERROR]
[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/MojoExecutionException

-Jeffrey




--
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/

Reply via email to