[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13869:
----------------------------------------
Not sure it can works when going into an integration-test folder.
Have you tried getting directly in an "eclipse-test-plugin" module and run it?
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13869
> URL: https://issues.jboss.org/browse/JBIDE-13869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test.
> 2) use something else than surefire to run the already built testsuites.
--
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, 5 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-14544:
--------------------------------------
Inconsistent behavior is being observed across different platforms, configurations, machines.
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> 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
12 years, 5 months
[JBoss JIRA] (JBIDE-15295) EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15295?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated JBIDE-15295:
--------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1028053
> EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
> -------------------------------------------------------------------------
>
> Key: JBIDE-15295
> URL: https://issues.jboss.org/browse/JBIDE-15295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.1.CR1
>
> Attachments: Maven_EAP61.png, Maven_warning.png, settings.xml
>
>
> For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.
> The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.
> Attached are:
> * my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
> * screenshot of added EAP 6.1 maven repo
> * Screenshot of enterprise maven repo warning in Java EE Web Project wizard
--
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, 5 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2710 at 11/7/13 9:47 AM:
-----------------------------------------------------------
As of Nov 6, we're down to these 4 pending reviews/updates (Quick Search has been deferred to JBDS 8):
* JBDS-2801 GWT 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43
* JBDS-2802, JBDS-2808 SpringIDE 3.4.0.201310051539-RELEASE ... will be added today (Nov 7)
* JBDS-2709 Subclipse/SVNKit 1.10_1.8 _waiting on their Final release (currently at 1.8.0-rc1)_
was (Author: nickboldt):
As of Nov 6, we're down to these 4 pending reviews/updates (Quick Search has been deferred to JBDS 8):
* JBDS-2801 GWT 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43
* JBDS-2802, JBDS-2808 SpringIDE 3.4.0.201310051539-RELEASE ... vetting in progress.
* JBDS-2709 Subclipse/SVNKit 1.10_1.8 _waiting on their Final release (currently at 1.8.0-rc1)_
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> *New* connector for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> *CR1 or GA, TBD*
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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, 5 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2710 at 11/7/13 9:47 AM:
-----------------------------------------------------------
As of Nov 6, we're down to these 3 pending reviews/updates (Quick Search has been deferred to JBDS 8):
* JBDS-2801 GWT 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43
* JBDS-2802, JBDS-2808 SpringIDE 3.4.0.201310051539-RELEASE ... will be added today (Nov 7)
* JBDS-2709 Subclipse/SVNKit 1.10_1.8 _waiting on their Final release (currently at 1.8.0-rc1)_
was (Author: nickboldt):
As of Nov 6, we're down to these 4 pending reviews/updates (Quick Search has been deferred to JBDS 8):
* JBDS-2801 GWT 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43
* JBDS-2802, JBDS-2808 SpringIDE 3.4.0.201310051539-RELEASE ... will be added today (Nov 7)
* JBDS-2709 Subclipse/SVNKit 1.10_1.8 _waiting on their Final release (currently at 1.8.0-rc1)_
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> *New* connector for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> *CR1 or GA, TBD*
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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, 5 months
[JBoss JIRA] (JBDS-2823) Scripted install is broken on windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2823?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2823 at 11/7/13 9:41 AM:
-----------------------------------------------------------
Looks like two issues:
a) you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
b) I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
Since you do not, you need to pass in your JDK 6 path to the script. I would add a check for "is this a valid JDK path?" but I don't know how to parse your PATH on windows to check for a valid JDK path in there.
FWIW, this limitation is stated on the usage page:
{quote}
Note that you can either specify a Java developer kit or use the default one in the script (c:\progra~1\java\jre7\bin\java for Microsoft Windows operating systems or /usr/bin/java for OS X and Linux-based operating systems).
{quote}
was (Author: nickboldt):
Looks like the problem is that you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
Also, I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
If you do not, then I need to add another check to verify that's a valid path.
FWIW, this limitation is stated ON the usage page:
{quote}
Note that you can either specify a Java developer kit or use the default one in the script (c:\progra~1\java\jre7\bin\java for Microsoft Windows operating systems or /usr/bin/java for OS X and Linux-based operating systems).
{quote}
> Scripted install is broken on windows
> -------------------------------------
>
> Key: JBDS-2823
> URL: https://issues.jboss.org/browse/JBDS-2823
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.Beta1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
> Attachments: jbds-install-script-fail.png
>
>
> Please see screenshot attached for more details.
> Script used: https://devstudio.jboss.com/usage/scripted-install/jbds-install.cmd
--
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, 5 months
[JBoss JIRA] (JBDS-2823) Scripted install is broken on windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2823?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2823 at 11/7/13 9:41 AM:
-----------------------------------------------------------
Looks like two issues:
a) you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
b) I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
Since you do not, you need to pass in your JDK 6 path to the script. I would add a check for "is this a valid JDK path?" but I don't know how to parse your PATH on windows to check for a valid JDK path in there.
FWIW, this limitation is stated on the usage page [1]:
{quote}
Note that you can either specify a Java developer kit or use the default one in the script (c:\progra~1\java\jre7\bin\java for Microsoft Windows operating systems or /usr/bin/java for OS X and Linux-based operating systems).
{quote}
[1] https://devstudio.jboss.com/usage/scripted-install/
was (Author: nickboldt):
Looks like two issues:
a) you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
b) I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
Since you do not, you need to pass in your JDK 6 path to the script. I would add a check for "is this a valid JDK path?" but I don't know how to parse your PATH on windows to check for a valid JDK path in there.
FWIW, this limitation is stated on the usage page:
{quote}
Note that you can either specify a Java developer kit or use the default one in the script (c:\progra~1\java\jre7\bin\java for Microsoft Windows operating systems or /usr/bin/java for OS X and Linux-based operating systems).
{quote}
> Scripted install is broken on windows
> -------------------------------------
>
> Key: JBDS-2823
> URL: https://issues.jboss.org/browse/JBDS-2823
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.Beta1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
> Attachments: jbds-install-script-fail.png
>
>
> Please see screenshot attached for more details.
> Script used: https://devstudio.jboss.com/usage/scripted-install/jbds-install.cmd
--
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, 5 months
[JBoss JIRA] (JBDS-2823) Scripted install is broken on windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2823?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2823 at 11/7/13 9:39 AM:
-----------------------------------------------------------
Looks like the problem is that you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
Also, I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
If you do not, then I need to add another check to verify that's a valid path.
FWIW, this limitation is stated ON the usage page:
{quote}
Note that you can either specify a Java developer kit or use the default one in the script (c:\progra~1\java\jre7\bin\java for Microsoft Windows operating systems or /usr/bin/java for OS X and Linux-based operating systems).
{quote}
was (Author: nickboldt):
Looks like the problem is that you have no writeable c:\temp folder, so the script can't create c:\temp\%installDir%.install.xml.
Also, I've assumed that you have JDK 7 installed here:
set JREPATH=c:\Progra~1\java\jre7\bin\java
If you do not, then I need to add another check to verify that's a valid path.
> Scripted install is broken on windows
> -------------------------------------
>
> Key: JBDS-2823
> URL: https://issues.jboss.org/browse/JBDS-2823
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.Beta1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
> Attachments: jbds-install-script-fail.png
>
>
> Please see screenshot attached for more details.
> Script used: https://devstudio.jboss.com/usage/scripted-install/jbds-install.cmd
--
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, 5 months