short addition: it looks like all release steps after the (git) push are missing (see [1]).
regards, gerhard [1] http://deltaspike.apache.org/staging/steps_for_a_release.html 2017-06-03 13:24 GMT+02:00 Gerhard Petracek <[email protected]>: > hi thomas, > > thx for the heads-up! > we discussed it in the irc-channel already... > i've pushed the fix, but we also have to upload the files for the > download-page,... > > regards, > gerhard > > > > 2017-06-03 12:57 GMT+02:00 Thomas Andraschko <[email protected]> > : > >> Hi Mark, >> >> is everything ok with the current builds? >> I did a fresh checkout today i cant build anymore: >> >> The build could not read 1 project -> [Help 1] >> >> The project >> org.apache.deltaspike.modules:deltaspike-data-module-test-ja >> va8:1.8.0-SNAPSHOT >> (/home/tandraschko/NetBeansProjects/deltaspike/deltaspike/mo >> dules/data/test-java8/pom.xml) >> has 1 error >> Non-resolvable parent POM: Could not find artifact >> org.apache.deltaspike.modules:data-module-project:pom:1.8.0-SNAPSHOT and >> 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> >> [Help 2] >> >> >> It seems that deltaspike-data-module-test-java8 still points to >> 1.8.0-SNAPSHOT >> >> Regards, >> Thomas >> >> 2017-05-28 10:16 GMT+02:00 Mark Struberg <[email protected]>: >> >> > Hi John! >> > >> > > I'd recommend just running a mvn deploy -Pdistribution from the 1.8.0 >> > tag, >> > > that should resolve this. >> > >> > Sadly not. Since the dist modules only get added conditionally they >> didn't >> > even have been included in the version bump. >> > So they are still on the 1.8.0-SNAPSHOT. >> > >> > I gonna clean up all our build and reroll the release. >> > >> > LieGrue, >> > strub >> > >> > >> > > Am 27.05.2017 um 22:33 schrieb John D. Ament <[email protected]>: >> > > >> > > On Sat, May 27, 2017 at 12:41 PM Mark Struberg >> <[email protected] >> > > >> > > wrote: >> > > >> > >> Found them locally. Seems they are not treated as attached artifacts? >> > Why >> > >> so? >> > >> >> > >> I'm not able to replicate the issue when I follow the release >> > > instructions, I just staged a release and got all of the artifacts. >> > > >> > > I'd recommend just running a mvn deploy -Pdistribution from the 1.8.0 >> > tag, >> > > that should resolve this. >> > > >> > > >> > >> I can put them to dist/dev. >> > >> Which of the artifacts do you need? >> > >> >> > > >> > > bom, full distribution. >> > > >> > > >> > >> >> > >> LieGrue, >> > >> strub >> > >> >> > >>> Am 27.05.2017 um 17:15 schrieb John D. Ament <[email protected] >> >: >> > >>> >> > >>> BTW while the release only matters about source, we know users care >> > about >> > >>> binaries [1] [2] >> > >>> >> > >>> >> > >>> [1]: https://issues.apache.org/jira/browse/DELTASPIKE-1194 >> > >>> [2]: >> > >>> >> > >> https://lists.apache.org/thread.html/72191470ff23a7b11a16b3b8e9d16e >> > ba48a755e552b58b9c88b426c2@%3Cusers.deltaspike.apache.org%3E >> > >>> >> > >>> >> > >>> On Sat, May 27, 2017 at 11:10 AM John D. Ament < >> [email protected] >> > > >> > >>> wrote: >> > >>> >> > >>>> Did you run with -Pdistribution -DreleaseProfiles=distribution as >> > >>>> mentioned on [1]? >> > >>>> >> > >>>> [1]: http://deltaspike.apache.org/steps_for_a_release.html >> > >>>> >> > >>>> On Sat, May 27, 2017 at 11:06 AM Mark Struberg >> > >> <[email protected]> >> > >>>> wrote: >> > >>>> >> > >>>>> Nothing has been changed in the build afaik. >> > >>>>> So if the bom was not produced via the maven build then it is not >> > here >> > >> - >> > >>>>> and most probably never has been. >> > >>>>> >> > >>>>> Note that an ASF release is ONLY about the sources and not about >> any >> > >>>>> binary. >> > >>>>> Binaries are just served for convenience. >> > >>>>> >> > >>>>> LieGrue, >> > >>>>> strub >> > >>>>> >> > >>>>> >> > >>>>>> Am 27.05.2017 um 15:37 schrieb John D. Ament < >> [email protected] >> > >: >> > >>>>>> >> > >>>>>> Hi Mark, >> > >>>>>> >> > >>>>>> I don't see the actual binary distribution/distribution bom in >> the >> > >>>>> release >> > >>>>>> repo. Are they missing? If they are I'm -1, I use the bom in my >> > >>>>> project >> > >>>>>> today. >> > >>>>>> >> > >>>>>> John >> > >>>>>> >> > >>>>>> On Wed, May 24, 2017 at 10:48 AM Mark Struberg >> > >>>>> <[email protected]> >> > >>>>>> wrote: >> > >>>>>> >> > >>>>>>> Hi folks! >> > >>>>>>> >> > >>>>>>> I'd like to call a VOTE on releasing Apache DeltaSpike-1.8.0 >> > >>>>>>> >> > >>>>>>> There have been lots of improvements and bug fixes: >> > >>>>>>> >> > >>>>>>> >> > >>>>> >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> > projectId=12312820&version=12338003 >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> The staging repository is >> > >>>>>>> >> > >>>>>>> >> > >>>>> >> > >> https://repository.apache.org/content/repositories/ >> > orgapachedeltaspike-1043/ >> > >>>>>>> >> > >>>>>>> I've pushed the build branch to my github repo. >> > >>>>>>> https://github.com/struberg/deltaspike/tree/release_ >> > deltaspike_1.8.0 >> > >>>>>>> the tag is >> > >>>>> https://github.com/struberg/deltaspike/tree/deltaspike-1.8.0 >> > >>>>>>> >> > >>>>>>> This will get merge and pushed to ASF master once the VOTE >> > succeeds. >> > >>>>>>> >> > >>>>>>> The source release is here >> > >>>>>>> >> > >>>>>>> >> > >>>>> >> > >> https://repository.apache.org/content/repositories/ >> > orgapachedeltaspike-1043/org/apache/deltaspike/deltaspike/1.8.0/ >> > >>>>>>> >> > >>>>>>> Please VOTE: >> > >>>>>>> >> > >>>>>>> [+1] yeah dude, let's ship it! >> > >>>>>>> [+0] meh, don't care >> > >>>>>>> [-1] woah, stop there is a ${showstopper} >> > >>>>>>> >> > >>>>>>> The VOTE is open for 72h. >> > >>>>>>> >> > >>>>>>> txs and LieGrue, >> > >>>>>>> strub >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> >> > >>>>> >> > >>>>> >> > >> >> > >> >> > >> > >> > >
