Create a branch or profile for testing AsciidoctorJ snapshots

[mojavelinux]

I think the Maven plugin should have a separate branch setup to build against an AsciidoctorJ snapshot. An alternative is to add a profile in the POM on the master branch for building against the AsciidoctorJ snapshot. Either way works for me.

[LightGuard]

@lordofthejars How often are you pushing snapshots to bintray? Also is there a way we can automate the testing of this? I have a new profile locally I'm going to push up, but it would be create if there was some sort of service or something we could call (or trigger a new build) to get the new version and automatically test with that version on the profile.

[lordofthejars]

I released to bintray when a new asciidoctor RC was released, and I did by using a maven profile. Because i was using my bintray account I didn t push final releases but this may change because now there is asciidoctor organization inside bintray

Enviat des del meu iPhone

El 20/08/2014, a les 19.06, Jason Porter [email protected] va escriure:

@lordofthejars How often are you pushing snapshots to bintray? Also is there a way we can automate the testing of this? I have a new profile locally I'm going to push up, but it would be create if there was some sort of service or something we could call (or trigger a new build) to get the new version and automatically test with that version on the profile.

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

[LightGuard]

As long as we're still pushing it up to maven central (or there's a sync) I'm fine with it being in bintray as well. Having to add a repository for a dependent articfact isn't a good idea. — Sent from Mailbox

On Wed, Aug 20, 2014 at 11:52 AM, Alex Soto [email protected] wrote:

I released to bintray when a new asciidoctor RC was released, and I did by using a maven profile. Because i was using my bintray account I didn t push final releases but this may change because now there is asciidoctor organization inside bintray Enviat des del meu iPhone El 20/08/2014, a les 19.06, Jason Porter [email protected] va escriure:

@lordofthejars How often are you pushing snapshots to bintray? Also is there a way we can automate the testing of this? I have a new profile locally I'm going to push up, but it would be create if there was some sort of service or something we could call (or trigger a new build) to get the new version and automatically test with that version on the profile.

—

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/94#issuecomment-52815276

[mojavelinux]

For sure, it will be in both places. The Gradle plugin deployment proves it works.

(Keep in mind for the Gradle plugin environment, adding jcenter is equivalent to adding mavenCentral...it's only Maven that has a bias towards a single binary repository).

[mojavelinux]

For example: http://jcenter.bintray.com/org/asciidoctor/asciidoctorj/1.5.0/asciidoctorj-1.5.0.pom

[mojavelinux]

And: http://repo1.maven.org/maven2/org/asciidoctor/asciidoctorj/1.5.0/asciidoctorj-1.5.0.pom

[uniqueck]

We can setup a github action job to run a matrix test job with different asciidoctorj versions. You can configure that failure for future asciidoctorj not fails the build, but gave an hint that there is an issue with the new asciidoctorj snapshot version. Is this still a desired behavior today?

[abelsromero]

Is this still a desired behavior today?

At least to detect breaking changes for sure, for starters, we could have an upstream pipeline that installs asciidoctorj from source in the local maven repo and then run the tests against that. But keep in mind there's been some breaking points and there will be in the future, we may have periods in which such pipeline will fail.