[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18815:
----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> Include freemarker.jar in FreeMarker IDE as maven dependency
> ------------------------------------------------------------
>
> Key: JBIDE-18815
> URL: https://issues.jboss.org/browse/JBIDE-18815
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17550:
----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> When Install/Update button pressed no progress reported about installation preparation
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17550
> URL: https://issues.jboss.org/browse/JBIDE-17550
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Labels: f2f2014
> Fix For: 4.3.0.Alpha2
>
>
> When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls
> {code}
> computeInstallableUnits(monitor.newChild(50));
> {code}
> and
> {code}resolveInstall(monitor.newChild(50));{code}
> which can take considerable amount of time.
> I think progress for Preparation to install requested features should be visible in eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18876:
----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18876
> URL: https://issues.jboss.org/browse/JBIDE-18876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.3.0.Alpha2
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3319.
------------------------------
Resolution: Done
Resolving. Feel free to reopen if you're not happy with over-reporting. Note too that the size on disk of JBDS 8.1.0 is about 665M, but JBDS 9.0.0.Alpha1 is only 592M.
[~dgolovin] [~maxandersen] [~ldimaggio] Is that size drop expected?
> JBDS 9.0 installer underreports space requirement by 225 - 250MB
> ----------------------------------------------------------------
>
> Key: JBDS-3319
> URL: https://issues.jboss.org/browse/JBDS-3319
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.2.GA
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 9.0.0.Alpha1
>
>
> The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required:
> Disk Space:
> Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB
> The actual install uses this much:
> du -sh installdir/
> 822M installdir/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3320) JBDS 8.x installer underreports space requirement by 225 - 250MB
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3320?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3320:
----------------------------------
1. Installed jboss-devstudio-8.1.0.Beta1-v20150206-2121-B406-installer-standalone.jar
2. Reported by installer: *Required Disk Space: 666.22 MB*
3. Installed size on disk reported by `du -sch`: *665M*
So... I think we're good here.
Leaving open in case [~ldimaggio] or someone else in QE wants to run an install of the EAP bundled installer too.
> JBDS 8.x installer underreports space requirement by 225 - 250MB
> ----------------------------------------------------------------
>
> Key: JBDS-3320
> URL: https://issues.jboss.org/browse/JBDS-3320
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.2.GA
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 8.1.0.GA
>
>
> The installer instructs the user that this much disk space is required:
> Disk Space:
> Available Disk Space: 30.83 GB Required Disk Space: 426.22 MB
> When actually, this much disk space is required:
> du -sh installdir/
> 661M installdir/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3319 at 2/6/15 5:32 PM:
----------------------------------------------------------
Tycho problem solved.
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 666.25 MB*
3. Installed size on disk reported by `du -sch`: *592M*
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 825.81 MB*
3. Installed size on disk reported by `du -sch`: *769M*
So now we're over-reporting by ~7-10%, but that's certainly better than under-reporting, right?
was (Author: nickboldt):
Tycho problem solved.
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 666.25 MB*
3. Installed size on disk reported by `du -sch`: *592M*
So now we're over-reporting by ~10%, but that's certainly better than under-reporting, right?
> JBDS 9.0 installer underreports space requirement by 225 - 250MB
> ----------------------------------------------------------------
>
> Key: JBDS-3319
> URL: https://issues.jboss.org/browse/JBDS-3319
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.2.GA
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required:
> Disk Space:
> Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB
> The actual install uses this much:
> du -sh installdir/
> 822M installdir/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3319 at 2/6/15 5:32 PM:
----------------------------------------------------------
Tycho problem solved.
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 666.25 MB*
3. Installed size on disk reported by `du -sch`: *592M*
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-eap.jar.
2. Reported by installer: *Required Disk Space: 825.81 MB*
3. Installed size on disk reported by `du -sch`: *769M*
So now we're over-reporting by ~7-10%, but that's certainly better than under-reporting, right?
was (Author: nickboldt):
Tycho problem solved.
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 666.25 MB*
3. Installed size on disk reported by `du -sch`: *592M*
1. Installed jboss-devstudio-9.0.0.Alpha1-v20150206-1912-B2758-installer-standalone.jar.
2. Reported by installer: *Required Disk Space: 825.81 MB*
3. Installed size on disk reported by `du -sch`: *769M*
So now we're over-reporting by ~7-10%, but that's certainly better than under-reporting, right?
> JBDS 9.0 installer underreports space requirement by 225 - 250MB
> ----------------------------------------------------------------
>
> Key: JBDS-3319
> URL: https://issues.jboss.org/browse/JBDS-3319
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.2.GA
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required:
> Disk Space:
> Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB
> The actual install uses this much:
> du -sh installdir/
> 822M installdir/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months