[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20392:
------------------------------------
Can you see it as an installed PLUGIN, if not the feature? Could be some strange filtering that Eclipse does. Is that the only feature that's not shown? Can you compare the whole list of features installed on disk to those shown in the UI?
> Browsersim feature not shown in Installation details
> ----------------------------------------------------
>
> Key: JBIDE-20392
> URL: https://issues.jboss.org/browse/JBIDE-20392
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Fix For: 4.3.0.CR1
>
>
> I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features.
> In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2.
> Maybe there is an explanation for this, but I asked around and nobody knows why this happens.
> Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20392:
-------------------------------
Fix Version/s: 4.3.0.CR1
> Browsersim feature not shown in Installation details
> ----------------------------------------------------
>
> Key: JBIDE-20392
> URL: https://issues.jboss.org/browse/JBIDE-20392
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Fix For: 4.3.0.CR1
>
>
> I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features.
> In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2.
> Maybe there is an explanation for this, but I asked around and nobody knows why this happens.
> Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20392:
----------------------------------
Assignee: Nick Boldt
> Browsersim feature not shown in Installation details
> ----------------------------------------------------
>
> Key: JBIDE-20392
> URL: https://issues.jboss.org/browse/JBIDE-20392
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.3.0.CR1
>
>
> I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features.
> In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2.
> Maybe there is an explanation for this, but I asked around and nobody knows why this happens.
> Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20208:
------------------------------------
Sorry, I was looking at the jar w/ Beyond Compare which was filtering it out of the view. :( So, I DO now see the file and it has the correct updated license address:
{code}
... For precise licensing details, consult the corresponding
source code, or contact Red Hat, Attn: General Counsel,
100 East Davie St., Raleigh NC 27601 USA. ...{code}
If the problem is that there's no longer a LINK to the file, then we can fix that by adding it back into feature.xml like this:
https://github.com/jbosstools/jbosstools-base/commit/3db3133fd026233daf4e...
{code}- <license>%license</license>
+ <license url="license.html">%license</license>{code}
> For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20208
> URL: https://issues.jboss.org/browse/JBIDE-20208
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.CR1
>
> Attachments: birt-no-license.png
>
>
> For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here:
> https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to...
> 2. Resolve this JIRA when done. QE can then verify and close it later.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20208 at 7/28/15 10:17 AM:
--------------------------------------------------------------
Sorry, I was looking at the jar w/ Beyond Compare which was filtering it out of the view. :( So, I DO now see the file and it has the correct updated license address:
{code}
... For precise licensing details, consult the corresponding
source code, or contact Red Hat, Attn: General Counsel,
100 East Davie St., Raleigh NC 27601 USA. ...{code}
If the problem is that there's no longer a LINK to the file, then we can *probably* fix that by adding it back into feature.xml like this:
https://github.com/jbosstools/jbosstools-base/commit/3db3133fd026233daf4e...
{code}- <license>%license</license>
+ <license url="license.html">%license</license>{code}
was (Author: nickboldt):
Sorry, I was looking at the jar w/ Beyond Compare which was filtering it out of the view. :( So, I DO now see the file and it has the correct updated license address:
{code}
... For precise licensing details, consult the corresponding
source code, or contact Red Hat, Attn: General Counsel,
100 East Davie St., Raleigh NC 27601 USA. ...{code}
If the problem is that there's no longer a LINK to the file, then we can fix that by adding it back into feature.xml like this:
https://github.com/jbosstools/jbosstools-base/commit/3db3133fd026233daf4e...
{code}- <license>%license</license>
+ <license url="license.html">%license</license>{code}
> For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20208
> URL: https://issues.jboss.org/browse/JBIDE-20208
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.CR1
>
> Attachments: birt-no-license.png
>
>
> For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here:
> https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to...
> 2. Resolve this JIRA when done. QE can then verify and close it later.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20394:
------------------------------------
Re: #1, the alternative solution is to build the whole project locally, THEN just run the test you want. But I suppose that's equivalent to resolving deps from the latest nightly, too.
How about if we have a *jbosstools-integrationtests-site* profile for this, which is enabled by default, but when run in Jenkins we disable it so that it's ONLY using local sources to resolve deps instead of this "self-bootstrapped" approach? Thus in Jenkins:
{code}mvn install -P!jbosstools-integrationtests-site{code}
Does that work for a profile name? We could call it "bootstrap" "nightly" "circular" ...
Or we could use the "hudson" profile (already in use in parent pom for other purposes) to set $\{jbosstools-integrationtests-site} to $\{jbosstools-site} so that it's effectively disabled.
> jbosstools integration tests site depends on itself to build; site is not self-cleaning
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20394
> URL: https://issues.jboss.org/browse/JBIDE-20394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> I've found some problems today:
> 1. building JBT integration tests requires the JBT integration tests site [circular dependency]
> {code}
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> {code}
> 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1]
> [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas...
> 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts.
> [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time.
> 5. The check that the build does to determine if it should publish the new bits is failing to find the check script.
> 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical.
> [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> This is because we have symlinks:
> {code}
> updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/
> updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/
> {code}
> So this is OK but we should migrate to use the new correct URLs instead of the old ones.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-20208 at 7/28/15 10:06 AM:
-----------------------------------------------------------------
[~nickboldt], I have JBoss Tools 4.3.0.Beta2 installed and I can see the license.html file inside Eclipse-jbt-4.3.0.Beta2-66.app/Contents/Eclipse/features/org.jboss.tools.birt.feature_1.8.0.Beta2-v20150716-2053-B23 .
Also, I clicked on your link to the jar above and I can see the license.html file inside that jar once I downloaded, so not sure why you can't see it.
BTW, the same applies for Browsersim, which also migrated to the license feature and yet the license.html file is included in the feature.
was (Author: mmalina):
[~nickboldt], I have JBoss Tools 4.3.0.Beta2 installed and I can see the license.html file inside Eclipse-jbt-4.3.0.Beta2-66.app/Contents/Eclipse/features/org.jboss.tools.birt.feature_1.8.0.Beta2-v20150716-2053-B23 .
Also, I clicked on your link to the jar above and I can see the license.html file inside that jar once I downloaded, so not sure why you can't see it.
> For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt]
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20208
> URL: https://issues.jboss.org/browse/JBIDE-20208
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.CR1
>
> Attachments: birt-no-license.png
>
>
> For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here:
> https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to...
> 2. Resolve this JIRA when done. QE can then verify and close it later.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20394:
---------------------------------------
[~nickboldt], thanks for spotting and helping with this.
1. [circular dependency]
At least it uses the same stream's url, so that's good :)
The reason for this is that we want to be able to checkout the git repo, go to a test plugin's directory, and run the given test using "mvn verify" - it will then get other dependencies from integration tests (if there are any) from the repo url.
I know that it seems like a circular dependency, but I thought that it shouldn't really be a problem when you build the whole repo in the root dir - everything should be built inside the reactor, no? Apparently it doesn't work that way?
But either way, where did the CR1 bits appear from? I know that we previously discussed the practice that to populate the 4.3.mars repo, you copy the contents from master, but I thought we don't do it anymore.
Your PR looks good, but it should be pushed to both Beta2x branch and master, right?
> jbosstools integration tests site depends on itself to build; site is not self-cleaning
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20394
> URL: https://issues.jboss.org/browse/JBIDE-20394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> I've found some problems today:
> 1. building JBT integration tests requires the JBT integration tests site [circular dependency]
> {code}
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> {code}
> 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1]
> [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas...
> 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts.
> [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time.
> 5. The check that the build does to determine if it should publish the new bits is failing to find the check script.
> 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical.
> [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t...
> [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3...
> This is because we have symlinks:
> {code}
> updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/
> updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/
> {code}
> So this is OK but we should migrate to use the new correct URLs instead of the old ones.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months