s/excluding the them/excluding them/g
On Fri, May 2, 2014 at 10:40 PM, Imesh Gunaratne <[email protected]> wrote: > Finally found the cause of this issue. The problem was with the maven > assembly plugin. We had used assembly plugin 2.2-beta-2 and it has included > target folders in source packages due to some reason. I upgraded it to > 2.2.1 and the problems was solved. > > However I found a different issue with this fix. In assembly plugin > version 2.2.1 the assembly id has been made mandatory. As a result the > build was failing after doing this fix. Now I have fixed all the assembly > xml files by adding the assembly ids and excluding the them from the > package file names. > > Thanks > > > On Fri, May 2, 2014 at 7:06 AM, Imesh Gunaratne <[email protected]> wrote: > >> Hi Devs, >> >> After doing some investigations I found that source packages generation >> logic is handled by the apache parent pom and it does not exclude target >> folders. >> >> Is this intentional? Really appreciate any thoughts on this. >> >> <profiles> >> <!-- START SNIPPET: release-profile --> >> <profile> >> <id>apache-release</id> >> <build> >> <plugins> >> <!-- Create a source-release artifact that contains the fully >> buildable >> project directory source structure. This is the artifact >> which is >> the official subject of any release vote. --> >> <plugin> >> <artifactId>maven-assembly-plugin</artifactId> >> <dependencies> >> <dependency> >> <groupId>org.apache.apache.resources</groupId> >> >> <artifactId>apache-source-release-assembly-descriptor</artifactId> >> <version>1.0.4</version> >> </dependency> >> </dependencies> >> <executions> >> <execution> >> <id>source-release-assembly</id> >> <phase>package</phase> >> <goals> >> <goal>single</goal> >> </goals> >> <configuration> >> <runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot> >> <descriptorRefs> >> >> <descriptorRef>${sourceReleaseAssemblyDescriptor}</descriptorRef> >> </descriptorRefs> >> <tarLongFileFormat>gnu</tarLongFileFormat> >> </configuration> >> </execution> >> </executions> >> </plugin> >> ... >> >> Thanks >> >> >> On Thu, May 1, 2014 at 7:12 PM, Imesh Gunaratne <[email protected]> wrote: >> >>> Hi Devs, >>> >>> Since we found a DISCLAIMER file issue in 4.0.0-RC1 we are now doing >>> another RC release build with fixes. Now I'm seeing the below error while >>> executing a release build: >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy >>> (default-deploy) on project stratos-parent: Failed to deploy artifacts: >>> Could not transfer artifact org.apache.stratos:stratos- >>> parent:zip:source-release:4.0.0-20140501.125729-11 from/to >>> apache.snapshots.https ( >>> https://repository.apache.org/content/repositories/snapshots): Failed >>> to transfer file: >>> https://repository.apache.org/content/repositories/snapshots/org/apache/stratos/stratos-parent/4.0.0-SNAPSHOT/stratos-parent-4.0.0-20140501.125729-11-source-release.zip. >>> Return code is: 400 -> [Help 1] >>> >>> It seems like the source release package includes the target folders. >>> I'm now working on this. >>> >>> Thanks >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Technical Lead, WSO2 >>> Committer & PPMC Member, Apache Stratos >>> >> >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PPMC Member, Apache Stratos >> > > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PPMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PPMC Member, Apache Stratos
