Just a few random thoughts:

A) When working in C and Java, we compiled the program, tested it, and shipped 
the very same executable.
We did not want it to get rebuilt - Something may be introduced in that process.

B) I also wonder if there is a way to split up this mailing list to better meet 
the users from the very different user communities. There are some overlapping 
needs between the various languages, but I wonder if there are also 
conversations that may only be interesting to the ruby community.

The group is still relatively small. So prematurely splitting it up into a 
bunch of mailing lists doesn't serve anyone's needs. But wanted to mention that 
there may be a way to partition the group.
And not sure if partitioning it on language, experience, or something else 
makes sense.

C) Documentations for New developers.
So far, there has been great documentation for setting up heroku environments 
and getting a ruby app up and running. It may be an idea to tweak the intro 
page on heroku to list the various environments rather than assume ruby. 
Searching shows that there are other environments in there, so maybe it just 
needs a little organization / cleanup.


It would also be nice to have a bunch of github sample apps e.g.: 
github.com/heroku/sample-java (http://github.com/heroku/sample-java) - seems 
there are a number of sample apps in there. maybe a consistent naming may make 
it easier to read these.
Or maybe there is an account with lots of samples that I did not see.


Very excited about all these great environments. (even though I'm very happy 
remaining in the ruby world)

—Keenan  


On Friday, September 30, 2011 at 12:33 PM, Carson Gross wrote:

> I'll say this again: I think that Heroku is making a mistake by mixing
> the build and the deploy steps in java applications. A lot of
> applications are not built using maven, that don't have easily
> resolvable dependencies, or that might rely on system-specific
> resources. Additionally, a lot of java shops aren't as comfortable
> shipping source code out to third parties as the scripting language
> communities are.
>  
> I feel we should be able to deploy wars/jars locally and deploy them
> directly. It is admittedly different than the rails approach, but it
> fits the java development process much more naturally.
>  
> Cheers,
> Carson
>  
> On Sep 21, 7:00 pm, TomXH <[email protected] (http://clear.net)> wrote:
> > I am trying to port a java application to Heroku. The application has
> > dependencies on many jars. Several of these were available in the
> > Maven repository so no problem.  However, I have a couple that are
> > not available on public repositories. I added these jars to my local
> > maven repository using "mvn install:install....". With that, I am
> > able to build and run my project locally. However, when I push to
> > Heroku, I get an error indicating "artifacts cannot be resolved".
> >  
> > What is the best way to make these jar files available to my
> > application on Heroku? I have to think this is a common problem and
> > there must be a simple answer.
> >  
> > Thanks
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Heroku" group.
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> To unsubscribe from this group, send email to 
> [email protected] 
> (mailto:[email protected]).
> For more options, visit this group at 
> http://groups.google.com/group/heroku?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to