In case you're not following d...@ace.apache.org (an OSGi project too)
they're considering moving from Maven to BndTools. Given some of the
recent toiling with releases / semantic versioning / having many many
bundles to release I think it's worth watching how the discussion
goes.
Cheers,
Jeremy
On 26 June 2012 21:39, Holly Cummins wrote:
> With some liberal borrowing from the Felix script Guillaume pointed us
> to, I've converted Jeremy's release verification instructions
> (http://aries.apache.org/development/verifyingrelease.html) into a
> shell script. This should make it *much* easie
ource ...
What's the safest source: http://svn.apache.org/repos/asf/aries/KEYS
or dist/aries/KEYS ? Or do you mean a non-apache source?
Would gpg --import --interactive and perhaps --verbose help you?
>
> Regards
> Felix
>
> Am 28.06.2012 um 15:00 schrieb Jeremy Hughes:
+1 I checked & compiled.
On 28 June 2012 14:04, Mark Nuttall wrote:
> I've checked out the artifacts using the verify_staged_release.sh. All
> looks fine.
>
> +1
>
> Regards,
> Mark
>
> On 20 June 2012 23:12, Holly Cummins wrote:
>
>> I've staged a release candidate for the Aries 1.0.0 test supp
The util modules look odd. trunk/util used to be a single module with
no sub-modules and produced a single bundle. This is the first time
we're trying to release util since it changed to a multi-bundle
project. It hasn't followed the pattern of the rest of Aries and so
since this is a 1.0 release I
quot;bundle" artifact
> contains a lot of stuff all of which is intended to also be available
> separately. The util-42 artifact is compoletely useless by itself and should
> not be released.
Yes, that is a difference. Like you I'd prefer to not release util-42.
>
>
Date: 1 July 2012 17:30
Subject: ASF Board Report - Initial Reminder for Jul 2012
To: Jeremy Hughes
This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder to give you plenty of time to prepare the report.
The meeting is scheduled for Wed, 18 July 201
Things still feel a bit odd in Util. The release is for
org.apache.aries.util-parent 1.0.0 (when we released 0.4 it was
org.apache.aries.util but then I know we've changed util to be a multi
module project).
But, the tag for the release which is:
https://svn.apache.org/repos/asf/aries/tags/org.ap
This is the report I put together for the board meeting which has now
actually been postponed from 18th July to 25th July.
Cheers,
Jeremy
-- Forwarded message --
From: Jeremy Hughes
Date: 11 July 2012 18:01
Subject: [REPORT] Apache Aries report July 2012
To: ASF Board
Apache
+1 ... used the verify script and there's an error in the output, but
a rebuild of the offending javadoc works out fine.
On 5 July 2012 22:20, Holly Cummins wrote:
> I've staged a second release candidate for the Aries 1.0.0 util and
> blueprint.api bundles. The difference between this candidate
I thought blueprint-parser was just shaded into other bundle projects and
wasn't a bundle itself.
On Jul 14, 2012 11:24 AM, "Holly Cummins"
wrote:
> Hi all,
>
> As I was preparing the most recent batch of bundle releases, I noticed
> that the artifact id for blueprint-parser doesn't follow the sa
+1. I checked the release using the verify script and unzipped some
source release zips as a manual check. Looks good. Thank you!
On 13 July 2012 18:15, Holly Cummins wrote:
> I've staged a release candidate for the next round of Aries bundles.
> This set of releases is now starting to get into m
Hi John,
On 23 August 2012 13:54, John W Ross wrote:
>
>
> I would like to begin the work of integrating Subsystems into the Aries
> build. I would add Subsystems to the trunk/pom.xml file, probably as the
> last thing before the samples. I would then monitor the build and fix any
> issues that o
It's been pointed out that we have a large number of these files in
www.apache.org/dist/aries and that they don't serve any purpose. When
I looked again at
http://www.apache.org/dev/release-signing#check-integrity
I realised we only need:
.asc
.md5
.sha1
in fact we probably should have .sha512
w Apache projects
> whose release instructions said the files should be deleted, so I went
> ahead and removed them, and corrected our scripts so they don't get
> uploaded in future.
>
> Holly
>
> On Mon, Sep 17, 2012 at 3:43 PM, Jeremy Hughes wrote:
> > It's
Thanks John. I was wondering if there's anyway of supplying a simple switch
to go back to 3.7 or 3.5.
Cheers, Jeremy
On Oct 5, 2012 5:20 PM, "John W Ross" wrote:
>
>
> Note that starting with build 1701 [1], you see a reduction by half in the
> number of application itests being executed. This i
That's a nice idea and certainly the easiest thing to start with.
Thanks!
On 8 October 2012 16:34, John W Ross wrote:
>
> We define three profiles within the POM: equinox38, equinox37, and
> equinox35. Each profile would use the maven-paxexam-plugin and point to a
> particular version of equinox
Does anyone have anything they'd like to contribute / mention on the
board report. I need to submit today.
Thanks,
Jeremy
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
== Releases ==
Several release vote threads during the last three months saw the release of
88 bundles at version 1.0. These can be found from the downloads link on the
Aries home p
On 22 October 2012 11:01, David Bosschaert wrote:
> I'm not sure what the rules are here but if you can't propose it as a
> non-committer I would be happy to propose it for you.
>
> Anyone else any thoughts?
Sure. The voting process dictates whose votes are binding and I would
expect one of those
, it's a relatively small codebase and I'm an Apache
>> member with an ICLA on file. But I have no problem going through with it
>> if this is preferred. After all, I've guided a larger contribution
>> through back in 2006 already.
>>
>>
>> Jeremias
+1 good idea.
On Nov 21, 2012 6:48 PM, "John W Ross" wrote:
>
> As you may have noticed, this has been a particularly bad week for build
> stability. This was exacerbated by two outright failures today. The
> failures occurred, and always occur, when the build runs on ubuntu2 due to
> a (Too many
FYI
I've opened
https://issues.apache.org/jira/browse/INFRA-5571
due to the missing data in the source tab on our JIRAs.
Cheers,
Jeremy
Since we're now using the versioning plugin during the build I feel we
should add it to the pom.xml . Any objections?
Cheers,
Jeremy
Hi Emily,
[INFO] [dependency:tree {execution: default-cli}]
[INFO]
org.apache.aries.versioning:org.apache.aries.versioning.plugin:maven-plugin:0.1.0-SNAPSHOT
[INFO] +-
org.apache.aries.versioning:org.apache.aries.versioning.checker:jar:0.1.0-SNAPSHOT:compile
[INFO] | \- org.apache.aries:org.apa
FYI.
-- Forwarded message --
From: "ASF Board"
Date: Jan 2, 2013 4:19 PM
Subject: ASF Board Report - Initial Reminder for Jan 2013
To: "Jeremy Hughes"
Cc:
This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder t
I'll echo that. Thanks Emily!!
David, I had thought it used the versions in the generated manifest. I
could be wrong.
Cheers,
Jeremy
On 3 January 2013 12:23, David Bosschaert wrote:
> Excellent! Kudos to Emily and others who were involved in this!
> One question, does it only work with package-
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
Project update
* The SPI Fly component now fully implements the ServiceLoader Mediator
Specification 1.0 from the OSGi Enterprise R5 spec (chapter 133). It is
the Reference Implemen
The Maven release plugin defaults to incrementing the minor number and
resetting the micro number. You don't have top pick the default - it's an
interactive process - but maybe that's what happened :-)
On Feb 8, 2013 5:30 PM, "John W Ross" wrote:
>
> Okay, so the consensus is to have the util tru
On 10 February 2013 17:01, John W Ross wrote:
> Okay. I thought our versioning tool was doing this. We presumably have no
> control over the default settings in the maven release plugin and will need
> to remember to override the default.
The versioning tool checks the versions are semantically (
I'll be putting the report together early next week in the usual place.
Please let me know of anything that should be in the it.
Thanks.
Jeremy
I've just posted the report here:
http://aries.apache.org/overview/boardreports/april-2013.html and I'm about
to commit to the Board agenda. Please let me know if you want to change
anything.
Thanks,
Jeremy
On 1 April 2013 18:44, Jeremy Hughes wrote:
> I'll be putting t
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
* Apache Aries Subsystem 1.0.0
This is the reference implementation of the OSGi Subsystem Service
Specification which "provides a declarative model for defining resourc
+1 I just ran the verify_staged_release.sh script and all is good (once I
tweaked the script !!)
Thanks!!!
On 23 April 2013 16:03, John W Ross wrote:
>
> This vote requires at least two more +1 votes from PMC members. (My
> apologies is this is a dupe for anyone. I received a delivery failure
The subsystem source-release.zip contains enough 'source' to build and test
the release as required by the 'what must every ASF release contain?' The
very nature of the uber bundle is to pull together other bundles into one.
The bundle isn't built from .java source, it is built from the .class file
+1 .. if it helps some people and doesn't hurt the rest then it must be
good.
On 25 April 2013 17:04, John W Ross wrote:
>
> I agree, and, based on Stuart's response to your other note, it seems like
> he's at least okay with it.
>
> The infrastructure for generating the sources.jar is already
+1 I used the verify_staged_release.sh script again.
On 26 April 2013 09:03, David Bosschaert wrote:
> +1
>
> David
>
>
> On 25 April 2013 20:53, John W Ross wrote:
>
> >
> >
> > This is the second vote for the release of subsystem-bundle 1.0.0, an
> uber
> > bundle containing subsystem-api 1.
d Bosschaert +1
> Jeremy Hughes+1
> Mark Nuttall +1
> Stuart McCulloch +1
>
> Non-binding
> John Ross+1
>
> John
>
> >
> > [VOTE] subsystem-bundle 1.0.0 (2nd attempt)
> >
> >
> >
> > This is the second vote for the release of s
Hi Tim, in JIRA there's a set of roles. Every committer gets to go in the
'Committers' group role. There's a PMC role that can do more stuff
including administer the JIRA project. We've only added PMCers to the PMC
role when they've needed it rather than add them all up front. So I've
added you an
Holly, I just added you too.
John, since you've been a release manager I'm happy to add you into the
list individually - unless there's an objection.
On 1 May 2013 16:07, wrote:
> Yes, I never managed to create new versions when I did the 1.0.0 releases
> either. I kept meaning to sort it out a
On 1 May 2013 16:07, wrote:
>
> Yes, I never managed to create new versions when I did the 1.0.0 releases
> either. I kept meaning to sort it out and tidy that all up but never quite
> managed it. It seems like the permissions might be a gap in our process and
> at the very least PMC members sh
I see we still have the Aries Util tag awkwardness:
http://markmail.org/message/cukixfhhwnza773j (not a release stopper
though).
Also, I get issues building this with Java 7. Is anyone else getting that?
This is the error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-pl
I'd +1 if we know the binaries built with Java 6 test ok with Java 7
JRE. But I can't see that would be very easy to do.
On 2 May 2013 12:30, Timothy Ward wrote:
> Having thought I was doing the whole release with Java 7, it turns out that
> an update reset my JAVA_HOME. I can't build with Java
Hi Tim,
On 6 May 2013 20:42, Timothy Ward wrote:
> General consensus is that we should upgrade the maven-compiler-plugin to 3.1.
> I will start to ripple changes through trunk so that it is possible to build
> everything from source using JDK 7. This will mean that *everything* has to
> be re-r
Yes, there's a part of the release process (maybe it's not clear)
where scripts/create_modules_table.pl is run to generate the info for
that page.
On 28 May 2013 15:12, David Bosschaert wrote:
> On 28 May 2013 14:43, Daniel Kulp wrote:
>
>>
>> On May 27, 2013, at 10:18 AM, David Bosschaert
>> w
Hi David,
I made some comments and votes largely in line with what's been discussed...
On 4 June 2013 12:24, David Bosschaert wrote:
> On 28 May 2013 14:43, Daniel Kulp wrote:
>
>>
>> On May 27, 2013, at 10:18 AM, David Bosschaert
>> wrote:
>> > Downloads
>> > * This page was last updated for
Hi Guillaume,
Could you say why you've bumped the version in:
blueprint/blueprint-parser/src/main/java/org/apache/aries/blueprint/packageinfo
from 1.1 to 1.2. ExtendedBlueprintContainer is the only class in
org.apache.aries.blueprint and that hasn't been changed. Unless
there's something I've ov
I see what's going on now. blueprint-parser classes are inserted into
the blueprint-core bundle and you've added a method to one of those.
I'm just realising the code from blueprint-parser in
org.apache.aries.blueprint is effectively API from the uber bundle.
Jeremy
On 1 July 201
Hi everyone, please let me know of anything you'd like included in the
board report. I'll put a draft together later.
Thanks,
Jeremy
ctive Aries blog.
> I've also updated the 'programming model' page to be a more comprehensive
> (but high-level) list of technologies available in Aries:
> http://aries.apache.org/documentation/ariesprogrammingmodel.html
>
> Anyone: feel free to make additional changes.
OK forget that. Either my browser was playing up or the publish I just
did for the July board report kicked it all into action.
On 10 July 2013 22:38, Jeremy Hughes wrote:
> Hi David, I was looking at the Aries home page and thought 'hang on
> didn't David update this to refer to
Dear Board, please find below the Apache Aries board report for July.
It is also checked into the board agenda file.
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
* Apache Aries Subsystems Bundle 1.0.0
This is an
Our board report is due on 9th Oct. Please let me have anything you'd
like to include.
Thanks!
Jeremy
-- Forwarded message --
From: ASF Board
Date: 29 September 2013 20:28
Subject: ASF Board Report - Initial Reminder for Oct 2013
To: Jeremy Hughes
This email was sent
+1 (ran the verify_staged_release.sh)
btw: had problems building with mvn 3.1.0 ... ok with 3.0.3
On 10 October 2013 12:57, John W Ross wrote:
> +1
>
>>
>> [VOTE] blueprint.cm 1.0.2
>>
>>
>> This vote is to release blueprint-cm 1.0.2. The only change is to
>> update the manifest to allow the i
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
* Apache Aries Blueprint Parser 1.1.0
Reusable component for parsing Blueprint xmls.
* Apache Aries Blueprint Core 1.2.0
Core of the implementation of the OSGi Bl
Sorry for the delay. It's working for me right now.
On 11 December 2013 22:28, wrote:
> http://aries.apache.org/modules/blueprintweb.html
>
Just seen that we have a board report to do for ahem today. Please let me
know if there's anything specific you'd like to add and I'll submit
tomorrow.
Thanks,
Jeremy
On 1 Jan 2014 14:17, "ASF Board" wrote:
>
>
> This email was sent by an automated system on behalf of the ASF Board.
> It is an i
Please find the Apache Aries board report for January 2014 below. Apologies
for the lateness of the report. No one particular reason, mostly catching
up after the new year. Thanks.
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
Hi, we have a problem building with Maven 3.1.x and some modules have
a problem with Java 7. Could you try with Maven 3.0.5 and Java 6?
Thanks,
Jeremy
On 22 January 2014 14:32, Giuseppe Gerla wrote:
> Hi all
> I need to use eclipselink 2.5.1 in Karaf container.
> I try to use Aries Jpa 1.0.0 and
Would moving to the latest pax-exam help (v3.4) Wondering whether the two
bumps in major version number mean a lot of API breaking changes.
Cheers,
Jeremy
On 28 March 2014 10:44, David Bosschaert wrote:
> I ran into the same issue recently with the Blueprint itests. I was
> able to work around
There's a long discussion on the members@ list.
https://mail-search.apache.org/members/private-arch/members/201311.mbox/%3c9cc82400-9a4b-4de3-a502-c18a7c6a3...@gmail.com%3E
(sorry that's a private list).
This summarises it:
https://issues.apache.org/jira/browse/LEGAL-156
Cheers,
Jeremy
On 28
gt; It definitely would help ;)
> > Though yes there are some API breaking changes and you'll need to rework
> > your POM a bit.
> > Still I think this switch is really worth it.
> >
> > Regards, Achim
> >
> >
> > 2014-03-28 11:49 GMT+01:00 J
Hi everyone, I'm currently on vacation. Would anyone of the committers
volunteer to put together a board report and submit it before Wednesday?
Previous ones are here http://aries.apache.org/overview/boardreports.html
I'd really appreciate it. Massive thanks.
Jeremy
This email was sent by an au
On 5 June 2014 19:06, Daniel Kulp wrote:
>
>
> Everything should now compile with Java6 and Maven 3.2.1.
>
> Tests are another story……..
>
I think some of this has to do with using Equinox 3.5.0 in tests. Now
that we default to OSGi 4.3.1 our bundles are doing Import-Packge:
org.eclipse.osgi;vers
The Aries PMC has voted in Tom Watson as committer, who you may know
as Eclipse Equinox Project co-lead.
Congratulations Tom, thanks for your contributions and welcome!
Jeremy
+1.
Does this mean those circular dependency errors go away?
On 10 Jun 2014 16:12, "Daniel Kulp" wrote:
>
>
> With the updates to the versioning stuff to support the newer ASM version
> and the updates to the plugin to allow it to be fully defined in the
> parent, do we think we’re ready to get t
+1 looks good. Thanks.
On 11 June 2014 18:00, Daniel Kulp wrote:
>
> This is a vote to release 0.3.0 of the versioning plugin.
>
> The two major changes for this version are:
>
> 1) Update to support Java 8
> 2) Update to provide “skip” functionality/option and only to compare bundle
> package t
Hi Christian, so what is the error with Java 6? Does it only appear
when moving to pax exam 3? Do you think there might be an issue with
pax exam 3 and Java 6? We could override the pax exam level to one
that works with Java 6 and 7 (if that exists :-)
On 16 June 2014 05:20, Christian Schneider w
Hi, it's true that Oracle's Java 6 is EOL. There are other vendors,
such as IBM who haven't EOL'd Java 6 yet:
According to https://www.ibm.com/developerworks/java/jdk/lifecycle/index.html
they will service it until Sep 2017. I'd like to make sure we can
continue to run / test on Java 6 until then.
ial Reminder for Jul 2014
To: "Jeremy Hughes"
Cc:
This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder to give you plenty of time to prepare the report.
The meeting is scheduled for Wed, 16 July 2014, 10:30:30:00 PST and the
deadline for
su
:)
>
> David
>
> On 26 June 2014 07:38, Jeremy Hughes wrote:
>> FYI our Board report is coming up. Please let me know anything particularly
>> exciting you'd like included. I'll also go through the mailing lists.
>>
>> Thanks,
>> Jeremy
>>
After the release candidate artifacts are posted, module poms have their
version bumped up. So parent is now 2.0.1-SNAPSHOT. Modules that are being
released at the same time were depending on 2.0.0-SNAPSHOT and moved to
depend on 2.0.0 as part of their own release process. Which is fine for
reviewi
Generally speaking, module dependencies on other Aries modules should
be at the minimum required level for them to function correctly. Then
using the -Pdev profile should bring those dependency versions up to
the latest snapshot levels.
blueprint-itests should be the same - when you run the tests
Please find the Apache Aries board report for July 2014 below.
Apologies for being a few days late.
# July 2014 Board report
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
There was a significant amount of release a
+1
On 17 July 2014 18:40, Daniel Kulp wrote:
> +1
>
> Dan
>
>
> On Jul 16, 2014, at 3:40 PM, Jean-Baptiste Onofré wrote:
>
> > Hi all,
> >
> > I submit the following release to your vote:
> >
> > Aries JPA API 1.0.1
> > ---
> > ChangeLog:
> > [ARIES-1047] Add JPA 2.
Hi Guillaume, this would be great. I've been applying a few patches over
the last couple of days. I'd like to take a look at these ones:
1201
1204
1242
1243
and if good, I'll get them in today.
Thanks,
Jeremy
On 12 September 2014 10:49, Guillaume Nodet wrote:
> We have a few issues solved bu
Hi. I committed those patches.
Thanks
On 12 Sep 2014 11:28, "Jeremy Hughes" wrote:
> Hi Guillaume, this would be great. I've been applying a few patches over
> the last couple of days. I'd like to take a look at these ones:
>
> 1201
> 1204
> 1242
> 124
Guillaume, since putting the fix for ARIES-1068 I found an issue that isn't
showing up in the tests. I need to figure out a testcase for it, but for
now I think it's best to pull the fix and respin the jndi-core bundle
release. ARIES-1068 is a performance fix when security is enabled.
Jeremy
On 1
e, I'll remove jndi-core from the staging repo and respin a release and
> vote for that bundle when you tell me it's ready.
>
> 2014-09-17 12:03 GMT+02:00 Jeremy Hughes :
>
> > Guillaume, since putting the fix for ARIES-1068 I found an issue that
> isn't
> &g
Hi everyone, the board report deadline is 8th October. Please respond with
anything you particularly want to get included.
Thanks,
Jeremy
This email was sent by an automated system on behalf of the ASF Board.
It is an initial reminder to give you plenty of time to prepare the report.
The meetin
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## New modules
Aries Blueprint Authz: An Aries Blueprint extension that supports role
based access control based on a JAAS login and the JEE @RolesAllowed
annotation.
## Releases
#
I agree, something should be done. Apache Felix seem to have an up to date
downloads page. Is that automated in some sense? They have a large number
of subprojects like us, so it would be good to do something similar.
On 13 January 2015 at 10:20, David Bosschaert
wrote:
> Hi all,
>
> The followi
I'm sorry I've missed organising the board report this month. We'll have to
report next month then back on schedule the month after.
I'll set up a page for Feb board report - please add any content you'd like
reported.
Cheers,
Jeremy
Please use CMS to edit this:
http://aries.apache.org/overview/boardreports/feb-2015.html
Thanks.
On 20 January 2015 at 22:13, Jeremy Hughes wrote:
> I'm sorry I've missed organising the board report this month. We'll have
> to report next month then back on schedule the
I've just sent the board report for February. Next report is due 8th April.
-- Forwarded message --
From: Jeremy Hughes
Date: 13 February 2015 at 14:30
Subject: Apache Aries board report Feb 2015
To: ASF Board
Here is our report:
# February 2015 Board report
Apache
I've been digging around in my memory. The Quiesce capability is a like a
soft-stop. It's a generic capability that is enforced differently depending
on the context. It's more normal for an extender to implement the
QuiesceParticipant rather than an individual bundle. In the case of the
Blueprint e
Hi, I've just bumped the jmx-core-whiteboard dependency on jmx-core
from 1.1.3-SNAPSHOT to 1.1.4-SNAPSHOT. It seems that's been the
pattern recently. But I think this is against our 'depend on the
minimum version' policy. jmx-core-whiteboard should only be depending
on jmx-core @ 1.1.0 as that is t
Hi guys, is there any reason to tie this down to Java 7. I've built
with Java 6 and all looks good.
On 16 March 2015 at 15:49, wrote:
...
> +
> +
> +
> + org.apache.maven.plugins
> + maven-co
Cool. Done. Thanks.
On 1 April 2015 at 14:19, David Bosschaert wrote:
> I've committed this on behalf of Kamesh Sampath the other day. I guess
> if it works fine with Java 6 then there is no reason to force Java 7.
>
> Cheers,
>
> David
>
> On 1 April 2015 at 14:17
Hi,
Simplifying the release process would definitely be good. I'd like to
know the detail of what you're suggesting. I think you're saying that
a release of (say) Aries JPA would contain all the artifacts the child
modules release today... plus tests plus samples. The release would be
a src and a
On 22 May 2015 at 16:15, Daniel Kulp wrote:
>
>> On May 21, 2015, at 11:44 AM, Jeremy Hughes wrote:
>>
>> Hi,
>>
>> Simplifying the release process would definitely be good. I'd like to
>> know the detail of what you're suggesting. I think you
may not have been tested with (although
if the others haven't changed the risk should be minimal).
>
> Christian
>
> On 22.05.2015 18:25, Jeremy Hughes wrote:
>>
>> Some consequences: every release we do we'll bump the bundle version
>> numbers so they'
Hi Sebastian, I guess I wasn't watching when the discussion happened
in April - sorry about that. We had a discussion before then about the
quiesce scenario with JPA. I see that the quiesce modules are no
longer used by JPA. Can you describe how quiesce is now achieved in
the new implementation. Wi
of the EMF and EM. So it is a lot easier to understand and there is
> less room for problems. If we would implement Quiesce then we probably would
> have to introduce such proxies again with all the problems they bring.
>
> Christian
>
>
> On 18.06.2015 15:19, Jeremy Hugh
I'd like to move this back into trunk alongside the new Aires JPA
implementation. The new JPA module/s depend on Java 7 and we still use
Java 6 (as well as 7 and 8). Yes, I know Oracle no longer support Java
6 but IBM (and maybe others) still do.
I want to keep with the approach of 'trunk-based-de
I actually thought we had some, but can't find them right now. Without
wanting to start the usual war of personal preference ... I'm happy as
long as tabs are disallowed and the rules roughly match the majority
of code we have - avoiding a full-blown code reformatting exercise.
On 7 July 2015 at 0
Hi, the board report is due tomorrow. Please let me know what items
you'd like to add. I will of course include all the releases from the
past 3 months.
Thanks,
Jeremy
rules as eclipse
> formatters and do not enforce them.
>
> We could then reformat source files when there are bigger changes. For
> smaller changes we should try to keep the original formatting of files to
> avoid bigger diffs.
>
> WDYT?
>
> Christian
>
>
> On 0
Hi,
We had a discussion at the end of May about changing out release
process to release at the top level module only. I've just realised
this release vote was for sub-modules and that really we should have
done a full Blueprint release.
Christian, that was the intent wasn't it?
I guess next time
le is not converted I propose we continue doing releases
> in the per bundle style. So we have a smooth transition and do not hold off
> releases.
>
> Christian
>
>
> On 13.07.2015 14:37, Jeremy Hughes wrote:
>>
>> Hi,
>>
>> We had a discussion at the end
1 - 100 of 594 matches
Mail list logo
