Hi,
I don't know. On the one side, this would of course solve our problems.
On the other side, this approach does not scale well with the amount of
plugins the TextMarker IDE depends on. Additionally, I have the strong
feeling that "really many" developers of maven-built plugins propagte
the p2 repositories and that doing the opposite isn't the best way to go.
I'd propose that we keep the pom-first approach for the TextMarker
plugins for now (however I'll switch to eclipse:to-maven). I boost first
the status of the TextMarker projects so that a release is reasonable
(remaining issues, documentation). Then, we could find a solution how to
automatically build the projects, probably the way Marshall pointed out.
In the meanwhile, I also work a bit more on the manifest-first approach
when I find the time and I'm not too annoyed of it.
Peter
On 01.07.2012 12:05, Richard Eckart de Castilho wrote:
Am 28.06.2012 um 17:34 schrieb Peter Klügl:
Is a repository for the bundles an option for us?
How about doing a third-party deploy to Maven Central?
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
Apache also runs a Nexus instance, maybe that would be an option?
I'm not sure if there is any strict policy for Maven Repositories to keep
normal JARs and OSGi JARs separate from each other.
-- Richard
--
---------------------------------------------------------------------
Dipl.-Inf. Peter Klügl
Universität Würzburg Tel.: +49-(0)931-31-86741
Am Hubland Fax.: +49-(0)931-31-86732
97074 Würzburg mail: [email protected]
http://www.is.informatik.uni-wuerzburg.de/en/staff/kluegl_peter/
---------------------------------------------------------------------
