[JBoss JIRA] (JBIDE-11041) It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously
by bin zhao (JIRA)
bin zhao created JBIDE-11041:
--------------------------------
Summary: It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously
Key: JBIDE-11041
URL: https://issues.jboss.org/browse/JBIDE-11041
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
64 Bit
Reporter: bin zhao
Assignee: Andre Dietisheim
Priority: Critical
1. Create a new Openshift application for example: phptest
2. nested rockmongo-1.1 and mongodb-2.0 to the application of the php type
3. Edit the application and select mongodb-2.0 and rockmongo-1.1 from the embeddable cartridge and click 'Finish'.
Notes:
It has also the same issue for nested rockmongo-1.1 individually.
Actual Result:
It will popup "problem occured" dialog...
Expect Result:
For individually nested rockmongo, it should popup "warning dialog" said that Mongodb must be embedded before rockmongo.
For simultaneously nested mongodb and rockmongo, it should be successful without any error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-10197) Deployment assembly missbehaves - workaround with fileset
by Dirk Dollar (Created) (JIRA)
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Minor
This is my first bugreport... if I'm doing something wrong or chose the wrong component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving similarly (but differnt) to older versions when it was used under a different name (J2EE module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or more accurately - under certain circumstances it will stop working. E.g. I think after adding some additional libraries to deploy to webcontent/lib. I suspect the problem is that it gets deleted before deploying. The workaround for me was to use a fileset of the <projectname>/WebContent folder and to point it to an empty deploy path - and to scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
by Nick Boldt (JIRA)
improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and "it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know "locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months