Proposed 4.27.0.AM1-SNAPSHOT target platform change(s): updated  eclipse I20230215-1800-M3 reddeer 4.5.0.M2 docker 5.10.0.202302212217  webtools S-3.29M3-20230220000017 jetty 10.0.13 cdt 11.0.0 simrel  202302241001-Simrel.2023-03-M3 m2e-wtp 1.6.0 orbit S20230214193619 jgit  6.5.0.202302221508-m3...
                                
                                
                                
                                    
                                        by sbouchet@redhat.com
                                    
                                
                                
                                        Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.27.0.AM1
jbt     TPs 4.27.0.AM1-SNAPSHOT 
central TPs 4.27.0.AM1-SNAPSHOT
Detail / Summary:
updated 
eclipse I20230215-1800-M3
reddeer 4.5.0.M2
docker 5.10.0.202302212217
webtools S-3.29M3-20230220000017
jetty 10.0.13
cdt 11.0.0
simrel 202302241001-Simrel.2023-03-M3
m2e-wtp 1.6.0
orbit S20230214193619
jgit 6.5.0.202302221508-m3
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-28878
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
attached to JIRA
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point 
TARGET_PLATFORM_VERSION_MAX at the new version, 4.27.0.AM1-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
    cd /path/to/jbosstools-target-platforms
    git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
    # or, using hub for git
    git checkout <pull-request-URL>
    mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
    cd /path/to/your/jbosstools-component
    mvn clean verify -Dtpc.version=4.27.0.AM1-SNAPSHOT       -Dtpc.targetKind=multiple
      
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
                                
                         
                        
                                
                                2 years, 8 months
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
            
        
        
        
                
                        
                                
                                
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        ACTION REQUIRED: JBoss Tools triage time
                                
                                
                                
                                    
                                        by sbouchet@redhat.com
                                    
                                
                                
                                        
As the current sprint 'Sprint #232 Feb 2023' draws to a close, it is time 
to review your unresolved issues! 
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.27.0.Final, 
to a future .x release, or LATER.
All unresolved issues for 4.27.0.AM1:
https://issues.redhat.com/issues/?jql=project%20in%20(JBIDE)%20AND%20fixV...
All *YOUR* unresolved issues for 4.27.0.AM1:
https://issues.redhat.com/issues/?jql=project%20in%20(JBIDE)%20AND%20fixV...
Once created, you can also begin scheduling your work for the upcoming 
sprint, 'Sprint #233 Mar 2023'. 
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
  move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint: 
  move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint: 
  move to .x (or LATER)
                                
                         
                        
                                
                                2 years, 8 months
                        
                        
                 
         
 
        
            
        
        
        
            
        
        
        
                
                        
                                
                                
                                        
                                
                         
                        
                                
                                
                                        
                                                
                                        
                                        
                                        Proposed 4.27.0.AM1-SNAPSHOT target platform change(s): removed  org.bouncycastle.bcpg 1.72.0.v20221013-1810...
                                
                                
                                
                                    
                                        by sbouchet@redhat.com
                                    
                                
                                
                                        Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.27.0.AM1
jbt     TPs 4.27.0.AM1-SNAPSHOT 
central TPs 4.27.0.AM1-SNAPSHOT
Detail / Summary:
removed org.bouncycastle.bcpg 1.72.0.v20221013-1810 
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-28745
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point 
TARGET_PLATFORM_VERSION_MAX at the new version, 4.27.0.AM1-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
    cd /path/to/jbosstools-target-platforms
    git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
    # or, using hub for git
    git checkout <pull-request-URL>
    mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
    cd /path/to/your/jbosstools-component
    mvn clean verify -Dtpc.version=4.27.0.AM1-SNAPSHOT       -Dtpc.targetKind=multiple
      
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
                                
                         
                        
                                
                                2 years, 9 months