1.0 preparations: vert.x on Maven Central

[Pid]

All,

Just a quick update: I have filed a ticket to register vert.x on Maven
Central.

Next significant task will be to prepare the expected format of artefacts:

vertx-embedded-{version}.jar
vertx-embedded-{version}-sources.jar
vertx-embedded-{version}-javadoc.jar

I propose to fix up the Gradle build & utilise this tools functionality
to provide the upload mechanism to the Sonatype repos.

p

--

[key:62590808]

[Pid]

On 25/04/2012 09:29, Pid wrote:
> All,
>
> Just a quick update: I have filed a ticket to register vert.x on Maven
> Central.

I am pleased to say that Sonatype have been splendidly quick & vert.x is
now registered & ready for snapshots & milestones.

Suggest CI is next on the agenda...

p

[Tim Fox]

On 25/04/12 16:13, Pid wrote:
> On 25/04/2012 09:29, Pid wrote:
>> All,
>>
>> Just a quick update: I have filed a ticket to register vert.x on Maven
>> Central.
> I am pleased to say that Sonatype have been splendidly quick& vert.x is
> now registered& ready for snapshots& milestones.

Marvellous

> Suggest CI is next on the agenda...

I was thinking cloudbees. wdyt?

>
> p
>
>> Next significant task will be to prepare the expected format of artefacts:
>>
>> vertx-embedded-{version}.jar
>> vertx-embedded-{version}-sources.jar
>> vertx-embedded-{version}-javadoc.jar
>>

>> I propose to fix up the Gradle build& utilise this tools functionality

>> to provide the upload mechanism to the Sonatype repos.
>>
>>
>> p
>>
>


--

Tim Fox

Vert.x - effortless polyglot asynchronous application development
http://vertx.io
twitter:@timfox

[Tim Fox]

Can you get the upload to work using ant too?

I don't use Gradle and I think others are in the same boat.

[Pid]

On 29/04/2012 08:57, Tim Fox wrote:
> Can you get the upload to work using ant too?

It's probably doable, just likely to be more convoluted.

> I don't use Gradle and I think others are in the same boat.

One of several nice things about Gradle is that you can put a minimal
wrapper in the repo & it downloads the runtime when you run the
'gradlew[.bat]' script for the first time. (It's a small download too.)

So it's easy for non-users to use it, as it were.


p

> On Wednesday, April 25, 2012 9:29:11 AM UTC+1, Pid wrote:
>
> All,
>
> Just a quick update: I have filed a ticket to register vert.x on Maven
> Central.
>
> Next significant task will be to prepare the expected format of
> artefacts:
>
> vertx-embedded-{version}.jar
> vertx-embedded-{version}-sources.jar
> vertx-embedded-{version}-javadoc.jar
>
> I propose to fix up the Gradle build & utilise this tools functionality
> to provide the upload mechanism to the Sonatype repos.
>
>
> p
>
> --
>
> [key:62590808]
>

--

[key:62590808]

[Pid]

On 25/04/2012 16:15, Tim Fox wrote:
> On 25/04/12 16:13, Pid wrote:
>> On 25/04/2012 09:29, Pid wrote:
>>> All,
>>>
>>> Just a quick update: I have filed a ticket to register vert.x on Maven
>>> Central.
>> I am pleased to say that Sonatype have been splendidly quick& vert.x is
>> now registered& ready for snapshots& milestones.
>
> Marvellous
>> Suggest CI is next on the agenda...
>
> I was thinking cloudbees. wdyt?

There is also Travis, actually, now that I think about it.
Has good integration with Github.

http://about.travis-ci.org/docs/user/getting-started/

p



>>> Next significant task will be to prepare the expected format of
>>> artefacts:
>>>
>>> vertx-embedded-{version}.jar
>>> vertx-embedded-{version}-sources.jar
>>> vertx-embedded-{version}-javadoc.jar
>>>
>>> I propose to fix up the Gradle build& utilise this tools functionality
>>> to provide the upload mechanism to the Sonatype repos.
>>>
>>>
>>> p
>>>
>>
>
>


--

[key:62590808]

[Andrew Cholakian]

I'll just chime in that I've found travis to be very straightforward to work with. It requires very little effort to get going.

Looking forward to being able to add this to existing projects!

[Jon Brisbin]

Travis doesn't currently have a Java 7 build agent AFAIK.

Sent from my iPhone

[blalor]

On Apr 25, 11:13 am, Pid <p...@pidster.com> wrote:

> I am pleased to say that Sonatype have been splendidly quick & vert.x is
> now registered & ready for snapshots & milestones.

What are the coordinates going to be?

[Pid]

org.vertx:

then various packages, e.g.

org.vertx:vertx-api:1.0-SNAPSHOT


p

--

[key:62590808]

[before]

Hello everyone,

I've made ​​some changes last night to the structure of vert.x locally
so that a clean multi-module project with Apache Maven integration was
created. Now it is very easy to load individual modules both in the
local Maven repository and in The Central Repository. Also the
dependencies and the transitives will be resolved by The Central
Repository. I recommend the convention-based modularization of vert.x
and the move to Maven, because the lifecycle management of this
project is much easier. If still Ant tasks are required, these can
also be triggered via Maven. I will create a new fork on GitHub and
would like to see some feedback, please.

kind regards,
André

[before]

I've uploaded an example to show how vert.x can be built with Maven.
Look at https://github.com/before/vert.x

[Nelson Silva]

+1 on maven

Still, IMHO we should use the vert-x organization on GitHub and move each maven module to its own repo.
We could use submodules if needed.

Also i don't agree with this module separation... vertx-javascript should include the RhinoVerticle, vertx-groovy the GroovyVerticle and so on. Thus the vertx-deploy isn't needed and the interfaces should be moved to core.

Busmods should be in their own projects as well...

[Jon Brisbin]

FWIW- a Gradle project can support both gradle and maven builds (you generate a Pom). IMO it would be more flexible than straight maven.

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "vert.x" group.
> To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/93pM9aFnXuoJ.
> To post to this group, send an email to ve...@googlegroups.com.
> To unsubscribe from this group, send email to vertx+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/vertx?hl=en-GB.
>

[Brian Lalor]

On May 22, 2012, at 8:06 PM, Jon Brisbin wrote:

> FWIW- a Gradle project can support both gradle and maven builds (you generate a Pom). IMO it would be more flexible than straight maven.

I can see the appeal for some projects, but for most it's nice to be able to get up and running (executing tests, building packages) without having to install yet another tool or trying to suss out what incantation I need. The fact that there are jars checked into Vert.x's GitHub project says to me that there's a better way to manage dependencies.

[Scott Frederick]

One really nice feature of Gradle is that you can easily create a wrapper script and check it into the project. You just download or clone the project, run the "gradlew" or "gradlew.bat" script, and it downloads all the necessary binaries and then launches the build script. No prior installation of Gradle is required. This also ensures that you get the version of Gradle that the build script was written against, eliminating the kids of problems you can get into with differences between Maven 2 and 3. Big win.  

[Tim Fox]

Yes, Pid is currently working on a Gradle build, this will include
pushing stuff to Maven. We won't be using Maven for our own build.

This should be finished soon. After that we will work on splitting up
the project.

I am leaving for a conference this morning, and will be back next
Tuesday, so won't be getting much done until then.

[Tim Fox]

Yes, and that has been known for a _long time_. We are just waiting for
the new build to be finished, and then hopefully we can devote our time
to discuss other thing than build systems! ;)

