Hi all,
I don't see how the javahelp sources can be built using the existing
mechanisms (e.g., it doesn't use maven and neither does its major
dependency). So I'm thinking I should port the sources over to our
repository, but that doesn't fit within the cool flow chart's bounds.
Can I get a yea/nay on which way to go? Given the rate of upgrade
bugs, I don't want to spend time on something that isn't part of the
plan.
Thanks,
Bobby
Begin forwarded message:
> From: Bobby Bissett <Robert.Bissett_at_Sun.COM>
> Date: September 24, 2009 4:44:51 PM EDT
> To: dev_at_glassfish.dev.java.net
> Subject: sources without maven (Re: GFv3 source integration)
> Reply-To: dev_at_glassfish.dev.java.net
>
> Hi all,
>
> It's taking a while for me to build this workspace, so I don't have
> an example handy to answer my own question (if there is one). So I'm
> asking the group, how do I handle a source integration where the
> build.xml file of the module downloads dependencies manually (e.g.,
> not through maven)?
>
> The javahelp project downloads and unpacks these:
>
> https://jdic.dev.java.net/files/documents/880/5715/jdic-0.8.4.1-bin-windows.zip
> http://www.apache.org/dist/tomcat/tomcat-5/v5.5.20/bin/apache-tomcat-5.5.20.zip
>
> Given that the second one there shouldn't be needed (it's for the
> JSP/Servlet APIs), how would I download and build the JDIC
> dependency and then build javahelp using that dependency in the
> maven repository? It looks like I'll have to make a new build.xml
> file for javahelp, which doesn't sound right.
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>