Hi Marcel,
I doubt you will find all releases in dist. For example most of the
aries releases are missing there. Maybe this is an error.
I did not want to say that maven is the only place where the artifacts
are published. What I wanted to express is that maven central is the only
place where you can find all the artifacts in a structured way. For
example if you look at the artifacts in dist you often have no clue what
dependencies they need and where to get them.
So what I wanted to express is that maven is the only source I can
currently really rely on for my build. So it would be really great to be
able to back bndtools builds by a maven repo.
I am not sure how to handle the dependencies in that case but at least
there would be a clear place where to find the binaries.
This would also help a lot for eclipse features. So I think it would be
great if an eclipse update site would only contain the feature file that
points to maven coordinates for each artifact. This
would make the update sites a lot smaller. Additionally it would be
easier to use the artifacts outside of p2 deployments as at least each
file could be found in maven too.
Christian
On 12.12.2014 17:17, Marcel Offermans wrote:
Hello Christian,
On 12 Dec 2014 at 16:06:02 , Christian Schneider
(ch...@die-schneider.net <mailto:ch...@die-schneider.net>) wrote:
I am especially interested in using maven central as most of the apache
projects are only available there.
I’m sorry, but this is simply not true. All Apache projects are
actually required to publish their releases to apache.org/dist
<http://apache.org/dist> from where it will be picked up to all the
mirrors connected to that.
Publishing to Maven Central is completely optional (as is publishing
anywhere else).
Greetings, Marcel
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
