Re: Understanding the snapshot and release process

Ok … reporting some progress here. I managed to get the build to create the java8 and the java7 artifacts in one run and to run the tests in both versions. The only thing I am currently struggling with is the Maven toolchain support. Maven provides a mechanism called “toolchains” in which you

Re: Understanding the snapshot and release process

Just have a look at the last few builds on Travis that my pull request initiated. You will see it failing with different tests every time I ran the build even if nothing changed (I think in the last commit I simply removed a space in one of the poms). Was successful … After moving some tests

Re: Understanding the snapshot and release process

I just pulled down the latest PR contents into a new clone. I get a bunch of warnings like the one below (but things work). mvn clean install [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for

Re: Understanding the snapshot and release process

Thx for the cleanup for Eclipse. > On Jun 15, 2017, at 7:09 AM, Christofer Dutz > wrote: > ...It seems as if some unit-tests tend to fail in random intervals. Right > now, I had 3 Travis runs without any functional changes and I got failures on > 3 different places.

Re: Understanding the snapshot and release process

Just another question … It seems as if some unit-tests tend to fail in random intervals. Right now, I had 3 Travis runs without any functional changes and I got failures on 3 different places. Is this “normal”? If yes … I think I should start identifiying the “random failers” and investigate

Re: Understanding the snapshot and release process

Your wish is my command ;-) I just installed the latest Eclipse “Neon.3” in the Developer edition (which comes with Maven support). Then I manually deleted all existing eclipse settings in the Edgent project as otherwise Eclipse would have insisted on using them instead. Also, I added them to

Re: Understanding the snapshot and release process

Yup, just noticed it. Looking good! > On Jun 14, 2017, at 11:36 AM, Christofer Dutz > wrote: > > Ok, so I just pushed a major update. > > On my machine with these changes both the java7 and java8 builds seem to be > working. In the next few days I’ll probably play

Re: Understanding the snapshot and release process

Ok, so I just pushed a major update. On my machine with these changes both the java7 and java8 builds seem to be working. In the next few days I’ll probably play around with some of the excluded modules and see if we can include them in the java7 build. Right now, it sort of looks as if they

Re: Understanding the snapshot and release process

> On Jun 12, 2017, at 4:56 PM, Christofer Dutz > wrote: > ... > In my opinion IDE settings shouldn’t be checked in and should rather be added > to the gitignore list. Don’t know how often we had issues in Flex with > checked in IDE settings :-( Agreed, with maven

Re: Understanding the snapshot and release process

> On Jun 13, 2017, at 10:16 AM, Christofer Dutz > wrote: > ... > Right now, I am still having issues running all Tests in the java7 version … > math3 is sort of causing issues, I haven’t quite figured out why. Edgent’s java7 platform support doesn’t include

Re: Understanding the snapshot and release process

Aaahh … well that’s a different thing … that’s already possible with maven :-) Right now, all Apache releases go to a so-called release-repository. That’s a Maven repository containing only the artifacts of the current release. The project can vote on this. If the vote doesn’t pass, the repo is

Re: Understanding the snapshot and release process

> On Jun 12, 2017, at 5:04 PM, Christofer Dutz > wrote: > ... > I guess also executing the pre-built test with java7 should also be possible, > but I’m struggling with one other of your requirements: > “Only deploy everything if the java8, java7 and android builds

Re: Understanding the snapshot and release process

LaBossiere <dml.apa...@gmail.com> Antworten an: "dev@edgent.apache.org" <dev@edgent.apache.org> Datum: Montag, 12. Juni 2017 um 22:43 An: "dev@edgent.apache.org" <dev@edgent.apache.org> Betreff: Re: Understanding the snapshot and release process Chris, I

Re: Understanding the snapshot and release process

> On Jun 12, 2017, at 10:23 AM, Christofer Dutz > wrote: > > Well “mvn test” would run the maven lifecycle up to the test phase, this > includes compiling etc … and compiling doesn’t work with Java7. Maven doesn’t have the notion of build-avoidance / artifact reuse?

Re: Understanding the snapshot and release process

Ok … so I’m working on the open issues … I do have one question though … Compiling with one java version and then running a different one with the tests will be challenging, if not impossible. What I did a while ago was to introduce the animal-sniffer plugin. This very strictly checks the

