[
https://issues.apache.org/jira/browse/ARIES-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross reassigned ARIES-1383:
Assignee: John Ross
> Provide option to disable the provisioning of dependencies at install time.
>
Hi all,
Just FYI I communicated with infra about this and the solution was to
go to https://cms.apache.org and force a new checkout of the repo.
Cheers,
David
On 17 August 2015 at 13:02, David Bosschaert wrote:
> Hi all,
>
> I wanted to edit the Aries website, which I normally do via the CMS
>
[
https://issues.apache.org/jira/browse/ARIES-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1382.
Resolution: Fixed
> Only allow jta annotations to configure transactions
> -
[
https://issues.apache.org/jira/browse/ARIES-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross updated ARIES-1383:
-
Description:
PROBLEM
-
The Subsystems specification states that all dependencies of a subsyst
John Ross created ARIES-1383:
Summary: Provide option to disable the provisioning of
dependencies at install time.
Key: ARIES-1383
URL: https://issues.apache.org/jira/browse/ARIES-1383
Project: Aries
Christian made a caveat in a previous message [1]. Given that, a bundle
version update will simply mean that the bundle is part of the X.X.X
release of the Z project and that something in the project changed.
[1]
>> For the bundle version I think the version policy described makes sense
>> in ge
Christian made a caveat in a previous message [1]. Given that, a bundle
version update will simply mean that the bundle is part of the X.X.X
release of the Z project and that something in the project changed.
[1]
>> For the bundle version I think the version policy described makes sense
>> in ge
Okay. We're clearly losing what is, in my opinion, useful meaning in the
bundle version, but this is a minor issue for me, and if a consensus has
already been reached then so be it.
> From: Jeremy Hughes
> To: dev@aries.apache.org
> Date: 08/19/2015 05:33 AM
> Subject: Re: Fw: Versioning Policy
Hi John, I went through the same feelings of trepidation at making
this change, but the reason for doing this in the first place is to
make the release process easier and provide a set of bundles that
users can know work together. So it's certainly a compromise from that
point of view. What is sacr
