July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13127) Scala jars added to deployment when they should not

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13127?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13127: ------------------------------------- I opened a bug in scala ide to get scala container serialized : https://scala-ide-portfolio.assembla.com/spaces/scala-ide/support/tickets... > Scala jars added to deployment when they should not > --------------------------------------------------- > > Key: JBIDE-13127 > URL: https://issues.jboss.org/browse/JBIDE-13127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Galder Zamarreño > Assignee: Fred Bricon > Labels: scala, upstream > Fix For: 4.2.x > > > Hmmm, seems like we've gone the opposite way now. > My lift dependencies, which bring in Scala, are defined as provided: > {code}<dependency> > <groupId>net.liftweb</groupId> > <artifactId>lift-mapper_${version.scala}</artifactId> > <version>2.4</version> > <scope>provided</scope> > </dependency>{code} > And now, you're adding the Scala jars to the WAR when it shouldn't? See screenshot: > https://dl.dropbox.com/u/6148072/Screen%20Shot%202012-11-14%20at%206.26.4... > Who's responsibility is this? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because it's using "multiple" with bugs in p2.mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2673: ---------------------------------- Default must be multiple since unified site is not publicly accessible to everyone. Therefore have opened JBDS-2674 to track moving the JBDS TP site to a public location, which would enable using "unified" as the default for both VPN and non-VPN users. > Can't build JBDS because it's using "multiple" with bugs in p2.mirrors > ---------------------------------------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2674) Publish JBDS TP onto download.jboss.org instead of internal server so that JBDS can build from sources using -Dtpc.targetKind=unified as default

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2674: -------------------------------- Summary: Publish JBDS TP onto download.jboss.org instead of internal server so that JBDS can build from sources using -Dtpc.targetKind=unified as default Key: JBDS-2674 URL: https://issues.jboss.org/browse/JBDS-2674 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, updatesite Affects Versions: 7.0.0.Beta2 Reporter: Nick Boldt As reported in JBDS-2673 (which conflicts with the needs of JBDS-2456), we need a solution which accommodates both Nick's and Max's definitions of "Correct" and "Simple". Thus, to allow all JBDS builds to default to using the unified TP instead of the multiple one from which the unified is built, we must publish the TP to a site which is fully public (eg., on download.jboss.org instead of www.qa). Then the JBDS product root pom can be updated to default to "unified" and builds can be done by anyone regardless of VPN access, without needing a different config for Jenkins vs. non-VPN users. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15059: ------------------------------------------ I'll have to double check the code in EGit. The git cmd line definitely updates the local tracking branch when you push. If this is done via a fetch (or an internal porcellaine cmd) is not clear to me: http://www.gitguys.com/topics/tracking-branches-and-remote-tracking-branc... - "Publish The Local Commit" 'Next, the git push command causes the remote-tracking branch to be updated with the latest updates from the remote repository' > Server adapter: tells me that there are local commits that I can publish even though there are none > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-15059 > URL: https://issues.jboss.org/browse/JBIDE-15059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.CR1, 4.2.0.Alpha1 > > Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png > > > 1. EXEC: launch OpenShift Application wizard > 2. EXEC: create a new application and have it imported to your workspace > 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes* > !committed-changes-to-publish.png! > 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of origin by 1) > !is-ahead-1.png! (*wrong!* since we pushed) > 5. EXEC: Pick your server adapter and tell it to publish to OpenShift > Result: > The adapter tells you that you that there are local commits that you may push. (*wrong!*) > !committed-changes-to-publish.png! > Expected: > We just pushed there cannot be local commits that were not pushed yet > 6. EXEC: Confirm the dialog and tell it to publish > Result: > It tells you that OpenShift is already up-to-date (which is true!) > !already-up-to-date.png! > 7. EXEC: pick Team->Fetch from Upstream > 8 ASSERT: > The remote "is ahead of" state of the current branch compared to origin is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed). > !is-ahead-0.png! > If you now publish via adapter it'll tell you that there are no local changes that you can push. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because it's using "multiple" with bugs in p2.mirrors

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2673: ------------------------------------------- nick - if this can't be the default then at least make the build use unified ? > Can't build JBDS because it's using "multiple" with bugs in p2.mirrors > ---------------------------------------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14114) Some eclipse bundles versions are higher in JBT 4.0 than in 4.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14114?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-14114. -------------------------------- Resolution: Done As all the reported issues here are either upstream problems we can't fix, or no longer issues within JBT, and the latest builds of the versionwatch job [1] are blue as of Jun 27, I'm going to resolve this issue. [1] http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ [~jpeterka] if that's wrong, please reopen. If you're satisfied, feel free to close. > Some eclipse bundles versions are higher in JBT 4.0 than in 4.1 > --------------------------------------------------------------- > > Key: JBIDE-14114 > URL: https://issues.jboss.org/browse/JBIDE-14114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, upstream > Affects Versions: 4.1.0.Alpha1 > Environment: Windows > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Priority: Blocker > Fix For: 4.1.0.CR1 > > Attachments: JBDS Version Watch.html > > > Some eclipse bundles have versions higher in JBT 4.0 than in 4.1. > There is a list: > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... *Eclipse version bug: https://bugs.eclipse.org/406225 * > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... *Eclipse version bug: https://bugs.eclipse.org/406224 * > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 2.0.108 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 3.0.401 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 2.1.401 OK in Alpha2 > http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... 1.2.2 OK in Alpha2 (maybe should be changed 1.2.200 or 1.3.0?) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14118) Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14118?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14118. ------------------------------ In JBT 4.0: {code:title=http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno/plugins/} org.jboss.tools.forge.core_1.1.0.Final-v20130327-0622-B107.jar org.jboss.tools.forge.runtime.ext_1.1.0.Final-v20130327-0622-B107.jar org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar org.jboss.tools.forge.ui_1.1.0.Final-v20130327-0622-B107.jar {code} Whereas in JBT 4.1: {code:title=http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/plugins/} org.jboss.tools.forge.core_1.2.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.runtime.ext_1.2.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.runtime_1.3.2.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.ui_1.2.0.CR1-v20130628-2152-B84.jar {code} Plus these new plugins: {code} org.jboss.tools.forge.ui.ext_1.0.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.ui.notifications_1.0.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.ui.wizards_1.0.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge2.runtime_2.0.0.CR1-v20130628-2152-B84.jar org.jboss.tools.forge.core.ext_1.0.0.CR1-v20130628-2152-B84.jar {code} So therefore we've upversioned correctly, and org.jboss.tools.forge.runtime is currently at 1.3.2. > Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0? > ----------------------------------------------------------------- > > Key: JBIDE-14118 > URL: https://issues.jboss.org/browse/JBIDE-14118 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge, updatesite > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Beta1 > > > In JBT 4.0.1: > org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar > In JBT 4.1.0.Alpha2b: > org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar > So timestamp goes up, but service does not? > Should this plugin be versioned 1.2.200? Or should it be 1.3.0? Also, if you're moving up this *one* plugin, [~maxandersen] will probably want you to bump the feature/plugin versions for the whole project to the same value, 1.2.200 or 1.3.0. > The big concern here is that we don't want Eclipse to see org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar (from JBT 4.0 / Juno) as a "newer" plugin than org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar (from JBT 4.1 / Kepler) because of the way osgi view "Final" as newer than "Alpha". > If both work equally well in Juno *and* in Kepler, this isn't a showstopper unless one of them prevents installation of something else in JBoss Tools due to platform conflicts. > You can bump all poms/manifests/feature.xml files in one operation like this: > {code:title=https://gist.github.com/nickboldt/4548933/raw/ec20825dbe7a3f07a9d388015564d2ced0f79885/upversion.sh} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=x.y.z-SNAPSHOT > {code} > See also: http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13040) Enable individual emails in Jenkins based on Git changes

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13040?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13040. ------------------------------------ Fix Version/s: 4.1.0.CR1 (was: 4.1.x) (was: 4.2.x) Resolution: Done I re-enabled individual mailing on all jobs. > Enable individual emails in Jenkins based on Git changes > -------------------------------------------------------- > > Key: JBIDE-13040 > URL: https://issues.jboss.org/browse/JBIDE-13040 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.CR1 > > > Now we have moved to Git, we can probably re-enable individual mailing from Jenkins. Previous issue appeared to be an issue with SVN plugin, which we don't use any longer. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because of p2.mirrors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2673: -------------------------------------- Ok. Isn't anyone who wants to build JBDS supposed to have VPN available? That sounds like a fair requirement to me. Also, couldn't we simply put JBDS target on a public site (download.jboss.org)? There is nothing to hide in our target-platform. As build is now running again, we can reduce the priority of this Jira and postpone it to later. WDYT ? > Can't build JBDS because of p2.mirrors > -------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because it's using "multiple" with bugs in p2.mirrors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2673: --------------------------------- Summary: Can't build JBDS because it's using "multiple" with bugs in p2.mirrors (was: Can't build JBDS because of p2.mirrors) > Can't build JBDS because it's using "multiple" with bugs in p2.mirrors > ---------------------------------------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- 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, 9 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 July 2013