You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by si...@insession.com on 2005/07/13 14:12:14 UTC
M4 QA Branch Build Failure
I tried building the M4 QA branch to test some dependency changes by doing
the following:
C:\Projects\J2EE\geronimo_m4qa>svn checkout
https://svn.apache.org/repos/asf/geronimo/branches/v1_0_M4-QA geronimo
C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:fresh-checkout
C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:rebuild-all
-Dmaven.test.failure.ignore=true
The build fails.
It appears some of the issues are:
* the m:fresh-checkout processing in branch hasn't been changed to get the
OpenEJB & TranQL code from a tag/branch. It appears that it would be
getting the latest OpenEJB code, which is not what we want. Have OpenEJB
and TranQL been tagged in CVS? Can we get the QA branch building in a
repeatable fashion with OpenEJB & TranQL?
* in etc/project.properties geronimo_version is set to 1.0-SNAPSHOT, yet
in the geronimo-1.0-M4-QA-src.zip file, it has a value of 1.0-M4-QA .
Shouldn't this version change be checked into the branch? This could
cause problems if the JARs are uploaded to a repository from the build.
Once these issues are resolved we should have some instructions on how it
should be built from source so that people can test fixes on the branch
before committing.
Build failure messages...
+----------------------------------------
| Executing default OpenEJB :: PK Generation :: Builder
| Memory: 66M/93M
+----------------------------------------
Attempting to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
WARNING: Failed to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
Attempting to download tranql-1.0-SNAPSHOT.jar.
Attempting to download openejb-core-2.0-SNAPSHOT.jar.
Attempting to download geronimo-deployment-1.0-SNAPSHOT.jar.
Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
Attempting to download geronimo-j2ee-1.0-SNAPSHOT.jar.
Attempting to download geronimo-j2ee-builder-1.0-SNAPSHOT.jar.
Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
Attempting to download commons-jelly-tags-velocity-SNAPSHOT.jar.
BUILD FAILED
File...... C:\Documents and
Settings\sissonj\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
The build cannot continue because of the following unsatisfied dependency:
xmlbeans-maven-plugin-2.0.0-beta1.jar
John
This e-mail message and any attachments may contain confidential,
proprietary or non-public information. This information is intended
solely for the designated recipient(s). If an addressing or transmission
error has misdirected this e-mail, please notify the sender immediately
and destroy this e-mail. Any review, dissemination, use or reliance upon
this information by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.
Re: M4 QA Branch Build Failure
Posted by David Jencks <dj...@gluecode.com>.
On Jul 13, 2005, at 10:34 AM, Geir Magnusson Jr. wrote:
>
> On Jul 13, 2005, at 11:45 AM, David Jencks wrote:
>
>>
>> On Jul 13, 2005, at 5:23 AM, Geir Magnusson Jr wrote:
>>
>>
>>>
>>> On Jul 13, 2005, at 8:12 AM, sissonj@insession.com wrote:
>>>
>>>
>>>> I tried building the M4 QA branch to test some dependency changes
>>>> by doing
>>>> the following:
>>>>
>>>> C:\Projects\J2EE\geronimo_m4qa>svn checkout
>>>> https://svn.apache.org/repos/asf/geronimo/branches/v1_0_M4-QA
>>>> geronimo
>>>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:fresh-checkout
>>>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:rebuild-all
>>>> -Dmaven.test.failure.ignore=true
>>>>
>>>> The build fails.
>>>>
>>>> It appears some of the issues are:
>>>>
>>>> * the m:fresh-checkout processing in branch hasn't been changed to
>>>> get the
>>>> OpenEJB & TranQL code from a tag/branch. It appears that it would
>>>> be
>>>> getting the latest OpenEJB code, which is not what we want. Have
>>>> OpenEJB
>>>> and TranQL been tagged in CVS? Can we get the QA branch building in
>>>> a
>>>> repeatable fashion with OpenEJB & TranQL?
>>>>
>>>
>>> At this point, can we just use released jars from OpenEJB and TranQL
>>> for M4? Gets rid of the need for their source to be involved.
>>>
>>
>> isn't that an assumption that there are no bugs in either project
>> that we need to fix for M4?
>
> Yes, but if they are fixed for M4, couldn't we ask them to produce a
> non-snapshot jar for us to depend on? Then we don't need their code
> in our M4 src to enable people to build...
I'd prefer that we find out if there are any bugs we need to fix for m4
before we release the non-snapshot jar. When we do the release, I
think we should release all the jars at once.
>
>
>> I also think there might be some value in providing a way to build m4
>> similar to the way we build head.
>
> Like
>
> $ tar zf m4.src.tgz
> $ cd m4
> $ maven
>
> ?
I was thinking more
maven -o m:rebuild
since in my experience the projects are still too intertwined to build
separately, whatever the virtues of greater separation may be.
thanks
david jencks
>>
>> thanks
>> david jencks
>>
>>>
>>>
>>>>
>>>> * in etc/project.properties geronimo_version is set to
>>>> 1.0-SNAPSHOT, yet
>>>> in the geronimo-1.0-M4-QA-src.zip file, it has a value of 1.0-M4-QA
>>>> .
>>>> Shouldn't this version change be checked into the branch? This
>>>> could
>>>> cause problems if the JARs are uploaded to a repository from the
>>>> build.
>>>>
>>>> Once these issues are resolved we should have some instructions on
>>>> how it
>>>> should be built from source so that people can test fixes on the
>>>> branch
>>>> before committing.
>>>>
>>>> Build failure messages...
>>>> +----------------------------------------
>>>> | Executing default OpenEJB :: PK Generation :: Builder
>>>> | Memory: 66M/93M
>>>> +----------------------------------------
>>>> Attempting to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>>>> WARNING: Failed to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>>>> Attempting to download tranql-1.0-SNAPSHOT.jar.
>>>> Attempting to download openejb-core-2.0-SNAPSHOT.jar.
>>>> Attempting to download geronimo-deployment-1.0-SNAPSHOT.jar.
>>>> Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
>>>> Attempting to download geronimo-j2ee-1.0-SNAPSHOT.jar.
>>>> Attempting to download geronimo-j2ee-builder-1.0-SNAPSHOT.jar.
>>>> Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
>>>> Attempting to download commons-jelly-tags-velocity-SNAPSHOT.jar.
>>>>
>>>> BUILD FAILED
>>>> File...... C:\Documents and
>>>> Settings\sissonj\.maven\cache\maven-multiproject-plugin
>>>> -1.3.1\plugin.jelly
>>>> Element... maven:reactor
>>>> Line...... 217
>>>> Column.... 9
>>>> The build cannot continue because of the following unsatisfied
>>>> dependency:
>>>>
>>>> xmlbeans-maven-plugin-2.0.0-beta1.jar
>>>>
>>>>
>>>> John
>>>>
>>>> This e-mail message and any attachments may contain confidential,
>>>> proprietary or non-public information. This information is intended
>>>> solely for the designated recipient(s). If an addressing or
>>>> transmission
>>>> error has misdirected this e-mail, please notify the sender
>>>> immediately
>>>> and destroy this e-mail. Any review, dissemination, use or
>>>> reliance upon
>>>> this information by unintended recipients is prohibited. Any
>>>> opinions
>>>> expressed in this e-mail are those of the author personally.
>>>>
>>>>
>>>>
>>>
>>> --
>>> Geir Magnusson Jr +1-203-665-6437
>>> geir@optonline.net
>>>
>>>
>>>
>>
>>
>
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>
>
Re: M4 QA Branch Build Failure
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Jul 13, 2005, at 11:45 AM, David Jencks wrote:
>
> On Jul 13, 2005, at 5:23 AM, Geir Magnusson Jr wrote:
>
>
>>
>> On Jul 13, 2005, at 8:12 AM, sissonj@insession.com wrote:
>>
>>
>>> I tried building the M4 QA branch to test some dependency changes
>>> by doing
>>> the following:
>>>
>>> C:\Projects\J2EE\geronimo_m4qa>svn checkout
>>> https://svn.apache.org/repos/asf/geronimo/branches/v1_0_M4-QA
>>> geronimo
>>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:fresh-checkout
>>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:rebuild-all
>>> -Dmaven.test.failure.ignore=true
>>>
>>> The build fails.
>>>
>>> It appears some of the issues are:
>>>
>>> * the m:fresh-checkout processing in branch hasn't been changed
>>> to get the
>>> OpenEJB & TranQL code from a tag/branch. It appears that it
>>> would be
>>> getting the latest OpenEJB code, which is not what we want. Have
>>> OpenEJB
>>> and TranQL been tagged in CVS? Can we get the QA branch building
>>> in a
>>> repeatable fashion with OpenEJB & TranQL?
>>>
>>
>> At this point, can we just use released jars from OpenEJB and
>> TranQL for M4? Gets rid of the need for their source to be involved.
>>
>
> isn't that an assumption that there are no bugs in either project
> that we need to fix for M4?
Yes, but if they are fixed for M4, couldn't we ask them to produce a
non-snapshot jar for us to depend on? Then we don't need their code
in our M4 src to enable people to build...
> I also think there might be some value in providing a way to build
> m4 similar to the way we build head.
Like
$ tar zf m4.src.tgz
$ cd m4
$ maven
?
>
> thanks
> david jencks
>
>>
>>
>>>
>>> * in etc/project.properties geronimo_version is set to 1.0-
>>> SNAPSHOT, yet
>>> in the geronimo-1.0-M4-QA-src.zip file, it has a value of 1.0-M4-
>>> QA .
>>> Shouldn't this version change be checked into the branch? This
>>> could
>>> cause problems if the JARs are uploaded to a repository from the
>>> build.
>>>
>>> Once these issues are resolved we should have some instructions
>>> on how it
>>> should be built from source so that people can test fixes on the
>>> branch
>>> before committing.
>>>
>>> Build failure messages...
>>> +----------------------------------------
>>> | Executing default OpenEJB :: PK Generation :: Builder
>>> | Memory: 66M/93M
>>> +----------------------------------------
>>> Attempting to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>>> WARNING: Failed to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>>> Attempting to download tranql-1.0-SNAPSHOT.jar.
>>> Attempting to download openejb-core-2.0-SNAPSHOT.jar.
>>> Attempting to download geronimo-deployment-1.0-SNAPSHOT.jar.
>>> Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
>>> Attempting to download geronimo-j2ee-1.0-SNAPSHOT.jar.
>>> Attempting to download geronimo-j2ee-builder-1.0-SNAPSHOT.jar.
>>> Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
>>> Attempting to download commons-jelly-tags-velocity-SNAPSHOT.jar.
>>>
>>> BUILD FAILED
>>> File...... C:\Documents and
>>> Settings\sissonj\.maven\cache\maven-multiproject-plugin-1.3.1
>>> \plugin.jelly
>>> Element... maven:reactor
>>> Line...... 217
>>> Column.... 9
>>> The build cannot continue because of the following unsatisfied
>>> dependency:
>>>
>>> xmlbeans-maven-plugin-2.0.0-beta1.jar
>>>
>>>
>>> John
>>>
>>> This e-mail message and any attachments may contain confidential,
>>> proprietary or non-public information. This information is intended
>>> solely for the designated recipient(s). If an addressing or
>>> transmission
>>> error has misdirected this e-mail, please notify the sender
>>> immediately
>>> and destroy this e-mail. Any review, dissemination, use or
>>> reliance upon
>>> this information by unintended recipients is prohibited. Any
>>> opinions
>>> expressed in this e-mail are those of the author personally.
>>>
>>>
>>>
>>
>> --
>> Geir Magnusson Jr +1-203-665-6437
>> geir@optonline.net
>>
>>
>>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: M4 QA Branch Build Failure
Posted by David Jencks <dj...@gluecode.com>.
On Jul 13, 2005, at 5:23 AM, Geir Magnusson Jr wrote:
>
> On Jul 13, 2005, at 8:12 AM, sissonj@insession.com wrote:
>
>> I tried building the M4 QA branch to test some dependency changes by
>> doing
>> the following:
>>
>> C:\Projects\J2EE\geronimo_m4qa>svn checkout
>> https://svn.apache.org/repos/asf/geronimo/branches/v1_0_M4-QA geronimo
>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:fresh-checkout
>> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:rebuild-all
>> -Dmaven.test.failure.ignore=true
>>
>> The build fails.
>>
>> It appears some of the issues are:
>>
>> * the m:fresh-checkout processing in branch hasn't been changed to
>> get the
>> OpenEJB & TranQL code from a tag/branch. It appears that it would be
>> getting the latest OpenEJB code, which is not what we want. Have
>> OpenEJB
>> and TranQL been tagged in CVS? Can we get the QA branch building in a
>> repeatable fashion with OpenEJB & TranQL?
>
> At this point, can we just use released jars from OpenEJB and TranQL
> for M4? Gets rid of the need for their source to be involved.
isn't that an assumption that there are no bugs in either project that
we need to fix for M4? I also think there might be some value in
providing a way to build m4 similar to the way we build head.
thanks
david jencks
>
>>
>> * in etc/project.properties geronimo_version is set to 1.0-SNAPSHOT,
>> yet
>> in the geronimo-1.0-M4-QA-src.zip file, it has a value of 1.0-M4-QA .
>> Shouldn't this version change be checked into the branch? This could
>> cause problems if the JARs are uploaded to a repository from the
>> build.
>>
>> Once these issues are resolved we should have some instructions on
>> how it
>> should be built from source so that people can test fixes on the
>> branch
>> before committing.
>>
>> Build failure messages...
>> +----------------------------------------
>> | Executing default OpenEJB :: PK Generation :: Builder
>> | Memory: 66M/93M
>> +----------------------------------------
>> Attempting to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>> WARNING: Failed to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
>> Attempting to download tranql-1.0-SNAPSHOT.jar.
>> Attempting to download openejb-core-2.0-SNAPSHOT.jar.
>> Attempting to download geronimo-deployment-1.0-SNAPSHOT.jar.
>> Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
>> Attempting to download geronimo-j2ee-1.0-SNAPSHOT.jar.
>> Attempting to download geronimo-j2ee-builder-1.0-SNAPSHOT.jar.
>> Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
>> Attempting to download commons-jelly-tags-velocity-SNAPSHOT.jar.
>>
>> BUILD FAILED
>> File...... C:\Documents and
>> Settings\sissonj\.maven\cache\maven-multiproject-plugin
>> -1.3.1\plugin.jelly
>> Element... maven:reactor
>> Line...... 217
>> Column.... 9
>> The build cannot continue because of the following unsatisfied
>> dependency:
>>
>> xmlbeans-maven-plugin-2.0.0-beta1.jar
>>
>>
>> John
>>
>> This e-mail message and any attachments may contain confidential,
>> proprietary or non-public information. This information is intended
>> solely for the designated recipient(s). If an addressing or
>> transmission
>> error has misdirected this e-mail, please notify the sender
>> immediately
>> and destroy this e-mail. Any review, dissemination, use or reliance
>> upon
>> this information by unintended recipients is prohibited. Any opinions
>> expressed in this e-mail are those of the author personally.
>>
>>
>
> --
> Geir Magnusson Jr +1-203-665-6437
> geir@optonline.net
>
>
Re: M4 QA Branch Build Failure
Posted by Jacek Laskowski <jl...@apache.org>.
sissonj@insession.com wrote:
> I looked in http://dist.codehaus.org/openejb/jars/ and
> http://dist.codehaus.org/tranql/jars/ and it doesn't look like there are
> any recent releases.
>
> Looks like some releases need to be built. How soon can this be done?
I think it's a good idea to release OpenEJB 2.0 G4. Since OpenEJB 2.0 is
specially developed for Geronimo why it would hurt anyone? I'd also vote
for releasing OpenEJB 2.0 at the same time Geronimo will.
If noone objects, I'll go for cutting the release 2.0G4.
> John
Jacek
Re: M4 QA Branch Build Failure
Posted by si...@insession.com.
Geir Magnusson Jr <ge...@4quarters.com> wrote on 13/07/2005 10:23:55 PM:
> >
> > It appears some of the issues are:
> >
> > * the m:fresh-checkout processing in branch hasn't been changed to
> > get the
> > OpenEJB & TranQL code from a tag/branch. It appears that it would be
> > getting the latest OpenEJB code, which is not what we want. Have
> > OpenEJB
> > and TranQL been tagged in CVS? Can we get the QA branch building in a
> > repeatable fashion with OpenEJB & TranQL?
>
> At this point, can we just use released jars from OpenEJB and TranQL
> for M4? Gets rid of the need for their source to be involved.
I looked in http://dist.codehaus.org/openejb/jars/ and
http://dist.codehaus.org/tranql/jars/ and it doesn't look like there are
any recent releases.
Looks like some releases need to be built. How soon can this be done?
John
This e-mail message and any attachments may contain confidential,
proprietary or non-public information. This information is intended
solely for the designated recipient(s). If an addressing or transmission
error has misdirected this e-mail, please notify the sender immediately
and destroy this e-mail. Any review, dissemination, use or reliance upon
this information by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.
Re: M4 QA Branch Build Failure
Posted by Geir Magnusson Jr <ge...@4quarters.com>.
On Jul 13, 2005, at 8:12 AM, sissonj@insession.com wrote:
> I tried building the M4 QA branch to test some dependency changes
> by doing
> the following:
>
> C:\Projects\J2EE\geronimo_m4qa>svn checkout
> https://svn.apache.org/repos/asf/geronimo/branches/v1_0_M4-QA geronimo
> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:fresh-checkout
> C:\Projects\J2EE\geronimo_m4qa\geronimo>maven m:rebuild-all
> -Dmaven.test.failure.ignore=true
>
> The build fails.
>
> It appears some of the issues are:
>
> * the m:fresh-checkout processing in branch hasn't been changed to
> get the
> OpenEJB & TranQL code from a tag/branch. It appears that it would be
> getting the latest OpenEJB code, which is not what we want. Have
> OpenEJB
> and TranQL been tagged in CVS? Can we get the QA branch building in a
> repeatable fashion with OpenEJB & TranQL?
At this point, can we just use released jars from OpenEJB and TranQL
for M4? Gets rid of the need for their source to be involved.
>
> * in etc/project.properties geronimo_version is set to 1.0-
> SNAPSHOT, yet
> in the geronimo-1.0-M4-QA-src.zip file, it has a value of 1.0-M4-QA .
> Shouldn't this version change be checked into the branch? This could
> cause problems if the JARs are uploaded to a repository from the
> build.
>
> Once these issues are resolved we should have some instructions on
> how it
> should be built from source so that people can test fixes on the
> branch
> before committing.
>
> Build failure messages...
> +----------------------------------------
> | Executing default OpenEJB :: PK Generation :: Builder
> | Memory: 66M/93M
> +----------------------------------------
> Attempting to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
> WARNING: Failed to download xmlbeans-maven-plugin-2.0.0-beta1.jar.
> Attempting to download tranql-1.0-SNAPSHOT.jar.
> Attempting to download openejb-core-2.0-SNAPSHOT.jar.
> Attempting to download geronimo-deployment-1.0-SNAPSHOT.jar.
> Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
> Attempting to download geronimo-j2ee-1.0-SNAPSHOT.jar.
> Attempting to download geronimo-j2ee-builder-1.0-SNAPSHOT.jar.
> Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
> Attempting to download commons-jelly-tags-velocity-SNAPSHOT.jar.
>
> BUILD FAILED
> File...... C:\Documents and
> Settings\sissonj\.maven\cache\maven-multiproject-plugin-1.3.1
> \plugin.jelly
> Element... maven:reactor
> Line...... 217
> Column.... 9
> The build cannot continue because of the following unsatisfied
> dependency:
>
> xmlbeans-maven-plugin-2.0.0-beta1.jar
>
>
> John
>
> This e-mail message and any attachments may contain confidential,
> proprietary or non-public information. This information is intended
> solely for the designated recipient(s). If an addressing or
> transmission
> error has misdirected this e-mail, please notify the sender
> immediately
> and destroy this e-mail. Any review, dissemination, use or
> reliance upon
> this information by unintended recipients is prohibited. Any opinions
> expressed in this e-mail are those of the author personally.
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@optonline.net