Nabble - Continuum - Dev (old)

SVN url

2008-03-12T00:04:01Z

Hi all,

Wat's the good one ?

thxs

Re: Confused about the branches

2008-03-11T16:49:17Z

On Sun, Mar 9, 2008 at 3:27 PM, Olivier Lamy <olamy@...> wrote:

> It looks we don't have any objections/opinions.
> All changes from branch has been merged.
> I will rename the version in the trunk to 1.2 (tomorow).

...and delete the continuum-1.x branch?

--
Wendy

Re: Confused about the branches

2008-03-10T16:08:59Z

The branches have been removed except for 'continuum-site_1.1' which had
some updates a few months ago. If this is not required please feel free
to remove.

Rahul

Olivier Lamy wrote:

> IMHO, we can remove.
>
> 2008/3/10, Rahul Thakur<rahul.thakur.xdev@...>:
>> There are some other branches residing in Continuum SVN. Should we
>> remove any (or all) of the following if they are not in active
>> development? I know (id-refactor and key-based-refactor can go)
>>
>> # continuum-acegi
>> # continuum-site_1.1
>> # gbuild
>> # id-refactor
>> # key-based-refactor
>> # osworkflow-integration
>> # release-integration
>>
>> Cheers,
>> Rahul
>>
>>
>> Brett Porter wrote:
>> > Hi,
>> >
>> > I'm a bit confused about the current branch scenarios, we have 1.2 on a
>> > branch and 2.0 on trunk. Several changes have been made on each, and
>> > none merged to the other.
>> >
>> > Can I suggest we merge all branch changes to trunk, rename trunk to
>> > 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use
>> > that for bugfixes only?
>> >
>> > WDYT?
>>
>> > - Brett
>> >
>> > --
>> > Brett Porter
>> > brett@...
>> > http://blogs.exist.com/bporter/
>> >
>> >
>>
>

Re: svn commit: r635719 - in /continuum/trunk: ./ continuum-api/ continuum-commons/ continuum-configuration/ continuum-core/ continuum-data-management/ continuum-data-management/continuum-legacy/ continuum-data-management/data-management-api/ continuum-dat...

2008-03-10T15:08:22Z

On 11/03/2008, at 9:05 AM, olamy@... wrote:

> - <value>${JAVA_HOME}</value>
> + <value>${java.homr}</value>

java.home?

>
> - <value>${M2_HOME}</value>
> + <value>${m2.home}</value>

maven.home?

:)

- Brett
--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: Confused about the branches

2008-03-10T03:56:11Z

IMHO, we can remove.

2008/3/10, Rahul Thakur <rahul.thakur.xdev@...>:

>
> There are some other branches residing in Continuum SVN. Should we
> remove any (or all) of the following if they are not in active
> development? I know (id-refactor and key-based-refactor can go)
>
> # continuum-acegi
> # continuum-site_1.1
> # gbuild
> # id-refactor
> # key-based-refactor
> # osworkflow-integration
> # release-integration
>
> Cheers,
> Rahul
>
>
> Brett Porter wrote:
> > Hi,
> >
> > I'm a bit confused about the current branch scenarios, we have 1.2 on a
> > branch and 2.0 on trunk. Several changes have been made on each, and
> > none merged to the other.
> >
> > Can I suggest we merge all branch changes to trunk, rename trunk to
> > 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use
> > that for bugfixes only?
> >
> > WDYT?
>
> >
> > - Brett
> >
> > --
> > Brett Porter
> > brett@...
> > http://blogs.exist.com/bporter/
> >
> >
>

Re: Confused about the branches

2008-03-09T20:17:04Z

There are some other branches residing in Continuum SVN. Should we
remove any (or all) of the following if they are not in active
development? I know (id-refactor and key-based-refactor can go)

# continuum-acegi
# continuum-site_1.1
# gbuild
# id-refactor
# key-based-refactor
# osworkflow-integration
# release-integration

Cheers,
Rahul

Brett Porter wrote:

