Re: svn commit: r633704 - in /continuum/branches/continuum-1.x: ./ continuum-api/ continuum-commons/ continuum-configuration/ continuum-core-it/ continuum-core/ continuum-data-management/ continuum-da
2008/3/5, Brett Porter <[EMAIL PROTECTED]>:
>
> On 05/03/2008, at 10:28 AM, [EMAIL PROTECTED] wrote:
>
> > use new continuum parent
> > change groupId to org.apache.continuum (continuun is now TLP :-) )
>
> Will this be merged to trunk too?
Yep
>
> >
> >
> >
> > -
> > org.apache.maven.continuum.management.DataManagementCli > mainClass>
> > +
> > org.apache.continuum.management.DataManagementCli > mainClass>
> >
> >
> >
> ...
> >
> >
> >
> >
> > - org.apache.maven.continuum
> > + org.apache.continuum
> > continuum-xmlrpc-client
> > ${project.version}
> >
> > @@ -60,7 +60,7 @@
> >
> > -classpath
> >
> > -
> > org.apache.maven.continuum.xmlrpc.backup.Backup
> > +org.apache.continuum.xmlrpc.backup.Backup > argument>
> > -h
> >
> >
> > @@ -73,7 +73,7 @@
> > src/assembly/app.xml
> >
> >
> > -
> > org.apache.maven.continuum.xmlrpc.backup.Backup
> > + org.apache.continuum.xmlrpc.backup.Backup > mainClass>
> >
> >
> >
> >
> ...
> >
> >
> > -
> > org.apache.maven.continuum.xmlrpc.client.SampleClient > argument>
> > +
> > org.apache.continuum.xmlrpc.client.SampleClient
> >
> >
> >
> >
> ...
> >
> >
> >
> > -
> > <
> > role
> > >org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcComponent > role>
> > +
> > org.apache.continuum.xmlrpc.server.ContinuumXmlRpcComponent > role>
> > per-lookup > strategy>
> >
> >
> >
>
> These all look to be in error because they refer to packages (not yet
> migrated).
>
Yep good catch error
> - Brett
>
>
> --
> Brett Porter
> [EMAIL PROTECTED]
> http://blogs.exist.com/bporter/
>
>
Re: svn commit: r633704 - in /continuum/branches/continuum-1.x: ./ continuum-api/ continuum-commons/ continuum-configuration/ continuum-core-it/ continuum-core/ continuum-data-management/ continuum-da
On 05/03/2008, at 10:28 AM, [EMAIL PROTECTED] wrote:
use new continuum parent
change groupId to org.apache.continuum (continuun is now TLP :-) )
Will this be merged to trunk too?
-
org.apache.maven.continuum.management.DataManagementClimainClass>
+
org.apache.continuum.management.DataManagementClimainClass>
...
- org.apache.maven.continuum
+ org.apache.continuum
continuum-xmlrpc-client
${project.version}
@@ -60,7 +60,7 @@
-classpath
-
org.apache.maven.continuum.xmlrpc.backup.Backup
+org.apache.continuum.xmlrpc.backup.Backupargument>
-h
@@ -73,7 +73,7 @@
src/assembly/app.xml
-
org.apache.maven.continuum.xmlrpc.backup.Backup
+ org.apache.continuum.xmlrpc.backup.BackupmainClass>
...
-
org.apache.maven.continuum.xmlrpc.client.SampleClientargument>
+
org.apache.continuum.xmlrpc.client.SampleClient
...
-
<
role
>org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcComponentrole>
+
org.apache.continuum.xmlrpc.server.ContinuumXmlRpcComponentrole>
per-lookupstrategy>
These all look to be in error because they refer to packages (not yet
migrated).
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
Re: Confused about the branches
On 05/03/2008, at 5:18 AM, Olivier Lamy wrote: 2008/3/4, Brett Porter <[EMAIL PROTECTED]>: On 04/03/2008, at 10:47 AM, Olivier Lamy wrote: Agree on this. Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which prevent using xml-rpc :-(. Cool - shall we just start using the 1.2 bucket in JIRA? There are only 14 issues there now so maybe we could keep that to 20-30 issues all together and release it. +1 ok, I'll get my stuff in there I found these changes on trunk that are not on the branch: r617400. (The rest is documentation) I found these changes on the branch that are not on trunk: r627196, r620613, r620612, r620611 I think we should just merge all those from the branch to trunk, set it as v1.2, and close the branch for now? +1. (Perso, I don't really like the idea of starting a parrallel branch/trunk "a la" mvn 2.1 :-) ) I'll merge the changes to trunk - but will wait to hear other's opinions on this too before changing the branch If no objections, I will change root pom to not have anymore maven pom as parent. Sounds good - do you think we should have a Continuum parent POM like we do for Archiva? https://svn.apache.org/repos/asf/continuum/parent/trunk ? A new pom without parent ? (I can certainly copy some contents from the maven parent pom) With an ASF parent instead of the Maven one, yep. Question : do we have to change the groupId in the poms : org.apache.maven.continuum -> org.apache.continuum ( java package too ? looks a big bang) I don't see any downside to doing this :) - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Confused about the branches
2008/3/4, Brett Porter <[EMAIL PROTECTED]>: > > On 04/03/2008, at 10:47 AM, Olivier Lamy wrote: > > > Agree on this. > > Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which > > prevent using xml-rpc :-(. > > > Cool - shall we just start using the 1.2 bucket in JIRA? There are > only 14 issues there now so maybe we could keep that to 20-30 issues > all together and release it. +1 > > I found these changes on trunk that are not on the branch: r617400. > (The rest is documentation) > > I found these changes on the branch that are not on trunk: r627196, > r620613, r620612, r620611 > > I think we should just merge all those from the branch to trunk, set > it as v1.2, and close the branch for now? +1. (Perso, I don't really like the idea of starting a parrallel branch/trunk "a la" mvn 2.1 :-) ) > > > > If no objections, I will change root pom to not have anymore maven pom > > as parent. > > > Sounds good - do you think we should have a Continuum parent POM like > we do for Archiva? https://svn.apache.org/repos/asf/continuum/parent/trunk ? A new pom without parent ? (I can certainly copy some contents from the maven parent pom) Question : do we have to change the groupId in the poms : org.apache.maven.continuum -> org.apache.continuum ( java package too ? looks a big bang) > > Cheers, > > Brett > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Re: Account locked
all accounts lock to prevent raw dictionary attacks, and you can unlock by restarting the server, then all admin accounts unlock jesse On Tue, Mar 4, 2008 at 7:07 AM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Hi all, > > After trying to log into our continuum v1.1 instance as an admin, > continuum is telling us: > > Account Locked > Project Groups list is empty. > > Why would the admin account ever be locked, and how does one unlock it? > > Regards, > Graham > -- > -- jesse mcconnell [EMAIL PROTECTED]
Account locked
Hi all, After trying to log into our continuum v1.1 instance as an admin, continuum is telling us: Account Locked Project Groups list is empty. Why would the admin account ever be locked, and how does one unlock it? Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
