stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Imesh Gunaratne <im...@apache.org>
Subject Re: 4.0.0-RC2 Release Preparation Work
Date Sun, 04 May 2014 11:45:25 GMT
Finally the 4.0.0-RC2 release build was successful.

One thing to point out, the parent source package uploaded to staging
repository contains the .gitignore file. Do we need to do another build by
removing this? IMO since this is a file in the source repository it
shouldn't be a problem. WDYT?

Thanks


On Sun, May 4, 2014 at 11:29 AM, Imesh Gunaratne <imesh@apache.org> wrote:

> The build is failing again with HTTP 500 series errors, may be something
> to do with the Apache maven staging repository availability:
>
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 19:53.260s
> [INFO] [INFO] Finished at: Sun May 04 11:00:02 IST 2014
> [INFO] [INFO] Final Memory: 167M/766M
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
> project org.apache.stratos.cartridge.agent: Failed to deploy artifacts:
> Could not transfer artifact
> org.apache.stratos:org.apache.stratos.cartridge.agent:pom:4.0.0-incubating
> from/to apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/stratos/org.apache.stratos.cartridge.agent/4.0.0-incubating/org.apache.stratos.cartridge.agent-4.0.0-incubating.pom.
> Return code is: 502 -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
> with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible
> solutions, please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build
> with the command
> [INFO] [ERROR]   mvn <goals> -rf :org.apache.stratos.cartridge.agent
>
>
> On Sat, May 3, 2014 at 6:38 PM, Imesh Gunaratne <imesh@apache.org> wrote:
>
>> Build failed with a 503 error in Apache maven staging repo, will execute
>> a new one.
>>
>> ...
>> [INFO] [INFO] Apache Stratos - Manager - Parent ................. SUCCESS
>> [6.504s]
>> [INFO] [INFO] Apache Stratos - Profile Generation ............... FAILURE
>> [4:43.443s]
>> [INFO] [INFO] Apache Stratos - Distribution ..................... SKIPPED
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] Total time: 49:21.166s
>> [INFO] [INFO] Finished at: Sat May 03 15:49:03 IST 2014
>> [INFO] [INFO] Final Memory: 241M/899M
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on
>> project stratos-profile-gen: Failed to deploy artifacts: Could not transfer
>> artifact org.apache.stratos:stratos-profile-gen:pom:4.0.0-incubating
>> from/to apache.releases.https (
>> https://repository.apache.org/service/local/staging/deploy/maven2):
>> Failed to transfer file:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/stratos/stratos-profile-gen/4.0.0-incubating/stratos-profile-gen-4.0.0-incubating.pom.
>> Return code is: 503 -> [Help 1]
>> [INFO] [ERROR]
>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
>> with the -e switch.
>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> [INFO] [ERROR]
>> [INFO] [ERROR] For more information about the errors and possible
>> solutions, please read the following articles:
>> [INFO] [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [INFO] [ERROR]
>> [INFO] [ERROR] After correcting the problems, you can resume the build
>> with the command
>> [INFO] [ERROR]   mvn <goals> -rf :stratos-profile-gen
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>> On Sat, May 3, 2014 at 1:39 PM, Imesh Gunaratne <imesh@apache.org> wrote:
>>
>>> I have now fixed following and started a new release build:
>>> - Added DISCLAIMER files to each product
>>> - Added new INSTALL.txt and README.txt files to cartridge agent.
>>> - Added note to CLI README file to mention that it includes only one jar
>>> file containing all dependent java libraries.
>>>
>>>
>>>
>>>
>>> On Sat, May 3, 2014 at 5:57 AM, Lahiru Sandaruwan <lahirus@wso2.com>wrote:
>>>
>>>> Great work Imesh,
>>>>
>>>>
>>>> On Fri, May 2, 2014 at 11:18 PM, Imesh Gunaratne <imesh@apache.org>wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> We have now updated the parent pom.xml file to package the DISCLAIMER
>>>>> file into all the maven artifacts.
>>>>>
>>>>> *DISCLAIMER files were not present in product packages:*
>>>>> I executed a new release build with this modification and the
>>>>> DISCLAIMER file in source root folder was properly packaged into all
the
>>>>> jar files. However I found that it was not included in product packages.
>>>>> May be we need to update each product assembly configuration to do this.
I
>>>>> will fix this.
>>>>>
>>>>> *Source packages were including target folders:*
>>>>> As described in other mail thread, I also noticed a different issue
>>>>> with the source packages. Each source package has included its target
>>>>> folder with all the content. As a result the size of the root source
>>>>> package was over 40 GB. Due to this large file size the mvn deploy command
>>>>> failed. I have now fixed this by upgrading the assembly plugin version.
>>>>>
>>>>> *Assembly ID was mandatory:*
>>>>> The cause of the target folder issue was the maven assembly plugin
>>>>> version (2.2-beta-2). Once it was updated to 2.2.1, the assembly id became
>>>>> mandatory. I have now fixed this in all product assembly definitions.
>>>>>
>>>>> *Issue in CLI package structure:*
>>>>> I'm now seeing a problem with the CLI package structure. Will
>>>>> investigate this further:
>>>>>
>>>>>
>>>>>
>>>> We can include this using assembly plugin as we do for LICENCE and
>>>> NOTICE files AFAIU.
>>>>
>>>>> Thanks
>>>>> ‚Äč
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PPMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PPMC member, Apache Stratos(incubating),
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> 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

Mime
View raw message