> Hi,
>
> I'm a bit confused about the current branch scenarios, we have 1.2 on a
> branch and 2.0 on trunk. Several changes have been made on each, and
> none merged to the other.
>
> Can I suggest we merge all branch changes to trunk, rename trunk to
> 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use
> that for bugfixes only?
>
> WDYT?
>
> - Brett
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

Re: Confused about the branches

2008-03-09T15:27:36Z

2008/3/4, Brett Porter <brett@...>:

>
> On 05/03/2008, at 5:18 AM, Olivier Lamy wrote:
>
> > 2008/3/4, Brett Porter <brett@...>:
> >>
> >> 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

It looks we don't have any objections/opinions.
All changes from branch has been merged.
I will rename the version in the trunk to 1.2 (tomorow).

>
>
> >
> >
> >>
> >>
> >>> 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
> brett@...
> http://blogs.exist.com/bporter/
>
>

Re: VMBuild needs volunteers

2008-03-09T15:24:00Z

On Sun, Mar 9, 2008 at 3:17 PM, Olivier Lamy <olamy@...> wrote:
> Hi,
> If I can help I will (propably not a 24/7 support :-) ).

None of us is, but if we spread it around, it works. :)

Brett, what's the next step? Can you add an account on vmbuild for
Olivier, and add him to the Nagios list? (Or can I?)

> > One thing we really need to do is upgrade it to the latest version.
> > I'm hesitant to take that on alone, but maybe someone else is braver
> > than I, or 2-3 people might collaborate to get it done and documented.
> >
> Sure won't be so easy (is all the build history important ?)

Probably. It will be a good test of the data migration tools!

> Ok but where ? (something like
> https://svn.apache.org/repos/asf/vmbuild or
> https://svn.apache.org/repos/asf/continuum/vmbuild).
> Using a site write with the maven format (apt xdoc) ?

No, just plain text. It might take special access to infra svn, too.
I've still got this on my list for now.

--
Wendy

Re: VMBuild needs volunteers

2008-03-09T15:17:24Z

Hi,
If I can help I will (propably not a 24/7 support :-) ).

2008/3/8, Wendy Smoak <wsmoak@...>:

> We have a Continuum instance available for ASF projects to use:
> http://vmbuild.apache.org/continuum/groupSummary.action
>
> This is our (internal) public face, and it would be great to have more
> volunteers keeping an eye on it!
>
> It was down this morning, so I re-started it (at 11AM MST.) I didn't
> investigate why it was unhappy.
>
> One thing we really need to do is upgrade it to the latest version.
> I'm hesitant to take that on alone, but maybe someone else is braver
> than I, or 2-3 people might collaborate to get it done and documented.
>

Sure won't be so easy (is all the build history important ?)

