Hi Danushka, Digging in deep I found out that even though we have put gitblit as a dependency in all of the above, we have actually used it in org.wso2.carbon.appfactory.s4.integration and org.wso2.carbon.appfactory.repository components only.
So we can remove the dependency from other components. Regards GayanD On Thu, Oct 30, 2014 at 10:43 AM, Gayan Dhanushka <gay...@wso2.com> wrote: > Hi Danushka, > > Following are the components that use gitblit as a dependency. > > org.wso2.carbon.appfactory.s4.integration > org.wso2.carbon.appfactory.listners > org.wso2.carbon.appfactory.deployers > org.wso2.carbon.appfactory.repository > org.wso2.carbon.appfactory.stratos.listners > > I think we need to use the gitblit apis to do operations related to > gitblit. > > Regards > GayanD > > On Thu, Oct 30, 2014 at 10:28 AM, Danushka Fernando <danush...@wso2.com> > wrote: > >> Hi Gayan >> What are the components that we are depending on gitblit? Do we really >> need to depend on gitblit code? >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> On Thu, Oct 30, 2014 at 7:55 AM, Gayan Dhanushka <gay...@wso2.com> wrote: >> >>> Hi all, >>> >>> I am seeing the following error while trying to build App Factory >>> components with the latest gitblit dependency. >>> >>> BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 1:01.152s >>> [INFO] Finished at: Thu Oct 30 07:45:24 IST 2014 >>> [INFO] Final Memory: 54M/981M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >>> (default-compile) on project org.wso2.carbon.appfactory.s4.integration: >>> Compilation failure >>> [ERROR] error: Exception thrown while constructing Processor object: >>> ro/fortsoft/pf4j/ExtensionsIndexer : Unsupported major.minor version 51.0 >>> [ERROR] -> [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 >>> >>> >>> This exception does not occur when building with java 1.7. As per [1] >>> this occurs when we try to use a java program on top of java 1.6 when it >>> has been compiled with java 1.7. >>> >>> Is there anyway to get around this and add the latest gitblit >>> dependencies to App Factory code. >>> >>> [1] >>> http://www.mkyong.com/java/java-unsupported-major-minor-version-51-0/ >>> >>> thanks >>> GayanD >>> -- >>> Gayan Dhanuska >>> Software Engineer >>> http://wso2.com/ >>> Lean Enterprise Middleware >>> >>> Mobile >>> 071 666 2327 >>> >>> Office >>> Tel : 94 11 214 5345 >>> Fax : 94 11 214 5300 >>> >>> Twitter : https://twitter.com/gayanlggd >>> >> >> > > > -- > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd > -- Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
