Closed GoogleCodeExporter closed 8 years ago
@mwisnicki & @sendorian
Indeed it is! I must have been blind this morning, lack of coffee, sleep,
drugs...
Original comment by dharri...@gmail.com
on 5 Oct 2010 at 2:44
Any plans to update hamcrest-all?
Original comment by chocol...@cpan.org
on 5 Oct 2010 at 8:08
No. It is not necessary, because hamcrest has a simple structure:
hamcrest-integration contains hamcrest-library which contains hamcrest-all.
That's all.
So reference hamcrest-integration (once it is approved and in central) and
that's it. It can be seen as "hamcrest-all".
The -all libraries are unpopular in the maven world. Even Spring has banned it.
Original comment by sendorian
on 5 Oct 2010 at 8:42
> So reference hamcrest-integration (once it is approved and in central) and
that's it.
Will do. Many thanks.
Original comment by chocol...@cpan.org
on 5 Oct 2010 at 8:46
I said:
>hamcrest-integration contains hamcrest-library which contains hamcrest-all.
The last has to be hamcrest-core, sorry...
What I meant is that hamcrest-integration references all hamcrest libs. ;)
Original comment by sendorian
on 5 Oct 2010 at 8:49
Got it (I think :-) Thanks again.
Original comment by chocol...@cpan.org
on 5 Oct 2010 at 8:52
@sendorian & @sgybas
Got also caught by the Java class format error.
If you need a hand, I'll be happy to have mine a bit dirty ;)
However I might guidance as the thing seems a bit tricky.
Original comment by brice.du...@gmail.com
on 12 Oct 2010 at 4:04
Sorry for the late reply. I was very busy... Fixed Versions 1.2-java5 were
uploaded to the Sonatype Repo and are waiting being approved...
Attached are the fixed POMs.
@brice
Thanks for the offer but this POM got really difficult and it's easier to
rework it than to explain it in every detail...
Original comment by sendorian
on 20 Dec 2010 at 2:51
Attachments:
@sendorian Hey it's open source, no problem for the late reply, I know what
it's like :)
Anyway thx for the patch
Original comment by brice.du...@gmail.com
on 20 Dec 2010 at 3:12
@sendorian
Why so much duplication instead of using POM inheritance ?
Original comment by mwisnicki@gmail.com
on 20 Dec 2010 at 8:34
@mwisnicki
Because this was no clean build process for Hamcrest. It was meant to be a
quick one-shot solution to get a clean version of Hamcrest 1.2 into central. As
it seems now I have to do this more frequently (1.3RC2 is out without a maven
artifact...) I will cleanup the POMs and create a parent.
Original comment by sendorian
on 21 Dec 2010 at 11:28
Sonatype rejected the naming 1.2-java5. So I had to rename the Version to
1.2.1. This version was now accepted and should be available in central until
tomorrow.
Original comment by sendorian
on 22 Dec 2010 at 8:27
Created Git-Repo at Github with all the POMs:
https://github.com/mvonrenteln/hamcrest-java-maven-integration
This project can be used in conjunction with the SVN-Repo of hamcrest here at
Google Code (base is hamcrest-java).
All POMs have been cleaned up, a parent POM has been created.
AND LAST BUT NOT LEAST Version 1.3.RC2 of Hamcrest has been submitted to
sonatype. Waiting for approval.
Original comment by sendorian
on 22 Dec 2010 at 4:29
Hamcrest 1.3.RC2 is in central now.
Original comment by sendorian
on 23 Dec 2010 at 7:38
Any chance of adding a "hamcrest-all" artifact to central, a la 1.1 ?
Original comment by daniel.r...@gmail.com
on 16 Jan 2011 at 6:09
Not as single jar. I will consider to create a POM-Only artifact that
references all hamcrest libs.
For now use hamcrest-integration. (See comment #55.)
Original comment by marc.von...@gmail.com
on 16 Jan 2011 at 4:06
Please make sure the sources are deployed as well by adding this plugin to the
pom.xml build/plugins section:
<plugin>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
Original comment by jacmo...@gmail.com
on 23 Mar 2011 at 10:48
This is not necessary. The Maven Release Plugin automatically deploys the
sources, too. The sources are present for all jars > 1.2.
Original comment by marc.von...@gmail.com
on 24 Mar 2011 at 7:30
Closing this issue because Maven bundles for all Versions > 1.2 are now in
central.
Original comment by marc.von...@gmail.com
on 12 Apr 2012 at 8:02
Original issue reported on code.google.com by
joe.wal...@gmail.com
on 22 May 2007 at 9:03