--
You received this message because you are subscribed to the Google Groups "Flow Based Programming" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flow-based-progra...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Paul,
Personally I think it has tremendous influence.
Many projects have 10-15 dependencies (or even more) and without Maven its very time consuming to handle them.
So often Maven is a prerequisite to start using some framework.
Being available in Maven Central means to be part of the game.
Many institutions seems to prefer Maven published frameworks as normal practice.
Please consider publishing JavaFBP in Maven Central.
Thanks
Toivo
I am not sure that we ever put JavaFBP on Maven...
a) what are the advantages?
b) if worthwhile, how does one go about doing that?
On Sun, May 29, 2016 at 6:47 AM, <toivo...@gmail.com> wrote:
Hi,
I cannot find JavaFBP on Maven Central.
Maybe I am using wrong name 'javafbp' during search?
Thanks
toivo
--
You received this message because you are subscribed to the Google Groups "Flow Based Programming" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flow-based-programming+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to flow-based-progra...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Flow Based Programming" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flow-based-progra...@googlegroups.com.
PaulTIASounds good!Question (for anyone): should the generated javadoc be posted to GitHub? It is generated into the 'build' folder, so .gitignore doesn't upload it. Should I make a special case of the javadoc?
<dependency>
<groupId>com.jpaulmorrison</groupId>
<artifactId>javafbp</artifactId>
<version>3.0.5</version>
</dependency>
--
a) should I put the javadoc on GitHub? It seems to be on Maven - is this sufficient? What is the standard?
I am going to try Jake Wharton's suggestion in http://stackoverflow.com/questions/3939595/making-javadocs-available-with-github-sonatype-maven-repo - presumably this is to put a browsable javadoc on GitHub - how does this play with Maven's copy?
Bert, any thoughts on this?
b) should I post the full build.gradle that I used on GitHub, or a version that just builds the jar file...?
Thanks in advance,
Paul