jaxws-api look same javax.xml.ws but when build with tycho it said about access restriction on package javax.xml.ws,..
(i guess jaxws-api is new and it follow jdk mudule)
javax.xml.ws is special package, it's marked for remove on next jdk release.
it can't resolve ever i use <arg>-warn:+discouraged,forbidden</arg>
update jetty to 12
update almost library to latest version
change org.eclipse.jdt.core.compiler.batch to org.eclipse.jdt.core
change javax.management.j2ee-api to org.apache.geronimo.specs.geronimo-j2ee-management_1.1_spec, reduce dependency and correct dependency of activeMQ
javax.activation to com.sun.activation.javax.activation
lib for service will take from library instea of jdk
groovy to date
+ add more Osgi for jasper dependency
+ don't fix incompatibility issue for swing
+ use bootdelegation to resolve org.w3c.dom.events issue. let all use class from jdk
online and offline taget platform with parameter
wire org.apache.lucene.core to 3.5.0.v20120725-1805 (match with current org.apache.lucene.analysis)
target file become simple because don't neeed filter out bundle
for maven build, taget just need to define url to repository
for eclipse
1. deselect lower version of singleton bundle in case have multi version
2. Some bunlde have multi version, lancher will auto pickup latest version, but dependency need older version, so deselect all new version
3. sourceforge.net is got trouble nowaday, so can't test remote repository
hieplq