Re: Understanding the snapshot and release process

Hi Dale, Thanks for that … I had noticed the merged pull request … today I pulled in the upstream changes and tweaked the build a little. Now both the java8 and java7 builds seem to be working. I also made the build compile to different target sub-directories so now you can inspect the output

Re: Understanding the snapshot and release process

Hi Chris, in case you hadn’t noticed the following merged PR (on master) eliminates the use of “default”. So you should be able to rebase your branch your branch and be all set. https://github.com/apache/incubator-edgent/pull/310 > On

Re: Understanding the snapshot and release process

sorry no idea about travis and memory On Jun 8, 2017, at 10:40 AM, Christofer Dutz wrote: > ... > Today I had some progress on the java7 side. ... > problem. The default methods in DirectTestSetup can’t seem to be backported > if the interface and the implementing

Re: Understanding the snapshot and release process

> On Jun 8, 2017, at 10:43 AM, Christofer Dutz > wrote: > > Eventually your approach with a sub-directory inside the target would be a > valid option … would probably have to adjust the maven-clean-plugin too, but > that should work in getting all results inside

Re: Understanding the snapshot and release process

Hi Dale, Today I had some progress on the java7 side. I successfully added the retrolambda-maven-plugin in a dedicated java7 profile to the main pom. Now the plugin automatically kicks in and converts the classes after compiling them. I also added the animal-sniffer-maven-plugin to explicitly

Re: Understanding the snapshot and release process

> On Jun 8, 2017, at 4:19 AM, Christofer Dutz wrote: > > Regarding java8 and java7 artifacts … Coincidentally, I started investigating this space yesterday and retrolambda-maven-plugin and was just composing mail on the question of publishing java8 and java7 to mvn

Re: Understanding the snapshot and release process

t; Datum: 07.06.17 18:45 (GMT+01:00) An: dev@edgent.apache.org Betreff: Re: Understanding the snapshot and release process OK, so mvn install -Papache-release generates the source release bundle zip. I poked around for a while but couldn’t come up with the incantation

Re: Understanding the snapshot and release process

inem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Dale LaBossiere <dml.apa...@gmail.com> Datum: 07.06.17 18:45 (GMT+01:00) An: dev@edgent.apache.org Betreff: Re: Understanding the snapshot and release process OK, so mvn install -Papache-release generat

Re: Understanding the snapshot and release process

.org Betreff: Re: Understanding the snapshot and release process install -Papache-release is generating the (arc) signature file :-) Chris, what needs to be done to get it to also generate the .md5 and .sha files? Also, did I now just populate the ASF snapshot repo? :-) — Dale

Re: Understanding the snapshot and release process

install -Papache-release is generating the (arc) signature file :-) Chris, what needs to be done to get it to also generate the .md5 and .sha files? Also, did I now just populate the ASF snapshot repo? :-) — Dale

Re: Understanding the snapshot and release process

OK, so mvn install -Papache-release generates the source release bundle zip. I poked around for a while but couldn’t come up with the incantation needed to start excluding things from the zip. e.g., the zip includes all of the residual gradle generated **/build/ Chris, can you enhance the

Re: Understanding the snapshot and release process

Checking our repo: https://repository.apache.org/#view-repositories;releases~browsestorage I can see that fewer than about 10% of all apache projects do that … But I wouldn’t mind adding that, if the others agree. Chris Am 07.06.17, 14:54 schrieb "Justin Mclean" :

Re: Understanding the snapshot and release process

Hi, While not a requirement prefixing with apache may add some legal protection and is good from a branding point of of view. Thanks, Justin

Re: Understanding the snapshot and release process

Well looking through the Apache repo there is no 100% standard, but most artifacts are indeed prefixed with the project name but not apache … I’ll add the edgent to each of the artifacts. Chris Am 07.06.17, 13:47 schrieb "John D. Ament" : Usually the maven norm is

Re: Understanding the snapshot and release process

Usually the maven norm is something like com.mycompany.myproduct:myproduct-some-module. So I would expect to see groupIds of org.apache.edgent, and artifact id's of edgent-some-module. However, I've noticed that both Eclipse and IBM (obviously not related in any way) seem to use completely

Re: Understanding the snapshot and release process

