[wildfly-dev] Hacking on WildFly - 2015

[Brandon Gaisford]

Simply acknowledging wildly full and wildly core would go a long way.  Highlight what a developer needs to do to build full to include core (mvn install -Dversion.org.wildfly.core=2.0.0.Alpha5-SNAPSHOT).  Highlight the integration test suite and unit testing infrastructure in place.  Keep it simple.  I got stuck on each of these things the first time.

Brandon

On Jun 24, 2015, at 5:52 AM, Brian Stansberry <brian.stansberry at redhat.com> wrote:

> Just brainstorming here. Perhaps add two pages, "Hacking on WildFly 
> Core" and "Hacking on WildFly Full"?
> 
> And then the existing "Hacking on WildFly" page just describes the core 
> vs full code split and explains how to decide which one it is you want 
> to hack on.
> 
> There will end up being redundant information, as a lot of it is 
> mechanics where just names and paths will be different, but the upside 
> is each page is conceptually clear.
> 
> On 6/23/15 11:57 PM, Brandon Gaisford wrote:
>> Hey All,
>> 
>> I’m hoping an effort is already underway to update the “Hacking on
>> WildFly” development article
>> (https://developer.jboss.org/wiki/HackingOnWildFly) based on all the
>> latest project changes.  I’m tempted to volunteer to do it, but I don’t
>> have enough background yet to pull it off.  The existing article is
>> great and was my gateway into open source development.  However, the
>> article is out of date and needs to be updated to account for the new
>> dual wildfly/wildfly-core project structure.  I’d also like to pass
>> along the development issues I’ve struggled with along the way so others
>> don’t have to repeat the same.  What do you guys think?
>> 
>> Brandon
>> 
>> 
>> 
>> 
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> 
> 
> 
> -- 
> Brian Stansberry
> Senior Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev