search

jocarreira / hamcrest

Automatically exported from code.google.com/p/hamcrest
0 stars 0 forks source link

Fix sources in central maven repo #30

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Please fix the sources in hamcrest maven artifacts. Currently, the sources
are bundled withing main hamcrest-*.jar files rather than sources jar files
hamcrest-*-source.jar. Sources jar files are empty, what makes it hard to
use in eclipse as eclipse:eclipse plugin attaches them to project and
sources in main jar files are ignored.

Original issue reported on code.google.com by jaroslav.kuruc on 31 Jan 2008 at 1:13

GoogleCodeExporter commented 8 years ago 
Any Maven gurus who can step-up to help address this?

thanks
-Joe

Original comment by joe.wal...@gmail.com on 17 Feb 2008 at 12:16

GoogleCodeExporter commented 8 years ago 
No problem: In Maven the source code is not expected to be in the actual jar 
file
(e.g. hamcrest-all-1.1.jar), but there should be a separate jar file named
${artifactId}-${version}-sources.jar (e.g. hamcrest-all-1.1-sources.jar) which
contains the sources.

I have attached a patch for the build.xml. After applying the patch the build 
will
produce the correct jar files in the build directory.

Original comment by michael.tamm2 on 27 Feb 2008 at 3:02

Attachments:

GoogleCodeExporter commented 8 years ago 
Attached is a simpler patch to the maven packaging only.

It takes the regular jar produced and generates a binary and source jar for 
maven.

To the extent that 1.1.1 (or such) could be pushed out to the maven repo with 
this, that'd totally rock :)

Original comment by peter.royal@pobox.com on 24 Jul 2008 at 4:56

Attachments:

GoogleCodeExporter commented 8 years ago 
It would be awesome if this was fixed.  Currently, I have to jump through hoops 
to
get sources attached when running in Eclipse.  Each time I generate my 
.classpath
file, I have to manually edit it.

Original comment by lukewpat...@gmail.com on 22 Feb 2010 at 9:06

GoogleCodeExporter commented 8 years ago 
This is a ridiculously easy fix and would be a huge help to developers using 
this library but has been an open issue since 2008?

Original comment by chengt on 1 Sep 2010 at 8:36

GoogleCodeExporter commented 8 years ago 
Jars submitted to central cannot be changed. Only a new version can fix this 
(can be a bugfix version such as 1.1.1). I will put it on my TODO list to 
create such a bugfix version.

Perhaps hamcrest 1.2 is a possible replacement for you? I have submitted it to 
central... The actual version is only usable with Java 6, a Java 5-version will 
be submitted soon as bugfix (1.2.1 or 1.2.0.1).

Original comment by sendorian on 4 Oct 2010 at 7:12

GoogleCodeExporter commented 8 years ago 
1.2-java5 was submitted to sonatype repo... (With correct source attachment... 
;)

Original comment by sendorian on 20 Dec 2010 at 3:37

GoogleCodeExporter commented 8 years ago 
Versions < 1.2 will not be fixed. Versions 1.2 and above will have correct 
source attachments.

Original comment by marc.von...@gmail.com on 16 Jan 2011 at 4:11