You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Ioan Eugen Stan <st...@gmail.com> on 2014/09/01 12:15:44 UTC
[discussion] the state of James Project svn module
Hello,
I've been looking at the James code base lately and I noticed we have
James Project in SVN but no corresponding JIRA project to log issues.
I have two solutions for this problem:
1. create a JIRA project for it
2. remove James Project in favor of per project parent pom's.
I'm in favor of option 2 because James Project doesn't quite require
the status of a project - since it doesn't do a lot and we can better
maintain per project parent pom's.
I suggest we move all information from James Project to James Server
and other components. From a fast analysis, James Project duplicates a
lot of information from org.apache:apache parent pom so we can inherit
from that + add the changes specific to each project.
It will create some duplicate information but I think we can live with that.
Wdyt?
--
Ioan Eugen Stan
0720 898 747
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [discussion] the state of James Project svn module
Posted by Ioan Eugen Stan <st...@gmail.com>.
I will check next week. I am traveling ATM.
Ioan Eugen Stan
Pe 01.09.2014 20:58, "Eric Charles" <er...@apache.org> a scris:
> We have some web pages in james-project.
>
> http://svn.apache.org/repos/asf/james/project/trunk/src/site
>
> Can you check for option 2 that the site can still be generated and
> deployed?
>
>
>
> On 09/01/2014 12:15 PM, Ioan Eugen Stan wrote:
> > Hello,
> >
> > I've been looking at the James code base lately and I noticed we have
> > James Project in SVN but no corresponding JIRA project to log issues.
> >
> > I have two solutions for this problem:
> >
> > 1. create a JIRA project for it
> > 2. remove James Project in favor of per project parent pom's.
> >
> > I'm in favor of option 2 because James Project doesn't quite require
> > the status of a project - since it doesn't do a lot and we can better
> > maintain per project parent pom's.
> >
> > I suggest we move all information from James Project to James Server
> > and other components. From a fast analysis, James Project duplicates a
> > lot of information from org.apache:apache parent pom so we can inherit
> > from that + add the changes specific to each project.
> >
> > It will create some duplicate information but I think we can live with
> that.
> >
> > Wdyt?
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
Re: [discussion] the state of James Project svn module
Posted by Eric Charles <er...@apache.org>.
We have some web pages in james-project.
http://svn.apache.org/repos/asf/james/project/trunk/src/site
Can you check for option 2 that the site can still be generated and
deployed?
On 09/01/2014 12:15 PM, Ioan Eugen Stan wrote:
> Hello,
>
> I've been looking at the James code base lately and I noticed we have
> James Project in SVN but no corresponding JIRA project to log issues.
>
> I have two solutions for this problem:
>
> 1. create a JIRA project for it
> 2. remove James Project in favor of per project parent pom's.
>
> I'm in favor of option 2 because James Project doesn't quite require
> the status of a project - since it doesn't do a lot and we can better
> maintain per project parent pom's.
>
> I suggest we move all information from James Project to James Server
> and other components. From a fast analysis, James Project duplicates a
> lot of information from org.apache:apache parent pom so we can inherit
> from that + add the changes specific to each project.
>
> It will create some duplicate information but I think we can live with that.
>
> Wdyt?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org