We are using the OpenEJB snapshot as an embedded container for our integration
testing.
Currently we get the message
"[WARNING] The POM for
org.apache.openejb:openejb-core:jar:4.6.1-20140513.040854-160 is invalid,
transitive dependencies (if any) will not be available, enable debug logging
fo
Seems ok on repository.apache.org so maybe try to cleanup
4.6.1-SNAPSHOTs from your local repo
If you have big issues we can force a new deployment
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://git
I tried cleaning my local cache and made sure that our company apache archive
doesn’t hold copies of the openejp-SNAPSHOT.
When I build I get the warning:
[WARNING] The POM for
org.apache.openejb:openejb-core:jar:4.6.1-20140513.040854-160 is invalid,
transitive dependencies (if any) will not b
The build is running already ;-)
http://ci.apache.org/builders/tomee-trunk-deploy/builds/23
JLouis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, May 14, 2014 at 8:03 AM, Markus F. Frisch wrote:
> I think I found something:
>
> openejb-core-4.6.1-201
I think I found something:
openejb-core-4.6.1-20140513.040854-160.pom:
—
org.apache.openjpa
openjpa
—
But in openejb-4.6.1-20140514.040710-171.pom we find:
—
org.apache.openejb.patch
openjpa
${openj
That's correct. This will be the patched version 'required' for running under
Java 1.6, as OpenJPA currently has their snapshot and planned release for
Java 1.7+.
When we release TomEE 1.7.0 then this will be documented 'loudly' to ensure
everyone using OpenJPA updates their pom's accordingly.
As
Markus,
You also have to understand that 'depending' on a snapshot is generally not
a good idea. That doesn't mean snapshot builds are not a good idea, rather
wait for a green build on the buildbot here:
http://ci.apache.org/builders/tomee-trunk-ubuntu, then deploy your own
version of it somewher
@Andy: it doesn't work neither. Users relying on snapshot needs a new
feature and it is important to stick on new snapshots to limit risk of
potential regressions we sometimes had cause we fixed only a part of
the real issue and by side effect the app was no more working. So I
think either you use
Andy,
Yes, I am aware of that. We started using the SNAPSHOTs after we got a (for
us) critical bugfix on trunk.
The fix was in the trunk only four hours after we reported the bug which, by
the way, we found quite impressive. But we underestimated the effort (and
thus time) it takes to roll a relea
@Romain, it works as well as the end user deems fit at the end of the
day - There is such a thing as a stable snapshot, that is one that
passes all the tests that has ever been written so far, and all the end
user tests that they have for their own app. There is definitely no
black and white ru
Yep, just wanted to make it less obvious. Internal/custom releases are
not always possible - one sample is open source releases of EE
products. That said it just means we should continue what you started
to do (thank you for that) ie release more often ;)
Romain Manni-Bucau
Twitter: @rmannibucau
11 matches
Mail list logo
