[
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