[Jon Brisbin]

Maybe I wasn't clear earlier, but the *library developer* generates and maintains the pom.xml file and checks that in.

As the end user of a Gradle project that supports Maven, you simply do "mvn test" or whatever. You don't have to know about Gradle or how to use it to use the Maven integration (though you can do ./gradlew install, which installs maven artifacts, etc... and there's maven plugin support. All kinds of nice things in Gradle...).

To you it would look like a regular maven project with some extra files in the root directory. :)

Thanks!

Jon Brisbin

http://jbrisbin.com
Twitter: @j_brisbin

> --
> You received this message because you are subscribed to the Google Groups "vert.x" group.

[Ted Naleid]

On Wednesday, May 23, 2012 1:45:06 AM UTC-5, Tim Fox wrote:

We are just waiting for the new build to be finished, and then hopefully we can devote our time
to discuss other thing than build systems! ;)

Sorry to bring this up yet again, but has there been any progress on getting vertx-core.jar out on maven central (or another similar repository)?  I've been waiting to write up a couple of blog posts on vert.x till I can make it as easy as using groovy @Grab annotations in a single script file.   

The current documentation is good and the framework install is easy, but installing it is still a barrier for a lot of people to see how easy it is to use.  Demonstrating it in one simple file without any extra steps makes the barriers for someone to try it as small as possible.  

I also know that I'm not the only one hoping for this to get done (as evidenced by this thread as well as this SO topic: http://stackoverflow.com/questions/10448520/maven-coordinates-for-vert-x).

Thanks,

-Ted

[Ed Ropple]

Chipping in another inquiry as to maven coordinates for vert.x - really excited about it, but hard to sell other developers I work with on it if we have to manage our dependencies directly. :)

Thanks!

-Ed

[Guillaume Laforge]

That would indeed be neat if we could use @Grab vertx in a Groovy script!

+1 :-)

Guillaume

--

You received this message because you are subscribed to the Google Groups "vert.x" group.

To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/ndHHAdEJYsIJ.

[Pid]

