Hey guys,
Looks like a bug here. Sorry! I've started a JIRA to track this issue:
https://issues.jboss.org/browse/FORGE-412
I'm guessing it's an issue on how the module.xml stream is being opened,
with regard to modularity, but not exactly sure, will have to debug.
~Lincoln
On Mon, Dec 19, 2011 at 3:49 PM, Daniel Sachse
<sachsedaniel(a)googlemail.com>wrote:
Hey Ryan,
yeah, I also noticed it. I also posted it with a little more details
yesterday here:
http://lists.jboss.org/pipermail/forge-dev/2011-December/001435.html
As one can see from the stacktrace, some stream is null in the XMLParser.
Regards,
Daniel
On 19.12.2011, at 20:03, Ryan Bradley <rbradley(a)redhat.com> wrote:
> Hi all,
>
> I just updated the plugin I am developing for Forge to use 1.0.0.Beta4.
> The plugin builds successfully; however, I run into problems when the
> plugin is being installed. Specifically, when the module.xml file is
> being written, I get the following error: "Could not import XML from
> stream". As well, because of the stage of failure, there is change
> registered to ~/.forge/plugins/installed.xml.
>
> Has anybody else run into this problem with the new version of Forge (or
> previous versions as well)? Also, what might help me figure out the
> issue is if there was detailed logging of the install process that I
> could examine somewhere.
>
> Thanks,
> Ryan
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"