I don't know off the top of my head why it wouldn't work, there must be
some deploy flags that were not specified.
The latest release procedure is documented here:
In 1.3.0, more sign / deploy steps were automated via Maven build steps, so
maybe something was lost when that change in the procedure was made. I
agree we should still deploy javadocs and sources for 1.3.0 and 1.3.1, if
On Sat, Apr 20, 2013 at 9:12 AM, Israel Ekpo <[EMAIL PROTECTED]> wrote:
> When building custom sinks, interceptors, channels and sinks for specific
> versions of Apache Flume, it would be nice to have the source for the
> classes attached after running running mvn eclipse:eclipse
> -DdownloadSources=true to set up the projects in Eclipse.
> I took a look at the Maven Central repository and it looks like the last
> time source jars were published alongside the class jars was in release
> Is there any reason why this was discontinued after 1.2.0
> I would like to update the pom files if needed or add additional steps to
> upload the source jars to Maven Central.
> Your feedback would be highly appreciated.
> Thank you.