[JBoss JIRA] (JBIDE-13535) Wrong bom version is required
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13535?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-13535.
-----------------------------------------
Resolution: Done
this is now fixed in JDF-230 and I verified it works afaics.
> Wrong bom version is required
> -----------------------------
>
> Key: JBIDE-13535
> URL: https://issues.jboss.org/browse/JBIDE-13535
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> Java EE Web Project has bom version always set to 1.0.4.Final-redhat-1 (which is version from EAP6.1) even if runtime is set to 6.0 or 6.0.1
> for HTML5 and Richfaces project it is the same, just the version is always set to 1.0.2.Final-redhat-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
13 years, 1 month
[JBoss JIRA] (JBIDE-13706) Cannot install Google tools from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13706?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13706:
------------------------------------
[~mickael_istria] FYI: you need to push the updated site to devstudio.jboss.com too, or else JBDS-2494 will happen. I've updated the devstudio mirror now.
> Cannot install Google tools from Central
> ----------------------------------------
>
> Key: JBIDE-13706
> URL: https://issues.jboss.org/browse/JBIDE-13706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Here is what log says:
> {code}
> Contains: Cannot complete the install because one or more required items could not be found.
> Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
> Contains: Cannot satisfy dependency:
> Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
> {code}
> Main message: *requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found*
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13599:
------------------------------------
[~maxandersen], [~snjeza] The recursive usecase is bupkis. All connectors in Central are pulled from the same URL (which is a composite site of various mirrors + JBT/JBDS core site + target platform). And before Max says that's not true, the exception to this rule is JRebel and Android, which have their own sites. But everything else comes from A SINGLE URL. There's no need for recursive replacements.
All we need is this:
{code:commandline override when testing a particular site}
-Djboss.central.site.url=http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1c.core/
or
-Djboss.central.site.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/
{code}
{code:plugin.properties w/ default URL}
siteUrl=${jboss.central.site.url:http://download.jboss.org/jbosstools/upd...
or
siteUrl=${jboss.central.site.url=https://devstudio.jboss.com/updates/7.0-...
{code}
{code:plugin.xml w/ variable}
siteUrl=%siteUrl
{code}
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13599 at 3/7/13 12:46 PM:
-------------------------------------------------------------
actually, according to dmlloyd: $\{foo,bar:default value\} would work.
was (Author: maxandersen):
actually, according to dmlloyd: ${foo,bar:default value} would work.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13718) Publish script fails for new components
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13718?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13718:
------------------------------------
Fixed by redirecting error code, so publish no longer fails if log not already present:
{code:title=https://github.com/jbosstools/jbosstools-build-ci/pull/33}
-PREV_REV=`wget ${wgetParams} -O - http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/logs/ALL_...
-if [[ ! ${PREV_REV} ]] || [[ ! ${PREV_REV%%*404*} ]]; then
+ PREV_REV=`wget ${wgetParams} -O - http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/logs/ALL_... && echo "found" || echo "not found"`
+ if [[ ! ${PREV_REV} ]] || [[ ! ${PREV_REV%%*not found*} ]]; then
{code}
{code}
+++ wget --timeout=900 --wait=10 --random-wait --tries=10 --retry-connrefused --no-check-certificate -O - http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m...
--2013-03-07 11:45:46-- http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m...
Resolving download.jboss.org... 64.208.159.26, 64.208.159.50
Connecting to download.jboss.org|64.208.159.26|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-03-07 11:45:46 ERROR 404: Not Found.
+++ echo 'not found'
++ PREV_REV='not found'
++ [[ ! -n not found ]]
++ [[ ! -n '' ]]
++ echo 'No previous log in http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m...'
No previous log in http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m...
{code}
> Publish script fails for new components
> ---------------------------------------
>
> Key: JBIDE-13718
> URL: https://issues.jboss.org/browse/JBIDE-13718
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
>
> While trying to publish the new "jbosstools-aerogear" component nightly site, the publish script fails telling
> {code}
> + cd /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/cordova
> + wget http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publi... -q --no-check-certificate -N
> + . publish.sh
> +++ mktemp -d
> ++ tmpdir=/tmp/tmp.DUivo13746
> ++ mkdir -p /tmp/tmp.DUivo13746
> ++ STAGINGDIR=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master
> ++ PUBLISHPATHSUFFIX=
> ++ [[ -n '' ]]
> ++ JOBNAMEREDUX=jbosstools-aerogear_master
> ++ JOBNAMEREDUX=aerogear_master
> ++ [[ '' == \Y\e\s ]]
> ++ ZIPSUFFIX=SNAPSHOT
> ++ SNAPNAME=jbosstools-aerogear_master-Update-SNAPSHOT.zip
> ++ SRCSNAME=jbosstools-aerogear_master-Sources-SNAPSHOT.zip
> ++ SUFFNAME=-Update-SNAPSHOT.zip
> ++ [[ '' == '' ]]
> ++ DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools
> ++ [[ '' == '' ]]
> ++ INTRNALDEST=/home/hudson/static_build_env/jbds
> ++ rm -fr /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master
> ++ z=
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/aggregate/site/target ]]
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/aggregate/site/site/target ]]
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/site/target ]]
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ bl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> ++ rm -f /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> ++ wget -q http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/consol... -O /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt --timeout=900 --wait=10 --random-wait --tries=10 --retry-connrefused --no-check-certificate
> +++ cat /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> +++ grep org/jboss/tools/parent/
> +++ head -1
> +++ sed -e 's#.\+org/jboss/tools/parent/\(.\+\)/\(maven-metadata.xml\|parent.\+\)#\1#'
> +++ sed -e s#-SNAPSHOT##
> +++ sed -e 's#[0-9].[0-9].[0-9].##'
> ++ BUILD_ALIAS=Alpha1
> ++ wgetParams='--timeout=900 --wait=10 --random-wait --tries=30 --retry-connrefused --no-check-certificate --server-response'
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ rl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/REVISION
> +++ find /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master -mindepth 2 -maxdepth 3 -name .git
> ++ [[ -n /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/.git ]]
> ++ rl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION
> ++ rm -f /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.txt /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml
> ++ wget -O /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml 'http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/api/xm...' --timeout=900 --wait=10 --random-wait --tries=30 --retry-connrefused --no-check-certificate --server-response
> --2013-03-05 07:00:07-- http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/api/xm...
> Resolving hudson.qa.jboss.com... 10.16.90.43
> Connecting to hudson.qa.jboss.com|10.16.90.43|:80... connected.
> HTTP request sent, awaiting response...
> HTTP/1.1 200 OK
> Date: Tue, 05 Mar 2013 12:00:07 GMT
> X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
> Content-Type: application/xml;charset=UTF-8
> Connection: close
> Length: unspecified [application/xml]
> Saving to: `/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml'
> 0K 34.5M=0s
> 2013-03-05 07:00:07 (34.5 MB/s) - `/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml' saved [193]
> ++ sed -e 's#<lastBuiltRevision><SHA1>\([a-f0-9]\+\)</SHA1><branch><SHA1>\([a-f0-9]\+\)</SHA1><name>\([^<>]\+\)</name></branch></lastBuiltRevision>#\3\@\1#g' /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml
> ++ sed -e 's#<[^<>]\+>##g'
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ ALLREVS=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/ALL_REVISIONS.txt
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> ++ [[ '' != \t\r\u\e ]]
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> +++ find /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master -mindepth 2 -maxdepth 3 -name .git
> ++ [[ -n /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/.git ]]
> +++ wget -nc -q -k http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m... -O -
> ++ PREV_REV=
> Build step 'Execute shell' marked build as failure
> {code}
> It looks like the publish.sh script except a previous version to be already available.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13752) New Footer wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-13752:
---------------------------------------------
Summary: New Footer wizard
Key: JBIDE-13752
URL: https://issues.jboss.org/browse/JBIDE-13752
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.1.0.Alpha2
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-2494) Cannot install GWT Designer - missing org.eclipse.wb.core.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2494?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-2494:
--------------------------------
Assignee: Martin Malina (was: Nick Boldt)
Bounce to Martin to try again when server is refreshed in about 30 mins.
> Cannot install GWT Designer - missing org.eclipse.wb.core.xml
> -------------------------------------------------------------
>
> Key: JBDS-2494
> URL: https://issues.jboss.org/browse/JBDS-2494
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyDependencies, Build
> Affects Versions: 7.0.0.Alpha1
> Environment: JBDS 7.0.0.Alpha1c
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 7.0.0.Alpha2
>
>
> I am unable to install GWT plugins including GWT Designer.
> Because of JBDS-2469 I am trying to use normal update sites and not JBoss Central.
> I have these update sites added:
> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4...
> http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.c...
> https://devstudio.jboss.com/updates/7.0-staging/extras/
> Then I go to Help -> Install New Software... and select the extras update site.
> I uncheck "Group items by category" and manually select all Google/GWT and Window Builder (which is needed for Google Designer).
> Then I am given this error:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919)
> Missing requirement: WindowBuilder Core for XML GUI's 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml 1.5.2.r42x201302111919) requires 'bundle org.eclipse.wb.core.java 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919)
> To: org.eclipse.wb.core.xml [1.5.2.r42x201302111919]
> {code}
> So the missing dependency is org.eclipse.wb.core.xml. Shouldn't that be on the target platform? Am I doing something wrong?
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-13346.
---------------------------------
I cannot replicate this in JBDS 7.0.0.Alpha1c, but neither could I in JBDS 6.0.0.GA.
Feel free to reopen if you can still see the problem after the fix.
Closing.
> DirectoryScanner fails on non-existing folders
> ----------------------------------------------
>
> Key: JBIDE-13346
> URL: https://issues.jboss.org/browse/JBIDE-13346
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives, JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows XP/Windows 7
> Eclipse 4.3M4
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: org.eclipse.wst.common.component
>
>
> DirectoryScanner can be made to fail on non-existing folders.
> In our setup, these folders are possibly picked up from the Deployment Assembly settings.
> The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse.
> But it seems the Archive DirectoryScanner runs before our builder.
> The stack trace looks like this:
>
> {code}
> java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552)
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588)
> at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow
by Guillaume Radde (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ]
Guillaume Radde commented on JBIDE-13703:
-----------------------------------------
I attached a screenshot of the "Open Project" workflow in Netbeans for comparison. It's a simple File selector panel. Folders that are recognized as project by one of the plugins show a different icons (like the "Ma" for maven projects in the screenshot). This is achieved using their [Project Factory API|http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-projectapi/...]
> Team - Verify the workflow
> --------------------------
>
> Key: JBIDE-13703
> URL: https://issues.jboss.org/browse/JBIDE-13703
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG
>
>
> The average end-user would like to:
> 1) check out (clone) a project from CVS, SVN or Git
> -- add repo, navigate repo, check out a project
> -- project may or may not have .classpath, .project or .settings files
> -- project may be Maven-based
> and see if the following work
> 2) Are the appropriate facets enabled?
> 3) Does it build immediately?
> 4) Can I immediately hit the run button to launch it on my app server?
> 5) Can I immediately hit the debug button to debug it on my app server?
> -- how do I step if there are no break points?
> 6) Make a change to a file, re-run/debug again
> 7) Run JUnit tests
> 8) Check the change back into the repo with comments
--
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
13 years, 1 month