[JBoss JIRA] (JBIDE-24417) getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24417?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24417:
-------------------------------
Sprint: devex #131 April 2017
> getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24417
> URL: https://issues.jboss.org/browse/JBIDE-24417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.4.Final
>
>
> Ran this:
> {code}
> /tmp/jbt.github/jbosstools-build-ci/util/getProjectRootPomParents.sh -updateRootPom -b jbosstools-4.4.x -b2 jbosstools-4.4.x -pv 4.4.4.Final -w1 /tmp/jbt.github -vjbt 4.4.4.Final -vds 10.4.0.GA -tpmin 4.60.3.Final -tpmax 4.63.0.Final -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" -jirahost https://issues.jboss.org{code}
> and the output suggested that all the root poms are already updated because they have 4.4.4.Final-SNAPSHOT (not 4.4.4.Final).
> So... need to fix this ASAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24417) getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24417?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-24417.
------------------------------
Resolution: Done
> getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24417
> URL: https://issues.jboss.org/browse/JBIDE-24417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.4.Final
>
>
> Ran this:
> {code}
> /tmp/jbt.github/jbosstools-build-ci/util/getProjectRootPomParents.sh -updateRootPom -b jbosstools-4.4.x -b2 jbosstools-4.4.x -pv 4.4.4.Final -w1 /tmp/jbt.github -vjbt 4.4.4.Final -vds 10.4.0.GA -tpmin 4.60.3.Final -tpmax 4.63.0.Final -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" -jirahost https://issues.jboss.org{code}
> and the output suggested that all the root poms are already updated because they have 4.4.4.Final-SNAPSHOT (not 4.4.4.Final).
> So... need to fix this ASAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24417) getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24417?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24417:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.5.0.Final)
> getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24417
> URL: https://issues.jboss.org/browse/JBIDE-24417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.4.Final
>
>
> Ran this:
> {code}
> /tmp/jbt.github/jbosstools-build-ci/util/getProjectRootPomParents.sh -updateRootPom -b jbosstools-4.4.x -b2 jbosstools-4.4.x -pv 4.4.4.Final -w1 /tmp/jbt.github -vjbt 4.4.4.Final -vds 10.4.0.GA -tpmin 4.60.3.Final -tpmax 4.63.0.Final -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" -jirahost https://issues.jboss.org{code}
> and the output suggested that all the root poms are already updated because they have 4.4.4.Final-SNAPSHOT (not 4.4.4.Final).
> So... need to fix this ASAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4394) Add requirement rh-java-common-google-gson
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4394?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4394:
-----------------------------
Sprint: devex #132 May 2017
> Add requirement rh-java-common-google-gson
> ------------------------------------------
>
> Key: JBDS-4394
> URL: https://issues.jboss.org/browse/JBDS-4394
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, rpm
> Affects Versions: 11.0.0.AM1
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> Add requirement rh-java-common-google-gson to the RPM spec file \[1\].
> \[1\] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu...
> ----
> *Reason:*
> After update form Devstudio 10.2 to 10.4 I had this error in the eclipse log:
> {code}
> !ENTRY org.eclipse.jgit.pgm 4 0 2017-05-12 14:03:44.808
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jgit.pgm [231]
> Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server.fs; version="[4.6.1,4.7.0)"
> -> Export-Package: org.eclipse.jgit.lfs.server.fs; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet, javax.servlet.http, org.eclipse.jgit.lfs.server, org.eclipse.jgit.lfs.lib"
> org.eclipse.jgit.lfs.server [230]
> Unresolved requirement: Import-Package: com.google.gson; version="[2.2.4,3.0.0)"
> Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server; version="[4.6.1,4.7.0)"
> -> Export-Package: org.eclipse.jgit.lfs.server; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet.http, org.eclipse.jgit.lfs.lib"
> ...
> ...
> !ENTRY org.eclipse.wst.jsdt.js.node 4 0 2017-05-12 14:03:46.661
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.wst.jsdt.js.node [653]
> Unresolved requirement: Require-Bundle: com.google.gson; bundle-version="[2.2.4,3.0.0)"
> {code}
> Steps to reproduce:
> # Disable RHSCL 2.4 and Devstudio snapshot repo
> # Add RHSCL 2.3 and Devstudio stable repo
> # yum remove rh-*
> # yum install rh-eclipse46-devstudio (should install 10.2.0.GA)
> # check if eclipse works (I had no errors in the log)
> # Disable RHSCL 2.3 and Devstudio stable repo
> # Enable RHSCL 2.4 and Devstudio snapshot repo
> # rm -rf ~/.eclipse
> # Start the Eclipse with -clean
> # There should be error I mentioned above. I didn't see any impact to users, egit worked fine.
> # sudo yum update "rh-*"
> {code}
> Updating:
> rh-java-common-google-gson noarch 2.2.4-1.el7 rh-eclipse46-build 177 k
> rh-java-common-javapackages-tools noarch 4.3.2-1.14.el7 rh-eclipse46-build 95 k
> rh-java-common-lucene5 noarch 5.4.1-2.3.el7 rh-eclipse46-build 2.2 M
> rh-java-common-lucene5-analysis noarch 5.4.1-2.3.el7 rh-eclipse46-build 1.3 M
> rh-java-common-lucene5-analyzers-smartcn noarch 5.4.1-2.3.el7 rh-eclipse46-build 3.4 M
> rh-java-common-lucene5-queries noarch 5.4.1-2.3.el7 rh-eclipse46-build 211 k
> rh-java-common-lucene5-queryparser noarch 5.4.1-2.3.el7 rh-eclipse46-build 339 k
> rh-java-common-lucene5-sandbox noarch 5.4.1-2.3.el7 rh-eclipse46-build 246 k
> rh-java-common-python-javapackages noarch 4.3.2-1.14.el7 rh-eclipse46-build 87 k
> rh-maven33-runtime
> {code}
> # Restart Eclipse, it will start without errors.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24225:
-------------------------------
Sprint: devex #132 May 2017
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ...
> !maven-releng-fetch.png|thumbnail!
> ... and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months