You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Israel Ekpo <is...@aicer.org> on 2013/04/20 18:12:14 UTC
Missing Source JAR Files for Flume Artifacts in Maven Repository
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
1.2.0
http://search.maven.org/#search%7Cga%7C1%7Cflume
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.
Re: Missing Source JAR Files for Flume Artifacts in Maven Repository
Posted by Mike Percy <mp...@apache.org>.
Thanks Israel for filing the JIRA! We do the releases, not INFRA.
Mike
On Tue, Apr 23, 2013 at 7:46 AM, Israel Ekpo <is...@aicer.org> wrote:
> The JIRA Task has been created.
>
> https://issues.apache.org/jira/browse/FLUME-2021
>
>
>
>
> On 23 April 2013 10:43, Israel Ekpo <is...@aicer.org> wrote:
>
> > Thanks Mike.
> >
> > I will create a JIRA task to track this.
> >
> > Do we need to assign this to INFRA?
> >
> >
> >
> >
> > On 23 April 2013 02:33, Mike Percy <mp...@apache.org> wrote:
> >
> >> Israel,
> >> 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:
> >> https://cwiki.apache.org/confluence/display/FLUME/How+to+Release
> >>
> >> 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
> >> possible.
> >>
> >> Regards,
> >> Mike
> >>
> >>
> >> On Sat, Apr 20, 2013 at 9:12 AM, Israel Ekpo <is...@aicer.org> 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
> >> > 1.2.0
> >> >
> >> > http://search.maven.org/#search%7Cga%7C1%7Cflume
> >> >
> >> > 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.
> >> >
> >>
> >
> >
>
Re: Missing Source JAR Files for Flume Artifacts in Maven Repository
Posted by Israel Ekpo <is...@aicer.org>.
The JIRA Task has been created.
https://issues.apache.org/jira/browse/FLUME-2021
On 23 April 2013 10:43, Israel Ekpo <is...@aicer.org> wrote:
> Thanks Mike.
>
> I will create a JIRA task to track this.
>
> Do we need to assign this to INFRA?
>
>
>
>
> On 23 April 2013 02:33, Mike Percy <mp...@apache.org> wrote:
>
>> Israel,
>> 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:
>> https://cwiki.apache.org/confluence/display/FLUME/How+to+Release
>>
>> 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
>> possible.
>>
>> Regards,
>> Mike
>>
>>
>> On Sat, Apr 20, 2013 at 9:12 AM, Israel Ekpo <is...@aicer.org> 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
>> > 1.2.0
>> >
>> > http://search.maven.org/#search%7Cga%7C1%7Cflume
>> >
>> > 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.
>> >
>>
>
>
Re: Missing Source JAR Files for Flume Artifacts in Maven Repository
Posted by Israel Ekpo <is...@aicer.org>.
Thanks Mike.
I will create a JIRA task to track this.
Do we need to assign this to INFRA?
On 23 April 2013 02:33, Mike Percy <mp...@apache.org> wrote:
> Israel,
> 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:
> https://cwiki.apache.org/confluence/display/FLUME/How+to+Release
>
> 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
> possible.
>
> Regards,
> Mike
>
>
> On Sat, Apr 20, 2013 at 9:12 AM, Israel Ekpo <is...@aicer.org> 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
> > 1.2.0
> >
> > http://search.maven.org/#search%7Cga%7C1%7Cflume
> >
> > 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.
> >
>
Re: Missing Source JAR Files for Flume Artifacts in Maven Repository
Posted by Mike Percy <mp...@apache.org>.
Israel,
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:
https://cwiki.apache.org/confluence/display/FLUME/How+to+Release
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
possible.
Regards,
Mike
On Sat, Apr 20, 2013 at 9:12 AM, Israel Ekpo <is...@aicer.org> 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
> 1.2.0
>
> http://search.maven.org/#search%7Cga%7C1%7Cflume
>
> 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.
>