After many hours trying to suppress the shade plugin during the release, I've come up with a workaround:
Shaded artifacts are now placed in /dist rather than /target when apache-release profile is activated. This allows mvn verify to create and integration test shaded jars, but ensures they are not uploaded to the staging repo during the release process. I'll send out a vote for streams-examples-0.2-incubating rc1 shortly. Steve Blackmon [email protected] On Tue, Apr 28, 2015 at 2:57 AM, Steve Blackmon <[email protected]> wrote: > All, > > I believe that release of streams-project 0.2-incubating is > essentially complete as of Monday evening - just need to make the > formal announcement. master in streams-project is now > 0.3-incubating-SNAPSHOT. > > I'm quite close to getting streams-examples 0.2-incubating-rc1 ready > to submit for a release vote from PPMC - have to figure out how to > stop maven from uploading shaded artifacts to the release repo. > > Currently working in branch 0.2-incubating-rc1 and trying variants of > the following (after release:prepare succeeds) > > mvn -Papache-release -Darguments='-Dmaven.test.skip.exec=true > -Dmaven.shade.skip=true' release:perform -Dgoals=deploy > -DlocalRepoDirectory=. -DlocalCheckout=true -Dmaven.shade.skip=true > > Steve Blackmon > [email protected] > > > On Sun, Apr 26, 2015 at 2:31 PM, First Developer <[email protected]> wrote: >> Hey everyone, >> >> Please announce when 0.2 is released, I am seeing that some poms have not >> been updated. >> >> - Joe