Hi, I’ll answer this one quickly as I can do that without digging in too deep. I wouldn’t add the apache-edgent to the artifact names as the groupId already qualifies them as apache edgent modules. However when creating a release zip/tar.gz with the sources or binary distribution I would add

Re: Understanding the snapshot and release process

Currently the generated JAR/WAR lack an “edgent” or “apache-edgent” prefix, e.g., "api-topology-1.2.0-SNAPSHOT.jar". How important/required is it to add that before we start publishing these to mvn repos? What’s the current ASF best-practice in this regard? e.g., I some (limited) # of

Re: Understanding the snapshot and release process

Hi Chris, I was trying the different forms of test execution noted in [1]. I’ve been mucking with my (Eclipse) .classpath files but that shouldn’t affect the following :-) I tried running just the jdbc connector tests. gradlew connectors:jdbc:test # does everything needed to run the “test”

Re: Maven wiki page [was Re: Understanding the snapshot and release process]

Hi Queeniw, thanks … I added most of the things in the upper section. For the questions in the lower one, I would like to ask you to watch the little maven introduction video I did. It should answer a lot of questions. Questions that my answers would probably sound confusing without this

Re: Maven wiki page [was Re: Understanding the snapshot and release process]

I’d love to, but you would need to give me the charma to do so ( Chris Am 05.06.17, 20:14 schrieb "Dale LaBossiere" : I created a wiki page [1] to help us work through / collaborate on this. IMO there are too many questions, etc to effectively deal with it just on

Re: Understanding the snapshot and release process

Hi, So, I just create a PR as I think I am currently finished with everything I wanted to fix. Edgent should now be buildable with Maven command. At least I managed to get the travis build working with maven ☺ Here some structural changes I did. I refactored the project and extracted the

Re: Understanding the snapshot and release process

Christofer, can you create a [WIP] PR for this work? Then I’ll have a context from which I can review / ask stupid nubie questions :-) Also, what’s the executive summary for running maven to build a release (or at least all of the jars) using this work? And to run the tests? I’d like to

Re: Understanding the snapshot and release process

@apache.org> > Datum: 28.05.17 16:20 (GMT+01:00) > An: dev@edgent.apache.org > Betreff: Re: Understanding the snapshot and release process > > The maven based build seems to be much more maintainable. I'm glad you > guys came together to solve this problem :-)

Re: Understanding the snapshot and release process

hey do, I was unable to find a job with a name that was easy to identify. > Chris > > > > Von meinem Samsung Galaxy Smartphone gesendet. > > > Ursprüngliche Nachricht > Von: "John D. Ament" <johndam...@apache.org> > Datum: 28.05.17 16:20 (

Re: Understanding the snapshot and release process

The maven based build seems to be much more maintainable. I'm glad you guys came together to solve this problem :-) RE distribution of snapshots. We only presently support publishing via our hosted jenkins, however Edgent currently builds in Travis. So that would need to be changed, or some

Re: Understanding the snapshot and release process

Hi guys, Strange people these Germans … if it rains, they complain about it and how much they would like to go swimming in the sun … now that it’s 32° and the sun is shining, no one wants to go swimming, cause it’s too fu***g hot ;-) … well this way I had some time to finish the maven

Re: Understanding the snapshot and release process

Awaiting others to chime in on this “switch to mvn” subject. A “don’t care” (+/- 0) response is preferred over silence. In the mean time... > On May 24, 2017, at 11:41 AM, Christofer Dutz > wrote: > ... > I just checked out everything and managed to get things

Re: Understanding the snapshot and release process

On May 24, 2017, at 9:38 AM, Christofer Dutz wrote: ... Regarding the build system … what is the projects general opinion on a Maven build? I know that Ant and Gradle are a lot more flexible as Maven, but I think it is a good thing that Maven is this strict, as it

Re: Understanding the snapshot and release process

Looks like we might also get some help from christofer.d...@c-ware.de in cleaning up the build system! I hope my previous message clarifies why things are the way they are. I don’t know if there are simpler ways to achieve the same effects or if it would be best to abandon some of them. e.g.,

Re: Understanding the snapshot and release process

> On May 22, 2017, at 9:54 PM, John D. Ament wrote: > ... > I'm trying to understand the current snapshot and release process for > Edgent, specifically to make it so that we can easily publish JARs into > maven central. > ... Yeah, the gradle stuff ended up that