Hi, apart from the discussion itself, one thing that should help in these kind of cases is create the project with the new archetype :
mvn archetype:generate -DarchetypeGroupId=org.apache.royale.framework -DarchetypeArtifactId=royale-jewel-module-application-archetype -DarchetypeVersion=0.9.8-SNAPSHOT -Dapplication=royaleapp -Dmodule=royalemodule And also add in this concrete case for Crux: -DincludeCrux=true That will set up all things event metadata that need to be keeped. Apart from that I don't know what should be better. I think Jewel should have its own config rules and maybe have others with jewel & crux, etc... HTH Carlos El jue., 17 sept. 2020 a las 11:23, Christofer Dutz (< [email protected]>) escribió: > Hi Greg, > > the problem I see with templates is that you need to know what you're > using when creating the project. > In my case I'm adding and learning one feature after the other so I would > have to re-create the project whenever I want to add something new. > > But on the other hand ... I think it should be possible to detect that for > example: > > If a given Crux Metadata is used and a Crux context is created, this will > not work if it's not also included, the build could automatically keep the > metadata needed or it could output a message telling the user that if he > wants to use a feature the code seems to be requiring, which changes he has > to add to the build. > > Chris > > > > Am 17.09.20, 10:25 schrieb "Greg Dove" <[email protected]>: > > I think the approach used here is the same as Flex, but that doesn't > mean > it is (was) the most intuitive. > > One reason not to do what you suggest could be that there are a number > of > metadata tags that don't have any value in the build output, but are > used > as ways to 'mark' specific classes for special treatment by the > compiler. > These would/should presumably always have to be explicitly excluded. > > I personally think the way to do it is to have preconfigured templates > or > 'archetypes' (speaking mavenish) that add the metadata inclusions. Or > maybe > some sort of 'add-on' convenience flex-config for end users to > 'load-config+=' for certain libs that specify sets of metadata. > > I do agree that forgetting to add metadata is one of those issues that > is a > head-scratcher until you pick it up. I'd be surprised if most long-term > Flexers haven't done that at one point or another (I certainly have!). > > Cheers, > Greg > > > > > On Thu, Sep 17, 2020 at 8:04 PM Christofer Dutz < > [email protected]> > wrote: > > > Hi all, > > > > as you know I have been involved with the Royale project even when > it was > > still called FlexJS. However even if I invested a huge amount of > time in > > the project, this was mainly in the backend. I never really built > anything > > with FlexJS/Royale. > > I was always looking forward to getting my fingers dirty (in a good > way) > > with building applications. > > > > Now I am finally doing so. And I am probably making some mistakes > typical > > new users of Royale would be making. So I thought it might be good > if I > > write down my findings. > > > > Perhaps it might be good to change some defaults to make it simpler > for > > people to get started. > > > > One of the things that just recently bit be, was AS metadata … I was > > giving Crux a try and really confused why it’s not working at all. > > With my background in build-stuff I compared my settings with the > ones of > > the examples … I noticed I wasn’t explicitly keeping some of the AS > > Metadata. > > > > So I thought … why explicitly add metadata to the list and instead > perhaps > > explicitly drop metadata? I mean if I’m not using something, it will > not be > > kept, so it wouldn’t change anything. > > If I am using Metadata it would per default be kept per default, and > if I > > know it’s not used and it makes the result better, I could exclude > things > > from the build. > > > > This could help avoid some of the problems newcomers might be having? > > > > Chris > > > > > > > > -- Carlos Rovira http://about.me/carlosrovira
