[JBoss JIRA] (JBTIS-163) Failed to resolve target definition
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTIS-163:
-----------------------------------------------
Marek Baluch <mbaluch(a)redhat.com> changed the Status of [bug 1005683|https://bugzilla.redhat.com/show_bug.cgi?id=1005683] from ON_QA to VERIFIED
> Failed to resolve target definition
> -----------------------------------
>
> Key: JBTIS-163
> URL: https://issues.jboss.org/browse/JBTIS-163
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.1.5.Alpha1-TP
>
>
> During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error:
> [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1]
--
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-15398) CDI Builder is sloooow
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-15398 at 9/16/13 7:44 PM:
-----------------------------------------------------------------
Building wildfly projects takes less than a minute in my environment with 1GB + Slava's fix and without m2e plugins at all (I disabled m2e 1.4 after importing the projects with 4GB of memory).
We have not tried m2e 1.5 yet to make sure it leaves enough memory for CDI (and JDT).
was (Author: akazakov):
Building wildfly projects takes less than a minute in my environment with 1GB + Slava's fix and without m2e plugins at all (I disabled m2e 1.4 after importing the projects with 4GB of memory).
We have not tried m2e 1.5 yet to make sure it leave enough memory for CDI (and JDT).
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:38 PM:
------------------------------------------------------------------------
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in
!MemoryUsedWithNewMaven.png|thumbnail!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
I had to kill Eclipse.
When run with 1.5Gb, build stuck at 100%, I had to kill Eclipse again.
When run with 1.8Gb, build passed in 10 minutes, on the verge of memory. I did a few modifications on files, then clean build on a few projects. After that I might believe that Maven released some memory used in build of workspace. Memory usage after all builds were completed is shown in
!MemoryUsedWithNewMavenAfterBuild.png|thumbnail!
It seems that Maven still keeps all grabbed memory.
My general impression is that Maven 1.5 takes *more* memory than Maven 1.4. With maven 1.4 I was able to do clean/build of wildfly workspace in 5 minutes.
was (Author: scabanovich):
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png|thumbnail!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:38 PM:
------------------------------------------------------------------------
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in
!MemoryUsedWithNewMaven.png|thumbnail!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
I had to kill Eclipse.
When run with 1.5Gb, build stuck at 100%, I had to kill Eclipse again.
When run with 1.8Gb, build passed in 10 minutes, on the verge of memory. I did a few modifications on files, then clean build on a few projects. After that I might believe that Maven released some memory used in build of workspace. Memory usage after all builds were completed is shown in
!MemoryUsedWithNewMavenAfterBuild.png|thumbnail!
It seems that Maven still keeps all grabbed memory.
My general impression is that Maven 1.5 takes *more* memory than Maven 1.4. With maven 1.4 I was able to do clean/build of wildfly workspace in 5 minutes with 1.5Gb.
was (Author: scabanovich):
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in
!MemoryUsedWithNewMaven.png|thumbnail!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
I had to kill Eclipse.
When run with 1.5Gb, build stuck at 100%, I had to kill Eclipse again.
When run with 1.8Gb, build passed in 10 minutes, on the verge of memory. I did a few modifications on files, then clean build on a few projects. After that I might believe that Maven released some memory used in build of workspace. Memory usage after all builds were completed is shown in
!MemoryUsedWithNewMavenAfterBuild.png|thumbnail!
It seems that Maven still keeps all grabbed memory.
My general impression is that Maven 1.5 takes *more* memory than Maven 1.4. With maven 1.4 I was able to do clean/build of wildfly workspace in 5 minutes.
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:31 PM:
------------------------------------------------------------------------
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png|thumbnail!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
was (Author: scabanovich):
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-15398:
------------------------------------------
Attachment: MemoryUsedWithNewMavenAfterBuild.png
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15398) CDI Builder is sloooow
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:28 PM:
------------------------------------------------------------------------
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
was (Author: scabanovich):
I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above).
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png!
Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min
--
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-15348) when hyperlinked file does not exist offer to create one
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15348?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15348:
-----------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.2.x)
> when hyperlinked file does not exist offer to create one
> --------------------------------------------------------
>
> Key: JBIDE-15348
> URL: https://issues.jboss.org/browse/JBIDE-15348
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
> Attachments: CreateFileHyperlink.png, Question.png
>
>
> When Ctrl+clicking on app.js in this snippet:
> <script type="text/javascript" src="js/app.js"></script>
> And the file js/app.js does not exist eclipse just "blinks".
> Better if we could offer creating the file, even just a blank/empty one.
> The same goes for image and css references, all those would be nice not having to go through the full ctrl+N wizard to just create such files.
--
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