You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2008/01/13 19:43:20 UTC
Native 1.1.12 release
All,
Have I missed the 1.1.12 native release vote?
http://archive.apache.org/dist/tomcat/tomcat-connectors/native/ shows a
1.1.12 but neither my recollection nor a check of the archives shows a
release vote for these files. The files are also on the mirrors.
Without a vote, these files need to be removed. In case I have missed the
vote, I will wait 24 hours to be corrected before deleting the files from
dist and the archives (assuming I have enough karma).
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Henri Gomez <he...@gmail.com>.
> The actual situation is bad:
> - a source tarball contains the tcnative sources corresponding to the
> tomcat tag.
> - a binary tarball contains the tcnative sources (in a tarball)
> corresponding to the
> /dist/tomcat/tomcat-connectors/native/tomcat-native-x.y.z-src.tar.gz
> (1.0.10 actualy)
Good
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
jean-frederic clere wrote:
> Mladen Turk wrote:
>> jean-frederic clere wrote:
>>> Mladen Turk wrote:
>>>> jean-frederic clere wrote:
>>>>> Mark Thomas wrote:
>>>>>> jean-frederic clere wrote:
>>>>>>> I think that is all working around the fact that tcnative is not
>>>>>>> mandatory module for Tomcat and it is somehow independent from
>>>>>>> tomcat.
>>>>>>>
>>>>>>> tcnative builds contain cryptosoftware (openssl) and that means
>>>>>>> they may not be available for download in the ASF site. But that
>>>>>>> doesn't prevent us from releasing tcnative sources.
>>>>>>>
>>>>>>> tcnative is not very visible and I am +1 for changing this.
>>>>>>> (updating site and tc build).
>>>>>>
>>>>>> This is my preferred option. There would also need to be a release
>>>>>> vote for all the src distros on a.o/dist.
>>>>>
>>>>> And we should remove any of the files that doesn't get voted.
>>>>>
>>>>>>
>>>>>> If there is some show stopper issue with releasing native
>>>>>> separately that I haven't seen, then I am happy as the svn
>>>>>> solution as an alternative.
>>>>>
>>>>> I am now working on arranging trunk to use a separated tcnative.
>>>>> Part of the logic is already in the actual code.
>>>>>
>>>>
>>>> I can only tell you that I'll vote -1 on any attempt
>>>> to make the tomcat native connector as separate product.
>>>>
>>>> We should better remove it altogether from the Tomcat distribution
>>>> until we either find a way to build it together with Tomcat
>>>> or just forget about it.
>>>
>>> The actual situation is bad:
>>> - a source tarball contains the tcnative sources corresponding to the
>>> tomcat tag.
>>> - a binary tarball contains the tcnative sources (in a tarball)
>>> corresponding to the
>>> /dist/tomcat/tomcat-connectors/native/tomcat-native-x.y.z-src.tar.gz
>>> (1.0.10 actualy)
>>>
>>> We have to fix that.
>>>
>>
>> Right, I agree.
>>
>> The easiest solution would be to just create configure and put
>> it inside the SVN,
>
> configure is a generated file and depend on the apr version...
> then probably we have to add apr sources...
>
No. Apr sources are needed for creating configure.
Right now any 1.2.x version will do, so we can update
it the same way we choose what APR source version we'll
use anyhow for running buildconf.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Mladen Turk wrote:
> jean-frederic clere wrote:
>> Mladen Turk wrote:
>>> jean-frederic clere wrote:
>>>> Mark Thomas wrote:
>>>>> jean-frederic clere wrote:
>>>>>> I think that is all working around the fact that tcnative is not
>>>>>> mandatory module for Tomcat and it is somehow independent from
>>>>>> tomcat.
>>>>>>
>>>>>> tcnative builds contain cryptosoftware (openssl) and that means
>>>>>> they may not be available for download in the ASF site. But that
>>>>>> doesn't prevent us from releasing tcnative sources.
>>>>>>
>>>>>> tcnative is not very visible and I am +1 for changing this.
>>>>>> (updating site and tc build).
>>>>>
>>>>> This is my preferred option. There would also need to be a release
>>>>> vote for all the src distros on a.o/dist.
>>>>
>>>> And we should remove any of the files that doesn't get voted.
>>>>
>>>>>
>>>>> If there is some show stopper issue with releasing native
>>>>> separately that I haven't seen, then I am happy as the svn solution
>>>>> as an alternative.
>>>>
>>>> I am now working on arranging trunk to use a separated tcnative.
>>>> Part of the logic is already in the actual code.
>>>>
>>>
>>> I can only tell you that I'll vote -1 on any attempt
>>> to make the tomcat native connector as separate product.
>>>
>>> We should better remove it altogether from the Tomcat distribution
>>> until we either find a way to build it together with Tomcat
>>> or just forget about it.
>>
>> The actual situation is bad:
>> - a source tarball contains the tcnative sources corresponding to the
>> tomcat tag.
>> - a binary tarball contains the tcnative sources (in a tarball)
>> corresponding to the
>> /dist/tomcat/tomcat-connectors/native/tomcat-native-x.y.z-src.tar.gz
>> (1.0.10 actualy)
>>
>> We have to fix that.
>>
>
> Right, I agree.
>
> The easiest solution would be to just create configure and put
> it inside the SVN,
configure is a generated file and depend on the apr version...
then probably we have to add apr sources...
Cheers
Jean-Frederic
and we won't need the tcnative tarball any more.
> Anyone wishing to build the native would then just download the
> tomcat source tarball.
>
>
> Regards,
> Mladen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
jean-frederic clere wrote:
> Mladen Turk wrote:
>> jean-frederic clere wrote:
>>> Mark Thomas wrote:
>>>> jean-frederic clere wrote:
>>>>> I think that is all working around the fact that tcnative is not
>>>>> mandatory module for Tomcat and it is somehow independent from tomcat.
>>>>>
>>>>> tcnative builds contain cryptosoftware (openssl) and that means
>>>>> they may not be available for download in the ASF site. But that
>>>>> doesn't prevent us from releasing tcnative sources.
>>>>>
>>>>> tcnative is not very visible and I am +1 for changing this.
>>>>> (updating site and tc build).
>>>>
>>>> This is my preferred option. There would also need to be a release
>>>> vote for all the src distros on a.o/dist.
>>>
>>> And we should remove any of the files that doesn't get voted.
>>>
>>>>
>>>> If there is some show stopper issue with releasing native separately
>>>> that I haven't seen, then I am happy as the svn solution as an
>>>> alternative.
>>>
>>> I am now working on arranging trunk to use a separated tcnative. Part
>>> of the logic is already in the actual code.
>>>
>>
>> I can only tell you that I'll vote -1 on any attempt
>> to make the tomcat native connector as separate product.
>>
>> We should better remove it altogether from the Tomcat distribution
>> until we either find a way to build it together with Tomcat
>> or just forget about it.
>
> The actual situation is bad:
> - a source tarball contains the tcnative sources corresponding to the
> tomcat tag.
> - a binary tarball contains the tcnative sources (in a tarball)
> corresponding to the
> /dist/tomcat/tomcat-connectors/native/tomcat-native-x.y.z-src.tar.gz
> (1.0.10 actualy)
>
> We have to fix that.
>
Right, I agree.
The easiest solution would be to just create configure and put
it inside the SVN, and we won't need the tcnative tarball any more.
Anyone wishing to build the native would then just download the
tomcat source tarball.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Mladen Turk wrote:
> jean-frederic clere wrote:
>> Mark Thomas wrote:
>>> jean-frederic clere wrote:
>>>> I think that is all working around the fact that tcnative is not
>>>> mandatory module for Tomcat and it is somehow independent from tomcat.
>>>>
>>>> tcnative builds contain cryptosoftware (openssl) and that means they
>>>> may not be available for download in the ASF site. But that doesn't
>>>> prevent us from releasing tcnative sources.
>>>>
>>>> tcnative is not very visible and I am +1 for changing this.
>>>> (updating site and tc build).
>>>
>>> This is my preferred option. There would also need to be a release
>>> vote for all the src distros on a.o/dist.
>>
>> And we should remove any of the files that doesn't get voted.
>>
>>>
>>> If there is some show stopper issue with releasing native separately
>>> that I haven't seen, then I am happy as the svn solution as an
>>> alternative.
>>
>> I am now working on arranging trunk to use a separated tcnative. Part
>> of the logic is already in the actual code.
>>
>
> I can only tell you that I'll vote -1 on any attempt
> to make the tomcat native connector as separate product.
>
> We should better remove it altogether from the Tomcat distribution
> until we either find a way to build it together with Tomcat
> or just forget about it.
The actual situation is bad:
- a source tarball contains the tcnative sources corresponding to the
tomcat tag.
- a binary tarball contains the tcnative sources (in a tarball)
corresponding to the
/dist/tomcat/tomcat-connectors/native/tomcat-native-x.y.z-src.tar.gz
(1.0.10 actualy)
We have to fix that.
Cheers
Jean-Frederic
>
> Regards,
> Mladen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Mladen Turk wrote:
> jean-frederic clere wrote:
>> Mark Thomas wrote:
>>> jean-frederic clere wrote:
>>>> I think that is all working around the fact that tcnative is not
>>>> mandatory module for Tomcat and it is somehow independent from tomcat.
>>>>
>>>> tcnative builds contain cryptosoftware (openssl) and that means they
>>>> may not be available for download in the ASF site. But that doesn't
>>>> prevent us from releasing tcnative sources.
>>>>
>>>> tcnative is not very visible and I am +1 for changing this.
>>>> (updating site and tc build).
>>>
>>> This is my preferred option. There would also need to be a release
>>> vote for all the src distros on a.o/dist.
>>
>> And we should remove any of the files that doesn't get voted.
>>
>>>
>>> If there is some show stopper issue with releasing native separately
>>> that I haven't seen, then I am happy as the svn solution as an
>>> alternative.
>>
>> I am now working on arranging trunk to use a separated tcnative. Part
>> of the logic is already in the actual code.
>>
>
> I can only tell you that I'll vote -1 on any attempt
> to make the tomcat native connector as separate product.
>
> We should better remove it altogether from the Tomcat distribution
> until we either find a way to build it together with Tomcat
> or just forget about it.
What is in the tomcat tarball is very hard to use it requires
automake/autoconf stuff.
Cheers
Jean-Frederic
>
> Regards,
> Mladen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
jean-frederic clere wrote:
> Mark Thomas wrote:
>> jean-frederic clere wrote:
>>> I think that is all working around the fact that tcnative is not
>>> mandatory module for Tomcat and it is somehow independent from tomcat.
>>>
>>> tcnative builds contain cryptosoftware (openssl) and that means they
>>> may not be available for download in the ASF site. But that doesn't
>>> prevent us from releasing tcnative sources.
>>>
>>> tcnative is not very visible and I am +1 for changing this. (updating
>>> site and tc build).
>>
>> This is my preferred option. There would also need to be a release
>> vote for all the src distros on a.o/dist.
>
> And we should remove any of the files that doesn't get voted.
>
>>
>> If there is some show stopper issue with releasing native separately
>> that I haven't seen, then I am happy as the svn solution as an
>> alternative.
>
> I am now working on arranging trunk to use a separated tcnative. Part of
> the logic is already in the actual code.
>
I can only tell you that I'll vote -1 on any attempt
to make the tomcat native connector as separate product.
We should better remove it altogether from the Tomcat distribution
until we either find a way to build it together with Tomcat
or just forget about it.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Mark Thomas wrote:
> jean-frederic clere wrote:
>> I think that is all working around the fact that tcnative is not
>> mandatory module for Tomcat and it is somehow independent from tomcat.
>>
>> tcnative builds contain cryptosoftware (openssl) and that means they
>> may not be available for download in the ASF site. But that doesn't
>> prevent us from releasing tcnative sources.
>>
>> tcnative is not very visible and I am +1 for changing this. (updating
>> site and tc build).
>
> This is my preferred option. There would also need to be a release vote
> for all the src distros on a.o/dist.
And we should remove any of the files that doesn't get voted.
>
> If there is some show stopper issue with releasing native separately
> that I haven't seen, then I am happy as the svn solution as an alternative.
I am now working on arranging trunk to use a separated tcnative. Part of
the logic is already in the actual code.
Cheers
Jean-Frederic
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
jean-frederic clere wrote:
> I think that is all working around the fact that tcnative is not
> mandatory module for Tomcat and it is somehow independent from tomcat.
>
> tcnative builds contain cryptosoftware (openssl) and that means they may
> not be available for download in the ASF site. But that doesn't prevent
> us from releasing tcnative sources.
>
> tcnative is not very visible and I am +1 for changing this. (updating
> site and tc build).
This is my preferred option. There would also need to be a release vote for
all the src distros on a.o/dist.
If there is some show stopper issue with releasing native separately that I
haven't seen, then I am happy as the svn solution as an alternative.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Guenter Knauf wrote:
> Hi,
>> Still need to figure out what to do with all the other versions in
>> a.o/dist though - we can't just leave them.
>
> well, someone needs to commit them all to a project's SVN subdir like 'tagged_tarballs' or such;
> this way the history would stay available...
Hi
I think that is all working around the fact that tcnative is not
mandatory module for Tomcat and it is somehow independent from tomcat.
tcnative builds contain cryptosoftware (openssl) and that means they may
not be available for download in the ASF site. But that doesn't
prevent us from releasing tcnative sources.
tcnative is not very visible and I am +1 for changing this. (updating
site and tc build).
Cheers
Jean-Frederic
>
> Guen.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Guenter Knauf <fu...@apache.org>.
Hi,
> Still need to figure out what to do with all the other versions in
> a.o/dist though - we can't just leave them.
well, someone needs to commit them all to a project's SVN subdir like 'tagged_tarballs' or such;
this way the history would stay available...
Guen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
Guenter Knauf wrote:
> just an idea / suggestion:
> isnt it usable for the release process that you create a place in SVN where you commit the tarballs, and then download them via http from there instead from a directory location?
That would work. We use the same process for the windows service binaries.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
Mladen Turk wrote:
> Guenter Knauf wrote:
>> just an idea / suggestion:
>> isnt it usable for the release process that you create a place in SVN
>> where you commit the tarballs, and then download them via http from
>> there instead from a directory location?
>>
>
> Finally, an interesting idea.
> You are right. This would make things much easier.
> It would complicate the url pattern for native
> inside build.xml, but who cares.
>
> Anyone?
If we treat it the same way as the windows binaries, it should just be a
local copy shouldn't it?
Sounds like a plan to me.
Still need to figure out what to do with all the other versions in a.o/dist
though - we can't just leave them.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Guenter Knauf wrote:
> Hi Mladen,
>> But that is exactly what we should *not* do.
>> Tomcat comes with it's native, so if you upgrade the
>> Tomcat, upgrade its native as well (if changed)
>
>> Like said, all that can be easy done by simply
>> extending requirements for building Tomcat release.
>> One will need Python and a set of GNU build tools,
>> and we can easily forget the native helper tarballs.
>
>> It would mean that you will need *nix for building
>> the Tomcat release, but that's fine with me.
>
>> If the Tomcat RM's are fine with that, it's a very
>> simple task.
>
> just an idea / suggestion:
> isnt it usable for the release process that you create a place in SVN where you commit the tarballs, and then download them via http from there instead from a directory location?
>
Finally, an interesting idea.
You are right. This would make things much easier.
It would complicate the url pattern for native
inside build.xml, but who cares.
Anyone?
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Guenter Knauf <fu...@apache.org>.
Hi Mladen,
> But that is exactly what we should *not* do.
> Tomcat comes with it's native, so if you upgrade the
> Tomcat, upgrade its native as well (if changed)
> Like said, all that can be easy done by simply
> extending requirements for building Tomcat release.
> One will need Python and a set of GNU build tools,
> and we can easily forget the native helper tarballs.
> It would mean that you will need *nix for building
> the Tomcat release, but that's fine with me.
> If the Tomcat RM's are fine with that, it's a very
> simple task.
just an idea / suggestion:
isnt it usable for the release process that you create a place in SVN where you commit the tarballs, and then download them via http from there instead from a directory location?
Guenter.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
William A. Rowe, Jr. wrote:
> Mladen Turk wrote:
>>
>> OK if you insist.
>
> The *Foundation* insists ;-)
OK ;)
>
>> I suppose we can then use the src tarball from the heanet.ie
>> site (used by the installer BTW) instead dist site.
>
> Or you can remove the file to /dev/dist/, and hold a release vote already?
>
> > Or we can have it inside
> > http://tomcat.apache.org/dev/dist/tomcat-connectors/
>
> /dev/dist/ should be for files that will (ultimately) be released,
> or taken down when they fail to garner the necessary votes. That
> area should not become a clearinghouse - trust me, I've seen it
> happen to snapshots I'd created. It's not for 'public consumption'.
>
The whole problem is miss understanding.
Those files are merely helper files for building Tomcat.
They are not, nor ever be released. They are released together
with Tomcat as tomcat-native.tar.gz inside /bin
I've moved the 1.1.12 and 1.1.10 native connector tag tarballs to
the tomcat/dev/dist.
I'll later change the build.properties.default to point to that
new location. Since it's used only for building Tomcat dist, the
actual url holding them is irrelevant.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Mladen Turk wrote:
>
> OK if you insist.
The *Foundation* insists ;-)
> I suppose we can then use the src tarball from the heanet.ie
> site (used by the installer BTW) instead dist site.
Or you can remove the file to /dev/dist/, and hold a release vote already?
> Or we can have it inside
> http://tomcat.apache.org/dev/dist/tomcat-connectors/
/dev/dist/ should be for files that will (ultimately) be released,
or taken down when they fail to garner the necessary votes. That
area should not become a clearinghouse - trust me, I've seen it
happen to snapshots I'd created. It's not for 'public consumption'.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
Filip Hanik - Dev Lists wrote:
> you're other option is to just vote on tcnative separately, and that way
> utilize all the ASF mirrors and release sites
A vote seems to be the quickest and best solution along with standard
releases (like mod_jk) going forward.
It isn't like there is a lack of people ready to vote +1 on this. We just
need the vote thread.
(IANAL - my terminology may not be spot on)
Until there is a vote all of the legal liability associated with the
release sits with the person who copied the code into www.a.o/dist rather
than with the ASF. Once we have a vote, the release is official and if
there are any problems it is the ASF that gets sued.
Therefore, in the interests of fixing the legal issues ASAP I'll call a
vote in a separate thread.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by jean-frederic clere <jf...@gmail.com>.
Filip Hanik - Dev Lists wrote:
> Mladen Turk wrote:
>> Filip Hanik - Dev Lists wrote:
>>> you're other option is to just vote on tcnative separately, and that
>>> way utilize all the ASF mirrors and release sites
>>>
>>
>> But that is exactly what we should *not* do.
>> Tomcat comes with it's native, so if you upgrade the
>> Tomcat, upgrade its native as well (if changed)
Yes that works because the API is now stable.
Cheers
Jean-Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
William A. Rowe, Jr. wrote:
> I understand the desire to make this
> "easy" for the RM, and the statement that its "useless" from
> outside of tomcat, but the simple fact is that this is a
> released unit of code, separately versioned, determined before
> the "real release" of Tomcat is designated.
>
Look, the whole purpose of "versioning" was to make
the things simpler to release.
It seems now, that we cannot rely on that any more,
for what ever reasons.
The only solution is to change the build.xml so it can
create all that at once, or just drop the native from
the distro.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Mladen Turk wrote:
>
> Because it's native and the one that makes a release needs
> some extra prerequisites to build it.
Part of this confusion is that projects never vote on binary
artifacts, they vote on source code releases.
Because the sources land in tags/ and a tarball, I'd strongly
consider a release vote is manditory before some binary
artifacts are shipped. I understand the desire to make this
"easy" for the RM, and the statement that its "useless" from
outside of tomcat, but the simple fact is that this is a
released unit of code, separately versioned, determined before
the "real release" of Tomcat is designated.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Filip Hanik - Dev Lists wrote:
> Mladen Turk wrote:
>> Filip Hanik - Dev Lists wrote:
>>> you're other option is to just vote on tcnative separately, and that
>>> way utilize all the ASF mirrors and release sites
>>>
>>
>> But that is exactly what we should *not* do.
>> Tomcat comes with it's native, so if you upgrade the
>> Tomcat, upgrade its native as well (if changed)
> except the fact that you could upgrade 5.5.25 (existing tomcat release)
> with the tcnative 1.1.12 (from the new tomcat release)
You can do that with any .jar file as well, right :)
> so if it is not a product, how come it's versioned and tagged
> separately, and not just tagged with Tomcat's tag like the jsp engine or
> the nio connector.
Because it's native and the one that makes a release needs
some extra prerequisites to build it.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Mladen Turk wrote:
> Filip Hanik - Dev Lists wrote:
>> you're other option is to just vote on tcnative separately, and that
>> way utilize all the ASF mirrors and release sites
>>
>
> But that is exactly what we should *not* do.
> Tomcat comes with it's native, so if you upgrade the
> Tomcat, upgrade its native as well (if changed)
except the fact that you could upgrade 5.5.25 (existing tomcat release)
with the tcnative 1.1.12 (from the new tomcat release)
so if it is not a product, how come it's versioned and tagged
separately, and not just tagged with Tomcat's tag like the jsp engine or
the nio connector.
>
> Like said, all that can be easy done by simply
> extending requirements for building Tomcat release.
> One will need Python and a set of GNU build tools,
> and we can easily forget the native helper tarballs.
>
> It would mean that you will need *nix for building
> the Tomcat release, but that's fine with me.
currently we require Win as the build environment (I think it had to do
with NSIS installer or something like that)
the tcnative, is a source tarball, right? so could we make it buildable
with ANT?
>
> If the Tomcat RM's are fine with that, it's a very
> simple task.
I'd be ok with putting it as part of the TC build itself if we don't
want it as a separate product.
Filip
>
>
> Regards,
> Mladen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
Mladen Turk wrote:
> It would mean that you will need *nix for building
> the Tomcat release, but that's fine with me.
>
> If the Tomcat RM's are fine with that, it's a very
> simple task.
That means we require the release to be built on Windows so we can built
the installer and on *nix for native. Essentially we need would need to
build every distribution on two platforms. Whilst it is manageable, that
strikes me significantly increasing the risk of their being subtle
differences between the Windows and Linux distributions.
I still don't see why we can't just do a native release in the same way we
do a mod_jk release. That wouldn't stop us bundling a particular native
release with a Tomcat release and it allows users to easily update the
native library if there are any serious bugs. It would mean there is a
greater requirement to keep the interface stable but I don't see that as a
major issue.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Filip Hanik - Dev Lists wrote:
> you're other option is to just vote on tcnative separately, and that way
> utilize all the ASF mirrors and release sites
>
But that is exactly what we should *not* do.
Tomcat comes with it's native, so if you upgrade the
Tomcat, upgrade its native as well (if changed)
Like said, all that can be easy done by simply
extending requirements for building Tomcat release.
One will need Python and a set of GNU build tools,
and we can easily forget the native helper tarballs.
It would mean that you will need *nix for building
the Tomcat release, but that's fine with me.
If the Tomcat RM's are fine with that, it's a very
simple task.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
you're other option is to just vote on tcnative separately, and that way
utilize all the ASF mirrors and release sites
Filip
Mladen Turk wrote:
> Mark Thomas wrote:
>> Mladen Turk wrote:
>>> Henri Gomez wrote:
>>>>> No, like said, Tomcat Native is voted *together*
>>>>> with Tomcat version that contains it.
>>>>
>>>> May be but the version numbers are different.
>>>>
>>>> It seems very similar to mod_jk in my opinion, since it's a part of
>>>> Tomcat but not mandatory.
>>>>
>>>
>>> But it's not. We don't have announce for Tomcat Native (so no release)
>>
>> Sorry, no. src tarball on dist == release. No ifs ands or buts.
>>
>> There needs to be a vote or the invalid release needs to be pulled.
>>
>
> OK if you insist.
> I suppose we can then use the src tarball from the heanet.ie
> site (used by the installer BTW) instead dist site.
> Or we can have it inside
> http://tomcat.apache.org/dev/dist/tomcat-connectors/
>
> It's just a line inside build.properties file.
> The latest would probably reflect the purpose of the file
> more properly thought.
>
> Regards,
> Mladen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Mark Thomas wrote:
> Mladen Turk wrote:
>> Henri Gomez wrote:
>>>> No, like said, Tomcat Native is voted *together*
>>>> with Tomcat version that contains it.
>>>
>>> May be but the version numbers are different.
>>>
>>> It seems very similar to mod_jk in my opinion, since it's a part of
>>> Tomcat but not mandatory.
>>>
>>
>> But it's not. We don't have announce for Tomcat Native (so no release)
>
> Sorry, no. src tarball on dist == release. No ifs ands or buts.
>
> There needs to be a vote or the invalid release needs to be pulled.
>
OK if you insist.
I suppose we can then use the src tarball from the heanet.ie
site (used by the installer BTW) instead dist site.
Or we can have it inside http://tomcat.apache.org/dev/dist/tomcat-connectors/
It's just a line inside build.properties file.
The latest would probably reflect the purpose of the file
more properly thought.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mark Thomas <ma...@apache.org>.
Mladen Turk wrote:
> Henri Gomez wrote:
>>> No, like said, Tomcat Native is voted *together*
>>> with Tomcat version that contains it.
>>
>> May be but the version numbers are different.
>>
>> It seems very similar to mod_jk in my opinion, since it's a part of
>> Tomcat but not mandatory.
>>
>
> But it's not. We don't have announce for Tomcat Native (so no release)
Sorry, no. src tarball on dist == release. No ifs ands or buts.
There needs to be a vote or the invalid release needs to be pulled.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Henri Gomez wrote:
>> No, like said, Tomcat Native is voted *together*
>> with Tomcat version that contains it.
>
> May be but the version numbers are different.
>
> It seems very similar to mod_jk in my opinion, since it's a part of
> Tomcat but not mandatory.
>
But it's not. We don't have announce for Tomcat Native (so no release),
and tomcat-native.tar.gz (created from tomcat-native-x.x.x.tar.gz)
is integral part of tomcat-x.x.x.tar.gz distribution, referenced
by the build.properties.
So we need tomcat-native.x.x.x.tar.gz to be able to create the
tomcat-native.tar.gz. We could create tomcat-native.tar.gz
directly, but it would require set of native build tools,
so this is just convenient methodology of doing things.
Not to mention that windows installer would need windows
binaries created, etc.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Henri Gomez <he...@gmail.com>.
> No, like said, Tomcat Native is voted *together*
> with Tomcat version that contains it.
May be but the version numbers are different.
It seems very similar to mod_jk in my opinion, since it's a part of
Tomcat but not mandatory.
Just my 0,01 EUR
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Henri Gomez wrote:
>> Tomcat native is not separate product, but rather an integral
>> part of Tomcat distribution. The need for tag is needed because
>> we'd need to put some serious native part build (as well as tools)
>> when building Tomcat. Perhaps some day we'll do that, so we can
>> tag the Tomcat together with native, call the
>> buildconf.sh and create the native .tar.gz all at the same time.
>>
>> Hope that explains.
>
> Do we need to vote right now ?
>
No, like said, Tomcat Native is voted *together*
with Tomcat version that contains it.
The only reason to have a thing we call
"tomcat native version" is so that current and
history builds can be reproduced, because
demanding full set of native build tools for
building tomcat is unrealistic right now thought.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Henri Gomez <he...@gmail.com>.
> Tomcat native is not separate product, but rather an integral
> part of Tomcat distribution. The need for tag is needed because
> we'd need to put some serious native part build (as well as tools)
> when building Tomcat. Perhaps some day we'll do that, so we can
> tag the Tomcat together with native, call the
> buildconf.sh and create the native .tar.gz all at the same time.
>
> Hope that explains.
Do we need to vote right now ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Native 1.1.12 release
Posted by Mladen Turk <mt...@apache.org>.
Mark Thomas wrote:
>
> Have I missed the 1.1.12 native release vote?
>
No :)
>
> Without a vote, these files need to be removed. In case I have missed
> the vote, I will wait 24 hours to be corrected before deleting the files
> from dist and the archives (assuming I have enough karma).
>
Native tag is needed because Tomcat build relies on it,
so when we vote the Tomcat, we vote for the native as well.
Tomcat native is not separate product, but rather an integral
part of Tomcat distribution. The need for tag is needed because
we'd need to put some serious native part build (as well as tools)
when building Tomcat. Perhaps some day we'll do that, so we can
tag the Tomcat together with native, call the
buildconf.sh and create the native .tar.gz all at the same time.
Hope that explains.
Regards,
Mladen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org