On 04.07.2012 18:00, Peter Klügl wrote:
On 04.07.2012 17:23, Marshall Schor wrote:
On 7/4/2012 7:27 AM, Peter Klügl wrote:
On 03.07.2012 23:27, Marshall Schor wrote:
On 7/3/2012 8:39 AM, Peter Klügl wrote:
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.
I'm thinking that if we went this way, you would take some level of
Eclipse
release and post *all* of its parts (if that was allowed). I
thought that's
what the maven-eclipse-plugin -- to maven mojo did (but I haven't
used it, so
that's just a guess...). If that was the case, then no further
updates would be
needed unless or until you decided to "depend" on some more recent
Eclipse
plugin version / feature.
So, I'm not understanding why it would not scale well...
I thought that you have to provide a bundle with eight files for
each jar you
want to add to the Maven Central (I interpreted Richard's link that
way).
Those also cover javadoc and sources. Gathering all that stuff
manually for
each dependency would be some work. "eclipse:to-maven" adds the
artifacts to
the local repository. Maybe I missed something or we are talking about
something different.
OK - I haven't used eclipse:to-maven myself. I thought it might
gather all the
stuff needed automatically, and put it into the local repo, but
could, just as
easily, deliver it to maven central. But, I don't know...
That option would come handy, but I don't know about it either.
There is of course the parameter "deployTo", which we (someone with
rights) could probably use to fill the maven repository of the build
server without touching the eclipse installation there. I don't know,
but I doubt that we could fill any repository.
Peter
