You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Jukka Zitting <ju...@gmail.com> on 2012/07/10 21:33:47 UTC
JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Hi,
On Thu, Jul 5, 2012 at 11:39 PM, Apache Wiki <wi...@apache.org> wrote:
> + Still following the objetive of making the first Apache release:
> +
> + 4 JIRA issues were fixed since last period, the project website has been revamped,
> + and few other niceties & fixes have got into trunk (for example lucene library was
> + upgraded to 3.6.0).
> +
> + 2 Release candidates have been made, but they didn't succeed because of
> + technical issues. Hopefully the third RC will become the first ASF release.
If I understand correctly, these issues were about functionality in
the JSPWiki software itself, not about the technicalities of the
Apache release process.
Do you have any active mentors available to help out in preparing the
release? If not, please post a recent RC also to general@ for review
by the rest of the IPMC. A quick look at one of the RCs brought up a
few issues, most notably the presence of binary dependencies in the
source release archive - a practice that's considered contrary to
Apache principles based on recent discussion on general@.
> + The main issues blocking graduation keep being the same as in the last report:
> + resolution acceptance, community and IPMC graduation vote.
Again, like in April, I'd note that the most pressing blocker is
getting an Apache release out.
Beyond that it looks like community activity in JSPWiki is at a bit
higher level than it used to be for the most part of the past two
years, which is good.
BR,
Jukka Zitting
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Sep 17, 2012 at 12:06 AM, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> almost there, the only remaining issue blocking the release is JSPWIKI-744,
> which is almost complete, should be finished this week (most probably
> tomorrow or Tuesday). So, the vote should be casted real soon.
Great news, thanks for the update!
BR,
Jukka Zitting
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Sep 17, 2012 at 12:06 AM, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> almost there, the only remaining issue blocking the release is JSPWIKI-744,
> which is almost complete, should be finished this week (most probably
> tomorrow or Tuesday). So, the vote should be casted real soon.
Great news, thanks for the update!
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hello Jukka,
almost there, the only remaining issue blocking the release is JSPWIKI-744,
which is almost complete, should be finished this week (most probably
tomorrow or Tuesday). So, the vote should be casted real soon.
br,
juan pablo
On Sun, Sep 16, 2012 at 11:51 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi JSPWiki,
>
> On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com>
> wrote:
> > Again, like in April, I'd note that the most pressing blocker is
> > getting an Apache release out.
>
> Any progress on this front?
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hello Jukka,
almost there, the only remaining issue blocking the release is JSPWIKI-744,
which is almost complete, should be finished this week (most probably
tomorrow or Tuesday). So, the vote should be casted real soon.
br,
juan pablo
On Sun, Sep 16, 2012 at 11:51 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi JSPWiki,
>
> On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com>
> wrote:
> > Again, like in April, I'd note that the most pressing blocker is
> > getting an Apache release out.
>
> Any progress on this front?
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi JSPWiki,
On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Again, like in April, I'd note that the most pressing blocker is
> getting an Apache release out.
Any progress on this front?
BR,
Jukka Zitting
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi JSPWiki,
On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Again, like in April, I'd note that the most pressing blocker is
> getting an Apache release out.
Any progress on this front?
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Dave,
thanks for the tip :-) Actually we're downloading a few LGPL jars via
maven-ant-tasks,
but this approach seems simpler for our libs, as we won't have to deal with
transitive
dependencies.
br,
juan pablo
On Thu, Jul 12, 2012 at 9:51 PM, Dave Fisher <da...@comcast.net> wrote:
>
> On Jul 12, 2012, at 10:38 AM, sebb wrote:
>
> > On 11 July 2012 22:26, Juan Pablo Santos Rodríguez
> > <ju...@gmail.com> wrote:
> >> Oh, my misunderstanding then. If that's the case, then there is one
> >> technicality of the apache release process blocking the release
> >> (distributing dependencies alongside source), although not a tough one.
> >> I'll file a Jira and reflect it at the project incubation status page.
> >>
> >>
> >> regards,
> >> juan pablo
> >>
> >> On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <jukka.zitting@gmail.com
> >wrote:
> >>
> >>> Hi,
> >>>
> >>> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
> >>> <ju...@gmail.com> wrote:
> >>>> Regarding the binary dependencies. Wasn't the discussion on
> general@more
> >>>> focused on (or raised because of) transitive dependencies which were
> >>>> brought into the build and not being AL-compatible?
> >>>
> >>> No, all the dependencies discussed were compliant with Apache
> >>> policies. The problem was about having binaries included in the source
> >>> archive.
> >>>
> >>>> Also, the build is Ant based, so we need them to be there in order to
> be
> >>>> able to build.
> >
> > Not so; Apache JMeter and Tomcat both use Ant and have external
> > dependencies which are not held in SVN.
> >
> >>>
> >>> The proposed solution for this case was to put the dependencies in a
> >>> separate -deps archive, that can be combined with the source release
> >>> to make it buildable. The build script can also automatically download
> >>> such separate binary dependencies.
> >
> > That's what JMeter and Tomcat do: there's a separate Ant task to do
> > the downloads.
> > But you could also use Ant+Ivy.
>
> Apache POI uses ant as well. Here are selected parts of the build.xml:
>
> <!-- the repository to download jars from -->
> <property name="repository.m2" value="http://repo1.maven.org"/>
> <property name="main.lib" location="lib"/>
>
> <!-- jars in the /lib directory, see the fetch-jars target-->
> <property name="main.commons-logging.jar"
> location="${main.lib}/commons-logging-1.1.jar"/>
> <property name="main.commons-logging.url"
>
> value="${repository.m2}/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.jar"/>
> <property name="main.commons-codec.jar"
> location="${main.lib}/commons-codec-1.5.jar"/>
> <property name="main.commons-codec.url"
>
> value="${repository.m2}/maven2/commons-codec/commons-codec/1.5/commons-codec-1.5.jar"/>
> <property name="main.log4j.jar"
> location="${main.lib}/log4j-1.2.13.jar"/>
> <property name="main.log4j.url"
> value="${repository.m2}/maven2/log4j/log4j/1.2.13/log4j-1.2.13.jar"/>
> <property name="main.junit.jar"
> location="${main.lib}/junit-3.8.1.jar"/>
> <property name="main.junit.url"
> value="${repository.m2}/maven2/junit/junit/3.8.1/junit-3.8.1.jar"/>
> <property name="main.ant.jar" location="${main.lib}/ant-1.8.2.jar"/>
> <property name="main.ant.url"
> value="${repository.m2}/maven2/org/apache/ant/ant/1.8.2/ant-1.8.2.jar"/>
>
> <target name="check-jars">
> <condition property="jars.present">
> <or>
> <and>
> <available file="${main.commons-logging.jar}"/>
> <available file="${main.commons-codec.jar}"/>
> <available file="${main.log4j.jar}"/>
> <available file="${main.junit.jar}"/>
> <available file="${main.ant.jar}"/>
> </and>
> <isset property="disconnected"/>
> </or>
> </condition>
> </target>
>
> <target name="fetch-jars" depends="check-jars" unless="jars.present"
> description="Fetches needed JAR files from the Internet">
> <mkdir dir="${main.lib}"/>
> <antcall target="downloadfile">
> <param name="sourcefile" value="${main.commons-logging.url}"/>
> <param name="destfile" value="${main.commons-logging.jar}"/>
> </antcall>
> <antcall target="downloadfile">
> <param name="sourcefile" value="${main.commons-codec.url}"/>
> <param name="destfile" value="${main.commons-codec.jar}"/>
> </antcall>
> <antcall target="downloadfile">
> <param name="sourcefile" value="${main.log4j.url}"/>
> <param name="destfile" value="${main.log4j.jar}"/>
> </antcall>
> <antcall target="downloadfile">
> <param name="sourcefile" value="${main.junit.url}"/>
> <param name="destfile" value="${main.junit.jar}"/>
> </antcall>
> <antcall target="downloadfile">
> <param name="sourcefile" value="${main.ant.url}"/>
> <param name="destfile" value="${main.ant.jar}"/>
> </antcall>
> </target>
>
> HTH,
> Dave
>
>
> >
> >>>
> >>> BR,
> >>>
> >>> Jukka Zitting
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Dave Fisher <da...@comcast.net>.
On Jul 12, 2012, at 10:38 AM, sebb wrote:
> On 11 July 2012 22:26, Juan Pablo Santos Rodríguez
> <ju...@gmail.com> wrote:
>> Oh, my misunderstanding then. If that's the case, then there is one
>> technicality of the apache release process blocking the release
>> (distributing dependencies alongside source), although not a tough one.
>> I'll file a Jira and reflect it at the project incubation status page.
>>
>>
>> regards,
>> juan pablo
>>
>> On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <ju...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
>>> <ju...@gmail.com> wrote:
>>>> Regarding the binary dependencies. Wasn't the discussion on general@more
>>>> focused on (or raised because of) transitive dependencies which were
>>>> brought into the build and not being AL-compatible?
>>>
>>> No, all the dependencies discussed were compliant with Apache
>>> policies. The problem was about having binaries included in the source
>>> archive.
>>>
>>>> Also, the build is Ant based, so we need them to be there in order to be
>>>> able to build.
>
> Not so; Apache JMeter and Tomcat both use Ant and have external
> dependencies which are not held in SVN.
>
>>>
>>> The proposed solution for this case was to put the dependencies in a
>>> separate -deps archive, that can be combined with the source release
>>> to make it buildable. The build script can also automatically download
>>> such separate binary dependencies.
>
> That's what JMeter and Tomcat do: there's a separate Ant task to do
> the downloads.
> But you could also use Ant+Ivy.
Apache POI uses ant as well. Here are selected parts of the build.xml:
<!-- the repository to download jars from -->
<property name="repository.m2" value="http://repo1.maven.org"/>
<property name="main.lib" location="lib"/>
<!-- jars in the /lib directory, see the fetch-jars target-->
<property name="main.commons-logging.jar" location="${main.lib}/commons-logging-1.1.jar"/>
<property name="main.commons-logging.url"
value="${repository.m2}/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.jar"/>
<property name="main.commons-codec.jar" location="${main.lib}/commons-codec-1.5.jar"/>
<property name="main.commons-codec.url"
value="${repository.m2}/maven2/commons-codec/commons-codec/1.5/commons-codec-1.5.jar"/>
<property name="main.log4j.jar" location="${main.lib}/log4j-1.2.13.jar"/>
<property name="main.log4j.url" value="${repository.m2}/maven2/log4j/log4j/1.2.13/log4j-1.2.13.jar"/>
<property name="main.junit.jar" location="${main.lib}/junit-3.8.1.jar"/>
<property name="main.junit.url" value="${repository.m2}/maven2/junit/junit/3.8.1/junit-3.8.1.jar"/>
<property name="main.ant.jar" location="${main.lib}/ant-1.8.2.jar"/>
<property name="main.ant.url" value="${repository.m2}/maven2/org/apache/ant/ant/1.8.2/ant-1.8.2.jar"/>
<target name="check-jars">
<condition property="jars.present">
<or>
<and>
<available file="${main.commons-logging.jar}"/>
<available file="${main.commons-codec.jar}"/>
<available file="${main.log4j.jar}"/>
<available file="${main.junit.jar}"/>
<available file="${main.ant.jar}"/>
</and>
<isset property="disconnected"/>
</or>
</condition>
</target>
<target name="fetch-jars" depends="check-jars" unless="jars.present"
description="Fetches needed JAR files from the Internet">
<mkdir dir="${main.lib}"/>
<antcall target="downloadfile">
<param name="sourcefile" value="${main.commons-logging.url}"/>
<param name="destfile" value="${main.commons-logging.jar}"/>
</antcall>
<antcall target="downloadfile">
<param name="sourcefile" value="${main.commons-codec.url}"/>
<param name="destfile" value="${main.commons-codec.jar}"/>
</antcall>
<antcall target="downloadfile">
<param name="sourcefile" value="${main.log4j.url}"/>
<param name="destfile" value="${main.log4j.jar}"/>
</antcall>
<antcall target="downloadfile">
<param name="sourcefile" value="${main.junit.url}"/>
<param name="destfile" value="${main.junit.jar}"/>
</antcall>
<antcall target="downloadfile">
<param name="sourcefile" value="${main.ant.url}"/>
<param name="destfile" value="${main.ant.jar}"/>
</antcall>
</target>
HTH,
Dave
>
>>>
>>> BR,
>>>
>>> Jukka Zitting
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by sebb <se...@gmail.com>.
On 11 July 2012 22:26, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> Oh, my misunderstanding then. If that's the case, then there is one
> technicality of the apache release process blocking the release
> (distributing dependencies alongside source), although not a tough one.
> I'll file a Jira and reflect it at the project incubation status page.
>
>
> regards,
> juan pablo
>
> On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <ju...@gmail.com>wrote:
>
>> Hi,
>>
>> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
>> <ju...@gmail.com> wrote:
>> > Regarding the binary dependencies. Wasn't the discussion on general@more
>> > focused on (or raised because of) transitive dependencies which were
>> > brought into the build and not being AL-compatible?
>>
>> No, all the dependencies discussed were compliant with Apache
>> policies. The problem was about having binaries included in the source
>> archive.
>>
>> > Also, the build is Ant based, so we need them to be there in order to be
>> > able to build.
Not so; Apache JMeter and Tomcat both use Ant and have external
dependencies which are not held in SVN.
>>
>> The proposed solution for this case was to put the dependencies in a
>> separate -deps archive, that can be combined with the source release
>> to make it buildable. The build script can also automatically download
>> such separate binary dependencies.
That's what JMeter and Tomcat do: there's a separate Ant task to do
the downloads.
But you could also use Ant+Ivy.
>>
>> BR,
>>
>> Jukka Zitting
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by sebb <se...@gmail.com>.
On 11 July 2012 22:26, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> Oh, my misunderstanding then. If that's the case, then there is one
> technicality of the apache release process blocking the release
> (distributing dependencies alongside source), although not a tough one.
> I'll file a Jira and reflect it at the project incubation status page.
>
>
> regards,
> juan pablo
>
> On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <ju...@gmail.com>wrote:
>
>> Hi,
>>
>> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
>> <ju...@gmail.com> wrote:
>> > Regarding the binary dependencies. Wasn't the discussion on general@more
>> > focused on (or raised because of) transitive dependencies which were
>> > brought into the build and not being AL-compatible?
>>
>> No, all the dependencies discussed were compliant with Apache
>> policies. The problem was about having binaries included in the source
>> archive.
>>
>> > Also, the build is Ant based, so we need them to be there in order to be
>> > able to build.
Not so; Apache JMeter and Tomcat both use Ant and have external
dependencies which are not held in SVN.
>>
>> The proposed solution for this case was to put the dependencies in a
>> separate -deps archive, that can be combined with the source release
>> to make it buildable. The build script can also automatically download
>> such separate binary dependencies.
That's what JMeter and Tomcat do: there's a separate Ant task to do
the downloads.
But you could also use Ant+Ivy.
>>
>> BR,
>>
>> Jukka Zitting
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Oh, my misunderstanding then. If that's the case, then there is one
technicality of the apache release process blocking the release
(distributing dependencies alongside source), although not a tough one.
I'll file a Jira and reflect it at the project incubation status page.
regards,
juan pablo
On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
> <ju...@gmail.com> wrote:
> > Regarding the binary dependencies. Wasn't the discussion on general@more
> > focused on (or raised because of) transitive dependencies which were
> > brought into the build and not being AL-compatible?
>
> No, all the dependencies discussed were compliant with Apache
> policies. The problem was about having binaries included in the source
> archive.
>
> > Also, the build is Ant based, so we need them to be there in order to be
> > able to build.
>
> The proposed solution for this case was to put the dependencies in a
> separate -deps archive, that can be combined with the source release
> to make it buildable. The build script can also automatically download
> such separate binary dependencies.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Oh, my misunderstanding then. If that's the case, then there is one
technicality of the apache release process blocking the release
(distributing dependencies alongside source), although not a tough one.
I'll file a Jira and reflect it at the project incubation status page.
regards,
juan pablo
On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
> <ju...@gmail.com> wrote:
> > Regarding the binary dependencies. Wasn't the discussion on general@more
> > focused on (or raised because of) transitive dependencies which were
> > brought into the build and not being AL-compatible?
>
> No, all the dependencies discussed were compliant with Apache
> policies. The problem was about having binaries included in the source
> archive.
>
> > Also, the build is Ant based, so we need them to be there in order to be
> > able to build.
>
> The proposed solution for this case was to put the dependencies in a
> separate -deps archive, that can be combined with the source release
> to make it buildable. The build script can also automatically download
> such separate binary dependencies.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> Regarding the binary dependencies. Wasn't the discussion on general@ more
> focused on (or raised because of) transitive dependencies which were
> brought into the build and not being AL-compatible?
No, all the dependencies discussed were compliant with Apache
policies. The problem was about having binaries included in the source
archive.
> Also, the build is Ant based, so we need them to be there in order to be
> able to build.
The proposed solution for this case was to put the dependencies in a
separate -deps archive, that can be combined with the source release
to make it buildable. The build script can also automatically download
such separate binary dependencies.
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
<ju...@gmail.com> wrote:
> Regarding the binary dependencies. Wasn't the discussion on general@ more
> focused on (or raised because of) transitive dependencies which were
> brought into the build and not being AL-compatible?
No, all the dependencies discussed were compliant with Apache
policies. The problem was about having binaries included in the source
archive.
> Also, the build is Ant based, so we need them to be there in order to be
> able to build.
The proposed solution for this case was to put the dependencies in a
separate -deps archive, that can be combined with the source release
to make it buildable. The build script can also automatically download
such separate binary dependencies.
BR,
Jukka Zitting
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Jukka,
answers inline:
On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Thu, Jul 5, 2012 at 11:39 PM, Apache Wiki <wi...@apache.org> wrote:
> > + Still following the objetive of making the first Apache release:
> > +
> > + 4 JIRA issues were fixed since last period, the project website has
> been revamped,
> > + and few other niceties & fixes have got into trunk (for example
> lucene library was
> > + upgraded to 3.6.0).
> > +
> > + 2 Release candidates have been made, but they didn't succeed because of
> > + technical issues. Hopefully the third RC will become the first ASF
> release.
>
> If I understand correctly, these issues were about functionality in
> the JSPWiki software itself, not about the technicalities of the
> Apache release process.
>
>
exactly.
> Do you have any active mentors available to help out in preparing the
> release? If not, please post a recent RC also to general@ for review
> by the rest of the IPMC. A quick look at one of the RCs brought up a
> few issues, most notably the presence of binary dependencies in the
> source release archive - a practice that's considered contrary to
> Apache principles based on recent discussion on general@.
>
If I recall correctly, I think that we have two active mentors, Craig L
Russell and sam Ruby.
We had 2 more mentors, but they stepped down due to lack of time.
Regarding the binary dependencies. Wasn't the discussion on general@ more
focused on (or raised because of) transitive dependencies which were
brought
into the build and not being AL-compatible?
In our case they're all AL compatible [#1], so that should be fine. We try
to look very
carefully to this issue. For instance, recently we added cobertura+sonar
support, which
weren't AL compatible so we had some discussion [#2] about the suitability
of including
them, given the fact that they were not going to be used to build the main
war. We
decided to not include them b/c they weren't AL compatible.
Also, the build is Ant based, so we need them to be there in order to be
able to build.
[#1] https://issues.apache.org/jira/browse/JSPWIKI-545
[#2]
http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201206.mbox/%3CCAMufup6kANwDJT5aVXo4m4D4Uwnj3Srabm=4NvrMs_fwbWFFBQ@mail.gmail.com%3E
>
> > + The main issues blocking graduation keep being the same as in the last
> report:
> > + resolution acceptance, community and IPMC graduation vote.
>
> Again, like in April, I'd note that the most pressing blocker is
> getting an Apache release out.
>
> Beyond that it looks like community activity in JSPWiki is at a bit
> higher level than it used to be for the most part of the past two
> years, which is good.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
regards,
juan pablo
Re: JSPWiki status (Was: [Incubator Wiki] Update of "July2012" by JuanPabloSantos)
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Jukka,
answers inline:
On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Thu, Jul 5, 2012 at 11:39 PM, Apache Wiki <wi...@apache.org> wrote:
> > + Still following the objetive of making the first Apache release:
> > +
> > + 4 JIRA issues were fixed since last period, the project website has
> been revamped,
> > + and few other niceties & fixes have got into trunk (for example
> lucene library was
> > + upgraded to 3.6.0).
> > +
> > + 2 Release candidates have been made, but they didn't succeed because of
> > + technical issues. Hopefully the third RC will become the first ASF
> release.
>
> If I understand correctly, these issues were about functionality in
> the JSPWiki software itself, not about the technicalities of the
> Apache release process.
>
>
exactly.
> Do you have any active mentors available to help out in preparing the
> release? If not, please post a recent RC also to general@ for review
> by the rest of the IPMC. A quick look at one of the RCs brought up a
> few issues, most notably the presence of binary dependencies in the
> source release archive - a practice that's considered contrary to
> Apache principles based on recent discussion on general@.
>
If I recall correctly, I think that we have two active mentors, Craig L
Russell and sam Ruby.
We had 2 more mentors, but they stepped down due to lack of time.
Regarding the binary dependencies. Wasn't the discussion on general@ more
focused on (or raised because of) transitive dependencies which were
brought
into the build and not being AL-compatible?
In our case they're all AL compatible [#1], so that should be fine. We try
to look very
carefully to this issue. For instance, recently we added cobertura+sonar
support, which
weren't AL compatible so we had some discussion [#2] about the suitability
of including
them, given the fact that they were not going to be used to build the main
war. We
decided to not include them b/c they weren't AL compatible.
Also, the build is Ant based, so we need them to be there in order to be
able to build.
[#1] https://issues.apache.org/jira/browse/JSPWIKI-545
[#2]
http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201206.mbox/%3CCAMufup6kANwDJT5aVXo4m4D4Uwnj3Srabm=4NvrMs_fwbWFFBQ@mail.gmail.com%3E
>
> > + The main issues blocking graduation keep being the same as in the last
> report:
> > + resolution acceptance, community and IPMC graduation vote.
>
> Again, like in April, I'd note that the most pressing blocker is
> getting an Apache release out.
>
> Beyond that it looks like community activity in JSPWiki is at a bit
> higher level than it used to be for the most part of the past two
> years, which is good.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
regards,
juan pablo