My intention is to make a public release, which is easily accessible (binaries through Maven central), but mark it as preview somehow to be able to get some feedback before we commit to a final API.
I would prefer if we could use the same group and artifact names as in the final, but include something in the version which marks it as preview. Such as "2.5-beta1" On Sat, Dec 12, 2015 at 12:15 PM, Ralph Goers <[email protected]> wrote: > I believe I could run the release plugin against just his module, but I > have never tried that. Or the process could be done manually. > > Sent from my iPad > > On Dec 11, 2015, at 11:44 PM, Remko Popma <[email protected]> wrote: > > I thought Mikael's intention was to make the scala module part of the next > release, while somehow marking it as experimental so that we can still make > changes to the API depending on user feedback. > > I don't mind either way, but is there any way to release only the scala > module? > > Remko > > Sent from my iPhone > > On 2015/12/12, at 14:56, Ralph Goers <[email protected]> wrote: > > If it builds by default it will be part of the next release, which I am > not certain is assured yet. I think that is why he wants to release it > separately. > > Ralph > > On Dec 11, 2015, at 8:21 PM, Remko Popma <[email protected]> wrote: > > I'm assuming that Mikael has verified some use cases on the dev branch, so > it should be okay to build this module by default. No need for setting up a > separate profile AFAIC. > > Sent from my iPhone > > On 2015/12/12, at 9:43, Ralph Goers <[email protected]> wrote: > > That seems like a bit of a pain. It would be better to specify the > classifier as experimental but you can’t do that in the pom as I recall. I > think you have to specify the project as of type pom and then use the maven > helper plugin to attach it as an artifact with a classifier. > > OTOH, the artifact name could be log4j-scala-experimental. > > Ralph > > On Dec 11, 2015, at 5:28 PM, Gary Gregory <[email protected]> wrote: > > Should the package name include ".experimental." ? > > Gary > > On Fri, Dec 11, 2015 at 3:52 PM, Ralph Goers <[email protected]> > wrote: > >> That is true. In fact, we could add an “experimental" profile to the >> parent pom that has the experimental modules in it. They wouldn’t have to >> build by default. >> >> Ralph >> >> On Dec 11, 2015, at 2:49 PM, Remko Popma <[email protected]> wrote: >> >> Why not just put it on master and _document_ it as "experimental, >> feedback requested". >> >> That way we simply use our existing release process and instead of 2.5.1, >> our next release would be 2.6. >> >> Sent from my iPhone >> >> On 2015/12/12, at 3:05, Ralph Goers <[email protected]> wrote: >> >> With SVN we had a separate branch for experimental stuff. In fact, that >> is where Log4j 2 originated. I am not sure how to do the same thing with >> git. If you have an account at github you could put the project there. But >> we really can’t publish anything officially from there. >> >> If you have a proposal on how to do this please let us know. >> >> Ralph >> >> On Dec 11, 2015, at 10:12 AM, Mikael Ståldal <[email protected]> >> wrote: >> >> I do not really know that it means to do RM stuff for Log4j. >> >> I think it would be enough to release the Scala modules, and let them >> depend on Log4j API 2.5, if that is possible. >> >> On Fri, Dec 11, 2015 at 6:09 PM, Gary Gregory <[email protected]> >> wrote: >> >>> Seems fine with me. Label it 2.6-beta1? Mikael, are you feeling up to >>> trying your hand at RM duties? >>> >>> Should we release just these Scala modules as 2.6-beta1 or the whole >>> suite? >>> >>> Gary >>> >>> On Fri, Dec 11, 2015 at 9:07 AM, Mikael Ståldal < >>> [email protected]> wrote: >>> >>>> So can we release some Scala API preview now when 2.5 is out? >>>> >>>> On Mon, Dec 7, 2015 at 3:58 AM, Gary Gregory <[email protected]> >>>> wrote: >>>> >>>>> On Dec 5, 2015 6:05 AM, "Ralph Goers" <[email protected]> >>>>> wrote: >>>>> > >>>>> > It would make more sense to me to release the scala beta as a single >>>>> separate module. Then integrate it once you are sure. >>>>> >>>>> +1 >>>>> >>>>> Gary >>>>> >>>>> > >>>>> > Speaking of a release I am happy to start the release today if we >>>>> are ready. I just want to review the delete stuff Remko just added. >>>>> > >>>>> > Ralph >>>>> > >>>>> > On Dec 5, 2015, at 6:45 AM, Gary Gregory <[email protected]> >>>>> wrote: >>>>> > >>>>> >> Maybe we could release 2.5 ASAP and the do a 2.6-beta _at the same >>>>> time_ with the Scala modules. >>>>> >> >>>>> >> Gary >>>>> >> >>>>> >> On Dec 4, 2015 6:31 AM, "Mikael Ståldal" <[email protected]> >>>>> wrote: >>>>> >>> >>>>> >>> How should we proceed on this? It would be good to be able to >>>>> release some beta or preview version of this and get some feedback from >>>>> Scala developers before we make the API final. >>>>> >>> >>>>> >>> On Fri, Oct 30, 2015 at 1:10 AM, Ralph Goers < >>>>> [email protected]> wrote: >>>>> >>>> >>>>> >>>> The artifact name does not have to match the directory name. >>>>> However, we were advised that they should or else some of the Maven >>>>> plugins >>>>> might have problems. I think the site plugin was one of them. >>>>> >>>> >>>>> >>>> Ralph >>>>> >>>> >>>>> >>>>> On Oct 29, 2015, at 1:56 PM, Matt Sicker <[email protected]> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> I know you can change the artifact name via <finalName> or >>>>> something like that. >>>>> >>>>> >>>>> >>>>> On 29 October 2015 at 15:52, Gary Gregory < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>> >>>>>> It does in all the maven projects i know. I think certain maven >>>>> behaviors relies on this... >>>>> >>>>>> >>>>> >>>>>> Gary >>>>> >>>>>> >>>>> >>>>>> On Oct 29, 2015 1:21 PM, "Matt Sicker" <[email protected]> >>>>> wrote: >>>>> >>>>>>> >>>>> >>>>>>> The folder name doesn't have to match the module name I >>>>> thought. >>>>> >>>>>>> >>>>> >>>>>>> On 29 October 2015 at 04:23, Mikael Ståldal < >>>>> [email protected]> wrote: >>>>> >>>>>>>> >>>>> >>>>>>>> Yes, look at branch LOG4J-1181 in Git. >>>>> >>>>>>>> >>>>> >>>>>>>> My plan is to add log4j-scala_2.10 as well. >>>>> >>>>>>>> >>>>> >>>>>>>> On Wed, Oct 28, 2015 at 7:51 PM, Gary Gregory < >>>>> [email protected]> wrote: >>>>> >>>>>>>>> >>>>> >>>>>>>>> Right, so the Maven module folder name will be like that >>>>> too, right? >>>>> >>>>>>>>> >>>>> >>>>>>>>> Gary >>>>> >>>>>>>>> >>>>> >>>>>>>>> On Wed, Oct 28, 2015 at 2:11 AM, Mikael Ståldal < >>>>> [email protected]> wrote: >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Yes, Scala does not maintain binary compatibility between >>>>> major versions. There is a convention for encoding this into Maven >>>>> artifact >>>>> IDs, it will be: "log4j-scala_2.10", "log4j-scala_2.11" etc. >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> On Mon, Oct 26, 2015 at 7:29 PM, Matt Sicker < >>>>> [email protected]> wrote: >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> Looks like it could be handy. >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> On 26 October 2015 at 12:29, Gary Gregory < >>>>> [email protected]> wrote: >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> I keep on hearing that Scala suffers from a lot >>>>> compatibility issues from version to version. Would is make sense to tag >>>>> on >>>>> a version to the module to account for this, like log4j-scala-2.11.7? >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> Gary >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 10:18 AM, Mikael Ståldal < >>>>> [email protected]> wrote: >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> I am thinking of making a log4j module, "log4j-scala", >>>>> with a Scala wrapper for Log4j 2, inspired from >>>>> >>>>>>>>>>>>> https://github.com/typesafehub/scala-logging >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> Would that make sense? >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> -- >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> Mikael Ståldal >>>>> >>>>>>>>>>>>> Senior software developer >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> Magine TV >>>>> >>>>>>>>>>>>> [email protected] >>>>> >>>>>>>>>>>>> Regeringsgatan 25 | 111 53 Stockholm, Sweden | >>>>> www.magine.com >>>>> >>>>>>>>>>>>> >>>>> >>>>>>>>>>>>> Privileged and/or Confidential Information may be >>>>> contained in this message. If you are not the addressee indicated in this >>>>> message >>>>> >>>>>>>>>>>>> (or responsible for delivery of the message to such a >>>>> person), you may not copy or deliver this message to anyone. In such case, >>>>> >>>>>>>>>>>>> you should destroy this message and kindly notify the >>>>> sender by reply email. >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> >>>>> >>>>>>>>>>>> -- >>>>> >>>>>>>>>>>> E-Mail: [email protected] | [email protected] >>>>> >>>>>>>>>>>> Java Persistence with Hibernate, Second Edition >>>>> >>>>>>>>>>>> JUnit in Action, Second Edition >>>>> >>>>>>>>>>>> Spring Batch in Action >>>>> >>>>>>>>>>>> Blog: http://garygregory.wordpress.com >>>>> >>>>>>>>>>>> Home: http://garygregory.com/ >>>>> >>>>>>>>>>>> Tweet! http://twitter.com/GaryGregory >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> >>>>> >>>>>>>>>>> -- >>>>> >>>>>>>>>>> Matt Sicker <[email protected]> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> -- >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Mikael Ståldal >>>>> >>>>>>>>>> Senior software developer >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Magine TV >>>>> >>>>>>>>>> [email protected] >>>>> >>>>>>>>>> Regeringsgatan 25 | 111 53 Stockholm, Sweden | >>>>> www.magine.com >>>>> >>>>>>>>>> >>>>> >>>>>>>>>> Privileged and/or Confidential Information may be contained >>>>> in this message. If you are not the addressee indicated in this message >>>>> >>>>>>>>>> (or responsible for delivery of the message to such a >>>>> person), you may not copy or deliver this message to anyone. In such case, >>>>> >>>>>>>>>> you should destroy this message and kindly notify the >>>>> sender by reply email. >>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>>> >>>>>>>>> -- >>>>> >>>>>>>>> E-Mail: [email protected] | [email protected] >>>>> >>>>>>>>> Java Persistence with Hibernate, Second Edition >>>>> >>>>>>>>> JUnit in Action, Second Edition >>>>> >>>>>>>>> Spring Batch in Action >>>>> >>>>>>>>> Blog: http://garygregory.wordpress.com >>>>> >>>>>>>>> Home: http://garygregory.com/ >>>>> >>>>>>>>> Tweet! http://twitter.com/GaryGregory >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> -- >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> Mikael Ståldal >>>>> >>>>>>>> Senior software developer >>>>> >>>>>>>> >>>>> >>>>>>>> Magine TV >>>>> >>>>>>>> [email protected] >>>>> >>>>>>>> Regeringsgatan 25 | 111 53 Stockholm, Sweden | >>>>> www.magine.com >>>>> >>>>>>>> >>>>> >>>>>>>> Privileged and/or Confidential Information may be contained >>>>> in this message. If you are not the addressee indicated in this message >>>>> >>>>>>>> (or responsible for delivery of the message to such a >>>>> person), you may not copy or deliver this message to anyone. In such case, >>>>> >>>>>>>> you should destroy this message and kindly notify the sender >>>>> by reply email. >>>>> >>>>>>> >>>>> >>>>>>> >>>>> >>>>>>> >>>>> >>>>>>> >>>>> >>>>>>> -- >>>>> >>>>>>> Matt Sicker <[email protected]> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Matt Sicker <[email protected]> >>>>> >>>> >>>>> >>>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> >>> -- >>>>> >>> >>>>> >>> >>>>> >>> Mikael Ståldal >>>>> >>> Senior software developer >>>>> >>> >>>>> >>> Magine TV >>>>> >>> [email protected] >>>>> >>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >>>>> >>> >>>>> >>> Privileged and/or Confidential Information may be contained in >>>>> this message. If you are not the addressee indicated in this message >>>>> >>> (or responsible for delivery of the message to such a person), you >>>>> may not copy or deliver this message to anyone. In such case, >>>>> >>> you should destroy this message and kindly notify the sender by >>>>> reply email. >>>>> >>>>> >>>> >>>> >>>> -- >>>> [image: MagineTV] >>>> >>>> *Mikael Ståldal* >>>> Senior software developer >>>> >>>> *Magine TV* >>>> [email protected] >>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >>>> >>>> Privileged and/or Confidential Information may be contained in this >>>> message. If you are not the addressee indicated in this message >>>> (or responsible for delivery of the message to such a person), you may >>>> not copy or deliver this message to anyone. In such case, >>>> you should destroy this message and kindly notify the sender by reply >>>> email. >>>> >>> >>> >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> Java Persistence with Hibernate, Second Edition >>> <http://www.manning.com/bauer3/> >>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >>> Spring Batch in Action <http://www.manning.com/templier/> >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >>> >> >> >> >> -- >> [image: MagineTV] >> >> *Mikael Ståldal* >> Senior software developer >> >> *Magine TV* >> [email protected] >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> >> Privileged and/or Confidential Information may be contained in this >> message. If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may >> not copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply >> email. >> >> >> >> > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > > > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
