Hi song, > However, the pom file in official released artifact is > https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo-maven/pom.xml > These 2 pom files are quite different, especially in the dependency scope > part.
You can package to generate an all-in-one dubbo jar, and the only difference lay in the pom.xml file, right? I think you have used the right way packing dubbo, take a closer look, the transitive dependencies passed by these two pom files are the same. So you will use the pom.xml different from the official one, and it makes no difference for end users. > So I wonder what is the normal release process for dubbo.jar? Is there some > configuration or step I missed? The release process to central repository for 2.5.x or above is a tricky one, that’s also one of the reasons that we changed the pom structure of dubbo project in 2.6.x. As mentioned above, use 'mvn clean install -DskipTests=true’ directly, and ignore the 'dubbo-maven/pom.xml’, a pom file only works for central maven repository. > On 8 May 2018, at 10:44 AM, ss宋顺 <[email protected]> wrote: > > Hi there, > > I have a patch<https://github.com/apache/incubator-dubbo/pull/1746> that > needs to be applied to our organization first. > So I use the normal way - 'mvn clean install -DskipTests=true' to package the > dubbo.jar (based on branch 2.5.x). > However, the pom file for the generated artifact is different from the one in > the official released artifact. > Specifically, the pom file in my generated artifact is > https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo/pom.xml > However, the pom file in official released artifact is > https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo-maven/pom.xml > These 2 pom files are quite different, especially in the dependency scope > part. > > So I wonder what is the normal release process for dubbo.jar? Is there some > configuration or step I missed? > Looking forward to your guidance! > > Thanks! > Jason
