You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by new_user_on_forum <Ki...@raytheon.co.uk> on 2011/01/05 12:30:40 UTC
pom upload issue
Our Maven project is a multi-module set up with approximately 20 modules.
I have noticed an issue whereby a project will fail to build as a dependent
project has a mal-formed pom uploaded into the repo and so Maven will fail
with an error stating that it was expecting closing tags etc.
Looking at the pom in the version control system the pom is well formed and
valid.
The issue arises when Continuum is installing the artifacts into the repo
after a sucessful build. The pom is written to the repo is its entirity and
then a chunk of the pom is removed leaving only a file of size 4096 bytes.
Interestinly we have poms of size > 4096 bytes that always are sucessfully
uploaded into the repo by Continuum.
I have opened in the pom in a hex editor and see no 'bad' character at the
4096k position in the file.
This issue does not present itself when building on the command line with
maven.
I don't see any issues in the Continuum log file to indicate that there has
been a problem.
We are using version 1.3.6 build 919943.
--
View this message in context: http://old.nabble.com/pom-upload-issue-tp30595161p30595161.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: pom upload issue
Posted by new_user_on_forum <Ki...@raytheon.co.uk>.
Continuum is downloading the pom from the source control tool to its working
directory and then passed to Maven. I'm also going to try to roll back to
version 1.2.3 of Continuum to determine if I experience the same issue.
A patch to log what is happening would be most helpful.
Louis Smith-3 wrote:
>
> I can confirm having seen this behavior as well. We couldn't determine
> whether it was something continuum was doing or if it was the maven
> install
> itself.
>
> Is the pom actually created by continuum and being passed to maven? If
> so,
> is there a quick patch that could be applied to write that pom to the log
> or
> somewhere else to look at it?
>
> Louis
>
> On Fri, Jan 7, 2011 at 2:11 AM, new_user_on_forum <
> Kieran.McGivern@raytheon.co.uk> wrote:
>
>>
>> Disk space is fine on the build machine where Continuum is installed.
>> I've
>> also deleted the contents of the repo but the issue remains.
>> I have tried changing the pom and viewed the offending pom in a hex
>> editor
>> just to ensure that there wasn't a special character that could be the
>> cause
>> but found nothing.
>>
>> Cheers,
>> K
>>
>>
>> brettporter wrote:
>> >
>> > I can't think of what might cause this - we've certainly not seen it.
>> >
>> > Is the corrupted version stuck and needs to be removed from the repo?
>> Disk
>> > space issues? Have you tried changing the POM to see how that impacts
>> the
>> > behaviour?
>> >
>> > Cheers,
>> > Brett
>> >
>> > On 05/01/2011, at 10:30 PM, new_user_on_forum wrote:
>> >
>> >>
>> >>
>> >> Our Maven project is a multi-module set up with approximately 20
>> modules.
>> >> I have noticed an issue whereby a project will fail to build as a
>> >> dependent
>> >> project has a mal-formed pom uploaded into the repo and so Maven will
>> >> fail
>> >> with an error stating that it was expecting closing tags etc.
>> >>
>> >> Looking at the pom in the version control system the pom is well
>> formed
>> >> and
>> >> valid.
>> >>
>> >> The issue arises when Continuum is installing the artifacts into the
>> repo
>> >> after a sucessful build. The pom is written to the repo is its
>> entirity
>> >> and
>> >> then a chunk of the pom is removed leaving only a file of size 4096
>> >> bytes.
>> >> Interestinly we have poms of size > 4096 bytes that always are
>> >> sucessfully
>> >> uploaded into the repo by Continuum.
>> >>
>> >> I have opened in the pom in a hex editor and see no 'bad' character at
>> >> the
>> >> 4096k position in the file.
>> >> This issue does not present itself when building on the command line
>> with
>> >> maven.
>> >> I don't see any issues in the Continuum log file to indicate that
>> there
>> >> has
>> >> been a problem.
>> >>
>> >> We are using version 1.3.6 build 919943.
>> >> --
>> >> View this message in context:
>> >> http://old.nabble.com/pom-upload-issue-tp30595161p30595161.html
>> >> Sent from the Continuum - Users mailing list archive at Nabble.com.
>> >>
>> >
>> > --
>> > Brett Porter
>> > brett@apache.org
>> > http://brettporter.wordpress.com/
>> > http://au.linkedin.com/in/brettporter
>> >
>> >
>> >
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/pom-upload-issue-tp30595161p30611931.html
>> Sent from the Continuum - Users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Dr. Louis Smith, ThD
> Chief Technology Officer, Kyra InfoTech
> Colonel, Commemorative Air Force
> <#>
> <#>
> <#> <#>
>
>
--
View this message in context: http://old.nabble.com/pom-upload-issue-tp30595161p30613444.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: pom upload issue
Posted by Louis Smith <dr...@gmail.com>.
I can confirm having seen this behavior as well. We couldn't determine
whether it was something continuum was doing or if it was the maven install
itself.
Is the pom actually created by continuum and being passed to maven? If so,
is there a quick patch that could be applied to write that pom to the log or
somewhere else to look at it?
Louis
On Fri, Jan 7, 2011 at 2:11 AM, new_user_on_forum <
Kieran.McGivern@raytheon.co.uk> wrote:
>
> Disk space is fine on the build machine where Continuum is installed. I've
> also deleted the contents of the repo but the issue remains.
> I have tried changing the pom and viewed the offending pom in a hex editor
> just to ensure that there wasn't a special character that could be the
> cause
> but found nothing.
>
> Cheers,
> K
>
>
> brettporter wrote:
> >
> > I can't think of what might cause this - we've certainly not seen it.
> >
> > Is the corrupted version stuck and needs to be removed from the repo?
> Disk
> > space issues? Have you tried changing the POM to see how that impacts the
> > behaviour?
> >
> > Cheers,
> > Brett
> >
> > On 05/01/2011, at 10:30 PM, new_user_on_forum wrote:
> >
> >>
> >>
> >> Our Maven project is a multi-module set up with approximately 20
> modules.
> >> I have noticed an issue whereby a project will fail to build as a
> >> dependent
> >> project has a mal-formed pom uploaded into the repo and so Maven will
> >> fail
> >> with an error stating that it was expecting closing tags etc.
> >>
> >> Looking at the pom in the version control system the pom is well formed
> >> and
> >> valid.
> >>
> >> The issue arises when Continuum is installing the artifacts into the
> repo
> >> after a sucessful build. The pom is written to the repo is its entirity
> >> and
> >> then a chunk of the pom is removed leaving only a file of size 4096
> >> bytes.
> >> Interestinly we have poms of size > 4096 bytes that always are
> >> sucessfully
> >> uploaded into the repo by Continuum.
> >>
> >> I have opened in the pom in a hex editor and see no 'bad' character at
> >> the
> >> 4096k position in the file.
> >> This issue does not present itself when building on the command line
> with
> >> maven.
> >> I don't see any issues in the Continuum log file to indicate that there
> >> has
> >> been a problem.
> >>
> >> We are using version 1.3.6 build 919943.
> >> --
> >> View this message in context:
> >> http://old.nabble.com/pom-upload-issue-tp30595161p30595161.html
> >> Sent from the Continuum - Users mailing list archive at Nabble.com.
> >>
> >
> > --
> > Brett Porter
> > brett@apache.org
> > http://brettporter.wordpress.com/
> > http://au.linkedin.com/in/brettporter
> >
> >
> >
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/pom-upload-issue-tp30595161p30611931.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
>
--
Dr. Louis Smith, ThD
Chief Technology Officer, Kyra InfoTech
Colonel, Commemorative Air Force
<#>
<#>
<#> <#>
Re: pom upload issue
Posted by new_user_on_forum <Ki...@raytheon.co.uk>.
Disk space is fine on the build machine where Continuum is installed. I've
also deleted the contents of the repo but the issue remains.
I have tried changing the pom and viewed the offending pom in a hex editor
just to ensure that there wasn't a special character that could be the cause
but found nothing.
Cheers,
K
brettporter wrote:
>
> I can't think of what might cause this - we've certainly not seen it.
>
> Is the corrupted version stuck and needs to be removed from the repo? Disk
> space issues? Have you tried changing the POM to see how that impacts the
> behaviour?
>
> Cheers,
> Brett
>
> On 05/01/2011, at 10:30 PM, new_user_on_forum wrote:
>
>>
>>
>> Our Maven project is a multi-module set up with approximately 20 modules.
>> I have noticed an issue whereby a project will fail to build as a
>> dependent
>> project has a mal-formed pom uploaded into the repo and so Maven will
>> fail
>> with an error stating that it was expecting closing tags etc.
>>
>> Looking at the pom in the version control system the pom is well formed
>> and
>> valid.
>>
>> The issue arises when Continuum is installing the artifacts into the repo
>> after a sucessful build. The pom is written to the repo is its entirity
>> and
>> then a chunk of the pom is removed leaving only a file of size 4096
>> bytes.
>> Interestinly we have poms of size > 4096 bytes that always are
>> sucessfully
>> uploaded into the repo by Continuum.
>>
>> I have opened in the pom in a hex editor and see no 'bad' character at
>> the
>> 4096k position in the file.
>> This issue does not present itself when building on the command line with
>> maven.
>> I don't see any issues in the Continuum log file to indicate that there
>> has
>> been a problem.
>>
>> We are using version 1.3.6 build 919943.
>> --
>> View this message in context:
>> http://old.nabble.com/pom-upload-issue-tp30595161p30595161.html
>> Sent from the Continuum - Users mailing list archive at Nabble.com.
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
>
--
View this message in context: http://old.nabble.com/pom-upload-issue-tp30595161p30611931.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: pom upload issue
Posted by Brett Porter <br...@apache.org>.
I can't think of what might cause this - we've certainly not seen it.
Is the corrupted version stuck and needs to be removed from the repo? Disk space issues? Have you tried changing the POM to see how that impacts the behaviour?
Cheers,
Brett
On 05/01/2011, at 10:30 PM, new_user_on_forum wrote:
>
>
> Our Maven project is a multi-module set up with approximately 20 modules.
> I have noticed an issue whereby a project will fail to build as a dependent
> project has a mal-formed pom uploaded into the repo and so Maven will fail
> with an error stating that it was expecting closing tags etc.
>
> Looking at the pom in the version control system the pom is well formed and
> valid.
>
> The issue arises when Continuum is installing the artifacts into the repo
> after a sucessful build. The pom is written to the repo is its entirity and
> then a chunk of the pom is removed leaving only a file of size 4096 bytes.
> Interestinly we have poms of size > 4096 bytes that always are sucessfully
> uploaded into the repo by Continuum.
>
> I have opened in the pom in a hex editor and see no 'bad' character at the
> 4096k position in the file.
> This issue does not present itself when building on the command line with
> maven.
> I don't see any issues in the Continuum log file to indicate that there has
> been a problem.
>
> We are using version 1.3.6 build 919943.
> --
> View this message in context: http://old.nabble.com/pom-upload-issue-tp30595161p30595161.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter