The log4net jenkinsfile pipeline is complicated because it targets many different frameworks, each one requiring different conditional compiletime constants. This java application should be by far easier to build by targeting the smallest java version to be supported.
I would certainly not expect a java ui on maven central. On 2 Aug 2017 4:29 p.m., "Matt Sicker" <[email protected]> wrote: > Also, as mentioned elsewhere, we should get a Jenkinsfile configured for > this project. It would be a good place to experiment with using the > pipelines feature with a Java project as the only other Logging example we > have so far is for .NET which is a lot more complicated it looks like. > > On 2 August 2017 at 09:27, Matt Sicker <[email protected]> wrote: > > > Getting snapshots configured to upload to the Apache repo would be a good > > first step so that users can download them from the proper location, > though > > I'm not sure if that's appropriate for GUI applications (there are some > > full featured Java applications on Maven Central technically, though > > they're all headless that I know of). Beyond that, I agree that a release > > would be necessary both to get artifacts on dist.a.o along with an > updated > > site with docs. > > > > On 2 August 2017 at 08:24, Ralph Goers <[email protected]> > wrote: > > > >> Work has been done to try to modify the Chainsaw site to meet the ASF > >> branding requirements, although the site does not yet reflect that. > >> However, the download link is clearly problematic as it has the release > >> artifacts inside the web site, which is not compliant with ASF release > >> guidelines. > >> > >> Performing a release would be one way to fix this. > >> > >> Other thoughts? > >> > >> Ralph > >> > > > > > > > > -- > > Matt Sicker <[email protected]> > > > > > > -- > Matt Sicker <[email protected]> >
