search

SalesforceFoundation / ApexDoc

The latest java source for ApexDoc, a tool to document your Salesforce Apex classes.
BSD 3-Clause "New" or "Revised" License
229 stars 128 forks source link

Fix for Issue #38 #41

Closed Bobnix closed 9 years ago

Bobnix commented 9 years ago

I added and configured a pom file for use with maven. As long as maven is installed on the host machine, the project can be built with mvn clean install.

Bobnix commented 9 years ago

I added a travis ci config file just because it was a trivial amount of effort. It does not force us to use Travis CI, the option is simply there. When we have tests, it would be nice to have it automatically build and test.

ceiroa commented 9 years ago

We have an existing Jenkins instance where we run all our Foundation Products Team builds. It might be nice to get it plugged in there: http://ci.salesforcefoundation.org/

Bobnix commented 9 years ago

Tying it to Jenkins would be great. I have a bit of a crush on Jenkins/Hudson as far as build systems go.

Bobnix commented 9 years ago

What was did your build process look like before? What were the steps to do it?

davidhabib commented 9 years ago

with the ApexDoc project selected in Eclipse, choose File, Export menu command. in the Export dialog, choose Java > Runnable JAR file. On the Runnable JAR File Export page, choose Extract required libraries into generated JAR. (I might have chosen the Package option instead; can't remember).

Bobnix commented 9 years ago

You were 100% right, while this setup worked fine for the maven flow, the export did not. I changed the class filter to grab all the files (including the resources) into the target jar. I also bumped the JRE version while I was at it though I am not sure if you want it set higher.

davidhabib commented 9 years ago

OK, I will merge this and test out to make sure it didn't negatively affect my build in Eclipse.

davidhabib commented 9 years ago

building the jar with Eclipse still works fine, so we are good.

Bobnix commented 9 years ago

Phew, I cant tell you how nervous I was about that one. Eclipse, for me at least, has always been a wonderfully fickle tool. Often times code that builds for one person would flat out refuse due to an otherwise innocuous settings problem. I am happy to see this work.