[JBoss JIRA] (JBIDE-15483) generate content in staging/_composite_/core/{trunk, 4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15483?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15483:
------------------------------------
[~dgolovin] Since we now have JBIDE-16309 fixed, I'd like to close this as WONTFIX unless you have more suggestions for how to implement this.
Please provide comments here and in JBIDE-15482, or I'll just close this.
> generate content in staging/_composite_/core/{trunk,4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15483
> URL: https://issues.jboss.org/browse/JBIDE-15483
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.x
>
>
> Because the content in builds/staging/\{JOB_NAME}/all/repo/ and builds/staging.previous/\{JOB_NAME}/all/repo/ is moving to builds/staging/\{JOB_NAME}/\{BUILD_ID_N} and builds/staging/\{JOB_NAME}/\{BUILD_ID_N-1}, we need to generate a list of matching build URLs for inclusion in the composite*.xml files, perhaps based on a template that's stored in github (to define which projects to include).
> Parameters to the generation would need to be:
> a) template
> b) number of builds per project to include (1, for stable_branch or 2, for trunk)
> Constraints:
> * Need to ensure that the generated files are always fresher than anything pulled from github via rsync, so templates should not be called "compositeContent.xml" but rather "compositeContent.template.xml"
> * Need to be able to run this regeneration as a Jenkins job, perhaps as the first step in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> Worries:
> * What happens if the regen happens and then a jbosstools-cleanup.sh fires minutes later, wiping out that N-1 build? Does jbosstools-cleaup.sh need to regen these files too?
> Default operation of jbosstools-cleanup.sh as called from publish_new.sh and publish.sh is to keep the last 5 builds and anything newer than 5 days old; if there are no such builds, it will always keep the last build in a folder:
> {code}./jbosstools-cleanup.sh --keep 5 --age-to-delete 5 --childFolderSuffix /all/repo/{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
12 years, 3 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16309.
------------------------------
Close, nothing left to do.
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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, 3 months
[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2956:
-------------------------------------------
look at the eclipse.properties I can see quite some differences, but in the spring area the plugins and features are the same.
The only difference that might be noteworthy for this context is that in the JBDS case not all of the spring plugins have started - many of them is in "starting" mode.
At what time did you generate the logs ? Had you just started JBDS or had it been running for a while ?
> Spring IDE's associated projects and files cannot be created
> ------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: Fedora 17
> Reporter: Marián Labuda
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
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, 3 months
[JBoss JIRA] (JBIDE-16644) Cordova Plugins are not loaded when they are not supported on certain platforms
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16644?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-16644:
------------------------------------
Assignee: Gorkem Ercan
Correct, we are processing the js modules on the incorrect place and js module gets lost if the a node for the platform does not exist on the plugin.xml
> Cordova Plugins are not loaded when they are not supported on certain platforms
> -------------------------------------------------------------------------------
>
> Key: JBIDE-16644
> URL: https://issues.jboss.org/browse/JBIDE-16644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I added the [Cordova StatusBar plugin|https://github.com/apache/cordova-plugins/tree/master/statusbar] (supported on iOS and not on Android) to my HMT project. When run this project on an Android emulator, the statusbar plugin is not loaded by the tooling, even though a reference to the plugin is added to the starting page of the app - index.html.
> See the [referenced screenshot|http://www.screencast.com/t/Jq5wZWLI8Ho] as an example.
> This is not the case when using the Cordova CLI. The CLI commands ensure that the JS file for the StatusBar plugin is loaded on Android. While a 404 is not harmful in this case, it is certainly not recommended.
> As a note, we must try and match the Cordova CLI behavior as much as possible, and this is a slight deviation from it - the iOS-specific plugin is referenced in {{android/assets/www/cordova_plugins.js}} in the Android project but is not copied to the {{android/assets/www/plugins}} directory in the project.
--
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, 3 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15895:
--------------------------------------
Can you please post a complete example. I was not able to find the "testing page" "on phonegap web page" and for me it seems to work.
I am closing this for now please reopen with a complete example.
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 3 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15895.
----------------------------------
Resolution: Cannot Reproduce Bug
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 3 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15895:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 3 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-15895:
------------------------------------
Assignee: Gorkem Ercan
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Fix For: 4.2.x
>
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 3 months