On 20/02/18 13:19, Emmanuel Bourg wrote:
> Le 20/02/2018 à 13:42, Mark Thomas a écrit :
>
>> But they'd be in the source bundle. Isn't that sufficient to build off-line?
>
> Yes it is, and that's fine for Debian (Although currently the Debian
> package doesn't use the source bundle but checks out
Le 20/02/2018 à 13:42, Mark Thomas a écrit :
> But they'd be in the source bundle. Isn't that sufficient to build off-line?
Yes it is, and that's fine for Debian (Although currently the Debian
package doesn't use the source bundle but checks out from SVN, but this
can be changed).
> I'm not clea
On 20/02/18 07:42, Emmanuel Bourg wrote:
> Le 14/02/2018 à 13:11, Rainer Jung a écrit :
>
>> I guess we would bundle the Java sources in any source distribution we
>> provide. So only people wanting to do a release would need to run that
>> "grab Java files from Tomcat" step. The step would be don
Le 14/02/2018 à 13:11, Rainer Jung a écrit :
> I guess we would bundle the Java sources in any source distribution we
> provide. So only people wanting to do a release would need to run that
> "grab Java files from Tomcat" step. The step would be done by the
> release script.
Copying the source f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Emmanuel,
On 2/14/18 6:15 AM, Emmanuel Bourg wrote:
> Le 12/02/2018 à 19:43, Christopher Schultz a écrit :
>
>> Is there also option 3) amend the build process to fetch the
>> source from svn?
>
> This would be a bit inconvenient for Linux distrib
Le 11/02/2018 à 21:36, Mark Thomas a écrit :
> Thoughts? comments?
I'd like to suggest an alternative: what about packaging the Java part
of tomcat-native into a jar (and potentially publishing it to Maven
Central) and then adding it to the Tomcat dependencies?
Emmanuel Bourg
--
Am 14.02.2018 um 12:15 schrieb Emmanuel Bourg:
Le 12/02/2018 à 19:43, Christopher Schultz a écrit :
Is there also option 3) amend the build process to fetch the source
from svn?
This would be a bit inconvenient for Linux distributions like Debian
that build Tomcat in offline mode.
I guess w
Le 12/02/2018 à 19:43, Christopher Schultz a écrit :
> Is there also option 3) amend the build process to fetch the source
> from svn?
This would be a bit inconvenient for Linux distributions like Debian
that build Tomcat in offline mode.
Emmanuel Bourg
-
Am 13.02.2018 um 11:56 schrieb Mark Thomas:
On 12/02/18 18:43, Christopher Schultz wrote:
Mark,
On 2/11/18 3:36 PM, Mark Thomas wrote:
Currently, Tomcat Native uses an svn:external to pull in the
current Java source from trunk. With the switch to git, we'll need
a different solution.
Possib
On 12/02/18 18:43, Christopher Schultz wrote:
> Mark,
>
> On 2/11/18 3:36 PM, Mark Thomas wrote:
>> Currently, Tomcat Native uses an svn:external to pull in the
>> current Java source from trunk. With the switch to git, we'll need
>> a different solution.
>
>> Possible options:
>
>> 1) Stop dist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/11/18 3:36 PM, Mark Thomas wrote:
> Currently, Tomcat Native uses an svn:external to pull in the
> current Java source from trunk. With the switch to git, we'll need
> a different solution.
>
> Possible options:
>
> 1) Stop distributing
Am 11.02.2018 um 21:36 schrieb Mark Thomas:
Currently, Tomcat Native uses an svn:external to pull in the current
Java source from trunk. With the switch to git, we'll need a different
solution.
Possible options:
1) Stop distributing Java elements of Tomcat Native in the Tomcat
Native releas
Currently, Tomcat Native uses an svn:external to pull in the current
Java source from trunk. With the switch to git, we'll need a different
solution.
Possible options:
1) Stop distributing Java elements of Tomcat Native in the Tomcat
Native release
2) Migrate Tomcat Native to git and use a su
13 matches
Mail list logo
