April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15332: ----------------------------------- Fix Version/s: LATER (was: 4.3.0.Alpha2) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19585. ------------------------------------ Fix Version/s: 4.3.0.Alpha2 Resolution: Done Change was merged. TP is respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19585: -------------------------------------- Assignee: Ilya Buziuk > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3285: -------------------------------------- Added Easymport feature to Central: https://github.com/jbosstools/jbosstools-central/pull/330 [~fbricon] Can you please merge it ASAP? this new feature has to get into the aggregator and then into the product definition. > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3285: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/140, https://github.com/jbosstools/jbosstools-central/pull/330 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/140) > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19585: --------------------------------------- It's fine for me, too. > Mixture of jetty 9 bundles versions in the TP > --------------------------------------------- > > Key: JBIDE-19585 > URL: https://issues.jboss.org/browse/JBIDE-19585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Priority: Minor > > Basically, here is the list of jetty 9 bundles in the TP: > 1. org.eclipse.jetty.http_9.2.9.v20150224.jar > 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar > 3. org.eclipse.jetty.http_9.2.9.v20150224.jar > 4. org.eclipse.jetty.io_9.2.9.v20150224.jar > 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar > 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar > 7. org.eclipse.jetty.security_9.2.9.v20150224.jar > 8. org.eclipse.jetty.server_9.2.9.v20150224.jar > 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar > 10. org.eclipse.jetty.util_9.2.9.v20150224.jar > 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff) > The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Priority: Critical (was: Major) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18772: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19025: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 April 2015