> And there are 11 open issues:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10410&component=12311662&resolution=-1&sorter/field=priority&sorter/order=DESC
>
> There is some documentation here:
> http://cwiki.apache.org/confluence/display/vmbuild/Home
> (This needs to be moved into svn to better conform with other infra
> documentation, something that's been on my list for a while now...)

Ok but where ? (something like
https://svn.apache.org/repos/asf/vmbuild or
https://svn.apache.org/repos/asf/continuum/vmbuild).
Using a site write with the maven format (apt xdoc) ?

>
> --
>
> Wendy
>

Re: Trouble building maven-plugins parent pom in Continuum

2008-03-09T15:14:49Z

512 should be - the error Wendy got was going over 255.

On 10/03/2008, at 9:08 AM, Olivier Lamy wrote:

> Hi,
> Currently the max size for this field is 512.
>
> ....
> <class>
> <name>ChangeFile</name>
> <packageName>org.apache.maven.continuum.model.scm</packageName>
> <version>1.0.9+</version>
> <fields>
> <field>
> <name stash.maxSize="512">name</name>
> <version>1.0.9+</version>
> <type>String</type>
> </field>
> ....
>
>
> Which doens't look enough.
> 1024 ?
>
> --
> Olivier
>
> 2008/3/9, Brett Porter <brett@...>:
>> I think Continuum needs to allow longer values in here - it certainly
>> should not error out.
>>
>>
>> On 10/03/2008, at 7:13 AM, Wendy Smoak wrote:
>>
>>> On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter <brett@...>
>>> wrote:
>>>> Even though it uses --non-recursive to build, the checkout does not
>>>> exclude any subdirectories. This would occur in the checkout/update
>>>> and building changesets.
>>>
>>> Is a build error and "Please correct your data!" the right response
>>> here, or can Continuum do something useful like truncate the data
>>> and
>>> keep going?
>>>
>>> --
>>> Wendy
>>
>>
>> --
>>
>> Brett Porter
>> brett@...
>>
>> http://blogs.exist.com/bporter/
>>
>>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: Trouble building maven-plugins parent pom in Continuum

2008-03-09T15:08:38Z

Hi,
Currently the max size for this field is 512.

....
<class>
<name>ChangeFile</name>
<packageName>org.apache.maven.continuum.model.scm</packageName>
<version>1.0.9+</version>
<fields>
<field>
<name stash.maxSize="512">name</name>
<version>1.0.9+</version>
<type>String</type>
</field>
....

Which doens't look enough.
1024 ?

--
Olivier

2008/3/9, Brett Porter <brett@...>:

> I think Continuum needs to allow longer values in here - it certainly
> should not error out.
>
>
> On 10/03/2008, at 7:13 AM, Wendy Smoak wrote:
>
> > On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter <brett@...>
> > wrote:
> >> Even though it uses --non-recursive to build, the checkout does not
> >> exclude any subdirectories. This would occur in the checkout/update
> >> and building changesets.
> >
> > Is a build error and "Please correct your data!" the right response
> > here, or can Continuum do something useful like truncate the data and
> > keep going?
> >
> > --
> > Wendy
>
>
> --
>
> Brett Porter
> brett@...
>
> http://blogs.exist.com/bporter/
>
>

Re: Trouble building maven-plugins parent pom in Continuum

2008-03-09T13:21:16Z

I think Continuum needs to allow longer values in here - it certainly
should not error out.

On 10/03/2008, at 7:13 AM, Wendy Smoak wrote:

> On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter <brett@...>
> wrote:
>> Even though it uses --non-recursive to build, the checkout does not
>> exclude any subdirectories. This would occur in the checkout/update
>> and building changesets.
>
> Is a build error and "Please correct your data!" the right response
> here, or can Continuum do something useful like truncate the data and
> keep going?
>
> --
> Wendy

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: Trouble building maven-plugins parent pom in Continuum

2008-03-09T13:13:13Z

On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter <brett@...> wrote:
> Even though it uses --non-recursive to build, the checkout does not
> exclude any subdirectories. This would occur in the checkout/update
> and building changesets.

Is a build error and "Please correct your data!" the right response
here, or can Continuum do something useful like truncate the data and
keep going?

--
Wendy

Re: Trouble building maven-plugins parent pom in Continuum

2008-03-09T12:48:44Z

Even though it uses --non-recursive to build, the checkout does not
exclude any subdirectories. This would occur in the checkout/update
and building changesets.

On 10/03/2008, at 4:08 AM, Wendy Smoak wrote:

> I added maven/plugins/trunk/pom.xml to Continuum 1.1 and forced a
> build of the maven-plugins parent pom. (This is my own instance, not
> vmbuild or the maven zone.)
>
> It's using the default --non-recursive build definition, so I don't
> understand this error:
>
> INFO | jvm 1 | 2008/03/09 09:55:55 |
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
> javax.jdo.JDOFatalUserException: Attempt to store value
> "/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/
> resolving-conflicts-using-the-dependency-tree.apt
> (from /maven/plugins/branches/maven-dependency-plugin-MDEP-100/src/
> site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt:
> 591694)"
> in column ""NAME"" that has maximum length of 255. Please correct your
> data!
>
> The full stack trace from the logs is here:
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?Continuum/MavenPluginsError
>
> Any ideas?
>
> --
> Wendy

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Trouble building maven-plugins parent pom in Continuum

2008-03-09T10:08:56Z

I added maven/plugins/trunk/pom.xml to Continuum 1.1 and forced a
build of the maven-plugins parent pom. (This is my own instance, not
vmbuild or the maven zone.)

It's using the default --non-recursive build definition, so I don't
understand this error:

INFO | jvm 1 | 2008/03/09 09:55:55 |
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
javax.jdo.JDOFatalUserException: Attempt to store value
"/maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
(from /maven/plugins/branches/maven-dependency-plugin-MDEP-100/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt:591694)"
in column ""NAME"" that has maximum length of 255. Please correct your
data!

The full stack trace from the logs is here:
http://wiki.wsmoak.net/cgi-bin/wiki.pl?Continuum/MavenPluginsError

Any ideas?

--
Wendy

VMBuild needs volunteers

2008-03-08T10:17:07Z

We have a Continuum instance available for ASF projects to use:
http://vmbuild.apache.org/continuum/groupSummary.action

This is our (internal) public face, and it would be great to have more
volunteers keeping an eye on it!

It was down this morning, so I re-started it (at 11AM MST.) I didn't
investigate why it was unhappy.

One thing we really need to do is upgrade it to the latest version.
I'm hesitant to take that on alone, but maybe someone else is braver
than I, or 2-3 people might collaborate to get it done and documented.

And there are 11 open issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10410&component=12311662&resolution=-1&sorter/field=priority&sorter/order=DESC

There is some documentation here:
http://cwiki.apache.org/confluence/display/vmbuild/Home
(This needs to be moved into svn to better conform with other infra
documentation, something that's been on my list for a while now...)

--
Wendy

Re: Build Error against trunk - First Build

2008-03-07T12:19:48Z

Thanks all. I added the repository in pom and it started working fine, but
seems to be stuck in the package phase (jar:jar) at:

*[WARNING] DEPRECATED [descriptor]: Please use descriptors instead
[INFO] [assembly:single {execution: default}]
[INFO] Building tar : ...\workspace\Continuum1\continuum-ple
xus-runtime\target\apache-continuum-2.0-SNAPSHOT-bin.tar.gz
[INFO] Building tar : ...\workspace\Continuum1\continuum-ple
xus-runtime\target\apache-continuum-2.0-SNAPSHOT-bin.tar.bz2

*BTW, I did a mvn -Dmaven.test.skip clean install.*
*
Also, Can we change the svn URL in this page -
http://maven.apache.org/continuum/source-repository.html - to the right one
please? It took me a while to find the right one.

Thanks.
Murali

On Fri, Mar 7, 2008 at 5:53 PM, Olivier Lamy <olamy@...> wrote:

> Oops.
> I have fixed that in the branch but not in the trunk. (my bad !!).
>
> The parent pom is deployed in the apache snapshot repo.
> You can fix that by adding the following repo in your settings.
>
> 
> <repository>
> <id>people.apache.org</id>
> <name>Apache Snapshot Development Repository</name>
> <url>http://people.apache.org/repo/m2-snapshot-repository</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> </repository>
>
> Again sorry I will fix that.
>
> --
> Olivier
>
> 2008/3/7, Wendy Smoak <wsmoak@...>:
> > On Fri, Mar 7, 2008 at 10:13 AM, murali mohan <muralihere@...>
> wrote:
> >
> > > Downloaded the source from svn trunk. Trying to compile, but get this
> error
> > > - *
> > >
> > > org.apache.maven.reactor.MavenExecutionException: Cannot find
> parent:
> > > org.apache
> > > .continuum:continuum-parent for project:
> > > org.apache.continuum:continuum:pom:2.0-
> > > SNAPSHOT for project
> org.apache.continuum:continuum:pom:2.0-SNAPSHOT*
> >
> > Sorry about that, we're still under construction during the move to a
> > top-level project.
> >
> > I suspect it's this one:
> > http://svn.apache.org/repos/asf/continuum/parent/trunk/
> >
> > Try checking that out and building it locally, then building Continuum
> again.
> >
> > --
> >
> > Wendy
> >
>

Re: Build Error against trunk - First Build

2008-03-07T09:53:43Z

Oops.
I have fixed that in the branch but not in the trunk. (my bad !!).

The parent pom is deployed in the apache snapshot repo.
You can fix that by adding the following repo in your settings.


<repository>
<id>people.apache.org</id>
<name>Apache Snapshot Development Repository</name>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<releases>
<enabled>false</enabled>
</releases>
</repository>

Again sorry I will fix that.

--
Olivier

2008/3/7, Wendy Smoak <wsmoak@...>:

> On Fri, Mar 7, 2008 at 10:13 AM, murali mohan <muralihere@...> wrote:
>
> > Downloaded the source from svn trunk. Trying to compile, but get this error
> > - *
> >
> > org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> > org.apache
> > .continuum:continuum-parent for project:
> > org.apache.continuum:continuum:pom:2.0-
> > SNAPSHOT for project org.apache.continuum:continuum:pom:2.0-SNAPSHOT*
>
> Sorry about that, we're still under construction during the move to a
> top-level project.
>
> I suspect it's this one:
> http://svn.apache.org/repos/asf/continuum/parent/trunk/
>
> Try checking that out and building it locally, then building Continuum again.
>
> --
>
> Wendy
>

Re: Build Error against trunk - First Build

2008-03-07T09:31:33Z

On Fri, Mar 7, 2008 at 10:13 AM, murali mohan <muralihere@...> wrote:

> Downloaded the source from svn trunk. Trying to compile, but get this error
> - *
>
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.apache
> .continuum:continuum-parent for project:
> org.apache.continuum:continuum:pom:2.0-
> SNAPSHOT for project org.apache.continuum:continuum:pom:2.0-SNAPSHOT*

Sorry about that, we're still under construction during the move to a
top-level project.

I suspect it's this one:
http://svn.apache.org/repos/asf/continuum/parent/trunk/

Try checking that out and building it locally, then building Continuum again.

--
Wendy

Build Error against trunk - First Build

2008-03-07T09:13:54Z

Downloaded the source from svn trunk. Trying to compile, but get this error
- *

org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.apache
.continuum:continuum-parent for project:
org.apache.continuum:continuum:pom:2.0-
SNAPSHOT for project org.apache.continuum:continuum:pom:2.0-SNAPSHOT*

I tried looking at the 3 repositories mentioned in the POM, but could not
locate anything for org.apache.continuum groupId. Pls help.

Murali.

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-data-management/continuum-legacy/ continuum-data-man

2008-03-04T15:40:47Z

2008/3/5, Brett Porter <brett@...>:
>
> On 05/03/2008, at 10:28 AM, olamy@... wrote:
>
> > use new continuum parent
> > change groupId to org.apache.continuum (continuun is now TLP :-) )
>
> Will this be merged to trunk too?

Yep

>
> >
> > <archive>
> > <manifest>
> > -
> > <mainClass>org.apache.maven.continuum.management.DataManagementCli</
> > mainClass>
> > +
> > <mainClass>org.apache.continuum.management.DataManagementCli</
> > mainClass>
> > </manifest>
> > </archive>
> > </configuration>
> ...
> >
> >
> > <dependencies>
> > <dependency>
> > - <groupId>org.apache.maven.continuum</groupId>
> > + <groupId>org.apache.continuum</groupId>
> > <artifactId>continuum-xmlrpc-client</artifactId>
> > <version>${project.version}</version>
> > </dependency>
> > @@ -60,7 +60,7 @@
> > <arguments>
> > <argument>-classpath</argument>
> > <classpath />
> > -
> > <argument>org.apache.maven.continuum.xmlrpc.backup.Backup</argument>
> > + <argument>org.apache.continuum.xmlrpc.backup.Backup</
> > argument>
> > <argument>-h</argument>
> > </arguments>
> > </configuration>
> > @@ -73,7 +73,7 @@
> > <descriptor>src/assembly/app.xml</descriptor>
> > <archive>
> > <manifest>
> > -
> > <mainClass>org.apache.maven.continuum.xmlrpc.backup.Backup</mainClass>
> > + <mainClass>org.apache.continuum.xmlrpc.backup.Backup</
> > mainClass>
> > </manifest>
> > </archive>
> > </configuration>
> >
> ...
> > 
> > <classpath />
> > -
> > <argument>org.apache.maven.continuum.xmlrpc.client.SampleClient</
> > argument>
> > +
> > <argument>org.apache.continuum.xmlrpc.client.SampleClient</argument>
> > </arguments>
> > </configuration>
> > </plugin>
> >
> ...
> > <configuration>
> > <roleDefaults>
> > <roleDefault>
> > -
> > <
> > role
> > >org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcComponent</
> > role>
> > +
> > <role>org.apache.continuum.xmlrpc.server.ContinuumXmlRpcComponent</
> > role>
> > <instantiation-strategy>per-lookup</instantiation-
> > strategy>
> > </roleDefault>
> > </roleDefaults>
> >
>
> These all look to be in error because they refer to packages (not yet
> migrated).
>

Yep good catch error

> - Brett
>
>
> --
> Brett Porter
> brett@...
> 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-data-management/continuum-legacy/ continuum-data-managemen...

2008-03-04T15:37:27Z

On 05/03/2008, at 10:28 AM, olamy@... wrote:

> use new continuum parent
> change groupId to org.apache.continuum (continuun is now TLP :-) )

Will this be merged to trunk too?

>
> <archive>
> <manifest>
> -
> <mainClass>org.apache.maven.continuum.management.DataManagementCli</
> mainClass>
> +
> <mainClass>org.apache.continuum.management.DataManagementCli</
> mainClass>
> </manifest>
> </archive>
> </configuration>

...

>
>
> <dependencies>
> <dependency>
> - <groupId>org.apache.maven.continuum</groupId>
> + <groupId>org.apache.continuum</groupId>
> <artifactId>continuum-xmlrpc-client</artifactId>
> <version>${project.version}</version>
> </dependency>
> @@ -60,7 +60,7 @@
> <arguments>
> <argument>-classpath</argument>
> <classpath />
> -
> <argument>org.apache.maven.continuum.xmlrpc.backup.Backup</argument>
> + <argument>org.apache.continuum.xmlrpc.backup.Backup</
> argument>
> <argument>-h</argument>
> </arguments>
> </configuration>
> @@ -73,7 +73,7 @@
> <descriptor>src/assembly/app.xml</descriptor>
> <archive>
> <manifest>
> -
> <mainClass>org.apache.maven.continuum.xmlrpc.backup.Backup</mainClass>
> + <mainClass>org.apache.continuum.xmlrpc.backup.Backup</
> mainClass>
> </manifest>
> </archive>
> </configuration>
>

...

> 
> <classpath />
> -
> <argument>org.apache.maven.continuum.xmlrpc.client.SampleClient</
> argument>
> +
> <argument>org.apache.continuum.xmlrpc.client.SampleClient</argument>
> </arguments>
> </configuration>
> </plugin>
>

...

> <configuration>
> <roleDefaults>
> <roleDefault>
> -
> <
> role
> >org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcComponent</
> role>
> +
> <role>org.apache.continuum.xmlrpc.server.ContinuumXmlRpcComponent</
> role>
> <instantiation-strategy>per-lookup</instantiation-
> strategy>
> </roleDefault>
> </roleDefaults>
>

These all look to be in error because they refer to packages (not yet
migrated).

- Brett

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: Confused about the branches

2008-03-04T13:31:55Z

On 05/03/2008, at 5:18 AM, Olivier Lamy wrote:

> 2008/3/4, Brett Porter <brett@...>:
>>
>> 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
brett@...
http://blogs.exist.com/bporter/

Re: Confused about the branches

2008-03-04T10:18:57Z

2008/3/4, Brett Porter <brett@...>:

>
> 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
> brett@...
> http://blogs.exist.com/bporter/
>
>

Re: Account locked

2008-03-04T05:40:56Z

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 <minfrin@...> 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
jesse.mcconnell@...

Account locked

2008-03-04T05:07:22Z

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 (4K) Download Attachment

Re: Confused about the branches

2008-03-03T16:29:00Z

Brett Porter wrote:

>
> On 29/02/2008, at 10:04 AM, Emmanuel Venisse wrote:
>
>> On Thu, Feb 28, 2008 at 11:55 PM, Brett Porter <brett@...> wrote:
>>
>>>
>>> On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote:
>>>
>>>> why 1.1.x?
>>>
>>> in case there was a bugfix release on 1.1? I thought that was what the
>>> branch was for... maintenance of 1.1.
>>>
>>> or is there going to be 2 completely different strands of development?
>>
>>
>> I thought to do 1.x in the branch instead of only maintenance in
>> 1.1.xbecause I don't know how many time we'll need for the first
>> 2.0 release. User will probably need some new small feature before the
>> 2.0release and not only maintenance.
>
> With the roadmap discussion recently, I thought it was going to be an
> incremental move towards 2.0 on trunk - 1.2 will have some parts and
> refactorings, 1.3, 1.4 and so on. I'm not sure why there would need to
> be two streams of development? I think there's a real danger of getting
> lost in the 2.0 trap (c.f. Maven 1.0, Maven 2.0 and Maven 2.1 :)

We haven't pegged any version numbers to the tasks extracted from the
roadmap discussion. I think we should consider what architecture rework
we intend to do (and impact), and if it merits keeping 2 streams (or not).

>
> I'm actually keen to do a couple of small things myself and get a
> release out:
> - a few small bug fixes, like the lost change sets for some builds
> - better error handling
> - switch to a Jetty runtime without the plexus appserver so we can use
> jetty 6
> - add a call to svn info --xml to check whether to do an svn update to
> speed up working copy updates
>

I agree on getting something out frequently. Having said that if there
is a consensus on 2 streams then I think we need to keep the momentum up
on both to get releases/milestones out there.

> Just stuff I see from running vmbuild and the maven zone.
>
> I think that and a couple of other refactorings that are being discussed
> on here would make a good 1.2 in the next couple of months. WDYT?
>
> - Brett
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

Cheers,
Rahul

Re: Confused about the branches

2008-03-03T16:23:27Z

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.

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?

> 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?

Cheers,
Brett

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: Confused about the branches

2008-03-03T15:47:25Z

Agree on this.
Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which
prevent using xml-rpc :-(.

If no objections, I will change root pom to not have anymore maven pom
as parent.

--
Olivier

2008/3/4, Brett Porter <brett@...>:

>
> On 29/02/2008, at 10:04 AM, Emmanuel Venisse wrote:
>
> > On Thu, Feb 28, 2008 at 11:55 PM, Brett Porter <brett@...>
> > wrote:
> >
> >>
> >> On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote:
> >>
> >>> why 1.1.x?
> >>
> >> in case there was a bugfix release on 1.1? I thought that was what
> >> the
> >> branch was for... maintenance of 1.1.
> >>
> >> or is there going to be 2 completely different strands of
> >> development?
> >
> >
> > I thought to do 1.x in the branch instead of only maintenance in
> > 1.1.xbecause I don't know how many time we'll need for the first
> > 2.0 release. User will probably need some new small feature before the
> > 2.0release and not only maintenance.
>
> With the roadmap discussion recently, I thought it was going to be an
> incremental move towards 2.0 on trunk - 1.2 will have some parts and
> refactorings, 1.3, 1.4 and so on. I'm not sure why there would need to
> be two streams of development? I think there's a real danger of
> getting lost in the 2.0 trap (c.f. Maven 1.0, Maven 2.0 and Maven 2.1 :)
>
> I'm actually keen to do a couple of small things myself and get a
> release out:
> - a few small bug fixes, like the lost change sets for some builds
> - better error handling
> - switch to a Jetty runtime without the plexus appserver so we can use
> jetty 6
> - add a call to svn info --xml to check whether to do an svn update to
> speed up working copy updates
>
> Just stuff I see from running vmbuild and the maven zone.
>
> I think that and a couple of other refactorings that are being
> discussed on here would make a good 1.2 in the next couple of months.
> WDYT?
>
> - Brett
>
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

Re: Confused about the branches

2008-03-03T15:32:56Z

On 29/02/2008, at 10:04 AM, Emmanuel Venisse wrote:

> On Thu, Feb 28, 2008 at 11:55 PM, Brett Porter <brett@...>
> wrote:
>
>>
>> On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote:
>>
>>> why 1.1.x?
>>
>> in case there was a bugfix release on 1.1? I thought that was what
>> the
>> branch was for... maintenance of 1.1.
>>
>> or is there going to be 2 completely different strands of
>> development?
>
>
> I thought to do 1.x in the branch instead of only maintenance in
> 1.1.xbecause I don't know how many time we'll need for the first
> 2.0 release. User will probably need some new small feature before the
> 2.0release and not only maintenance.

With the roadmap discussion recently, I thought it was going to be an
incremental move towards 2.0 on trunk - 1.2 will have some parts and
refactorings, 1.3, 1.4 and so on. I'm not sure why there would need to
be two streams of development? I think there's a real danger of
getting lost in the 2.0 trap (c.f. Maven 1.0, Maven 2.0 and Maven 2.1 :)

I'm actually keen to do a couple of small things myself and get a
release out:
- a few small bug fixes, like the lost change sets for some builds
- better error handling
- switch to a Jetty runtime without the plexus appserver so we can use
jetty 6
- add a call to svn info --xml to check whether to do an svn update to
speed up working copy updates

Just stuff I see from running vmbuild and the maven zone.

I think that and a couple of other refactorings that are being
discussed on here would make a good 1.2 in the next couple of months.
WDYT?

- Brett

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

Re: release button in project group page.

2008-03-03T01:34:27Z

Yes, but I think that it should release all projects in the group.
It's really strange that this button doesn't work as the "build all
projects" button. And it would be a very great feature if it do it.

Benoit.

Edwin Punzalan wrote:

> I think this is because the release plugin is being called at the parent pom
> once to also release all its modules whereas builds are being called at each
> project in the project group.
> On Sun, Mar 2, 2008 at 3:23 AM, Benoit Decherf <decherfb@...>
> wrote:
>
>
>> Hi,
>>
>> The release button of the project group page only works if all projects
>> in the group have the same parent and the parent is in the group.
>>
>> Why doesn't it make a release of all projects in the group ? I think
>> that it should work as the build all projects button.
>>
>> Benoit.
>>
>>
>
>

Re: release button in project group page.

2008-03-02T20:22:29Z

I think this is because the release plugin is being called at the parent pom
once to also release all its modules whereas builds are being called at each
project in the project group.
On Sun, Mar 2, 2008 at 3:23 AM, Benoit Decherf <decherfb@...>
wrote:

> Hi,
>
> The release button of the project group page only works if all projects
> in the group have the same parent and the parent is in the group.
>
> Why doesn't it make a release of all projects in the group ? I think
> that it should work as the build all projects button.
>
> Benoit.
>

release button in project group page.

2008-03-02T03:13:09Z

Hi,

The release button of the project group page only works if all projects
in the group have the same parent and the parent is in the group.

Why doesn't it make a release of all projects in the group ? I think
that it should work as the build all projects button.

Benoit.

Re: CI disabled for Continuum due to svn move

2008-03-01T14:32:34Z

I was due to move it to vmbuild anyway so I'll just do that now.

Sorry about that, should have remembered.

- Brett

On 02/03/2008, at 3:12 AM, Wendy Smoak wrote:

> On the Maven zone, I changed the schedule for the "Continuum Parent"
> group to 'On Demand' so that it won't run.
>
> AFAIK there's no way to tell it where the source code moved, so we'll
> have to delete and re-add the projects.
>
> (Talking about using Continuuum to build Continuum is confusing...)
>
> --
> Wendy

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

CI disabled for Continuum due to svn move

2008-03-01T08:12:03Z

On the Maven zone, I changed the schedule for the "Continuum Parent"
group to 'On Demand' so that it won't run.

AFAIK there's no way to tell it where the source code moved, so we'll
have to delete and re-add the projects.

(Talking about using Continuuum to build Continuum is confusing...)

--
Wendy