On 29/05/2012 02:27, Ed Ropple wrote:
> Chipping in another inquiry as to maven coordinates for vert.x - really
> excited about it, but hard to sell other developers I work with on it if
> we have to manage our dependencies directly. :)

I've been snowed under with customer work in the last couple of weeks.
It's not been forgotten though, so please bear with me.


p

> On Monday, May 28, 2012 8:22:37 PM UTC-4, Ted Naleid wrote:
>
> On Wednesday, May 23, 2012 1:45:06 AM UTC-5, Tim Fox wrote:
>
> We are just waiting for the new build to be finished, and then
> hopefully we can devote our time
> to discuss other thing than build systems! ;)
>
>
> Sorry to bring this up yet again, but has there been any progress on
> getting vertx-core.jar out on maven central (or another similar
> repository)? I've been waiting to write up a couple of blog posts
> on vert.x till I can make it as easy as using groovy @Grab
> annotations in a single script file.
>
> The current documentation is good and the framework install is easy,
> but installing it is still a barrier for a lot of people to see how
> easy it is to use. Demonstrating it in one simple file without any
> extra steps makes the barriers for someone to try it as small as
> possible.
>
> I also know that I'm not the only one hoping for this to get done
> (as evidenced by this thread as well as this SO
> topic: http://stackoverflow.com/questions/10448520/maven-coordinates-for-vert-x

> <http://stackoverflow.com/questions/10448520/maven-coordinates-for-vert-x>).
>
> Thanks,
> -Ted

>
> --
> You received this message because you are subscribed to the Google
> Groups "vert.x" group.
> To view this discussion on the web, visit

> https://groups.google.com/d/msg/vertx/-/71mI2XFeHq8J.

> To post to this group, send an email to ve...@googlegroups.com.
> To unsubscribe from this group, send email to
> vertx+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/vertx?hl=en-GB.

--

[key:62590808]

[Tim Fox]

On 29/05/12 08:29, Pid wrote:
> On 29/05/2012 02:27, Ed Ropple wrote:
>> Chipping in another inquiry as to maven coordinates for vert.x - really
>> excited about it, but hard to sell other developers I work with on it if
>> we have to manage our dependencies directly. :)
> I've been snowed under with customer work in the last couple of weeks.
> It's not been forgotten though, so please bear with me.

As well as pid being busy, I was travelling all last week, so that's
made things even slower.

I am working all this week, then I have a week holiday next week, so
that's going to be slow too.

After that, should be able to get up to speed properly again!

Unfortunately this is one of the perils of a very small team

[Ed Ropple]

No worries at all! I grabbed before's branch, pulled to master HEAD (with no trouble), and installed it to my public maven repo for anyone who wants it for now (with the usual caveats: I had to hack up the pom so it might not work identically to the official Central release whenever that happens, it's 1.0-SNAPSHOT and so might make demons fly out of your nose, under no circumstances should you trust some hack like me to build you a production jar, etc. etc. etc.).

Some brief testing does indicate that before's pom.xml and changes are solid, though; I had to pull the sonatype parent pom because otherwise I couldn't get wagon to deploy to my stuff instead of sonatype but everything else checked out A-OK.

You can access the repository at http://maven.edropple.com - the groupId is io.vertx, artifacts are vertx-{core,deploy,groovy,groovy-test-framework,groovy-java-test-framework,parent,ruby,test-java}, version is 1.0-SNAPSHOT.

-Ed

> vertx+unsubscribe@googlegroups.com.

[Tim Fox]

Great, thanks :)

Hopefully won't be too long before we have the official one there too.

> <https://groups.google.com/d/msg/vertx/-/71mI2XFeHq8J>.

> > To post to this group, send an email to ve...@googlegroups.com

> <mailto:ve...@googlegroups.com>.

> > To unsubscribe from this group, send email to

> > vertx+un...@googlegroups.com
> <mailto:vertx%2Bunsu...@googlegroups.com>.

> > For more options, visit this group at
> > http://groups.google.com/group/vertx?hl=en-GB

> <http://groups.google.com/group/vertx?hl=en-GB>.
>
>
> --
>
> [key:62590808]

>
> --
> You received this message because you are subscribed to the Google
> Groups "vert.x" group.
> To view this discussion on the web, visit

> https://groups.google.com/d/msg/vertx/-/7K9DO0qoMLIJ.

> To post to this group, send an email to ve...@googlegroups.com.
> To unsubscribe from this group, send email to

> vertx+un...@googlegroups.com.

> For more options, visit this group at
> http://groups.google.com/group/vertx?hl=en-GB.


--

[Ted Naleid]

Thanks for standing this up Ed, this is great for quick test stuff and helps give the vert.x core team more time to fit things in when they are able.

-Ted

To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/7K9DO0qoMLIJ.

To post to this group, send an email to ve...@googlegroups.com.

To unsubscribe from this group, send email to vertx+un...@googlegroups.com.