On Mon, Jan 24, 2011 at 13:08, Harshana Eranga Martin <[email protected]> wrote: > Hi Andreas, > > On 23 January 2011 17:18, Andreas Veithen <[email protected]> wrote: >> >> I don't see any issue with using this plugin, but I'm more worried >> about using the WSO2 Maven repository. While preparing the Rampart >> release we discovered that this repository contains artifacts with the >> same groupId/artifactId/version as artifacts in Maven central, but >> with different content [1]. This is a potential source for build >> instabilities. For Rampart we solved that by removing the WSO2 >> repository so that only artifacts from Maven central are used. I think >> that right now, none of the Axis2 projects use the WSO2 repository. > > Thanks for the explanation and I understand your concern here. > If we don't declare the WSO2 maven repository at the root pom level and > declare it only at the relevant module/sub module level, will maven still be > looking at WSO2 repository to resolve dependencies even outside of that > declared module/sub module? If not, there won't be any issues in using it > since I have declared it only at the newly added sub module level to resolve > the Carbon p2 maven plugin. > Thanks and Regards, > Harshana
The problem is that it is impossible to predict if it will break something and where the issue will surface. Yesterday I spent an hour debugging a failing unit test in CXF only to find out that the issue was caused by a pollution of my local Maven repository with an incorrect wsdl4j:wsdl4j:1.6.2 artifact from the WSO2 repository. There are a couple of examples [1] [2] of other repositories that caused very hard to debug issues with the Axis2 build, although they are much better managed than the WSO2 repository. In all these cases, we ended up removing them from the build. Are there no other plugins available from Maven central that have similar features? [1] http://markmail.org/thread/clyu2jp3iisv4kbo [2] http://markmail.org/thread/j6c3kw7fueihhjya >> >> Andreas >> >> [1] http://markmail.org/message/botp2pirxkvj7wap >> >> On Sat, Jan 22, 2011 at 10:50, Harshana Eranga Martin >> <[email protected]> wrote: >> > Hi All, >> > I'm delighted to inform you that I've completed this task. I need to >> > clarify >> > few things before submitting the patch. >> > For this task, I used the Carbon p2 maven plugin [0] which is licensed >> > under >> > ASL 2.0 and publically available at WSO2 maven repository[1]. Is there >> > any >> > issue using this maven plugin? >> > >> > [0]. http://wso2.org/svn/browse/wso2/branches/carbon/3.0.0/dependencies/carbon-p2-plugin/?pathrev=63544 >> > [1]. http://dist.wso2.org/maven2/org/wso2/maven/carbon-p2-plugin/ >> > >> > Thanks and Regads, >> > Harshana >> > >> > On 21 January 2011 10:58, Harshana Eranga Martin <[email protected]> >> > wrote: >> >> >> >> Hi All, >> >> I will go forward and will do the needful. Meanwhile I have created >> >> AXIS2-4937 [0] issue to track the progress of this task. >> >> [0]. https://issues.apache.org/jira/browse/AXIS2-4937 >> >> Thanks and Regards, >> >> Harshana >> >> >> >> On 20 January 2011 22:16, Saminda Wijeratne <[email protected]> wrote: >> >>> >> >>> +1 >> >>> Saminda >> >>> >> >>> On Thu, Jan 20, 2011 at 5:18 PM, Harshana Eranga Martin >> >>> <[email protected]> wrote: >> >>>> >> >>>> Hi All, >> >>>> Currently there are 2 Eclipse plugins as Axis2 Codegen plugin and >> >>>> Axis2 >> >>>> Service archive plugin under Axis2 tools and at the moment these >> >>>> plugins are >> >>>> distributed as zip archives. Eclipse users need to extract these >> >>>> zip archives and copy the jar files to the plugins folder of their >> >>>> Eclipse >> >>>> installation. >> >>>> Disadvantage in this approach is, inability to install the plugins if >> >>>> all the dependencies are not already contains in the users' Eclipse >> >>>> installation. For example this[0] is caused due to missing >> >>>> javax.activation >> >>>> and javax.xml.stream bundles/packages. >> >>>> As Andreas has explained in this [1] issue to solve this problem, we >> >>>> have to create Eclipse Features for these plugins so that the p2 >> >>>> based Eclipse update manager can automatically calculate and download >> >>>> the >> >>>> missing dependencies. >> >>>> So how about we create Eclipse Features and a p2 repository for Axis2 >> >>>> Eclipse plugins and distribute the Eclipse plugins via p2 repository. >> >>>> Devs, >> >>>> WDYT? >> >>>> >> >>>> [0]. http://markmail.org/message/bzkt6ylqcvqxznnn >> >>>> [1]. https://issues.apache.org/jira/browse/AXIS2-4916 >> >>>> >> >>>> >> >>>> Thanks and Regards, >> >>>> Harshana Martin >> >>>> -- >> >>>> Harshana Eranga Martin >> >>>> Software Engineer, >> >>>> WSO2 Inc. >> >>>> Web: http://wso2.com >> >>>> http://wso2.org >> >>>> ECF Committer: http://www.eclipse.org/ecf/ >> >>>> Blog: http://harshana05.blogspot.com >> >>>> Profile: https://www.google.com/profiles/harshana05 >> >>> >> >> >> >> -- >> >> Harshana Eranga Martin >> >> Software Engineer, >> >> WSO2 Inc. >> >> Web: http://wso2.com >> >> http://wso2.org >> >> ECF Committer: http://www.eclipse.org/ecf/ >> >> Blog: http://harshana05.blogspot.com >> >> Profile: https://www.google.com/profiles/harshana05 >> > >> > >> > >> > -- >> > Thanks and Regards, >> > Harshana Martin >> > -- >> > Harshana Eranga Martin >> > Software Engineer, >> > WSO2 Inc. >> > Web: http://wso2.com >> > http://wso2.org >> > ECF Committer: http://www.eclipse.org/ecf/ >> > Blog: http://harshana05.blogspot.com >> > Profile: https://www.google.com/profiles/harshana05 >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Thanks and Regards, > Harshana Martin > -- > Harshana Eranga Martin > Software Engineer, > WSO2 Inc. > Web: http://wso2.com > http://wso2.org > ECF Committer: http://www.eclipse.org/ecf/ > Blog: http://harshana05.blogspot.com > Profile: https://www.google.com/profiles/harshana05 > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
