Hello, again.
After further investigation; I *do* see the JPA configurator feature in both repositories when I access them via Eclipse, but when I mirror the repositories I seem to lose the JPA stuff in Kepler. I’m using the same method (”…artifact.repository.mirrorApplication” and “…metadata.repository.mirrorApplication”) to mirror both repositories; any clue why I fail to get just JPA in my Kepler mirror? Is it perhaps a repository configuration issue, or are the p2 applications failing somehow?
Any hints are welcomed.
Thanks (again),
- Ian
From: Ian Trimble
Sent: Friday, February 22, 2013 4:37 PM
To: M2E-WTP Developers mailing list
Subject: Re: [m2e-wtp-dev] m2e-wtp 0.17.0 has been released
Hi, Fred.
In the Juno repository, I see the JPA feature/plugin, but I don’t see JPA in the Kepler repository. Is this an oversight, or is it packaged differently for Kepler?
Thanks,
- Ian
From: Fred Bricon [mailto:fbricon@xxxxxxxxx]
Sent: Wednesday, February 20, 2013 3:41 PM
To: Maven Integration for Eclipse users mailing list; M2E-WTP Developers mailing list
Cc: jbosstools-dev
Subject: [m2e-wtp-dev] m2e-wtp 0.17.0 has been released
Hot on the heels of m2e 1.3.1, here comes m2e-wtp 0.17.0.
0.17.0 is available in 2 flavors : Juno(and Indigo) [1] and Kepler [2]
The highlight of this release concerns the new JAX-RS, JSF and JPA configurators, contributed by JBoss Tools and available as optional features.
See the changelog[3] and New and Noteworthy[4] for more information on this release. A somewhat lengthier blog post is published at [5]
As usual please report any bugs to bugzilla[6]
--
"Have you tried turning it off and on again" - The IT Crowd