[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ]
Tom Cunningham commented on JBTIS-165:
--------------------------------------
Makes sense to me that attachments should be in esbcontent or src. Not sure why this bug is a blocker if it is not a regression.
> Regression - Cannot add a file to the attachments
> -------------------------------------------------
>
> Key: JBTIS-165
> URL: https://issues.jboss.org/browse/JBTIS-165
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.1.2
> Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Attachments: esb_attachment_bug.png, test.zip
>
>
> Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15147) Livereload server shows restart status when it is used by BrowserSim
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15147:
----------------------------------
Comment: was deleted
(was: Steps to reproduce with JBT Alpha1-v20130909-0110-B392:
1. Import HTML5 project from JBoss Central
2. Run HTML5 project on server
3. Open HTML5project using Server view context menu Show in > Web Server via LiveReload Server
4. Choose Yes to inject Livereload.js script
ASSERT: Live Reload Server status is [Started]
5. Update index.html file within VPE editor and save changes
ASSERT: Live Reload Server status is [Started, Synchronized]
6. Stop Live Reload Server
ASSERT: Live Reload Server status is [Stopped, Synchronized]
7. Repeat steps 3., 4. and 5.
ERROR: Live Reload Server status is [Started, Restart]
8. Close Web Server
9. Repeat step 5.
ASSERT: Live Reload Server is [Started])
> Livereload server shows restart status when it is used by BrowserSim
> --------------------------------------------------------------------
>
> Key: JBIDE-15147
> URL: https://issues.jboss.org/browse/JBIDE-15147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.CR1
> Environment: Win7 64, Eclipse + JBT
> Reporter: Konstantin Marmalyukov
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.1.Alpha2
>
> Attachments: livereload_bug.png
>
>
> I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-165:
-----------------------------------------
I'm guessing that the folders must be on the classpath for the project, which is why it's limited to esbcontent and src.
[~tcunning] Can you verify that any attachments must be in the project classpath?
> Regression - Cannot add a file to the attachments
> -------------------------------------------------
>
> Key: JBTIS-165
> URL: https://issues.jboss.org/browse/JBTIS-165
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.1.2
> Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Attachments: esb_attachment_bug.png, test.zip
>
>
> Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15147) Livereload server shows restart status when it is used by BrowserSim
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15147:
----------------------------------
Steps to Reproduce:
Steps to reproduce with JBT Alpha1-v20130909-0110-B392:
1. Import HTML5 project from JBoss Central
2. Run HTML5 project on server
3. Open HTML5project using Server view context menu Show in > Web Server via LiveReload Server
4. Choose Yes to inject Livereload.js script
ASSERT: Live Reload Server status is [Started]
5. Update index.html file within VPE editor and save changes
ASSERT: Live Reload Server status is [Started, Synchronized]
6. Stop Live Reload Server
ASSERT: Live Reload Server status is [Stopped, Synchronized]
7. Repeat steps 3., 4. and 5.
ERROR: Live Reload Server status is [Started, Restart]
8. Close Web Server
9. Repeat step 5.
ASSERT: Live Reload Server is [Started]
> Livereload server shows restart status when it is used by BrowserSim
> --------------------------------------------------------------------
>
> Key: JBIDE-15147
> URL: https://issues.jboss.org/browse/JBIDE-15147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.CR1
> Environment: Win7 64, Eclipse + JBT
> Reporter: Konstantin Marmalyukov
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.1.Alpha2
>
> Attachments: livereload_bug.png
>
>
> I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-171:
----------------------------------
The above site is simply for testing purposes, so that you can resolve a given (any!) version of JBT and JBTIS or JBDS and JBDS IS from a single URL. Makes explaining to QE which version(s) to combine a whole lot simpler than to have to feed in multiple -Dflags when launching JBT or JBDS.
Once we release, we have full control over which site(s) are listed in the discovery plugins (one for core and one for IS). In fact, the URLs are hardcoded in the plugins, so there's no mystery at all.
Or to put it another way, "Trust me, this works." (Want proof? See JBDS Core 5 + JBDS SOA Tooling 5.)
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ]
Viacheslav Kabanovich commented on JBTIS-165:
---------------------------------------------
Yes, it has always been this way. Should not the location of project root be added to list of web roots to make its resources accessible?
> Regression - Cannot add a file to the attachments
> -------------------------------------------------
>
> Key: JBTIS-165
> URL: https://issues.jboss.org/browse/JBTIS-165
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.1.2
> Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Attachments: esb_attachment_bug.png, test.zip
>
>
> Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ]
Viacheslav Kabanovich edited comment on JBTIS-165 at 9/17/13 11:55 AM:
-----------------------------------------------------------------------
Yes, it has always been this way. Should not the location of project root be added to the list of web roots to make its resources accessible?
was (Author: scabanovich):
Yes, it has always been this way. Should not the location of project root be added to list of web roots to make its resources accessible?
> Regression - Cannot add a file to the attachments
> -------------------------------------------------
>
> Key: JBTIS-165
> URL: https://issues.jboss.org/browse/JBTIS-165
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.1.2
> Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Attachments: esb_attachment_bug.png, test.zip
>
>
> Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months