i deleted the dir javax.transaction from:
C:\Users\jcomp\.m2\repository\p2\osgi\bundle
because that is seen in the classpath:
C:\Users\jcomp\.m2\repository\p2\osgi\bundle\org.apache.commons.commons-dbcp2\2.7.0\org.apache.commons.commons-dbcp2-2.7.0.jar[+org/apache/commons/dbcp2/*
[INFO] Fetching javax.transaction_1.1.0.jar from
http://developer.servoy.com/p2_repository/ship_plugins/2019.12/plugins/ (22,27kB)
http://developer.servoy.com/p2_repository/ship_plugins/2019.12/plugins/javax.transaction_1.1.0.jari see this on both ends if i delete it, so also on jenkins i delete that same folder in the repo dir
then it also fetches the same jar, and i download the jar from that jenkinks repo dir to compare with mine localy repo one and that is the same..
So the javax.transaction jars on that location in the maven p2 repo is the same in both ends.
It is just very weird
if i look at the -X output of both builds
then the build on jenkins that fails if i search for javax/transaction
i get a hit on the -classpath argument
so this:
[DEBUG] Manifest BREEs: [OSGi profile 'JavaSE-1.8' { source level: 1.8, target level: 1.8}]
[DEBUG] Effective EE: OSGi profile 'JavaSE-1.8' { source level: 1.8, target level: 1.8}
[DEBUG] Effective source/target: 1.8/1.8
[DEBUG] Using compiler 'jdt'.
[DEBUG] Source directories: [/var/lib/jenkins/jobs/master/jobs/server/workspace/j2db_server/src]
[DEBUG] Classpath:
then a lot of stuff
and for:
xxxxxx;
/var/lib/jenkins/.m2/repository/p2/osgi/bundle/org.eclipse.osgi/3.15.0.v20190830-1434/org.eclipse.osgi-3.15.0.v20190830-1434.jar[+javax/transaction/*:+org/osgi/framework/*
a lot more paths and also +javax/transaction/xa/*:
but if i look that classpath entry (of osgi) on my local machine:
C:\Users\jcomp\.m2\repository\p2\osgi\bundle\org.eclipse.osgi\3.15.0.v20190830-1434\org.eclipse.osgi-3.15.0.v20190830-1434.jar[+org/osgi/framework/*
a lot more and then: +javax/transaction/xa/*;
But you see where it fails for some reason it is the first entry of the org.eclipse.osgi plugin......
(also a bit weird why that really is the first there..)
So at this stage the working on doesn't have it and the one that fails does have it at this level...
if i then search on on that classpath i encounter javax.transaction itself:
jenkinks:
/var/lib/jenkins/.m2/repository/p2/osgi/bundle/javax.transaction/1.1.0/javax.transaction-1.1.0.jar[+javax/transaction/xa/*:?**/*]
local:
C:\Users\jcomp\.m2\repository\p2\osgi\bundle\javax.transaction\1.1.0\javax.transaction-1.1.0.jar[+javax/transaction/*;+javax/transaction/xa/*;?**/*]
so there it is suddenly in reverse...
So that is the weird part here.. somehow that javax.transaction package is seen at some point as a exported package (for org.eclipse.osgi) but then it is somehow removed at javax.transaction plugin itself..
i can't run with: -Dtycho.localArtifacts=ignore because i have many projects that are builded locally that this one depends on again..
it tried deleting .cache/tycho dir but that didn't help
then i renamed the whole repository dir so i start full clean over..
Still the same problem, still javax.transaction has a access restriction on that package...
So how this is possible i don;t know what the actual difference is between the 2 maven builds
yes 1 is windows the other is linux, but both should be using the same java versions to compile against..
