[
https://issues.apache.org/jira/browse/TUSCANY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2212.
---------------------------------
Resolution: Fixed
It looks like specific work was done in 1.3.1 and 1.3.2 to address this issue.
If this is still an issue, let's open a Jira against a specific version of
Tuscany and try to resolve and reduce dependencies and size issues in that
specific release.
> SCA Java builds are getting very large
> --------------------------------------
>
> Key: TUSCANY-2212
> URL: https://issues.apache.org/jira/browse/TUSCANY-2212
> Project: Tuscany
> Issue Type: Improvement
> Components: Build System
> Affects Versions: Java-SCA-Next
> Reporter: ant elder
> Fix For: Java-SCA-Next
>
>
> As discussed on the ML SCA Java builds are getting very large. See
> http://apache.markmail.org/message/u7ebawcoicyqi55a
> Current size for me is 1.5GB so this jira is to track fixes to reduce that.
> Looking at the build and repo there's here's some things OTTOMH to start with:
> - the distribution build copies the distros to the target-last-successful
> folder. this is only needed for the continuum build and adds 120MB
> - where ever JMS is used the ActiveMQ default is persistence=true which adds
> about 50MB for the dbs, changing to persistence=false avoids that
> - a large amount of the mvn repository size is webapp samples but we don't
> need these installed into the mvn repo, is there a way to prevent that
> happening?
>
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
