You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kevin Christmas (JIRA)" <ji...@codehaus.org> on 2007/11/12 16:47:25 UTC

[jira] Created: (CONTINUUM-1562) NullPointerException when saving project

NullPointerException when saving project
----------------------------------------

                 Key: CONTINUUM-1562
                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.1-alpha-1
         Environment: Windows 2004 server installation
            Reporter: Kevin Christmas
            Assignee: Emmanuel Venisse
             Fix For: 1.1-beta-2


I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.

When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (CONTINUUM-1562) NullPointerException when saving project

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated CONTINUUM-1562:
----------------------------------------

             Assignee:     (was: Emmanuel Venisse)
    Affects Version/s:     (was: 1.1-alpha-1)
                       1.1-beta-4
        Fix Version/s:     (was: 1.1-beta-2)

Can you explain how to reproduce this issue? I tried and I can't.

> NullPointerException when saving project
> ----------------------------------------
>
>                 Key: CONTINUUM-1562
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-4
>         Environment: Windows 2004 server installation
>            Reporter: Kevin Christmas
>         Attachments: stacktrace.txt
>
>
> I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.
> When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CONTINUUM-1562) NullPointerException when saving project

Posted by "Kevin Christmas (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113596 ] 

Kevin Christmas commented on CONTINUUM-1562:
--------------------------------------------

I am struggling to recreate this issue with sample projects.

My company has a fairly large product that we've set up like this:

pom.xml
    libraries/pom.xml
        library1/pom.xml
        library2/pom.xml
        library3/pom.xml
        libraryN/pom.xml
    webmodules/pom.xml
        webmodule1/pom.xml
        webmodule2/pom.xml
        webmodule3/pom.xml
        webmoduleN/pom.xml

After initially adding the root pom.xml and letting continuum load and build the rest, adding a notifications section to the root pom.xml will place continuum in a state where none of the projects in the tree can be saved to the database.  Projects not in that inheritance chain will be unaffected, meaning you can still save them to the continuum database.

I can reproduce this error 100% of the time with my company's project.

I would love to scratch my own itch on this, but I'm struggling to see how the StoreManager on the StateManagerImpl class gets set in the first place.

> NullPointerException when saving project
> ----------------------------------------
>
>                 Key: CONTINUUM-1562
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-4
>         Environment: Windows 2004 server installation
>            Reporter: Kevin Christmas
>         Attachments: stacktrace.txt
>
>
> I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.
> When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CONTINUUM-1562) NullPointerException when saving project

Posted by "Kevin Christmas (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113543 ] 

Kevin Christmas commented on CONTINUUM-1562:
--------------------------------------------

I cloned CONTINUUM-1265 which seems to be the same issue.  I am currently using 1.1-beta-4 however.

This issue has been driving  me crazy for the last few days, but I think I've been able to figure out how to recreate it.

It problem manifests itself when you initially add a multi-module pom.xml file.  After all main project and sub projects (inherits from parent) loads, I add a notifications section to the parent pom.xml and commit it to subversion.  Continuum is unable to deal the added notifications section and neither the parent project or child projects can be saved.

> NullPointerException when saving project
> ----------------------------------------
>
>                 Key: CONTINUUM-1562
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-alpha-1
>         Environment: Windows 2004 server installation
>            Reporter: Kevin Christmas
>            Assignee: Emmanuel Venisse
>             Fix For: 1.1-beta-2
>
>         Attachments: stacktrace.txt
>
>
> I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.
> When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Issue Comment Edited: (CONTINUUM-1562) NullPointerException when saving project

Posted by "Kevin Christmas (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113596 ] 

Kevin Christmas edited comment on CONTINUUM-1562 at 11/12/07 4:40 PM:
----------------------------------------------------------------------

I am struggling to recreate this issue with sample projects.

My company has a fairly large product that we've set up like this:

pom.xml
----> libraries/pom.xml
---------> library1/pom.xml
---------> library2/pom.xml
---------> library3/pom.xml
---------> libraryN/pom.xml
----> webmodules/pom.xml
---------> webmodule1/pom.xml
---------> webmodule2/pom.xml
---------> webmodule3/pom.xml
---------> webmoduleN/pom.xml

After initially adding the root pom.xml and letting continuum load and build the rest, adding a notifications section to the root pom.xml will place continuum in a state where none of the projects in the tree can be saved to the database.  Projects not in that inheritance chain will be unaffected, meaning you can still save them to the continuum database.

I can reproduce this error 100% of the time with my company's project.

I would love to scratch my own itch on this, but I'm struggling to see how the StoreManager on the StateManagerImpl class gets set in the first place.


 was:
I am struggling to recreate this issue with sample projects.

My company has a fairly large product that we've set up like this:

pom.xml
    libraries/pom.xml
        library1/pom.xml
        library2/pom.xml
        library3/pom.xml
        libraryN/pom.xml
    webmodules/pom.xml
        webmodule1/pom.xml
        webmodule2/pom.xml
        webmodule3/pom.xml
        webmoduleN/pom.xml

After initially adding the root pom.xml and letting continuum load and build the rest, adding a notifications section to the root pom.xml will place continuum in a state where none of the projects in the tree can be saved to the database.  Projects not in that inheritance chain will be unaffected, meaning you can still save them to the continuum database.

I can reproduce this error 100% of the time with my company's project.

I would love to scratch my own itch on this, but I'm struggling to see how the StoreManager on the StateManagerImpl class gets set in the first place.

> NullPointerException when saving project
> ----------------------------------------
>
>                 Key: CONTINUUM-1562
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-4
>         Environment: Windows 2004 server installation
>            Reporter: Kevin Christmas
>         Attachments: stacktrace.txt
>
>
> I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.
> When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (CONTINUUM-1562) NullPointerException when saving project

Posted by "Kevin Christmas (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Christmas updated CONTINUUM-1562:
---------------------------------------

    Attachment: stacktrace.txt

> NullPointerException when saving project
> ----------------------------------------
>
>                 Key: CONTINUUM-1562
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1562
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-alpha-1
>         Environment: Windows 2004 server installation
>            Reporter: Kevin Christmas
>            Assignee: Emmanuel Venisse
>             Fix For: 1.1-beta-2
>
>         Attachments: stacktrace.txt
>
>
> I have three Continuum instances running now and for one of them there seems to be some state issue when attempting to add a module to a project group. There is no problem adding modules to the other two instances.
> When invoking this operation I get a NullPointerException (see the attachment).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira