January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19047) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Nick . (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19047?page=com.atlassian.jira.plugi... ] Nick . updated JBIDE-19047: --------------------------- Attachment: sample-with-unresolved-dep.zip PFA updated project with unsatisfied dependency. > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-19047 > URL: https://issues.jboss.org/browse/JBIDE-19047 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Environment: Ubuntu 14.04, Wildfly 8.2.0 FInal, Eclipse Luna > Reporter: Nick . > Assignee: Fred Bricon > Fix For: 4.3.x > > Attachments: sample-with-unresolved-dep.zip, sample.zip, settings.zip > > > Hi, > I have a maven EAR project, which contains a couple of WAR and JAR files. I'm using Eclipse Luna (tried STS and IntelliJ ) IDE with JBoss Tools 1.6.0 (latest). > When I try to deploy my EAR to Wildfly (as well as in EAP 6.2.0) with JBoss Tools from eclipse i'm facing the following issues. > My Jars (external jars and project jar) are getting copied into WEB-INF/lib and EAR/lib, where i expected it to be only in EAR/lib. > EAR application.xml is not getting copied into EAR/META-INF/ folder > But when i use command line to build my project , i'm not experiencing the above issue. > FYI : We are using <skinnyWars>true</skinnyWars>. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19110) Add Mockito to Target platform 4.50.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19110?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19110: --------------------------------------------- Is JBIDE-18053 about powermock still relevant ? That was previous suggestion from openshift but had issues because of library incompatibilities which might have been fixed since then. > Add Mockito to Target platform 4.50.0 > ------------------------------------- > > Key: JBIDE-19110 > URL: https://issues.jboss.org/browse/JBIDE-19110 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Matej Gagyi > Priority: Optional > Fix For: 4.3.0.Final > > > *Reason:* Needed to simplify testing of jbosstools-openshift > *Project page/sources:* https://github.com/mockito/mockito > *Version:* 1.9.5 > *License and owner:* MIT > *Original p2 repo:* http://download.eclipse.org/tools/orbit/downloads/drops/R20140525021250/r... > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/orbit/S20141129... > *Include Sources:* Yes > *Affected projects:* > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > diff --git a/jbosstools/multiple/jbosstools-multiple.target b/jbosstools/multiple/jbosstools-multiple.ta > index c17fb92..51f6076 100644 > --- a/jbosstools/multiple/jbosstools-multiple.target > +++ b/jbosstools/multiple/jbosstools-multiple.target > @@ -10,8 +10,6 @@ >  >  > @@ -86,6 +84,10 @@ > <unit id="org.apache.jasper.glassfish" version="2.2.2.v201205150955"/> >  > <unit id="org.slf4j.api" version="1.7.2.v20121108-1250"/> > + > +  > + <unit id="org.mockito" version="1.9.5.v201311280930"/> > + <unit id="org.objenesis" version="1.0.0.v201105211943"/> > </location> > > <!-- TODO: make sure these versions match up across JBT/JBDS/Central target platforms (JBIDE-17429) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19110) Add Mockito to Target platform 4.50.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19110?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19110: --------------------------------------------- This has been attempted added multiple times in past. Is there a reason we can't just use the mockito IS have in their target platform that comes from locus ? > Add Mockito to Target platform 4.50.0 > ------------------------------------- > > Key: JBIDE-19110 > URL: https://issues.jboss.org/browse/JBIDE-19110 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Matej Gagyi > Priority: Optional > Fix For: 4.3.0.Final > > > *Reason:* Needed to simplify testing of jbosstools-openshift > *Project page/sources:* https://github.com/mockito/mockito > *Version:* 1.9.5 > *License and owner:* MIT > *Original p2 repo:* http://download.eclipse.org/tools/orbit/downloads/drops/R20140525021250/r... > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/orbit/S20141129... > *Include Sources:* Yes > *Affected projects:* > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > diff --git a/jbosstools/multiple/jbosstools-multiple.target b/jbosstools/multiple/jbosstools-multiple.ta > index c17fb92..51f6076 100644 > --- a/jbosstools/multiple/jbosstools-multiple.target > +++ b/jbosstools/multiple/jbosstools-multiple.target > @@ -10,8 +10,6 @@ >  >  > @@ -86,6 +84,10 @@ > <unit id="org.apache.jasper.glassfish" version="2.2.2.v201205150955"/> >  > <unit id="org.slf4j.api" version="1.7.2.v20121108-1250"/> > + > +  > + <unit id="org.mockito" version="1.9.5.v201311280930"/> > + <unit id="org.objenesis" version="1.0.0.v201105211943"/> > </location> > > <!-- TODO: make sure these versions match up across JBT/JBDS/Central target platforms (JBIDE-17429) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Alexander Kurtakov commented on JBDS-3331: ------------------------------------------ Do you have some logic that prefers xulrunner on rhel6 but webkit on rhel 7 ? SWT in DTS is compiled without xulrunner as xulrunner is not ABI stable and swt can be compiled only against ancient versions which are not available in RHEL. If you have such preference would you please try preferring webkit on RHEL 6 too? > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RHEL66_jbosstools-diagnostics-20150127000831.zip, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3331: ----------------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RHEL66_jbosstools-diagnostics-20150127000831.zip, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19056: ---------------------------------------- Mojo was merged to codebase. Next step to enable this would be to merge change in parent pom. Any objection to do this ASAP? > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- Mojo updated according to [~maxandersen]'s comments. > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19056: ---------------------------------------- [~rob.stryker] It's because jbosstools-4.2.x branch isn't using the version of parent pom (4.3.0.Alpha1-SNAPSHOT) that's in my PR, but an older one that doesn't configure the validate mojo. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19056: ------------------------------------- I shouldn't say the "suite" passed. What I mean is the build was a success. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19056: ------------------------------------- I gave it a try on jbt4.2.x in jbosstools-server, and seriously saw no change at all. The suite still passed. {code} cd jbosstools-maven-plugins/tycho-plugins/repository-utils git checkout mistria/JBIDE-19056 mvn install cd ../../../jbosstools-build/parent git checkout mistria/JBIDE-19056 mvn install cd ../../jbosstools-server git checkout jbosstools-4.2.x mvn clean install -DskipTests {code} The build is marked as a success. I'm not seeing any failure here. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015