[JBoss JIRA] (JBDS-1592) Document procedures, server URLs, who has access, etc. for publishing JBDS to early access & CSP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-1592?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-1592:
----------------------------------
[~maxandersen]: http://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/20...
> Document procedures, server URLs, who has access, etc. for publishing JBDS to early access & CSP
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-1592
> URL: https://issues.jboss.org/browse/JBDS-1592
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Plan
> Reporter: Nick Boldt
> Assignee: mark yarborough
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> Document:
> * procedures,
> * list of server URLs,
> * who has access, usernames/passwords, etc.
> publishing JBDS to early access & CSP
> Suggest putting new doc in here:
> http://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13718) Publish script fails for new components
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13718?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13718:
------------------------------------
Problem... if I switch to use curl, it could fail because not all slaves have curl. Need a way to make wget fail gracefully when it 404s.
> Publish script fails for new components
> ---------------------------------------
>
> Key: JBIDE-13718
> URL: https://issues.jboss.org/browse/JBIDE-13718
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> While trying to publish the new "jbosstools-aerogear" component nightly site, the publish script fails telling
> {code}
> + cd /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/cordova
> + wget http://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publi... -q --no-check-certificate -N
> + . publish.sh
> +++ mktemp -d
> ++ tmpdir=/tmp/tmp.DUivo13746
> ++ mkdir -p /tmp/tmp.DUivo13746
> ++ STAGINGDIR=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master
> ++ PUBLISHPATHSUFFIX=
> ++ [[ -n '' ]]
> ++ JOBNAMEREDUX=jbosstools-aerogear_master
> ++ JOBNAMEREDUX=aerogear_master
> ++ [[ '' == \Y\e\s ]]
> ++ ZIPSUFFIX=SNAPSHOT
> ++ SNAPNAME=jbosstools-aerogear_master-Update-SNAPSHOT.zip
> ++ SRCSNAME=jbosstools-aerogear_master-Sources-SNAPSHOT.zip
> ++ SUFFNAME=-Update-SNAPSHOT.zip
> ++ [[ '' == '' ]]
> ++ DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools
> ++ [[ '' == '' ]]
> ++ INTRNALDEST=/home/hudson/static_build_env/jbds
> ++ rm -fr /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master
> ++ z=
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/aggregate/site/target ]]
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/aggregate/site/site/target ]]
> ++ [[ -d /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/site/target ]]
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ bl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> ++ rm -f /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> ++ wget -q http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/consol... -O /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt --timeout=900 --wait=10 --random-wait --tries=10 --retry-connrefused --no-check-certificate
> +++ cat /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/BUILDLOG.txt
> +++ grep org/jboss/tools/parent/
> +++ head -1
> +++ sed -e 's#.\+org/jboss/tools/parent/\(.\+\)/\(maven-metadata.xml\|parent.\+\)#\1#'
> +++ sed -e s#-SNAPSHOT##
> +++ sed -e 's#[0-9].[0-9].[0-9].##'
> ++ BUILD_ALIAS=Alpha1
> ++ wgetParams='--timeout=900 --wait=10 --random-wait --tries=30 --retry-connrefused --no-check-certificate --server-response'
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ rl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/REVISION
> +++ find /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master -mindepth 2 -maxdepth 3 -name .git
> ++ [[ -n /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/.git ]]
> ++ rl=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION
> ++ rm -f /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.txt /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml
> ++ wget -O /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml 'http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/api/xm...' --timeout=900 --wait=10 --random-wait --tries=30 --retry-connrefused --no-check-certificate --server-response
> --2013-03-05 07:00:07-- http://hudson.qa.jboss.com/hudson/job/jbosstools-aerogear_master/2/api/xm...
> Resolving hudson.qa.jboss.com... 10.16.90.43
> Connecting to hudson.qa.jboss.com|10.16.90.43|:80... connected.
> HTTP request sent, awaiting response...
> HTTP/1.1 200 OK
> Date: Tue, 05 Mar 2013 12:00:07 GMT
> X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
> Content-Type: application/xml;charset=UTF-8
> Connection: close
> Length: unspecified [application/xml]
> Saving to: `/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml'
> 0K 34.5M=0s
> 2013-03-05 07:00:07 (34.5 MB/s) - `/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml' saved [193]
> ++ sed -e 's#<lastBuiltRevision><SHA1>\([a-f0-9]\+\)</SHA1><branch><SHA1>\([a-f0-9]\+\)</SHA1><name>\([^<>]\+\)</name></branch></lastBuiltRevision>#\3\@\1#g' /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/GIT_REVISION.xml
> ++ sed -e 's#<[^<>]\+>##g'
> ++ mkdir -p /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs
> ++ ALLREVS=/qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/results/jbosstools-aerogear_master/logs/ALL_REVISIONS.txt
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> ++ [[ '' != \t\r\u\e ]]
> ++ [[ jbosstools-aerogear_master != jbosstools-aerogear_master ]]
> +++ find /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master -mindepth 2 -maxdepth 3 -name .git
> ++ [[ -n /qa/services/hudson/hudson_workspace/workspace/jbosstools-aerogear_master/sources/.git ]]
> +++ wget -nc -q -k http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m... -O -
> ++ PREV_REV=
> Build step 'Execute shell' marked build as failure
> {code}
> It looks like the publish.sh script except a previous version to be already available.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13569) Error when waiting for application to become reachable
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13569?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13569:
-------------------------------------------------
Bill DeCoste <wdecoste(a)redhat.com> made a comment on [bug 895507|https://bugzilla.redhat.com/show_bug.cgi?id=895507]
Andre are you still seeing the base cartridge being returned in version 1.0? Looks like we are - the tests expecting 0 carts are still failing.
> Error when waiting for application to become reachable
> ------------------------------------------------------
>
> Key: JBIDE-13569
> URL: https://issues.jboss.org/browse/JBIDE-13569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: error-waiting-for-reachable.png, JBT_0219.png
>
>
> {code}
> com.openshift.client.NotFoundOpenShiftException: Could not find any OpenShift resource at "http://testapp-1360837500661.rhcloud.com/health"
> at com.openshift.internal.client.RestService.request(RestService.java:101)
> at com.openshift.internal.client.ApplicationResource.waitForPositiveHealthResponse(ApplicationResource.java:510)
> at com.openshift.internal.client.ApplicationResource.waitForAccessible(ApplicationResource.java:487)
> at org.jboss.tools.openshift.express.internal.ui.job.WaitForApplicationJob.doRun(WaitForApplicationJob.java:50)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:35)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.NotFoundException: Could not find resource "http://testapp-1360837500661.rhcloud.com/health"
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:96)
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:97)
> ... 5 more
> Caused by: java.io.FileNotFoundException: http://testapp-1360837500661.rhcloud.com/health
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94)
> ... 7 more
> {code}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-13602.
-------------------------------------
Resolution: Done
Resetting resolution status after reopening JIRA for release notes text.
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> When trying to create a new Java EE Web Project, the following description is presented:
> {quote}
> This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1.
> This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
> Project based on the *null:null:null* Maven archetype
> {quote}
> If I go forward with the creation of the project, I get the following error message:
> {quote}
> Failed to create project.
> Root cause: For artifact null:null:null:pom : The group id cannot be empty.
> {quote}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13535) Wrong bom version is required
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13535?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-13535:
-----------------------------------------
[~ldimaggio] I manually changed the jboss-bom-enterprise-version value on page 3 of the Java EE web project wizard to 1.0.2.Final-redhat-1 (for EAP 6.0 as target runtime).
> Wrong bom version is required
> -----------------------------
>
> Key: JBIDE-13535
> URL: https://issues.jboss.org/browse/JBIDE-13535
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> Java EE Web Project has bom version always set to 1.0.4.Final-redhat-1 (which is version from EAP6.1) even if runtime is set to 6.0 or 6.0.1
> for HTML5 and Richfaces project it is the same, just the version is always set to 1.0.2.Final-redhat-1
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13602:
------------------------------------
Release Notes Text:
Cause:
Consequence:
Fix:
Result:
Affects: Release Notes
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> When trying to create a new Java EE Web Project, the following description is presented:
> {quote}
> This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1.
> This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
> Project based on the *null:null:null* Maven archetype
> {quote}
> If I go forward with the creation of the project, I get the following error message:
> {quote}
> Failed to create project.
> Root cause: For artifact null:null:null:pom : The group id cannot be empty.
> {quote}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13602:
------------------------------------
Release Notes Docs Status: Not Yet Documented (was: Not Required)
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> When trying to create a new Java EE Web Project, the following description is presented:
> {quote}
> This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1.
> This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
> Project based on the *null:null:null* Maven archetype
> {quote}
> If I go forward with the creation of the project, I get the following error message:
> {quote}
> Failed to create project.
> Root cause: For artifact null:null:null:pom : The group id cannot be empty.
> {quote}
--
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
13 years, 1 month