You are viewing a plain text version of this content. The canonical link for it is here.
Posted to droids-dev@incubator.apache.org by Chapuis Bertil <bc...@agimem.com> on 2011/02/08 16:19:03 UTC
Re: Droids 0.1 release
Reactivation of the release thread. :-)
I can move the opened issues from 0.1 to 0.2. For the other aspects of the
release, I'm not really familiar with the process.
What has to be done ?
On 24 December 2010 06:56, Otis Gospodnetic <ot...@yahoo.com>wrote:
> Hi Salu & others:
>
> * Does anyone know what it takes to create a release? Droids hasn't
> actually
> had any releases, has it?
>
> * Would anyone be interested in simply making A release off of the trunk
> now?
> I see no reason not to do that. It always helps to have a release. Call
> it
> 0.1.
>
> * Should somebody with some level of understanding of Droids move all
> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody can
> create
> 0.1 off trunk now), so anyone who can review patches knows which patches
> need to
> be reviewed first?
>
> Otis
> ----
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Richard Frovarp <rf...@apache.org>.
On 02/25/2011 03:53 AM, Thorsten Scherler wrote:
> On Fri, 2011-02-25 at 09:13 +0100, Chapuis Bertil wrote:
>> About the documentation file what's the convention? Do we have to put the
>> apache license in their headers?
>
> ASAIR yes, in general all files need the header.
>
There are some exclusions. Certainly binary files are an exclusion.
Filling up CSS and HTML files with headers probably doesn't make sense.
Certainly code should have it, including Javascript. Text docs such as
readmes, todos, change log, commiter lists, etc don't typically have
headers.
Is there a reason those docs are in that area? If the docs are to be
published on a webpage, they should be moved to a different part of the
svn tree. I don't know that I see the benefit of publishing that content
as a maven artifact.
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Fri, 2011-02-25 at 09:13 +0100, Chapuis Bertil wrote:
> About the documentation file what's the convention? Do we have to put the
> apache license in their headers?
ASAIR yes, in general all files need the header.
Regarding the question you raised in other mails:
- yes the changes doc should go in BEFORE
- yes the committer doc should go in BEFORE
Cheers Chapuis for pushing the release.
BTW it is not official yet but we (some Apache committer from Spain
planing an apache barcamp in May in Sevilla. It would be a nice
opportunity to conduct a sprint on droids with all of you and may see
some of you face-to-face.
Would that be interesting for people here?
salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I follow the steps described in
http://www.apache.org/dev/publishing-maven-artifacts.htm<http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot>
.
I encountered the problem in step 2.
On 25 February 2011 11:05, Chapuis Bertil <bc...@agimem.com> wrote:
> simply mvn deploy.
>
>
> On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com> wrote:
>
>> What is the command you tried?
>>
>> Will try it then.
>>
>> salu2
>>
>> On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
>> > I tried to publish the project on the snapshot repository [1]. I get the
>> > following error:
>> >
>> > Error deploying artifact: Authorization failed: Access denied to:
>> >
>> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
>> >
>> > My settings.xml contains the correct servers [2]. I tried with
>> plain-text
>> > and encrypted passwords. The strange thing is that I am able to login
>> the
>> > nexus server through the web interface. The thread [3] is describing a
>> > similar problem. I probably simply don't have the right to deploy. Could
>> > someone with sufficient rights do the release?
>> >
>> > Thanks in advance.
>> >
>> > [1] -
>> >
>> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
>> > [2] - http://maven.apache.org/developers/committer-settings.html
>> > [3] -
>> >
>> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
>> >
>> >
>> > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com> wrote:
>> >
>> > > About the documentation file what's the convention? Do we have to put
>> the
>> > > apache license in their headers?
>> > >
>> > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
>> wrote:
>> > >
>> > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>> > >>
>> > >> Make sure that all your files contain a ASF licence header (look at
>> > >>> the RAT report when in doubt, generated with mvn site)
>> > >>> => mvn rat:check leads to a build failure with "too many unlicensed
>> > >>> files:
>> > >>> 199", looks quite strange. I'd love if someone had a look at this,
>> in my
>> > >>> opinion most classes and resources contains the ASF license header.
>> > >>>
>> > >>>
>> > >> There was this, where the number of correct was reported back instead
>> of
>> > >> the number wrong:
>> > >>
>> > >> https://issues.apache.org/jira/browse/RAT-35
>> > >>
>> > >> I don't know if it was fixed in 0.7 or not.
>> > >>
>> > >> At the bottom you will see the problem files. Shouldn't docs come out
>> of
>> > >> this area of svn?
>> > >>
>> > >> The most troublesome of the files are these two:
>> > >>
>> > >> droids-examples/src/main/java/org/apache/droids/App.java
>> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> > >>
>> > >> They've got GPL headers on them, but on the positive side they don't
>> do
>> > >> anything. They have been removed in r1074224.
>> > >>
>> > >> docs/mail-lists.dispatcher.css
>> > >> docs/linkmap.html
>> > >> docs/changes.dispatcher.css
>> > >> docs/default.html
>> > >> docs/contrib.html
>> > >> docs/index.dispatcher.css
>> > >> docs/mail-lists.html
>> > >> docs/default.dispatcher.css
>> > >> docs/contrib.dispatcher.css
>> > >> docs/themes/droids.css
>> > >> docs/api/droids-norobots/package-list
>> > >> docs/api/droids-wicket/package-list
>> > >> docs/api/droids-tika/package-list
>> > >> docs/api/droids-solr/package-list
>> > >> docs/api/droids-core/package-list
>> > >> docs/api/droids-spring/package-list
>> > >> docs/develope.html
>> > >> docs/changes.rss
>> > >> docs/develope.dispatcher.css
>> > >> docs/changes.html
>> > >> docs/todo.html
>> > >> docs/todo.dispatcher.css
>> > >> docs/index.html
>> > >> docs/linkmap.dispatcher.css
>> > >> docs/develop/develop.dispatcher.css
>> > >> docs/develop/hello-crawler.html
>> > >> docs/develop/develop.html
>> > >> docs/develop/hello-crawler.dispatcher.css
>> > >> docs/install.html
>> > >> docs/install.dispatcher.css
>> > >> droids-examples/pom.xml
>> > >> droids-examples/src/main/java/org/apache/droids/App.java
>> > >> droids-examples/src/site/apt/index.apt
>> > >> droids-examples/src/site/site.xml
>> > >> droids-examples/src/site/fml/faq.fml
>> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> > >> testing.properties
>> > >> doap.rdf
>> > >> tools/ant/bin/README-forrest-upgrade.txt
>> > >> src/templates/component/DROIDS-README.txt
>> > >> src/documentation/content/xdocs/images/droidsOverview.svg
>> > >> src/documentation/resources/themes/common/css/droids.css
>> > >> droids-crawler-web/droids-crawler-web.iml
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > Bertil Chapuis
>> > > Agimem Sàrl
>> > > http://www.agimem.com
>> > >
>> > >
>> >
>> >
>>
>> --
>> Thorsten Scherler <thorsten.at.apache.org>
>> codeBusters S.L. - web based systems
>> <consulting, training and solutions>
>> http://www.codebusters.es/
>>
>>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Thanks, we are encountering difficulties with the release process. in fact
last week, we started solving some of the 0.0.2 issues on the trunk.
Yesterday I created a branch/stable which may be used to release 0.0.1
without blocking the work on 0.0.2.
Best regards,
Bertil
On 17 March 2011 23:02, Otis Gospodnetic <og...@yahoo.com> wrote:
> Hi,
>
> So it looks like only 1 issue remains for 0.0.1?
> https://issues.apache.org/jira/browse/DROIDS/fixforversion/12313486
>
> Good work Bertil & Co.!
>
> Otis
>
>
>
>
> ----- Original Message ----
> > From: Chapuis Bertil <bc...@agimem.com>
> > To: droids-dev@incubator.apache.org
> > Sent: Thu, March 10, 2011 4:41:21 PM
> > Subject: Re: Droids 0.1 release
> >
> > Hello,
> >
> > What's the current status for the release? Should we start working on
> 0.0.2
> > without this step? The problem I see is that by applying the small
> patches
> > on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I
> tried
> > to apply are already applied partially. So the more we wait to apply
> them
> > the more work we will have.
> >
> > Thanks for your answer,
> >
> > Bertil
> >
> > On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
> >
> > >
> > >
> > > On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> > >
> > >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> > >> > I had a look at the different way available to automatically
> generate
> > >> the
> > >> > team list and changes files. It seems it will be difficult to use
> them
> > >> with
> > >> > our current documentation workflow. In consequence I hard coded
> the
> > >> > team-list.xml and the changes.xml files in the documentation
> folder.
> > >> >
> > >> > For the project team, I took all the committers and all the
> contributors
> > >> who
> > >> > provided patches.
> > >>
> > >> The problem with this as I see it is that this puts a too high value
> on
> > >> code contributions and too less on community contributions. For
> example
> > >> Otis who mainly contributed to the mailing list is not listed on the
> > >> team but personally I value his contribution equally as a patch.
> > >>
> > >> To draw a line I think we should only list official committers as
> the
> > >> TEAM.
> > >>
> > >> WDYT?
> > >>
> > >
> > > That's ok for me. I did it without really knowing what the practices
> are
> in
> > > this area.
> > >
> > >
> > >>
> > >> > For the changes, I used the report generated by jira for 0.0.1 and
> > >> formated
> > >> > it in xdoc.
> > >> > Please check if modifications or additions are required.
> > >>
> > >> That is fine, I see the initial changes more as pin pointing the main
> > >> feature of droids but yours is good.
> > >>
> > >> >
> > >> > I think the aim for 0.0.1 is to release as soon as possible. It
> seems
> > >> > several people are motivated to work on 0.0.2.
> > >>
> > >> Yeah, I just tried the deploy again (had to fix an issue with the
> > >> version of the buildnumber-maven-plugin) but as well get a 401. Will
> > >> review my config again.
> > >>
> > >
> > > I just read one of the article [1] pointed by someone in the general
> > > mailing list. The idea is to create a long lived stable branch and to
> keep
> > > the trunk really dynamic. It may be a really good practice for us,
> what do
> > > you think?
> > >
> > > [1] -
> > >
> http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> > >
> > >
> > >>
> > >> salu2
> > >>
> > >>
> > >> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> > >> wrote:
> > >> >
> > >> > > Hi,
> > >> > > About the changes.xml file - is there anything to add here,
> seeing how
> > >> > > there
> > >> > > is no previous release?
> > >> > > Should the release use the apache-release maven profile
> > >> (-Papache-release)?
> > >> > > Is there anything I can help with?
> > >> > > Eugen.
> > >> > >
> > >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> > >> scherler@gmail.com
> > >> > > >wrote:
> > >> > >
> > >> > > > Ok, will try that this afternoon, need to attend some meetings
> now.
> > >> > > >
> > >> > > > salu2
> > >> > > >
> > >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > >> > > > > simply mvn deploy.
> > >> > > > >
> > >> > > > > On 25 February 2011 10:55, Thorsten Scherler <
> scherler@gmail.com>
> > >> > > wrote:
> > >> > > > >
> > >> > > > > > What is the command you tried?
> > >> > > > > >
> > >> > > > > > Will try it then.
> > >> > > > > >
> > >> > > > > > salu2
> > >> > > > > >
> > >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > >> > > > > > > I tried to publish the project on the snapshot repository
> [1].
> > >> I
> > >> > > get
> > >> > > > the
> > >> > > > > > > following error:
> > >> > > > > > >
> > >> > > > > > > Error deploying artifact: Authorization failed: Access
> denied
> > >> to:
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> >
> > >> > > > > > >
> > >> > > > > > > My settings.xml contains the correct servers [2]. I tried
> with
> > >> > > > plain-text
> > >> > > > > > > and encrypted passwords. The strange thing is that I am
> able
> > >> to
> > >> > > login
> > >> > > > the
> > >> > > > > > > nexus server through the web interface. The thread [3] is
> > >> > > describing
> > >> > > > a
> > >> > > > > > > similar problem. I probably simply don't have the right
> to
> > >> deploy.
> > >> > > > Could
> > >> > > > > > > someone with sufficient rights do the release?
> > >> > > > > > >
> > >> > > > > > > Thanks in advance.
> > >> > > > > > >
> > >> > > > > > > [1] -
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > >> > > > > > > [2] -
> > >> http://maven.apache.org/developers/committer-settings.html
> > >> > > > > > > [3] -
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
> > >> bchapuis@agimem.com>
> > >> > > > wrote:
> > >> > > > > > >
> > >> > > > > > > > About the documentation file what's the convention? Do
> we
> > >> have to
> > >> > > > put
> > >> > > > > > the
> > >> > > > > > > > apache license in their headers?
> > >> > > > > > > >
> > >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> > >> rfrovarp@apache.org>
> > >> > > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > >> > > > > > > >>
> > >> > > > > > > >> Make sure that all your files contain a ASF licence
> header
> > >> > > (look
> > >> > > > at
> > >> > > > > > > >>> the RAT report when in doubt, generated with mvn
> site)
> > >> > > > > > > >>> => mvn rat:check leads to a build failure with "too
> many
> > >> > > > unlicensed
> > >> > > > > > > >>> files:
> > >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a
> look
> > >> at
> > >> > > > this, in
> > >> > > > > > my
> > >> > > > > > > >>> opinion most classes and resources contains the ASF
> > >> license
> > >> > > > header.
> > >> > > > > > > >>>
> > >> > > > > > > >>>
> > >> > > > > > > >> There was this, where the number of correct was
> reported
> > >> back
> > >> > > > instead
> > >> > > > > > of
> > >> > > > > > > >> the number wrong:
> > >> > > > > > > >>
> > >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > >> > > > > > > >>
> > >> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> > >> > > > > > > >>
> > >> > > > > > > >> At the bottom you will see the problem files.
> Shouldn't
> > >> docs
> > >> > > come
> > >> > > > out
> > >> > > > > > of
> > >> > > > > > > >> this area of svn?
> > >> > > > > > > >>
> > >> > > > > > > >> The most troublesome of the files are these two:
> > >> > > > > > > >>
> > >> > > > > > > >>
> droids-examples/src/main/java/org/apache/droids/App.java
> > >> > > > > > > >>
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >> > > > > > > >>
> > >> > > > > > > >> They've got GPL headers on them, but on the positive
> side
> > >> they
> > >> > > > don't
> > >> > > > > > do
> > >> > > > > > > >> anything. They have been removed in r1074224.
> > >> > > > > > > >>
> > >> > > > > > > >> docs/mail-lists.dispatcher.css
> > >> > > > > > > >> docs/linkmap.html
> > >> > > > > > > >> docs/changes.dispatcher.css
> > >> > > > > > > >> docs/default.html
> > >> > > > > > > >> docs/contrib.html
> > >> > > > > > > >> docs/index.dispatcher.css
> > >> > > > > > > >> docs/mail-lists.html
> > >> > > > > > > >> docs/default.dispatcher.css
> > >> > > > > > > >> docs/contrib.dispatcher.css
> > >> > > > > > > >> docs/themes/droids.css
> > >> > > > > > > >> docs/api/droids-norobots/package-list
> > >> > > > > > > >> docs/api/droids-wicket/package-list
> > >> > > > > > > >> docs/api/droids-tika/package-list
> > >> > > > > > > >> docs/api/droids-solr/package-list
> > >> > > > > > > >> docs/api/droids-core/package-list
> > >> > > > > > > >> docs/api/droids-spring/package-list
> > >> > > > > > > >> docs/develope.html
> > >> > > > > > > >> docs/changes.rss
> > >> > > > > > > >> docs/develope.dispatcher.css
> > >> > > > > > > >> docs/changes.html
> > >> > > > > > > >> docs/todo.html
> > >> > > > > > > >> docs/todo.dispatcher.css
> > >> > > > > > > >> docs/index.html
> > >> > > > > > > >> docs/linkmap.dispatcher.css
> > >> > > > > > > >> docs/develop/develop.dispatcher.css
> > >> > > > > > > >> docs/develop/hello-crawler.html
> > >> > > > > > > >> docs/develop/develop.html
> > >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> > >> > > > > > > >> docs/install.html
> > >> > > > > > > >> docs/install.dispatcher.css
> > >> > > > > > > >> droids-examples/pom.xml
> > >> > > > > > > >>
> droids-examples/src/main/java/org/apache/droids/App.java
> > >> > > > > > > >> droids-examples/src/site/apt/index.apt
> > >> > > > > > > >> droids-examples/src/site/site.xml
> > >> > > > > > > >> droids-examples/src/site/fml/faq.fml
> > >> > > > > > > >>
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >> > > > > > > >> testing.properties
> > >> > > > > > > >> doap.rdf
> > >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > >> > > > > > > >> src/templates/component/DROIDS-README.txt
> > >> > > > > > > >>
> src/documentation/content/xdocs/images/droidsOverview.svg
> > >> > > > > > > >>
> src/documentation/resources/themes/common/css/droids.css
> > >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> > >> > > > > > > >>
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > --
> > >> > > > > > > > Bertil Chapuis
> > >> > > > > > > > Agimem Sàrl
> > >> > > > > > > > http://www.agimem.com
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> > >> > > > > > codeBusters S.L. - web based systems
> > >> > > > > > <consulting, training and solutions>
> > >> > > > > > http://www.codebusters.es/
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > > --
> > >> > > > Thorsten Scherler <thorsten.at.apache.org>
> > >> > > > codeBusters S.L. - web based systems
> > >> > > > <consulting, training and solutions>
> > >> > > > http://www.codebusters.es/
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >>
> > >> --
> > >> Thorsten Scherler <thorsten.at.apache.org>
> > >> codeBusters S.L. - web based systems
> > >> <consulting, training and solutions>
> > >> http://www.codebusters.es/
> > >>
> > >>
> > >
> > >
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> > >
> >
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Otis Gospodnetic <og...@yahoo.com>.
Hi,
So it looks like only 1 issue remains for 0.0.1?
https://issues.apache.org/jira/browse/DROIDS/fixforversion/12313486
Good work Bertil & Co.!
Otis
----- Original Message ----
> From: Chapuis Bertil <bc...@agimem.com>
> To: droids-dev@incubator.apache.org
> Sent: Thu, March 10, 2011 4:41:21 PM
> Subject: Re: Droids 0.1 release
>
> Hello,
>
> What's the current status for the release? Should we start working on 0.0.2
> without this step? The problem I see is that by applying the small patches
> on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I tried
> to apply are already applied partially. So the more we wait to apply them
> the more work we will have.
>
> Thanks for your answer,
>
> Bertil
>
> On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
>
> >
> >
> > On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> >
> >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> >> > I had a look at the different way available to automatically generate
> >> the
> >> > team list and changes files. It seems it will be difficult to use them
> >> with
> >> > our current documentation workflow. In consequence I hard coded the
> >> > team-list.xml and the changes.xml files in the documentation folder.
> >> >
> >> > For the project team, I took all the committers and all the contributors
> >> who
> >> > provided patches.
> >>
> >> The problem with this as I see it is that this puts a too high value on
> >> code contributions and too less on community contributions. For example
> >> Otis who mainly contributed to the mailing list is not listed on the
> >> team but personally I value his contribution equally as a patch.
> >>
> >> To draw a line I think we should only list official committers as the
> >> TEAM.
> >>
> >> WDYT?
> >>
> >
> > That's ok for me. I did it without really knowing what the practices are
in
> > this area.
> >
> >
> >>
> >> > For the changes, I used the report generated by jira for 0.0.1 and
> >> formated
> >> > it in xdoc.
> >> > Please check if modifications or additions are required.
> >>
> >> That is fine, I see the initial changes more as pin pointing the main
> >> feature of droids but yours is good.
> >>
> >> >
> >> > I think the aim for 0.0.1 is to release as soon as possible. It seems
> >> > several people are motivated to work on 0.0.2.
> >>
> >> Yeah, I just tried the deploy again (had to fix an issue with the
> >> version of the buildnumber-maven-plugin) but as well get a 401. Will
> >> review my config again.
> >>
> >
> > I just read one of the article [1] pointed by someone in the general
> > mailing list. The idea is to create a long lived stable branch and to keep
> > the trunk really dynamic. It may be a really good practice for us, what do
> > you think?
> >
> > [1] -
> > http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> >
> >
> >>
> >> salu2
> >>
> >>
> >> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> >> wrote:
> >> >
> >> > > Hi,
> >> > > About the changes.xml file - is there anything to add here, seeing how
> >> > > there
> >> > > is no previous release?
> >> > > Should the release use the apache-release maven profile
> >> (-Papache-release)?
> >> > > Is there anything I can help with?
> >> > > Eugen.
> >> > >
> >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> >> scherler@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > Ok, will try that this afternoon, need to attend some meetings now.
> >> > > >
> >> > > > salu2
> >> > > >
> >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> >> > > > > simply mvn deploy.
> >> > > > >
> >> > > > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
> >> > > wrote:
> >> > > > >
> >> > > > > > What is the command you tried?
> >> > > > > >
> >> > > > > > Will try it then.
> >> > > > > >
> >> > > > > > salu2
> >> > > > > >
> >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> >> > > > > > > I tried to publish the project on the snapshot repository [1].
> >> I
> >> > > get
> >> > > > the
> >> > > > > > > following error:
> >> > > > > > >
> >> > > > > > > Error deploying artifact: Authorization failed: Access denied
> >> to:
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >>
>https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
>
> >> > > > > > >
> >> > > > > > > My settings.xml contains the correct servers [2]. I tried with
> >> > > > plain-text
> >> > > > > > > and encrypted passwords. The strange thing is that I am able
> >> to
> >> > > login
> >> > > > the
> >> > > > > > > nexus server through the web interface. The thread [3] is
> >> > > describing
> >> > > > a
> >> > > > > > > similar problem. I probably simply don't have the right to
> >> deploy.
> >> > > > Could
> >> > > > > > > someone with sufficient rights do the release?
> >> > > > > > >
> >> > > > > > > Thanks in advance.
> >> > > > > > >
> >> > > > > > > [1] -
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> >> > > > > > > [2] -
> >> http://maven.apache.org/developers/committer-settings.html
> >> > > > > > > [3] -
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
> >> bchapuis@agimem.com>
> >> > > > wrote:
> >> > > > > > >
> >> > > > > > > > About the documentation file what's the convention? Do we
> >> have to
> >> > > > put
> >> > > > > > the
> >> > > > > > > > apache license in their headers?
> >> > > > > > > >
> >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> >> rfrovarp@apache.org>
> >> > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> >> > > > > > > >>
> >> > > > > > > >> Make sure that all your files contain a ASF licence header
> >> > > (look
> >> > > > at
> >> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
> >> > > > > > > >>> => mvn rat:check leads to a build failure with "too many
> >> > > > unlicensed
> >> > > > > > > >>> files:
> >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a look
> >> at
> >> > > > this, in
> >> > > > > > my
> >> > > > > > > >>> opinion most classes and resources contains the ASF
> >> license
> >> > > > header.
> >> > > > > > > >>>
> >> > > > > > > >>>
> >> > > > > > > >> There was this, where the number of correct was reported
> >> back
> >> > > > instead
> >> > > > > > of
> >> > > > > > > >> the number wrong:
> >> > > > > > > >>
> >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> >> > > > > > > >>
> >> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> >> > > > > > > >>
> >> > > > > > > >> At the bottom you will see the problem files. Shouldn't
> >> docs
> >> > > come
> >> > > > out
> >> > > > > > of
> >> > > > > > > >> this area of svn?
> >> > > > > > > >>
> >> > > > > > > >> The most troublesome of the files are these two:
> >> > > > > > > >>
> >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> >> > > > > > > >>
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >> > > > > > > >>
> >> > > > > > > >> They've got GPL headers on them, but on the positive side
> >> they
> >> > > > don't
> >> > > > > > do
> >> > > > > > > >> anything. They have been removed in r1074224.
> >> > > > > > > >>
> >> > > > > > > >> docs/mail-lists.dispatcher.css
> >> > > > > > > >> docs/linkmap.html
> >> > > > > > > >> docs/changes.dispatcher.css
> >> > > > > > > >> docs/default.html
> >> > > > > > > >> docs/contrib.html
> >> > > > > > > >> docs/index.dispatcher.css
> >> > > > > > > >> docs/mail-lists.html
> >> > > > > > > >> docs/default.dispatcher.css
> >> > > > > > > >> docs/contrib.dispatcher.css
> >> > > > > > > >> docs/themes/droids.css
> >> > > > > > > >> docs/api/droids-norobots/package-list
> >> > > > > > > >> docs/api/droids-wicket/package-list
> >> > > > > > > >> docs/api/droids-tika/package-list
> >> > > > > > > >> docs/api/droids-solr/package-list
> >> > > > > > > >> docs/api/droids-core/package-list
> >> > > > > > > >> docs/api/droids-spring/package-list
> >> > > > > > > >> docs/develope.html
> >> > > > > > > >> docs/changes.rss
> >> > > > > > > >> docs/develope.dispatcher.css
> >> > > > > > > >> docs/changes.html
> >> > > > > > > >> docs/todo.html
> >> > > > > > > >> docs/todo.dispatcher.css
> >> > > > > > > >> docs/index.html
> >> > > > > > > >> docs/linkmap.dispatcher.css
> >> > > > > > > >> docs/develop/develop.dispatcher.css
> >> > > > > > > >> docs/develop/hello-crawler.html
> >> > > > > > > >> docs/develop/develop.html
> >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> >> > > > > > > >> docs/install.html
> >> > > > > > > >> docs/install.dispatcher.css
> >> > > > > > > >> droids-examples/pom.xml
> >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> >> > > > > > > >> droids-examples/src/site/apt/index.apt
> >> > > > > > > >> droids-examples/src/site/site.xml
> >> > > > > > > >> droids-examples/src/site/fml/faq.fml
> >> > > > > > > >>
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >> > > > > > > >> testing.properties
> >> > > > > > > >> doap.rdf
> >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> >> > > > > > > >> src/templates/component/DROIDS-README.txt
> >> > > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> >> > > > > > > >> src/documentation/resources/themes/common/css/droids.css
> >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> >> > > > > > > >>
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > --
> >> > > > > > > > Bertil Chapuis
> >> > > > > > > > Agimem Sàrl
> >> > > > > > > > http://www.agimem.com
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> >> > > > > > codeBusters S.L. - web based systems
> >> > > > > > <consulting, training and solutions>
> >> > > > > > http://www.codebusters.es/
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > > --
> >> > > > Thorsten Scherler <thorsten.at.apache.org>
> >> > > > codeBusters S.L. - web based systems
> >> > > > <consulting, training and solutions>
> >> > > > http://www.codebusters.es/
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >>
> >> --
> >> Thorsten Scherler <thorsten.at.apache.org>
> >> codeBusters S.L. - web based systems
> >> <consulting, training and solutions>
> >> http://www.codebusters.es/
> >>
> >>
> >
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
> >
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Fri, 2011-03-18 at 07:56 -0500, Richard Frovarp wrote:
> On 3/18/2011 7:04 AM, Thorsten Scherler wrote:
> > On Fri, 2011-03-18 at 11:52 +0100, Chapuis Bertil wrote:
> >> +1
> >>
> >> Is there someone with sufficient rights to publish the release on the maven
> >> repository?
> > Actually all of our committer should have enough rights. @Richard you
> > did RM on lenya many times, but we never published to maven, or?
> >
> > However we may want to ask on infrastructure what the problem may be.
> >
> > salu2
> >
>
> Right, we've never published to maven, so that would be something new.
> I'd be willing to be the RM for this release and get things figured out.
That would be awesome. Many thanks!
salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Mon, 2011-03-21 at 21:10 +0100, Chapuis Bertil wrote:
> r1080355 is probably the best candidate for the release. branch/stable is
> based on this revision. Some modifications may be required on the main pom
> file to release.
+1
Actually we may directly use the stable branch Bertil created.
wdyt?
salu2
>
>
>
> On 21 March 2011 20:57, Richard Frovarp <rf...@apache.org> wrote:
>
> > On 03/19/2011 07:14 AM, Chapuis Bertil wrote:
> >
> >> Many thanks to Richard. That's really nice to see that there is a will to
> >> release Droids. I created a stable branch in r1082122 and applied
> >> DROIDS-56
> >> in r1082332. Should we revert this last commit to release from the trunk ?
> >>
> >>
> >>
> > Well, that's the thing. I'll do the release work, but at this point we
> > don't have an approved set of code to release. Do we want to call a vote on
> > trunk or what?
> >
> > Given that this is in the incubator, who's votes actually count towards
> > doing a release? I imagine it would be the PPMC, but I'm not even sure who
> > is on that.
> >
>
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
r1080355 is probably the best candidate for the release. branch/stable is
based on this revision. Some modifications may be required on the main pom
file to release.
On 21 March 2011 20:57, Richard Frovarp <rf...@apache.org> wrote:
> On 03/19/2011 07:14 AM, Chapuis Bertil wrote:
>
>> Many thanks to Richard. That's really nice to see that there is a will to
>> release Droids. I created a stable branch in r1082122 and applied
>> DROIDS-56
>> in r1082332. Should we revert this last commit to release from the trunk ?
>>
>>
>>
> Well, that's the thing. I'll do the release work, but at this point we
> don't have an approved set of code to release. Do we want to call a vote on
> trunk or what?
>
> Given that this is in the incubator, who's votes actually count towards
> doing a release? I imagine it would be the PPMC, but I'm not even sure who
> is on that.
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Richard Frovarp <rf...@apache.org>.
On 03/19/2011 07:14 AM, Chapuis Bertil wrote:
> Many thanks to Richard. That's really nice to see that there is a will to
> release Droids. I created a stable branch in r1082122 and applied DROIDS-56
> in r1082332. Should we revert this last commit to release from the trunk ?
>
>
Well, that's the thing. I'll do the release work, but at this point we
don't have an approved set of code to release. Do we want to call a vote
on trunk or what?
Given that this is in the incubator, who's votes actually count towards
doing a release? I imagine it would be the PPMC, but I'm not even sure
who is on that.
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Many thanks to Richard. That's really nice to see that there is a will to
release Droids. I created a stable branch in r1082122 and applied DROIDS-56
in r1082332. Should we revert this last commit to release from the trunk ?
On 18 March 2011 20:36, Otis Gospodnetic <og...@yahoo.com> wrote:
> Hurray for Richard!
>
>
> Otis
> ----
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> ----- Original Message ----
> > From: Richard Frovarp <rf...@apache.org>
> > To: droids-dev@incubator.apache.org
> > Sent: Fri, March 18, 2011 8:56:15 AM
> > Subject: Re: Droids 0.1 release
> >
> > On 3/18/2011 7:04 AM, Thorsten Scherler wrote:
> > > On Fri, 2011-03-18 at 11:52 +0100, Chapuis Bertil wrote:
> > >> +1
> > >>
> > >> Is there someone with sufficient rights to publish the release on the
> >maven
> > >> repository?
> > > Actually all of our committer should have enough rights. @Richard you
> > > did RM on lenya many times, but we never published to maven, or?
> > >
> > > However we may want to ask on infrastructure what the problem may be.
> > >
> > > salu2
> > >
> >
> > Right, we've never published to maven, so that would be something new.
> > I'd be willing to be the RM for this release and get things figured out.
> >
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Otis Gospodnetic <og...@yahoo.com>.
Hurray for Richard!
Otis
----
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
----- Original Message ----
> From: Richard Frovarp <rf...@apache.org>
> To: droids-dev@incubator.apache.org
> Sent: Fri, March 18, 2011 8:56:15 AM
> Subject: Re: Droids 0.1 release
>
> On 3/18/2011 7:04 AM, Thorsten Scherler wrote:
> > On Fri, 2011-03-18 at 11:52 +0100, Chapuis Bertil wrote:
> >> +1
> >>
> >> Is there someone with sufficient rights to publish the release on the
>maven
> >> repository?
> > Actually all of our committer should have enough rights. @Richard you
> > did RM on lenya many times, but we never published to maven, or?
> >
> > However we may want to ask on infrastructure what the problem may be.
> >
> > salu2
> >
>
> Right, we've never published to maven, so that would be something new.
> I'd be willing to be the RM for this release and get things figured out.
>
Re: Droids 0.1 release
Posted by Richard Frovarp <rf...@apache.org>.
On 3/18/2011 7:04 AM, Thorsten Scherler wrote:
> On Fri, 2011-03-18 at 11:52 +0100, Chapuis Bertil wrote:
>> +1
>>
>> Is there someone with sufficient rights to publish the release on the maven
>> repository?
> Actually all of our committer should have enough rights. @Richard you
> did RM on lenya many times, but we never published to maven, or?
>
> However we may want to ask on infrastructure what the problem may be.
>
> salu2
>
Right, we've never published to maven, so that would be something new.
I'd be willing to be the RM for this release and get things figured out.
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Fri, 2011-03-18 at 11:52 +0100, Chapuis Bertil wrote:
> +1
>
> Is there someone with sufficient rights to publish the release on the maven
> repository?
Actually all of our committer should have enough rights. @Richard you
did RM on lenya many times, but we never published to maven, or?
However we may want to ask on infrastructure what the problem may be.
salu2
>
>
> On 18 March 2011 11:45, Thorsten Scherler <sc...@gmail.com> wrote:
>
> > On Thu, 2011-03-10 at 22:41 +0100, Chapuis Bertil wrote:
> > > Hello,
> > >
> > > What's the current status for the release? Should we start working on
> > 0.0.2
> > > without this step? The problem I see is that by applying the small
> > patches
> > > on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I
> > tried
> > > to apply are already applied partially. So the more we wait to apply them
> > > the more work we will have.
> >
> > We need to release NOW otherwise we will never get a release done. Maybe
> > we should nominate an official RM to push the code out now.
> >
> > salu2
> >
> >
> > >
> > > Thanks for your answer,
> > >
> > > Bertil
> > >
> > > On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
> > >
> > > >
> > > >
> > > > On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> > > >
> > > >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> > > >> > I had a look at the different way available to automatically
> > generate
> > > >> the
> > > >> > team list and changes files. It seems it will be difficult to use
> > them
> > > >> with
> > > >> > our current documentation workflow. In consequence I hard coded the
> > > >> > team-list.xml and the changes.xml files in the documentation folder.
> > > >> >
> > > >> > For the project team, I took all the committers and all the
> > contributors
> > > >> who
> > > >> > provided patches.
> > > >>
> > > >> The problem with this as I see it is that this puts a too high value
> > on
> > > >> code contributions and too less on community contributions. For
> > example
> > > >> Otis who mainly contributed to the mailing list is not listed on the
> > > >> team but personally I value his contribution equally as a patch.
> > > >>
> > > >> To draw a line I think we should only list official committers as the
> > > >> TEAM.
> > > >>
> > > >> WDYT?
> > > >>
> > > >
> > > > That's ok for me. I did it without really knowing what the practices
> > are in
> > > > this area.
> > > >
> > > >
> > > >>
> > > >> > For the changes, I used the report generated by jira for 0.0.1 and
> > > >> formated
> > > >> > it in xdoc.
> > > >> > Please check if modifications or additions are required.
> > > >>
> > > >> That is fine, I see the initial changes more as pin pointing the main
> > > >> feature of droids but yours is good.
> > > >>
> > > >> >
> > > >> > I think the aim for 0.0.1 is to release as soon as possible. It
> > seems
> > > >> > several people are motivated to work on 0.0.2.
> > > >>
> > > >> Yeah, I just tried the deploy again (had to fix an issue with the
> > > >> version of the buildnumber-maven-plugin) but as well get a 401. Will
> > > >> review my config again.
> > > >>
> > > >
> > > > I just read one of the article [1] pointed by someone in the general
> > > > mailing list. The idea is to create a long lived stable branch and to
> > keep
> > > > the trunk really dynamic. It may be a really good practice for us, what
> > do
> > > > you think?
> > > >
> > > > [1] -
> > > >
> > http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> > > >
> > > >
> > > >>
> > > >> salu2
> > > >>
> > > >>
> > > >> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> > > >> wrote:
> > > >> >
> > > >> > > Hi,
> > > >> > > About the changes.xml file - is there anything to add here, seeing
> > how
> > > >> > > there
> > > >> > > is no previous release?
> > > >> > > Should the release use the apache-release maven profile
> > > >> (-Papache-release)?
> > > >> > > Is there anything I can help with?
> > > >> > > Eugen.
> > > >> > >
> > > >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> > > >> scherler@gmail.com
> > > >> > > >wrote:
> > > >> > >
> > > >> > > > Ok, will try that this afternoon, need to attend some meetings
> > now.
> > > >> > > >
> > > >> > > > salu2
> > > >> > > >
> > > >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > > >> > > > > simply mvn deploy.
> > > >> > > > >
> > > >> > > > > On 25 February 2011 10:55, Thorsten Scherler <
> > scherler@gmail.com>
> > > >> > > wrote:
> > > >> > > > >
> > > >> > > > > > What is the command you tried?
> > > >> > > > > >
> > > >> > > > > > Will try it then.
> > > >> > > > > >
> > > >> > > > > > salu2
> > > >> > > > > >
> > > >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > >> > > > > > > I tried to publish the project on the snapshot repository
> > [1].
> > > >> I
> > > >> > > get
> > > >> > > > the
> > > >> > > > > > > following error:
> > > >> > > > > > >
> > > >> > > > > > > Error deploying artifact: Authorization failed: Access
> > denied
> > > >> to:
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > >
> > > >> > >
> > > >>
> > https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > > >> > > > > > >
> > > >> > > > > > > My settings.xml contains the correct servers [2]. I tried
> > with
> > > >> > > > plain-text
> > > >> > > > > > > and encrypted passwords. The strange thing is that I am
> > able
> > > >> to
> > > >> > > login
> > > >> > > > the
> > > >> > > > > > > nexus server through the web interface. The thread [3] is
> > > >> > > describing
> > > >> > > > a
> > > >> > > > > > > similar problem. I probably simply don't have the right to
> > > >> deploy.
> > > >> > > > Could
> > > >> > > > > > > someone with sufficient rights do the release?
> > > >> > > > > > >
> > > >> > > > > > > Thanks in advance.
> > > >> > > > > > >
> > > >> > > > > > > [1] -
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > >
> > > >> > >
> > > >>
> > http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > >> > > > > > > [2] -
> > > >> http://maven.apache.org/developers/committer-settings.html
> > > >> > > > > > > [3] -
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > >
> > > >> > >
> > > >>
> > http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > > >> > > > > > >
> > > >> > > > > > >
> > > >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
> > > >> bchapuis@agimem.com>
> > > >> > > > wrote:
> > > >> > > > > > >
> > > >> > > > > > > > About the documentation file what's the convention? Do
> > we
> > > >> have to
> > > >> > > > put
> > > >> > > > > > the
> > > >> > > > > > > > apache license in their headers?
> > > >> > > > > > > >
> > > >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> > > >> rfrovarp@apache.org>
> > > >> > > > > > wrote:
> > > >> > > > > > > >
> > > >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > >> > > > > > > >>
> > > >> > > > > > > >> Make sure that all your files contain a ASF licence
> > header
> > > >> > > (look
> > > >> > > > at
> > > >> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
> > > >> > > > > > > >>> => mvn rat:check leads to a build failure with "too
> > many
> > > >> > > > unlicensed
> > > >> > > > > > > >>> files:
> > > >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a
> > look
> > > >> at
> > > >> > > > this, in
> > > >> > > > > > my
> > > >> > > > > > > >>> opinion most classes and resources contains the ASF
> > > >> license
> > > >> > > > header.
> > > >> > > > > > > >>>
> > > >> > > > > > > >>>
> > > >> > > > > > > >> There was this, where the number of correct was
> > reported
> > > >> back
> > > >> > > > instead
> > > >> > > > > > of
> > > >> > > > > > > >> the number wrong:
> > > >> > > > > > > >>
> > > >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > > >> > > > > > > >>
> > > >> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> > > >> > > > > > > >>
> > > >> > > > > > > >> At the bottom you will see the problem files. Shouldn't
> > > >> docs
> > > >> > > come
> > > >> > > > out
> > > >> > > > > > of
> > > >> > > > > > > >> this area of svn?
> > > >> > > > > > > >>
> > > >> > > > > > > >> The most troublesome of the files are these two:
> > > >> > > > > > > >>
> > > >> > > > > > > >>
> > droids-examples/src/main/java/org/apache/droids/App.java
> > > >> > > > > > > >>
> > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > >> > > > > > > >>
> > > >> > > > > > > >> They've got GPL headers on them, but on the positive
> > side
> > > >> they
> > > >> > > > don't
> > > >> > > > > > do
> > > >> > > > > > > >> anything. They have been removed in r1074224.
> > > >> > > > > > > >>
> > > >> > > > > > > >> docs/mail-lists.dispatcher.css
> > > >> > > > > > > >> docs/linkmap.html
> > > >> > > > > > > >> docs/changes.dispatcher.css
> > > >> > > > > > > >> docs/default.html
> > > >> > > > > > > >> docs/contrib.html
> > > >> > > > > > > >> docs/index.dispatcher.css
> > > >> > > > > > > >> docs/mail-lists.html
> > > >> > > > > > > >> docs/default.dispatcher.css
> > > >> > > > > > > >> docs/contrib.dispatcher.css
> > > >> > > > > > > >> docs/themes/droids.css
> > > >> > > > > > > >> docs/api/droids-norobots/package-list
> > > >> > > > > > > >> docs/api/droids-wicket/package-list
> > > >> > > > > > > >> docs/api/droids-tika/package-list
> > > >> > > > > > > >> docs/api/droids-solr/package-list
> > > >> > > > > > > >> docs/api/droids-core/package-list
> > > >> > > > > > > >> docs/api/droids-spring/package-list
> > > >> > > > > > > >> docs/develope.html
> > > >> > > > > > > >> docs/changes.rss
> > > >> > > > > > > >> docs/develope.dispatcher.css
> > > >> > > > > > > >> docs/changes.html
> > > >> > > > > > > >> docs/todo.html
> > > >> > > > > > > >> docs/todo.dispatcher.css
> > > >> > > > > > > >> docs/index.html
> > > >> > > > > > > >> docs/linkmap.dispatcher.css
> > > >> > > > > > > >> docs/develop/develop.dispatcher.css
> > > >> > > > > > > >> docs/develop/hello-crawler.html
> > > >> > > > > > > >> docs/develop/develop.html
> > > >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> > > >> > > > > > > >> docs/install.html
> > > >> > > > > > > >> docs/install.dispatcher.css
> > > >> > > > > > > >> droids-examples/pom.xml
> > > >> > > > > > > >>
> > droids-examples/src/main/java/org/apache/droids/App.java
> > > >> > > > > > > >> droids-examples/src/site/apt/index.apt
> > > >> > > > > > > >> droids-examples/src/site/site.xml
> > > >> > > > > > > >> droids-examples/src/site/fml/faq.fml
> > > >> > > > > > > >>
> > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > >> > > > > > > >> testing.properties
> > > >> > > > > > > >> doap.rdf
> > > >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > >> > > > > > > >> src/templates/component/DROIDS-README.txt
> > > >> > > > > > > >>
> > src/documentation/content/xdocs/images/droidsOverview.svg
> > > >> > > > > > > >>
> > src/documentation/resources/themes/common/css/droids.css
> > > >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> > > >> > > > > > > >>
> > > >> > > > > > > >
> > > >> > > > > > > >
> > > >> > > > > > > >
> > > >> > > > > > > > --
> > > >> > > > > > > > Bertil Chapuis
> > > >> > > > > > > > Agimem Sàrl
> > > >> > > > > > > > http://www.agimem.com
> > > >> > > > > > > >
> > > >> > > > > > > >
> > > >> > > > > > >
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > > > --
> > > >> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> > > >> > > > > > codeBusters S.L. - web based systems
> > > >> > > > > > <consulting, training and solutions>
> > > >> > > > > > http://www.codebusters.es/
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > Thorsten Scherler <thorsten.at.apache.org>
> > > >> > > > codeBusters S.L. - web based systems
> > > >> > > > <consulting, training and solutions>
> > > >> > > > http://www.codebusters.es/
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Thorsten Scherler <thorsten.at.apache.org>
> > > >> codeBusters S.L. - web based systems
> > > >> <consulting, training and solutions>
> > > >> http://www.codebusters.es/
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Bertil Chapuis
> > > > Agimem Sàrl
> > > > http://www.agimem.com
> > > >
> > > >
> > >
> > >
> >
> > --
> > Thorsten Scherler <thorsten.at.apache.org>
> > codeBusters S.L. - web based systems
> > <consulting, training and solutions>
> > http://www.codebusters.es/
> >
> >
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
+1
Is there someone with sufficient rights to publish the release on the maven
repository?
On 18 March 2011 11:45, Thorsten Scherler <sc...@gmail.com> wrote:
> On Thu, 2011-03-10 at 22:41 +0100, Chapuis Bertil wrote:
> > Hello,
> >
> > What's the current status for the release? Should we start working on
> 0.0.2
> > without this step? The problem I see is that by applying the small
> patches
> > on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I
> tried
> > to apply are already applied partially. So the more we wait to apply them
> > the more work we will have.
>
> We need to release NOW otherwise we will never get a release done. Maybe
> we should nominate an official RM to push the code out now.
>
> salu2
>
>
> >
> > Thanks for your answer,
> >
> > Bertil
> >
> > On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
> >
> > >
> > >
> > > On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> > >
> > >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> > >> > I had a look at the different way available to automatically
> generate
> > >> the
> > >> > team list and changes files. It seems it will be difficult to use
> them
> > >> with
> > >> > our current documentation workflow. In consequence I hard coded the
> > >> > team-list.xml and the changes.xml files in the documentation folder.
> > >> >
> > >> > For the project team, I took all the committers and all the
> contributors
> > >> who
> > >> > provided patches.
> > >>
> > >> The problem with this as I see it is that this puts a too high value
> on
> > >> code contributions and too less on community contributions. For
> example
> > >> Otis who mainly contributed to the mailing list is not listed on the
> > >> team but personally I value his contribution equally as a patch.
> > >>
> > >> To draw a line I think we should only list official committers as the
> > >> TEAM.
> > >>
> > >> WDYT?
> > >>
> > >
> > > That's ok for me. I did it without really knowing what the practices
> are in
> > > this area.
> > >
> > >
> > >>
> > >> > For the changes, I used the report generated by jira for 0.0.1 and
> > >> formated
> > >> > it in xdoc.
> > >> > Please check if modifications or additions are required.
> > >>
> > >> That is fine, I see the initial changes more as pin pointing the main
> > >> feature of droids but yours is good.
> > >>
> > >> >
> > >> > I think the aim for 0.0.1 is to release as soon as possible. It
> seems
> > >> > several people are motivated to work on 0.0.2.
> > >>
> > >> Yeah, I just tried the deploy again (had to fix an issue with the
> > >> version of the buildnumber-maven-plugin) but as well get a 401. Will
> > >> review my config again.
> > >>
> > >
> > > I just read one of the article [1] pointed by someone in the general
> > > mailing list. The idea is to create a long lived stable branch and to
> keep
> > > the trunk really dynamic. It may be a really good practice for us, what
> do
> > > you think?
> > >
> > > [1] -
> > >
> http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> > >
> > >
> > >>
> > >> salu2
> > >>
> > >>
> > >> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> > >> wrote:
> > >> >
> > >> > > Hi,
> > >> > > About the changes.xml file - is there anything to add here, seeing
> how
> > >> > > there
> > >> > > is no previous release?
> > >> > > Should the release use the apache-release maven profile
> > >> (-Papache-release)?
> > >> > > Is there anything I can help with?
> > >> > > Eugen.
> > >> > >
> > >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> > >> scherler@gmail.com
> > >> > > >wrote:
> > >> > >
> > >> > > > Ok, will try that this afternoon, need to attend some meetings
> now.
> > >> > > >
> > >> > > > salu2
> > >> > > >
> > >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > >> > > > > simply mvn deploy.
> > >> > > > >
> > >> > > > > On 25 February 2011 10:55, Thorsten Scherler <
> scherler@gmail.com>
> > >> > > wrote:
> > >> > > > >
> > >> > > > > > What is the command you tried?
> > >> > > > > >
> > >> > > > > > Will try it then.
> > >> > > > > >
> > >> > > > > > salu2
> > >> > > > > >
> > >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > >> > > > > > > I tried to publish the project on the snapshot repository
> [1].
> > >> I
> > >> > > get
> > >> > > > the
> > >> > > > > > > following error:
> > >> > > > > > >
> > >> > > > > > > Error deploying artifact: Authorization failed: Access
> denied
> > >> to:
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > >> > > > > > >
> > >> > > > > > > My settings.xml contains the correct servers [2]. I tried
> with
> > >> > > > plain-text
> > >> > > > > > > and encrypted passwords. The strange thing is that I am
> able
> > >> to
> > >> > > login
> > >> > > > the
> > >> > > > > > > nexus server through the web interface. The thread [3] is
> > >> > > describing
> > >> > > > a
> > >> > > > > > > similar problem. I probably simply don't have the right to
> > >> deploy.
> > >> > > > Could
> > >> > > > > > > someone with sufficient rights do the release?
> > >> > > > > > >
> > >> > > > > > > Thanks in advance.
> > >> > > > > > >
> > >> > > > > > > [1] -
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > >> > > > > > > [2] -
> > >> http://maven.apache.org/developers/committer-settings.html
> > >> > > > > > > [3] -
> > >> > > > > > >
> > >> > > > > >
> > >> > > >
> > >> > >
> > >>
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
> > >> bchapuis@agimem.com>
> > >> > > > wrote:
> > >> > > > > > >
> > >> > > > > > > > About the documentation file what's the convention? Do
> we
> > >> have to
> > >> > > > put
> > >> > > > > > the
> > >> > > > > > > > apache license in their headers?
> > >> > > > > > > >
> > >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> > >> rfrovarp@apache.org>
> > >> > > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > >> > > > > > > >>
> > >> > > > > > > >> Make sure that all your files contain a ASF licence
> header
> > >> > > (look
> > >> > > > at
> > >> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
> > >> > > > > > > >>> => mvn rat:check leads to a build failure with "too
> many
> > >> > > > unlicensed
> > >> > > > > > > >>> files:
> > >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a
> look
> > >> at
> > >> > > > this, in
> > >> > > > > > my
> > >> > > > > > > >>> opinion most classes and resources contains the ASF
> > >> license
> > >> > > > header.
> > >> > > > > > > >>>
> > >> > > > > > > >>>
> > >> > > > > > > >> There was this, where the number of correct was
> reported
> > >> back
> > >> > > > instead
> > >> > > > > > of
> > >> > > > > > > >> the number wrong:
> > >> > > > > > > >>
> > >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > >> > > > > > > >>
> > >> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> > >> > > > > > > >>
> > >> > > > > > > >> At the bottom you will see the problem files. Shouldn't
> > >> docs
> > >> > > come
> > >> > > > out
> > >> > > > > > of
> > >> > > > > > > >> this area of svn?
> > >> > > > > > > >>
> > >> > > > > > > >> The most troublesome of the files are these two:
> > >> > > > > > > >>
> > >> > > > > > > >>
> droids-examples/src/main/java/org/apache/droids/App.java
> > >> > > > > > > >>
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >> > > > > > > >>
> > >> > > > > > > >> They've got GPL headers on them, but on the positive
> side
> > >> they
> > >> > > > don't
> > >> > > > > > do
> > >> > > > > > > >> anything. They have been removed in r1074224.
> > >> > > > > > > >>
> > >> > > > > > > >> docs/mail-lists.dispatcher.css
> > >> > > > > > > >> docs/linkmap.html
> > >> > > > > > > >> docs/changes.dispatcher.css
> > >> > > > > > > >> docs/default.html
> > >> > > > > > > >> docs/contrib.html
> > >> > > > > > > >> docs/index.dispatcher.css
> > >> > > > > > > >> docs/mail-lists.html
> > >> > > > > > > >> docs/default.dispatcher.css
> > >> > > > > > > >> docs/contrib.dispatcher.css
> > >> > > > > > > >> docs/themes/droids.css
> > >> > > > > > > >> docs/api/droids-norobots/package-list
> > >> > > > > > > >> docs/api/droids-wicket/package-list
> > >> > > > > > > >> docs/api/droids-tika/package-list
> > >> > > > > > > >> docs/api/droids-solr/package-list
> > >> > > > > > > >> docs/api/droids-core/package-list
> > >> > > > > > > >> docs/api/droids-spring/package-list
> > >> > > > > > > >> docs/develope.html
> > >> > > > > > > >> docs/changes.rss
> > >> > > > > > > >> docs/develope.dispatcher.css
> > >> > > > > > > >> docs/changes.html
> > >> > > > > > > >> docs/todo.html
> > >> > > > > > > >> docs/todo.dispatcher.css
> > >> > > > > > > >> docs/index.html
> > >> > > > > > > >> docs/linkmap.dispatcher.css
> > >> > > > > > > >> docs/develop/develop.dispatcher.css
> > >> > > > > > > >> docs/develop/hello-crawler.html
> > >> > > > > > > >> docs/develop/develop.html
> > >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> > >> > > > > > > >> docs/install.html
> > >> > > > > > > >> docs/install.dispatcher.css
> > >> > > > > > > >> droids-examples/pom.xml
> > >> > > > > > > >>
> droids-examples/src/main/java/org/apache/droids/App.java
> > >> > > > > > > >> droids-examples/src/site/apt/index.apt
> > >> > > > > > > >> droids-examples/src/site/site.xml
> > >> > > > > > > >> droids-examples/src/site/fml/faq.fml
> > >> > > > > > > >>
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >> > > > > > > >> testing.properties
> > >> > > > > > > >> doap.rdf
> > >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > >> > > > > > > >> src/templates/component/DROIDS-README.txt
> > >> > > > > > > >>
> src/documentation/content/xdocs/images/droidsOverview.svg
> > >> > > > > > > >>
> src/documentation/resources/themes/common/css/droids.css
> > >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> > >> > > > > > > >>
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > --
> > >> > > > > > > > Bertil Chapuis
> > >> > > > > > > > Agimem Sàrl
> > >> > > > > > > > http://www.agimem.com
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> > >> > > > > > codeBusters S.L. - web based systems
> > >> > > > > > <consulting, training and solutions>
> > >> > > > > > http://www.codebusters.es/
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > > --
> > >> > > > Thorsten Scherler <thorsten.at.apache.org>
> > >> > > > codeBusters S.L. - web based systems
> > >> > > > <consulting, training and solutions>
> > >> > > > http://www.codebusters.es/
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >> >
> > >> >
> > >>
> > >> --
> > >> Thorsten Scherler <thorsten.at.apache.org>
> > >> codeBusters S.L. - web based systems
> > >> <consulting, training and solutions>
> > >> http://www.codebusters.es/
> > >>
> > >>
> > >
> > >
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> > >
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Thu, 2011-03-10 at 22:41 +0100, Chapuis Bertil wrote:
> Hello,
>
> What's the current status for the release? Should we start working on 0.0.2
> without this step? The problem I see is that by applying the small patches
> on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I tried
> to apply are already applied partially. So the more we wait to apply them
> the more work we will have.
We need to release NOW otherwise we will never get a release done. Maybe
we should nominate an official RM to push the code out now.
salu2
>
> Thanks for your answer,
>
> Bertil
>
> On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
>
> >
> >
> > On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> >
> >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> >> > I had a look at the different way available to automatically generate
> >> the
> >> > team list and changes files. It seems it will be difficult to use them
> >> with
> >> > our current documentation workflow. In consequence I hard coded the
> >> > team-list.xml and the changes.xml files in the documentation folder.
> >> >
> >> > For the project team, I took all the committers and all the contributors
> >> who
> >> > provided patches.
> >>
> >> The problem with this as I see it is that this puts a too high value on
> >> code contributions and too less on community contributions. For example
> >> Otis who mainly contributed to the mailing list is not listed on the
> >> team but personally I value his contribution equally as a patch.
> >>
> >> To draw a line I think we should only list official committers as the
> >> TEAM.
> >>
> >> WDYT?
> >>
> >
> > That's ok for me. I did it without really knowing what the practices are in
> > this area.
> >
> >
> >>
> >> > For the changes, I used the report generated by jira for 0.0.1 and
> >> formated
> >> > it in xdoc.
> >> > Please check if modifications or additions are required.
> >>
> >> That is fine, I see the initial changes more as pin pointing the main
> >> feature of droids but yours is good.
> >>
> >> >
> >> > I think the aim for 0.0.1 is to release as soon as possible. It seems
> >> > several people are motivated to work on 0.0.2.
> >>
> >> Yeah, I just tried the deploy again (had to fix an issue with the
> >> version of the buildnumber-maven-plugin) but as well get a 401. Will
> >> review my config again.
> >>
> >
> > I just read one of the article [1] pointed by someone in the general
> > mailing list. The idea is to create a long lived stable branch and to keep
> > the trunk really dynamic. It may be a really good practice for us, what do
> > you think?
> >
> > [1] -
> > http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
> >
> >
> >>
> >> salu2
> >>
> >>
> >> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> >> wrote:
> >> >
> >> > > Hi,
> >> > > About the changes.xml file - is there anything to add here, seeing how
> >> > > there
> >> > > is no previous release?
> >> > > Should the release use the apache-release maven profile
> >> (-Papache-release)?
> >> > > Is there anything I can help with?
> >> > > Eugen.
> >> > >
> >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> >> scherler@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > Ok, will try that this afternoon, need to attend some meetings now.
> >> > > >
> >> > > > salu2
> >> > > >
> >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> >> > > > > simply mvn deploy.
> >> > > > >
> >> > > > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
> >> > > wrote:
> >> > > > >
> >> > > > > > What is the command you tried?
> >> > > > > >
> >> > > > > > Will try it then.
> >> > > > > >
> >> > > > > > salu2
> >> > > > > >
> >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> >> > > > > > > I tried to publish the project on the snapshot repository [1].
> >> I
> >> > > get
> >> > > > the
> >> > > > > > > following error:
> >> > > > > > >
> >> > > > > > > Error deploying artifact: Authorization failed: Access denied
> >> to:
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> >> > > > > > >
> >> > > > > > > My settings.xml contains the correct servers [2]. I tried with
> >> > > > plain-text
> >> > > > > > > and encrypted passwords. The strange thing is that I am able
> >> to
> >> > > login
> >> > > > the
> >> > > > > > > nexus server through the web interface. The thread [3] is
> >> > > describing
> >> > > > a
> >> > > > > > > similar problem. I probably simply don't have the right to
> >> deploy.
> >> > > > Could
> >> > > > > > > someone with sufficient rights do the release?
> >> > > > > > >
> >> > > > > > > Thanks in advance.
> >> > > > > > >
> >> > > > > > > [1] -
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> >> > > > > > > [2] -
> >> http://maven.apache.org/developers/committer-settings.html
> >> > > > > > > [3] -
> >> > > > > > >
> >> > > > > >
> >> > > >
> >> > >
> >> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
> >> bchapuis@agimem.com>
> >> > > > wrote:
> >> > > > > > >
> >> > > > > > > > About the documentation file what's the convention? Do we
> >> have to
> >> > > > put
> >> > > > > > the
> >> > > > > > > > apache license in their headers?
> >> > > > > > > >
> >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> >> rfrovarp@apache.org>
> >> > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> >> > > > > > > >>
> >> > > > > > > >> Make sure that all your files contain a ASF licence header
> >> > > (look
> >> > > > at
> >> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
> >> > > > > > > >>> => mvn rat:check leads to a build failure with "too many
> >> > > > unlicensed
> >> > > > > > > >>> files:
> >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a look
> >> at
> >> > > > this, in
> >> > > > > > my
> >> > > > > > > >>> opinion most classes and resources contains the ASF
> >> license
> >> > > > header.
> >> > > > > > > >>>
> >> > > > > > > >>>
> >> > > > > > > >> There was this, where the number of correct was reported
> >> back
> >> > > > instead
> >> > > > > > of
> >> > > > > > > >> the number wrong:
> >> > > > > > > >>
> >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> >> > > > > > > >>
> >> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> >> > > > > > > >>
> >> > > > > > > >> At the bottom you will see the problem files. Shouldn't
> >> docs
> >> > > come
> >> > > > out
> >> > > > > > of
> >> > > > > > > >> this area of svn?
> >> > > > > > > >>
> >> > > > > > > >> The most troublesome of the files are these two:
> >> > > > > > > >>
> >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> >> > > > > > > >>
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >> > > > > > > >>
> >> > > > > > > >> They've got GPL headers on them, but on the positive side
> >> they
> >> > > > don't
> >> > > > > > do
> >> > > > > > > >> anything. They have been removed in r1074224.
> >> > > > > > > >>
> >> > > > > > > >> docs/mail-lists.dispatcher.css
> >> > > > > > > >> docs/linkmap.html
> >> > > > > > > >> docs/changes.dispatcher.css
> >> > > > > > > >> docs/default.html
> >> > > > > > > >> docs/contrib.html
> >> > > > > > > >> docs/index.dispatcher.css
> >> > > > > > > >> docs/mail-lists.html
> >> > > > > > > >> docs/default.dispatcher.css
> >> > > > > > > >> docs/contrib.dispatcher.css
> >> > > > > > > >> docs/themes/droids.css
> >> > > > > > > >> docs/api/droids-norobots/package-list
> >> > > > > > > >> docs/api/droids-wicket/package-list
> >> > > > > > > >> docs/api/droids-tika/package-list
> >> > > > > > > >> docs/api/droids-solr/package-list
> >> > > > > > > >> docs/api/droids-core/package-list
> >> > > > > > > >> docs/api/droids-spring/package-list
> >> > > > > > > >> docs/develope.html
> >> > > > > > > >> docs/changes.rss
> >> > > > > > > >> docs/develope.dispatcher.css
> >> > > > > > > >> docs/changes.html
> >> > > > > > > >> docs/todo.html
> >> > > > > > > >> docs/todo.dispatcher.css
> >> > > > > > > >> docs/index.html
> >> > > > > > > >> docs/linkmap.dispatcher.css
> >> > > > > > > >> docs/develop/develop.dispatcher.css
> >> > > > > > > >> docs/develop/hello-crawler.html
> >> > > > > > > >> docs/develop/develop.html
> >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> >> > > > > > > >> docs/install.html
> >> > > > > > > >> docs/install.dispatcher.css
> >> > > > > > > >> droids-examples/pom.xml
> >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> >> > > > > > > >> droids-examples/src/site/apt/index.apt
> >> > > > > > > >> droids-examples/src/site/site.xml
> >> > > > > > > >> droids-examples/src/site/fml/faq.fml
> >> > > > > > > >>
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >> > > > > > > >> testing.properties
> >> > > > > > > >> doap.rdf
> >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> >> > > > > > > >> src/templates/component/DROIDS-README.txt
> >> > > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> >> > > > > > > >> src/documentation/resources/themes/common/css/droids.css
> >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> >> > > > > > > >>
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > --
> >> > > > > > > > Bertil Chapuis
> >> > > > > > > > Agimem Sàrl
> >> > > > > > > > http://www.agimem.com
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> >> > > > > > codeBusters S.L. - web based systems
> >> > > > > > <consulting, training and solutions>
> >> > > > > > http://www.codebusters.es/
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > > --
> >> > > > Thorsten Scherler <thorsten.at.apache.org>
> >> > > > codeBusters S.L. - web based systems
> >> > > > <consulting, training and solutions>
> >> > > > http://www.codebusters.es/
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >>
> >> --
> >> Thorsten Scherler <thorsten.at.apache.org>
> >> codeBusters S.L. - web based systems
> >> <consulting, training and solutions>
> >> http://www.codebusters.es/
> >>
> >>
> >
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
> >
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Hello,
What's the current status for the release? Should we start working on 0.0.2
without this step? The problem I see is that by applying the small patches
on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I tried
to apply are already applied partially. So the more we wait to apply them
the more work we will have.
Thanks for your answer,
Bertil
On 1 March 2011 18:31, Chapuis Bertil <bc...@agimem.com> wrote:
>
>
> On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
>
>> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
>> > I had a look at the different way available to automatically generate
>> the
>> > team list and changes files. It seems it will be difficult to use them
>> with
>> > our current documentation workflow. In consequence I hard coded the
>> > team-list.xml and the changes.xml files in the documentation folder.
>> >
>> > For the project team, I took all the committers and all the contributors
>> who
>> > provided patches.
>>
>> The problem with this as I see it is that this puts a too high value on
>> code contributions and too less on community contributions. For example
>> Otis who mainly contributed to the mailing list is not listed on the
>> team but personally I value his contribution equally as a patch.
>>
>> To draw a line I think we should only list official committers as the
>> TEAM.
>>
>> WDYT?
>>
>
> That's ok for me. I did it without really knowing what the practices are in
> this area.
>
>
>>
>> > For the changes, I used the report generated by jira for 0.0.1 and
>> formated
>> > it in xdoc.
>> > Please check if modifications or additions are required.
>>
>> That is fine, I see the initial changes more as pin pointing the main
>> feature of droids but yours is good.
>>
>> >
>> > I think the aim for 0.0.1 is to release as soon as possible. It seems
>> > several people are motivated to work on 0.0.2.
>>
>> Yeah, I just tried the deploy again (had to fix an issue with the
>> version of the buildnumber-maven-plugin) but as well get a 401. Will
>> review my config again.
>>
>
> I just read one of the article [1] pointed by someone in the general
> mailing list. The idea is to create a long lived stable branch and to keep
> the trunk really dynamic. It may be a really good practice for us, what do
> you think?
>
> [1] -
> http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
>
>
>>
>> salu2
>>
>>
>> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
>> wrote:
>> >
>> > > Hi,
>> > > About the changes.xml file - is there anything to add here, seeing how
>> > > there
>> > > is no previous release?
>> > > Should the release use the apache-release maven profile
>> (-Papache-release)?
>> > > Is there anything I can help with?
>> > > Eugen.
>> > >
>> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
>> scherler@gmail.com
>> > > >wrote:
>> > >
>> > > > Ok, will try that this afternoon, need to attend some meetings now.
>> > > >
>> > > > salu2
>> > > >
>> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
>> > > > > simply mvn deploy.
>> > > > >
>> > > > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > > What is the command you tried?
>> > > > > >
>> > > > > > Will try it then.
>> > > > > >
>> > > > > > salu2
>> > > > > >
>> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
>> > > > > > > I tried to publish the project on the snapshot repository [1].
>> I
>> > > get
>> > > > the
>> > > > > > > following error:
>> > > > > > >
>> > > > > > > Error deploying artifact: Authorization failed: Access denied
>> to:
>> > > > > > >
>> > > > > >
>> > > >
>> > >
>> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
>> > > > > > >
>> > > > > > > My settings.xml contains the correct servers [2]. I tried with
>> > > > plain-text
>> > > > > > > and encrypted passwords. The strange thing is that I am able
>> to
>> > > login
>> > > > the
>> > > > > > > nexus server through the web interface. The thread [3] is
>> > > describing
>> > > > a
>> > > > > > > similar problem. I probably simply don't have the right to
>> deploy.
>> > > > Could
>> > > > > > > someone with sufficient rights do the release?
>> > > > > > >
>> > > > > > > Thanks in advance.
>> > > > > > >
>> > > > > > > [1] -
>> > > > > > >
>> > > > > >
>> > > >
>> > >
>> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
>> > > > > > > [2] -
>> http://maven.apache.org/developers/committer-settings.html
>> > > > > > > [3] -
>> > > > > > >
>> > > > > >
>> > > >
>> > >
>> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
>> > > > > > >
>> > > > > > >
>> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <
>> bchapuis@agimem.com>
>> > > > wrote:
>> > > > > > >
>> > > > > > > > About the documentation file what's the convention? Do we
>> have to
>> > > > put
>> > > > > > the
>> > > > > > > > apache license in their headers?
>> > > > > > > >
>> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
>> rfrovarp@apache.org>
>> > > > > > wrote:
>> > > > > > > >
>> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>> > > > > > > >>
>> > > > > > > >> Make sure that all your files contain a ASF licence header
>> > > (look
>> > > > at
>> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
>> > > > > > > >>> => mvn rat:check leads to a build failure with "too many
>> > > > unlicensed
>> > > > > > > >>> files:
>> > > > > > > >>> 199", looks quite strange. I'd love if someone had a look
>> at
>> > > > this, in
>> > > > > > my
>> > > > > > > >>> opinion most classes and resources contains the ASF
>> license
>> > > > header.
>> > > > > > > >>>
>> > > > > > > >>>
>> > > > > > > >> There was this, where the number of correct was reported
>> back
>> > > > instead
>> > > > > > of
>> > > > > > > >> the number wrong:
>> > > > > > > >>
>> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
>> > > > > > > >>
>> > > > > > > >> I don't know if it was fixed in 0.7 or not.
>> > > > > > > >>
>> > > > > > > >> At the bottom you will see the problem files. Shouldn't
>> docs
>> > > come
>> > > > out
>> > > > > > of
>> > > > > > > >> this area of svn?
>> > > > > > > >>
>> > > > > > > >> The most troublesome of the files are these two:
>> > > > > > > >>
>> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
>> > > > > > > >>
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> > > > > > > >>
>> > > > > > > >> They've got GPL headers on them, but on the positive side
>> they
>> > > > don't
>> > > > > > do
>> > > > > > > >> anything. They have been removed in r1074224.
>> > > > > > > >>
>> > > > > > > >> docs/mail-lists.dispatcher.css
>> > > > > > > >> docs/linkmap.html
>> > > > > > > >> docs/changes.dispatcher.css
>> > > > > > > >> docs/default.html
>> > > > > > > >> docs/contrib.html
>> > > > > > > >> docs/index.dispatcher.css
>> > > > > > > >> docs/mail-lists.html
>> > > > > > > >> docs/default.dispatcher.css
>> > > > > > > >> docs/contrib.dispatcher.css
>> > > > > > > >> docs/themes/droids.css
>> > > > > > > >> docs/api/droids-norobots/package-list
>> > > > > > > >> docs/api/droids-wicket/package-list
>> > > > > > > >> docs/api/droids-tika/package-list
>> > > > > > > >> docs/api/droids-solr/package-list
>> > > > > > > >> docs/api/droids-core/package-list
>> > > > > > > >> docs/api/droids-spring/package-list
>> > > > > > > >> docs/develope.html
>> > > > > > > >> docs/changes.rss
>> > > > > > > >> docs/develope.dispatcher.css
>> > > > > > > >> docs/changes.html
>> > > > > > > >> docs/todo.html
>> > > > > > > >> docs/todo.dispatcher.css
>> > > > > > > >> docs/index.html
>> > > > > > > >> docs/linkmap.dispatcher.css
>> > > > > > > >> docs/develop/develop.dispatcher.css
>> > > > > > > >> docs/develop/hello-crawler.html
>> > > > > > > >> docs/develop/develop.html
>> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
>> > > > > > > >> docs/install.html
>> > > > > > > >> docs/install.dispatcher.css
>> > > > > > > >> droids-examples/pom.xml
>> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
>> > > > > > > >> droids-examples/src/site/apt/index.apt
>> > > > > > > >> droids-examples/src/site/site.xml
>> > > > > > > >> droids-examples/src/site/fml/faq.fml
>> > > > > > > >>
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> > > > > > > >> testing.properties
>> > > > > > > >> doap.rdf
>> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
>> > > > > > > >> src/templates/component/DROIDS-README.txt
>> > > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
>> > > > > > > >> src/documentation/resources/themes/common/css/droids.css
>> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
>> > > > > > > >>
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Bertil Chapuis
>> > > > > > > > Agimem Sàrl
>> > > > > > > > http://www.agimem.com
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Thorsten Scherler <thorsten.at.apache.org>
>> > > > > > codeBusters S.L. - web based systems
>> > > > > > <consulting, training and solutions>
>> > > > > > http://www.codebusters.es/
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Thorsten Scherler <thorsten.at.apache.org>
>> > > > codeBusters S.L. - web based systems
>> > > > <consulting, training and solutions>
>> > > > http://www.codebusters.es/
>> > > >
>> > > >
>> > >
>> >
>> >
>> >
>>
>> --
>> Thorsten Scherler <thorsten.at.apache.org>
>> codeBusters S.L. - web based systems
>> <consulting, training and solutions>
>> http://www.codebusters.es/
>>
>>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
On 1 March 2011 15:14, Thorsten Scherler <sc...@gmail.com> wrote:
> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> > I had a look at the different way available to automatically generate the
> > team list and changes files. It seems it will be difficult to use them
> with
> > our current documentation workflow. In consequence I hard coded the
> > team-list.xml and the changes.xml files in the documentation folder.
> >
> > For the project team, I took all the committers and all the contributors
> who
> > provided patches.
>
> The problem with this as I see it is that this puts a too high value on
> code contributions and too less on community contributions. For example
> Otis who mainly contributed to the mailing list is not listed on the
> team but personally I value his contribution equally as a patch.
>
> To draw a line I think we should only list official committers as the
> TEAM.
>
> WDYT?
>
That's ok for me. I did it without really knowing what the practices are in
this area.
>
> > For the changes, I used the report generated by jira for 0.0.1 and
> formated
> > it in xdoc.
> > Please check if modifications or additions are required.
>
> That is fine, I see the initial changes more as pin pointing the main
> feature of droids but yours is good.
>
> >
> > I think the aim for 0.0.1 is to release as soon as possible. It seems
> > several people are motivated to work on 0.0.2.
>
> Yeah, I just tried the deploy again (had to fix an issue with the
> version of the buildnumber-maven-plugin) but as well get a 401. Will
> review my config again.
>
I just read one of the article [1] pointed by someone in the general mailing
list. The idea is to create a long lived stable branch and to keep the trunk
really dynamic. It may be a really good practice for us, what do you think?
[1] -
http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
>
> salu2
>
>
> > On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com>
> wrote:
> >
> > > Hi,
> > > About the changes.xml file - is there anything to add here, seeing how
> > > there
> > > is no previous release?
> > > Should the release use the apache-release maven profile
> (-Papache-release)?
> > > Is there anything I can help with?
> > > Eugen.
> > >
> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <
> scherler@gmail.com
> > > >wrote:
> > >
> > > > Ok, will try that this afternoon, need to attend some meetings now.
> > > >
> > > > salu2
> > > >
> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > > > > simply mvn deploy.
> > > > >
> > > > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
> > > wrote:
> > > > >
> > > > > > What is the command you tried?
> > > > > >
> > > > > > Will try it then.
> > > > > >
> > > > > > salu2
> > > > > >
> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > > > > > I tried to publish the project on the snapshot repository [1].
> I
> > > get
> > > > the
> > > > > > > following error:
> > > > > > >
> > > > > > > Error deploying artifact: Authorization failed: Access denied
> to:
> > > > > > >
> > > > > >
> > > >
> > >
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > > > > > >
> > > > > > > My settings.xml contains the correct servers [2]. I tried with
> > > > plain-text
> > > > > > > and encrypted passwords. The strange thing is that I am able to
> > > login
> > > > the
> > > > > > > nexus server through the web interface. The thread [3] is
> > > describing
> > > > a
> > > > > > > similar problem. I probably simply don't have the right to
> deploy.
> > > > Could
> > > > > > > someone with sufficient rights do the release?
> > > > > > >
> > > > > > > Thanks in advance.
> > > > > > >
> > > > > > > [1] -
> > > > > > >
> > > > > >
> > > >
> > >
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > > > > > [2] -
> http://maven.apache.org/developers/committer-settings.html
> > > > > > > [3] -
> > > > > > >
> > > > > >
> > > >
> > >
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > > > > > >
> > > > > > >
> > > > > > > On 25 February 2011 09:13, Chapuis Bertil <bchapuis@agimem.com
> >
> > > > wrote:
> > > > > > >
> > > > > > > > About the documentation file what's the convention? Do we
> have to
> > > > put
> > > > > > the
> > > > > > > > apache license in their headers?
> > > > > > > >
> > > > > > > > On 24 February 2011 18:27, Richard Frovarp <
> rfrovarp@apache.org>
> > > > > > wrote:
> > > > > > > >
> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > > > > > >>
> > > > > > > >> Make sure that all your files contain a ASF licence header
> > > (look
> > > > at
> > > > > > > >>> the RAT report when in doubt, generated with mvn site)
> > > > > > > >>> => mvn rat:check leads to a build failure with "too many
> > > > unlicensed
> > > > > > > >>> files:
> > > > > > > >>> 199", looks quite strange. I'd love if someone had a look
> at
> > > > this, in
> > > > > > my
> > > > > > > >>> opinion most classes and resources contains the ASF license
> > > > header.
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >> There was this, where the number of correct was reported
> back
> > > > instead
> > > > > > of
> > > > > > > >> the number wrong:
> > > > > > > >>
> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > > > > > > >>
> > > > > > > >> I don't know if it was fixed in 0.7 or not.
> > > > > > > >>
> > > > > > > >> At the bottom you will see the problem files. Shouldn't docs
> > > come
> > > > out
> > > > > > of
> > > > > > > >> this area of svn?
> > > > > > > >>
> > > > > > > >> The most troublesome of the files are these two:
> > > > > > > >>
> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > > > >>
> > > > > > > >> They've got GPL headers on them, but on the positive side
> they
> > > > don't
> > > > > > do
> > > > > > > >> anything. They have been removed in r1074224.
> > > > > > > >>
> > > > > > > >> docs/mail-lists.dispatcher.css
> > > > > > > >> docs/linkmap.html
> > > > > > > >> docs/changes.dispatcher.css
> > > > > > > >> docs/default.html
> > > > > > > >> docs/contrib.html
> > > > > > > >> docs/index.dispatcher.css
> > > > > > > >> docs/mail-lists.html
> > > > > > > >> docs/default.dispatcher.css
> > > > > > > >> docs/contrib.dispatcher.css
> > > > > > > >> docs/themes/droids.css
> > > > > > > >> docs/api/droids-norobots/package-list
> > > > > > > >> docs/api/droids-wicket/package-list
> > > > > > > >> docs/api/droids-tika/package-list
> > > > > > > >> docs/api/droids-solr/package-list
> > > > > > > >> docs/api/droids-core/package-list
> > > > > > > >> docs/api/droids-spring/package-list
> > > > > > > >> docs/develope.html
> > > > > > > >> docs/changes.rss
> > > > > > > >> docs/develope.dispatcher.css
> > > > > > > >> docs/changes.html
> > > > > > > >> docs/todo.html
> > > > > > > >> docs/todo.dispatcher.css
> > > > > > > >> docs/index.html
> > > > > > > >> docs/linkmap.dispatcher.css
> > > > > > > >> docs/develop/develop.dispatcher.css
> > > > > > > >> docs/develop/hello-crawler.html
> > > > > > > >> docs/develop/develop.html
> > > > > > > >> docs/develop/hello-crawler.dispatcher.css
> > > > > > > >> docs/install.html
> > > > > > > >> docs/install.dispatcher.css
> > > > > > > >> droids-examples/pom.xml
> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > > > >> droids-examples/src/site/apt/index.apt
> > > > > > > >> droids-examples/src/site/site.xml
> > > > > > > >> droids-examples/src/site/fml/faq.fml
> > > > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > > > >> testing.properties
> > > > > > > >> doap.rdf
> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > > > > > >> src/templates/component/DROIDS-README.txt
> > > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > > > > > > >> src/documentation/resources/themes/common/css/droids.css
> > > > > > > >> droids-crawler-web/droids-crawler-web.iml
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Bertil Chapuis
> > > > > > > > Agimem Sàrl
> > > > > > > > http://www.agimem.com
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Thorsten Scherler <thorsten.at.apache.org>
> > > > > > codeBusters S.L. - web based systems
> > > > > > <consulting, training and solutions>
> > > > > > http://www.codebusters.es/
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Thorsten Scherler <thorsten.at.apache.org>
> > > > codeBusters S.L. - web based systems
> > > > <consulting, training and solutions>
> > > > http://www.codebusters.es/
> > > >
> > > >
> > >
> >
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote:
> I had a look at the different way available to automatically generate the
> team list and changes files. It seems it will be difficult to use them with
> our current documentation workflow. In consequence I hard coded the
> team-list.xml and the changes.xml files in the documentation folder.
>
> For the project team, I took all the committers and all the contributors who
> provided patches.
The problem with this as I see it is that this puts a too high value on
code contributions and too less on community contributions. For example
Otis who mainly contributed to the mailing list is not listed on the
team but personally I value his contribution equally as a patch.
To draw a line I think we should only list official committers as the
TEAM.
WDYT?
> For the changes, I used the report generated by jira for 0.0.1 and formated
> it in xdoc.
> Please check if modifications or additions are required.
That is fine, I see the initial changes more as pin pointing the main
feature of droids but yours is good.
>
> I think the aim for 0.0.1 is to release as soon as possible. It seems
> several people are motivated to work on 0.0.2.
Yeah, I just tried the deploy again (had to fix an issue with the
version of the buildnumber-maven-plugin) but as well get a 401. Will
review my config again.
salu2
> On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com> wrote:
>
> > Hi,
> > About the changes.xml file - is there anything to add here, seeing how
> > there
> > is no previous release?
> > Should the release use the apache-release maven profile (-Papache-release)?
> > Is there anything I can help with?
> > Eugen.
> >
> > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <scherler@gmail.com
> > >wrote:
> >
> > > Ok, will try that this afternoon, need to attend some meetings now.
> > >
> > > salu2
> > >
> > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > > > simply mvn deploy.
> > > >
> > > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
> > wrote:
> > > >
> > > > > What is the command you tried?
> > > > >
> > > > > Will try it then.
> > > > >
> > > > > salu2
> > > > >
> > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > > > > I tried to publish the project on the snapshot repository [1]. I
> > get
> > > the
> > > > > > following error:
> > > > > >
> > > > > > Error deploying artifact: Authorization failed: Access denied to:
> > > > > >
> > > > >
> > >
> > https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > > > > >
> > > > > > My settings.xml contains the correct servers [2]. I tried with
> > > plain-text
> > > > > > and encrypted passwords. The strange thing is that I am able to
> > login
> > > the
> > > > > > nexus server through the web interface. The thread [3] is
> > describing
> > > a
> > > > > > similar problem. I probably simply don't have the right to deploy.
> > > Could
> > > > > > someone with sufficient rights do the release?
> > > > > >
> > > > > > Thanks in advance.
> > > > > >
> > > > > > [1] -
> > > > > >
> > > > >
> > >
> > http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > > > > [2] - http://maven.apache.org/developers/committer-settings.html
> > > > > > [3] -
> > > > > >
> > > > >
> > >
> > http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > > > > >
> > > > > >
> > > > > > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com>
> > > wrote:
> > > > > >
> > > > > > > About the documentation file what's the convention? Do we have to
> > > put
> > > > > the
> > > > > > > apache license in their headers?
> > > > > > >
> > > > > > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
> > > > > wrote:
> > > > > > >
> > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > > > > >>
> > > > > > >> Make sure that all your files contain a ASF licence header
> > (look
> > > at
> > > > > > >>> the RAT report when in doubt, generated with mvn site)
> > > > > > >>> => mvn rat:check leads to a build failure with "too many
> > > unlicensed
> > > > > > >>> files:
> > > > > > >>> 199", looks quite strange. I'd love if someone had a look at
> > > this, in
> > > > > my
> > > > > > >>> opinion most classes and resources contains the ASF license
> > > header.
> > > > > > >>>
> > > > > > >>>
> > > > > > >> There was this, where the number of correct was reported back
> > > instead
> > > > > of
> > > > > > >> the number wrong:
> > > > > > >>
> > > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > > > > > >>
> > > > > > >> I don't know if it was fixed in 0.7 or not.
> > > > > > >>
> > > > > > >> At the bottom you will see the problem files. Shouldn't docs
> > come
> > > out
> > > > > of
> > > > > > >> this area of svn?
> > > > > > >>
> > > > > > >> The most troublesome of the files are these two:
> > > > > > >>
> > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > > >>
> > > > > > >> They've got GPL headers on them, but on the positive side they
> > > don't
> > > > > do
> > > > > > >> anything. They have been removed in r1074224.
> > > > > > >>
> > > > > > >> docs/mail-lists.dispatcher.css
> > > > > > >> docs/linkmap.html
> > > > > > >> docs/changes.dispatcher.css
> > > > > > >> docs/default.html
> > > > > > >> docs/contrib.html
> > > > > > >> docs/index.dispatcher.css
> > > > > > >> docs/mail-lists.html
> > > > > > >> docs/default.dispatcher.css
> > > > > > >> docs/contrib.dispatcher.css
> > > > > > >> docs/themes/droids.css
> > > > > > >> docs/api/droids-norobots/package-list
> > > > > > >> docs/api/droids-wicket/package-list
> > > > > > >> docs/api/droids-tika/package-list
> > > > > > >> docs/api/droids-solr/package-list
> > > > > > >> docs/api/droids-core/package-list
> > > > > > >> docs/api/droids-spring/package-list
> > > > > > >> docs/develope.html
> > > > > > >> docs/changes.rss
> > > > > > >> docs/develope.dispatcher.css
> > > > > > >> docs/changes.html
> > > > > > >> docs/todo.html
> > > > > > >> docs/todo.dispatcher.css
> > > > > > >> docs/index.html
> > > > > > >> docs/linkmap.dispatcher.css
> > > > > > >> docs/develop/develop.dispatcher.css
> > > > > > >> docs/develop/hello-crawler.html
> > > > > > >> docs/develop/develop.html
> > > > > > >> docs/develop/hello-crawler.dispatcher.css
> > > > > > >> docs/install.html
> > > > > > >> docs/install.dispatcher.css
> > > > > > >> droids-examples/pom.xml
> > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > > >> droids-examples/src/site/apt/index.apt
> > > > > > >> droids-examples/src/site/site.xml
> > > > > > >> droids-examples/src/site/fml/faq.fml
> > > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > > >> testing.properties
> > > > > > >> doap.rdf
> > > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > > > > >> src/templates/component/DROIDS-README.txt
> > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > > > > > >> src/documentation/resources/themes/common/css/droids.css
> > > > > > >> droids-crawler-web/droids-crawler-web.iml
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Bertil Chapuis
> > > > > > > Agimem Sàrl
> > > > > > > http://www.agimem.com
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Thorsten Scherler <thorsten.at.apache.org>
> > > > > codeBusters S.L. - web based systems
> > > > > <consulting, training and solutions>
> > > > > http://www.codebusters.es/
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Thorsten Scherler <thorsten.at.apache.org>
> > > codeBusters S.L. - web based systems
> > > <consulting, training and solutions>
> > > http://www.codebusters.es/
> > >
> > >
> >
>
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I had a look at the different way available to automatically generate the
team list and changes files. It seems it will be difficult to use them with
our current documentation workflow. In consequence I hard coded the
team-list.xml and the changes.xml files in the documentation folder.
For the project team, I took all the committers and all the contributors who
provided patches.
For the changes, I used the report generated by jira for 0.0.1 and formated
it in xdoc.
Please check if modifications or additions are required.
I think the aim for 0.0.1 is to release as soon as possible. It seems
several people are motivated to work on 0.0.2.
On 25 February 2011 19:12, Eugen Paraschiv <ha...@gmail.com> wrote:
> Hi,
> About the changes.xml file - is there anything to add here, seeing how
> there
> is no previous release?
> Should the release use the apache-release maven profile (-Papache-release)?
> Is there anything I can help with?
> Eugen.
>
> On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <scherler@gmail.com
> >wrote:
>
> > Ok, will try that this afternoon, need to attend some meetings now.
> >
> > salu2
> >
> > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > > simply mvn deploy.
> > >
> > > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com>
> wrote:
> > >
> > > > What is the command you tried?
> > > >
> > > > Will try it then.
> > > >
> > > > salu2
> > > >
> > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > > > I tried to publish the project on the snapshot repository [1]. I
> get
> > the
> > > > > following error:
> > > > >
> > > > > Error deploying artifact: Authorization failed: Access denied to:
> > > > >
> > > >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > > > >
> > > > > My settings.xml contains the correct servers [2]. I tried with
> > plain-text
> > > > > and encrypted passwords. The strange thing is that I am able to
> login
> > the
> > > > > nexus server through the web interface. The thread [3] is
> describing
> > a
> > > > > similar problem. I probably simply don't have the right to deploy.
> > Could
> > > > > someone with sufficient rights do the release?
> > > > >
> > > > > Thanks in advance.
> > > > >
> > > > > [1] -
> > > > >
> > > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > > > [2] - http://maven.apache.org/developers/committer-settings.html
> > > > > [3] -
> > > > >
> > > >
> >
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > > > >
> > > > >
> > > > > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com>
> > wrote:
> > > > >
> > > > > > About the documentation file what's the convention? Do we have to
> > put
> > > > the
> > > > > > apache license in their headers?
> > > > > >
> > > > > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
> > > > wrote:
> > > > > >
> > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > > > >>
> > > > > >> Make sure that all your files contain a ASF licence header
> (look
> > at
> > > > > >>> the RAT report when in doubt, generated with mvn site)
> > > > > >>> => mvn rat:check leads to a build failure with "too many
> > unlicensed
> > > > > >>> files:
> > > > > >>> 199", looks quite strange. I'd love if someone had a look at
> > this, in
> > > > my
> > > > > >>> opinion most classes and resources contains the ASF license
> > header.
> > > > > >>>
> > > > > >>>
> > > > > >> There was this, where the number of correct was reported back
> > instead
> > > > of
> > > > > >> the number wrong:
> > > > > >>
> > > > > >> https://issues.apache.org/jira/browse/RAT-35
> > > > > >>
> > > > > >> I don't know if it was fixed in 0.7 or not.
> > > > > >>
> > > > > >> At the bottom you will see the problem files. Shouldn't docs
> come
> > out
> > > > of
> > > > > >> this area of svn?
> > > > > >>
> > > > > >> The most troublesome of the files are these two:
> > > > > >>
> > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > >>
> > > > > >> They've got GPL headers on them, but on the positive side they
> > don't
> > > > do
> > > > > >> anything. They have been removed in r1074224.
> > > > > >>
> > > > > >> docs/mail-lists.dispatcher.css
> > > > > >> docs/linkmap.html
> > > > > >> docs/changes.dispatcher.css
> > > > > >> docs/default.html
> > > > > >> docs/contrib.html
> > > > > >> docs/index.dispatcher.css
> > > > > >> docs/mail-lists.html
> > > > > >> docs/default.dispatcher.css
> > > > > >> docs/contrib.dispatcher.css
> > > > > >> docs/themes/droids.css
> > > > > >> docs/api/droids-norobots/package-list
> > > > > >> docs/api/droids-wicket/package-list
> > > > > >> docs/api/droids-tika/package-list
> > > > > >> docs/api/droids-solr/package-list
> > > > > >> docs/api/droids-core/package-list
> > > > > >> docs/api/droids-spring/package-list
> > > > > >> docs/develope.html
> > > > > >> docs/changes.rss
> > > > > >> docs/develope.dispatcher.css
> > > > > >> docs/changes.html
> > > > > >> docs/todo.html
> > > > > >> docs/todo.dispatcher.css
> > > > > >> docs/index.html
> > > > > >> docs/linkmap.dispatcher.css
> > > > > >> docs/develop/develop.dispatcher.css
> > > > > >> docs/develop/hello-crawler.html
> > > > > >> docs/develop/develop.html
> > > > > >> docs/develop/hello-crawler.dispatcher.css
> > > > > >> docs/install.html
> > > > > >> docs/install.dispatcher.css
> > > > > >> droids-examples/pom.xml
> > > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > > >> droids-examples/src/site/apt/index.apt
> > > > > >> droids-examples/src/site/site.xml
> > > > > >> droids-examples/src/site/fml/faq.fml
> > > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > > >> testing.properties
> > > > > >> doap.rdf
> > > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > > > >> src/templates/component/DROIDS-README.txt
> > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > > > > >> src/documentation/resources/themes/common/css/droids.css
> > > > > >> droids-crawler-web/droids-crawler-web.iml
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Bertil Chapuis
> > > > > > Agimem Sàrl
> > > > > > http://www.agimem.com
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Thorsten Scherler <thorsten.at.apache.org>
> > > > codeBusters S.L. - web based systems
> > > > <consulting, training and solutions>
> > > > http://www.codebusters.es/
> > > >
> > > >
> > >
> > >
> >
> > --
> > Thorsten Scherler <thorsten.at.apache.org>
> > codeBusters S.L. - web based systems
> > <consulting, training and solutions>
> > http://www.codebusters.es/
> >
> >
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Eugen Paraschiv <ha...@gmail.com>.
Hi,
About the changes.xml file - is there anything to add here, seeing how there
is no previous release?
Should the release use the apache-release maven profile (-Papache-release)?
Is there anything I can help with?
Eugen.
On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler <sc...@gmail.com>wrote:
> Ok, will try that this afternoon, need to attend some meetings now.
>
> salu2
>
> On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> > simply mvn deploy.
> >
> > On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com> wrote:
> >
> > > What is the command you tried?
> > >
> > > Will try it then.
> > >
> > > salu2
> > >
> > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > > I tried to publish the project on the snapshot repository [1]. I get
> the
> > > > following error:
> > > >
> > > > Error deploying artifact: Authorization failed: Access denied to:
> > > >
> > >
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > > >
> > > > My settings.xml contains the correct servers [2]. I tried with
> plain-text
> > > > and encrypted passwords. The strange thing is that I am able to login
> the
> > > > nexus server through the web interface. The thread [3] is describing
> a
> > > > similar problem. I probably simply don't have the right to deploy.
> Could
> > > > someone with sufficient rights do the release?
> > > >
> > > > Thanks in advance.
> > > >
> > > > [1] -
> > > >
> > >
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > > [2] - http://maven.apache.org/developers/committer-settings.html
> > > > [3] -
> > > >
> > >
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > > >
> > > >
> > > > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com>
> wrote:
> > > >
> > > > > About the documentation file what's the convention? Do we have to
> put
> > > the
> > > > > apache license in their headers?
> > > > >
> > > > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
> > > wrote:
> > > > >
> > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > > >>
> > > > >> Make sure that all your files contain a ASF licence header (look
> at
> > > > >>> the RAT report when in doubt, generated with mvn site)
> > > > >>> => mvn rat:check leads to a build failure with "too many
> unlicensed
> > > > >>> files:
> > > > >>> 199", looks quite strange. I'd love if someone had a look at
> this, in
> > > my
> > > > >>> opinion most classes and resources contains the ASF license
> header.
> > > > >>>
> > > > >>>
> > > > >> There was this, where the number of correct was reported back
> instead
> > > of
> > > > >> the number wrong:
> > > > >>
> > > > >> https://issues.apache.org/jira/browse/RAT-35
> > > > >>
> > > > >> I don't know if it was fixed in 0.7 or not.
> > > > >>
> > > > >> At the bottom you will see the problem files. Shouldn't docs come
> out
> > > of
> > > > >> this area of svn?
> > > > >>
> > > > >> The most troublesome of the files are these two:
> > > > >>
> > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > >>
> > > > >> They've got GPL headers on them, but on the positive side they
> don't
> > > do
> > > > >> anything. They have been removed in r1074224.
> > > > >>
> > > > >> docs/mail-lists.dispatcher.css
> > > > >> docs/linkmap.html
> > > > >> docs/changes.dispatcher.css
> > > > >> docs/default.html
> > > > >> docs/contrib.html
> > > > >> docs/index.dispatcher.css
> > > > >> docs/mail-lists.html
> > > > >> docs/default.dispatcher.css
> > > > >> docs/contrib.dispatcher.css
> > > > >> docs/themes/droids.css
> > > > >> docs/api/droids-norobots/package-list
> > > > >> docs/api/droids-wicket/package-list
> > > > >> docs/api/droids-tika/package-list
> > > > >> docs/api/droids-solr/package-list
> > > > >> docs/api/droids-core/package-list
> > > > >> docs/api/droids-spring/package-list
> > > > >> docs/develope.html
> > > > >> docs/changes.rss
> > > > >> docs/develope.dispatcher.css
> > > > >> docs/changes.html
> > > > >> docs/todo.html
> > > > >> docs/todo.dispatcher.css
> > > > >> docs/index.html
> > > > >> docs/linkmap.dispatcher.css
> > > > >> docs/develop/develop.dispatcher.css
> > > > >> docs/develop/hello-crawler.html
> > > > >> docs/develop/develop.html
> > > > >> docs/develop/hello-crawler.dispatcher.css
> > > > >> docs/install.html
> > > > >> docs/install.dispatcher.css
> > > > >> droids-examples/pom.xml
> > > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > > >> droids-examples/src/site/apt/index.apt
> > > > >> droids-examples/src/site/site.xml
> > > > >> droids-examples/src/site/fml/faq.fml
> > > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > > >> testing.properties
> > > > >> doap.rdf
> > > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > > >> src/templates/component/DROIDS-README.txt
> > > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > > > >> src/documentation/resources/themes/common/css/droids.css
> > > > >> droids-crawler-web/droids-crawler-web.iml
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Bertil Chapuis
> > > > > Agimem Sàrl
> > > > > http://www.agimem.com
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Thorsten Scherler <thorsten.at.apache.org>
> > > codeBusters S.L. - web based systems
> > > <consulting, training and solutions>
> > > http://www.codebusters.es/
> > >
> > >
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
Ok, will try that this afternoon, need to attend some meetings now.
salu2
On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote:
> simply mvn deploy.
>
> On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com> wrote:
>
> > What is the command you tried?
> >
> > Will try it then.
> >
> > salu2
> >
> > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > > I tried to publish the project on the snapshot repository [1]. I get the
> > > following error:
> > >
> > > Error deploying artifact: Authorization failed: Access denied to:
> > >
> > https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> > >
> > > My settings.xml contains the correct servers [2]. I tried with plain-text
> > > and encrypted passwords. The strange thing is that I am able to login the
> > > nexus server through the web interface. The thread [3] is describing a
> > > similar problem. I probably simply don't have the right to deploy. Could
> > > someone with sufficient rights do the release?
> > >
> > > Thanks in advance.
> > >
> > > [1] -
> > >
> > http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > > [2] - http://maven.apache.org/developers/committer-settings.html
> > > [3] -
> > >
> > http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> > >
> > >
> > > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com> wrote:
> > >
> > > > About the documentation file what's the convention? Do we have to put
> > the
> > > > apache license in their headers?
> > > >
> > > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
> > wrote:
> > > >
> > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > > >>
> > > >> Make sure that all your files contain a ASF licence header (look at
> > > >>> the RAT report when in doubt, generated with mvn site)
> > > >>> => mvn rat:check leads to a build failure with "too many unlicensed
> > > >>> files:
> > > >>> 199", looks quite strange. I'd love if someone had a look at this, in
> > my
> > > >>> opinion most classes and resources contains the ASF license header.
> > > >>>
> > > >>>
> > > >> There was this, where the number of correct was reported back instead
> > of
> > > >> the number wrong:
> > > >>
> > > >> https://issues.apache.org/jira/browse/RAT-35
> > > >>
> > > >> I don't know if it was fixed in 0.7 or not.
> > > >>
> > > >> At the bottom you will see the problem files. Shouldn't docs come out
> > of
> > > >> this area of svn?
> > > >>
> > > >> The most troublesome of the files are these two:
> > > >>
> > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > >>
> > > >> They've got GPL headers on them, but on the positive side they don't
> > do
> > > >> anything. They have been removed in r1074224.
> > > >>
> > > >> docs/mail-lists.dispatcher.css
> > > >> docs/linkmap.html
> > > >> docs/changes.dispatcher.css
> > > >> docs/default.html
> > > >> docs/contrib.html
> > > >> docs/index.dispatcher.css
> > > >> docs/mail-lists.html
> > > >> docs/default.dispatcher.css
> > > >> docs/contrib.dispatcher.css
> > > >> docs/themes/droids.css
> > > >> docs/api/droids-norobots/package-list
> > > >> docs/api/droids-wicket/package-list
> > > >> docs/api/droids-tika/package-list
> > > >> docs/api/droids-solr/package-list
> > > >> docs/api/droids-core/package-list
> > > >> docs/api/droids-spring/package-list
> > > >> docs/develope.html
> > > >> docs/changes.rss
> > > >> docs/develope.dispatcher.css
> > > >> docs/changes.html
> > > >> docs/todo.html
> > > >> docs/todo.dispatcher.css
> > > >> docs/index.html
> > > >> docs/linkmap.dispatcher.css
> > > >> docs/develop/develop.dispatcher.css
> > > >> docs/develop/hello-crawler.html
> > > >> docs/develop/develop.html
> > > >> docs/develop/hello-crawler.dispatcher.css
> > > >> docs/install.html
> > > >> docs/install.dispatcher.css
> > > >> droids-examples/pom.xml
> > > >> droids-examples/src/main/java/org/apache/droids/App.java
> > > >> droids-examples/src/site/apt/index.apt
> > > >> droids-examples/src/site/site.xml
> > > >> droids-examples/src/site/fml/faq.fml
> > > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > > >> testing.properties
> > > >> doap.rdf
> > > >> tools/ant/bin/README-forrest-upgrade.txt
> > > >> src/templates/component/DROIDS-README.txt
> > > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > > >> src/documentation/resources/themes/common/css/droids.css
> > > >> droids-crawler-web/droids-crawler-web.iml
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Bertil Chapuis
> > > > Agimem Sàrl
> > > > http://www.agimem.com
> > > >
> > > >
> > >
> > >
> >
> > --
> > Thorsten Scherler <thorsten.at.apache.org>
> > codeBusters S.L. - web based systems
> > <consulting, training and solutions>
> > http://www.codebusters.es/
> >
> >
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
simply mvn deploy.
On 25 February 2011 10:55, Thorsten Scherler <sc...@gmail.com> wrote:
> What is the command you tried?
>
> Will try it then.
>
> salu2
>
> On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> > I tried to publish the project on the snapshot repository [1]. I get the
> > following error:
> >
> > Error deploying artifact: Authorization failed: Access denied to:
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
> >
> > My settings.xml contains the correct servers [2]. I tried with plain-text
> > and encrypted passwords. The strange thing is that I am able to login the
> > nexus server through the web interface. The thread [3] is describing a
> > similar problem. I probably simply don't have the right to deploy. Could
> > someone with sufficient rights do the release?
> >
> > Thanks in advance.
> >
> > [1] -
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> > [2] - http://maven.apache.org/developers/committer-settings.html
> > [3] -
> >
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
> >
> >
> > On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com> wrote:
> >
> > > About the documentation file what's the convention? Do we have to put
> the
> > > apache license in their headers?
> > >
> > > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org>
> wrote:
> > >
> > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> > >>
> > >> Make sure that all your files contain a ASF licence header (look at
> > >>> the RAT report when in doubt, generated with mvn site)
> > >>> => mvn rat:check leads to a build failure with "too many unlicensed
> > >>> files:
> > >>> 199", looks quite strange. I'd love if someone had a look at this, in
> my
> > >>> opinion most classes and resources contains the ASF license header.
> > >>>
> > >>>
> > >> There was this, where the number of correct was reported back instead
> of
> > >> the number wrong:
> > >>
> > >> https://issues.apache.org/jira/browse/RAT-35
> > >>
> > >> I don't know if it was fixed in 0.7 or not.
> > >>
> > >> At the bottom you will see the problem files. Shouldn't docs come out
> of
> > >> this area of svn?
> > >>
> > >> The most troublesome of the files are these two:
> > >>
> > >> droids-examples/src/main/java/org/apache/droids/App.java
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >>
> > >> They've got GPL headers on them, but on the positive side they don't
> do
> > >> anything. They have been removed in r1074224.
> > >>
> > >> docs/mail-lists.dispatcher.css
> > >> docs/linkmap.html
> > >> docs/changes.dispatcher.css
> > >> docs/default.html
> > >> docs/contrib.html
> > >> docs/index.dispatcher.css
> > >> docs/mail-lists.html
> > >> docs/default.dispatcher.css
> > >> docs/contrib.dispatcher.css
> > >> docs/themes/droids.css
> > >> docs/api/droids-norobots/package-list
> > >> docs/api/droids-wicket/package-list
> > >> docs/api/droids-tika/package-list
> > >> docs/api/droids-solr/package-list
> > >> docs/api/droids-core/package-list
> > >> docs/api/droids-spring/package-list
> > >> docs/develope.html
> > >> docs/changes.rss
> > >> docs/develope.dispatcher.css
> > >> docs/changes.html
> > >> docs/todo.html
> > >> docs/todo.dispatcher.css
> > >> docs/index.html
> > >> docs/linkmap.dispatcher.css
> > >> docs/develop/develop.dispatcher.css
> > >> docs/develop/hello-crawler.html
> > >> docs/develop/develop.html
> > >> docs/develop/hello-crawler.dispatcher.css
> > >> docs/install.html
> > >> docs/install.dispatcher.css
> > >> droids-examples/pom.xml
> > >> droids-examples/src/main/java/org/apache/droids/App.java
> > >> droids-examples/src/site/apt/index.apt
> > >> droids-examples/src/site/site.xml
> > >> droids-examples/src/site/fml/faq.fml
> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> > >> testing.properties
> > >> doap.rdf
> > >> tools/ant/bin/README-forrest-upgrade.txt
> > >> src/templates/component/DROIDS-README.txt
> > >> src/documentation/content/xdocs/images/droidsOverview.svg
> > >> src/documentation/resources/themes/common/css/droids.css
> > >> droids-crawler-web/droids-crawler-web.iml
> > >>
> > >
> > >
> > >
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> > >
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
What is the command you tried?
Will try it then.
salu2
On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote:
> I tried to publish the project on the snapshot repository [1]. I get the
> following error:
>
> Error deploying artifact: Authorization failed: Access denied to:
> https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
>
> My settings.xml contains the correct servers [2]. I tried with plain-text
> and encrypted passwords. The strange thing is that I am able to login the
> nexus server through the web interface. The thread [3] is describing a
> similar problem. I probably simply don't have the right to deploy. Could
> someone with sufficient rights do the release?
>
> Thanks in advance.
>
> [1] -
> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
> [2] - http://maven.apache.org/developers/committer-settings.html
> [3] -
> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
>
>
> On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com> wrote:
>
> > About the documentation file what's the convention? Do we have to put the
> > apache license in their headers?
> >
> > On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org> wrote:
> >
> >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> >>
> >> Make sure that all your files contain a ASF licence header (look at
> >>> the RAT report when in doubt, generated with mvn site)
> >>> => mvn rat:check leads to a build failure with "too many unlicensed
> >>> files:
> >>> 199", looks quite strange. I'd love if someone had a look at this, in my
> >>> opinion most classes and resources contains the ASF license header.
> >>>
> >>>
> >> There was this, where the number of correct was reported back instead of
> >> the number wrong:
> >>
> >> https://issues.apache.org/jira/browse/RAT-35
> >>
> >> I don't know if it was fixed in 0.7 or not.
> >>
> >> At the bottom you will see the problem files. Shouldn't docs come out of
> >> this area of svn?
> >>
> >> The most troublesome of the files are these two:
> >>
> >> droids-examples/src/main/java/org/apache/droids/App.java
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >>
> >> They've got GPL headers on them, but on the positive side they don't do
> >> anything. They have been removed in r1074224.
> >>
> >> docs/mail-lists.dispatcher.css
> >> docs/linkmap.html
> >> docs/changes.dispatcher.css
> >> docs/default.html
> >> docs/contrib.html
> >> docs/index.dispatcher.css
> >> docs/mail-lists.html
> >> docs/default.dispatcher.css
> >> docs/contrib.dispatcher.css
> >> docs/themes/droids.css
> >> docs/api/droids-norobots/package-list
> >> docs/api/droids-wicket/package-list
> >> docs/api/droids-tika/package-list
> >> docs/api/droids-solr/package-list
> >> docs/api/droids-core/package-list
> >> docs/api/droids-spring/package-list
> >> docs/develope.html
> >> docs/changes.rss
> >> docs/develope.dispatcher.css
> >> docs/changes.html
> >> docs/todo.html
> >> docs/todo.dispatcher.css
> >> docs/index.html
> >> docs/linkmap.dispatcher.css
> >> docs/develop/develop.dispatcher.css
> >> docs/develop/hello-crawler.html
> >> docs/develop/develop.html
> >> docs/develop/hello-crawler.dispatcher.css
> >> docs/install.html
> >> docs/install.dispatcher.css
> >> droids-examples/pom.xml
> >> droids-examples/src/main/java/org/apache/droids/App.java
> >> droids-examples/src/site/apt/index.apt
> >> droids-examples/src/site/site.xml
> >> droids-examples/src/site/fml/faq.fml
> >> droids-examples/src/test/java/org/apache/droids/AppTest.java
> >> testing.properties
> >> doap.rdf
> >> tools/ant/bin/README-forrest-upgrade.txt
> >> src/templates/component/DROIDS-README.txt
> >> src/documentation/content/xdocs/images/droidsOverview.svg
> >> src/documentation/resources/themes/common/css/droids.css
> >> droids-crawler-web/droids-crawler-web.iml
> >>
> >
> >
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
> >
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I tried to publish the project on the snapshot repository [1]. I get the
following error:
Error deploying artifact: Authorization failed: Access denied to:
https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom
My settings.xml contains the correct servers [2]. I tried with plain-text
and encrypted passwords. The strange thing is that I am able to login the
nexus server through the web interface. The thread [3] is describing a
similar problem. I probably simply don't have the right to deploy. Could
someone with sufficient rights do the release?
Thanks in advance.
[1] -
http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
[2] - http://maven.apache.org/developers/committer-settings.html
[3] -
http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html
On 25 February 2011 09:13, Chapuis Bertil <bc...@agimem.com> wrote:
> About the documentation file what's the convention? Do we have to put the
> apache license in their headers?
>
> On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org> wrote:
>
>> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>>
>> Make sure that all your files contain a ASF licence header (look at
>>> the RAT report when in doubt, generated with mvn site)
>>> => mvn rat:check leads to a build failure with "too many unlicensed
>>> files:
>>> 199", looks quite strange. I'd love if someone had a look at this, in my
>>> opinion most classes and resources contains the ASF license header.
>>>
>>>
>> There was this, where the number of correct was reported back instead of
>> the number wrong:
>>
>> https://issues.apache.org/jira/browse/RAT-35
>>
>> I don't know if it was fixed in 0.7 or not.
>>
>> At the bottom you will see the problem files. Shouldn't docs come out of
>> this area of svn?
>>
>> The most troublesome of the files are these two:
>>
>> droids-examples/src/main/java/org/apache/droids/App.java
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>>
>> They've got GPL headers on them, but on the positive side they don't do
>> anything. They have been removed in r1074224.
>>
>> docs/mail-lists.dispatcher.css
>> docs/linkmap.html
>> docs/changes.dispatcher.css
>> docs/default.html
>> docs/contrib.html
>> docs/index.dispatcher.css
>> docs/mail-lists.html
>> docs/default.dispatcher.css
>> docs/contrib.dispatcher.css
>> docs/themes/droids.css
>> docs/api/droids-norobots/package-list
>> docs/api/droids-wicket/package-list
>> docs/api/droids-tika/package-list
>> docs/api/droids-solr/package-list
>> docs/api/droids-core/package-list
>> docs/api/droids-spring/package-list
>> docs/develope.html
>> docs/changes.rss
>> docs/develope.dispatcher.css
>> docs/changes.html
>> docs/todo.html
>> docs/todo.dispatcher.css
>> docs/index.html
>> docs/linkmap.dispatcher.css
>> docs/develop/develop.dispatcher.css
>> docs/develop/hello-crawler.html
>> docs/develop/develop.html
>> docs/develop/hello-crawler.dispatcher.css
>> docs/install.html
>> docs/install.dispatcher.css
>> droids-examples/pom.xml
>> droids-examples/src/main/java/org/apache/droids/App.java
>> droids-examples/src/site/apt/index.apt
>> droids-examples/src/site/site.xml
>> droids-examples/src/site/fml/faq.fml
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> testing.properties
>> doap.rdf
>> tools/ant/bin/README-forrest-upgrade.txt
>> src/templates/component/DROIDS-README.txt
>> src/documentation/content/xdocs/images/droidsOverview.svg
>> src/documentation/resources/themes/common/css/droids.css
>> droids-crawler-web/droids-crawler-web.iml
>>
>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
About the documentation file what's the convention? Do we have to put the
apache license in their headers?
On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org> wrote:
> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>
> Make sure that all your files contain a ASF licence header (look at
>> the RAT report when in doubt, generated with mvn site)
>> => mvn rat:check leads to a build failure with "too many unlicensed
>> files:
>> 199", looks quite strange. I'd love if someone had a look at this, in my
>> opinion most classes and resources contains the ASF license header.
>>
>>
> There was this, where the number of correct was reported back instead of
> the number wrong:
>
> https://issues.apache.org/jira/browse/RAT-35
>
> I don't know if it was fixed in 0.7 or not.
>
> At the bottom you will see the problem files. Shouldn't docs come out of
> this area of svn?
>
> The most troublesome of the files are these two:
>
> droids-examples/src/main/java/org/apache/droids/App.java
> droids-examples/src/test/java/org/apache/droids/AppTest.java
>
> They've got GPL headers on them, but on the positive side they don't do
> anything. They have been removed in r1074224.
>
> docs/mail-lists.dispatcher.css
> docs/linkmap.html
> docs/changes.dispatcher.css
> docs/default.html
> docs/contrib.html
> docs/index.dispatcher.css
> docs/mail-lists.html
> docs/default.dispatcher.css
> docs/contrib.dispatcher.css
> docs/themes/droids.css
> docs/api/droids-norobots/package-list
> docs/api/droids-wicket/package-list
> docs/api/droids-tika/package-list
> docs/api/droids-solr/package-list
> docs/api/droids-core/package-list
> docs/api/droids-spring/package-list
> docs/develope.html
> docs/changes.rss
> docs/develope.dispatcher.css
> docs/changes.html
> docs/todo.html
> docs/todo.dispatcher.css
> docs/index.html
> docs/linkmap.dispatcher.css
> docs/develop/develop.dispatcher.css
> docs/develop/hello-crawler.html
> docs/develop/develop.html
> docs/develop/hello-crawler.dispatcher.css
> docs/install.html
> docs/install.dispatcher.css
> droids-examples/pom.xml
> droids-examples/src/main/java/org/apache/droids/App.java
> droids-examples/src/site/apt/index.apt
> droids-examples/src/site/site.xml
> droids-examples/src/site/fml/faq.fml
> droids-examples/src/test/java/org/apache/droids/AppTest.java
> testing.properties
> doap.rdf
> tools/ant/bin/README-forrest-upgrade.txt
> src/templates/component/DROIDS-README.txt
> src/documentation/content/xdocs/images/droidsOverview.svg
> src/documentation/resources/themes/common/css/droids.css
> droids-crawler-web/droids-crawler-web.iml
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Sorry :-), I missed the fact you already did it.
On 24 February 2011 18:45, Chapuis Bertil <bc...@agimem.com> wrote:
> I missed the example package. These files have been added yesterday as a
> basis for the examples. Since they do nothing and contains a copyright I
> will simply remove them.
>
>
> On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org> wrote:
>
>> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>>
>> Make sure that all your files contain a ASF licence header (look at
>>> the RAT report when in doubt, generated with mvn site)
>>> => mvn rat:check leads to a build failure with "too many unlicensed
>>> files:
>>> 199", looks quite strange. I'd love if someone had a look at this, in my
>>> opinion most classes and resources contains the ASF license header.
>>>
>>>
>> There was this, where the number of correct was reported back instead of
>> the number wrong:
>>
>> https://issues.apache.org/jira/browse/RAT-35
>>
>> I don't know if it was fixed in 0.7 or not.
>>
>> At the bottom you will see the problem files. Shouldn't docs come out of
>> this area of svn?
>>
>> The most troublesome of the files are these two:
>>
>> droids-examples/src/main/java/org/apache/droids/App.java
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>>
>> They've got GPL headers on them, but on the positive side they don't do
>> anything. They have been removed in r1074224.
>>
>> docs/mail-lists.dispatcher.css
>> docs/linkmap.html
>> docs/changes.dispatcher.css
>> docs/default.html
>> docs/contrib.html
>> docs/index.dispatcher.css
>> docs/mail-lists.html
>> docs/default.dispatcher.css
>> docs/contrib.dispatcher.css
>> docs/themes/droids.css
>> docs/api/droids-norobots/package-list
>> docs/api/droids-wicket/package-list
>> docs/api/droids-tika/package-list
>> docs/api/droids-solr/package-list
>> docs/api/droids-core/package-list
>> docs/api/droids-spring/package-list
>> docs/develope.html
>> docs/changes.rss
>> docs/develope.dispatcher.css
>> docs/changes.html
>> docs/todo.html
>> docs/todo.dispatcher.css
>> docs/index.html
>> docs/linkmap.dispatcher.css
>> docs/develop/develop.dispatcher.css
>> docs/develop/hello-crawler.html
>> docs/develop/develop.html
>> docs/develop/hello-crawler.dispatcher.css
>> docs/install.html
>> docs/install.dispatcher.css
>> droids-examples/pom.xml
>> droids-examples/src/main/java/org/apache/droids/App.java
>> droids-examples/src/site/apt/index.apt
>> droids-examples/src/site/site.xml
>> droids-examples/src/site/fml/faq.fml
>> droids-examples/src/test/java/org/apache/droids/AppTest.java
>> testing.properties
>> doap.rdf
>> tools/ant/bin/README-forrest-upgrade.txt
>> src/templates/component/DROIDS-README.txt
>> src/documentation/content/xdocs/images/droidsOverview.svg
>> src/documentation/resources/themes/common/css/droids.css
>> droids-crawler-web/droids-crawler-web.iml
>>
>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I missed the example package. These files have been added yesterday as a
basis for the examples. Since they do nothing and contains a copyright I
will simply remove them.
On 24 February 2011 18:27, Richard Frovarp <rf...@apache.org> wrote:
> On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
>
> Make sure that all your files contain a ASF licence header (look at
>> the RAT report when in doubt, generated with mvn site)
>> => mvn rat:check leads to a build failure with "too many unlicensed
>> files:
>> 199", looks quite strange. I'd love if someone had a look at this, in my
>> opinion most classes and resources contains the ASF license header.
>>
>>
> There was this, where the number of correct was reported back instead of
> the number wrong:
>
> https://issues.apache.org/jira/browse/RAT-35
>
> I don't know if it was fixed in 0.7 or not.
>
> At the bottom you will see the problem files. Shouldn't docs come out of
> this area of svn?
>
> The most troublesome of the files are these two:
>
> droids-examples/src/main/java/org/apache/droids/App.java
> droids-examples/src/test/java/org/apache/droids/AppTest.java
>
> They've got GPL headers on them, but on the positive side they don't do
> anything. They have been removed in r1074224.
>
> docs/mail-lists.dispatcher.css
> docs/linkmap.html
> docs/changes.dispatcher.css
> docs/default.html
> docs/contrib.html
> docs/index.dispatcher.css
> docs/mail-lists.html
> docs/default.dispatcher.css
> docs/contrib.dispatcher.css
> docs/themes/droids.css
> docs/api/droids-norobots/package-list
> docs/api/droids-wicket/package-list
> docs/api/droids-tika/package-list
> docs/api/droids-solr/package-list
> docs/api/droids-core/package-list
> docs/api/droids-spring/package-list
> docs/develope.html
> docs/changes.rss
> docs/develope.dispatcher.css
> docs/changes.html
> docs/todo.html
> docs/todo.dispatcher.css
> docs/index.html
> docs/linkmap.dispatcher.css
> docs/develop/develop.dispatcher.css
> docs/develop/hello-crawler.html
> docs/develop/develop.html
> docs/develop/hello-crawler.dispatcher.css
> docs/install.html
> docs/install.dispatcher.css
> droids-examples/pom.xml
> droids-examples/src/main/java/org/apache/droids/App.java
> droids-examples/src/site/apt/index.apt
> droids-examples/src/site/site.xml
> droids-examples/src/site/fml/faq.fml
> droids-examples/src/test/java/org/apache/droids/AppTest.java
> testing.properties
> doap.rdf
> tools/ant/bin/README-forrest-upgrade.txt
> src/templates/component/DROIDS-README.txt
> src/documentation/content/xdocs/images/droidsOverview.svg
> src/documentation/resources/themes/common/css/droids.css
> droids-crawler-web/droids-crawler-web.iml
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Richard Frovarp <rf...@apache.org>.
On 02/24/2011 05:47 AM, Chapuis Bertil wrote:
> Make sure that all your files contain a ASF licence header (look at
> the RAT report when in doubt, generated with mvn site)
> => mvn rat:check leads to a build failure with "too many unlicensed files:
> 199", looks quite strange. I'd love if someone had a look at this, in my
> opinion most classes and resources contains the ASF license header.
>
There was this, where the number of correct was reported back instead of
the number wrong:
https://issues.apache.org/jira/browse/RAT-35
I don't know if it was fixed in 0.7 or not.
At the bottom you will see the problem files. Shouldn't docs come out of
this area of svn?
The most troublesome of the files are these two:
droids-examples/src/main/java/org/apache/droids/App.java
droids-examples/src/test/java/org/apache/droids/AppTest.java
They've got GPL headers on them, but on the positive side they don't do
anything. They have been removed in r1074224.
docs/mail-lists.dispatcher.css
docs/linkmap.html
docs/changes.dispatcher.css
docs/default.html
docs/contrib.html
docs/index.dispatcher.css
docs/mail-lists.html
docs/default.dispatcher.css
docs/contrib.dispatcher.css
docs/themes/droids.css
docs/api/droids-norobots/package-list
docs/api/droids-wicket/package-list
docs/api/droids-tika/package-list
docs/api/droids-solr/package-list
docs/api/droids-core/package-list
docs/api/droids-spring/package-list
docs/develope.html
docs/changes.rss
docs/develope.dispatcher.css
docs/changes.html
docs/todo.html
docs/todo.dispatcher.css
docs/index.html
docs/linkmap.dispatcher.css
docs/develop/develop.dispatcher.css
docs/develop/hello-crawler.html
docs/develop/develop.html
docs/develop/hello-crawler.dispatcher.css
docs/install.html
docs/install.dispatcher.css
droids-examples/pom.xml
droids-examples/src/main/java/org/apache/droids/App.java
droids-examples/src/site/apt/index.apt
droids-examples/src/site/site.xml
droids-examples/src/site/fml/faq.fml
droids-examples/src/test/java/org/apache/droids/AppTest.java
testing.properties
doap.rdf
tools/ant/bin/README-forrest-upgrade.txt
src/templates/component/DROIDS-README.txt
src/documentation/content/xdocs/images/droidsOverview.svg
src/documentation/resources/themes/common/css/droids.css
droids-crawler-web/droids-crawler-web.iml
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I had a look to the release checklist.
Make sure that you are not referencing any SNAPSHOT version (dependencies
and plugins) otherwise the release will fail
=> OK
Make sure that you update the xdocs/changes.xml file to reflect your release
=> no changes.xml file yet. Should we add that in 0.1 or in 0.2.?
Make sure that all your files contain a ASF licence header (look at
the RAT report when in doubt, generated with mvn site)
=> mvn rat:check leads to a build failure with "too many unlicensed files:
199", looks quite strange. I'd love if someone had a look at this, in my
opinion most classes and resources contains the ASF license header.
Make sure that the LICENSE and NOTICE files are present and correct -
especially that the year is correct in the NOTICE file.
=> should be OK
Make sure that you make a test build using a clean checkout
=> OK
Make sure that there are no major bugs in JIRA
=> OK
Make sure to add all missing committers and contributers
=> No contributers and committers page yet. Should we add that in 0.1 or in
0.2.?
On 24 February 2011 11:11, Chapuis Bertil <bc...@agimem.com> wrote:
> Ok, I will wait for the advices.
>
>
> On 24 February 2011 11:04, Thorsten Scherler <sc...@gmail.com> wrote:
>
>> On Thu, 2011-02-24 at 10:25 +0100, Chapuis Bertil wrote:
>> > ...
>> >
>> > Do I run the mvn release:prepare without the dry run parameter to see
>> the
>> > magic in action? ;-)
>>
>> I just wrote to the general incubator list to get advice about when to
>> use the plugin. In my understanding we need to first do some RC, no?
>>
>> Maybe you can try to do a "0.1-RC1-incubator" release first?
>>
>> salu2
>> --
>> Thorsten Scherler <thorsten.at.apache.org>
>> codeBusters S.L. - web based systems
>> <consulting, training and solutions>
>> http://www.codebusters.es/
>>
>>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Ok, I will wait for the advices.
On 24 February 2011 11:04, Thorsten Scherler <sc...@gmail.com> wrote:
> On Thu, 2011-02-24 at 10:25 +0100, Chapuis Bertil wrote:
> > ...
> >
> > Do I run the mvn release:prepare without the dry run parameter to see the
> > magic in action? ;-)
>
> I just wrote to the general incubator list to get advice about when to
> use the plugin. In my understanding we need to first do some RC, no?
>
> Maybe you can try to do a "0.1-RC1-incubator" release first?
>
> salu2
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Thu, 2011-02-24 at 10:25 +0100, Chapuis Bertil wrote:
> ...
>
> Do I run the mvn release:prepare without the dry run parameter to see the
> magic in action? ;-)
I just wrote to the general incubator list to get advice about when to
use the plugin. In my understanding we need to first do some RC, no?
Maybe you can try to do a "0.1-RC1-incubator" release first?
salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Strange, I also did it and this problem has not appeared. After a diff on
the generated poms, it seems everything went well with the dry run. I also
added a profile for the generation of pgp signatures [1] and commented the
droids-example module since we don't want it to be released it now.
Do I run the mvn release:prepare without the dry run parameter to see the
magic in action? ;-)
[1] -
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
On 24 February 2011 10:12, Thorsten Scherler <sc...@gmail.com> wrote:
> On Wed, 2011-02-23 at 13:45 +0100, Chapuis Bertil wrote:
> > It seems that it is possible to perform a dry run:
> >
> > mvn release:prepare -DdryRun=true
> >
> > I can try but I hope it will have no direct effects on the repository.
>
> Yeah I just did that but get an error.
> [INFO] Missing:
> [INFO] ----------
> [INFO] 1)
>
> com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:jar:1.13-SNAPSHOT
>
> Looks quite weird however
>
> [INFO] Path to dependency:
> [INFO] 1)
> org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-5-SNAPSHOT
> [INFO] 2)
>
> com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:jar:1.13-SNAPSHOT
>
> seems to come from "buildnumber-maven-plugin"
>
> salu2
>
> >
> >
> >
> > On 23 February 2011 13:21, Thorsten Scherler <sc...@gmail.com>
> > wrote:
> > On Wed, 2011-02-23 at 11:49 +0100, Chapuis Bertil wrote:
> > > I had a look at the apache documentation page for releases
> > [1]. The section
> > > "Prepare your pom for release" says : Make sure there are no
> > snapshots in
> > > the POMs to be released. Does it means we have to change all
> > the version
> > > numbers in our pom files? I thought that the maven release
> > plugin was asking
> > > for the release number and making the changes automatically.
> >
> >
> > I tied to use it ones in a client project but I can remember
> > that I had
> > to drop it since it did to much (including it tagged the scm
> > rep). I am
> > not sure whether we can make it staged to review the different
> > steps.
> >
> > salu2
> >
> >
> > >
> > > [1] -
> > http://www.apache.org/dev/publishing-maven-artifacts.html
> > >
> > >
> > > On 21 February 2011 21:19, Eugen Paraschiv
> > <ha...@gmail.com> wrote:
> > >
> > > > Hi,
> > > > I've used maven-release-plugin before. It requires a few
> > elements to be
> > > > present in the pom and does indeed do all of the work for
> > you. I will follow
> > > > up with a quick guide from my own documentation about how
> > to use it and what
> > > > it needs.
> > > > Eugen.
> > > >
> > > > On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil
> > <bc...@agimem.com>wrote:
> > > >
> > > >> Hello all,
> > > >>
> > > >> The opened tickets for the release 0.0.1 are nearly all
> > closed. As Otis
> > > >> mentioned it, it may be a good idea to release.
> > > >>
> > > >> I had a look at the maven-release-plugin. It seems that
> > mvn
> > > >> release:prepare
> > > >> [1] is doing most of the work. Since it looks quite
> > magic, I wanted to
> > > >> know
> > > >> who already did that in the past with another
> > project :-).
> > > >>
> > > >> At this step, several questions also occurs about how
> > releases will be
> > > >> managed.
> > > >>
> > > >> - Do we set a time scope for the next release?
> > > >> - How do we prioritize the tickets?
> > > >> - Who wants to provide patches?
> > > >> - Etc...
> > > >>
> > > >> Thanks in advance for your feedbacks,
> > > >>
> > > >> [1] -
> >
> http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
> > > >>
> > > >>
> > > >> On 15 February 2011 11:44, Eugen Paraschiv
> > <ha...@gmail.com> wrote:
> > > >>
> > > >> > Hi,
> > > >> > I have moved some of these issues to 0.0.2. I'm
> > tracking the final 3 and
> > > >> > making the necessary changes to get them committed
> > during the next few
> > > >> days
> > > >> > if possible. Than, perhaps we get to 0.0.2.
> > > >> > Eugen.
> > > >> >
> > > >> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil
> > <bc...@agimem.com>
> > > >> > wrote:
> > > >> >
> > > >> > > In fact, I can't reschedule the tickets I doesn't
> > own. May the issues
> > > >> > > owners
> > > >> > > reschedule the tickets they have from 0.0.1 to 0.0.2
> > or provide the
> > > >> > > necessary patches to include them in the release?
> > > >> > >
> > > >> > > I hadn't a deep look a DROIDS-106 but a working patch
> > has been
> > > >> provided
> > > >> > by
> > > >> > > Eugen. It introduce the usage of Guava. We may
> > include it in the
> > > >> release.
> > > >> > >
> > > >> > > The tickets to reschedule are the followings:
> > > >> > >
> > > >> > > *Eugen Paraschiv*
> > > >> > > DROIDS-89 > no patch
> > > >> > > DROIDS-112 > no patch
> > > >> > > DROIDS-113 > a patch is provided > tests are not
> > passing
> > > >> > > DROIDS-114 > Eugen Paraschiv > no patch
> > > >> > >
> > > >> > > *Oleg Kalnichevski *
> > > >> > > DROIDS-35 > > no patch
> > > >> > >
> > > >> > > Thanks in advance.
> > > >> > >
> > > >> > >
> > > >> > > On 8 February 2011 17:19, Chapuis Bertil
> > <bc...@agimem.com> wrote:
> > > >> > >
> > > >> > > > Reactivation of the release thread. :-)
> > > >> > > >
> > > >> > > > I can move the opened issues from 0.1 to 0.2. For
> > the other aspects
> > > >> of
> > > >> > > the
> > > >> > > > release, I'm not really familiar with the process.
> > > >> > > >
> > > >> > > > What has to be done ?
> > > >> > > >
> > > >> > > >
> > > >> > > > On 24 December 2010 06:56, Otis Gospodnetic <
> > > >> > otis_gospodnetic@yahoo.com
> > > >> > > >wrote:
> > > >> > > >
> > > >> > > >> Hi Salu & others:
> > > >> > > >>
> > > >> > > >> * Does anyone know what it takes to create a
> > release? Droids
> > > >> hasn't
> > > >> > > >> actually
> > > >> > > >> had any releases, has it?
> > > >> > > >>
> > > >> > > >> * Would anyone be interested in simply making A
> > release off of the
> > > >> > trunk
> > > >> > > >> now?
> > > >> > > >> I see no reason not to do that. It always helps
> > to have a
> > > >> release.
> > > >> > > Call
> > > >> > > >> it
> > > >> > > >> 0.1.
> > > >> > > >>
> > > >> > > >> * Should somebody with some level of understanding
> > of Droids move
> > > >> all
> > > >> > > >> appropriate Unscheduled issues to 0.0.1 version
> > (or 0.2 if somebody
> > > >> > can
> > > >> > > >> create
> > > >> > > >> 0.1 off trunk now), so anyone who can review
> > patches knows which
> > > >> > patches
> > > >> > > >> need to
> > > >> > > >> be reviewed first?
> > > >> > > >>
> > > >> > > >> Otis
> > > >> > > >> ----
> > > >> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene
> > - Nutch
> > > >> > > >> Lucene ecosystem search ::
> > http://search-lucene.com/
> > > >> > > >>
> > > >> > > >>
> > > >> > > > --
> > > >> > > > Bertil Chapuis
> > > >> > > > Agimem Sàrl
> > > >> > > > http://www.agimem.com
> > > >> > > >
> > > >> > > >
> > > >> > > --
> > > >> > > Bertil Chapuis
> > > >> > > Agimem Sàrl
> > > >> > > http://www.agimem.com
> > > >> > >
> > > >> >
> > > >>
> > > >> --
> > > >> Bertil Chapuis
> > > >> Agimem Sàrl
> > > >> http://www.agimem.com
> > > >>
> > > >
> > > >
> > >
> > >
> >
> > --
> >
> > Thorsten Scherler <thorsten.at.apache.org>
> > codeBusters S.L. - web based systems
> > <consulting, training and solutions>
> > http://www.codebusters.es/
> >
> >
> >
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Wed, 2011-02-23 at 13:45 +0100, Chapuis Bertil wrote:
> It seems that it is possible to perform a dry run:
>
> mvn release:prepare -DdryRun=true
>
> I can try but I hope it will have no direct effects on the repository.
Yeah I just did that but get an error.
[INFO] Missing:
[INFO] ----------
[INFO] 1)
com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:jar:1.13-SNAPSHOT
Looks quite weird however
[INFO] Path to dependency:
[INFO] 1)
org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-5-SNAPSHOT
[INFO] 2)
com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:jar:1.13-SNAPSHOT
seems to come from "buildnumber-maven-plugin"
salu2
>
>
>
> On 23 February 2011 13:21, Thorsten Scherler <sc...@gmail.com>
> wrote:
> On Wed, 2011-02-23 at 11:49 +0100, Chapuis Bertil wrote:
> > I had a look at the apache documentation page for releases
> [1]. The section
> > "Prepare your pom for release" says : Make sure there are no
> snapshots in
> > the POMs to be released. Does it means we have to change all
> the version
> > numbers in our pom files? I thought that the maven release
> plugin was asking
> > for the release number and making the changes automatically.
>
>
> I tied to use it ones in a client project but I can remember
> that I had
> to drop it since it did to much (including it tagged the scm
> rep). I am
> not sure whether we can make it staged to review the different
> steps.
>
> salu2
>
>
> >
> > [1] -
> http://www.apache.org/dev/publishing-maven-artifacts.html
> >
> >
> > On 21 February 2011 21:19, Eugen Paraschiv
> <ha...@gmail.com> wrote:
> >
> > > Hi,
> > > I've used maven-release-plugin before. It requires a few
> elements to be
> > > present in the pom and does indeed do all of the work for
> you. I will follow
> > > up with a quick guide from my own documentation about how
> to use it and what
> > > it needs.
> > > Eugen.
> > >
> > > On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil
> <bc...@agimem.com>wrote:
> > >
> > >> Hello all,
> > >>
> > >> The opened tickets for the release 0.0.1 are nearly all
> closed. As Otis
> > >> mentioned it, it may be a good idea to release.
> > >>
> > >> I had a look at the maven-release-plugin. It seems that
> mvn
> > >> release:prepare
> > >> [1] is doing most of the work. Since it looks quite
> magic, I wanted to
> > >> know
> > >> who already did that in the past with another
> project :-).
> > >>
> > >> At this step, several questions also occurs about how
> releases will be
> > >> managed.
> > >>
> > >> - Do we set a time scope for the next release?
> > >> - How do we prioritize the tickets?
> > >> - Who wants to provide patches?
> > >> - Etc...
> > >>
> > >> Thanks in advance for your feedbacks,
> > >>
> > >> [1] -
> http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
> > >>
> > >>
> > >> On 15 February 2011 11:44, Eugen Paraschiv
> <ha...@gmail.com> wrote:
> > >>
> > >> > Hi,
> > >> > I have moved some of these issues to 0.0.2. I'm
> tracking the final 3 and
> > >> > making the necessary changes to get them committed
> during the next few
> > >> days
> > >> > if possible. Than, perhaps we get to 0.0.2.
> > >> > Eugen.
> > >> >
> > >> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil
> <bc...@agimem.com>
> > >> > wrote:
> > >> >
> > >> > > In fact, I can't reschedule the tickets I doesn't
> own. May the issues
> > >> > > owners
> > >> > > reschedule the tickets they have from 0.0.1 to 0.0.2
> or provide the
> > >> > > necessary patches to include them in the release?
> > >> > >
> > >> > > I hadn't a deep look a DROIDS-106 but a working patch
> has been
> > >> provided
> > >> > by
> > >> > > Eugen. It introduce the usage of Guava. We may
> include it in the
> > >> release.
> > >> > >
> > >> > > The tickets to reschedule are the followings:
> > >> > >
> > >> > > *Eugen Paraschiv*
> > >> > > DROIDS-89 > no patch
> > >> > > DROIDS-112 > no patch
> > >> > > DROIDS-113 > a patch is provided > tests are not
> passing
> > >> > > DROIDS-114 > Eugen Paraschiv > no patch
> > >> > >
> > >> > > *Oleg Kalnichevski *
> > >> > > DROIDS-35 > > no patch
> > >> > >
> > >> > > Thanks in advance.
> > >> > >
> > >> > >
> > >> > > On 8 February 2011 17:19, Chapuis Bertil
> <bc...@agimem.com> wrote:
> > >> > >
> > >> > > > Reactivation of the release thread. :-)
> > >> > > >
> > >> > > > I can move the opened issues from 0.1 to 0.2. For
> the other aspects
> > >> of
> > >> > > the
> > >> > > > release, I'm not really familiar with the process.
> > >> > > >
> > >> > > > What has to be done ?
> > >> > > >
> > >> > > >
> > >> > > > On 24 December 2010 06:56, Otis Gospodnetic <
> > >> > otis_gospodnetic@yahoo.com
> > >> > > >wrote:
> > >> > > >
> > >> > > >> Hi Salu & others:
> > >> > > >>
> > >> > > >> * Does anyone know what it takes to create a
> release? Droids
> > >> hasn't
> > >> > > >> actually
> > >> > > >> had any releases, has it?
> > >> > > >>
> > >> > > >> * Would anyone be interested in simply making A
> release off of the
> > >> > trunk
> > >> > > >> now?
> > >> > > >> I see no reason not to do that. It always helps
> to have a
> > >> release.
> > >> > > Call
> > >> > > >> it
> > >> > > >> 0.1.
> > >> > > >>
> > >> > > >> * Should somebody with some level of understanding
> of Droids move
> > >> all
> > >> > > >> appropriate Unscheduled issues to 0.0.1 version
> (or 0.2 if somebody
> > >> > can
> > >> > > >> create
> > >> > > >> 0.1 off trunk now), so anyone who can review
> patches knows which
> > >> > patches
> > >> > > >> need to
> > >> > > >> be reviewed first?
> > >> > > >>
> > >> > > >> Otis
> > >> > > >> ----
> > >> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene
> - Nutch
> > >> > > >> Lucene ecosystem search ::
> http://search-lucene.com/
> > >> > > >>
> > >> > > >>
> > >> > > > --
> > >> > > > Bertil Chapuis
> > >> > > > Agimem Sàrl
> > >> > > > http://www.agimem.com
> > >> > > >
> > >> > > >
> > >> > > --
> > >> > > Bertil Chapuis
> > >> > > Agimem Sàrl
> > >> > > http://www.agimem.com
> > >> > >
> > >> >
> > >>
> > >> --
> > >> Bertil Chapuis
> > >> Agimem Sàrl
> > >> http://www.agimem.com
> > >>
> > >
> > >
> >
> >
>
> --
>
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
It seems that it is possible to perform a dry run:
mvn release:prepare -DdryRun=true
I can try but I hope it will have no direct effects on the repository.
On 23 February 2011 13:21, Thorsten Scherler <sc...@gmail.com> wrote:
> On Wed, 2011-02-23 at 11:49 +0100, Chapuis Bertil wrote:
> > I had a look at the apache documentation page for releases [1]. The
> section
> > "Prepare your pom for release" says : Make sure there are no snapshots in
> > the POMs to be released. Does it means we have to change all the version
> > numbers in our pom files? I thought that the maven release plugin was
> asking
> > for the release number and making the changes automatically.
>
> I tied to use it ones in a client project but I can remember that I had
> to drop it since it did to much (including it tagged the scm rep). I am
> not sure whether we can make it staged to review the different steps.
>
> salu2
>
> >
> > [1] - http://www.apache.org/dev/publishing-maven-artifacts.html
> >
> >
> > On 21 February 2011 21:19, Eugen Paraschiv <ha...@gmail.com>
> wrote:
> >
> > > Hi,
> > > I've used maven-release-plugin before. It requires a few elements to be
> > > present in the pom and does indeed do all of the work for you. I will
> follow
> > > up with a quick guide from my own documentation about how to use it and
> what
> > > it needs.
> > > Eugen.
> > >
> > > On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil <bchapuis@agimem.com
> >wrote:
> > >
> > >> Hello all,
> > >>
> > >> The opened tickets for the release 0.0.1 are nearly all closed. As
> Otis
> > >> mentioned it, it may be a good idea to release.
> > >>
> > >> I had a look at the maven-release-plugin. It seems that mvn
> > >> release:prepare
> > >> [1] is doing most of the work. Since it looks quite magic, I wanted to
> > >> know
> > >> who already did that in the past with another project :-).
> > >>
> > >> At this step, several questions also occurs about how releases will be
> > >> managed.
> > >>
> > >> - Do we set a time scope for the next release?
> > >> - How do we prioritize the tickets?
> > >> - Who wants to provide patches?
> > >> - Etc...
> > >>
> > >> Thanks in advance for your feedbacks,
> > >>
> > >> [1] -
> http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
> > >>
> > >>
> > >> On 15 February 2011 11:44, Eugen Paraschiv <ha...@gmail.com>
> wrote:
> > >>
> > >> > Hi,
> > >> > I have moved some of these issues to 0.0.2. I'm tracking the final 3
> and
> > >> > making the necessary changes to get them committed during the next
> few
> > >> days
> > >> > if possible. Than, perhaps we get to 0.0.2.
> > >> > Eugen.
> > >> >
> > >> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <
> bchapuis@agimem.com>
> > >> > wrote:
> > >> >
> > >> > > In fact, I can't reschedule the tickets I doesn't own. May the
> issues
> > >> > > owners
> > >> > > reschedule the tickets they have from 0.0.1 to 0.0.2 or provide
> the
> > >> > > necessary patches to include them in the release?
> > >> > >
> > >> > > I hadn't a deep look a DROIDS-106 but a working patch has been
> > >> provided
> > >> > by
> > >> > > Eugen. It introduce the usage of Guava. We may include it in the
> > >> release.
> > >> > >
> > >> > > The tickets to reschedule are the followings:
> > >> > >
> > >> > > *Eugen Paraschiv*
> > >> > > DROIDS-89 > no patch
> > >> > > DROIDS-112 > no patch
> > >> > > DROIDS-113 > a patch is provided > tests are not passing
> > >> > > DROIDS-114 > Eugen Paraschiv > no patch
> > >> > >
> > >> > > *Oleg Kalnichevski *
> > >> > > DROIDS-35 > > no patch
> > >> > >
> > >> > > Thanks in advance.
> > >> > >
> > >> > >
> > >> > > On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com>
> wrote:
> > >> > >
> > >> > > > Reactivation of the release thread. :-)
> > >> > > >
> > >> > > > I can move the opened issues from 0.1 to 0.2. For the other
> aspects
> > >> of
> > >> > > the
> > >> > > > release, I'm not really familiar with the process.
> > >> > > >
> > >> > > > What has to be done ?
> > >> > > >
> > >> > > >
> > >> > > > On 24 December 2010 06:56, Otis Gospodnetic <
> > >> > otis_gospodnetic@yahoo.com
> > >> > > >wrote:
> > >> > > >
> > >> > > >> Hi Salu & others:
> > >> > > >>
> > >> > > >> * Does anyone know what it takes to create a release? Droids
> > >> hasn't
> > >> > > >> actually
> > >> > > >> had any releases, has it?
> > >> > > >>
> > >> > > >> * Would anyone be interested in simply making A release off of
> the
> > >> > trunk
> > >> > > >> now?
> > >> > > >> I see no reason not to do that. It always helps to have a
> > >> release.
> > >> > > Call
> > >> > > >> it
> > >> > > >> 0.1.
> > >> > > >>
> > >> > > >> * Should somebody with some level of understanding of Droids
> move
> > >> all
> > >> > > >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if
> somebody
> > >> > can
> > >> > > >> create
> > >> > > >> 0.1 off trunk now), so anyone who can review patches knows
> which
> > >> > patches
> > >> > > >> need to
> > >> > > >> be reviewed first?
> > >> > > >>
> > >> > > >> Otis
> > >> > > >> ----
> > >> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > >> > > >> Lucene ecosystem search :: http://search-lucene.com/
> > >> > > >>
> > >> > > >>
> > >> > > > --
> > >> > > > Bertil Chapuis
> > >> > > > Agimem Sàrl
> > >> > > > http://www.agimem.com
> > >> > > >
> > >> > > >
> > >> > > --
> > >> > > Bertil Chapuis
> > >> > > Agimem Sàrl
> > >> > > http://www.agimem.com
> > >> > >
> > >> >
> > >>
> > >> --
> > >> Bertil Chapuis
> > >> Agimem Sàrl
> > >> http://www.agimem.com
> > >>
> > >
> > >
> >
> >
>
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Thorsten Scherler <sc...@gmail.com>.
On Wed, 2011-02-23 at 11:49 +0100, Chapuis Bertil wrote:
> I had a look at the apache documentation page for releases [1]. The section
> "Prepare your pom for release" says : Make sure there are no snapshots in
> the POMs to be released. Does it means we have to change all the version
> numbers in our pom files? I thought that the maven release plugin was asking
> for the release number and making the changes automatically.
I tied to use it ones in a client project but I can remember that I had
to drop it since it did to much (including it tagged the scm rep). I am
not sure whether we can make it staged to review the different steps.
salu2
>
> [1] - http://www.apache.org/dev/publishing-maven-artifacts.html
>
>
> On 21 February 2011 21:19, Eugen Paraschiv <ha...@gmail.com> wrote:
>
> > Hi,
> > I've used maven-release-plugin before. It requires a few elements to be
> > present in the pom and does indeed do all of the work for you. I will follow
> > up with a quick guide from my own documentation about how to use it and what
> > it needs.
> > Eugen.
> >
> > On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil <bc...@agimem.com>wrote:
> >
> >> Hello all,
> >>
> >> The opened tickets for the release 0.0.1 are nearly all closed. As Otis
> >> mentioned it, it may be a good idea to release.
> >>
> >> I had a look at the maven-release-plugin. It seems that mvn
> >> release:prepare
> >> [1] is doing most of the work. Since it looks quite magic, I wanted to
> >> know
> >> who already did that in the past with another project :-).
> >>
> >> At this step, several questions also occurs about how releases will be
> >> managed.
> >>
> >> - Do we set a time scope for the next release?
> >> - How do we prioritize the tickets?
> >> - Who wants to provide patches?
> >> - Etc...
> >>
> >> Thanks in advance for your feedbacks,
> >>
> >> [1] - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
> >>
> >>
> >> On 15 February 2011 11:44, Eugen Paraschiv <ha...@gmail.com> wrote:
> >>
> >> > Hi,
> >> > I have moved some of these issues to 0.0.2. I'm tracking the final 3 and
> >> > making the necessary changes to get them committed during the next few
> >> days
> >> > if possible. Than, perhaps we get to 0.0.2.
> >> > Eugen.
> >> >
> >> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <bc...@agimem.com>
> >> > wrote:
> >> >
> >> > > In fact, I can't reschedule the tickets I doesn't own. May the issues
> >> > > owners
> >> > > reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
> >> > > necessary patches to include them in the release?
> >> > >
> >> > > I hadn't a deep look a DROIDS-106 but a working patch has been
> >> provided
> >> > by
> >> > > Eugen. It introduce the usage of Guava. We may include it in the
> >> release.
> >> > >
> >> > > The tickets to reschedule are the followings:
> >> > >
> >> > > *Eugen Paraschiv*
> >> > > DROIDS-89 > no patch
> >> > > DROIDS-112 > no patch
> >> > > DROIDS-113 > a patch is provided > tests are not passing
> >> > > DROIDS-114 > Eugen Paraschiv > no patch
> >> > >
> >> > > *Oleg Kalnichevski *
> >> > > DROIDS-35 > > no patch
> >> > >
> >> > > Thanks in advance.
> >> > >
> >> > >
> >> > > On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
> >> > >
> >> > > > Reactivation of the release thread. :-)
> >> > > >
> >> > > > I can move the opened issues from 0.1 to 0.2. For the other aspects
> >> of
> >> > > the
> >> > > > release, I'm not really familiar with the process.
> >> > > >
> >> > > > What has to be done ?
> >> > > >
> >> > > >
> >> > > > On 24 December 2010 06:56, Otis Gospodnetic <
> >> > otis_gospodnetic@yahoo.com
> >> > > >wrote:
> >> > > >
> >> > > >> Hi Salu & others:
> >> > > >>
> >> > > >> * Does anyone know what it takes to create a release? Droids
> >> hasn't
> >> > > >> actually
> >> > > >> had any releases, has it?
> >> > > >>
> >> > > >> * Would anyone be interested in simply making A release off of the
> >> > trunk
> >> > > >> now?
> >> > > >> I see no reason not to do that. It always helps to have a
> >> release.
> >> > > Call
> >> > > >> it
> >> > > >> 0.1.
> >> > > >>
> >> > > >> * Should somebody with some level of understanding of Droids move
> >> all
> >> > > >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody
> >> > can
> >> > > >> create
> >> > > >> 0.1 off trunk now), so anyone who can review patches knows which
> >> > patches
> >> > > >> need to
> >> > > >> be reviewed first?
> >> > > >>
> >> > > >> Otis
> >> > > >> ----
> >> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> >> > > >> Lucene ecosystem search :: http://search-lucene.com/
> >> > > >>
> >> > > >>
> >> > > > --
> >> > > > Bertil Chapuis
> >> > > > Agimem Sàrl
> >> > > > http://www.agimem.com
> >> > > >
> >> > > >
> >> > > --
> >> > > Bertil Chapuis
> >> > > Agimem Sàrl
> >> > > http://www.agimem.com
> >> > >
> >> >
> >>
> >> --
> >> Bertil Chapuis
> >> Agimem Sàrl
> >> http://www.agimem.com
> >>
> >
> >
>
>
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
I had a look at the apache documentation page for releases [1]. The section
"Prepare your pom for release" says : Make sure there are no snapshots in
the POMs to be released. Does it means we have to change all the version
numbers in our pom files? I thought that the maven release plugin was asking
for the release number and making the changes automatically.
[1] - http://www.apache.org/dev/publishing-maven-artifacts.html
On 21 February 2011 21:19, Eugen Paraschiv <ha...@gmail.com> wrote:
> Hi,
> I've used maven-release-plugin before. It requires a few elements to be
> present in the pom and does indeed do all of the work for you. I will follow
> up with a quick guide from my own documentation about how to use it and what
> it needs.
> Eugen.
>
> On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil <bc...@agimem.com>wrote:
>
>> Hello all,
>>
>> The opened tickets for the release 0.0.1 are nearly all closed. As Otis
>> mentioned it, it may be a good idea to release.
>>
>> I had a look at the maven-release-plugin. It seems that mvn
>> release:prepare
>> [1] is doing most of the work. Since it looks quite magic, I wanted to
>> know
>> who already did that in the past with another project :-).
>>
>> At this step, several questions also occurs about how releases will be
>> managed.
>>
>> - Do we set a time scope for the next release?
>> - How do we prioritize the tickets?
>> - Who wants to provide patches?
>> - Etc...
>>
>> Thanks in advance for your feedbacks,
>>
>> [1] - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
>>
>>
>> On 15 February 2011 11:44, Eugen Paraschiv <ha...@gmail.com> wrote:
>>
>> > Hi,
>> > I have moved some of these issues to 0.0.2. I'm tracking the final 3 and
>> > making the necessary changes to get them committed during the next few
>> days
>> > if possible. Than, perhaps we get to 0.0.2.
>> > Eugen.
>> >
>> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <bc...@agimem.com>
>> > wrote:
>> >
>> > > In fact, I can't reschedule the tickets I doesn't own. May the issues
>> > > owners
>> > > reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
>> > > necessary patches to include them in the release?
>> > >
>> > > I hadn't a deep look a DROIDS-106 but a working patch has been
>> provided
>> > by
>> > > Eugen. It introduce the usage of Guava. We may include it in the
>> release.
>> > >
>> > > The tickets to reschedule are the followings:
>> > >
>> > > *Eugen Paraschiv*
>> > > DROIDS-89 > no patch
>> > > DROIDS-112 > no patch
>> > > DROIDS-113 > a patch is provided > tests are not passing
>> > > DROIDS-114 > Eugen Paraschiv > no patch
>> > >
>> > > *Oleg Kalnichevski *
>> > > DROIDS-35 > > no patch
>> > >
>> > > Thanks in advance.
>> > >
>> > >
>> > > On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
>> > >
>> > > > Reactivation of the release thread. :-)
>> > > >
>> > > > I can move the opened issues from 0.1 to 0.2. For the other aspects
>> of
>> > > the
>> > > > release, I'm not really familiar with the process.
>> > > >
>> > > > What has to be done ?
>> > > >
>> > > >
>> > > > On 24 December 2010 06:56, Otis Gospodnetic <
>> > otis_gospodnetic@yahoo.com
>> > > >wrote:
>> > > >
>> > > >> Hi Salu & others:
>> > > >>
>> > > >> * Does anyone know what it takes to create a release? Droids
>> hasn't
>> > > >> actually
>> > > >> had any releases, has it?
>> > > >>
>> > > >> * Would anyone be interested in simply making A release off of the
>> > trunk
>> > > >> now?
>> > > >> I see no reason not to do that. It always helps to have a
>> release.
>> > > Call
>> > > >> it
>> > > >> 0.1.
>> > > >>
>> > > >> * Should somebody with some level of understanding of Droids move
>> all
>> > > >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody
>> > can
>> > > >> create
>> > > >> 0.1 off trunk now), so anyone who can review patches knows which
>> > patches
>> > > >> need to
>> > > >> be reviewed first?
>> > > >>
>> > > >> Otis
>> > > >> ----
>> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
>> > > >> Lucene ecosystem search :: http://search-lucene.com/
>> > > >>
>> > > >>
>> > > > --
>> > > > Bertil Chapuis
>> > > > Agimem Sàrl
>> > > > http://www.agimem.com
>> > > >
>> > > >
>> > > --
>> > > Bertil Chapuis
>> > > Agimem Sàrl
>> > > http://www.agimem.com
>> > >
>> >
>>
>> --
>> Bertil Chapuis
>> Agimem Sàrl
>> http://www.agimem.com
>>
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Eugen Paraschiv <ha...@gmail.com>.
Hi,
I've used maven-release-plugin before. It requires a few elements to be
present in the pom and does indeed do all of the work for you. I will follow
up with a quick guide from my own documentation about how to use it and what
it needs.
Eugen.
On Mon, Feb 21, 2011 at 11:58 AM, Chapuis Bertil <bc...@agimem.com>wrote:
> Hello all,
>
> The opened tickets for the release 0.0.1 are nearly all closed. As Otis
> mentioned it, it may be a good idea to release.
>
> I had a look at the maven-release-plugin. It seems that mvn release:prepare
> [1] is doing most of the work. Since it looks quite magic, I wanted to know
> who already did that in the past with another project :-).
>
> At this step, several questions also occurs about how releases will be
> managed.
>
> - Do we set a time scope for the next release?
> - How do we prioritize the tickets?
> - Who wants to provide patches?
> - Etc...
>
> Thanks in advance for your feedbacks,
>
> [1] - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
>
>
> On 15 February 2011 11:44, Eugen Paraschiv <ha...@gmail.com> wrote:
>
> > Hi,
> > I have moved some of these issues to 0.0.2. I'm tracking the final 3 and
> > making the necessary changes to get them committed during the next few
> days
> > if possible. Than, perhaps we get to 0.0.2.
> > Eugen.
> >
> > On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <bc...@agimem.com>
> > wrote:
> >
> > > In fact, I can't reschedule the tickets I doesn't own. May the issues
> > > owners
> > > reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
> > > necessary patches to include them in the release?
> > >
> > > I hadn't a deep look a DROIDS-106 but a working patch has been provided
> > by
> > > Eugen. It introduce the usage of Guava. We may include it in the
> release.
> > >
> > > The tickets to reschedule are the followings:
> > >
> > > *Eugen Paraschiv*
> > > DROIDS-89 > no patch
> > > DROIDS-112 > no patch
> > > DROIDS-113 > a patch is provided > tests are not passing
> > > DROIDS-114 > Eugen Paraschiv > no patch
> > >
> > > *Oleg Kalnichevski *
> > > DROIDS-35 > > no patch
> > >
> > > Thanks in advance.
> > >
> > >
> > > On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
> > >
> > > > Reactivation of the release thread. :-)
> > > >
> > > > I can move the opened issues from 0.1 to 0.2. For the other aspects
> of
> > > the
> > > > release, I'm not really familiar with the process.
> > > >
> > > > What has to be done ?
> > > >
> > > >
> > > > On 24 December 2010 06:56, Otis Gospodnetic <
> > otis_gospodnetic@yahoo.com
> > > >wrote:
> > > >
> > > >> Hi Salu & others:
> > > >>
> > > >> * Does anyone know what it takes to create a release? Droids hasn't
> > > >> actually
> > > >> had any releases, has it?
> > > >>
> > > >> * Would anyone be interested in simply making A release off of the
> > trunk
> > > >> now?
> > > >> I see no reason not to do that. It always helps to have a release.
> > > Call
> > > >> it
> > > >> 0.1.
> > > >>
> > > >> * Should somebody with some level of understanding of Droids move
> all
> > > >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody
> > can
> > > >> create
> > > >> 0.1 off trunk now), so anyone who can review patches knows which
> > patches
> > > >> need to
> > > >> be reviewed first?
> > > >>
> > > >> Otis
> > > >> ----
> > > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > > >> Lucene ecosystem search :: http://search-lucene.com/
> > > >>
> > > >>
> > > > --
> > > > Bertil Chapuis
> > > > Agimem Sàrl
> > > > http://www.agimem.com
> > > >
> > > >
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> >
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
Hello all,
The opened tickets for the release 0.0.1 are nearly all closed. As Otis
mentioned it, it may be a good idea to release.
I had a look at the maven-release-plugin. It seems that mvn release:prepare
[1] is doing most of the work. Since it looks quite magic, I wanted to know
who already did that in the past with another project :-).
At this step, several questions also occurs about how releases will be
managed.
- Do we set a time scope for the next release?
- How do we prioritize the tickets?
- Who wants to provide patches?
- Etc...
Thanks in advance for your feedbacks,
[1] - http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
On 15 February 2011 11:44, Eugen Paraschiv <ha...@gmail.com> wrote:
> Hi,
> I have moved some of these issues to 0.0.2. I'm tracking the final 3 and
> making the necessary changes to get them committed during the next few days
> if possible. Than, perhaps we get to 0.0.2.
> Eugen.
>
> On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <bc...@agimem.com>
> wrote:
>
> > In fact, I can't reschedule the tickets I doesn't own. May the issues
> > owners
> > reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
> > necessary patches to include them in the release?
> >
> > I hadn't a deep look a DROIDS-106 but a working patch has been provided
> by
> > Eugen. It introduce the usage of Guava. We may include it in the release.
> >
> > The tickets to reschedule are the followings:
> >
> > *Eugen Paraschiv*
> > DROIDS-89 > no patch
> > DROIDS-112 > no patch
> > DROIDS-113 > a patch is provided > tests are not passing
> > DROIDS-114 > Eugen Paraschiv > no patch
> >
> > *Oleg Kalnichevski *
> > DROIDS-35 > > no patch
> >
> > Thanks in advance.
> >
> >
> > On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
> >
> > > Reactivation of the release thread. :-)
> > >
> > > I can move the opened issues from 0.1 to 0.2. For the other aspects of
> > the
> > > release, I'm not really familiar with the process.
> > >
> > > What has to be done ?
> > >
> > >
> > > On 24 December 2010 06:56, Otis Gospodnetic <
> otis_gospodnetic@yahoo.com
> > >wrote:
> > >
> > >> Hi Salu & others:
> > >>
> > >> * Does anyone know what it takes to create a release? Droids hasn't
> > >> actually
> > >> had any releases, has it?
> > >>
> > >> * Would anyone be interested in simply making A release off of the
> trunk
> > >> now?
> > >> I see no reason not to do that. It always helps to have a release.
> > Call
> > >> it
> > >> 0.1.
> > >>
> > >> * Should somebody with some level of understanding of Droids move all
> > >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody
> can
> > >> create
> > >> 0.1 off trunk now), so anyone who can review patches knows which
> patches
> > >> need to
> > >> be reviewed first?
> > >>
> > >> Otis
> > >> ----
> > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > >> Lucene ecosystem search :: http://search-lucene.com/
> > >>
> > >>
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> > >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com
Re: Droids 0.1 release
Posted by Eugen Paraschiv <ha...@gmail.com>.
Hi,
I have moved some of these issues to 0.0.2. I'm tracking the final 3 and
making the necessary changes to get them committed during the next few days
if possible. Than, perhaps we get to 0.0.2.
Eugen.
On Sat, Feb 12, 2011 at 4:46 AM, Chapuis Bertil <bc...@agimem.com> wrote:
> In fact, I can't reschedule the tickets I doesn't own. May the issues
> owners
> reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
> necessary patches to include them in the release?
>
> I hadn't a deep look a DROIDS-106 but a working patch has been provided by
> Eugen. It introduce the usage of Guava. We may include it in the release.
>
> The tickets to reschedule are the followings:
>
> *Eugen Paraschiv*
> DROIDS-89 > no patch
> DROIDS-112 > no patch
> DROIDS-113 > a patch is provided > tests are not passing
> DROIDS-114 > Eugen Paraschiv > no patch
>
> *Oleg Kalnichevski *
> DROIDS-35 > > no patch
>
> Thanks in advance.
>
>
> On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
>
> > Reactivation of the release thread. :-)
> >
> > I can move the opened issues from 0.1 to 0.2. For the other aspects of
> the
> > release, I'm not really familiar with the process.
> >
> > What has to be done ?
> >
> >
> > On 24 December 2010 06:56, Otis Gospodnetic <otis_gospodnetic@yahoo.com
> >wrote:
> >
> >> Hi Salu & others:
> >>
> >> * Does anyone know what it takes to create a release? Droids hasn't
> >> actually
> >> had any releases, has it?
> >>
> >> * Would anyone be interested in simply making A release off of the trunk
> >> now?
> >> I see no reason not to do that. It always helps to have a release.
> Call
> >> it
> >> 0.1.
> >>
> >> * Should somebody with some level of understanding of Droids move all
> >> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody can
> >> create
> >> 0.1 off trunk now), so anyone who can review patches knows which patches
> >> need to
> >> be reviewed first?
> >>
> >> Otis
> >> ----
> >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> >> Lucene ecosystem search :: http://search-lucene.com/
> >>
> >>
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
> >
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
Re: Droids 0.1 release
Posted by Chapuis Bertil <bc...@agimem.com>.
In fact, I can't reschedule the tickets I doesn't own. May the issues owners
reschedule the tickets they have from 0.0.1 to 0.0.2 or provide the
necessary patches to include them in the release?
I hadn't a deep look a DROIDS-106 but a working patch has been provided by
Eugen. It introduce the usage of Guava. We may include it in the release.
The tickets to reschedule are the followings:
*Eugen Paraschiv*
DROIDS-89 > no patch
DROIDS-112 > no patch
DROIDS-113 > a patch is provided > tests are not passing
DROIDS-114 > Eugen Paraschiv > no patch
*Oleg Kalnichevski *
DROIDS-35 > > no patch
Thanks in advance.
On 8 February 2011 17:19, Chapuis Bertil <bc...@agimem.com> wrote:
> Reactivation of the release thread. :-)
>
> I can move the opened issues from 0.1 to 0.2. For the other aspects of the
> release, I'm not really familiar with the process.
>
> What has to be done ?
>
>
> On 24 December 2010 06:56, Otis Gospodnetic <ot...@yahoo.com>wrote:
>
>> Hi Salu & others:
>>
>> * Does anyone know what it takes to create a release? Droids hasn't
>> actually
>> had any releases, has it?
>>
>> * Would anyone be interested in simply making A release off of the trunk
>> now?
>> I see no reason not to do that. It always helps to have a release. Call
>> it
>> 0.1.
>>
>> * Should somebody with some level of understanding of Droids move all
>> appropriate Unscheduled issues to 0.0.1 version (or 0.2 if somebody can
>> create
>> 0.1 off trunk now), so anyone who can review patches knows which patches
>> need to
>> be reviewed first?
>>
>> Otis
>> ----
>> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
>> Lucene ecosystem search :: http://search-lucene.com/
>>
>>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com