[
http://issues.ops4j.org/browse/PAXRUNNER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12095#action_12095
]
Alin Dreghiciu commented on PAXRUNNER-208:
------------------------------------------
Status update:
Still to be done:
* find a "definitive" place for profiles repository and move them from
https://scm.ops4j.org/repos/ops4j/laboratory/users/adreghiciu/pax/runner/profiles-new
* cache or not the profiles locally. Maybe do not cache for the first release
and implement caching if requested later on.
> Refactor profiles
> -----------------
>
> Key: PAXRUNNER-208
> URL: http://issues.ops4j.org/browse/PAXRUNNER-208
> Project: Pax Runner
> Issue Type: Improvement
> Affects Versions: 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.6.0,
> 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0,
> 0.14.1, 0.14.2, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.17.2
> Reporter: Alin Dreghiciu
> Assignee: Alin Dreghiciu
> Fix For: 0.18.0
>
>
> The current implementation of profiles is no longer suitable to accommodate
> many profiles and dependencies between them. Also minus is that because the
> profiles are hardcoded in runner itself any change to profiles like
> correcting them or adding new ones requires a new version of pax runner to be
> released.
> To avoid this profiles will have to be refactored by allowing profiles to be
> downloaded/cached from public repositories (maybe also provide some minimum
> set of profiles in the pax runner distribution so profiles could be used
> without internet access).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
