[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17207:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.CR1)
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.x
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18053) Add Powermock to the target platform
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18053:
----------------------------------------
We've been in touch with the author of Powermock-osgi and it's not clear whether a different JUnit and Hamcrest are required. There is no way we put in our TP a different version of JUnit and Hamcrest. So we're postponing this change.
If it's OK to use Orbit's hamcrest and JUnit, then it's just a matter of accepting to use the Mockito Powermock-osgi is shipping instead of Locus' one, or to adapt Locus one to export necessary packages for Powermock-osgi
> Add Powermock to the target platform
> ------------------------------------
>
> Key: JBIDE-18053
> URL: https://issues.jboss.org/browse/JBIDE-18053
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.2.x
> Reporter: Jeff Cantrill
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> *Reason:* To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7
> *License and owner:* Apache 2.0 / https://github.com/jayway
> *Original p2 repo:* http://powermock-osgi.googlecode.com/svn/updateSite/1.5.4.1/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/powermock/1.5.4.1/
> *Sources:* https://code.google.com/p/powermock-osgi/ , http://powermock-osgi.googlecode.com/svn/trunk/
> *Affected projects:* OpenShift tests
> *Include in JBDS:* No
> *Type of dependency:* testing
> *List of bundles added/removed:*
> {code}
> + <unit id="org.powermock.mockito-junit.feature.feature.group" version="1.5.4.1"/>
> + <unit id="org.objenesis" version="2.1.0"/>
> + <unit id="javassist" version="3.18.1.GA"/>
> {code}
> *p2diff report:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> > org.mockito.mockito-core [1.9.5]
> > javassist [3.18.1.GA]
> > org.powermock.powermock-api-support [1.5.4]
> > org.powermock.powermock-reflect [1.5.4]
> > org.powermock.powermock-api-mockito [1.5.4]
> > org.powermock.powermock-module-junit4-common [1.5.4]
> > org.powermock.powermock-module-junit4 [1.5.4]
> > org.powermock.powermock-core [1.5.4]
> > org.objenesis [2.1.0]
> === Summary ===
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 9 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-16626.
-----------------------------------
Resolution: Rejected
Agree, rejecting. At the time of creating a issue I did not have this information.
> OpenShift Server Adapter: Binary deployment
> -------------------------------------------
>
> Key: JBIDE-16626
> URL: https://issues.jboss.org/browse/JBIDE-16626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final, 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment.
> Current workflow is following:
> PRESTEPS:
> 1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application)
> 2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers...
> 3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge).
> 4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index)
> 5. Push application to OpenShift (e.g. context menu of application - Team - Commit...)
> BINARY DEPLOYMENT
> 1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title).
> 2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is built in deployment folder as ROOT.war.
> 3. Add ROOT.war to git index (context menu - Team - Add to index)
> 4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter.
> 5. Confirm push.
> My idea of binary deployment is:
> 1. User change something in application
> 2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index.
> 3. Confirm to push.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14818:
----------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.x)
> Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Labels: server_adapter_editor
> Fix For: 4.2.1.Final
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14818:
----------------------------------------
Assignee: Rob Stryker
> Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Labels: server_adapter_editor
> Fix For: 4.2.x
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months