Community
Participate
Working Groups
https://repo.eclipse.org/content/repositories/eclipse-staging/org/eclipse/jdt/ does contains core, compiler.apt and ecj but not compiler.tool. we use jdt for two purposes: - work with class and source file (ecj would be sufficient) - generate code with emf. emf needs `org.eclipse.jdt.core.formatter.CodeFormatter` thus we currently consume the 3 artifacts core, compiler.tool and compiler.apt. is there any reason the staging repo above does not contain compiler.tool?
Ist this a regression, or was this always like this?
i cannot tell this. we look for a way to consume preview versions/snapshots with maven
@Jay, @Sravan, s.t. you can settle between the two of you?
We never published compiler.tool till now. We started publishing ecj from last week as tycho moved to ecj for compilation. Our plan is to stop publishing jdt.core and compiler.apt once tycho 1.3.0 is out. Could you please let us know how you are consuming compiler.apt earlier?
see https://search.maven.org/artifact/org.eclipse.jdt/org.eclipse.jdt.compiler.tool/1.2.300/jar and https://search.maven.org/artifact/org.eclipse.jdt/org.eclipse.jdt.compiler.apt/1.3.300/jar artifacts are published to maven central for a while now. but only after releases. so there is nothing we can start using early for testing
This request is very similar to bug 534315. I would need some one from community to create necessary scripts to do this. The current process will not scale up with more libraries. I would like some one from community to take up this effort.
as far as i understood stephan already has the scripts. since eclipse/p2 does not distingush between snapshots and releases you could put pseudo releases to the staging repo on a regular basis.
(In reply to Christian Dietrich from comment #7) > as far as i understood stephan already has the scripts. > since eclipse/p2 does not distingush between snapshots and releases you > could put pseudo releases to the staging repo on a regular basis. See bug 534315 comment 2
