missing javamoney-lib 0.5-SNAPSHOT about javamoney-examples HOT 15 CLOSED

We only used cloudbees for building. Currently we switched as well to travis-ci.

Additionally we do currently focus on the JSR's main artifacts: API/RI/TCK.

We should see also, if we can render the library modules to be more independent from each other. This would allows us to release them depending on their individual maturity only. Some modules already are quite far advanced, whereas some others may never go to the any release within the next 6-12 months (are very experimental)

So the missing maturity of the library components is one of the reasons, why they are currently not available. Of course, we could deploy some snaphots into the Sonatype snapshot repositories, but I would not have a good feeling if people would start using this library already as of now.

from javamoney-examples.

Hi Anatole Tresch,

Thanks for your prompt reply.

I am trying to check out the javamoney-examples into eclipse as a maven project, where javamoney-lib 0.5-SNAPSHOT dependency is needed to build the project. I have tried it with 0.4-SNAPSHOT but it doesn't work, caused by the changed order of Money.for method's arguments. May I know how can resolve this? Do I need to checkout the javamoney-lib and build it myself?

Thanks.

Regards,
Kian Giap Lee (Glenn)

On 28 Oct 2014, at 6:01 pm, Anatole Tresch [email protected] wrote:

We only used cloudbees for building. Currently we switched as well to travis-ci.

Additionally we do currently focus on the JSR's main artifacts: API/RI/TCK.

We should see also, if we can render the library modules to be more independent from each other. This would allows us to release them depending on their individual maturity only. Some modules already are quite far advanced, whereas some others may never go to the any release within the next 6-12 months (are very experimental)

So the missing maturity of the library components is one of the reasons, why they are currently not available. Of course, we could deploy some snaphots into the Sonatype snapshot repositories, but I would not have a good feeling if people would start using this library already as of now.

—
Reply to this email directly or view it on GitHub.

from javamoney-examples.

As of now, I think this would be the best solution. If you branch, you can as well do changes needed and do a pull request (dont forget to add your twitter handle, so i can give you back some merits ;) ).

from javamoney-examples.

Cool, thanks for your kind help.

:D

Twitter: @leekiangiap

Regards,
Kian Giap Lee (Glenn)

On 28 Oct 2014, at 6:23 pm, Anatole Tresch [email protected] wrote:

As of now, I think this would be the best solution. If you branch, you can as well do changes needed and do a pull request (dont forget to add your twitter handle, so i can give you back some merits ;) ).

—
Reply to this email directly or view it on GitHub.

from javamoney-examples.

I've created issue for JavaMoney-Lib
JavaMoney/javamoney-lib#14

We can deploy this dependency to bintray.com

from javamoney-examples.

Haven't heard of bintray.com, is it easier to deploy to than e.g. MavenCentral or just another repository alternative?;-)

from javamoney-examples.

Looked at BinTray, it seems backed or run by JFrog, the company behind e.g. Artifactory. Looks cool and it has a similar business model as GitHub.

from javamoney-examples.

Yes, you can create your own repositories, like in GitHub but for binaries.
For example, here is my repository https://bintray.com/stokito/maven

from javamoney-examples.

Have to check it out, ideally we would have an "organization" user, not one for a person, but that could also be registered under names like JavaMoney or UOM, etc. where the name is available. Unless it knows the notion of organization already?;-)

from javamoney-examples.

You said that there is UOM repository for JavaMoney, so it would be better use it instead of bintray

from javamoney-examples.

No, JavaMoney so far has no private repo, UOM has its own binary repository but not for JavaMoney;-)

from javamoney-examples.

So, how we can resolve this issue? This lib should be deployed somewhere

from javamoney-examples.

Hi all

The library currently is considered to be highly experimental and there is
no clear ownership defined (I personally currently try to get the formula
part on track, but I will not do anything on other parts currently). So
there is actually no plan to deploy any parts of the library to anywhere
(generally easily visible) unless it has reached at least somehow some
point of maturitys. Of course, if you want to take help us to kick them
out, you are very welcome. But many of them are far beyond the quality
standards we have on API/RI.
I also want to split the versioning and deployment of the libraries up, so
more important parts like the calc library can be deployed/released
separately, whereas others without clear ownership will be end up in the
experimental/shelter part of the repos.

Cheers,
Anatole

2014-11-14 1:47 GMT+01:00 Sergey Ponomarev [email protected]:

So, how we can resolve this issue? This lib should be deployed somewhere

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

Anatole Tresch
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

Switzerland, Europe Zurich, GMT+1
Twitter: @atsticks
_Blogs: _http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/

Google: atsticksMobile +41-76 344 62 79

from javamoney-examples.

Of course a "snapshot" release should not have to be in Maven, where prior tagged versions even at an earlier stage could and should. Either a private "embedded" repo in GitHub or BinTray sounds good.

Something worth improving is the "dependency chain", e.g. before making major changes to JSR 363 (UOM) API recently I created a distinct tag over all relevant components, API, RI and alternate implementations like the SE port as well as libraries (much thinner in that case) and demos. That way every "Sprint" (we group issues in JIRA by relevant milestones like "JavaOne" where we had a F2F) gets a well-defined output and even it people had to manually retrieve an archive or check out the tag from GitHub they know which versions to use together. We should try working on that here in the future, too. Even if the RI may be stable with 1.0, libraries and demos might evolve.

Cheers,
Werner

from javamoney-examples.

The 0.5 release is now tagged. Should be possible to also get it to JCenter.

from javamoney-examples.