Wednesday, December 28, 2016, 2:09:11 PM, John D. Ament wrote: > On Wed, Dec 28, 2016 at 5:35 AM Daniel Dekany <ddek...@freemail.hu> wrote: > Wednesday, December 28, 2016, 4:12:06 AM, Christopher wrote: > > [snip] >> The one complication here is that the release artifact (source tarball) is >> most easily created with a maven project by using the maven-assembly-plugin >> with the source tarball assembly defined in the ASF-wide parent POM. > > I'm not sure how hard it would be to set up the POM so that it > produces an assembly with the "-incubating" suffix even if the project > version doesn't contain it. Anyway, some extra release steps during > incubation can be better than troubling the users (developers who > depend on your project) with an additional groupId change or with a > non-standard version suffix. There are much more users than people who > do releases after all. > > Do you need to add the -incubating suffix via maven? When staging > the release in dev, you can name the file as you like. Even if not, > maven assembly adds a suffix for you. you can name your execution > -src-incubating to include it.
Yes, I guess it's not a problem even for Maven-based projects, that was my point. The FreeMarker build is not Maven-based, and it can already do this. -- Thanks, Daniel Dekany --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
