Release 1.2

[mcculls]

Originally reported on Google Code with ID 63

Hi gusy,

there are several fixes that are really useful for us out there. Especially #37.
What about creating a new release? This would be very helpful for us.


Thanks

Reported by js.cedarsoft on 2011-09-14 12:11:04

[mcculls]

Reported by mcculls on 2011-09-16 01:48:01

• Status changed: Accepted

[mcculls]

FYI, I've staged a first build of peaberry 1.2 at https://oss.sonatype.org/content/repositories/orgops4j-143
so people can try it out and report any issues / inconsistencies. This is the first
release using the new OPS4J Maven setup, so there may well be things we need to tweak,
especially wrt API versioning.

Reported by mcculls on 2011-09-21 16:21:57

• Status changed: Started

[mcculls]

I have tried to use that version. But run into some problems.

Eclipse tells me that the extension point used to configure the modules, has now changed
to:

org.ops4j.peaberry.extensions.peaberry.eclipse.modules

But the modules are not recognized when using that one.

The value of 
org.ops4j.peaberry.eclipse.GuiceExtensionFactory#POINT_ID
is still the same.


I think that might be a problem?

Reported by js.cedarsoft on 2011-09-22 09:57:41

[mcculls]

Fixed the extension bundle symbolic names (extra segments had crept in) and restaged
1.2:

   https://oss.sonatype.org/content/repositories/orgops4j-027/

Reported by mcculls on 2011-09-22 19:06:30

[mcculls]

Thanks. First (very basic) tests seem to work fine.

Reported by js.cedarsoft on 2011-09-27 07:39:22

[mcculls]

Pushed to central: http://search.maven.org/#search%7Cga%7C1%7Cpeaberry - any regressions
can be fixed in 1.2.1

Reported by mcculls on 2011-09-30 20:56:27

• Status changed: Fixed