# Source distribution

**URL:** https://discuss.elastic.co/t/source-distribution/2883
**Category:** Elasticsearch
**Created:** [April 1, 2010, 8:16pm UTC](https://discuss.elastic.co/t/source-distribution/2883 "2010-04-01T20:16:17Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [April 1, 2010, 8:16pm UTC](https://discuss.elastic.co/t/source-distribution/2883/1 "2010-04-01T20:16:17Z")

</div>

Hi,

I have just pushed a change to the build so the source files will be  
within the actual distribution jar (elasticsearch-XXX.jar). It does mean  
that jar is a bit bigger, but I think its helpful for java developers out  
there. Once attaching it as source, you get javadoc and source in IDEAs.  
What do you think?

-shay.banon

p.s.

I am working on the maven thingy, hope to resolve this soon. Probably it  
will not be on central though...

---

<div class="post-metadata">

### Author: ![mooky](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mooky](https://discuss.elastic.co/u/mooky)
#### Post date: [April 1, 2010, 11:05pm UTC](https://discuss.elastic.co/t/source-distribution/2883/2 "2010-04-01T23:05:26Z")

</div>

Excellent! (but then again, you knew that 😉 )

-Nick

On 1 April 2010 21:16, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote:

> Hi,
> 
> I have just pushed a change to the build so the source files will be  
> within the actual distribution jar (elasticsearch-XXX.jar). It does mean  
> that jar is a bit bigger, but I think its helpful for java developers out  
> there. Once attaching it as source, you get javadoc and source in IDEAs.  
> What do you think?
> 
> -shay.banon
> 
> p.s.
> 
> I am working on the maven thingy, hope to resolve this soon. Probably it  
> will not be on central though...

---

<div class="post-metadata">

### Author: ![Paolo\_Castagna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paolo_castagna/32/3347_2.png) [@Paolo\_Castagna](https://discuss.elastic.co/u/Paolo_Castagna)
#### Post date: [April 2, 2010, 1:38pm UTC](https://discuss.elastic.co/t/source-distribution/2883/3 "2010-04-02T13:38:57Z")

</div>

Good news. Thanks.

For Maven, it might be better to have separate artifacts for byte code,  
sources and javadocs.

Paolo

Shay Banon wrote:

> Hi,
> 
> I have just pushed a change to the build so the source files will be  
> within the actual distribution jar (elasticsearch-XXX.jar). It does mean  
> that jar is a bit bigger, but I think its helpful for java developers  
> out there. Once attaching it as source, you get javadoc and source in  
> IDEAs. What do you think?
> 
> -shay.banon
> 
> p.s.
> 
> I am working on the maven thingy, hope to resolve this soon. Probably  
> it will not be on central though...

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [April 2, 2010, 2:52pm UTC](https://discuss.elastic.co/t/source-distribution/2883/4 "2010-04-02T14:52:54Z")

</div>

Don't think I am going to do that for maven... . The jar file itself will  
also hold the code, source (and javadoc).

-shay.banon

On Fri, Apr 2, 2010 at 4:38 PM, Paolo Castagna \<  
[castagna.lists@googlemail.com](mailto:castagna.lists@googlemail.com)\> wrote:

> Good news. Thanks.
> 
> For Maven, it might be better to have separate artifacts for byte code,  
> sources and javadocs.
> 
> Paolo
> 
> Shay Banon wrote:
> 
> > Hi,
> > 
> > I have just pushed a change to the build so the source files will be  
> > within the actual distribution jar (elasticsearch-XXX.jar). It does mean  
> > that jar is a bit bigger, but I think its helpful for java developers out  
> > there. Once attaching it as source, you get javadoc and source in IDEAs.  
> > What do you think?
> > 
> > -shay.banon
> > 
> > p.s.
> > 
> > I am working on the maven thingy, hope to resolve this soon. Probably it  
> > will not be on central though...

---

<div class="post-metadata">

### Author: ![Paolo\_Castagna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paolo_castagna/32/3347_2.png) [@Paolo\_Castagna](https://discuss.elastic.co/u/Paolo_Castagna)
#### Post date: [April 2, 2010, 5:49pm UTC](https://discuss.elastic.co/t/source-distribution/2883/5 "2010-04-02T17:49:04Z")

</div>

Shay Banon wrote:

> Don't think I am going to do that for maven... . The jar file itself  
> will also hold the code, source (and javadoc).

This will probably cause problems to people wanting to use plugins  
such as:

- [Apache Maven Eclipse Plugin (RETIRED) - Introduction](http://maven.apache.org/plugins/maven-eclipse-plugin/)
- [Apache Maven IDEA Plugin (RETIRED) - Introduction](http://maven.apache.org/plugins/maven-idea-plugin/)

And everybody else who rely on the "conventions" in place:

"If you browse the Maven central repository, you will notice  
that the classifiers sources and javadoc are used to deploy  
the project source code and API docs along with the packaged  
class files."  
-- [Maven – POM Reference](http://maven.apache.org/pom.html#POM_Relationships)

Paolo

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [April 2, 2010, 5:53pm UTC](https://discuss.elastic.co/t/source-distribution/2883/6 "2010-04-02T17:53:58Z")

</div>

I agree, but for people who use Ivy (and build systems that use Ivy  
internally), they will run into problems with source/javadoc separate jar  
files (it does not support that...). Updating the IDE to point to the source  
one is quite simple.

As you can tell, I am not a big fan of maven. But, I am willing to go the  
extra mile to support it, but just that mile :). I am working most of today  
at getting things up into the OSS sonatype thingy, time that I am waisting  
in not developing elasticsearch. This is what I almost always found with  
maven, the time you spend on it just does not justifies it.

Shay

On Fri, Apr 2, 2010 at 8:49 PM, Paolo Castagna \<  
[castagna.lists@googlemail.com](mailto:castagna.lists@googlemail.com)\> wrote:

> Shay Banon wrote:
> 
> > Don't think I am going to do that for maven... . The jar file itself will  
> > also hold the code, source (and javadoc).
> 
> This will probably cause problems to people wanting to use plugins  
> such as:
> 
> - [Apache Maven Eclipse Plugin (RETIRED) - Introduction](http://maven.apache.org/plugins/maven-eclipse-plugin/)
> - [Apache Maven IDEA Plugin (RETIRED) - Introduction](http://maven.apache.org/plugins/maven-idea-plugin/)
> 
> And everybody else who rely on the "conventions" in place:
> 
> "If you browse the Maven central repository, you will notice  
> that the classifiers sources and javadoc are used to deploy  
> the project source code and API docs along with the packaged  
> class files."  
> -- [Maven – POM Reference](http://maven.apache.org/pom.html#POM_Relationships)
> 
> Paolo

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:24am UTC](https://discuss.elastic.co/t/source-distribution/2883/7 "2017-07-06T04:24:56Z")

</div>


